Develop Bugs

Reboot Loop in Fresh 3.0.1.2 Any suggestions?

My phone is just rebooting to the Fresh boot animation over and over again. Here is what I've done.
I did a full wipe (3 times), cleared storage in recovery, wiped dalvik cache, pulled the battery, fastboot, wipe cache partition, wipe data/factory reset in recovery and nothing works. I'm using Clockwork Recovery v2.5.0.1 and I rooted via this method for mac:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac.html
I'm pretty sure half the **** I did was not necessary but I had to try something. Any ideas on what to do next?

Usually clearing cache/dalvik works... And you've wiped everything else... Have you checked the MD5 of your ZIP that you're flashing from? Or tried a different ROM?
Furthermore, have you just let the phone sit for a bit? The first boot after wiping cache can take quite a while.
EDIT: Also, did you do NAND unlock/eng hboot when you rooted?

I never did a nand backup. What would happen if I nand backup while having these problems? How do I check MD5?

I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.

Well doing a Nandroid backup of a broken ROM won't do you any good.
As for MD5, you should be able to open adb shell, then use the "md5sum" command to get the MD5 of the file. For example:
Code:
adb shell
md5sum /sdcard/some_rom.zip
You can then compare the MD5 it outputs with the MD5 posted by the ROM maker. If they haven't posted an MD5, you might want to re-think about using that ROM, and the competence of its creator. For example, CM6 Nightly has the MD5 posted in a text file in the same directory as all the ROM zip files for flashing. Amon RA Recovery has the MD5 posted in the OP of the thread, etc.

Philosuffer said:
I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.
Click to expand...
Click to collapse
What I'm trying to do is get my phone to work again. Here's what happened:
I downloaded this Rosie Clear Taskbar zip file that I found in the Themes section and flashed it. It looked horrible and was showing distorted so I figured I'll just reset my whole phone and get rid of it. Well it didn't work and it put me in a boot loop. I have no idea how to do a logcat and I'm pretty much new at this unless you post instructions I can adb with my mac. I need my phone today because it's my daughters birthday and people are going to be calling me left and right for details on the party. My phone just keeps rebooting at the Fresh boot. I can enter recovery just fine:
Is there a command I can do in adb while in recovery to make it ''safe boot''? How do I flash Fresh again?
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.

It's that easy
gqstatus0685 said:
...
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.
Click to expand...
Click to collapse
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.

Jim M said:
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.
Click to expand...
Click to collapse
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.

Apparently in my case it isn't as easy as flashing from the zip. I downloaded the ROM from geekme and put it on my SD card. Flashed it and even though it was successful I still get boot loop. Could it be because I accidentally did a nand backup of the problem?
What else could I do. I'm using Clockwork but is there a way to flash the other recovery through ADB even though my phone won't boot.
I can't take this to Sprint as it's rooted and showing the Fresh boot screen.

I had the same problem. Turns out I had the wrong kernel flashed from a previous rom. I had constant reboots, couldnt access my sd card, and the usb quit working. I had to ship it back to Asurion. Just got my new one back.
Bottom line:
MAKE SURE YOU HAVE THE RIGHT KERNEL BEFORE YOU FLASH A NEW ROM!!

SD Card
Do you have another memory card that you could use? Try putting a copy of a rooted stock ROM on it and try to install that.
http://forum.xda-developers.com/showthread.php?t=743352

As others have mentioned clockwork does not always work well with Fresh, try Amon RA's recovery

TheBiles said:
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.
Click to expand...
Click to collapse
The dalvik cache is under /data but the android cache has it's own partition.

Newbie help with VZN GN

So I decided to root my phone and upgrade to JB. But after I unlocked the bootloader, rooted the phone, flashed CWM Recovery and downloaded "Vicious JellyBean V2- No SU Zip necessary- Francos kernel and WiFi fix Zip" then went in to fastboot mode and installed it, my phone is hanging up on the new multicolored x splash screen and will not load. I waited 30 mins, I bricked it. So I went back into fastboot mode and reinstalled the JB, but still same thing.
So I am without a phone because I dont know what to do. :crying:
Any help is greatly appreciated!!!!! TIA

what do you mean by fastboot mode. You should have been flashing it through clockwork. Did you wipe your data, cache and Dalvik cache before hand? Or make a nandroid backup before installing Liquid?
If not sounds as if you are going to need the toolkit or push the stock files via adb to flash back to stock then start again

Get this set up.
I don't feel like debugging for two hours via text and reply.
I'll recover as much as I can.
Edit:
http://www.teamviewer.com/en/index.aspx?utm_expid=60202728-6
Lol, meant to paste that link.
Once that's installed I'll remote connect to your PC and try to fix this.

NeoMagus said:
what do you mean by fastboot mode. You should have been flashing it through clockwork. Did you wipe your data, cache and Dalvik cache before hand? Or make a nandroid backup before installing Liquid?
If not sounds as if you are going to need the toolkit or push the stock files via adb to flash back to stock then start again
Click to expand...
Click to collapse
I wiped with toolkit didnt cache or Dalvik cache. I have a replacement device coming today and want to try again. Is there a link to somewhere with step by step directions. I would assume the replacement device has factory settings so do I have to wipe, etc?

skinnytoo2 said:
I wiped with toolkit didnt cache or Dalvik cache. I have a replacement device coming today and want to try again. Is there a link to somewhere with step by step directions. I would assume the replacement device has factory settings so do I have to wipe, etc?
Click to expand...
Click to collapse
Manual Method
Toolkit Method
Just download a JB rom from the Development forum after you've unlocked bootloader, flashed a custom recovery, and have rooted your phone. Most are bug and glitch free...

I reflashed JB and it worked!!! Thanks guys!! Love JB

