Affichage des articles dont le libellé est accidentally. Afficher tous les articles
Affichage des articles dont le libellé est accidentally. Afficher tous les articles

dimanche 22 février 2015

Accidentally wiped *everything* - now stuck on samsung screen with lock topic






I have been using a custom rom via safestrap for a long time with no problem. Recently, I went to upgrade my rom and in safe strap, I foolishly did not back up. I did a factory wipe, but then I went into advanced wipe where I would normally check dalvik cache and a couple others, but this time I inadvertently checked ALL the boxes, including microsd card. So, I deleted EVERYTHING.

I took my external sd card out and put it in the computer, then copied my rom .zip file over to it. When I rebooted the phone though, I just get to the SAMSUNG screen with the little padlock on it and the word "custom" underneath. I can't seem to access safestrap to flash the rom over again.

What are my options?

Thanks!






mercredi 11 février 2015

Just downgraded. (Accidentally). Now I have some questions topic






This is NOT a how-to or anything. Don't try to follow in my footsteps of stupidity and brick your phone.

That being said...

XT 1060 (Verizon)

I have been running 4.4.4 for quite a while now. Right after JCase released sunshine for our phones. (I have an unlocked bootloader.)

I had it rooted, and tried out the 5.0 ROMs a while ago. Flashed back to stock to wait for the update when we heard it was coming "very soon". But tonight I got impatient and decided I was going to re-root and switch back to CM12. So, I opened Moto X Toolkit (love that tool) and installed TWRP. When I manually rebooted I forgot to boot into recovery. Don't know if that had anything to do with the ensuing problems or not, but after that, I couldn't get it to boot into recovery.

So, I flashed back to stock 4.4.4 again. Tried rebooting into stock recovery... no joy.
So off I go again... one more attempt to flash stock 4.4.4. This time, when it asked me if I wanted to reboot into bootloader or android, I tried to boot into android. Sadly I missed the "a" and typed "ndroid". The toolkit began doing something... looks like it was running the flash all over again. I let it do its thing, then very carefully typed "android" so I wouldnt screw it up again.

It rebooted perfectly, but once it was up and running, I noticed all of my icons were blue. I quickly jumped into the "about phone section and noticed it said "4.2.2".

This is not supposed to be possible, so at this point I was half panicking and half curious... so I decided to do an even more stupid thing and accept the updates.

I am now updated completely to 4.4.4. Zero issues... recovery works fine, radio is fine, wifi and BT are fine.


This leads me to two questions (Directed to developers)...

1) Is there a possibility this is repeatable?

2) My curiosity is about to get me into trouble... I have two more Moto X's that are 4.4.4. Locked BL. I would like to know what the worst case scenario is. I know there is a possibility of "bricking", but that term has not, for a long time, meant what it originally did. How badly "bricked" might it be? Bootloops? Chance of recovering by flashing stock firmware or RSD? Or truly bricked?






mardi 10 février 2015

[Q] I just find out I accidentally left the screen turned on for 7 hours on the same topic






Hey guys,
I just figured out that I left my Tablet screen turned on for like 7 hours on the same screen. The YouTube app was stuck and that's why the screen haven't auto turned off.

Is it any dangerous for the screen? Should I be worried? Just bought it yesterday :x

Thanks