version: v8.5
wiped data/factory reset
wiped cache
wiped battery statistics
installed v9 using CWM 5(install zip from SDCARD).
result: bootloop
what gives?
My suggestion would be to try and Flash it all the way from kpe->kpq-> Miui .
This should not be happening based on what you have done so far. That is why the extreme measure of starting over.
If it still does not boot. We might be looking at something entirely different than screwed flashing.
cYbOrG5 said:
version: v8.5
wiped data/factory reset
wiped cache
wiped battery statistics
installed v9 using CWM 5(install zip from SDCARD).
result: bootloop
what gives?
Click to expand...
Click to collapse
same prob for me.
follow the above post method.
cYbOrG5 said:
version: v8.5
wiped data/factory reset
wiped cache
wiped battery statistics
installed v9 using CWM 5(install zip from SDCARD).
result: bootloop
what gives?
Click to expand...
Click to collapse
I install so: flash to KPE---KPQ---Root---Flash with CWM Miui V9. and good
even i had this problem...flash your i9003 with kpq and do factory reset/wipe cache...after rooting process is done using cf root...install miui and clear cache/factory reset
another suggestion may be only good for those not quite in bootloop:
when I flashed to v9, all of a sudden the phone had difficulty "waking up" for an alarm or incoming call. the home button wasn't enough, so I had to press the power button instead. things were weird like that, even when set to oc, etc., until I re-flashed vurrut v3 kernel. things have been normal after that. I didn't factory reset, just wiped caches before flashing v9 so I don't know why it worked that way for me.
is it possible that someone stuck in bootloop may be able to recover without starting over by doing this? for the next person that bootloops, try flashing vurrut v3 from recovery and wipe caches again, then try starting the phone and see if you still have bootloop.
May it helps...
Clean flash of xxkpe then xxkpq.....cf root for xxkpq.......nt ny kernal.....go to recovery...factory reset....cache clear....clear dalvik cache...battery stats....format system...flash v9......repeat procedure not flashing...nd dnt format the system again...reboot...keep still for 10 min....ur done
I found that" ddkp3" as bottom package will be more power, than other bottom package power, I tried[SIZE="<font><font class="">6</font></font>"][/SIZE]
Related
Well i have been using the cm7 nightlies with no problem. Today i decided to flash the RC1 since im sick of having to flash everyday. So i flashed the rom with rom manager and my phone was stuck in a boot loop.
So i had to do a battery pull and then restore the rom i had just backed up. After restoring i reboot the phone and am stuck in a boot loop again. I did another battery pull did a full data wipe, wiped cache and dalvik cache. And reinstalled the nightly 41 and am no longer in a boot loop.
So i tried to install RC1 again and everything was fine after flashing rom and gapps. i thought everything was fine so i rebooted into recovery to flash the 1.2.2 BFS Netarchy kernel. Before flashing i wiped cache, and dalvik cache. And of course now im stuck into a boot loop again. Has anyone else experienced this problem? i believe i am doing everything right. This is the first time i have ever experienced this problem.
B2L said:
Well i have been using the cm7 nightlies with no problem. Today i decided to flash the RC1 since im sick of having to flash everyday. So i flashed the rom with rom manager and my phone was stuck in a boot loop.
So i had to do a battery pull and then restore the rom i had just backed up. After restoring i reboot the phone and am stuck in a boot loop again. I did another battery pull did a full data wipe, wiped cache and dalvik cache. And reinstalled the nightly 41 and am no longer in a boot loop.
So i tried to install RC1 again and everything was fine after flashing rom and gapps. i thought everything was fine so i rebooted into recovery to flash the 1.2.2 BFS Netarchy kernel. Before flashing i wiped cache, and dalvik cache. And of course now im stuck into a boot loop again. Has anyone else experienced this problem? i believe i am doing everything right. This is the first time i have ever experienced this problem.
Click to expand...
Click to collapse
try flashing the kernel without wiping the dalvik or cache.
personal, i dont use or recommend using rom manager, as it creates issues of its own. i download everything myself and flash in recovery without rom managers aid.
I'm trying that now. Thanks for the quick reply. I have even tried installing the rom without using rom manager and it still did the same thing to me. Hopefully this works.
I was following a guide to root and flash a ROM for my LG Optimus V. I got to the step where I wipe data/factory reset, cache, and dalvik-cache, but I decided to continue the guide later and powered off my phone and ended up in fastboot. I got out of fastboot by installing the zip files for BACKside ROM from the recovery menu, so now my phone works but a few things are off like I can't receive calls, getting server errors on google play, and getting an error that com.phone.android stopped working. I'm not sure what to do next to resolve those issues.
Edit: I realized that before installing BACKside, I didn't wipe caches or format anything since I had done them before my phone went into fastboot. Does this make a difference and means I need to re-install BACKside (by wiping caches, formatting, and then flashing)?
flowerTea said:
I was following a guide to root and flash a ROM for my LG Optimus V. I got to the step where I wipe data/factory reset, cache, and dalvik-cache, but I decided to continue the guide later and powered off my phone and ended up in fastboot. I got out of fastboot by installing the zip files for BACKside ROM from the recovery menu, so now my phone works but a few things are off like I can't receive calls, getting server errors on google play, and getting an error that com.phone.android stopped working. I'm not sure what to do next to resolve those issues.
Edit: I realized that before installing BACKside, I didn't wipe caches or format anything since I had done them before my phone went into fastboot. Does this make a difference and means I need to re-install BACKside (by wiping caches, formatting, and then flashing)?
Click to expand...
Click to collapse
1)maybe the rom and ur baseband don't match
2) maybe bcoz u didn't wipe so ders problem
3) or the rom itself has prob
so do a full wipe including formatting system.
I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.
dmccrack said:
I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.
Click to expand...
Click to collapse
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?
Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
SlimSnoopOS said:
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?
Click to expand...
Click to collapse
The ROM was downloaded via Goo.im app
dmccrack said:
Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
Click to expand...
Click to collapse
So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse
Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse
dmccrack said:
So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
Click to expand...
Click to collapse
dmccrack said:
Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
Click to expand...
Click to collapse
No problem. As for your issue, its fairly simple actually. What you need to do is a clean flash which is either of the two steps I listed earlier. You're trying to go from TW to AOSP but what you did was only wipe the cache then flashed the rom. Wiping cache and dalvik cache is regarded as a dirty flash, something you only do when flashing a newer version of the rom you're on. You never fully removed the TW rom before flashing Liquid which is why it did not boot. Basically, when you want to flash a new rom, by a different developer, you need to do 1 or 2 in order to have a successful flash.
For AOSP roms, you should also be flashing the recommended GApps (Google Apps) as well so that you have your Play Store and a few other Google Apps. The latest "generic" gapps zip is listed here at the top, its "20120301" which is March 1st. Liquid may have their own, that's for you to find out via their thread. Google apps are included in TW roms so this is not necessary.
Samsung Galaxy S2 i727 Skyrocket.
I recently updated to a 4.3 rom.
It booted up and I just got a message "Unfortuanately, Nfc Service has stopped. Blame Tyler."
I couldn't get the message to go away and the only thing I could do was a hard reboot.
Still same issue.
Rebooted into Recovery mode.
Factory Reset, wipe cache partition, format /system, wipe dalvich cache
Restored an older rom.
It booted up with no issues. But when I rebooted, I just get the Samsung logo and then the screen goes black.
I even tried Factory Reset, wipe cache partition, format /system, wipe dalvich cache and installed a new rom from scratch.
Same problem.
I have no idea what to try next or why this is happening.
Any help or comments are welcome.
Thanks
benraines said:
Samsung Galaxy S2 i727 Skyrocket.
I recently updated to a 4.3 rom.
It booted up and I just got a message "Unfortuanately, Nfc Service has stopped. Blame Tyler."
I couldn't get the message to go away and the only thing I could do was a hard reboot.
Still same issue.
Rebooted into Recovery mode.
Factory Reset, wipe cache partition, format /system, wipe dalvich cache
Restored an older rom.
It booted up with no issues. But when I rebooted, I just get the Samsung logo and then the screen goes black.
I even tried Factory Reset, wipe cache partition, format /system, wipe dalvich cache and installed a new rom from scratch.
Same problem.
I have no idea what to try next or why this is happening.
Any help or comments are welcome.
Thanks
Click to expand...
Click to collapse
What recovery are you using?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Clock Work Method CWM...
I've done several ROM updates in the past with no problems...
benraines said:
Clock Work Method CWM...
I've done several ROM updates in the past with no problems...
Click to expand...
Click to collapse
What version of cwm? Most likely you need to update it. And what 4.3 rom?
Thanks.
I had a an older version of CWM and just upgraded to 6043..
Its now working with reboots...
I didn't realize CWM had that type of effect..
jd1639 said:
What version of cwm? Most likely you need to update it. And what 4.3 rom?
Click to expand...
Click to collapse
Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
CaffeinatedGuy said:
Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
Click to expand...
Click to collapse
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
CaffeinatedGuy said:
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
Click to expand...
Click to collapse
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
His bootloader is not locked, he never upgraded to the official 4.3 ota.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Click to expand...
Click to collapse
I wanted to try something else before formatting the card and having to deal with that, so I downloaded the zipped rom here http://forum.xda-developers.com/showthread.php?t=2591895
From CWM I wiped cache (again), wiped dalvik (again), and installed rom. On reboot, went through app optimization without any problems.
I'm not sure what the problem was, but I fixed it by using a different rom.
Thank you for the help.