skinnytoo2 said:
I reflashed JB and it worked!!! Thanks guys!! Love JB
Click to expand...
Click to collapse
grats. next time, please dont incorrectly use the term 'brick'
brick = unable to turn on. no bootloader mode [fastboot], no recovery, no download.

Endless Boot Loop Gnex

I have been most recently running AOKP Milestone 6, and flashed to the JB build last night. I wiped, cleared cache, etc, and everything was fine; I went about restoring my apps and settings. My battery died shortly thereafter and now I'm stuck in an endless boot loop.
I tried restoring my backup, but still get the boot loop. I've even went as far as restoring my stock recovery of 4.0.3, but get "error restoring /data" when doing so.
How boned am I? I'd love to avoid going all the way back to factory settings and lose my data.
Any help is greatly appreciated.

Did you try to just reflash the ROM itself that you were using? If that doesn't work just wipe everything again and reinstall. If you have app backups it's no biggie.
Sent from my Galaxy Nexus using Tapatalk 2

codacrawford said:
I have been most recently running AOKP Milestone 6, and flashed to the JB build last night. I wiped, cleared cache, etc, and everything was fine; I went about restoring my apps and settings. My battery died shortly thereafter and now I'm stuck in an endless boot loop.
I tried restoring my backup, but still get the boot loop. I've even went as far as restoring my stock recovery of 4.0.3, but get "error restoring /data" when doing so.
How boned am I? I'd love to avoid going all the way back to factory settings and lose my data.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you flash a new bootloader or anything? Flashing the latest JB bootloader might help.

There's a thought that JB may run a file system check during the early boot phase in certain situations which is causing a lot of people to freak out because the phone stays at the Google splash screen for a long time. It's been reported that if you wait it out (can take up to tens of minutes) your phone should boot up normally.
I've myself have ran into this problem a few times but I've never tried waiting it out. What I've done is boot into CWM and use adb to pull the contents of my internal storage (/data/media) which includes my nandroid backups and then use "fastboot -w" to wipe the entire userdata partition. Afterwards I let the phone boot up to rebuild the userdata partition, copy my internal storage backup, and restore my nandroid backup.

silow said:
There's a thought that JB may run a file system check during the early boot phase in certain situations which is causing a lot of people to freak out because the phone stays at the Google splash screen for a long time. It's been reported that if you wait it out (can take up to tens of minutes) your phone should boot up normally.
I've myself have ran into this problem a few times but I've never tried waiting it out. What I've done is boot into CWM and use adb to pull the contents of my internal storage (/data/media) which includes my nandroid backups and then use "fastboot -w" to wipe the entire userdata partition. Afterwards I let the phone boot up to rebuild the userdata partition, copy my internal storage backup, and restore my nandroid backup.
Click to expand...
Click to collapse
I'm not stuck at the splash screen, it loops through the splash screen and the boot animation. Could you give me a little more detail on the process of pulling my data through adb?

Try this, wipe /system then reflash your old ROM again. Once that's flashed wipe davlik and cache and try a reboot. That should keep your data intact and just reload your old rom. Then you can renandroid and reflash.
Edit: just for safe measures makes sure you have any kernel software or tweaks disabled when you flash the new JB build. Of course if you are doing a clean install this won't matter. You just want to make sure things like overclocking or undervolting aren't crossong over to the new ROM, as say a 1.8 overclock might work on ICS kernel but not on a JB kernel. Hopefully that makes sense.
G-Nexus Sent

If all fails, use adb to pull all the important files, then use adb to push super wipe, and then flash it using your recovery. This will make sure that it wipes EVERYTHING. After that, just use adb to push Rom of your choice and then flash it.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

codacrawford said:
I'm not stuck at the splash screen, it loops through the splash screen and the boot animation. Could you give me a little more detail on the process of pulling my data through adb?
Click to expand...
Click to collapse
1.) Boot into CWM
2.) Go to the "Mounts and Storage Menu" and "mount /data"
3.) Plug in your phone to the PC
4.) adb pull /data/media c:\gnex_sdcard_backup

Stock Nandroid backup Bootloop - help

Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you

Try the cache clean up after the nandroid is restored.
Also try to install some other compatible kernel (if it's stock it should be also to find on the forums) after the restore with its modules if the cache clean up doesn't help.
Sent from my HTC One X using Tapatalk 2

Wipe the cache and dalvik cache again.

shadehh said:
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Click to expand...
Click to collapse
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat

Thanks for the help guys. I mentioned all the suggestions on this thread to him and it he was able to get it running
Sent from my HTC One X using xda app-developers app

bradmax57 said:
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Click to expand...
Click to collapse
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong

squirrelbo1 said:
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
Click to expand...
Click to collapse
The file shouldn't be on the phone, but on the PC.
Place it in the folder in which you have your fastboot files.

oh of course. I'm being a moron again.
I cant believe I did that. so very very simple. sorry for being a numpty guys. wasn't thinking strait. Done a few custom rom installs but never flashed a backup. Didnt even think. You even have to type the directory into command prompt.sorry guys I can't believe I didn't think that. (was thinking along the lines of installing from zip way)
to be fair the only reason I'm doing all this is because my screen is playing up and I need to return it so getting everything as close to stock as possible so got other things on my mind
everything is working now. Thanks guys. My god stock rom on HTC one x from orange is ugly.

No worries mate. You're not a moron, just a beginner.

TToivanen said:
No worries mate. You're not a moron, just a beginner.
Click to expand...
Click to collapse
thanks heaps for the thread guys, this has been a great help as I'm doing a similar thing and had the same problem.

USB Debugging not accessible

Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?

Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.

CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate

Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release

xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?

Try wiping data and cache again in recovery

xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.

BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.

xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help

aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?

xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery

it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?

It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4

actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.

BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide

BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated