A few days ago, I nearly bricked my phone had the Android guy with blue cube in his chest running. Which I managed to freeze the device, pulling up what looked like blue lit boot-loader appearance commands, which I prompted the reboot and returned to stock 4.0.4. My device has been running fine at the stock level. Sorry, for the long intro but here is my question. I went ahead and did the Root for Razr HD, have the latest drivers, usb debugging and pulled off the bug report and of course finished. The phone reboots as normal, loading to the “locked phone” state, all my apps are still active, which I find that Superuser is downloading and I update the binaries, and there I have root. As far as I can tell the device is just as responsive as it was prior to root, of course I am going to play around, doesn’t it seem odd? Should I be concerned with this dirty wipe?
Related
Had oxygen mod installed and franco kernel etc and after months of using it fine I thought the phone was running a bit funny so thought it reinstall fresh.
I knew the files were still on my sd card so i went to go into bootloader or recovery and i got a black screen that had a message Firmware Update Step 1/2 Unpacking.
It finished and appears to put me back on Android 2.21
I then rooted the phone and tried installing clockword mod etc but was having all sorts of problems getting marketplace to work. Can search for apps but when i click install nothing happens. I did enter my gmail account details for sync and it can list my apps available from my account.
USB is not working, it shows up sometimes in the top bar but when i click connect nothing happens and the phone freezes or reboots.
I cant get into the bootloader screen it instead brings up the standard Android bootloader and wont recognise my rom on the sdcard.
I tried rooting with superoneclick and although it roots the phone it seems to cause the issues???
Is Superoneclick the only way of rooting U8800?
One day, I got tired of the lame and boring Kindle interface, so I decided to use CyanogenMod to fix that problem. The Kindle Model I had was the 2012 HD Kindle "Soho" model, the one they had a warning on not to mod. So I previously rooted my tablet, and after unknowingly installing the wrong TWRP version, I got Recovery Reboot from the Google Play .apk I got. The first time I used the app, it gave me a red triangle saying I should reset to factory default or reboot. Each time I rebooted got the same triangle, but factory resetting fixed that problem. I logged my Amazon account back in and got all my apps back, then re-rooted and got the Google Play .apk from before. I saw the warning about the Soho models after going back to the CyanogenMod wiki to see what I did wrong, and I gave up and stayed with the boring interface. BUT, my Kindle ran out of battery, and it automatically shut down, and when I charged it, it rebooted into the familiar red triangle. I rebooted again a couple times, didn't work, factory reset didn't work either, and leaving it on for a few hours to completely drain the battery didn't work. I think the TWRP files were still hidden in the system files after I reset it the first time, and rebooting with charging the tablet activated the reboot into recovery, which triggered the TWRP files into action, but it was the wrong version, leading to this brick. How do you fix this? Do I need a fast boot cable?
Hi all. I have been trying to update my VS980 to Lollipop for a week now; I've tried absolutely everything I can think of / find in the forums, and nothing works.
The basic problem is this: I have a rooted (via Stump Root) Verizon G2 running stock 4.4.2. I wanted to upgrade it to Lollipop, so I unrooted with SuperSU and tried to OTA update it, but somehow it still knows it was once rooted, so the OTA fails. I have tried MANY things to fix/work around this, but here are the highlights:
Hard reset. The hard reset procedure completed ok, but when I try to then install the OTA update, it fails with "Err: 1117008." Settings -> About Phone still shows "Status: Rooted," even though I don't actually have root control anymore.
Use LG FLash Tool to flash back to factory stock: VS980011A_01.tot. Tried two different computers, using both Vista and Windows 10. Failed because the proper LGE Mobile USB Serial Port driver was never found/installed by Windows (despite it clearly working in the video).
Copied a text file called RCT_security containing "forel.lee" onto the SD card, b/c somehow that's supposed to reset the status to "unrooted." It didn't.
Re-rooted with Stump Root, manually installed TWRP to try to flash a ROM that way. Phone is now rooted again, but attempts to boot into recovery result in "secure boot error," and no TWRP.
Installed Quick Boot to boot directly into recovery. Fails with same "secure boot error."
Installed FreeGee and TWRP Manager, b/c now I'm just grasping at straws. FreeGee hangs on a black screen and does nothing. TWRP Manager tells me that TWRP is already installed; haven't tried using it to flash a new ROM from here, b/c that feels brickish.
Use AutoRec to fix the "secure boot error." Fails b/c running AutoRec results in it hanging at "checking for loki....installing," When I backed out after many minutes, I got an error that said "Tried to install Loki Tool, no luck."
I am out of ideas. I am pulling my hair out. The phone is working fine, except that it's stuck on 4.4.2. When I started, all I wanted was a working version of Lollipop, even if it was stock/unrooted. At this point, I'm so mad at Verizon/LG/Android for making this process so painful that I really just want to flash the latest CyanogenMod just for spite. But really -- I'll take anything.
Help?
jackpurrton said:
Hi all. I have been trying to update my VS980 to Lollipop for a week now; I've tried absolutely everything I can think of / find in the forums, and nothing works.
The basic problem is this: I have a rooted (via Stump Root) Verizon G2 running stock 4.4.2. I wanted to upgrade it to Lollipop, so I unrooted with SuperSU and tried to OTA update it, but somehow it still knows it was once rooted, so the OTA fails. I have tried MANY things to fix/work around this, but here are the highlights:
Hard reset. The hard reset procedure completed ok, but when I try to then install the OTA update, it fails with "Err: 1117008." Settings -> About Phone still shows "Status: Rooted," even though I don't actually have root control anymore.
Use LG FLash Tool to flash back to factory stock: VS980011A_01.tot. Tried two different computers, using both Vista and Windows 10. Failed because the proper LGE Mobile USB Serial Port driver was never found/installed by Windows (despite it clearly working in the video).
Copied a text file called RCT_security containing "forel.lee" onto the SD card, b/c somehow that's supposed to reset the status to "unrooted." It didn't.
Re-rooted with Stump Root, manually installed TWRP to try to flash a ROM that way. Phone is now rooted again, but attempts to boot into recovery result in "secure boot error," and no TWRP.
Installed Quick Boot to boot directly into recovery. Fails with same "secure boot error."
Installed FreeGee and TWRP Manager, b/c now I'm just grasping at straws. FreeGee hangs on a black screen and does nothing. TWRP Manager tells me that TWRP is already installed; haven't tried using it to flash a new ROM from here, b/c that feels brickish.
Use AutoRec to fix the "secure boot error." Fails b/c running AutoRec results in it hanging at "checking for loki....installing," When I backed out after many minutes, I got an error that said "Tried to install Loki Tool, no luck."
I am out of ideas. I am pulling my hair out. The phone is working fine, except that it's stuck on 4.4.2. When I started, all I wanted was a working version of Lollipop, even if it was stock/unrooted. At this point, I'm so mad at Verizon/LG/Android for making this process so painful that I really just want to flash the latest CyanogenMod just for spite. But really -- I'll take anything.
Help?
Click to expand...
Click to collapse
VICTORY IS MINE. Here's what I did:
I decided to focus on the LG Flash Tool as my best potential for a successful outcome, and I further decided to focus on the LG drivers, which didn't seem be installing properly. So:
Nuked my computer and installed a fresh version of Windows 10, to ensure no errant drivers were present.
Installed LG United drivers from the top of this page: [link deleted b/c xda won't let me post it] (LG VZW_United_WHQL_v2.16.1.exe)
Connected the phone in Media Sync mode and waited while Windows installed some more drivers.
Connected the phone in Internet Connection -> Ethernet mode and waited while Windows installed yet more Drivers. (I think this may be the step I missed in all previous attempts; once this was done, the correct LG driver appeared in Device Manager.)
Installed LG Flash Tool 2014 (download link in the description of the below video).
Followed the instructions in this video: [link deleted b/c xda won't let me post it] ...
... to install VS98027A_05.kdz, which I found somewhere, but now can't remember where. But it's around.
Once all those elements were in place, it worked perfectly. Got a completely stock phone, just like the day I bought it. Immediately installed 3 software updates and am now on Lollipop.
I'm still not sure which parts of this puzzle mattered and which didn't, but I *think* the key was installing those specific drivers (and not the many other versions of the same that I came across while researching), and THEN connecting the phone in MTP mode (ethernet) -- because that's when I finally had the correct drivers appear in Device Manager. Once I got there, the LG Flash Tool worked the first time.
Right. I hope this helps someone. I lost two weeks of my life to this (and a perfectly good CentOS box).
Last thing: download mode for me doesn't work quite the way anyone describes it. I have to turn it off, hold the UP volume button, plug it in, then let go of the UP button briefly and then hold it down AGAIN. No one mentions that last part.
Hello I bought an Nvidia Shield LTE and had Bliss Rom in it, I restored to the original (factory image) and everything seemed to go ok. after reboot I set the wifi and said that there was an update, it rebooted but after flashing the android bot with the progress bar everything went black. I have not been able to power it on or get into recovery mode, if I plug it to the pc it make a different plug in sound. but I have not been able to figure it out, please help.
Hi,
did you buy a "pyrotab" (a recalled tablet because of a Y01 battery) knowing what it was? Did the seller mentioned this?
Yours had Blissrom on it, the tablet could not download and execute the TegraOTA.zip executable that kills the tablet as soon as the replacement is activated. But since you restored the tablet using the official Nvidia Shield rom and did not flash the nomoreota zip file in TRWP *BEFORE* rebooting, the tablet downloaded the ST - YY kill update and your tablet is now a paper weight. And no there's no way to restore it, search the forums for confirmation.
I know this because I bought myself a pyrotab knowing what it was and read many times the instructions on how to prevent it to be killed. It had a crappy rom on it so I flashed the official one but made sure to run the nomoreota.zip and supersu in TRWP before rebooting to make sure it did not have the dreaded files and my tablet is still working perfect so far. (Gotta check that battery though!!)
Sorry for your loss!
When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet