[Q] Phone Stuck in Boot Loop - HTC Rezound

Hello All,
After replacing my shattered screen, I left my sd card in while pulling the red case out and damaged the sd card housing. With a little more troubleshooting, the sd card slot fell out and disintegrated. I filled in the contacts with solder, however ever since (before and after) it gets stuck in a boot loop. I am able to connect to it through adb and push roms, even update them, but on reboot they dont work.
I followed the steps to a T. http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing_2
I have amon RA recovery, wiped all data/factory reset, wiped cache and dalvik cache. Flashed rom. Cleared cache and dalvik again. rebooted, nothing.
I am attaching a logfile. It is big, but I didn't know where it started and where it ended.
http://pastebin.ca/2488280
Any help is appreciated.

thefonzz2625 said:
Hello All,
After replacing my shattered screen, I left my sd card in while pulling the red case out and damaged the sd card housing. With a little more troubleshooting, the sd card slot fell out and disintegrated. I filled in the contacts with solder, however ever since (before and after) it gets stuck in a boot loop. I am able to connect to it through adb and push roms, even update them, but on reboot they dont work.
I followed the steps to a T. http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing_2
I have amon RA recovery, wiped all data/factory reset, wiped cache and dalvik cache. Flashed rom. Cleared cache and dalvik again. rebooted, nothing.
I am attaching a logfile. It is big, but I didn't know where it started and where it ended.
http://pastebin.ca/2488280
Any help is appreciated.
Click to expand...
Click to collapse
if s-on are you flashing the boot.img from that rom in fastboot?

REV3NT3CH said:
if s-on are you flashing the boot.img from that rom in fastboot?
Click to expand...
Click to collapse
You're right, I am s-on. So i did that, but I am hitting the same problem.
Namely:
"cutils-trace: Error opening trace file: No such file or directory
"JNI posting fatal error: Native registration unable to find class 'android/media/videoeditor/VideoEditorProfile', aborting
Followed this: androidforums.com/gsm-evo-3d-all-things-root/723480-how-install-custom-rom-s.html

thefonzz2625 said:
You're right, I am s-on. So i did that, but I am hitting the same problem.
Namely:
"cutils-trace: Error opening trace file: No such file or directory
"JNI posting fatal error: Native registration unable to find class 'android/media/videoeditor/VideoEditorProfile', aborting
Followed this: androidforums.com/gsm-evo-3d-all-things-root/723480-how-install-custom-rom-s.html
Click to expand...
Click to collapse
you do realize thats for the evo 3d and not for the rezound right....2 different devices and setups
what rom are you trying to flash and ill step by step you with what you need to do

REV3NT3CH said:
you do realize thats for the evo 3d and not for the rezound right....2 different devices and setups
what rom are you trying to flash and ill step by step you with what you need to do
Click to expand...
Click to collapse
I'm trying to flash Pac-Man http://forum.xda-developers.com/showthread.php?t=2425473 . I did a wipe data/cache on amon ra, wipe system, wipe dalvik. Adb push the pacman zip, push the gapps zip, push the boot.img zip. I flashed them to internal_sd.( Other times, when I flashed them to /data/ and then used recovery --upgrade_package=DATA:file_name.zip It would either say the install completed or hang and in either instance not work.) After flashing to internal_sd, i used the flash_zip functionality from amon_ra which lets you pick from internal_sd. I flashed pacman, it said it was successful, gapps successful. I rebooted the bootloader as directed into fastboot, i issued the fastboot boot /path/to/boot.img and it gave an OK. I rebooted back into recovery, cleared dalvik, cleared cache and rebooted. Thats what I got above.
Let me know if I should do something different. Thank you for the help.

thefonzz2625 said:
I'm trying to flash Pac-Man http://forum.xda-developers.com/showthread.php?t=2425473 . I did a wipe data/cache on amon ra, wipe system, wipe dalvik. Adb push the pacman zip, push the gapps zip, push the boot.img zip. I flashed them to internal_sd.( Other times, when I flashed them to /data/ and then used recovery --upgrade_package=DATA:file_name.zip It would either say the install completed or hang and in either instance not work.) After flashing to internal_sd, i used the flash_zip functionality from amon_ra which lets you pick from internal_sd. I flashed pacman, it said it was successful, gapps successful. I rebooted the bootloader as directed into fastboot, i issued the fastboot boot /path/to/boot.img and it gave an OK. I rebooted back into recovery, cleared dalvik, cleared cache and rebooted. Thats what I got above.
Let me know if I should do something different. Thank you for the help.
Click to expand...
Click to collapse
Bump?

