First I unrooted my phone. I downlaoded mini kies. Ran the Froyo update 2.2. Let it reboot my phone, and now it won't load... What should I do??? All it does is keep vibrating, and the keys stay lit. I'm really lost...
well i would forget anything update from samsung myself
and i would ODIN back to 2.1 stock and flash custom ROMs
http://forum.xda-developers.com/showthread.php?t=747335
the third one on this page
and a video that shows what to do
http://martint.net/2010/how-to-use-odin-to-go-back-to-stock-jfd-2/
IM NOT RESPONSIBLE OF WHAT NIGHT HAPPEN TO YOUR PHONE IF SOMETHING DOES GO WRONG!!!
good luck
I just tried installing GreyBlur on my rooted atrix phone with GingerBlur installed..I followed the instructions corrently..When I turned the phone on it boots up..the GreyBlur screen comes up (instead of the At&T welcome screen) and then I see the locked home screen which it doesn't let me do anything..it's like the touch screen isn't responding or something..then it appears as it turns off and it won't light back up when i hit the power button. When I connect it to the computer, my phone makes the notification sound it always makes if its on and connected thru usb. The screen won't come back on..I don't know what to do. When I take the battery out and put it back in, it boots up again and the same thing happens...I don't know what to do..plese help! I need my phone!
Someone please help =( I can't find anything on this issue.
I'm willing to restore to the factory defaults if I have to.
The only thing that i can think of is flash back to 1.26, 1.52, or 1.56 (or .57, whatever it was).
ooor the new 1.83.
I didn't have this problem. Sorry I wasn't any help. Hope you get it fixed.
How do I flash back without having touchscreen functionality on my phone?
mikeabsurd said:
How do I flash back without having touchscreen functionality on my phone?
Click to expand...
Click to collapse
Follow this thread
http://forum.xda-developers.com/showthread.php?t=991072
I flashed back to 1.2.6
and it worked! Thank you guys so much for all your help.
I have no idea what went wrong and why I came across that issue.
I spent an hour looking it up and couldn't find anyone with the same issue
I was wondering if you have any recommendations what I should do now
to get out of my atrix. I'm still interested in greyblur and I wish I could
get it to work.
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...
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?
Dear All,
I need some help here. I have searched the forum and could not find the answer to my problem.
Anyway, I just got the Droid RAZR with Verizon written on the phone.
And I wanted to upgrade to ICS.
So I followed the guide here http://forum.xda-developers.com/showthread.php?t=1786107
My mistake was that I did not check if the phone was from Latam (I didn't know what latam was, later on i figured it was Latin America).
However, when I try to flash Blur_Version.651.167.3370.XT910.Brasil.en.BR.zip , it says the E: file signature failed.
I found out that I need to instal CMW first. However, all the guide for installing CMW needs me to get into the phone to install the .apk.
Right now, I can only get to the AP Fast boot , stock recovery etc (by holding both vol buttons and press power button).
I can't get past the Motorola Dual Core logo.
Anyone might be able to help?
Thanks in advance
A couple ideas, but take them all with a grain of salt...
but you may want to either research fastboot files and RSD lite, or getting Matt's 1.81 utility in the dev section. You may need check some other forums for an active link though. I just had a similar problem, but couldn't even get to the ap fastboot w/out a little trickery.