I followed the steps from this thread:
http://forum.xda-developers.com/showthread.php?t=1952038
I successfully unlocked my phone and installed TWRP recovery, but that's as far as I can get. I tried to flash the latest CM10 nightly but hit an error when I run the zip, saying that the MD5 file is not found. I also tried to separately flash the boot.img from the CM10 zip, but it didn't help.
I've cleared my cache and factory wiped (through recovery), but I'm still stuck in the boot loop and can't get to the OS. Please help!!
I think the problem might be that I never actually rooted the phone, despite having unlocked it. Is there a way to root my phone via recovery, since I can't actually boot into it?
I tried to install RebelMod, but i hit an error saying "Unable to mount /data" -- I'm assuming that's because it's unrooted?
you want to root a stock ROM?
flash superuser downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
update: i managed to flash RebelMod successfully (according to TWRC) by running the zip file, but I'm still stuck in the boot loop even after doing a Factory Reset thru TWRC.
am I missing something?
wait a sec -- I got it working after I flashed the boot.img with fastboot.
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
Phone (xt1033) is rooted (status code 3). I had installed some custom rom, but later went back to stock with lolipop.
I now want to install CM12.1
I flashed the latest twrp using adb (twrp-2.8.6.0-xt1032). However, if I try to access recovery from the bootloader, phone just gives me a black screen.
So, I flashed a slightly older twrp. Again, same result.
Phone is booting up, but none of the options given with the bootloader seem to be working, and I have no recovery, custom or otherwise. What should I do?
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.
PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
I would also suggest starting over with the RUU for your model. Once you get TWRP back however you may want to take a look at this thread http://forum.xda-developers.com/one-a9/development/rom-a9-base-roms-recovery-flashable-t3282335 for some pre-rooted stock ROMS. I'm running the Sprint one with Xposed/GravityBox right now and it's great.
CSnowRules said:
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.
Click to expand...
Click to collapse
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it
Did you try re-installing drivers and flashing new recovery with fastboot?
PHYN1X said:
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it
Click to expand...
Click to collapse
I believe SuperSU 2.46 was your problem and that a RUU is not required to fix this. The older SuperSU broke the dm-verity for your system partition, which is enforced by your kernel. Flash SuperSU 2.76 (the latest stable release). This will automatically patch your boot partition. You will not be able to take an OTA until flashing the stock system image, though.
You just need to fastboot flash TWRP back to your device, first (fastboot flash recovery twrp.img) just like the first time from download mode--not the bootloader. Unlike ADB, your phone doesn't need to trust your computer.
If fastboot doesn't work, check what creusset said.
creusset said:
Did you try re-installing drivers and flashing new recovery with fastboot?
Click to expand...
Click to collapse
Yesterday i tried to root my phone, but i still fail booting twrp. At starting the recovery mode, the update system progress suddenly stops and i get the following errors
Whatever sm-j330fn version of twrp i could find, all gave me the same error... Unlocked oem lock and used heimdall on linux to flash twrp on phone with success..
Anyone any idea's?