I'm s-on so I use flash image gui to update. I screwed up Friday, while flashing the kernel from the new update a menu popped up after I had selected the kernel and I hit the back button. Instead of re-selecting the kernel, I flashed anyway.. So after, I reboot into recovery to install the update. At the end of the install twrp prompts unable to mount system or cache. Long story short, I end up rebooting into system. The new build number shows up with last installs kernel. I retry the process and now at the end of the install twrp reboots system instead of giving me the option to wipe or whatever. Everything works great, it's just twrp rebooting on its own that had me concerned. The only thing I did differently was not wipe dalvic or cache, due to flash image doing so when flashing kernel. The other times before the screw up, fi-gui wiped and I also wiped in recovery, before and after. I know the cm updater installs and reboots, is the dirty install performing that action like cm updater or is something wrong? I re-flashes twrp 2.6.3.3 and it's still the same.
Sent from my Amazon Kindle Fire HD using Tapatalk
probably the dirty install i would wipe dalvik an cache and reflash cm10.2 and kernel
Related
Followed instructions to flash KlassicRom and am now bootlooping.
Installed Steve's Kernel and booted into CWM where I made a backup.
Then back to odin to install KlassicRom R5 - no errors but on reboot just bootlooped.
After waiting 15 minutes with bootlooping, I booted into CWM to restore. Restore indicated success but on reboot, now just get Samsung boot screen with Steve's android guy in the corner. Stuck on boot.
I can still reboot into CWM and Odin recognizes the player when in download mode, so I'm hoping it's recoverable.
Anyone available to guide?
Thanks in advance for any help!
DCoy
Boot into CWM and
wipe cache
Factory Reset
go to advance and Wipe Dalvick Cache
then exit CWM and reboot.
Tried the wipes before. Did so again.
No errors reported with Wipe Cache
No errors reported with Factory Reset
Wipe Dalvik Cache reports:
Dalvik Cache wiped.
E:unknown volume for path [/sd-ext]
Reboot hangs at Steve's Android guy and Samsung again.
R5 don't work with steve's kernel. It only works with klin kernel or terrasilent.
Sent from my YP-G1 using xda premium
zaclimon said:
R5 don't work with steve's kernel. It only works with klin kernel or terrasilent.
Sent from my YP-G1 using xda premium
Click to expand...
Click to collapse
Downloaded and Odin Flashed R3
Odin reported PASS
on reboot, bootlooping again.
Booted into CWM and Wiped Cache, Factory Reset, and Wiped Dalvik, then reboot.
Bootlooping still.
Same error messages as before when boot hung:
No errors reported with Wipe Cache
No errors reported with Factory Reset
Wipe Dalvik Cache reports:
Dalvik Cache wiped.
E:unknown volume for path [/sd-ext]
Then bootlooping.
US or international, if US there is a stock but rooted ROM on here somewhere (not the full restore using heimdall), i'll look for it later that you can use to flash back with odin then boot into STOCK recovery and wipe data and factory reset that is what got me out of the bootloops when I first started flashing.
here is the link if your running the US model http://forum.xda-developers.com/showthread.php?t=1512331&highlight=stock+rooted+4+0
Downloaded the stock rom. Odin flashed. Booted into stock recovery and did factory reset/wipe.
Rebooted to joy. Thanks!
Might wait a bit before trying to flash the custom rom again.
DavidCoy said:
Downloaded the stock rom. Odin flashed. Booted into stock recovery and did factory reset/wipe.
Rebooted to joy. Thanks!
Might wait a bit before trying to flash the custom rom again.
Click to expand...
Click to collapse
Flash the terrasilent kernel and use that version of CWM to make a backup, its a much newer version and backs up things the older misses, also don't have the USB cable connected to the player when your in CWM thats what seamed to throw me into the bootloop, As long as you stick to Klins ROMs only (not using any of those CM7's or anything based off CM7) what you just experienced and solved with the "stock" ROM flash is the worst case scenario when flashing only variations of Klin's ROM with Odin.
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help
So I'm tying to help my best friend flash CM11 on his e970, it's rooted and had TWRP 2.7.0.1 installed. I did a full backup and attempted to wipe data, system, cache, and dalvik. It would start then flash off and then back to TWRP again. Doing this one at a time showed that the error happened when attempting to wipe data. I tried the latest Phil's CWM and backed up wiped fine but when I attempted to install CM11 either M6 or the 052114 Nightly it gives a status 7 error. So I tried it with the latest CWM touch recovery and the same thing. Backups restore each time. I then attempted to flash Mokee thinking it must be an.issue with the downloads, and still status 7. Any ideas? Thanks, every time I google the error I read it's a recovery issue, now I'm not too sure it is in this case. 3 different recoveries and 3 different ROMs. I did keep the phone on ice to keep it cool when it was getting hit to be safe.
Thanks
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.
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?