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.
Related
I've recently flash Aura ROM, and it was successful. Now I want to try the Neutrino build. Do I have to flash back to my Stock Gingerbread 4.5.91.img and then flash Neutrino?
Or do I simply go ahead and flash Neutrino with these steps.
-boot to recovery
-wipe dalvik&wipe cache
-factor reset/data
-flash ROM in recovery
-wipe dalvik&wipe cache again
-reboot
Sadly I did not do a backup on CWM(Using Rom Racer's).
You don't uninstall a rom. You wipe and flash another.
Each rom's thread will give the wiping instructions that work best; I've only stuck with blur roms and have had luck with -- AFTER backing up -- booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Others recommend first wiping everything separately using fastboot (and someone will likely chime in here). If you want Neutrino, head over there and see what wipe procedures users have found the most success with.
sheeparecurious said:
You don't uninstall a rom. You wipe and flash another.
Each rom's thread will give the wiping instructions that work best; I've only stuck with blur roms and have had luck with -- AFTER backing up -- booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Others recommend first wiping everything separately using fastboot (and someone will likely chime in here). If you want Neutrino, head over there and see what wipe procedures users have found the most success with.
Click to expand...
Click to collapse
After all this time! I've always thought you'd have to go back to your stock ROM. Thanks a bunch sheeparecurious! Neurtion seems to want you to wipe everything.
Do I need to wipe dalvik and cache everytime I flash a simple mod or add on?
Depends on the rom. Does the OP in the Neutrino thread say anything specific?
I've been able to flash mods without clearing any caches. I've seen two themes "not play nicely" when flashing one after another, and others were fine to go from theme to theme.
"Wiping data may not be necessary with every update, but it's best to flash clean. However, if you regularly flash the updates, you'll most likely need to wipe data at some stage anyway."
It says to wipe when you flash updates. Does he mean updates to Neutrion updates?
Here's thread link. If you'd like to look for yourself. http://forum.xda-developers.com/showthread.php?t=1398819
Thanks in advanced. I'm headed to bed now. Very pleased as to how things went today on my phone.
Yeah, he probably means "updates to neutrino." I'd say if you successfully flashed the rom and any additional mods you wanted, and the phone is working well, make a nandroid backup so you have a good restore point.
Whenever it comes around, try the next update without wiping - either it'll work fine & life is great, or something will be screwy & you'll need to wipe clean and flash from a fresh state anyway (or restore your backup state).
Sent from my MB860 using XDA
sheeparecurious said:
booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Click to expand...
Click to collapse
fastboot -w does the same as wiping data and cache in recovery.
---------------------------------------------------------------------------
For the best results, when you want to flash a new ROM you should always perform a full wipe in fastboot per the following to make sure you will avoid any unforeseen complications:
reboot to recovery
wipe Dalvik
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
reboot
If you are updating an exisiting ROM, then you would normally just reboot to recovery, wipe Dalvik and cache, then flash the update unless the dev has instructed otherwise in the ROM's thread.
You should ALWAYS do a nandroid backup of your current ROM through recovery prior to wiping and flashing anything. Much easier to restore to a previous state than have to set-up completely from scratch again if something goes wrong.
See? Told ya someone would chime in.
and I knew "fastboot -w" did the same data/cache wipe as in CWM, something something placebo effect can never be too sure. Wouldn't feel right if I didn't do it anyway.
Now, I never erased the webtop when I started flashing roms -- I only did the 2.3.6 webtop fruitcake because it was an update compared to my original one. Granted, I stuck with blur roms but it didn't seem to cause any issues. I assume if I were to switch to a CM-based rom, it could cause glitches if I don't erase the webtop partition?
You guys are awesome thanks! I copied down the procedure you recommended CaelanT. This will help me a ton.
Sent from my MB860 using XDA
Thanks for that CaelanT thats also useful to know, I have only just entered the world of different roms.
I always do a CWM backup and then a factory reset, wipe the dalvik cache and then flash the new ROM and any add-ons or kernels. Don't forget to wipe your battery stats/calibrate your battery. (I turn off my phone, charge it to 100%, wait about 15 minutes to be sure and boot into recovery to wipe the battery stats)
Sent from my MB860 using XDA App
I posted this. This is a fix for Sense 3.6 ROMS for boot loops OR if you want to flash the ROM without custom Firmware messing stuff up.
http://forum.xda-developers.com/showthread.php?p=26386620#post26386620
Or ask your question in this thread and I will try to answer it!
I flashed my phone to mean Rom ics 1.2 and I keep experiencing reboot like every couple of hours or so. First time I flashed, I did a dirty flash. Then I did a superwipe and started over from scratch and the same thing is happening. What can I do?
Hmmm....
Well, what recovery are you using. IF you are using 4-EXT recovery, I can help. If not, I still am going to say what I'd do.
I SUGGEST FLASHING 4-EXT, JUST SAYING.
1. Wipe Boot, System, and Data partitions individually. (In 4-EXT its under wipe and press each individual button (Wipe Data button, Wipe Boot button etc...).)
2. Wipe dalvik cache.
3. Flash your rom. DO NOT REBOOT
4. Flash kernel (AnthraX zip file)
5. Reboot and it should work.
I am using 4-EXT recovery, and HBOOT 1.50 S-ON.
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...
I have an unusual problem, in that my Moto Z always boots to TWRP. The only way to boot the ROM is first to boot bootloader and reboot bootloader a few times and then select Start. Any idea why and if there is something I can do?
lollyjay said:
I have an unusual problem, in that my Moto Z always boots to TWRP. The only way to boot the ROM is first to boot bootloader and reboot bootloader a few times and then select Start. Any idea why and if there is something I can do?
Click to expand...
Click to collapse
Try clearing cache
Manish54 said:
Try clearing cache
Click to expand...
Click to collapse
Yes I cleared both dalvik and cache and did not solve the problem.
I'd maybe flash twrp again (optional if twrp seems fine) and then dirty flash your rom again. (without any wipes first.)
If that fails, maybe only wipe system, and flash rom again.
Backing up with twrp before doing anything.
Assuming it's a custom rom. If it's stock, then you need to use fastboot obviously. (or mfastboot if that's what we use, I haven't done anything to my Z yet.) :good:
I finally solved the problem and solved it by reflashing stock ROM using fastboot. Then I could flash twrp again and then the custom ROM.
So I'm trying to clean flash a ROM and I want to wipe Cache, Dalvik, System and Data, but TWRP reboots every time and doesn't finish the wipe. And nothing gets wiped.
I tried only a cache + dalvik, but nada. Instant reboot to my home screen.
Tried TWRP 3.0.2.1 and 3.1.0.0 both, same issue.
Ideas?
Solved it. Went back to the May update via fastboot & rerooted + TWRP (latest). Done and dusted.
Mods may close this thread.
Same problem here. Any solution aside from flashing factory image?