I just got this from a friend, it's the original that he never sent back for replacement. I planned to replace the battery myself and use it. I installed Resurrection Rom and somehow the file system got corrupted. No idea how it happened as the tablet already had TWRP and all I did was transfer over the rom files/gapps, recovery wipe, installed and restarted. Bootloader is unlocked.
How can I remedy this without running the risk of getting my bootloader brick from the kill switch?
EDIT:
Could it be that I went from LP to MM?
I got this fixed. I found this nv-recovery-image-shield-tablet-wifi-update3_1_1.zip in another thread, ran that and restored the tablet, stayed in fastboot and pushed the latest TWRP, booted into TWRP, and flashed Blisspop. I'm back up and running.
Related
I have an AT&T HTC One X that's rooted. I wanted to put Cyanogenmod 10 on it, but I accidently wiped the System files instead of the cache. Now it can't boot up regularly, I've tried using Rom Update Utility but it doesn't seem to work. Factory Reset doesn't seem to work either. I didn't expect this to happen because my friend just flashed his a couple of days ago. I've tried making a backup and restoring but no matter what I can't get the phone to start up normally. Unless I put it in TWRP (Team Win Recovery Project) or the HBoot/Bootloader I really can't use it for anything. Any suggestions? I would greatly appreciate it. Also when bootloader opens it says "Tampered" and under it "Unlocked" because I did root it. It didn't have "Tampered" when I first rooted it.
I don't care about Cyanogenmod 10 anymore I just want to have it working again.
Everything else about the phone is in perfect condition but what I just said is the only problem.
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
iElvis said:
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
Click to expand...
Click to collapse
Well, I've already flashed it to a few things and so far it hasn't changed anything. Got any links?
Did you fastboot flash boot boot.IMG ? Don't know what hboot you are on, but could be it.
Sent from my Carbon-ize Evita using xda-developers app
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
ilinimud said:
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
Click to expand...
Click to collapse
You have to ensure the ROM you are using is built for the KK kernel. Not all ROMs work with the KK kernel.
Here is a list of ROMs that work with KK:
http://www.droidrzr.com/index.php/topic/48909-kitkat-roms-list/
Anything else will result in what you are experiencing - bootloops.
Hi,
I'm getting killed with this device. I have a VZW XT926 Stock from reverting back to VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml this twice tonight:
I'll begin with how I started, I unlocked the SIM and threw a T-Mobile in there. No problems, so I rooted with Towelunlock, installed SuperSU and updated the Binary. Then I installed TWRP2710-RAZR-HD_M-KITKAT through Fastboot. I could get into TWRP and all was right with the world. Then I tried to install cm-11-20140708-SNAPSHOT-M8-moto_msm8960 and I'd get stuck at the Moto dual core logo. No progressing. So I thought maybe the Factory reset wipe wasn't enough in TWRP so back to recovery and wipe everything, and flash again and reboot and same result. So now I can only boot to recovery I didn't backup my current rom, cause, ya know I'm a stoopid, and I have to factory reset to 4.4.2, and re root, and re unlock sim. Frustrated right now to the point of entertaining the idea of using this Verizon bloat rom rooted and not going for CM11.
I'm sure I'm too tired to keep this up tonight, and I'll probably really brick my phone if I keep at it without any sleep. My question for you is:
What am I doing wrong, what simple instruction am I missing when reading that is screwing me up? Because I'm too dumb/tired/whatever to figure it out without your help.
The snapshot is for the old kernel. Download the newest nightly. I ran into the same issue not knowing. Its that easy!
You need to start over jethro....back to HoM And this time make a backup of Stock before flashing a custom rom
j37hr0 said:
Hi,
I'm getting killed with this device. I have a VZW XT926 Stock from reverting back to VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml this twice tonight:
I'll begin with how I started, I unlocked the SIM and threw a T-Mobile in there. No problems, so I rooted with Towelunlock, installed SuperSU and updated the Binary. Then I installed TWRP2710-RAZR-HD_M-KITKAT through Fastboot. I could get into TWRP and all was right with the world. Then I tried to install cm-11-20140708-SNAPSHOT-M8-moto_msm8960 and I'd get stuck at the Moto dual core logo. No progressing. So I thought maybe the Factory reset wipe wasn't enough in TWRP so back to recovery and wipe everything, and flash again and reboot and same result. So now I can only boot to recovery I didn't backup my current rom, cause, ya know I'm a stoopid, and I have to factory reset to 4.4.2, and re root, and re unlock sim. Frustrated right now to the point of entertaining the idea of using this Verizon bloat rom rooted and not going for CM11.
I'm sure I'm too tired to keep this up tonight, and I'll probably really brick my phone if I keep at it without any sleep. My question for you is:
What am I doing wrong, what simple instruction am I missing when reading that is screwing me up? Because I'm too dumb/tired/whatever to figure it out without your help.
Click to expand...
Click to collapse
ESCollins90 said:
The snapshot is for the old kernel. Download the newest nightly. I ran into the same issue not knowing. Its that easy!
Click to expand...
Click to collapse
Yup, this worked. Now to delete that backup
Sent from my Amazon Jem using XDA Free mobile app
I recently dropped and broke my N5 so I got a newer one. It came with KK, so I rooted it and it's great. I decided to download LL over the OTA, so I did and it downloaded. After then downloading it then asked if I wanted to install and restart, so I said yes. It then rebooted into TWRP. At that point I had no idea what to do or whether the phone was even supposed to do that. Not knowing what to do I simply rebooted the phone. But when it rebooted it was still in KK and of course it was still rooted. Of course LL is nowhere to be found. Anyone have an idea what went wrong, because I don't? Why did the download take me to TWRP? And what do I have to do if I again decide to install LL? Thanks.
You have to be 100% stock for the OTA to install, meaning TWRP has to go. You gotta flash the stock recovery and undo any changes you might have made to /system.
its a first gen US boost mobile moto g xt1031. it is boot-loader unlocked and rooted. currently has twrp recovery and had cwm. i have never been able to flash any rom either from side-load or from internal or external sd. about a month ago i started having trouble restoring backups and now a few days ago it wont let me make a backup either. it gets stuck when it comes to restoring or backing up the data partition. beforehand i had no problems with backups. when i got the phone almost a year ago i didn't have any trouble boot-loader unlocking and rooting it. i am currently using lubuntu with the android sdk installed and my phone is recognized in adb and fastboot. i have been rooting and flashing android since my hd2 days and i never had this problem. i have tried several different boost moto g roms and none of them will boot. i just get boot loops. i have tried 4.4.2 4.4.4 and 5.0 roms. none will boot up. can anyone help me out with any ideas of whats wrong? debugging is on and again it is rooted boot-loader unlocked running twrp and recognized on my computer with adb and fastboot. thanks.
I am having the exact same issue. I first flashed BlissPop onto the device, and immediately ran into boot loops. I flashed a CM nightly for the 1031, same issue, and now even a stock rom does nothing but boot loops.
i have been trying to run cm since last july. im almost to the point that i dont even want this phone anymore. ive never had this problem with any other phone. i hope someone can help us. the only thing i can flash is recovery. but thats pretty much pointless since i can flash a rom or create or restore a backup. the old backup i have fails when it comes to date but it will boot. i just have to start from the beginning every time.
Yeah man, I've been through everything I typically do for rescues like this one, nothing has worked. Stock ROMs bootloop as well, which is just strange. I'm starting to think I killed the parition table on the phone itself.
davenull said:
I am having the exact same issue. I first flashed BlissPop onto the device, and immediately ran into boot loops. I flashed a CM nightly for the 1031, same issue, and now even a stock rom does nothing but boot loops.
Click to expand...
Click to collapse
good news that might help you. i had to reformat my whole system and change it to f2fs using twrp. installed cm 11 and it booted up just fine. im gonna try to install cm 12 now. finally after nearly a year... oh and no thanks to anyone else on this thread. (you not included in that).