Database Users

Unbrick Using ADB

If this is in the wrong area please mods answer and redirect it into the correct area.
I was wondering if your phone is looped at the first bootloader screen and you cannot access recovery or bootloader is there a way to unbrick your device using a code in the adb?
Please answer...... and move if nessasary.
Thank You

I had been running Cyanogen 3.5.2 and then switched to JACHero 2.2 to see the changes. Then when I tried to switch back to Cyanogen and I kept getting the bootloop. No matter what I did, wipe, flash, wipe again, flash again. Nothing. I assume it might have something to do with the Apps2SD setup but I have no idea. I just reflashed back to JACHero and it is working fine.

chuckhriczko said:
I had been running Cyanogen 3.5.2 and then switched to JACHero 2.2 to see the changes. Then when I tried to switch back to Cyanogen and I kept getting the bootloop. No matter what I did, wipe, flash, wipe again, flash again. Nothing. I assume it might have something to do with the Apps2SD setup but I have no idea. I just reflashed back to JACHero and it is working fine.
Click to expand...
Click to collapse
Did you reflash using the ABD. If you did not then you would have to use the recovery or bootloader mode on the device. Therefore not using the abd commands at all. Im not bashing you or anything btw.

about cyan to jachero same happened to me... it has somthing to do with apps2sd your correct. somthing like the .odex files from hero saving on ur sd partion and ruining the whole setup on cyans. so what i did was use paragon partion manager to completely reformat my sd card and then remade my ext3 partion on it. and it works fine. im never switching off of cyans rom thoe. anymore to much of a headache and stuff.
(as you can tell im drunk and i really dont understand all this rom lingo lol bare with me i hope i helped you?)

nickryan0612 said:
If this is in the wrong area please mods answer and redirect it into the correct area.
I was wondering if your phone is looped at the first bootloader screen and you cannot access recovery or bootloader is there a way to unbrick your device using a code in the adb?
Please answer...... and move if nessasary.
Thank You
Click to expand...
Click to collapse
There are other posts on this but if you can't get into recovery or bootloader you are toast adb may not connect(really it should connect to adb when on the boot screen but many have been through this and haven't been able to get their phones working. I bet you tried flashing the Haykuro SPL("Danger" SPL) right?
It is brick you will have to look into a replacement/exchange if possible.

savethechicken said:
There are other posts on this but if you can't get into recovery or bootloader you are toast adb may not connect(really it should connect to adb when on the boot screen but many have been through this and haven't been able to get their phones working. I bet you tried flashing the Haykuro SPL("Danger" SPL) right?
It is brick you will have to look into a replacement/exchange if possible.
Click to expand...
Click to collapse
Oh no was just wondering cause i am thinking about rooting my phone but under the right direction. Not the posts they have here cause they are to hard to follow. If you or someone could help me i only wanna upgrade to a hero that has flash player and can put notifications out like this one : http://4.bp.blogspot.com/_Q-JSg53A3...AFD4/6TWLdeIi3VY/s400/rosie7-lock-screen2.jpg

I also had bootloop when switching back from jachero to Dude's 1.3. I had to pull the battery out to get it to shut down, but then I was able to use recovery to flash Dude's... how is it that you're unable to get into recovery mode? Have you tried pulling ythe battery?

ohnoezmahfone said:
I also had bootloop when switching back from jachero to Dude's 1.3. I had to pull the battery out to get it to shut down, but then I was able to use recovery to flash Dude's... how is it that you're unable to get into recovery mode? Have you tried pulling ythe battery?
Click to expand...
Click to collapse
If you mess up the SPL you can't get into recovery. The only known method of messing up the SPL is with the "Hero" SPL (afaik, without manually trying to brick your phone).
If you get a bootloop, make sure you wiped AND completely cleared your ext2/ext3 partition with apps2sd. That always seems to cause a bootloop.

G1 loops "hero" logo over and over

I purchased a used G1 off of ebay and when i got it it worked fine. I reset it in order to load my own profile as the previous owner still had his info on the phone.
The phone is running on the cyanogen mod v1.4 +jf.
I have rebooted the phone but now when i try to reboot the phone just keeps loading, with the "hero" logo comming up and the tone emmitting from the phone. it just keeps doing this over and over until i remove the battery.
Any help would be greatly appreciated.
Thanks

I also have this same problem of keep rebooting endless..after I choose Reboot phone, hope someone can help..

Grab the recovery image from my sig, install it, wipe the phone and ext parition.

thanks evilkorn, you must forgive me but i am new to the G1 so i am not sure exactly fhow to do that. any additional help would be appreciated

evilkorn said:
Grab the recovery image from my sig
Click to expand...
Click to collapse
See that, it says recovery image and you download that and follow the instructions.

