You dont have to say I am silly or noob or stupid, cause I know that already. This is what has happened in case someone stucks in the same situation.
Three weeks using Nexus 4 (my first smartphone and first android phone ofcourse) and I have restocked 2 times (succesful, not count the fail one). Sometimes I felt frustrated and desperate, sometimes happy like I win lottery tickets )
- I used 4.2.2 franco kernel r80, nominal CPU. It sounds crazy but I UV -200 for all frequencies (the lowest one from 900 to 700). And everything run completly normal, I have tested ASpahlt 7 for 4 hours. NO reboot. 2 days without any reboot.
- I turned off the phone to charge it. Then opened again. UV -200, but it rebooted this time.
- Bootloop.
- I have tried to flash boot.img. It passed the X, then stuck at "Upgrading apps, starting apps" or something like that, I dont remember exactly.
- Then tried to reset to stock kernel. Stuck at Upgrading again.
- I try to restore my nadroid through CWM recovery mode, but the d*** recovery said MD5 checking failed.
- I restocked to 4.2.1 by Nexus Root tool kit, option: bootloop. After finishing, it stayed at fastboot for 15 minutes (i can still choose to recovery or reboot) while the tool says wait for the device to boot or something similar. I restart manually --> still stuck at Upgrading apps. I knew something was wrong here. Restart --> bootloop
- I restocked to 4.2.2 --> bootloop. (followed this guide http://forum.xda-developers.com/showthread.php?t=2010312)
- I restocked to 4.2.1 ---> bootloop.
- I restocked to 4.2.1 by NExus Root tool kit --> bootloop.
- I restocked to 4.2.1 by fastboot again --> still bootloop.
- About to call Google for RMA.
- I have no idea why I did the following thing. I went to recovery mode (the one with the android lying with a red triangle).
- Wipe cache partition
- Wipe data/factory reset. (maybe this is what saved me)
- Reboot.
- Huray, my darling comes alive again.
- But what has happened? Would you mind explaning for me please.
When you get a boot "error" due to a great UV the first thing to do is to reflash a kernel-> wipe cache and dalvik. If it doesn't work then you should Wipe data-> cache-> dalvik and here you go.
Important: Reflashing stock images without doing a wipe cache and dalvik cache often cause a bootloop, because you have the cache of the OLD ROM on your device.
These are my experiences, i may have said a lot of bulls***s
I can't give a good explanation, only an incomplete one. But when /cache contains bad data, reflashing /system and /boot will do nothing to solve the problem. Restoring a nandroid backup would work if you didn't encounter the md5 failure. The real question is why /cache got populated with bad data.
I got stuck in a bootloop when I first rooted my phone (by flashing CWM, then installing a .zip that contained SU). Wiping /cache cleared up the problem. It seems /cache is more prone to corruption on the N4 than my previous phone.
sorcio91 said:
When you get a boot "error" due to a great UV the first thing to do is to reflash a kernel-> wipe cache and dalvik. If it doesn't work then you should Wipe data-> cache-> dalvik and here you go.
Important: Reflashing stock images without doing a wipe cache and dalvik cache often cause a bootloop, because you have the cache of the OLD ROM on your device.
These are my experiences, i may have said a lot of bulls***s
Click to expand...
Click to collapse
I did wipe the cache and davilk when I reflashed the stock kernel, but I didnt wipe the data, maybe I should try this in the first time.
Thanks for your replying I am still a fresh man, so everything has its value, no bulls___s here :good:
fenstre said:
I can't give a good explanation, only an incomplete one. But when /cache contains bad data, reflashing /system and /boot will do nothing to solve the problem. Restoring a nandroid backup would work if you didn't encounter the md5 failure. The real question is why /cache got populated with bad data.
I got stuck in a bootloop when I first rooted my phone (by flashing CWM, then installing a .zip that contained SU). Wiping /cache cleared up the problem. It seems /cache is more prone to corruption on the N4 than my previous phone.
Click to expand...
Click to collapse
Thanks for this too
I am rooting my phone. Such a long night.
Related
Hello, I have recently been unable to flash ROM's succesfully.
I have Clockwork MOD 4.0.0.2 installed as it came with CF-Root, and I am on stock 2.3.5 KI3.
I have tried flashing several roms, and while it says install complete, whenever it restarts, it is on a boot loop, where it won't go past the Galaxy S II bit with the yellow triangle, I have to flash the stock rom again using odin to even use the phone, I have tried to flash other recovery versions, like 4.0.0.14 and 5.1.2.6 (I think it is) but they all come up with errors mounting or getting recovery.log or something, could you please help?
Did you try to do a full wipe?
Most issues can be resolved by this.
In the CWM menu chose the factory reset/full wipe. (Don't worry it won't touch your files on the internal SD card)
Do a cache wipe and in the advanced menu do a dalvik cache wipe.
Some recommend to do this procedure twice, but you should be settled with doing it once
Let me know if it helped?
theMartyMcfly said:
Did you try to do a full wipe?
Most issues can be resolved by this.
In the CWM menu chose the factory reset/full wipe. (Don't worry it won't touch your files on the internal SD card)
Do a cache wipe and in the advanced menu do a dalvik cache wipe.
Some recommend to do this procedure twice, but you should be settled with doing it once
Let me know if it helped?
Click to expand...
Click to collapse
Yeah I did all that, didn't help, the progress bar gets half way and says complete :S I have downloaded the ROMs several times aswell incase they were corrupt, still didn't help.
Take out the battery, wait a bit, put it back in. Do all the wipe and formatting procedures (perhaps twice) and format the internal sd card as well and wipe the battery stats (just to be sure)
Sent from my GT-I9100 using XDA App
Backup EFS folder 1st....
ultramag69 said:
Backup EFS folder 1st....
Click to expand...
Click to collapse
That's probably not a bad idea.
Here's how:
http://forum.xda-developers.com/showthread.php?t=1068193
Guys, I desperately need help. I followed this guide to install CM7.1 nightly into my Defy and at the end I got the CM7 logo loop. Based on the guide, I took out the battery and put it back and now it's stuck at the small "Google" logo. I took out the battery again and went to the system recovery to wipe cache/factory reset. I got bunch of "mount" cache errors (command, log). I then went to the custom recovery and did the wipe cache again, this time beside "mount" cache error, there were some "open" cache errors. I did the wipe one more time and all of these errors gone. Booted it up again, and it still stuck at the "Google" screen so I went into the custom recovery trying to wipe dalvik cache as the guide said. I selected that option but nothing happened. No question asked to confirm the wipe and all it did was a short blink screen and the screen stayed the same.
Any helps would be highly appreciated !!!
That sounds a bit tricky to me, but first things first.
The first boot after installing CM7 can take a while (some minutes) since all the dalvik cache and other things has to be built. Taking out the battery during that is somewhat risky I think. After the first boot, the system starts pretty fast.
The best guess for you (at least that is what I would try) is:
go to recovery, clear dalvik cache and cache. If you have not installed CM7 before, i would also recommend to clear data as well (ok you lose you data but I hope that you were not doing it without a backup).
Then I would reflash cm7 and try again.
since you had the cm7 boot scree, I believe you have no kernel problem...
by the way, do you know what version your initial rom was?
I think it`s better to flash it from scratch:
1) Flash your previous rom with RSD
2) Root + cwm recovery
3) Cyan
(and if I were you - I would do wipe from stock recovery after 1st step and wipe from custom recovery after 3 step)
Yes, as Iddqd2 suggested just flash stock froyo using RSD Lite and then go all over for CM7 method of installation.
Hey, first time posting. Flashed Shooter RLS 4.4 (first ROM) and everything was GREAT. I decided to change the unlock Screen from Android to Honeycomb (because it didn't show who was calling if the phone wasn't unlocked) and it said that I needed to reboot. So I did... And then it's been stuck on the white HTC Evo 4G screen ever since. I took out the battery and tried restarting, nothing. I took out the battery, booted into recovery, attempted to reboot via Amon Ra,...back to the white screen. Anything I can do other than re-flash the ROM? I don't have a nandroid backup (yeah, messed up).
Thanks in advance for the help.
Did you try wiping the Cache and the Dalvik while you were in recovery?
m20120 said:
Did you try wiping the Cache and the Dalvik while you were in recovery?
Click to expand...
Click to collapse
Just did and so far it's back up and running. A lil sluggish right now but I'm sure it'll work itself out.
Appreciate the help.
What exactly does wiping Cache and Dalvik do, if you don't mind explaining.
Thanks either way.
You need to wipe everything before flashing a new rom and cache and dalvik before flashing a theme or mod to a rom, cache and dalvike are temp files that need to be erased and rebuilt, you have to wipe everything else when flashing a new rom to get rid of all the data just like formatting a hard drive before installing a new OS
We are legion, for we are many
Whole Story:
I'm on a i337m Canadian S4 - Comes with Bootloader unlocked.
Last night I clicked "Format Data" by mistake in the newest TWRP - Lost everything - Could not do anything - flashing Roms did not work, so I downloaded a complete Restore of 4.2.2 from Sammobile and Odin 3.0.7 and was going to flash it back to stock.
About 1/2 way through the flash, something failed regarding a partition - Now my phone will not do anything other than display the below screen. It does not load a recovery, it does not go into download mode. Kies does not detect the phone anymore.
What can I do? Anything?
I'm so depressed over this.
bigystyle84 said:
Whole Story:
I'm on a i337m Canadian S4 - Comes with Bootloader unlocked.
Last night I clicked "Format Data" by mistake in the newest TWRP - Lost everything - Could not do anything - flashing Roms did not work, so I downloaded a complete Restore of 4.2.2 from Sammobile and Odin 3.0.7 and was going to flash it back to stock.
About 1/2 way through the flash, something failed regarding a partition - Now my phone will not do anything other than display the below screen. It does not load a recovery, it does not go into download mode. Kies does not detect the phone anymore.
What can I do? Anything?
I'm so depressed over this.
Click to expand...
Click to collapse
Format data will do nothing other than restore to factory settings, it should boot straight after.
winwiz said:
Format data will do nothing other than restore to factory settings, it should boot straight after.
Click to expand...
Click to collapse
From what I've read, Format Data using the newest version of TWRP deletes everything, causing everything not to work and is some sort of bug.
The ODIN Flash then failed after too.
I have the i337M Canadian version with the S600 Qualcomm
I've flashed via Odin dozens of times before with my previous Note II / S3 - never had one fail.
bigystyle84 said:
From what I've read, Format Data using the newest version of TWRP deletes everything, causing everything not to work and is some sort of bug.
The ODIN Flash then failed after too.
I have the i337M Canadian version with the S600 Qualcomm
I've flashed via Odin dozens of times before with my previous Note II / S3 - never had one fail.
Click to expand...
Click to collapse
Does adb detect the phone?
kingzain900 said:
Does adb detect the phone?
Click to expand...
Click to collapse
I'm not sure - I can see when I get home.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
Why did Format Data in TWRP cause all this to happen?
bigystyle84 said:
I'm not sure - I can see when I get home.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
Why did Format Data in TWRP cause all this to happen?
Click to expand...
Click to collapse
You can also ask Does god exist and what is the meaning of life.
Haha. I don't know. Such rethorical questions.
The cable matters because the other cable might not push enough current. Not sure. About the rest I have no idea. TWRP has a bug that's for sure. I don't use it. Check what adb says.
RESOLVED!!!
Tried my Laptop running Windows 7, and switched the cable. Also tried ODIN 1.85 instead of 3.07
Finally! This version of ODIN recongizes my phone.
3rd Attempt at flashing the firmware worked. The first TWO times failed.
Once it flashed, it froze, but factory rest has me back to Stock.
Now - to avoid that format Data button in TWRP, think I'll be giving CWM a try for the first time in years. Need me some Google Edition.
bigystyle84 said:
RESOLVED!!!
Tried my Laptop running Windows 7, and switched the cable. Also tried ODIN 1.85 instead of 3.07
Finally! This version of ODIN recongizes my phone.
3rd Attempt at flashing the firmware worked. The first TWO times failed.
Once it flashed, it froze, but factory rest has me back to Stock.
Now - to avoid that format Data button in TWRP, think I'll be giving CWM a try for the first time in years. Need me some Google Edition.
Click to expand...
Click to collapse
Wiping data, opposed to Formatting data.
TWRP FAQ
What to Wipe in TWRP
If you are switching ROMs (changing from one ROM to a completely different one) then you should perform a factory reset. A factory reset wipes data and cache (which includes dalvik cache). A factory reset will also wipe sd-ext and android_secure if your device has those items. 99% of the time, this is all that you need to wipe and you only need to do it once, not three times as some people would lead you to believe.
If you're installing a nightly update, then oftentimes you don't need to wipe anything at all. However, if you encounter strange behavior, then you may want to consider performing a factory reset. Of course, if the ROM maker recommends that you do a factory reset during an update, then it's a good idea to follow their recommendation.
The vast majority of ROMs wipe system as part of the zip install. This means that in most cases you do not need to wipe system... ever.
At this point, cache (not dalvik cache) is primarily used for recovery. It's used to store the recovery log and for storing OTA (Over The Air) updates. You probably don't need to wipe cache, and cache is already wiped as part of a factory reset.
In most ROMs, dalvik cache is stored in the data partition, so if you do a factory reset, you've also wiped dalvik cache. In a few custom ROMs, especially on older devices with small data partitions, the ROM maker may have moved dalvik to the cache partition to provide you with more room for apps. Since we wipe cache with a factory reset, again, you probably don't need to wipe dalvik. There are a few situations where you may need to wipe dalvik cache when installing updates, but you will know that it's needed when you are greeted with force closes when trying to open some apps.
Depending on your device and its configuration, you may have options for wiping internal storage, external storage, sd-ext, android_secure, and/or an option for formatting data. There's almost no reason that you would ever need to use these items. These options are there for convenience. For instance, if you're getting ready to sell your device, then it's a good idea to wipe everything on the device so that the new owner doesn't get your private data. Note that these wipe options may not be completely destructive. If you store especially sensitive information on your device or are really concerned about your private data, then you may need to look into other options to ensure that your data is fully destroyed.
norml said:
Wiping data, opposed to Formatting data.
TWRP FAQ
What to Wipe in TWRP
If you are switching ROMs (changing from one ROM to a completely different one) then you should perform a factory reset. A factory reset wipes data and cache (which includes dalvik cache). A factory reset will also wipe sd-ext and android_secure if your device has those items. 99% of the time, this is all that you need to wipe and you only need to do it once, not three times as some people would lead you to believe.
If you're installing a nightly update, then oftentimes you don't need to wipe anything at all. However, if you encounter strange behavior, then you may want to consider performing a factory reset. Of course, if the ROM maker recommends that you do a factory reset during an update, then it's a good idea to follow their recommendation.
The vast majority of ROMs wipe system as part of the zip install. This means that in most cases you do not need to wipe system... ever.
At this point, cache (not dalvik cache) is primarily used for recovery. It's used to store the recovery log and for storing OTA (Over The Air) updates. You probably don't need to wipe cache, and cache is already wiped as part of a factory reset.
In most ROMs, dalvik cache is stored in the data partition, so if you do a factory reset, you've also wiped dalvik cache. In a few custom ROMs, especially on older devices with small data partitions, the ROM maker may have moved dalvik to the cache partition to provide you with more room for apps. Since we wipe cache with a factory reset, again, you probably don't need to wipe dalvik. There are a few situations where you may need to wipe dalvik cache when installing updates, but you will know that it's needed when you are greeted with force closes when trying to open some apps.
Depending on your device and its configuration, you may have options for wiping internal storage, external storage, sd-ext, android_secure, and/or an option for formatting data. There's almost no reason that you would ever need to use these items. These options are there for convenience. For instance, if you're getting ready to sell your device, then it's a good idea to wipe everything on the device so that the new owner doesn't get your private data. Note that these wipe options may not be completely destructive. If you store especially sensitive information on your device or are really concerned about your private data, then you may need to look into other options to ensure that your data is fully destroyed.
Click to expand...
Click to collapse
Thanks - I realize this and am installing TWRP as we speak. (I just prefer it)
I was actually reading the Complete Guide in the general section and saw under CWM install that you need to format data between switching Roms.. I never actually did this ever with previous phones. Completely my fault for reading the CWM part, not the TWRP part, right under neath. I thought the Format Data was something S4 specific since this is my 2nd day with the device.
I'm now rooted with TWRP back on.
I installed Naptime (rooted phone). Put my 6P into standby. Worked for 15 minutes. I went away and came back and the device was in a bootloop. Can't believe naptime could be the cause of this, but things were fine before this was installed. Symptoms sounds like the bootloop others are complaining about.
Wiped the Davlik cache. Made no difference.
Tried to restore my TWRP backup and that reboots after about 90MB. If I choose verify the MD5 backup, TWRP reboots after about 30 seconds of verification. So it seems like any I/O attempt on the system partition is causing the 6P to reboot. Is there anything else I can try before resorting to an RMA w/Google?
mrlad said:
I installed Naptime (rooted phone). Put my 6P into standby. Worked for 15 minutes. I went away and came back and the device was in a bootloop. Can't believe naptime could be the cause of this, but things were fine before this was installed. Symptoms sounds like the bootloop others are complaining about.
Wiped the Davlik cache. Made no difference.
Tried to restore my TWRP backup and that reboots after about 90MB. If I choose verify the MD5 backup, TWRP reboots after about 30 seconds of verification. So it seems like any I/O attempt on the system partition is causing the 6P to reboot. Is there anything else I can try before resorting to an RMA w/Google?
Click to expand...
Click to collapse
Wipe everything except internal, and not only the cashes, and try your restore again.
You can also try to install a full factory image from the Google website using flash-all.bat command.
jhs39 said:
You can also try to install a full factory image from the Google website using flash-all.bat command.
Click to expand...
Click to collapse
Tried a full factory install of 7.1.2 (was on 7.1.1). Didn't help. Shows the Google boot logo and then reboots.
What is interesting is fastboot was able to write the system image for 7.1.2.
coremania said:
Wipe everything except internal, and not only the cashes, and try your restore again.
Click to expand...
Click to collapse
I'm on TWRP 3.1. Just noticed its crashing wiping any of the items (cache, Dalvik cache etc.). The reboot happens after it shows updating partition table.
Was finally able to get a clean Dalvik cache wipe. I noticed that in all cases, there are three TWRP errors about mounting the cache partition before it does the wipe. Is this normal?
mrlad said:
Was finally able to get a clean Dalvik cache wipe. I noticed that in all cases, there are three TWRP errors about mounting the cache partition before it does the wipe. Is this normal?
Click to expand...
Click to collapse
I don't know if it's normal but I've seen the same errors on my device after installing the 7.1.2 factory images and wiping the cache in TWRP 3.1. I assumed it might have to do with no cache partition being included with 7.1.2.
Sent from my Nexus 6P using XDA Labs
mrlad said:
Tried a full factory install of 7.1.2 (was on 7.1.1). Didn't help. Shows the Google boot logo and then reboots.
What is interesting is fastboot was able to write the system image for 7.1.2.
Click to expand...
Click to collapse
I still get a constant reboot too.
I also have naptime but this issue wasn't an immediate problem after any form of installation. I was just scrolling through facebook and then phone freezes and reboots and then gets stuck in reboot lol.
HELP
jono0402 said:
I still get a constant reboot too.
Click to expand...
Click to collapse
What does your reboot loop look like? I see the Google logo for a few seconds then the device reboots. I never see the animation start.