********************************************UPDATE01/17/12***************************************************************************
Allrighty then finally found a fix that is 10x easier to fix ur 4g/lte
1)Unlock bootloader
2)download RSD v5.4.4 and MZ602 .SBF files from my dropbox below
3)use RSD to flash back to stock 3.2.2 should be back and baseband should allow it be shown if not just do a factory reset and after boot up, it should be fixed!!!
BOOTLOADER 1.50
http://dl.dropbox.com/u/47975216/LTE-Baseband.zip
MZ602 .SBF 3g/4g BASEBAND STOCK FIX use the latest RSD v5
http://dl.dropbox.com/u/47975216/VZ...00_03.1A.54_signed_LTEDC_U_05.19.00.combo.rar
RSD VERSION 5.4.4
http://dl.dropbox.com/u/47975216/RSDLite 5.4.4.msi
if baseband does not show go into settings privacy and do a factory reset should fix xoom back to 3.2.2 with radio working
"Its one thing to thank somebody just hit the button and make it a true thank you!"
Thanks a lot!!!
BTW, stuck on the "Starting LTE (USB2) Software Bypass Mode"
ended up RSD says "Phone disconnected"
my Xoom managed to boot though but it doesn't seem to help flash the baseband
Do you flash the bootloader ZIP in ClockworkMod or stock recovery? I would assume stock recovery since the updater script uses a motorola flash function that I would assume is not built into ClockworkMod.
oldblue910 said:
Do you flash the bootloader ZIP in ClockworkMod or stock recovery? I would assume stock recovery since the updater script uses a motorola flash function that I would assume is not built into ClockworkMod.
Click to expand...
Click to collapse
My bootloader is actually v1.50 so there is no need to flash it
Yes but there may be in the future, thus the question.
I would reccomend to just reflash anyways even if your bootloader is at 1.5, I only did this because I flashed 1.35 everest when I f'ed up my xoom from the start
That's my point. So how do you flash it? ClockworkMod or stock recovery? Given that the update script uses some kind of Motorola function to flash the bootloader, I'm assuming stock since I doubt ClockworkMod has Motorola functions built into it. On the off chance that I'm wrong though, can someone verify?
Sent from my Xoom using Tapatalk
oldblue910 said:
That's my point. So how do you flash it? ClockworkMod or stock recovery? Given that the update script uses some kind of Motorola function to flash the bootloader, I'm assuming stock since I doubt ClockworkMod has Motorola functions built into it. On the off chance that I'm wrong though, can someone verify?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Hey bro just give some time I'll make a in depth tutorial seems like you your going to have to flash back to 3.0 flash the 1.50 boot then go back and flash the mz602
Sent from my Xoom using Tapatalk
amysdadforever said:
Hey bro just give some time I'll make a in depth tutorial seems like you your going to have to flash back to 3.0 flash the 1.50 boot then go back and flash the mz602
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.
oldblue910 said:
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.
Click to expand...
Click to collapse
Oh cool saves me the troubles of making a tut thanks bro and good job on the fix. I guess your fix does well and yeah awesome why east coast tired of the farms
oldblue910 said:
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.
Click to expand...
Click to collapse
The point is have you seen the "Start LTE Software Bypass Mode" screen? And how did you pass through it? Because when my xoom boot into that screen, it lost connection with my computer(I checked the "Device Manager" actually, there is no unknown devices, no motorola flash interface, etc..)
So what operating system you are using? (I tried both Windows XP and Win7 64bits) And what's the cable you are using(stock cable or program cable)? Also did you plug your power when flash? Did you pull out your sim card? etc..
Its Work with MZ605/MZ601 3G ?
DragonEarth said:
Its Work with MZ605/MZ601 3G ?
Click to expand...
Click to collapse
It will definitely brick your xoom, don't ever try that.
DragonEarth said:
Its Work with MZ605/MZ601 3G ?
Click to expand...
Click to collapse
NOOO! This is for MZ602 (Verizon US 4G LTE version) ONLY!!! If you try this on ANY other Xoom model, you will brick it. Plain and simple.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
kerry_xu_cs said:
The point is have you seen the "Start LTE Software Bypass Mode" screen? And how did you pass through it? Because when my xoom boot into that screen, it lost connection with my computer(I checked the "Device Manager" actually, there is no unknown devices, no motorola flash interface, etc..)
So what operating system you are using? (I tried both Windows XP and Win7 64bits) And what's the cable you are using(stock cable or program cable)? Also did you plug your power when flash? Did you pull out your sim card? etc..
Click to expand...
Click to collapse
When it got to that screen for me, it lost connection temporarily, then found the device again, installed the motorola driver for it, and kept on going.
Related
Here it is, Un-Official USA WiFi 3.1 & 3.2 Stock images. These are pulled from a clean USA WiFi 3.1 (stock 3.0.1 updated through the Official update). 3.2 is pulled from a clean USA WiFi 3.2 (stock 3.0.1 updated through the Official updates).
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
THESE IMAGES ARE FOR FIXING PROBLEMS AND WILL NOT WORK WITHOUT THE 3.1 BOOTLOADER
I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE, FOLLOW THE DIRECTIONS 100%
DO NOT TRY AND OEM LOCK YOUR DEVICE WITH THESE IMAGES​
Download links: HMJ37 USA WiFi 3.1 & Mirror
Download links: HTJ85B USA WiFi 3.2 & Mirror
Mirrors provided by Berzerker
Thank you Sir.
Sent from my HTC HD2
Thx B 10chars
Awesome .. thanks for posting.. still scared to root my WiFi Xoom though.. been through OG DROID, DROID x and HTC thunderbolt. But not sure if I want to cross the line with the Xoom.. I've had to use the sbf before on the DROID x..
May I ask how you do the backup of stock images?
Thanks.
khtdev said:
May I ask how you do the backup of stock images?
Thanks.
Click to expand...
Click to collapse
As far as I know, there are two methods. One is through CWR which I haven't really looked at. The other way is through Linux on a semi rooted Xoom. In that case you just have to use the dd or cat command on the proper device. If you type "mount" from Linux, you'll see where system is. Go to that "by-name" directory and you'll see the links for the boot and recovery partitions as well.
khtdev said:
May I ask how you do the backup of stock images?
Thanks.
Click to expand...
Click to collapse
As Scourge1024 said the easiest way on the xoom is to oem unlock, then load CWM. Do a nand backup, you have the system and boot img. This will not get you the userdata or recovery though. To get recovery, you have to load a rooted boot.img and just pull it with adb commands. Getting the userdata will never happen on the xoom (by an end user). The problem is that when you pull it, it pulls the entire partition regardless of how much is in use. You can not backup a 30gb partition on a 30gb partition
Yup. To grab the recovery, you need to sacrifice the boot partition. Or have a system image with su and Superuser.apk injected into it already. With putting in a new kernel, you'll have root through adb. With the su/Superuser.apk method, you can get root through terminal emulator. And just use the dd command from either methods.
It is safe to use oem lock with files bwcorvus?
gerald410 said:
It is safe to use oem lock with files bwcorvus?
Click to expand...
Click to collapse
As it says in the first post, DO NOT try and lock with these files. I tried 3 times, softbricked all 3 times. You need official files from Motorola to lock. If you need to lock, grab the files from my other sticky for stock wifi and use them.
bwcorvus said:
As it says in the first post, DO NOT try and lock with these files. I tried 3 times, softbricked all 3 times. You need official files from Motorola to lock. If you need to lock, grab the files from my other sticky for stock wifi and use them.
Click to expand...
Click to collapse
Duh how could I miss that in big red letters no less! thx for the confirmation
bwcorvus said:
As it says in the first post, DO NOT try and lock with these files. I tried 3 times, softbricked all 3 times. You need official files from Motorola to lock. If you need to lock, grab the files from my other sticky for stock wifi and use them.
Click to expand...
Click to collapse
While on unlocked/rooted 3.1 can you use the official 3.0.1 (HWI69) images to get back to stock/locked mode safely or do we have to wait for Motorola to release the HMJ39 images to do that ?
lazarost said:
While on unlocked/rooted 3.1 can you use the official 3.0.1 (HWI69) images to get back to stock/locked mode safely or do we have to wait for Motorola to release the HMJ39 images to do that ?
Click to expand...
Click to collapse
You can back safety, only way to lock as of right now.
Sent From My Evo
I have a completely stock Canadian Wifi Xoom MZ604.
If I unlock my xoom, wiping everything clean, can I then use these files to update it to 3.1? Would this effectively convert my xoom into a US model MZ604?
great dude keep it on
Thanks,
These may save my Xoom one day. Good to know.
Damn, it really works ...
bwcorvus said:
Here it is, Un-Official USA WiFi 3.1 Stock images. These are pulled from a clean USA WiFi 3.1 (stock 3.0.1 updated through the Official update). I have flashed all four twice now just to make sure it works.
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
THESE IMAGES ARE FOR FIXING PROBLEMS AND WILL NOT WORK WITHOUT THE 3.1 BOOTLOADER
I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE, FOLLOW THE DIRECTIONS 100%
DO NOT TRY AND OEM LOCK YOUR DEVICE WITH THESE IMAGES​
Download link: HMJ37 USA WiFi 3.1
Click to expand...
Click to collapse
It's working like a charm ...
What I did ...
0. I've root my Xoom WiFi (which I think wasn't a required step).
1. I've unlocked my Xoom using "fastboot" tool (please check if usb debugging was turn on if can't detect device)
2. I've got the file "HMJ37(USA_WiFi_3.1).zip", extracted and just flash those images ...
3. as the 1st post said, DO NOT lock it using fastboot!!!
steps:
> adb reboot bootloader
> fastboot oem unlock
# it will reboot after successful unlock process
> fastboot flash boot boot.img
# ... etc as quoted command
> fastboot erase cache
> fastboot reboot
4. got a taste of the new Android 3.1 on my Xoom
Gee bwcorvus, thanks again for sharing!!!
sweet good to have
HI, yes iam a noob, I have a similar problem to Masterslacker above.
My MZ604 Xoom has a build no. that says it's Latin America, in addition it's a Demo model bought in the US from Walmart. My question is, can i change the Build from H.6.2-21- demo 1301358186, to the US version, HWJ 37 (USA Wifi 3.1)??
Reflashing the Xoom
Ok, I have been looking around the site for the directions to reflash my Xoom. Can't find them. Can someone point me in the right direction.
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.
So I can literally flash a different recovery from within another?
jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium
Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks
Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk
I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.
Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.
Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+
You're all going to have to forgive my idiocy, but I have a problem. I installed SM7 in my Atrix on an unlocked bootloader. I decided to go back to stock today and downloaded and flashed the SBF through RSLite. Reading now, you're not suppose to flash a previous sbf version if your bootloader is unlocked, but I didn't know that, at least that's what I'm assuming happenned. Now, the phone goes into a loop on the Motorola animation and does nothing. I can get into fastboot, recovery, RsLite mode and all of that, but the phone itself is in a loop. My questions is, what (If anything) can I do (eg. flash, fastboot etc) to go back and fix my problem? That battery already died once and I found a way to charge it so I can get back in those menus, but any tidbits would be majorly helpful.
madetoservehim said:
You're all going to have to forgive my idiocy, but I have a problem. I installed SM7 in my Atrix on an unlocked bootloader. I decided to go back to stock today and downloaded and flashed the SBF through RSLite. Reading now, you're not suppose to flash a previous sbf version if your bootloader is unlocked, but I didn't know that, at least that's what I'm assuming happenned. Now, the phone goes into a loop on the Motorola animation and does nothing. I can get into fastboot, recovery, RsLite mode and all of that, but the phone itself is in a loop. My questions is, what (If anything) can I do (eg. flash, fastboot etc) to go back and fix my problem? That battery already died once and I found a way to charge it so I can get back in those menus, but any tidbits would be majorly helpful.
Click to expand...
Click to collapse
If you can get into recovery, flash a fruitcake.
Make sure to data wipe & cache wipe beforehand.
Swiftks said:
If you can get into recovery, flash a fruitcake.
Make sure to data wipe & cache wipe beforehand.
Click to expand...
Click to collapse
I tried going into recovery mode; no dice. Droid error icon showed up. What's this I'm reading about flashing using fastboot? Can I download and flash a fastboot file so as to fix my phone?
Tried full wipe using fastboot? That pulled me out of boot loop once.
There are instructions and batch files to automate it somewhere in development forum.
if ur ATnT then screwed for very long time(till there is a fix)
if ur international/bell user (i am bell user and i messed up mine big time) then download the bootloader unlock SBF (IHOP_Bell) and flash it via rdslite and this will give u back the bootloader unlocked logo on ur boot screen.
if yes then ur lucky connect ur phone in fastboot mode and remove every **** out of it
fastboot erase boot
fastboot erase system
fastboot erase webtop
fastboot erase userdata
fastboot erase cache
then flash latest recovery via fastboot (do a search in forum ull find it)
boot into recovery and mount ur memory card as a usb mass storage device and copy the fruitcake or any other rom's zip file into it and flash it via recovery and u should be good to go.
since i am bell user i was able to flash back 2.2.2 french rom via SBF and RSD but after flashing cm7 i am not touching rsd or any sbf for that matter.
Press thanks if i helped you, and if i didnt then press it anyways
i would say do what swiftks says
flash a fruitcake use fastboot its your
only hope now also swiftks has guides
in his signature
Yer not hard bricked. You'll be fine. PM swift or myself if you can't figure it out.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
I was trying to revert to stock through RSDLite and got the "Failed to boot 1" error.
Since then I can't access the RSD Mode, only Fastboot. If I try to flash the sbf file again, I get the following error :
http://i.imgur.com/HKpPq.png
Any idea what I could do ? Can I unlock it again going through fastboot (not IHOP as it uses a sbf file) ?
I feel stuck...
My Atrix is an European model.
Thanks !
Oh god what an idiot : to solve this, just boot your phone and don't use the volume rocker to access RSD mode as the phone IS in RSD Mode by default ! Just flash the sbf file again and it works.
I leave it here for information purposes !
DannyBiker said:
I was trying to revert to stock through RSDLite and got the "Failed to boot 1" error.
Since then I can't access the RSD Mode, only Fastboot. If I try to flash the sbf file again, I get the following error :
http://i.imgur.com/HKpPq.png
Any idea what I could do ? Can I unlock it again going through fastboot (not IHOP as it uses a sbf file) ?
I feel stuck...
My Atrix is an European model.
Thanks !
Click to expand...
Click to collapse
Look here for the failed to boot error (soft brick). Might help.
Before flashing an sbf, did you look in the Atrix Reboot Project for a fruit cake?
Rsd after unlocking is fast lane to brick city. You could try to flash your model's .IMG files, specifically boot.img and system.img and fastboot flash those if possible.
Sent from my MB860 using xda app-developers app
So you advice fruit cakes but I thought RSD would provide a "back to factory" reset. Fruit cakes needs a recovery, so it needs the bootloader to be unlock and I want to relock the bootloader (or at least, remove the "unlocked" message at boot).
I went the RSD road once and it worked. Now I tried it again : fixed the failed to boot issue but I get a bootloop flashing a French sbf.
Problem is I never knew what model I got exactly when I bought it. I did made a recovery back up of the stock though.
So it there a way to relock the bootloader AFTER going fruit cake or restoring the rom from recovery ?
Yes in that case be sure your sbf is safe or has "pudding". Akaik sbf is only way to remove the unlocked message on boot screen. You'll need the sbf for your carrier/region.
Sent from my MB860 using xda app-developers app
DannyBiker said:
So you advice fruit cakes but I thought RSD would provide a "back to factory" reset. Fruit cakes needs a recovery, so it needs the bootloader to be unlock and I want to relock the bootloader (or at least, remove the "unlocked" message at boot).
I went the RSD road once and it worked. Now I tried it again : fixed the failed to boot issue but I get a bootloop flashing a French sbf.
Problem is I never knew what model I got exactly when I bought it. I did made a recovery back up of the stock though.
So it there a way to relock the bootloader AFTER going fruit cake or restoring the rom from recovery ?
Click to expand...
Click to collapse
See the link I posted earlier for going back to stock options.
Flashing an sbf is never a good idea even when you know your exact model and version. Flashing an sbf without knowing this info is just asking for big trouble.
The answer to your last question is no.
Thanks.
I'll go with a CWR restore. I'll let the "Unlocked" mention...
Thank you !
I was having some pretty serious radio issues with cyanogenmod so I attempted to use RSD Lite which had previously worked like a charm to go back to stock rom (using what came pre-bundled with matt's script v. 1.2)
My phone is unlocked at the bootloader
I have it rooted.
I get the original droid boot loop.
I can definitely get it into a status code 3 AP Fastboot, but none of the tools for the script or RSD lite have gotten me past the droid eye bootloop.
I'm presuming a wipe of the cache will do the trick, but either my googling skills are gone or I'm just too tired after 6 hours.... but I'm unable to get any type of recovery flashed.
My first question is if I am in AP Fastboot, who knows how to get a recovery image flashed so I can see if it's just a cache issue of trying to go from cyanogenmod to stock firmware.
My second question is - Does anyone have a link to a guide to "re-lock" my bootloader in case I need to get this to tech support?
Thanks
matthew1429 said:
I was having some pretty serious radio issues with cyanogenmod so I attempted to use RSD Lite which had previously worked like a charm to go back to stock rom (using what came pre-bundled with matt's script v. 1.2)
My phone is unlocked at the bootloader
I have it rooted.
I get the original droid boot loop.
I can definitely get it into a status code 3 AP Fastboot, but none of the tools for the script or RSD lite have gotten me past the droid eye bootloop.
I'm presuming a wipe of the cache will do the trick, but either my googling skills are gone or I'm just too tired after 6 hours.... but I'm unable to get any type of recovery flashed.
My first question is if I am in AP Fastboot, who knows how to get a recovery image flashed so I can see if it's just a cache issue of trying to go from cyanogenmod to stock firmware.
My second question is - Does anyone have a link to a guide to "re-lock" my bootloader in case I need to get this to tech support?
Thanks
Click to expand...
Click to collapse
First off, after you flash the firmware via fastboot, go back into recovery and do a factory reset. Second, you can't relock the bootloader.
thanks for responding. I wish it was this easy - it's been caught in a loop after trying factory again. I think I'd be able to resolve this if there were a way to wipe everything clear and build from scratch
RikRong said:
Second, you can't relock the bootloader.
Click to expand...
Click to collapse
No you cannot relock the bootloader...
Download this http://forum.xda-developers.com/showthread.php?p=40682385 chose option one... once flashed boot into recovery factory reset... boot up device... once booted root... install voodoo protect root install update restore root... install custom recovery if desired... I have boot looped I've been stuck at boot logo I've also been stuck with no data n WiFi this has saved me on more times then I can count on 3 separate devices and his utility n what I described has saved me more times then I can count...
Sent from my XT907 using xda app-developers app
I had some issues with aftermarket recoveries and formatting. I'm not sure if you've had any luck or if this is even helpful but assuming you are in fastboot and have the SDK set up...
Extract the stock sbf/XML and grab the recovery image.
At command line enter: "fastboot flash recovery recovery.img"
Reboot with all three buttons and select recovery.
Do factory reset.
Get back into fastboot
And repeat the command above (with different recovery obviously) to reflash a recovery of your choice.
(The official Philz cwm touch posted recently in development subforum works very well with the new 4.3 ROMs)
Hope that helps...if its too basic, please disregard! Good luck.
Sent from my XT907 using Tapatalk 2