evilkorn said:
See that, it says recovery image and you download that and follow the instructions.
Click to expand...
Click to collapse
Thanks for the help, I did what you said, wipe, reflash everything back, run ok, do all the setting everything fine, but soon as I restart it, there we go again, went from logo to blank screen and keep trying to boot endless..

i tried it as well. no luck here

You said wipe, were you sure you wiped the ext partition. If you did, repartition the sd card after you backup. Amon_RA makes a damn good recovery so it's easy to partition the card.

[Q] Did I brick my Hero?

Hello,
Last night I tried to install another radio fw on my Hero because of bad reception since the last one I installed.
I placed the new radio on my SD, rebooted and forgot to push the right buttons to access the "Android system recovery" (RA?) part.
Because it takes ages to wait for the phone to boot I pulled the battery and tried it again witch failed again, pulled the battery again etc.
When I finally managed to acces the "Android system recovery" part I flashed the new GSM radio to my GSM Hero. All the steps in described in the manual I used worked and all looked well.
After rebooting the phone started till the point of the Villainrom logo. I kept the phone on for hours till the battery was fully drained but it stays the same.
I can still acces the "Android system recovery", fast boot etc,
Tried the following:
-Wipe
-Restore backup
I'm getting pretty desperate!!
I's there anyone who has recovered his Hero from such a situation?
Please help..

If you can get to the recovery screen then you're not bricked. just reflash your rom and gapps add on and you should be fine or do a nandroid restore.

