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.
Related
this isn't first time that i wipe all os system but this time i can't flash any rom (i use twrp). the difference now is that when i can wipe dalvik cache always said: failed; i try with difference rom (after installing the boot image correctly in fastboot mode), i try install rom in adb sideload but nothing.
help me
Naijian said:
this isn't first time that i wipe all os system but this time i can't flash any rom (i use twrp). the difference now is that when i can wipe dalvik cache always said: failed; i try with difference rom (after installing the boot image correctly in fastboot mode), i try install rom in adb sideload but nothing.
help me
Click to expand...
Click to collapse
You have the wrong recovery for your hboot, follow this:
http://forum.xda-developers.com/showthread.php?t=2502327
GtrCraft said:
You have the wrong recovery for your hboot, follow this:
http://forum.xda-developers.com/showthread.php?t=2502327
Click to expand...
Click to collapse
i have hboot- 1.25.0002 and use twrp v2.6.3.0 (but i try also v2.5.0.0). this recovery and the rom i used before wipe (mySensedx) works fine but now whit this new os wipe there is a problem that i can't resolve. the only difference that i understand is the failed of dalvik cache.
Naijian said:
i have hboot- 1.25.0002 and use twrp v2.6.3.0 (but i try also v2.5.0.0). this recovery and the rom i used before wipe (mySensedx) works fine but now whit this new os wipe there is a problem that i can't resolve. the only difference that i understand is the failed of dalvik cache.
Click to expand...
Click to collapse
Try another recovery for JB or reflash the current one. Flashing works btw?
i don't know how but i resolve it, maybe the problem was the boot image of the twrp recovery. nevermind :good:
Naijian said:
i don't know how but i resolve it, maybe the problem was the boot image of the twrp recovery. nevermind :good:
Click to expand...
Click to collapse
Maybe you had another kernel installed? Or you flashed the recovery / kernel to wrong partition?
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.
i flash custom rom i my friend's device then i get the boot loop.
I thought stock rom will solve the problem so i used to odin to flash the stock rom.
Stock rom was flashed successfully but again when it booted up then at optimizing app screen it reboots.
Plz help
It does not reboot to recovery. Mobile is simply restarting and boot loop occurs at "optimizing apps".
Click to expand...
Click to collapse
Device is currently at stock rom flashed via odin
Click to expand...
Click to collapse
Try to reflash CWM and then wipe cache and dalvik cache to see if it boots. If it doesn't boot, try to flash another custom rom to see if it boots
freitaz said:
Try to reflash CWM and then wipe cache and dalvik cache to see if it boots. If it doesn't boot, try to flash another custom rom to see if it boots
Click to expand...
Click to collapse
ok going to try this and will tell you if it works or not
And if you or someone else got more methods please post because after flashing stock via odin whole partition was seem to erased and flashed(am i right)
i have got pit file from
http://forum.xda-developers.com/showthread.php?t=2482980
Click to expand...
Click to collapse
will this repair the device.
how does this PIT works.
Does it erase all the partition then create it again and then flash the rom.
is this method is used by the service center
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.
So, this is kinda weird and I don't know what's wrong...
I unlocked the bootloader by enabling the orm stuff in the developer settings and flashing a fastboot rom. Then I unlocked the bootloader and installed TWRP. After that I tried some roms (miui, cyanogenmods), but now I want to use the normal global developer version again. So what I did was reinstalling this rom which worked fine. Then I went back into TWRP to install SuperSU, but then I was unable to boot... Any ideas on how to fix this, or how to avoid the boot processing becoming stuck?
Thanks!
try clearing cache and devik cache if that dosent work try flashing this zip http://forum.xda-developers.com/attachment.php?attachmentid=3740290&d=1462390986
leave a THANK if it helped
filthyrich77 said:
try clearing cache and devik cache if that dosent work try flashing this zip http://forum.xda-developers.com/attachment.php?attachmentid=3740290&d=1462390986
leave a THANK if it helped
Click to expand...
Click to collapse
I had to use the boot.img in order to get it working. Thanks!
autCyrius said:
I had to use the boot.img in order to get it working. Thanks!
Click to expand...
Click to collapse
Used alla twrp, it was the simple way to flash official rom: http://en.miui.com/thread-282773-1-1.html?mobile=2
Sent from my Redmi Note 3 using Tapatalk
filthyrich77 said:
try clearing cache and devik cache if that dosent work try flashing this zip http://forum.xda-developers.com/attachment.php?attachmentid=3740290&d=1462390986
leave a THANK if it helped
Click to expand...
Click to collapse
I am also stuck in the same problem with my Redmi 4A. I unlocked the bootloader, installed cofface recovery then installed supersu 2.46 and my phone is stuck on mi logo. I have got this zip file but don't know how to flash it since I cannot start my phone normally so how would I put this zip file in my phone?