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.

Nexus One "continuously reboots to "X" screen."

Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!

fastboot
just check for fastboot. the rest is easy cheeze.
how much is a good deal ?

unlocked $300 (cad)
What should I check? Instruct me plz, I never had a nexus one or even a Droid phone before ... (coming from 2 years old HTC cruise, with WM 6.5 with an XDA rom ....)
If I meet the guy, how to I check that hes not selling me a bricked nexus lol ?

Installing a new rom will fix it
Sent from my IPhone 4 using XDA App

Amritttt said:
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Click to expand...
Click to collapse
are you 100% ?
I dont mind working on it, I just want to make sure that it is reparable via software/roms.
ppl plz tell yours, im just about calling this guy, really dont wanna waste $300
what is its restarts so much, that I cant flash the rom or something? there's no way that that could be the case, right?

sold ... goddamit lol But I'll get one one way or another

I was having this happen to me a lot. I moved in to a new place with no cable or internet yet, so my N1 was under extremely heavy use. And when it was warm, it would get both the touch screen problem and the random reboots.
I was using pershoots 2.35 Kernal. I went back to the stock kernal and the phone has since been running a lot cooler. Zero reboots, touch screen responds correctly. I take the stock kernal stability over an OC kernal any day.

It's a kernel issue that can most likely be fixed by flashing a new
ROM/Kernel, however there is always a small chance that it is triggered by faulty hardware.

My Nexus had this Problem Was unfixable by software. Hardware defect. I wouldn't buy.
Still waiting for my swap unit

i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?

xxlikquidxx said:
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
Click to expand...
Click to collapse
all is not lost if you can still get into hboot:
Have you tried to restore these original files via adb?
boot boot.img
recovery.img
system.img

