I believe this is what everyone is looking for.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
Sent from my Xoom using xda premium
It says it's for MZ602. Will this still work with our current XOOMs.
Furthermore, will it work with a 3G XOOM that has yet to be upgraded?
It says Verizon. It is the same file we updated to. Ours was the mz600, but after the upgrade it became mz602. You know of any other Verizon xoom with 4g? They are going to sell the same xoom, just has the lte card in it this time.
Sent from my Xoom using xda premium
Well, I'm having trouble with it.
I'm using RSDLite and trying to flash the .SBF and it's saying:
"Error validating image files" under status, before I even hit start.
Then afterwards, I get:
"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."
Thanks... Anybody knows if I flash one of the latinamerican image into a US 4G would brick the Xoom?
I think you have to extract it or unzip it.
Sent from my Xoom using xda premium
hammer4203 said:
I think you have to extract it or unzip it.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.
Great. After using this, my Xoom won't go past the boot screen.
It won't even boot into recovery. I can still access Fastboot and RSD.
Even after trying different unbrick solutions. Even after flashing back to HRI66.
Can't even get my Xoom to turn off now.
You may need the other cable to flash it in rsd mode. There is a special cable that looks exactly like the normal usb cable. It's wired different.
Sent from my ADR6400L using xda premium
You may need rsd lite on your PC and USB drivers to do it with the stock cable.
Sent from my Xoom using xda premium
hammer4203 said:
You may need rsd lite on your PC and USB drivers to do it with the stock cable.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Yeah.. That's what I'm doing it with. The stock USB cable included with the Xoom and RSDLite v5.4.4 with all the updated drivers.
My Xoom just sits there at the boot screen now, like I said, even after trying to flash back down to HRI66 afterwards to fix it.
I can still boot into Fastboot and RSD mode, but my Xoom stalls and doesn't enter recovery, even after trying another recovery img.
I thought I read something about needing a proper boot.img to go with the SBF file, but I even tried flashing AceXMachine's boot img and nothing.
So you guys haven't gotten this to work or are you just the lucky ones who had problems?
There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
Sent from my ADR6400L using xda premium
dethrok said:
Well, I'm having trouble with it.
I'm using RSDLite and trying to flash the .SBF and it's saying:
"Error validating image files" under status, before I even hit start.
Then afterwards, I get:
"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."
Click to expand...
Click to collapse
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.
hammer4203 said:
There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.
And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.
zone23 said:
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.
Click to expand...
Click to collapse
Find and download RSDLite 5.4.4. That's what fixed it for me.
dethrok said:
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.
Click to expand...
Click to collapse
dethrok, you've got most of it right >extract the .SBF (I've had issues on 64 bit Win 7 machine, unless I've place the file at either the root of C: or else under c:\users\<my username>\ (??-weird??))
> make sure you have the latest drivers
> (this is the gotcha) you need to use RSDLite v5.4.4
>>Note: Yes the HLK75D SBF works and was designed with the original MZ600
Hardware, since the MZ602 is just the MZ600 w/ LTE
This should do it for you, however for good measure, I aways run a short script that unlocks, erases (boot/sys/rec/uda & cache partitions), flashes HR166 back onto the device & then relocks it. I know this is probably a waste of time; it just seems to SBF with less issues.
Here's the text out of the .bat I wrote:
(!!!Please bear in mind this will erase/format your device, so please make sure you have all personal data backed up.!!!)
If your system is already powered up and has USB debugging enabled you can remove the 1st REM statement & just execute the .bat file, otherwise reboot the device by holding down the volume up and power button > release both and then hold down the volume down button until the "fastboot" screen appears.
Copy the below text into notepad and save as a .bat file
REM adb reboot bootloader
fastboot oem unlock
REM Press and hold the volume down button
pause
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot -w
pause
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you want to use this, you need to d/l the HRI66 build .img files from MotoDEV as well as having the
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
* you can also just REM out the fastboot commands that flash the HR166 image, so the device is completely blank and you can just load the HLK75D sbf via RSDLite, either way works........
** Remember after any OS flash, you should launch “Android recovery Mode” (press & release the down volume button after the red Motorola symbol appears when the device powers on) and reset the device to factory defaults.
Cheers,
Hat
That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
Sent from my Xoom using xda premium
hammer4203 said:
That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Now see, someone mentioned the other file included in that old .SBF, but no one ever answered as to what to do with it:
janjan said:
Do we need to flash both of these following?
1: 1.35-everest.reflash.sbf
2: VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
And what is 1.35-everest.reflash.sbf is for?
thanks
Click to expand...
Click to collapse
Actually, another person in that thread said they flashed the file first, rebooted, then flashed the .SBF. So I'm not sure anymore.
dethrok said:
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.
And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.
Find and download RSDLite 5.4.4. That's what fixed it for me.
Click to expand...
Click to collapse
Thanks a lot guy that worked and I'm now back in business. Meaning my 3G is now operational. Don't have 4G in my area but I assume it works now as well. My device was unlocked and when I go into network now it shows CDMA/LTE.
Edit:
I did not have the official Xoom cable either.
Zone, did you flash the HLK75D SBF?
Related
Welcome to my thread on bootloop fixes for flashing new ROM's through CWM.
I have seen many cases where people will get stuck in a bootloop from flashing a newer 2.3.4 ROM with CWM, and this has also happened to me. Please be aware I made this guide for AT&T Atrix 4G's. I am unaware if this works for international devices.
Click to expand...
Click to collapse
DISCLAIMER:
I AM NOT RESPONSIBLE FOR ANYTHING THAT MAY GO WRONG WHILE FOLLOWING MY INSTRUCTIONS. YOU SHOULD ALREADY KNOW THERE IS ALWAYS A RISK OF BRICKING YOUR DEVICE WHILE FLASHING.
DO NOT DO THIS IF YOU ARE COMING FROM A 2.3.4 STOCK AT&T OTA UPDATE ROM.
THIS WILL WIPE ALL DATA EXCEPT INTERNAL MEMORY AND THE SD CARD, AND MAKE YOUR PHONE LIKE NEW.
ALSO, BE AWARE THIS IS FOR AT&T, NOT INTERNATIONAL.
Click to expand...
Click to collapse
WHY?:
In almost every bootloop case, it is because the CWM version installed on your atrix is older then what the ROM maker made it for. For example, if you were like me and flashed the HKTW ROM right when it came out with Tenfar's first unlocked CWM recovery, then tried to flash a new ROM such as Kenneth's 2.3.4 AT&T, then you would be stuck in a bootloop. So again, you always need the latest CWM.
Click to expand...
Click to collapse
SOLUTION?:
WINDOWS ONLY:
Prerequisites:
1.2.6 SBF file (the password to extract the file is "atrixbl")
RSD Lite 5.0
Drivers: 32 bit OR 64 bit
INSTUCTIONS:
1. Make sure your phone is turned off
2. Take out your microSD card and SIM card for the flashing process
3. While turning the phone on, hold the Volume Up button until it acknowledges RSD
4. Your device will say “Starting RSD protocol support”
5. Run “RSD Lite” on your computer
6. Press the “. . .” button next to the box labeled “Filename”
7. Load up the SBF file (The SBF file is located inside of the .gz file, you must extract it out before loading it into RSD Lite)
(Use WinRAR or 7-Zip to extract the .gz file on your computer)
8. Plug your device into your computer
9. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
10. Press the “Start” button
11. Be patient while the phone reboots. It will take a long time.
12. OTA update from 1.2.6, all the way to 1.8.3
Download "Rom Manager" from the android market.
13. Click the first option "Flash ClockworkMod Recovery"
14. Select Motorola Atrix 4G.
15. Now you're all set and back in the game. You are safe to flash any new ROMs with this OFFICIAL CWM. And Rom Manager will let you know when a new CWM version is available.
Click to expand...
Click to collapse
IF ANYTHING IS INCORRECT, PLEASE LET ME KNOW. ALSO, IF THESE METHODS DO NOT WORK, LET ME KNOW AND I WILL UPDATE THE GUIDE. WHAT I HAVE POSTED HERE IS BASED ON WHAT WORKED FOR ME, AND EVERYONE I HAVE HELPED.
Click to expand...
Click to collapse
If you would like to donate to me, I will put a link below. What I do with donations is find ROM developers, and see their current work progress, and donate to them. So anything you donate to me, gets donated to future ROM making.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8Q3MSD9KW2GD6
Click to expand...
Click to collapse
Thank you for everyone who has given us ROMs, hacks, mods, you name it. This device is nothing without you guys!
Click to expand...
Click to collapse
Reserved
Sent from my MB860 using XDA Premium App
jbrussee said:
Does this not effect anyone?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
People who are on the ota DO NOT flash back to 1.83 or prior op make this clear please although most will know some noobs wont lol
edit my fault you did, maybe a little bigger? if not its ok at least you have it
Yeah, I made sure I said that.
Sent from my MB860 using XDA Premium App
hi im posting this so I can post in the development section.
LMAO Techno. You got punked on two consecutive threads. Why do you have to be so rude and arrogant? Oh and please follow your own advice.....read before posting any comment.
Sent from my MB860 using XDA App
logantyler said:
hi im posting this so I can post in the development section.
Click to expand...
Click to collapse
+1 This place is way to aggressive with new users.
bootloop
Hi All,
I wanted to add my solution for having my phone stuck in a bootloop and then soft bricking it. My phone did not unlock successfully
1. Download a working version of 1.83
2. Download RSD Lite for your computer
3. When starting phone enter recovery by holding the volume down and pressing the power button, when the recovery option at the top shows up, use the volume down to get to RSD Mode. Volume Up selects.
4. Launch RSD Lite
5. Plug phone into computer using USB and RSD Lite should recognize phone.
6. Select the 1.83 file. Then run it
7. This may take some time, but it will boot your phone back to stock settings.
8. Read directions more carefully next time when you install a custom rom.
Hope this helps someone!
Thanks for more input!
Sent from my Motorola Atrix 4G MB860 using XDA Premium App
Hello, I installed GingerBlur and Now want to upgrade to Gingerbread. I am having some issues with doing an OTA upgrade. I aslo no longer have a PC which I used to root and flash before. Any help would be greatly appreciated.
I believe your instructions are only for AT&T users (judging by the files and OTA numbers).
If so, you should state that so some new International user doesn't try this and hard brick.
Zero-k, thank you for informing me of this.
Sent from my Motorola Atrix 4G MB860 using XDA Premium App
As the title says, After I unlocked the bootloader, and flashed a 2.3.4 rom, My Atrix sometimes will go up to the blur phase of the boot and then it will restart, but most of the time will just do a boot loop on the Red Moto Logo at boot, I can go into fastboot and recovery no problem...
Thanks on any help...
same thing
i get the same thing every now and then but i can get fastboot and recovery so im good i guess.
Did you wipe before you installed your ROM?
Do a fastboot -w then reinstall your ROM.
also do a factory reset and make sure your on the newest recovery
quicklyspent said:
Did you wipe before you installed your ROM?
Do a fastboot -w then reinstall your ROM.
Click to expand...
Click to collapse
Did the fastboot -w and reinstalled the ROM and it is doing the bootloop the same, first boot goes up to the blur phase and reboots, and afterwards just does the boot loop up to the motorola dual core red logo.
TechnoNeto said:
also do a factory reset and make sure your on the newest recovery
Click to expand...
Click to collapse
I have the latest recovery, thanks...
Flash back to stock and follow my guide
Sent from my MB860 using XDA Premium App
TechnoNeto said:
Flash back to stock and follow my guide
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Where can I find your guide, and should I SBF 1.83 or what..
It's in general under video how to go... Sorry I'm on my phone
Sent from my MB860 using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=1179506
Sent from my MB860 using XDA Premium App
Did you make sure to use tenfar's CWM instead of ROM Manager's? My 2.3.4 install also bootlooped, and that ended up being the issue.
Sent from my ATRIX running CherryBlur 1.3.
I'm still having issues, I have the latest Recovery, and I have tried to flash through Recovery and still get the boot loops...
Just Flashed via RSD the SBF 1.2.6 and still have the reboots, I think that my phone it's bricked, I can go into RSD, Fastboot, Recovery, everywere, I can flash anything, but when it boots, it does a bootloop everytime... I
If someone has an answer please help...
poorg said:
Just Flashed via RSD the SBF 1.2.6 and still have the reboots, I think that my phone it's bricked, I can go into RSD, Fastboot, Recovery, everywere, I can flash anything, but when it boots, it does a bootloop everytime... I
If someone has an answer please help...
Click to expand...
Click to collapse
Take out the battery for 30 sec and then put it back press vol up while you turn on.... can you please post what it show up in your screen after this?
Sent from my MB860 using XDA App
mramirezusa said:
Take out the battery for 30 sec and then put it back press vol up while you turn on.... can you please post what it show up in your screen after this?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Starting RSD protocol support....
poorg said:
Starting RSD protocol support....
Click to expand...
Click to collapse
Ok I will post a guide and follow up give 1 minute
Sent from my MB860 using XDA App
mramirezusa said:
Ok I will post a guide and follow up give 1 minute
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks for the help, really appreciate this...
poorg said:
Thanks for the help, really appreciate this...
Click to expand...
Click to collapse
Ok maybe is time for clean starp up, DEEP CLEAN, I did this script for a friend and it help:
Need Windows PC and UNLOCKED BOOTLOADER (when I said unlocked bootloader need to be that everytime you boot you saw "unlocked" tag at the left top corner)
1. Download and extract/unzip the following file in a new folder (example C:\atrix):
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
2. You will end after extracted/unzip the file with something like this:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
3. Download this file "CLEAN_2.3.4_ATT.zip" and extract/unzip to the same location (example C:\atrix)
http://forum.xda-developers.com/attachment.php?attachmentid=673330&d=1312203457
5. Run the script "clean" and follow exactly all the instrucctions!
6. This will install a Pristine Official ATT GB 2.3.4/4.5.91
Done!
Hope it help
mramirezusa said:
Ok maybe is time for clean starp up, DEEP CLEAN, I did this script for a friend and it help:
Need Windows PC and UNLOCKED BOOTLOADER (when I said unlocked bootloader need to be that everytime you boot you saw "unlocked" tag at the left top corner)
1. Download and extract/unzip the following file in a new folder (example C:\atrix):
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
2. You will end after extracted/unzip the file with something like this:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
3. Download this file "CLEAN_2.3.4_ATT.zip" and extract/unzip to the same location (example C:\atrix)
http://forum.xda-developers.com/attachment.php?attachmentid=673330&d=1312203457
5. Run the script "clean" and follow exactly all the instrucctions!
6. This will install a Pristine Official ATT GB 2.3.4/4.5.91
Done!
Hope it help
Click to expand...
Click to collapse
Ok, but mine does not say unlocked right now, I did Unlock the bootloader but after I flashed the 1.2.6 SBF it does not say it!!!!
I noticed you posted that you actually have unlocked bootloader just make sure that when you turn on the phone it said in the left top corner "unlocked", if it is not that case just follow intructions on this post:
http://forum.xda-developers.com/showpost.php?p=15930466&postcount=1
download the script and select option 1 from the main menu and then option 3 and complete all the steps
so you can re unlocked the bootloader
then follow the instrucionts that I posted before here
mramirezusa Thank You.... As you stated, everything went smoothly and my phone it's perfect again, something I noticed, when it boots, it's does not say unlocked anymore shoul'd I do the procedure with the the script that you sent posted above...
I'm about at my wits end trying to figure out this problem of mine.
Here's a quick overview of my situation, so I don't have to go through it again:
http://forum.xda-developers.com/showthread.php?t=1301091
Anyways, I decided to take another shot late at night to see if I could get this working. I'm running on 3.2.2 right now, build HLK75D, with no 3G/4G connectivity. I looked at a screen shot of a stock updated 4G Xoom's settings and I noticed that my baseband is the only thing different.
Is there some way to change the baseband from what it is now (CDMA_N_03.1A.54P) to "CDMA_N_03.1A.52P ltedc_u_05.15.00"?
I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.
Jewremy said:
I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.
Click to expand...
Click to collapse
Yeah, well, I don't have either 3G or 4G. My Xoom says activation successful over Wi-Fi, and I have full signal with the Verizon towers, but it just doesn't connect.
I still haven't heard anything back from Motorola regarding any way to get the baseband back to the LTE version.
Guys use Motorola stock imgs, but remove your sim card after you flash it. See if it connects to 3g then. If not look for the hlk75c stock root on here flash that with your sim in.
Sent from my Xoom using xda premium
HLK75C is the Verizon one. Try to flash this.
http://forum.xda-developers.com/showthread.php?t=1294824
Sent from my Xoom using xda premium
hammer4203 said:
HLK75C is the Verizon one. Try to flash this.
http://forum.xda-developers.com/showthread.php?t=1294824
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.
Did you flash hri66? What kernels have you tried? Oh and are you in a 4g area, cuz that can cause an issue if your not.
Sent from my Xoom using xda premium
http://forum.xda-developers.com/showthread.php?p=18224270
AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.
Sent from my Xoom using xda premium
hammer4203 said:
http://forum.xda-developers.com/showthread.php?p=18224270
AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I've tried AceXMachine's solution. Still no deal.
No matter what image I've used, I still have no option for LTE in my mobile network settings. My baseband still has never changed back to LTE.
I live in the dead center of a strong 4G area. My 4G was working fine prior to making the stupid mistake of flashing over what Motorola sent back.
Jewremy said:
We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.
Click to expand...
Click to collapse
And that is exactly what mine says when I power up BP.
I just received a total generic e-mail response from Motorola telling me to make sure to check for updates, etc.
I replied to them and told them that my baseband is the wrong version and that my LTE radio is turned off. Lets see if they can provide anything to help out.
Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.
Sent from my ADR6400L using xda premium
hammer4203 said:
Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I think it involves pulling your build.prop?
http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
dethrok said:
I think it involves pulling your build.prop?
http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Click to expand...
Click to collapse
No. This is lower-level software. It's part of the bootloader, governs the radio. The build.prop files are the same between 3.2.2 back from moto and 3.2.2 upgraded from stock.
I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.
Sent from my Xoom using xda premium
I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039
Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.
hammer4203 said:
I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.
It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. EDIT: Nevermind. Don't bother.
zarkuu said:
I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039
Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.
Click to expand...
Click to collapse
See above in this same post.
Well, this is all hurting my head. Motorola e-mailed me back and said they were bumping my case up to their repair escalation team and I'll be getting a call in 1-2 days.
Hopefully they'll still help me out when it was my own stupid fault that I screwed up my connection. Maybe they'll be able to give me a solution to turn the radio back on.
Jewremy said:
It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.
It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. I'm thinking the baseband is contained in the ebb partition, also known as the bootloader. Reflashing the bootloader is extremely risky. You really don't want to do that. It's at /dev/block/mmcblk1p1. Controls the whole boot sequence. The HTJ85B update overwrites/updates the bootloader, which is what could cause our issue.
Click to expand...
Click to collapse
OK, this makes sense to me since I have flashed back to HRI66 and did OTA updates to HTL85B and nothing else would presumably have changed it back. My mistake was probably allowing the device to boot under HTJ85B. If I had just done it through recovery and then flashed back to HLK75C it wouldn't have touched the bootloader. I bet some people didn't do that and so they work when flashing various restores. I understand it is risky to flash the bootloader (because if it goes wrong you won't be able to even go to fastboot) but what other option is there other than RMA back to Moto? Do we think Moto will be releasing stock images for this new bootloader anytime soon? That's really more of a rhetorical question I think.
I guess if someone wants to try making a backup I might try flashing it.
From http://forum.xda-developers.com/showthread.php?t=1294824
Pulling your own images
1. Flash a custom recovery
2. Boot straight into recovery.
Code:
adb shell
mount /data
mkdir -p /data/media/images
dd if=/dev/block/platform/sdhci-tegra.3/by-name/ebb of=/data/media/images/bootloader322.img
sync
Then reboot back into android and pull it off your device.
See if you can use this.
http://forum.xda-developers.com/showthread.php?t=1270848
Sent from my Xoom using xda premium
I'm in the same boat: http://forum.xda-developers.com/showthread.php?t=1299485
Hopefully we'll find an answer soon.
hammer4203 said:
See if you can use this.
http://forum.xda-developers.com/showthread.php?t=1270848
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
No dice. I've checked all the OTA updates I know about:
19dea2ba1ae5.signed-trygon-HTJ85B-from-HMJ37.19dea2ba.zip
7a15c95f18ba.signed-trygon-HLK75-from-HLK42B.7a15c95f.zip
7ac6aeb09117.signed-trygon-HLK75D-from-HLK75C.7ac6aeb0.zip
a5de99b3e437.signed-trygon-HMJ37-from-HRI66.a5de99b3.zip
In HMJ37 from HRI66 (3.0.1 to 3.1) I see a bootloader.bin along with this in the updater-script
Code:
assert(package_extract_file("bootloader.bin", "/tmp/bootloader.bin"),
moto.set_mbm_update("/tmp/bootloader.bin"),
delete("/tmp/bootloader.bin"));
There is nothing else that does an "set_mbm_update" in any of the other updates.
On the upside the md5sum of this bootloader.bin matches my own dd dump of the ebb partition.
Code:
c3a74df4a356c0e4158fd592cc8be693 bootloader.img
c3a74df4a356c0e4158fd592cc8be693 /tmp/updates/bootloader.bin
I'd be interested to see if someone can take a dump of their ebb partition as I documented earlier and see if the md5sum matches. if it does, then we will know the bootloader is not the problem. If not, then this is something new to try. Basically we need the dump and then an update.zip to flash it. If someone can provide the dd dump then I can make the update.zip. That should be safe enough to flash I think.
So I wanted to go into recovery, so I clicked (in the bootstrap recovery app) Clicked Bootstrap recovery, then reboot recovery. When I tried to restart it, it got stuck on the Motorola logo. Then I went swimming and the phone died. Now when I try to turn it on it has a ? in the battery. I have no idea what is happening, any ideas?
You probably shouldn't have taken the phone swimming!
Jokes aside, find a fully charged Droid X battery (you can also splice a cable to charge the battery), then SBF the device back to the firmware it was on before.
First though, enter bootloader mode and if you don't get a battery error, attempt to SBF.
Sent from my Galaxy Nexus using Tapatalk 2
Haha! Well, thanks! Thats what I was thinking. I'm not sure exactly how to SBF it, to root it before, my freind told me to use http://forum.xda-developers.com/showthread.php?t=1680037 so maybe the SBF file will work?
Stevenator21 said:
Haha! Well, thanks! Thats what I was thinking. I'm not sure exactly how to SBF it, to root it before, my freind told me to use http://forum.xda-developers.com/showthread.php?t=1680037 so maybe the SBF file will work?
Click to expand...
Click to collapse
Unfortunately, that prerooted SBF file doesn't work.
First you should try to SBF to .602, but it will only one if you were not on .621 before that. (.602 is much easier to root).
If you were on .621 before use a .621 SBF file.
If I can find any links to the files I will post them back here. A Google search on how to SBF should bring up tons of guides and tutorials on SBFing, so it shouldn't be too difficult. XD
Sent from my Galaxy Nexus using Tapatalk 2
I actuallu changed my plan, while posting this, I am currently SBF-ing using this post http://forum.xda-developers.com/showthread.php?t=1560608 Thanks so much!
EDIT: When it did a reboot after SBF it does the motorola splash screen but keeps repeating, how do I fix this?
Power off. Then hold home and power til you get to the screen with an android and an exclamation point. Press both volume keys simultaneously at this screen. Use volume keys to navigate to wipe data/ factory reset. Use power key to select. After it does its thing then reboot.
Sent from my Liquid X
Thanks so much! Back and working. One more thing. I remember in a video a guy did a command in terminal after installing CM9 to make it so you can put files on it from the PC. Do you know what it is?
No idea. I use the data cable for file transfer. Or you can use Software Data Cable from the market to transfer files over WiFi.
Sent from my Liquid X
Stevenator21 said:
Thanks so much! Back and working. One more thing. I remember in a video a guy did a command in terminal after installing CM9 to make it so you can put files on it from the PC. Do you know what it is?
Click to expand...
Click to collapse
If you have a working ADB set-up you can "adb push" files to the device.
But simply plugging in the phone to a computer should trigger USB Mass Storage mode.
http://gyazo.com/c7b4bbfdb69ba1de32e472063a362e96
I am unable to boot into anything buy AP FASTBOOT and it is failed
Use rsdlite 6.1.4 and try again
Try this XML http://db.tt/XKakqGhK
tadgerloks said:
Use rsdlite 6.1.4 and try again
Try this XML http://db.tt/XKakqGhK
Click to expand...
Click to collapse
Follow up, Where would one goto get the latest version of RSDlite?
It was a problem with the phone I messed with the image a bit and went in fine
Sent from my XT907 using xda app-developers app
straylight said:
Follow up, Where would one goto get the latest version of RSDlite?
Click to expand...
Click to collapse
Just Google rsdlite 6.1.4 or if needed I can upload it and share the link
Here you go. This has everything you need.
http://www.phonearena.com/news/How-...-M-back-to-stock-ICS-from-the-JB-leak_id35580
Moved To Q&A
Do not post questions in the dev section!
had same exact issue, and followed guide. However, it still only boots into fastboot with the reason: Sticky Bit factory_fastboot. tried doing the flash again a couple more times (each time successfully through rsdlite), but same result each time.
Any thoughts?
EDIT: Nevermind, found that I could still boot into the white text boot menu, and choose factory from there (this was after trying a factory wipe from the recovery menu, but still failed to boot). This FINALLY brought it back to life, and back to ICS