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!!
Related
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
After flashing the "zomgunlock-lite.sbf" you could have pulled the battery (then put it back in) and without turning it on just plug back into the computer and it would have turned on by itself and given you a menu in which you would have selected fastboot and then entered the commands for unlocking the bootloader.
I'm glad you got yours working and appreciate the info but there is a way out of it. Actually, someone has created an automatic script for just that occasion here:
http://forum.xda-developers.com/showthread.php?t=1182871
Just follow the directions for the error.
ravicus said:
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
Click to expand...
Click to collapse
glad you're phone is ok, but yea you were not hard bricked. You just had to redo the OEM unlock command in fastboot one more time. The hard brick is when trying to downgrade, not from flashing pudding and it takes away the ability to RSD or fastboot. If those options are there then there's a way out.
I think a mod should change title so people aren't getting false hope.
You were soft bricked. Unlocking a stock 2.3.4 phone always results in a 0x1000 No OS error, at which point you are supposed to choose fastboot before the 5 seconds are up (or reboot into fastboot mode if you miss the 5 second window) and run fastboot oem unlock once to get the unique key and then again with the key followed by a fastboot reboot.
I repeat, all unlock attempts on stock 2.3.4 OTA Atrices will result in this temporary soft brick.
This thread really did me a massive favor in telling me exactly what I was searching for when google was being useless. Thank you guys. Particularly the post above mine about soft bricks.
ravicus said:
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
Click to expand...
Click to collapse
Massive n00b post, nothing but misinformation.
Sweet.....
soft brick could be fixed.. my phone is hard one, can not be read by PC.. it is always booting loop.
and blemeIf
I have also hard bricked my Atrix. I have read many post on this forum and on google that phone can not be recovered after hard brick. Is it confirmed that there is no way to recover after a hard bricked? Please help.
mysticdrew said:
glad you're phone is ok, but yea you were not hard bricked. You just had to redo the OEM unlock command in fastboot one more time. The hard brick is when trying to downgrade, not from flashing pudding and it takes away the ability to RSD or fastboot. If those options are there then there's a way out.
I think a mod should change title so people aren't getting false hope.
Click to expand...
Click to collapse
So, i did try to downgrade using RSD lite since nothing seemed to work when i was stuck at the unlocked M screen despite flashing 3 different roms via CWM. Now i get the error message failed to boot 0x1000, but there are no options at all and my phone just goes to black after 1sec. this is considered hard bricked correct? and there is nothing i can do other than send it into motorola
patsprobst said:
So, i did try to downgrade using RSD lite since nothing seemed to work when i was stuck at the unlocked M screen despite flashing 3 different roms via CWM. Now i get the error message failed to boot 0x1000, but there are no options at all and my phone just goes to black after 1sec. this is considered hard bricked correct? and there is nothing i can do other than send it into motorola
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/showthread.php?t=1648947
dcarpenter85 said:
You were soft bricked. Unlocking a stock 2.3.4 phone always results in a 0x1000 No OS error, at which point you are supposed to choose fastboot before the 5 seconds are up (or reboot into fastboot mode if you miss the 5 second window) and run fastboot oem unlock once to get the unique key and then again with the key followed by a fastboot reboot.
I repeat, all unlock attempts on stock 2.3.4 OTA Atrices will result in this temporary soft brick.
Click to expand...
Click to collapse
I can't believe it was so hard to find these particular instructions and that it is not listed anywhere on the sbf file. Thank you so much for your answer and the last sentence should be added to the sbf file. Actually your whole statement should be there. Thanks a lot. Saved me a lot of anguish.
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 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?
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
Just got this phone of ebay. Said it would power on but unable to get past boot up screen. They however didnt tell me there was also an error on screen. It says "Modem did not power up (3). Starting RSD protcol support." Battery too low to flash. So i went to my local radio shack to charge it on there universal charge. so i got the battery too low error to go away and my learning started from there. So i figured out what rsd was, got it and tries flashing an sbf to factory stock hoping the radio software got borked. But with no luck i keep getting the "error to switching phone to bp pass through mode". it will boot up no problem in "boot android (no bp)". so is the radio broke? anyone know how i can get it to get past the error in rsd when flashing an sbf? im really hoping its a software error i can work around but its not looking to bright in my eyes. and it also didnt come with the factory sim card. i was wondering if maybe that could be causing the problem? thanks for any help guys.
help
jump454 said:
Just got this phone of ebay. Said it would power on but unable to get past boot up screen. They however didnt tell me there was also an error on screen. It says "Modem did not power up (3). Starting RSD protcol support." Battery too low to flash. So i went to my local radio shack to charge it on there universal charge. so i got the battery too low error to go away and my learning started from there. So i figured out what rsd was, got it and tries flashing an sbf to factory stock hoping the radio software got borked. But with no luck i keep getting the "error to switching phone to bp pass through mode". it will boot up no problem in "boot android (no bp)". so is the radio broke? anyone know how i can get it to get past the error in rsd when flashing an sbf? im really hoping its a software error i can work around but its not looking to bright in my eyes. and it also didnt come with the factory sim card. i was wondering if maybe that could be causing the problem? thanks for any help guys.
Click to expand...
Click to collapse
i have same problem too. who have any ideas? please help us
i dropped it (with the case still on it)and when i picked it up it reset by itself and when it did that it wouldn't leave the Motorola screen it just said couldn't start modem (3) and starting rsd protocol support. so every time it starts up it does that
Modem did not power up DRIVING ME NUTs
Thanks