Related
Hey i have At&t Motorola Atrix, i Want to unlock my boot loader. My phone is running 2.3.4(OTA), webtop version 1.2.0-110,build number 4.5.91 and kernel 2.6.32.9 and more over i rooted my phone . i read so many threads and in the end im so confused and i dont know from where to start. can you help me ?
http://forum.xda-developers.com/showthread.php?t=1202883
Sent from my MB860 using XDA App
im getting error when i click on start button it says failed to flash
You cannot get all the info you need in one post, search through the thread and look to see if anyone else is having your issue.
Here is another thread that offer up some links that might help too.
http://forum.xda-developers.com/showthread.php?t=1154600
You will have to read a little bit. It would take a very long time for someone to compile a tutorial that would include all the variables that might be relative to this phone.
usman.daud said:
im getting error when i click on start button it says failed to flash
Click to expand...
Click to collapse
usman.daud said:
Hey i have At&t Motorola Atrix, i Want to unlock my boot loader. My phone is running 2.3.4(OTA), webtop version 1.2.0-110,build number 4.5.91 and kernel 2.6.32.9 and more over i rooted my phone . i read so many threads and in the end im so confused and i dont know from where to start. can you help me ?
Click to expand...
Click to collapse
I can confirm that flashing the latest sbf from pudding will work on 2.3.4 OTA, using RSD lite. After flashing the sbf, you will get a 0x1000 cannot boot message, but don't worry, its not a real hard brick. When that message pops up, IMMEDIATELY go into fastboot and type "fastboot oem unlock" and you will not be bricked, and you will be unlocked. I performed this on my 2.3.4 OTA atrix yesterday, without any problems.
where u get latest Sbf file ? when i click start for flashing it gave error that flashing process failed
and also have u tired any custom rom ? and how was the experience
http://forum.xda-developers.com/showthread.php?t=1182526
use that sbf file. it works on 2.3.4 OTA.
read through the thread - it will explain well what to expect, explain the soft brick issue and how to remedy it, and also what you need to have in advance for it to all work smoothly.
MY RSD give error. when i entered in RSd support rsdlite show it connected when i start sbf flashing it give error that flashing process failed.0x7027 phone cant retrieve any help with that ?.
try using this version of RSDLite. It worked for me with this one.
http://forum.gsmhosting.com/vbb/archive/t-1229831.html
im previously on 5.3.1 is safe to use a downgraded version
yeah.
its just a different version of the pc software. downgrading is only a problem if you're downgrading phone software but this is ok.
not working
Same error? Did you check that the drivers installed correctly? Try a reboot on pc and use a different usb port
I am reviewing PUDDING information to unlock the bootloader and I have some concerns.
PUDDING Link: http://forum.xda-developers.com/showthread.php?t=1136261
1. This guide posted in PUDDING says your phone must register as NS Flash Olympus and mine is registering (now) as SE Flash Olympus. Why is that? My phone "used" to register as NS Flash Olympus but no longer does and I am concern with any "issues" that may arise in RSD Lite due to that discrepancy.
Is there any way to get my phone to register back as NS Flash Olympus? Does it matter?
Guide: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
2. I see this post regarding my situation from OTA Gingerbread (official, not the beta that was easily unlocked via the guide) to unlocking the Bootloader via PUDDING:
http://forum.xda-developers.com/showpost.php?p=15953305&postcount=362
While it seems that people are getting by this fine, with my first issue I am skeptical and I also saw this thread that made me a bit more weary of the situation and hard bricking:
http://forum.xda-developers.com/showthread.php?t=1165154
Is this something I should be concerned or worried about? The only note in that thread that concerned me was "If you managed to un-brick:" section.
System Version: 4.5.91.MB860.ATT.en.US
Android Version: 2.3.4
Rooted: No
Please, save yourself time. If you just plan on being rude, flaming, etc...I don't care. I am just attempting to ensure I don't hard brick and the guides do not match exact specs in my situation. If I had a "fraction" of the time available to investigate, work, test, etc I wouldn't be here.
I used this on the official OTA and it worked perfectly: http://forum.xda-developers.com/showthread.php?t=1182871
I had the soft brick error as was to be expected, but just put the phone in fastboot mode and chose option 3 to fix it.
It did reset /data for me unfortunately, so I had to re-setup and reinstall my apps.
jkrohn said:
I used this on the official OTA and it worked perfectly: http://forum.xda-developers.com/showthread.php?t=1182871
I had the soft brick error as was to be expected, but just put the phone in fastboot mode and chose option 3 to fix it.
It did reset /data for me unfortunately, so I had to re-setup and reinstall my apps.
Click to expand...
Click to collapse
Did you share the same problem as my concern #1?
Never even checked to be honest. I had used RSD to flash a few SBFs in the past though for this atrix, so I was not concerned.
Well, in short...I just used the method you posted above -
http://forum.xda-developers.com/showpost.php?p=16520624&postcount=2
Worked just fine. No brick, safe and sound... I really do appreciate the extra info I somehow missed looking around for.
That's it! You just made me realize my problem. After my official update back to stock my phone comes up se flash not nf flash and it does not allow rsdlite or the moto software upgrade to see my phone when connected to pc hence I am unable to unlock again. Please post back if unlock is successful. I am betting its not while coming up se flash but maybe I am wrong.
Sent from my MB860 using Tapatalk
I have a Moto Photon that I have had for about a year (since the phone was first released). Shortly after getting the phone I rooted it, but I have not (up to this point) felt the need to load an alternate ROM. (I had several Android phones before this one, such as a Droid 1 and Droid Incredible, and had CM ROMs loaded on those, but I was OK with the speed or the Nvidia CPU and the stock OK that was loaded on it when I got the phone.) I got impatient waiting for Moto to release the ICS update for Photon (it's now been about a year since ICS was released, and JB is now out), so I decided to try unlocking the bootloader and loading a new ROM. I have however had quite a bit of trouble with the bootloader unlock process.
When I try to do the standard Pudding bootloader unlock process, I get the following errors...
- When I use RSDLite to flash the derpunlock.sbf file, I get an error "flash failed". I get this no matter how many times I try.
(I'm not sure if this is normal, but if it is, it would have been great if someone mentioned that in the doc.)
- After the attempts (above) to flash the derpunlock.sbf file, when I reboot the phone, I do see "unlocked" in the upper left corner of the screen.
(I read somewhere on another forum post that the bootloader is not really unlocked at that point.)
- When I then try to use fastboot to do the "oem unlock" operation, I get the error "phone already unlocked".
(Again, I'm not sure if this is normal, but if it is, it would have been great if someone mentioned that in the doc.)
After doing the steps above, I have been able to use fastboot flash the CWM recovery (version 5.0.2.8). That worked fine, and I had no trouble booting into recover and doing a factory reset the phone.
After flashing CWM recovery tried loading both the Joker ICS and the Miui 4 ROMs for Photon, but in both cases when the phone boots with the new ROM I got an error that an Android service failed to start, and the Android "phone" features (being able to call or connect to a mobile network) didn't work. (I suspect this is due to an issue with the unlocking process, but I don't know.)
At this point I tried reloading the stock Blur ROM (Sunfire 198_7) and doing the root/unlock process over again from scratch, but when I did that I was now not able to even get any CM9 or Miui ROMs I loaded to boot.
I reloaded a backup of the rooted stock ROM (Sunfire 198_7), and that booted ok. I also tied loading the latest nightly build of CM7 (from the Cyanogen site), and that booted OK.
After doing that, I again tried loading a couple of different builds of the Jokersax CM9 ROM (as well as again trying to load the latest build of the Miui ROM), but the phone won't boot with any of these ROMs. (It just hangs at the Motorola Dual Core Technology logo screen.)
I would really like to load an ICS based ROM. Can any suggest a way I can get beyond these issues?
Thanks.
- mediawiz -
NOTE: I also tried the following...
After doing all of the steps listed above, I tried using RSDLite to flash a stock Moto ROM image (the Sunfire 198_7 SBF file), and did the root/unlock/flash CWM process over again from scratch, but had the same results. (ie: I can get any ROM based on Android 4.0 to boot. Only ROMs based on Android 2.3.x.)
After doing I thought that perhaps the unlock process had to be applied to an earlier version of the stock ROM. I tried using RSDLite to flash a the Sunfire 198_7 SBF file, and did the root/unlock/flash CWM process over again from scratch, but again had the same results. (ie: I can get any ROM based on Android 4.0 to boot. Only ROMs based on Android 2.3.x.)
Suggestions???
If you can't do it the easy way, make it more complicated
If it writes that it was already unlocked, why don't you believe that? You cannot be more unlocked, than you already are.
Those problems with phone on ics roms are nothing unknown, that is normal and you need to do few more steps. It was already mentioned many times all over here. I am not using ics rom, so I cannot help you more.
Why are you posting this in development section?
mediawiz said:
- After the attempts (above) to flash the derpunlock.sbf file, when I reboot the phone, I do see "unlocked" in the upper left corner of the screen.
(I read somewhere on another forum post that the bootloader is not really unlocked at that point.)
After doing the steps above, I have been able to use fastboot flash the CWM recovery (version 5.0.2.8). That worked fine, and I had no trouble booting into recover and doing a factory reset the phone.
Click to expand...
Click to collapse
You cannot be unlocked more than that It says you are already unlocked, so what do you want from it?
The problem is you are using CWM v 5.0.2.8, but to flash jokers CM9 and all the ICS roms based on it you should be using CWM v 5.5.0.4
Just flash the attached .zip from your current (5.0.2.8) CWM, and it will be updated to the latest version (5.5.0.4), and you will be able to flash ICS-based roms.
Simple as that.
And all this stuff doesnt belong to the dev thread. You have Q\A forums for it.
Thank you so much for your help!
moto photon root/ boot loading problems (permission denied)
i believe this belongs in the dev. section but seeing as i am a new member i am not allowed to post there.
i am having a lot of trouble rooting my moto photon 4g in any way shape or form. the most rescent script i have tried is xda's cm9 one click root.
script reads.
* daemon not running. starting it now *
*daemon started successfully *
Getting temp root
Re-boot-en
Hackin Things
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
cannot create /data/local.prop: permission denied
deleting all yo sh*t
remount failed: Operation not permitted
381 kb/s (4292 bytes in 0.011s)
in usb debugging mode and in charge only setting, any ideas?
Killer...
For rooting, this is what worked for me.
http://forum.xda-developers.com/showthread.php?p=28790312
Success has been reported in post 15 of the same thread. Also, check out the stickys, particularly "Read Here First. All things MoPho". The best info is kept there.
Good luck!
Sent from my MB855 using xda premium
mediawiz said:
I have a Moto Photon that I have had for about a year (since the phone was first released). Shortly after getting the phone I rooted it, but I have not (up to this point) felt the need to load an alternate ROM. (I had several Android phones before this one, such as a Droid 1 and Droid Incredible, and had CM ROMs loaded on those, but I was OK with the speed or the Nvidia CPU and the stock OK that was loaded on it when I got the phone.) I got impatient waiting for Moto to release the ICS update for Photon (it's now been about a year since ICS was released, and JB is now out), so I decided to try unlocking the bootloader and loading a new ROM. I have however had quite a bit of trouble with the bootloader unlock process.
When I try to do the standard Pudding bootloader unlock process, I get the following errors...
- When I use RSDLite to flash the derpunlock.sbf file, I get an error "flash failed". I get this no matter how many times I try.
(I'm not sure if this is normal, but if it is, it would have been great if someone mentioned that in the doc.)
- After the attempts (above) to flash the derpunlock.sbf file, when I reboot the phone, I do see "unlocked" in the upper left corner of the screen.
(I read somewhere on another forum post that the bootloader is not really unlocked at that point.)
- When I then try to use fastboot to do the "oem unlock" operation, I get the error "phone already unlocked".
(Again, I'm not sure if this is normal, but if it is, it would have been great if someone mentioned that in the doc.)
After doing the steps above, I have been able to use fastboot flash the CWM recovery (version 5.0.2.8). That worked fine, and I had no trouble booting into recover and doing a factory reset the phone.
After flashing CWM recovery tried loading both the Joker ICS and the Miui 4 ROMs for Photon, but in both cases when the phone boots with the new ROM I got an error that an Android service failed to start, and the Android "phone" features (being able to call or connect to a mobile network) didn't work. (I suspect this is due to an issue with the unlocking process, but I don't know.)
At this point I tried reloading the stock Blur ROM (Sunfire 198_7) and doing the root/unlock process over again from scratch, but when I did that I was now not able to even get any CM9 or Miui ROMs I loaded to boot.
I reloaded a backup of the rooted stock ROM (Sunfire 198_7), and that booted ok. I also tied loading the latest nightly build of CM7 (from the Cyanogen site), and that booted OK.
After doing that, I again tried loading a couple of different builds of the Jokersax CM9 ROM (as well as again trying to load the latest build of the Miui ROM), but the phone won't boot with any of these ROMs. (It just hangs at the Motorola Dual Core Technology logo screen.)
I would really like to load an ICS based ROM. Can any suggest a way I can get beyond these issues?
Thanks.
- mediawiz -
Click to expand...
Click to collapse
the force close is caused by the radio being put it a mode that's not cdma. flash the 0.3.1 of cm9 first. boot up the os. reboot to recovery and flash the latest + gapps. done. or you could also go into the dialer press *#*#info#*#* go to phone information. in network menu select cdma auto prl. easy as that. and the recovery you figured out was wrong. read up next time! all the info is around in one simple place. try using the search button! :silly: and be specific when searching.
JohnH4 said:
Killer...
For rooting, this is what worked for me.
http://forum.xda-developers.com/showthread.php?p=28790312
Success has been reported in post 15 of the same thread. Also, check out the stickys, particularly "Read Here First. All things MoPho". The best info is kept there.
Good luck!
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I was able to manually root my phone using torpedo through DOS. now i am having a lot of trouble unlocking my bootloader. rds lite seems to not be working properly. it seems to install very fast, sit at 100% and then fail. it never says that it is unlocked, when i try to finish the unlock in dos it says that the INFOOEM unlock is not implemented....plz help
killerz0125 said:
I was able to manually root my phone using torpedo through DOS. now i am having a lot of trouble unlocking my bootloader. rds lite seems to not be working properly. it seems to install very fast, sit at 100% and then fail. it never says that it is unlocked, when i try to finish the unlock in dos it says that the INFOOEM unlock is not implemented....plz help
Click to expand...
Click to collapse
i was wondering if this is attributed to the fact that this is a new mopho with android 2.3.5???
RSD Lite 5.7 multi-flash status:
Phone [0000]: Waiting for re-enumeration.
failed flashing process. phone[0000]: Phone did not re-enumerate after RAM-downloader was sent. (0x703E)
phone reads:
svf:106:1:2
sec_exception: b655, eddc, eb
killerz0125 said:
i was wondering if this is attributed to the fact that this is a new mopho with android 2.3.5???
RSD Lite 5.7 multi-flash status:
Phone [0000]: Waiting for re-enumeration.
failed flashing process. phone[0000]: Phone did not re-enumerate after RAM-downloader was sent. (0x703E)
phone reads:
svf:106:1:2
sec_exception: b655, eddc, eb
Click to expand...
Click to collapse
2.3.5 cant be unlocked as far as i know
Is anyone working on a way to unlock the boot loader for 2.3.5. I haven't heard of anyone doing it out finding a work around. Can you down grade back to 2.3.4 thanks
You cannot downgrade and being that the bootloader is configured completely different could be a while before you see any unlock.
Sent from my MB855 using xda app-developers app
ajandrew1991 said:
Is anyone working on a way to unlock the boot loader for 2.3.5. I haven't heard of anyone doing it out finding a work around. Can you down grade back to 2.3.4 thanks
Click to expand...
Click to collapse
Check out this thread. It explains the 2.35 bootloader problem and whats being done about it. http://forum.xda-developers.com/showthread.php?t=1650520
Sent from my MB855 using xda premium
JohnH4 said:
Check out this thread. It explains the 2.35 bootloader problem and whats being done about it. http://forum.xda-developers.com/showthread.php?t=1650520
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Thanks that helped. Just doesn't look like anyone is still working on it
Because it's useless...
peetr_ said:
Because it's useless...
Click to expand...
Click to collapse
Lmaoooo
Sent from my MB855 using xda premium
My Photon 4G is keeping rebooting when trying to prepare the internal storage.
I tried the following solutions without success:
Reset to factory
flashed "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM-release-keys-signed-Sprint-US.sbf" using RSD, an error raised:
On phone screen: SVF: 106:1:2
sec_exception: b655, eddc, eb
On RSD Status: Phone[0000]: Waiting for re-enumeration
On RSD Status: Phone did not re-eumerate after RAM-downloader was sent. (0x703E)
flashed "1FF-sunfire-userdebug-2.3.5-4.5.1A-1_SUN-385-307-test-keys-Sprint-US.sbf" using RSD, an error raised:
On phone screen: sec_exception: febe, 4e, 4e
On RSD Status: Phone[0000]: Waiting for re-enumeration
On RSD Status: Phone did not re-enumerate after RAM-downloader was sent. (0x703E)
please your help.
The factory reset worked with no problems? Did you try to erase data via fastboot?
Try to use other computer with other OS. It might solve the problem sometimes.
yairku said:
The factory reset worked with no problems? Did you try to erase data via fastboot?
Try to use other computer with other OS. It might solve the problem sometimes.
Click to expand...
Click to collapse
Thank you for your help.
I tried to reset using fastboot but it didn't solve the issue. I also tried another PC [my pc and the other pc are running windows 7] but same issue.
Is the issue related to OS?
fhuwaidy said:
Thank you for your help.
I tried to reset using fastboot but it didn't solve the issue. I also tried another PC [my pc and the other pc are running windows 7] but same issue.
Is the issue related to OS?
Click to expand...
Click to collapse
Doing my best, but I'm still not an expert.
I think it's not related to OS. I just thought that you should try other computer, that may have all required drivers. But it looks like it doesn't help.
The second SBF you mentioned could probably lock your bootloader forever, and you shan't have tried it, unless you want stock 2.3.5 . Moreover, I read somewhere that this file is not signed, and that could make problems with flashing too.
I can't tell what the problem is, since I don't have much experience, but I'd say that the problem may happen due to missing drivers or maybe the files you try to flash are bad. Where did you get them? Did you get any notifications from windows about downloading new drivers during the flash process? Can you get a normal 198_7 SBF and try to flash it? Take one from here. I didn't try it but it looks good. Just unzip it and flash (I'm not responsible for any brick). And Please, make sure your battery is full. It's important.
Hope this helps! Otherwise, I'm sorry, but I have no idea.
yairku said:
Doing my best, but I'm still not an expert.
I think it's not related to OS. I just thought that you should try other computer, that may have all required drivers. But it looks like it doesn't help.
The second SBF you mentioned could probably lock your bootloader forever, and you shan't have tried it, unless you want stock 2.3.5 . Moreover, I read somewhere that this file is not signed, and that could make problems with flashing too.
I can't tell what the problem is, since I don't have much experience, but I'd say that the problem may happen due to missing drivers or maybe the files you try to flash are bad. Where did you get them? Did you get any notifications from windows about downloading new drivers during the flash process? Can you get a normal 198_7 SBF and try to flash it? Take one from ***1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf.gz. I didn't try it but it looks good. Just unzip it and flash (I'm not responsible for any brick). And Please, make sure your battery is full. It's important.
Hope this helps! Otherwise, I'm sorry, but I have no idea.
Click to expand...
Click to collapse
Thank you for your help.
I tried to flash this SBF using RSD but again sec_exception is raised.
I want to raise something here, before the phone got this issue, I've updated the android using OTA and I'm not sure what that update was. Maybe the update upgraded the android to 2.3.5 so the RSD flash is maintaining as downgrade so it fail.
Please your help. Thanks
Hi
What build did you have before you applied the OTA update? When have you got the update?
I'm sure that there are more experienced users here that have better ways to tell what build you have, but I don't know any better ways.
The issue raised just after the applying the OTA update or when?
Lots of people face problems of random reboots after downloading the new OTA. Maybe you have a problem like this, but not random. I think that the best thing to do is to flash the official 2.3.5 SBF. The one that you tried to flash is not signed and was made for tests, and that seems to be the reason why you can't flash it. Please answer the questions, and hope to find a signed SBF somewhere, soon.
Edit: Looked into this thread, and as I understand you have a way out. But first we should make sure you have a 2.3.5 build. Otherwise, it won't be a wise step to flash Electrify's 2.3.5 SBF.
Anyhow I sent a PM to peetr_ to have a professional advice.
fhuwaidy said:
My Photon 4G is keeping rebooting when trying to prepare the internal storage.
I tried the following solutions without success:
Reset to factory
flashed "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM-release-keys-signed-Sprint-US.sbf" using RSD, an error raised:
On phone screen: SVF: 106:1:2
sec_exception: b655, eddc, eb
On RSD Status: Phone[0000]: Waiting for re-enumeration
On RSD Status: Phone did not re-eumerate after RAM-downloader was sent. (0x703E)
flashed "1FF-sunfire-userdebug-2.3.5-4.5.1A-1_SUN-385-307-test-keys-Sprint-US.sbf" using RSD, an error raised:
On phone screen: sec_exception: febe, 4e, 4e
On RSD Status: Phone[0000]: Waiting for re-enumeration
On RSD Status: Phone did not re-enumerate after RAM-downloader was sent. (0x703E)
please your help.
Click to expand...
Click to collapse
I would also suggest the same as above. If you are on 2.3.5 (OTA) 254_23, flash 254_13 sbf of electrify.
Well, Peetr_ answered my questions, and now I'm sure about your next steps.
1)Flash this SBF. Now you'll have stock 2.3.5 for Electrify. But you need Sprint services (I assume), so you don't stop here.
2) Download bootstrap from Google Play, and get it working. Of course you need to root your photon first.
3) Flash this ROM from bootstrap. I think that this is the only custom ROM that supports Sprint services, so you need it. Please follow the instructions for this ROM carefully, you don't wanna flash the SBF again.
4) Flash 254_13 modules with bootstrap. you need them.
5) Flash 2.3.5_254_13 sv2 boot, recovery and cdrom image sbf with RSD Lite.
6) Flash 254_12 libmoto_ril.so with bootstrap. You don't need to flash the radio SBF. That's what Peetr_ told me.
That's it. You have a locked bootloader, but you're able to use your Photon.
Have fun!
yairku said:
Well, Peetr_ answered my questions, and now I'm sure about your next steps.
1)Flash this SBF. Now you'll have stock 2.3.5 for Electrify. But you need Sprint services (I assume), so you don't stop here.
2) Download bootstrap from Google Play, and get it working. Of course you need to root your photon first.
3) Flash this ROM from bootstrap. I think that this is the only custom ROM that supports Sprint services, so you need it. Please follow the instructions for this ROM carefully, you don't wanna flash the SBF again.
4) Flash 254_13 modules with bootstrap. you need them.
5) Flash 2.3.5_254_13 sv2 boot, recovery and cdrom image sbf with RSD Lite.
6) Flash 254_12 libmoto_ril.so with bootstrap. You don't need to flash the radio SBF. That's what Peetr_ told me.
That's it. You have a locked bootloader, but you're able to use your Photon.
Have fun!
Click to expand...
Click to collapse
Thank you yairku and also for Peetr_ for your professional help.
I tried to flash the mentioned SBF and it was flashed successfully, but my issue still exists and the phone keep rebooting when trying to initialize the internal storage.
I believe that the issue may be hardware issue. Is there a tool or something to get the phone log using fastboot?
What do you mean by initialization of internal storage? You mean mounting internal sd after boot? Or something different? Internal data partition? When does it happen? Or do you mean mounting internal sd in usb mass storage mode?
peetr_ said:
What do you mean by initialization of internal storage? You mean mounting internal sd after boot? Or something different? Internal data partition? When does it happen? Or do you mean mounting internal sd in usb mass storage mode?
Click to expand...
Click to collapse
Thank you Peetr_ for instant reply.
I meant mounting internal sd after boot and it happened after the splash screen of US.Cellular.
Did you try to format it in bootstrap recovery?
But you cannot install it probably, if it keeps rebooting.
Try to boot in usb early enumeration mode (vol. down + power).
But most probably this has nothing with sd card, but radio.
Try flashing 2.3.5 sv2 198_7 radio sbf from 2.3.5 sv2 custom sbf thread.
peetr_ said:
Did you try to format it in bootstrap recovery?
But you cannot install it probably, if it keeps rebooting.
Try to boot in usb early enumeration mode (vol. down + power).
But most probably this has nothing with sd card, but radio.
Try flashing 2.3.5 sv2 198_7 radio sbf from 2.3.5 sv2 custom sbf thread.
Click to expand...
Click to collapse
Thank you Peetr_.
I tried all mentioned options(USB early enumeration, flashed the radio SPF file) but my issue still
yairku said:
Well, Peetr_ answered my questions, and now I'm sure about your next steps.
1)Flash this SBF. Now you'll have stock 2.3.5 for Electrify. But you need Sprint services (I assume), so you don't stop here.
2) Download bootstrap from Google Play, and get it working. Of course you need to root your photon first.
3) Flash this ROM from bootstrap. I think that this is the only custom ROM that supports Sprint services, so you need it. Please follow the instructions for this ROM carefully, you don't wanna flash the SBF again.
4) Flash 254_13 modules with bootstrap. you need them.
5) Flash 2.3.5_254_13 sv2 boot, recovery and cdrom image sbf with RSD Lite.
6) Flash 254_12 libmoto_ril.so with bootstrap. You don't need to flash the radio SBF. That's what Peetr_ told me.
That's it. You have a locked bootloader, but you're able to use your Photon.
Have fun!
Click to expand...
Click to collapse
Ok, trying to follow your smart tuto, but stuck at root, do i need to have unlocked bootloader in order to obtain root access ? what procedure you followed to get your phone rooted ?
---------- Post added at 08:19 AM ---------- Previous post was at 07:35 AM ----------
Ok, phone rooted with this procedure
http://forum.xda-developers.com/showthread.php?t=1216131
now following next procedure....
fhuwaidy said:
Thank you Peetr_.
I tried all mentioned options(USB early enumeration, flashed the radio SPF file) but my issue still
Click to expand...
Click to collapse
First of all, don't even think of opening the screws of your Photon! That will completely void the warranty that Motorola gives to its customers!
When this issue started? If you opened your photon or dropped it, there might be a hardware problem. The thing that holds the SIM card and the Micro SD card mightn't be in its place. When I opened my Photon it couldn't finish booting, and the reason was that I opened it while the cards were still on their places. Opening the Photon this way made that thing move and that prevented my Photon from finishing the boot process.
So please tell us, when you started to face that issue?
Motorola covers its customers with warranty for a year after purchase. You can send your device for a free fix if it doesn't show "unlocked" when you boot it, and if you didn't remove the seal from the screws.
I have faced the same earlier and this solution worked for me,
1)press the power button and volume down, by using volume down button go to the Android recovery.
2)press volume up to enter the recovery,,if you see the triangle symbol press both volume up and down at the same time after that it will enter in to the recovery.
3)wipe data, cache in the recovery and reboot, it will be fixed.
Sent from my e1809c_v75_jbl_5647 using xda app-developers app
I'm having a similar problem where I can't get service. I followed the steps posted by yairku. Looking through this post, I see some people have posted their specs. When I look at mine, I don't see a Baseband version listed. Not sure if that makes a difference?
System version: 45.4.13.MB855.Sprint.en.US
Model number: MB855
Android version: 2.3.5
Baseband version: Unknown
Webtop version: WT-1.2.0-131_6
Kernal: 2.6.32.9 [email protected] #2
Build number: 4.5.1A-1_SUN-254_13
ERI version: Unknown
PRL version: Unknown
I’m stuck in a rut. I got a Motorola Atrix 4G (AT&T) last week and was trying to unlock it using the following instructions: http://wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Full_Update_Guide#Unlocking_the_Bootloader
I installed RSD Lite 5.7, the Motorola Drivers, and downloaded the unlockable bootloader. I got to step 12, and then everything quickly went downhill. I got stuck on the horrid “Failed to boot 0x1000” screen, along with the list of options. I have tried booting into RSD, running RSD Lite, and loading the bootloader, but I get a “Device Interface” prompt…not exactly sure of the wording at the moment. I drained the battery last week messing with it, and had to buy a standalone charger (which I just received today).
I am not sure of the Android version/firmware version that was on the phone prior to doing this. I know, mistake #1.
My computer is recognizing the Atrix, but the RSD Lite is not able to install the unlockable bootloader (listed on the above site). I have downloaded one “Stock Restore” MFBSR.zip (I can’t seem to find the link to the thread) but this was not able to fix the problem. It recognized my device, but the Atrix wouldn’t accept any of the commands.
I am not sure of what to do, short of calling Motorola and trying to get them to help. I’m sure they would either want to replace it (charging me) or just basically tell me I’m SOL.
I wanted to try FruitCake’s recovery tool, and found the following thread, which has mirror links of some of the files:
http://forum.xda-developers.com/showthread.php?p=24472332#post24472332
I have no clue as to what I would use, so I haven’t even tried downloading one of them. I’m seriously at my wit’s end..I have been Googling and trying to avoid making a post about this. Any help is greatly appreciated. I am about to try the following directions:
http://forum.xda-developers.com/showpost.php?p=19986512&post=234
Also probably important to note that I tried unlocking it using Fastboot, but it was "Waiting for device" for forever and did nothing. When I try to go into Recovery, it says Magic Value Mismatch.
Thanks guys.
http://forum.xda-developers.com/showthread.php?t=1857099
Try! Good Luck!
maggedo said:
I was stuck on the Moto Dual Core Screen as well. I used the automatic unlock MAIN program to unlock, root and install custom recovery. When I tried to flash epinter's CM10 ROM I got boot hang at the Moto screen.
You can RSD back to stock (e.g. I found the AT&T .151 sbf file and restored my phone to working condition on 2.3.6 GB).
In the end I figured out that the recovery in the auto unlock tool (both the telfar and CWM options) was borking the CM10 flash. I ended up:
1. RSD lite AT&T .151 GB 2.3.6 sbf file
2. Unlock Bootloader with automatic unlock
3. Root and install custom recovery
4. Boot into android
5. download goo.manager from play store
6. Install open source recovery with goo.manager
7. reboot into recovery
8. Make backup of everything
9. Flash JB CM10 & GApps
Phone is up and running w/o issues. A bit of googling should find you the necessary sbf to get you on your feet again.
Good luck!
Click to expand...
Click to collapse
I am trying this...but when I am in RSD Lite, it says "Failed Flashing Process: Unable to retrieve interface handle (0x7027)". It does detect my device before this, saying Port Type: USB, IMEI/ESN/MEID: NA, and Status: Connected...
Please help!
KokoATL said:
I am trying this...but when I am in RSD Lite, it says "Failed Flashing Process: Unable to retrieve interface handle (0x7027)". It does detect my device before this, saying Port Type: USB, IMEI/ESN/MEID: NA, and Status: Connected...
Please help!
Click to expand...
Click to collapse
http<delete>://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Go there and unlock your bootloader first.
Then flash the sbf above on post#2 again.
have u solve your problem?
Sent from my MB860 using xda premium
maggedo_defy said:
http<delete>://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Go there and unlock your bootloader first.
Then flash the sbf above on post#2 again.
Click to expand...
Click to collapse
He can't. Fastboot doesn't respond. Also he can't flash any SBF, everything fails.
Looks more like a hard brick to me...
Perhaps... (option number 3)
http://forum.xda-developers.com/showthread.php?t=1182871
soft bricked
KokoATL said:
I’m stuck in a rut. I got a Motorola Atrix 4G (AT&T) last week and was trying to unlock it using the following instructions: http://wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Full_Update_Guide#Unlocking_the_Bootloader
I installed RSD Lite 5.7, the Motorola Drivers, and downloaded the unlockable bootloader. I got to step 12, and then everything quickly went downhill. I got stuck on the horrid “Failed to boot 0x1000” screen, along with the list of options. I have tried booting into RSD, running RSD Lite, and loading the bootloader, but I get a “Device Interface” prompt…not exactly sure of the wording at the moment. I drained the battery last week messing with it, and had to buy a standalone charger (which I just received today).
I am not sure of the Android version/firmware version that was on the phone prior to doing this. I know, mistake #1.
My computer is recognizing the Atrix, but the RSD Lite is not able to install the unlockable bootloader (listed on the above site). I have downloaded one “Stock Restore” MFBSR.zip (I can’t seem to find the link to the thread) but this was not able to fix the problem. It recognized my device, but the Atrix wouldn’t accept any of the commands.
I am not sure of what to do, short of calling Motorola and trying to get them to help. I’m sure they would either want to replace it (charging me) or just basically tell me I’m SOL.
I wanted to try FruitCake’s recovery tool, and found the following thread, which has mirror links of some of the files:
http://forum.xda-developers.com/showthread.php?p=24472332#post24472332
I have no clue as to what I would use, so I haven’t even tried downloading one of them. I’m seriously at my wit’s end..I have been Googling and trying to avoid making a post about this. Any help is greatly appreciated. I am about to try the following directions:
http://forum.xda-developers.com/showpost.php?p=19986512&post=234
Also probably important to note that I tried unlocking it using Fastboot, but it was "Waiting for device" for forever and did nothing. When I try to go into Recovery, it says Magic Value Mismatch.
Thanks guys.
Click to expand...
Click to collapse
Did the same to mine about 5hr 's ago, but i found These SBF files (https://sites.google.com/site/motosbf/atrix-sbf-files ) found the one i was running ,booted the phone into RSD mode again and ran it in RSD Lite ,took a while about 30mins but it worked .
hope this works for you