Hi pwraggcan,
I already restored a Nadroid backup.. Did not do the trick....
Also I tried to reflash the radio fw... Nothing helps. It just hangs at the unfolding Villainrom Logo which every few minutes restarts unfolding (I don't know how to call it otherwise, I do not mean that the phone restarts).

You're not bricked, so you're OK.
Re-flash the ROM you had installed after wiping your /data
Failing that, remove the SD card as that sometimes helps get the phone to boot.

If all else fails set up adb and get us a logcat.

Download the ROM again, full wipe & try again... Just to make sure the download didn't go bad?
Sent from my HTC Hero using XDA App

pulser_g2 said:
You're not bricked, so you're OK.
Re-flash the ROM you had installed after wiping your /data
Failing that, remove the SD card as that sometimes helps get the phone to boot.
Click to expand...
Click to collapse
Thanx pulser_g2!!
I started with the simple solution, removing my SD..
Without the SD is just starts!!!
HAPPY!!
Thank you for your quick replies!

RealR74 said:
Thanx pulser_g2!!
I started with the simple solution, removing my SD..
Without the SD is just starts!!!
HAPPY!!
Thank you for your quick replies!
Click to expand...
Click to collapse
You're welcome
Clear out your SD on your computer (back it up first), format it, and you should be good to go
It's usually the SD when this happens

[Q] Nook stuck on loading on Cyanoboot screen

Hello,
I was running one of the CM9 nightlies and decided to try one of eyeballer's with OpenGL, and was able to make the switch without any problems, but after a while wanted to go to a non-openGL build and after flashing it my Nook won't boot past the loading screen.
I have a 1GB card with CMW which I'm able to boot to, I've tried wiping data, format boot and format system and reinstalling one of the builds that had previously worked, but still get stuck on Cyanoboot's loading screen. Even tried going back down to CM7 to see if that helped, but stuck on that loading screen as well.
What am I missing here? I've formatted boot, system, cache, data, everything, but the issue persists.
Any suggestions as to how I can make my Nook come back to live.

ryuz4ki said:
Hello,
I was running one of the CM9 nightlies and decided to try one of eyeballer's with OpenGL, and was able to make the switch without any problems, but after a while wanted to go to a non-openGL build and after flashing it my Nook won't boot past the loading screen.
I have a 1GB card with CMW which I'm able to boot to, I've tried wiping data, format boot and format system and reinstalling one of the builds that had previously worked, but still get stuck on Cyanoboot's loading screen. Even tried going back down to CM7 to see if that helped, but stuck on that loading screen as well.
What am I missing here? I've formatted boot, system, cache, data, everything, but the issue persists.
Any suggestions as to how I can make my Nook come back to live.
Click to expand...
Click to collapse
Well, for one thing, never format boot.
After trying cm7, you still get cyanoboot? It should have changed to the green cyanogenmod logo. If not then your flashes are not working.
Sent from my Nook Color running ICS and Tapatalk

After flashing CM7 I get the green boot screen, but my Nook also gets stuck on that loading screen.
When flashing CM9 I can press the ''N'' button and scroll the available boot methods, but when I choose one I get stuck on loading again.
So on both CMs I'm getting stucked on ''loading'', which started to happen on Monday after going from one of the openGL builds to the latest non-openGL build.

ryuz4ki said:
After flashing CM7 I get the green boot screen, but my Nook also gets stuck on that loading screen.
When flashing CM9 I can press the ''N'' button and scroll the available boot methods, but when I choose one I get stuck on loading again.
So on both CMs I'm getting stucked on ''loading'', which started to happen on Monday after going from one of the openGL builds to the latest non-openGL build.
Click to expand...
Click to collapse
Ok, that means that CWM is putting the boot files on the boot partition since they change CM7 vs CM9.
Which version is your CWM on the SD?
You can't boot to anything, not even emmc recovery? Or you just can't boot to 'normal'? Do you even have emmc recovery installed? If you don't, get the first file on this post and flash it with your CWM card. You may be in a recovery bootloop, without a recovery.
http://forum.xda-developers.com/showthread.php?p=21932561
Sent from my Nook Color running ICS and Tapatalk

Thank you leapinlar, seems like it was me having an old CWM on my boot card that wasn't helping me, installed the recovery zip and manage to boot into that from cyanoboot's loading screen and reflashed and managed to boot my Nook.
I'm still intrigue as to how this happened, do you think that when switching between openGL and non-openGL the boot partition got corrupted or something? I've been flashing many roms for almost a year and had never had this issue happen to me before.
Thanks a million for taking time to help me, you're a life saver.

ryuz4ki said:
Thank you leapinlar, seems like it was me having an old CWM on my boot card that wasn't helping me, installed the recovery zip and manage to boot into that from cyanoboot's loading screen and reflashed and managed to boot my Nook.
I'm still intrigue as to how this happened, do you think that when switching between openGL and non-openGL the boot partition got corrupted or something? I've been flashing many roms for almost a year and had never had this issue happen to me before.
Thanks a million for taking time to help me, you're a life saver.
Click to expand...
Click to collapse
It's possible your recovery somehow got corrupted during the flash. If that happens, it does not clear the recovery boot flag and it keeps trying to boot to recovery and it can't because it is corrupted. And it just bootloops forever.
Also, make sure your CWM bootable card is a recent version. If you have a newer nook and an old CWM and you try to clear data, it fails and you have a mess.

Hi, I am totally new at this but I been having a nook color for over a year now and been running CM7 on it for the longest time. Tonight I wanted to put CM9 on and for whatever I did now I just can't seem to get pass the Cyanoboot screen. Doesnt matter what I do it just gives me a blank screen and stays there. What do I gotta do to fix it or get rid of this cyanoboot and back to CWM so i can re flash everything. Any help would be great. Thanks

huyroy said:
Hi, I am totally new at this but I been having a nook color for over a year now and been running CM7 on it for the longest time. Tonight I wanted to put CM9 on and for whatever I did now I just can't seem to get pass the Cyanoboot screen. Doesnt matter what I do it just gives me a blank screen and stays there. What do I gotta do to fix it or get rid of this cyanoboot and back to CWM so i can re flash everything. Any help would be great. Thanks
Click to expand...
Click to collapse
Try flashing latest CM7 then CM9 over the top. Might want to format Data and wipe caches in between.

DizzyDen said:
Try flashing latest CM7 then CM9 over the top. Might want to format Data and wipe caches in between.
Click to expand...
Click to collapse
I cant flash anything right now. I cant go into CWM and it just stuck at the cyanoboot screen and whatever choice i pick from that screen will give me a blank screen.

huyroy said:
I cant flash anything right now. I cant go into CWM and it just stuck at the cyanoboot screen and whatever choice i pick from that screen will give me a blank screen.
Click to expand...
Click to collapse
Try using my bootable CWM card in my tips thread in my signature. It works fine under ordinary circumstances, but I have been wanting someone to try it to see if it gets you out of that bootloop.
Edit: Just a question out of curiosity. When you finished flashing that new ROM with your CWM, were you able to reboot from CWM normally using the menu choice? Or was there some lockup or something where you had to reboot from CWM by hard powering off?

leapinlar said:
Try using my bootable CWM card in my tips thread in my signature. It works fine under ordinary circumstances, but I have been wanting someone to try it to see if it gets you out of that bootloop.
Edit: Just a question out of curiosity. When you finished flashing that new ROM with your CWM, were you able to reboot from CWM normally using the menu choice? Or was there some lockup or something where you had to reboot from CWM by hard powering off?
Click to expand...
Click to collapse
I believe i had to powering off. I'm sorry but I didnt quite understand what you told me to do with the bootable CWM. I am fairly new to all this flashing ROMS crap. If u can explain it a lil bit better that would be greatly appreciated.

huyroy said:
I believe i had to powering off. I'm sorry but I didnt quite understand what you told me to do with the bootable CWM. I am fairly new to all this flashing ROMS crap. If u can explain it a lil bit better that would be greatly appreciated.
Click to expand...
Click to collapse
Just follow the directions in the thread to make the card. Then put it in the nook and try booting. If it boots to CWM, just use it to flash like DizzyDen said. And when you exit, use the menu to choose re-boot.
PS, the hard powering off caused the problem. CWM was not able to clear the recovery flag and you ended up in a recovery bootloop. Let me know if my card boots.

leapinlar said:
Just follow the directions in the thread to make the card. Then put it in the nook and try booting. If it boots to CWM, just use it to flash like DizzyDen said. And when you exit, use the menu to choose re-boot.
PS, the hard powering off caused the problem. CWM was not able to clear the recovery flag and you ended up in a recovery bootloop. Let me know if my card boots.
Click to expand...
Click to collapse
Ok I read the instruction, i know i gotta put the bootable CMW Recovery SD. you said the file is attached to the board... what board? where can i get this file? lol thanks

huyroy said:
Ok I read the instruction, i know i gotta put the bootable CMW Recovery SD. you said the file is attached to the board... what board? where can i get this file? lol thanks
Click to expand...
Click to collapse
Look at the link in my signature. If you read the instructions, scroll to the bottom. Attached to that post.

leapinlar said:
Look at the link in my signature. If you read the instructions, scroll to the bottom. Attached to that post.
Click to expand...
Click to collapse
I got it to work, thanks alot running 4.0.4 now. Slightly choppier than the CM7 I had on but whatever lol

huyroy said:
I got it to work, thanks alot running 4.0.4 now. Slightly choppier than the CM7 I had on but whatever lol
Click to expand...
Click to collapse
Thank YOU for testing my card and proving that gets you out of the recovery bootloop you were in.
You need to take one more step. You need to put a new CWM back on your internal memory so it is there ready for the next time you want to install a ROM. If you go back to my tips thread, there is a link to a new flashable CWM zip (version 5.5.0.4) that can be put on your internal memory. The link is in item B1. Just download that zip file, then boot one more time to my bootable CWM card and install that zip. You should not need my card anymore after that unless you get in a bootloop again.

I've had something similar going on. I believe my nook has been using the EMMC to boot. It was on CM7. I grabbed the latest open GL CM9 because I plan on giving this to my parents. I wanted them to be able to use the TWC TV/DVR app which only works on ICS. I am stuck in a loop where it keeps going to recovery and neither flashing cm9 again nor recovering to an old back up is working. Is the recovery SD card the suggested method for fixing this? I'm not stuck in a loop but I am stuck and having to go into recovery every boot.
For awhile, the N menu gave me both EMMC and SD card boot options. Now it only has EMMC ones.

NapalmDawn said:
I've had something similar going on. I believe my nook has been using the EMMC to boot. It was on CM7. I grabbed the latest open GL CM9 because I plan on giving this to my parents. I wanted them to be able to use the TWC TV/DVR app which only works on ICS. I am stuck in a loop where it keeps going to recovery and neither flashing cm9 again nor recovering to an old back up is working. Is the recovery SD card the suggested method for fixing this? I'm not stuck in a loop but I am stuck and having to go into recovery every boot.
For awhile, the N menu gave me both EMMC and SD card boot options. Now it only has EMMC ones.
Click to expand...
Click to collapse
You could try the new CWM SD. Just make sure when you finish using CWM to exit from that by using the 'reboot' choice in the menu. Do not just hard power off.

leapinlar said:
You could try the new CWM SD. Just make sure when you finish using CWM to exit from that by using the 'reboot' choice in the menu. Do not just hard power off.
Click to expand...
Click to collapse
So slap the image on a clean SD card and boot up from it. After it's done and I hit reboot, what would I do to get back to CM7 or CM9? I haven't had to do something like this yet. Any time I've had issues, I've been lucky enough to go back to a saved clockwork backup and restore things back to how they should be

NapalmDawn said:
So slap the image on a clean SD card and boot up from it. After it's done and I hit reboot, what would I do to get back to CM7 or CM9? I haven't had to do something like this yet. Any time I've had issues, I've been lucky enough to go back to a saved clockwork backup and restore things back to how they should be
Click to expand...
Click to collapse
First thing I would try is just to exit the new CWM via the menu to see if it gets you out of the bootloop. Retry booting without the SD in. If it will still only boot to recovery, I would again boot to my CWM and flash the new recovery to emmc. Next I would try to restore your old nandroid backup with the new CWM. If none of that works, flash a new CM to emmc with the new CWM.

[Q] Stuck at Samsung Screen

Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..

I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2

jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:

FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.

Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.

Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great