Flashed phone to cm 10.2. Problem Solved.

thefonzz2625 said:
I'm trying to flash Pac-Man http://forum.xda-developers.com/showthread.php?t=2425473 . I did a wipe data/cache on amon ra, wipe system, wipe dalvik. Adb push the pacman zip, push the gapps zip, push the boot.img zip. I flashed them to internal_sd.( Other times, when I flashed them to /data/ and then used recovery --upgrade_package=DATA:file_name.zip It would either say the install completed or hang and in either instance not work.) After flashing to internal_sd, i used the flash_zip functionality from amon_ra which lets you pick from internal_sd. I flashed pacman, it said it was successful, gapps successful. I rebooted the bootloader as directed into fastboot, i issued the fastboot boot /path/to/boot.img and it gave an OK. I rebooted back into recovery, cleared dalvik, cleared cache and rebooted. Thats what I got above.
Let me know if I should do something different. Thank you for the help.
Click to expand...
Click to collapse
use twrp or cwm.... amon ra is not recommended as it will give many bugs with flashing any rom higher than ice cream sandwhich....such as many random reboots...overheating...bad signal...etc....i suggest not doing adb method....only flash rom and gapps in recovery then reboot to botloader and select fastboot and plug it in so it says fastboot usb... in your fastboot folder on pc place the boot.img in it....open commabd prompt and cd to that folder and type: fastboot flash boot boot.img
again amonra will not work on ny jb or kit kat roms....a good thorough reading from the users and comments will ensure this....adb only works in certain recoveries or in rom with android debugging enabled...

Related

Think I may have bricked my prime?

I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
geon106 said:
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
Click to expand...
Click to collapse
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
McJesus15 said:
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
Click to expand...
Click to collapse
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
geon106 said:
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
Click to expand...
Click to collapse
IT LIVES!!!
Don't know how I did it, but I managed to get TWRP installed on it. Using Fastboot somehow or ADB. It booted into TWRP and mounted external SD card, then flashed an official JB ROM(the Prime was on ICS before) and it has now booted up fine
I will now try and re-flash a custom ROM again(a different one) using TWRP but it is all looking superb
I was worried i'd have to claim on the extended insurance I took out with the retailer

[Q] Flashed Boot.img without rom/gapps, stuck in bootloop, can't access adb

I was trying to flash CM and made the stupid mistake of only flashing the boot.img and now my dna repeatedly restarts and won't get past the droid light thing. The rom files and gapps are not on my sd card. I can't get a connection to adb and my computer doesn't see the device. ADB will recognize the device at one part during the bootloop but says "offline" right next to it. I'm s-off (moonshine), rooted, and have CWM recovery. I've tried wiping the cache, dalvik cache, and tried a factory reset. None of those worked. If I lose this phone I'm really screwed, is there no way to get out of this?
mistahthron said:
I was trying to flash CM and made the stupid mistake of only flashing the boot.img and now my dna repeatedly restarts and won't get past the droid light thing. The rom files and gapps are not on my sd card. I can't get a connection to adb and my computer doesn't see the device. ADB will recognize the device at one part during the bootloop but says "offline" right next to it. I'm s-off (moonshine), rooted, and have CWM recovery. I've tried wiping the cache, dalvik cache, and tried a factory reset. None of those worked. If I lose this phone I'm really screwed, is there no way to get out of this?
Click to expand...
Click to collapse
Boot in CM recovery and there is an option to connect the phone to the computer as a USB. There you can put the rom files etc and flash it again.
abhi897 said:
Boot in CM recovery and there is an option to connect the phone to the computer as a USB. There you can put the rom files etc and flash it again.
Click to expand...
Click to collapse
I ended up fixing the problem by finding out what sideloading is and sideloading the rom/gapps. Thanks for the help though!

[Q] Boot Loot -- Help!

