Hi XDA, been lurking for a while and today decided to start posting, beginning with a relatively urgent question.
My brother's been marveling at the ability to flash custom ROMs onto my Galaxy S2, and decided he wanted to root his Atrix today. Rooting process went well (he used Pete's Motorola Root Tools) and then flashed CWM through ROM Manager, but did NOT unlock his bootloader. After CWM was purportedly done, he put a ROM onto his HDD, turned the phone off, and attempted to boot into CWM. He was greeted with an error message, "Failure to Boot 2, Starting RSD Mode", which pops up whether he tries to turn on the phone normally or by holding the volume button down. Taking out the battery doesn't help.
Now, my assumption is that because he didn't unlock his bootloader, he's getting this error, but my experience with Android dev is limited. So, how would I go about fixing this? My only concern is getting the phone back to a working state, we don't care about the data on it.
Thank you for the time taken to read and answer this question, any and all help is appreciated.
Warm Regards,
Leo
EDIT: Just want to make sure, I did a fair amount of searching before I made this thread and found a bunch of answers, just not sure which one I should do. One thread champions just unlocking the bootloader, others suggest flashing an OEM ROM, which I'm not sure how to do without CWM. Essentially I'm just looking for some guidance and would deeply appreciate any help I can get.
EDIT 2: Forgot to add - he was running 2.2.1 stock. Root was successful. Feel free to ask any questions if necessary.
UPDATE: I've been trying to use these instructions to unlock the bootloader, but I'm stuck on the step that asks you to reboot your phone into RSD mode. The phone doesn't boot without being plugged in, and gives me the following error when I do:
Failed to Boot 2, Starting RSD Mode
"Battery is too low to Flash". Right now the phone's plugged into the wall with this message displaying,
It also goes without saying that RSD Mode, in fact, is never started .
Added some more information (apparently new members aren't allowed to post links, so added the information as UPDATE in the original post).
Again, thanks for your help and suggestions.
Bump, somebody please weigh in.
- Leo
Sent from my i777 using Tapatalk, on ICScrweD 2.1
FatalFlaw said:
Hi XDA, been lurking for a while and today decided to start posting, beginning with a relatively urgent question.
My brother's been marveling at the ability to flash custom ROMs onto my Galaxy S2, and decided he wanted to root his Atrix today. Rooting process went well (he used Pete's Motorola Root Tools) and then flashed CWM through ROM Manager, but did NOT unlock his bootloader. After CWM was purportedly done, he put a ROM onto his HDD, turned the phone off, and attempted to boot into CWM. He was greeted with an error message, "Failure to Boot 2, Starting RSD Mode", which pops up whether he tries to turn on the phone normally or by holding the volume button down. Taking out the battery doesn't help.
Now, my assumption is that because he didn't unlock his bootloader, he's getting this error, but my experience with Android dev is limited. So, how would I go about fixing this? My only concern is getting the phone back to a working state, we don't care about the data on it.
Thank you for the time taken to read and answer this question, any and all help is appreciated.
Warm Regards,
Leo
EDIT: Just want to make sure, I did a fair amount of searching before I made this thread and found a bunch of answers, just not sure which one I should do. One thread champions just unlocking the bootloader, others suggest flashing an OEM ROM, which I'm not sure how to do without CWM. Essentially I'm just looking for some guidance and would deeply appreciate any help I can get.
EDIT 2: Forgot to add - he was running 2.2.1 stock. Root was successful. Feel free to ask any questions if necessary.
UPDATE: I've been trying to use these instructions to unlock the bootloader, but I'm stuck on the step that asks you to reboot your phone into RSD mode. The phone doesn't boot without being plugged in, and gives me the following error when I do:
Failed to Boot 2, Starting RSD Mode
"Battery is too low to Flash". Right now the phone's plugged into the wall with this message displaying,
It also goes without saying that RSD Mode, in fact, is never started .
Click to expand...
Click to collapse
You are correct in just trying to unlock the BL. Unfortunately, you will need a charged battery to do so. If you don't have access to a different battery, you can go to an AT&T store and they should charge it for you.
The OEM you're referring to is a full .sbf, instead of just the smaller "unlock" .sbf. That is an option, but in all honesty, unlocking the BL should be the quickest way to fix your situation.
If you run into any problems, let us know.
Thanks for the advice, it's immensely reassuring. He went to an AT&T store and they were unhelpful, refused to charge it for him I'm going to order a battery charger off Amazon and charge it that way, and will post here when I have results.
In the meantime if anyone else has something to add it would be quite appreciated.
Thanks,
Leo
Sent from my i777 using Tapatalk, on ICScrweD 2.1
Alright, we've run into a problem.
The screen never gets past the error message "Failure to Boot 2, Starting RSD Mode". We turn it off, hold power and up at the same time, and it still boots to that message. I press the power button and hold the volume up button, nothing changes.
The battery is charged.
Is there something I'm missing here?
FatalFlaw said:
Alright, we've run into a problem.
The screen never gets past the error message "Failure to Boot 2, Starting RSD Mode". We turn it off, hold power and up at the same time, and it still boots to that message. I press the power button and hold the volume up button, nothing changes.
The battery is charged.
Is there something I'm missing here?
Click to expand...
Click to collapse
The .sbf's are flashed while your phone is in RSD Mode
in order to charge your battery (to fix the "Battery is too low" message) you will need to sacrifice any USB cable, cut it open and tape the red and black wires to the battery. (Red goes on +, Black goes on -)
ghost_og said:
The .sbf's are flashed while your phone is in RSD Mode
Click to expand...
Click to collapse
Yep, I realized that. I thought "Starting RSD Mode" would at some point subside, and it would say something along the lines of "In RSD Mode" or something. But he flashed an unlock SBF and got it unlocked. He now has a beautiful Atrix running ICS MIUI.
Thank you all for the help.
Same problem but the solution does not work for me
I am in the same boat. I downloaded RSD 5.9 and used the file in pudding.rar. After I loaded the file, RSD said it passed with 100% load but the phone is still stuck in the same place. Can anyone help?
Related
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
are you getting a screen with just...
(SVF message: 105:1:2 failed to boot 0x1000)
or something like this?
No OS detected, going to rsd mode in 5seconds press a key to stop count down available modes are:
1)rsd
2)fastboot
3)NvFlash
4)Bp HW Bypass rsd
5)BP HW bypass QC Dload
6)BP HW diag & Boot AP
7)BP HW Bypass BP only
8)BP SW Bypass RSD
9)Android recovery
10)boot android (no BP)
11)Device UID
12)console=tty50,115200n8
13 Early USB enumeration
14)BP tools
Did you not read the WARNING thread? It's stickied and is called WARNING for a reason.
[WARNING] Hard Brick with Official 4.5.91 Update
http://forum.xda-developers.com/showthread.php?t=1160408
If the error is indeed (SVF message: 105:1:2 failed to boot 0x1000), you are SoL.
Defnow...i keep getting the first msg. followed by a REALLY quick one about RSD and then the phone shuts off...to the point where i need to take the battery out so i can look at the msg again. Edgeicator was right on target with the link.
Edgeicator, you got it right...unfortunately i didn't read the post...the shock of loosing a phone like this (specially living in Brazil) was enough to have me trying everything i could...i did read a couple of posts where people was being told to try the rollback...i was stupid and unlucky...a dangerous combination.
So i guess there's no solution in sight? should i just prepare myself psychologically to buy ANOTHER phone?
Thanks for the answer guys.
hard brick man. Sorry.
Sent from my MB860 using XDA App
if u can somehow get the phone to stay on and be recognized in RSD u could try to flash the pudding sbf then fast boot and load the system and boot.img files from the fruitcakes thread. Otherwise ull be buyin a new phone if u cant get a warranty replacement.
GeekIndustries said:
Defnow...i keep getting the first msg. followed by a REALLY quick one about RSD and then the phone shuts off...to the point where i need to take the battery out so i can look at the msg again. Edgeicator was right on target with the link.
Edgeicator, you got it right...unfortunately i didn't read the post...the shock of loosing a phone like this (specially living in Brazil) was enough to have me trying everything i could...i did read a couple of posts where people was being told to try the rollback...i was stupid and unlucky...a dangerous combination.
So i guess there's no solution in sight? should i just prepare myself psychologically to buy ANOTHER phone?
Thanks for the answer guys.
Click to expand...
Click to collapse
I believe if its still under warranty you call up the ATT guys which will direct you to the Moto guys and they will ask you to ship your phone to them to fix since its a software related issue.
And how the hell do you manage to HARD BRICK your phone even with all these threads and warnings.
One question though, when you boot up the phone does the computer recognize it? I believe if it does you still can fix it.
Yeah i thought so...it sucks, but its good learning.
As i said before, searched around the web and got a couple posts, all pointing in the direction of a rollback, even if already updated to 2.3.4 ...bad luck for me.
I already sent msgs to those threads so they post a big ass red warning so no one will follow the same path.
...time to ponder my next buy...should i go for a replacement Atrix...should i try the galaxy 2s...should i get a crappy phone and wait for Atrix2?
GeekIndustries said:
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
Click to expand...
Click to collapse
Another one bites the dust...Sounds like a HARD Brick. Ginger*ucked!!
GeekIndustries said:
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
Click to expand...
Click to collapse
Another one bites the dust...Sounds like a HARD Brick. Ginger*ucked!!
I really suck at installing custom ROMs.
I hard bricked because of low battery while flashing (I think, screen won't turn on, green light only comes on when plugged into a computer with no battery in, and a couple of posts I read made it sound like I'm screwed). So I'm going to AT&T tomorrow and hopefully getting a new phone. My main question is...
Can someone point me in the direction of a very comprehensive guide to installing a custom ROM on a stock Atrix brand new from the store?
I have poured over these forums for five days obsessively trying to figure out why I am so stupid and can't make it work, and have probably tried ten different methods of everything to get it to work, hoping that one of them had whatever I was missing already taken care of.
I rooted and unlocked my bootloader just fine. Even installed the Gingerblur rom (but that's a P-ROM right?). I think my problem is the custom recovery. Yes I deleted the recovery_install file. I tried flashing tenfar's CWM (the newest one I think, I sideloaded a different one to get Gingerblur) with fastboot but it said something like "flash:recovery is not a known command." (Sorry I don't remember completely, this was very early this morning before I went to sleep) I thought at the time that once you unlocked the bootloader you didn't have to do it again, but I read a thread an hour ago that said you just have to flash the unlock image after an RSD reset. So I was going to try to re-unlock, then try and flash with fastboot. Unfortunately I never got to try.
I am sorry for my obnoxiously long post, but I figured the more info I gave the higher chance there would be that someone could point at the obvious for me.
Thanks for your time.
when you plug the phone to wall-charger...wt happens?..do you see anything on the screen..
No. Also nothing happens when I press the power button. The green light ONLY comes on when I plug it into my computer with no battery, not when I plug it into an outlet.
Not entirely the right person to give advice but I guess it's worth a shot trying.
I'm a bit confused as to what you actually did. You're rooted and unlocked (100% sure on this?) Had gingerblur installed (guessing you were unlocked on 1.8.3?) and then wanted to install CMW, correct?
From the error you got you probably didn't cd (folder fastboot is in) flash fastboot recovery (path of recovery-en-goapk.img). Deleting the stock Android recovery folder most likely left you without any recovery. (Someone correct me if I'm wrong )
Entirely sure NOTHING happens while being plugged in into a computer? Can you get into fastboot at all? When connected via USB, does RSD show your device?
xscottishx27 said:
Not entirely the right person to give advice but I guess it's worth a shot trying.
I'm a bit confused as to what you actually did. You're rooted and unlocked (100% sure on this?) Had gingerblur installed (guessing you were unlocked on 1.8.3?) and then wanted to install CMW, correct?
From the error you got you probably didn't cd (folder fastboot is in) flash fastboot recovery (path of recovery-en-goapk.img). Deleting the stock Android recovery folder most likely left you without any recovery. (Someone correct me if I'm wrong )
Entirely sure NOTHING happens while being plugged in into a computer? Can you get into fastboot at all? When connected via USB, does RSD show your device?
Click to expand...
Click to collapse
The screen will not turn on. Nothing, no moto symbol, nothing. I did cd, I got an interface, fastboot said it was going to install a recovery, but then it failed, and that is the message the phone gave me. I was rooted, because I had superuser. I WAS unlocked,, because it had said unlocked on boot, though not at the time of fastboot, but then I used rsd after I was stuck in boot after trying to install a custom rom. After that it didn't say unlocked, so I unlocked again, and while doing so it said I was already unlocked. I failed to install a custom rom again with the same result, so I rsd'ed again back to 1.2. I never unlocked after that because I figured I didn't need to. I tried to install a custom rom many times with pretty much the same result after trying several different things, including flashing CWM with fastboot. Then I read that I had to re unlock after RSDing, so I was in the process of that when my screen shut off in the middle of it. I assume it didn't have enough charge and died (or that is what it sounds like according to what I have read)
mediocrepiracy said:
The screen will not turn on. Nothing, no moto symbol, nothing. I did cd, I got an interface, fastboot said it was going to install a recovery, but then it failed, and that is the message the phone gave me. I was rooted, because I had superuser. I WAS unlocked,, because it had said unlocked on boot, though not at the time of fastboot, but then I used rsd after I was stuck in boot after trying to install a custom rom. After that it didn't say unlocked, so I unlocked again, and while doing so it said I was already unlocked. I failed to install a custom rom again with the same result, so I rsd'ed again back to 1.2. I never unlocked after that because I figured I didn't need to. I tried to install a custom rom many times with pretty much the same result after trying several different things, including flashing CWM with fastboot. Then I read that I had to re unlock after RSDing, so I was in the process of that when my screen shut off in the middle of it. I assume it didn't have enough charge and died (or that is what it sounds like according to what I have read)
Click to expand...
Click to collapse
sounds like hard brick bro...
You need to find a way to charge your battery. It sounds like your battery is dead. Try to find a someone with the same phone as you.
Sent from my MB860 using XDA Premium App
To charge your battery,
Take ANY USB cable and cut one end of it off.
Strip the outer layer and strip the Black and red wires exposing the wire itself.
Starting with the black wire, tape that end to the NEGATIVE sign on the battery
Then take the red wire and tape it to the POSITIVE side of the battery.
Make sure you check it every few minutes so it does not over heat because it WILL get hot due to no regulations
I would charge it for approximately 30 min or so then put the battery back into your phone and boot it up
AND NO YOU DID NOT HARDBRICK BECAUSE YOU DID NOT HAVE HAVE THE RIGHT CWM IN ORDER TO FLASH THE OTA THAT WOULD CAUSE YOU TO HARDBRICK IF GOING BACKWARDS
ClearFire said:
To charge your battery,
Take ANY USB cable and cut one end of it off.
Strip the outer layer and strip the Black and red wires exposing the wire itself.
Starting with the black wire, tape that end to the NEGATIVE sign on the battery
Then take the red wire and tape it to the POSITIVE side of the battery.
Make sure you check it every few minutes so it does not over heat because it WILL get hot due to no regulations
I would charge it for approximately 30 min or so then put the battery back into your phone and boot it up
AND NO YOU DID NOT HARDBRICK BECAUSE YOU DID NOT HAVE HAVE THE RIGHT CWM IN ORDER TO FLASH THE OTA THAT WOULD CAUSE YOU TO HARDBRICK IF GOING BACKWARDS
Click to expand...
Click to collapse
If this works I will give you many thanks, and my firstborn child.
It didn't work. Walked into an AT&T store and said "It broke, I don't know what to do" and they gave me a new one under manufacturers warranty. I am going to try again, but if someone could point me towards a comprehensive guide that may be able to solve my problems, I would be appreciative.
I figured out my issue with not being able to install custom recovery, it was the fact that I hadn't unlocked again after flashing an sbf. I am now running Aura ROM, and so far I've been geeking out nonstop. Thanks everyone who tried to help me.
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Have you tried to reinstall the motorola driver?
Yes, when I first "lost" RSD support and since the current "Failed to boot 2" message.
It has the flash interface when I plug it in, but the motorola software dosent see it, same with RSD. just like nothing is plugged in.
Why not put it into fastboot mode when it reboots and then flash a different file?
phobos512 said:
Why not put it into fastboot mode when it reboots and then flash a different file?
Click to expand...
Click to collapse
It won't boot into any other mode, upon putting the battery in, it shows the dual core logo for about 1.5-2 seconds that pops up the "Failed to boot 2" message and starting RSD mode.
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ya, from what I can tell its Motorola locking me out for using an modified rom. But I think that I should be able to return to a stock firmware using RSD lite or the Motorola software restore from thier site, but neither see my phone connected. This leads me to belive that somewhere in the process the RSD protocol got messed up. Now I really don't know much, just enough to be dangerous. So if theres anyone that can tell me if I'm even looking the right direction.
And if I am right is there anything I could possibly do?
gjRabbit said:
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Click to expand...
Click to collapse
Hey man, I have the same problem with you.. have you some progress for that..
I find some infor from forum that this kind of hard brick can be solved by using the developping cable to reflash the sbk file, this method is pending at the SBK file is unavailable which is not released out by MOtorola.. I find a one of my friend who is working in MOTO (Tianjing, CHINA) to see my device, I hope he can help me to unbrick my phone.. when i have good news, I'll update it.
Hi all,
first up, after having spent three days going through the forums I've come up empty on a problem I'm currently experiencing. I'm not a complete n00b on this stuff but currently I'm stuck so hopefully someone can help me.
Backstory:
Bell Atrix, with root but a locked bootloader received and successfully installed the OTA 2.3.4 update last week.
I'm in Australia so am running on the Telstra Network. (not in Canada on the Bell).
After the upgrade, I had the problem with 3G+ Data, so started to investigate.
Tried to follow the instructions given here:
(fastboot) 2.3.4 OrangeFR (Jul5: 4.5.2A-11) w/ RAM fix for Intl. unlocked
So, I tried unlocking the bootloader to flash the files mentioned (system.img). Ultimately I've now concluded that I mustn't have unlocked the bootloader successfully.
After system.img had moto-fastbooted across, when booting I currently get the 'famous':
Failed to boot 4
Starting RSD
So, off I went to RSDLite, with the latest install, the latest moto drivers, and armed with the IHOP_Bell.sbf, I thought I'd try RSD'ing that to my phone.
It gave me SUCCESS, but still no fastboot access.
So I tried intl-fix-try1.sbf [inside the IHOP_Bell.rar] with the same results.
Still Failed to Boot 4.
Now, from all the reading it sounds like I need to flash an entire sbf to my phone.
That's OK, but I can't find one that I feel safe dropping on there.
All of the talk is that flashing a Froyo SBF to a phone that has been OTA updated to 2.3.4 is Baaaaaaad (ie hard brick), and the only 2.3.4 available appears to be the ATT one.
Am I missing something incredibly obvious here?
I've been through the pudding thread, and the SBF thread at length but remain none the wiser. Until I can either unlock my bootloader, and have fastboot access, there's not much I can do.
Seems the way to do this is with a full ROM.
Any of you good people out there able to help a fella?
cheers
Sorry, I should also add that I can't seem to get to fastboot either.
When I plug in the phone to USB, green light comes on.
Then, I press power button again, green light is brighhter and it starts the moto screen.
After about 8 sec the Failed to boot 4 message comes up.
So I tried fastboot, power on with vol down button held.
Exactly the same outcome, no fastboot access it seems.
can you get into RSD lite mode by starting up the phone with the volume UP button and power held?
Phalanx7621 said:
can you get into RSD lite mode by starting up the phone with the volume UP button and power held?
Click to expand...
Click to collapse
Thanks for the reply mate.
Whether I hold vol-up during the boot doesn't seem to make a difference - it still boots to:
Failed to Boot 4
Starting RSD Mode
From there though RSDLite (windows 7/latest version/latest moto drivers) does recognise the phone via USB.
I am able to flash that pudding IHOP sbf to the phone (but after doing so it seems to have no effect. I can't get to the next step due to a lack of fastboot access).
So I'm comfortable that I can make an RSD connection from PC to phone, but from there can't seem to make much progress.
Thanks
Just wondering if anyone's got any clues on how to fix this one? I've been quoted $180 to fix but if anyone's happy to do it for less I'll pay... I'm in Australia...
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10