I have this problem now...
It keeps on rebooting and rebooting ... and just comes not forther than the flashing X..
I tried system wipe but this didnt help ( I installed a battery widget which wasn't for my rom)
how can i restore my nexus now?
Pleas help!
Edit: Found a way...
Unlock you phone, fastboot, clockworkmod(?) recovery and the select the nandroid backup...
about passimg (see lower) i have no clue

passimg FRG33...
Sent from my Nexus One using XDA App

Even though solved, something to keep in mind: Its probably a ROM (or kernel issue as they said), but I had a revolving X due to a bad battery too.

it can be solved
ViSK said:
Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
Click to expand...
Click to collapse
4 color problem can be solved ..

Bricked my Evo.

Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.

TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven

TWRP2.0 is an evo killer as far as I know there is no fix for a TWRP brick I'm pretty sure it messes up something in the partitions possibly boot or system partition which is why it bootloops
We are legion, for we are many

Unfortunately your phone is toast. Had the same problem, and really there is no way to recover. You should have bit the bullet in used insurance instead of going through Sprint since the Evo is past EOL. You maybe waiting a long time to get a replacement where as going through Ausion (sp) you either would have gotten either a new Evo, a refurb'ed Evo, or a new Evo3D (most likely).
Sent from my ICS-less Transformer TF101 using Tapatalk

Art2Fly said:
Well, I first of all was using TWRP 2.0 as my recovery. However, i did not know that it was known to cause bricks. Anyway, I was doing a routine clean flash of a new rom i wanted to try, the aokp build 22 rom. I wiped everything, making sure to hit wipe system as well in twrp, then i put my phone to mount the sd card, transfered the rom, flashed it and its gapps then i reboot. Now all my phone can do is reboot endlessly, So I got into the bootloader and selected recovery, still, just keeps bootlooping. So then I decide to find an RUU and flash it through fastboot. It flashed everything correctly but when it got to step 4, (system) the phone would say error and it would fail to flash the system. After this I was still at bootloop. I dont know what it is, I even tried flashing Amon_Ra through fastboot, and ive been able to get to recovery once or twice but just to find it completely unresponsive and it wont read/mount my SD card even though i checked and the sd card was fine. All in all, I took it over to sprint and since i have TEP they agreed to get me a new one, though it was backordered so now im a week without a phone. Anyway just wanted to share my story, if anyone else knows of a way to fix it, im all yours.
Click to expand...
Click to collapse
scottspa74 said:
TWRP kills. Good luck. Sorry you didn't follow up regularly on the thread of the product you were using. If anyone can help you, it might be Captain Throwback, but I think he's been a bit busy lately (i.e. been absent). Good luck, but TWRP fncks you.
sent from AOKP heaven
Click to expand...
Click to collapse
It's been a busy week for me, but I am still alive, and still using my previously-soft-bricked device .
I can link you to what I was able to do to get mine working (HERE), but if you can't get the device to boot up at all, you might be in dire straits. What is your HBOOT status? (version, NAND status)

hey Cap'n, you need some kind of superhero shield in your user icon
sent from AOKP heaven

How I almost made a brick

My 2 cents..
I was using ICSSGS from 1st RC. But it becomes very laggy after 3-4 weeks, so factory reset every month was necessary. I decided to change ROM.
I installed DOC's v12 ( I assume is is the same Doc that was cooking ROMs for my Omnia, and I was werry pleased with those ROMs). Did wipe, cleaned cache, cleaned Dalvik, formatted /system, flashed ROM, wipe again and it was working. But after two days it was still very laggy (talking about waiting for response for 3-5 seconds) so I wanted something faster. I had choose this Openkang milestone 6.
And then the fun begins.
Downloaded, copied to sd, booted to CWM, all wipes, flashed ROM, flashed gapps and went to bootloop. 3 button combo worked only for download mode, not for entering CWM. There was no way I could access CWM. I even could not enter Android boot (don't know exactly how it is called, but it saved my TF101 more than once.)
So after 1/2 hour of unsuccessful trying to get to CWM, phone just shows logo for icyglitch kernel and went to boot again, I have seen that only option to do anything was Odin. I downloaded Odin, downloaded some 2.3.6 ROM and downloaded CWM for that rom.
First I had to find driver for phone. I remembered phone on ICS wants nexus drivers so I installed those, booted phone to download mode and flashed 2.3.6 rom with Odin.
Phone booted, boot animation was on screen, but it did not boot to working Android. I didn't care too much, just booted to download mode again, flashed CWM and now I had at least access to my sd card. Did all wipes again, flashed DOC again and went to bootloop (Icyglitch kernel logo) again.
....
So I repeated Odin procedure, and when I had working CWM I flashed good old ICSSGS 4.02. This one worked.
I had spent 4 hours to solve this problem mostly because I was not full prepared to flash.
-I had no working USB driver on PC
-I did not had Odin
-I do not have ADB installed. Even if I had it, I don't know much how to use it.
-I did not have any working 2.3.6 ROM WITH bootloader
-Nandroid backup... hmmmm... what is that? Bah, don't need it...
Luckily I flashed my phone so many times I already roughly know what to do, but I still have experienced my share of "OMGOMGOMGOMG".
My advice to new and seasoned flashers:
Don't be cocky. After million of successful flashes once will go wrong. If nothing else Murphy will kick in. And when something goes wrong, be sure that all that you need to rescue phone is on your HDD and you know WHERE it is and how to use it. And read guides. And when you finish reading read them again, then go to sleep and flash next day.
Now I'm even more satisfied with myself because I do not flash other people's phones. If it happens that I create a 400€ brick, it will be at least mine.
If this helps anyone to restore phone, click Thanks button :good:

Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!

slaphead20 said:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
Click to expand...
Click to collapse
Lol you were faster .

I had the same problem today trying to flash aokp m6...
Got bootloop and then Odin was hanging at various points when I tried going back to stock GB.
I thought I was goosed but the good old SGS came through in the end!
Sent from my GT-I9000 using xda premium

Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Stratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.

I would suggest you try SlimICS the next time you get sickend of (laggy) ROM. I for one, absolutely love SlimICS, and as all, it does have some drawbacks (no lag, though) when you're pimping it out too much.

upichie said:
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Sratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
Click to expand...
Click to collapse
Too bad I didn't know that. Somehow I was convinced that no ICS rom or kernel is flashable via Odin. But Later when everything worked and I finally had time to breathe I thought that I didn't need to go to GB. I think maybe only to flash any GB CWM with Odin would be enough. All I needed was working CWM, not entire rom.
Anyway, I'll try Slim now, let's hope I won't need to rescue phone again.

I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.

bpp9 said:
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
Click to expand...
Click to collapse
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!

Always brick my phone in the past, nearly one time a day
Well some tips for flashing:
- On stock ROMs, try flashing all partition firmware (i.e. 3 files in Odin) with re-partition checked before finding for help.
- Always backup you data with apps like Titanium backup, I don't usually use nandroid because it is not so flexible.
- Get GB bootloader before going to CM based ROMs, and go back to froyo bootloader if you want to have froyo back (search EzBoot for this).
- CM based ROMs and stock ROMs use a different filesystem, so flash all partition firmware before going back from CM to stock.
- Same reason, you will mostly get bootloops when going to CM ROMs. In this case, just hold the 3-button combo to enter recovery and flash it again.
- Same reason again, don't use CWM2 recovery to flash CM.
In case that anyone don't know, CM means CyanogenMod.
Hope this helps!
Sent from my GT-I9000 using xda app-developers app

tt0204 said:
Always brick my phone in the past, nearly one time a day
Click to expand...
Click to collapse
Uauuu, and you still didn't have heart attack?
I'm not sure if the fact that I managed to rescue my phone is good. Now I still don't have reason to buy SGS II.
And yes, Slim is woking, you can see my new signature. :highfive:

Managed to flash properly before I did
Wait at least until we get a working jelly bean before getting a new phone!
Sent from my GT-I9000 using xda app-developers app

slaphead20 said:
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Click to expand...
Click to collapse
Ahaha, I did the exact same thing the day before yesterday!
Using GT-I9000 my sent Tapatalk 2 from.

First time i flashed my phone was a heart in mouth moment when it boot looped for the first 2 or 3 times.
Swore I'd never flash my phone again. Over a year later and my phone has gone through countless changes and still going strong.
The only other issue I've had with customizing my phone is telling my flatmate about it. Problem being that he doesn't quite understand the concept of 'rooting' or 'flashing'. At least not in the geek sense of the words.

Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi

dreamer94 said:
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Actually boot directly into download mode without rebooting computer/phone will work

i know but wanted to live with that action,adrenaline
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi

I think we should start a membership here. Anyone who wants to join must expirience "OMG" factor for at least 20 min. I had it 4-5 times, if I count my hassling with Omnia too.
Isn't something interesting? I mean, look at us. We flash phones, sometimes we manage to make it useless, we spend hours for rescuing them, all that time we swear to god that we will never do that again, but 5 minutes after we manage to make our phones work we are ready for next flashing. Here in Slovenia we use to say that even donkey goes on ice only once, but looks like we newer learn...

My current favorite thread, it's refreshingly honest to see people laughing at themselves, and sharing their disasters, we all do it, in fact that's why we do it! Nice to see so much humility

About not bricking other people's phones....
Right now I'm in the process of bricking my boss's phone. He wants ICS on his Dell Streak 5, even if it is only pre-alpha ... Wish me luck.

Problems installing new ROM

Dear All,
After losing my Samsung Galaxy Note in Amsterdam during a heavy weekend I am back on my girlfriend's old ZTE Blade and have been trying to update it a little.
I downloaded the KonstaKang ROM and GApps to the ext. Sd card and booted into clockwork mod recovery (I rooted and flashed a custom rom for her when I gave it to her originally).
I did the full wipe just to make it all as clean as poss and went to install the new rom but ran into some problems.
Firstly the sd card could not be accessed. It was if it was not mounted. I tried various things including mounting it in mounts and storage, restarting recovery, reformatting the sd in another android and the pc etc. Eventually (it felt random) it let me choose zip from sd.
Thats when the rom was selected but it then told me that the rom was (bad) and would not install. Again I redownloaded it and another rom and also a new version of cwm. Still nothing would work it was all (bad).
Out of frustration I kept trying and eventually it changed its mind and let me install the rom. After installation I attempted to reboot system but it just hanged at the boot logo and would go no further.
I have tried all the above multiple times and all combos of things I can think of to get it to work but no luck. The phone randomly seems to decide if the .zips are (bad) but at least it allows me to access them now. Ive also tried installing the other rom and new cwm but nothing will work. Boot logo and nothing more.
Anyone have any ideas what might be wrong? Whats the best way to get a rom on this old blade?!
Many thanks x
Sent from my GT-I9300 using Tapatalk 2

Well, first, you have an S3. Why use the Blade?
Second, have you looked into TPT + ROM? Also, what Gen blade is it? Once you can get something stable like cm7 booting, we can progress further
Sent from my Nexus 4

QuantumFoam said:
Well, first, you have an S3. Why use the Blade?
Second, have you looked into TPT + ROM? Also, what Gen blade is it? Once you can get something stable like cm7 booting, we can progress further
Sent from my Nexus 4
Click to expand...
Click to collapse
Well I believe it is a gen2 blade. I vaguely remember having to update it from gen1 but I cant be 100% sure. It was a long time ago!
I am using my girlfriends s3 to get on these forums so unfortunately I cant keep it!
I havent looked at tpt + rom and am unsure what that is at the moment . I shall have a read.
I must also say that I managed to install a new version of cwm but still no luck with any roms.
I am loading new roms on the ext sd from this s3 or through my pc I was wondering if the files were getting corrupted somehow. My pc doesnt see the phone so I have to use a card reader.
So yes roms are still saying 'cant open... (bad)' error when trying to install...
Thanks for your reply
Sent from my GT-I9300 using Tapatalk 2

rattymon said:
Out of frustration I kept trying and eventually it changed its mind and let me install the rom. After installation I attempted to reboot system but it just hanged at the boot logo
Click to expand...
Click to collapse
I also have realised since installing new version of cwm that it never actually let me install it just restarted recovery and didnt show the error log.
Sent from my GT-I9300 using Tapatalk 2