Here's my situation--I had been running MeanBean for a while and decided to try Kush's KK build (http://forum.xda-developers.com/showthread.php?t=2518211&highlight=loop). I flashed the recovery he linked to, then installed the rom and gapps he linked to. TWRP said everything went successfully. But, when I reboot, the phone just hung at the HTC splash screen. I tried flashing again, downloading fresh and flashing again, wiping the cache, etc. Nothing worked.
So, I decided to go back to my last nandroid of MeanBean. But, after TWRP "successfully" recovered to the latest nandroid, I got stuck in a boot loop. The phone gets through the first part of the boot animation, then freezes and reboots. I tried installing a fresh version of MeanBean, flashing back to TWRP 2.6.3, but nothing has eliminated the boot loop.
I'm s-off and I've never gotten stuck like this before. Anyone have any thoughts?
Reboot to the bootloader and run the command "fastboot erase cache" from a command prompt, then try a fresh install. Are you sure you're S-off?
Sent from my HTC EVO 4G LTE
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
tbhtjd said:
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot image from the rom? You shouldn't need to if you're s-off but couldn't hurt if you're still getting boot loops.
Sent from my EVO LTE
Thanks, Fin. I tried fastboot flashing to boot.img separately (which shouldn't be necessary with s-off) after a fresh install, and I'm still in the boot loop. Any other ideas?
Go to recovery, do a full system wipe (data, system, Dalvik & cache) and re-flash the ROM after a fresh download. Really, though, you shouldn't have to wipe cache, since it's under /data.
Sent from my HTC EVO 4G LTE
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
tbhtjd said:
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
Click to expand...
Click to collapse
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
FinZ28 said:
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Trying to flash MeanBean, which is what I've been using previously. I flashed the regular 2.6.3 Jewel TWRP.
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
fredgar75 said:
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
Click to expand...
Click to collapse
Hmm, don't think that's it. I've been able to mount internal storage and wipe the cache, etc. just fine.
I'm at a loss at this point as to what the problem might be. If you shoot me a PM I have one last option for you.
Sent from my HTC EVO 4G LTE

[Q] Upgrading on reboot converted M8

Ok so I have a HTC One M8 from At&T unlocked. I had a friend(I bought it from him as a GPE) convert my phone to the GPE. Now it has been great, but now for some reason on every reboot it has to "optimize" about 40 apps(Only on ART). So to avoid using the RUU again we have tried to just uninstall some apps and take away root permissions to see if that would fix the issue, but it didn't. So then we tried to flash the GPE ROM, but first we had to flash TWPR because stock did not support flashing ROMs. I was able to flash the img successfully, but it will not boot into the recovery mode. What can I do at this point?
TL;DR - I now have a phone that takes about 5 minutes to boot and has no recovery.
axiosjackson said:
Ok so I have a HTC One M8 from At&T unlocked. I had a friend(I bought it from him as a GPE) convert my phone to the GPE. Now it has been great, but now for some reason on every reboot it has to "optimize" about 40 apps(Only on ART). So to avoid using the RUU again we have tried to just uninstall some apps and take away root permissions to see if that would fix the issue, but it didn't. So then we tried to flash the GPE ROM, but first we had to flash TWPR because stock did not support flashing ROMs. I was able to flash the img successfully, but it will not boot into the recovery mode. What can I do at this point?
TL;DR - I now have a phone that takes about 5 minutes to boot and has no recovery.
Click to expand...
Click to collapse
To be clear, you can get into bootloader, but if you pick recovery, it just reboots? Or adb reboot just reboots phone?
Try to fastboot erase cache, and use fastboot to flash TWRP again. It looks like you just have a faulty TWRP install (and wiping cache often fixes this). Make sure its the latest TWRP. If it still doesn't work, try Philz recovery.
ART cache rebuilding itself (partially?) is an odd issue. I've seen someone mention it before, but can't say I know what this one is. This will usually only occur on first boot after flashing a ROM, switching between Dalvik/ART, or wiping Dalvik. Not certain how wiping Dalvik cache relates to ART (does it wipe a corresponding ART cache?). But you might try to wipe Dalvik and see if this helps.
Sorry
redpoint73 said:
To be clear, you can get into bootloader, but if you pick recovery, it just reboots? Or adb reboot just reboots phone?
Try to fastboot erase cache, and use fastboot to flash TWRP again. It looks like you just have a faulty TWRP install (and wiping cache often fixes this). Make sure its the latest TWRP. If it still doesn't work, try Philz recovery.
ART cache rebuilding itself (partially?) is an odd issue. I've seen someone mention it before, but can't say I know what this one is. This will usually only occur on first boot after flashing a ROM, switching between Dalvik/ART, or wiping Dalvik. Not certain how wiping Dalvik cache relates to ART (does it wipe a corresponding ART cache?). But you might try to wipe Dalvik and see if this helps.
Click to expand...
Click to collapse
Kinda forgot about this thread. I was able to just use the RUU again and it fixed it. Thanks though.

[Help] Flashing PAC Rom

I don't understand what is it that I might be doing wrong, I root the tablet, have bootloader unlocked, and install Dualrecovery. From TWRP recovery I wipe Dalvik cache, Cache, System, and Data. Install PAC Rom Castor and GApps using TWRP, all seems to go well, no errors present themselves. Then I reflash "TabZ2-lockeddualrecovery2.8.21-RELEASE.flashable" to keep the recovery intact before I attempt to boot into system per their instructions after installing a custom ROM. I wiped Dalvik and Cache before I reboot and once it goes away from recovery nothing occurs just my tablet remaining in flash boot which is a good thing so I can start all over again since obviously something went wrong and just use flashtools to get back to an old stock firmware. I have a SGP512. Any help is appreciated, thanks.
Edit: Even tried it w/o wiping system and same results just doesn't boot.
D03035790 said:
I don't understand what is it that I might be doing wrong, I root the tablet, have bootloader unlocked, and install Dualrecovery. From TWRP recovery I wipe Dalvik cache, Cache, System, and Data. Install PAC Rom Castor and GApps using TWRP, all seems to go well, no errors present themselves. Then I reflash "TabZ2-lockeddualrecovery2.8.21-RELEASE.flashable" to keep the recovery intact before I attempt to boot into system per their instructions after installing a custom ROM. I wiped Dalvik and Cache before I reboot and once it goes away from recovery nothing occurs just my tablet remaining in flash boot which is a good thing so I can start all over again since obviously something went wrong and just use flashtools to get back to an old stock firmware. I have a SGP512. Any help is appreciated, thanks.
Edit: Even tried it w/o wiping system and same results just doesn't boot.
Click to expand...
Click to collapse
Your device will never Boot if you flash pac with nuts recovery. It causes to much Problems with cm based roms. So to rescue your tab you need Boot into fastboot and write "fastboot erase recovery" then flash this kernel http://doomlord.xperia-files.com/do...2U3RrS2VybmVsX1dJRkktdjAzXzE3LjEuMS5BLjAuNDAy
Do not reboot to system. Power of the device and then Boot into recovery (when you see the Sony logo and the LED light turns pink/amber/orange keep tapping/pressing VOLUME UP key). Then you will See cwm recovery. There first do a factory reset and Format system. Format system is in mounts and storage options) now flash PAC Rom and gapps and reboot to system now the device should Boot correctly. After the first boot do all settings then go to developer options and you will find expand reboot menu or something Luke this. Tick it and than hold the power button for some second tap reboot than bootloader (before connect the device with your PC) than use fastboot to flash the New recovery. Use one of these http://forum.xda-developers.com/xpe...wrp-cwm-philz-recovery-collection-z2-t3052676
For instructions to flash recovery look in the thread there are a step "Installation" if you need more help write me
rcstar6696 said:
Your device will never Boot if you flash pac with nuts recovery. It causes to much Problems with cm based roms. So to rescue your tab you need Boot into fastboot and write "fastboot erase recovery" then flash this kernel http://doomlord.xperia-files.com/do...2U3RrS2VybmVsX1dJRkktdjAzXzE3LjEuMS5BLjAuNDAy
Do not reboot to system. Power of the device and then Boot into recovery (when you see the Sony logo and the LED light turns pink/amber/orange keep tapping/pressing VOLUME UP key). Then you will See cwm recovery. There first do a factory reset and Format system. Format system is in mounts and storage options) now flash PAC Rom and gapps and reboot to system now the device should Boot correctly. After the first boot do all settings then go to developer options and you will find expand reboot menu or something Luke this. Tick it and than hold the power button for some second tap reboot than bootloader (before connect the device with your PC) than use fastboot to flash the New recovery. Use one of these http://forum.xda-developers.com/xpe...wrp-cwm-philz-recovery-collection-z2-t3052676
For instructions to flash recovery look in the thread there are a step "Installation" if you need more help write me
Click to expand...
Click to collapse
Thanks! I used Flashtools to flash over the recovery via fastboot and accessed the recovery to do the rest. I had no idea CM based ROMS don't work well that recovery or any other I haven't tried yet. Any suggestion on what recovery to use? So far CWM got me this far not sure if I should try others. Philz Touch seems to be more appealing and the same as CWM.
D03035790 said:
Thanks! I used Flashtools to flash over the recovery via fastboot and accessed the recovery to do the rest. I had no idea CM based ROMS don't work well that recovery or any other I haven't tried yet. Any suggestion on what recovery to use? So far CWM got me this far not sure if I should try others. Philz Touch seems to be more appealing and the same as CWM.
Click to expand...
Click to collapse
Use this one https://mega.nz/#!rI4y2bJS!VksDLNy_a8cy8x-VBviYRkTP2SdSBm7Rs9G445vUXCU
This is twrp but it works with cmbased roms.

Categories

Resources