Recently I bought a Bravo which came with 2.2.2 "Blur_Version.38.6.0.MB520.Generic.en.US", there was a different kernel too.
I was trying to root it and install custom recovery but I installed custom recovery twice and then I had to flash sbf because it went into bootloop, nothing beyond moto logo.
after installing sbf 2.2.1 again, when I go to system updates, it says its up to date.
I was trying to backup system to have it.
Did anybody here get this update?
josuearisty said:
Recently I bought a Bravo which came with 2.2.2 "Blur_Version.38.6.0.MB520.Generic.en.US", there was a different kernel too.
I was trying to root it and install custom recovery but I installed custom recovery twice and then I had to flash sbf because it went into bootloop, nothing beyond moto logo.
after installing sbf 2.2.1 again, when I go to system updates, it says its up to date.
I was trying to backup system to have it.
Did anybody here get this update?
Click to expand...
Click to collapse
No, but I haven't been on the actual Bravo factory system to know if an update would even be available. I've always suspected that there were more Bravo systems than our one sbf, but with all our users instantly upgrading to CM7 I can easily see it being overlooked. The other/maybe newer kernel intrigues me since it might be more compatible\similar to the Defy kernel since the Defy's last official update was a 2.2.2 Froyo. While officially the Bravo is listed as a US ATT Phone, all the Chinese and non American users makes it very obvious that this isn't the case. I'd love to get my hands on a Chinese SBF for the Bravo.
While you weren't able to get past the Moto logo, were you able to root it? Or access 2nd-init? If so, then why the hell didn't you do a dd on the bootloader? :silly: I'd of gladly dumped that dump onto my Bravo. If you happen to come across one again then for the love of God don't sbf it.
Knowing that there's another Bravo system and kernel I can't try makes me a very sad panda.
/Now I gotta sbf to stock and fire up cheesecake and see if anything happens. If cheesecake even still works.
skeevy420 said:
No, but I haven't been on the actual Bravo factory system to know if an update would even be available. I've always suspected that there were more Bravo systems than our one sbf, but with all our users instantly upgrading to CM7 I can easily see it being overlooked. The other/maybe newer kernel intrigues me since it might be more compatible\similar to the Defy kernel since the Defy's last official update was a 2.2.2 Froyo. While officially the Bravo is listed as a US ATT Phone, all the Chinese and non American users makes it very obvious that this isn't the case. I'd love to get my hands on a Chinese SBF for the Bravo.
While you weren't able to get past the Moto logo, were you able to root it? Or access 2nd-init? If so, then why the hell didn't you do a dd on the bootloader? :silly: I'd of gladly dumped that dump onto my Bravo. If you happen to come across one again then for the love of God don't sbf it.
Knowing that there's another Bravo system and kernel I can't try makes me a very sad panda.
/Now I gotta sbf to stock and fire up cheesecake and see if anything happens. If cheesecake even still works.
Click to expand...
Click to collapse
Uuuuuuups, I alredy SBF it, the phone belong to my father and I had to give it to him yesterday
There was another kernel yes, side applications was enabled, it was faster than 2.2.1, there were less bloatware
And the most important thing is that the phone didnt say AT&T down the home button.
I am very sad because I couldnt even create a backup for system, I forgot about dd codes for backing up too, but as I told you before, I had to act inmediatly.
I thought that flashing 2.2.1 again, I was able to update it via system update, but it wasnt possible.
josuearisty said:
Uuuuuuups, I alredy SBF it, the phone belong to my father and I had to give it to him yesterday
There was another kernel yes, side applications was enabled, it was faster than 2.2.1, there were less bloatware
And the most important thing is that the phone didnt say AT&T down the home button.
I am very sad because I couldnt even create a backup for system, I forgot about dd codes for backing up too, but as I told you before, I had to act inmediatly.
I thought that flashing 2.2.1 again, I was able to update it via system update, but it wasnt possible.
Click to expand...
Click to collapse
I've looked a bit on Google and haven't seen anything about a Bravo 2.2.2 system . And that includes translating a few Russian, Spanish, and Chinese sites. I sbf'd back to stock so I'm gonna install try looking on the cheesecake servers (hopefully they still work for us) and hope something happens.
Other than AT&T, what other carrier uses the Bravo? If we knew that then all we'd need to do is take a sim unlocked stock Bravo, connect to that network, and check for a system update. Bravo 2.2.2 might be carrier exclusive, and that carrier isn't AT&T. If it weren't for the different kernel version, I'd almost think that it came with a Defy 2.2.2 T-Mobile port (same way to port as CM7).
skeevy420 said:
I've looked a bit on Google and haven't seen anything about a Bravo 2.2.2 system . And that includes translating a few Russian, Spanish, and Chinese sites. I sbf'd back to stock so I'm gonna install try looking on the cheesecake servers (hopefully they still work for us) and hope something happens.
Other than AT&T, what other carrier uses the Bravo? If we knew that then all we'd need to do is take a sim unlocked stock Bravo, connect to that network, and check for a system update. Bravo 2.2.2 might be carrier exclusive, and that carrier isn't AT&T. If it weren't for the different kernel version, I'd almost think that it came with a Defy 2.2.2 T-Mobile port (same way to port as CM7).
Click to expand...
Click to collapse
I hope you get something, maybe you can ask somebody at AT&T, the answer maybe its there, maybe it was approved by AT&T.
I would like to help with that, but after flashing our SBF, you know there is no way to go back. Do you know anybody at motorola?
But there is no use now, we almost have jelly bean 4.2.2 with custom kernel.
Speaking about it, there have not been anything new with that, do you know something about?
2.2.2 = Consumer Cellular
Guys, I'm on Consumer Cellular and getting wife fixed up with Bravo that they sell/support. First one I bought had 2.2.1 on it and couldn't get MMS working. Found another on ebay listing says it was used on Consumer Cellular and photo of About Page shows version 2.2.2 and Version.38.6.0.MB520.Generic.en.US. I plan to buy the phone and will be glad to backup the rom and share it with you. Just need pointer to process to follow. I'm somewhat of a newbie (with android phones) but have flashed CM7 to the bravo and reflashed back to 2.2.1 sbf using rsdlite.
Toby
Making an SBF file is not an easy task. I think Consumer Cellular clients may ask their carrier for any help with stock rom.
bohdan4ik13 said:
Making an SBF file is not an easy task. I think Consumer Cellular clients may ask their carrier for any help with stock rom.
Click to expand...
Click to collapse
I see that now. If/when I get the phone, I'm willing to backup the 2.2.2 rom if a nandroid backup would be helpful.
tobewan said:
I see that now. If/when I get the phone, I'm willing to backup the 2.2.2 rom if a nandroid backup would be helpful.
Click to expand...
Click to collapse
Its not just to make a nandroid backup, we would like to get the bootloader too.
skeevy can help you getting the backup we need, using dd codes, I dont remember which were these codes, lets wait for him.
Thanks!
tobewan said:
Guys, I'm on Consumer Cellular and getting wife fixed up with Bravo that they sell/support. First one I bought had 2.2.1 on it and couldn't get MMS working. Found another on ebay listing says it was used on Consumer Cellular and photo of About Page shows version 2.2.2 and Version.38.6.0.MB520.Generic.en.US. I plan to buy the phone and will be glad to backup the rom and share it with you. Just need pointer to process to follow. I'm somewhat of a newbie (with android phones) but have flashed CM7 to the bravo and reflashed back to 2.2.1 sbf using rsdlite.
Toby
Click to expand...
Click to collapse
Well I'll be damned...someone actually still has the Stock 2.2.2 . The most important partitions we'll need are bootloader, devtree, and system. A nandroid backup will work for the system, but the bootloader and devtree should be dd off the phone. Make sure you have at least a gig of free sd space. I'm gonna be thorough and have you dump more than needed.
To make the copies you'll need to root the phone and have a PC handy with ADB working....PC not necessary but makes it much easier. Any of the adb shell commands can be done from Android Terminal Emulator.
For adb, open up a Terminal Window\Command Prompt
type "adb shell" to access the phones terminal environment
then "su" to be root user
For Android Terminal Emulator
Just open it and type "su"
Code:
Do all these commands as root with adb or Terminal Emulator.
dd if=/dev/block/mmcblk1p0 /mnt/sdcard/dump/mbr
dd if=/dev/block/mmcblk1p1 /mnt/sdcard/dump/mbmloader
dd if=/dev/block/mmcblk1p2 /mnt/sdcard/dump/mbm
dd if=/dev/block/mmcblk1p3 /mnt/sdcard/dump/mbmbackup
dd if=/dev/block/mmcblk1p4 /mnt/sdcard/dump/ebr
dd if=/dev/block/mmcblk1p5 /mnt/sdcard/dump/bploader
dd if=/dev/block/mmcblk1p6 /mnt/sdcard/dump/cdt.bin
dd if=/dev/block/mmcblk1p7 /mnt/sdcard/dump/pds
dd if=/dev/block/mmcblk1p8 /mnt/sdcard/dump/lbl
dd if=/dev/block/mmcblk1p9 /mnt/sdcard/dump/lbl_backup
dd if=/dev/block/mmcblk1p10 /mnt/sdcard/dump/logo.bin
dd if=/dev/block/mmcblk1p11 /mnt/sdcard/dump/sp
[B]dd if=/dev/block/mmcblk1p12 /mnt/sdcard/dump/devtree[/B]
dd if=/dev/block/mmcblk1p13 /mnt/sdcard/dump/devtree_backup
dd if=/dev/block/mmcblk1p14 /mnt/sdcard/dump/bpsw
[B]dd if=/dev/block/mmcblk1p15 /mnt/sdcard/dump/boot[/B]
[B]dd if=/dev/block/mmcblk1p16 /mnt/sdcard/dump/recovery[/B]
dd if=/dev/block/mmcblk1p17 /mnt/sdcard/dump/cdrom
dd if=/dev/block/mmcblk1p18 /mnt/sdcard/dump/misc
dd if=/dev/block/mmcblk1p19 /mnt/sdcard/dump/cid
dd if=/dev/block/mmcblk1p20 /mnt/sdcard/dump/kpanic
[B]dd if=/dev/block/mmcblk1p21 /mnt/sdcard/dump/system[/B]
dd if=/dev/block/mmcblk1p22 /mnt/sdcard/dump/prek
dd if=/dev/block/mmcblk1p23 /mnt/sdcard/dump/pkbackup
**don't upload these two unless you factory reset and don't enter any personal data**
dd if=/dev/block/mmcblk1p24 /mnt/sdcard/dump/cache
dd if=/dev/block/mmcblk1p25 /mnt/sdcard/dump/userdata
**************************************************************************************************
After that, mount your sdcard over USB and zip up the entire "dump" directory (/mnt/sdcard/dump) and upload that somewhere, preferably anywhere without a bandwidth cap. Should be around 350-400mb total.
The most important ones needed are in bold, though all could possible help. Other than system and cdrom, most should be under 4mb, 2mb, or 512k.
I tried to make this as easy as possible. You should be able to just go down the line and copy\paste everything.
Thank you. Even if its old, we'd still like any stock Bravo system that's not AT&T -- especially if it comes with a different kernel .
PM me if you need to get my attention since I'm not around the Bravo forums as much as I once was.
EDIT--Can you get a better screenshot of the kernel version? From the picture the kernel is the same as the stock one...I need the bottom line to verify.
Help: I bricked the consumer cellular mb520
I bought a Consumer Cellular version of Motorola Bravo MB520, and the device was sim-locked, so I was trying to do "soft-unlocking" using the defy method (http://forum.xda-developers.com/showthread.php?t=1483297).
I successfully rooted the phone, and flashed one of GB roms, WhateRabbitNextGen-2.1.1.
Then I flashed Baseband_change(EP93_U_00.59.01).zip to match the baseband version.
After that it booted straight to bootloader recovery every time.
So I flashed the sbf (p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf) to start over again.
But it kept rebooting, even worse now I can not load a CWM recovery mode.
The only thing I can access is sbf.
Is it possible to make a custom sbf to recover this phone?
If I buy another same phone, then can I make a restore file to flash this phone back to the stock status?
Solved
purpleid said:
I bought a Consumer Cellular version of Motorola Bravo MB520, and the device was sim-locked, so I was trying to do "soft-unlocking" using the defy method (http://forum.xda-developers.com/showthread.php?t=1483297).
I successfully rooted the phone, and flashed one of GB roms, WhateRabbitNextGen-2.1.1.
Then I flashed Baseband_change(EP93_U_00.59.01).zip to match the baseband version.
After that it booted straight to bootloader recovery every time.
So I flashed the sbf (p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf) to start over again.
But it kept rebooting, even worse now I can not load a CWM recovery mode.
The only thing I can access is sbf.
Is it possible to make a custom sbf to recover this phone?
If I buy another same phone, then can I make a restore file to flash this phone back to the stock status?
Click to expand...
Click to collapse
I found that I can still access stock recovery and could factory reset and solved the problem.
======
Note: If you bootloop and are stuck at the red M logo, you need to wipe data in stock recovery. To do that, hold the volume down button and continue holding it when you power up the phone. Then, once you see the triangle and android, press both volume buttons at the same time. After that, scroll down and select wipe data/factory reset.
=======
BTW, I am still looking for a solution to sim unlock this device.
I tried to buy an unlock code from ebay, but I got
IMEI: *********** Code: Code not found. (Rejected)
I guess the seller was doing for AT&T IMEI only.
You couldn't have hooked it up with a system dump first? Consumer Cellular phones are the only source for Motorola Bravo 2.2.2 factory system and different stock kernel\devtree. Us old school Bravo users really, really want that.
skeevydude said:
You couldn't have hooked it up with a system dump first? Consumer Cellular phones are the only source for Motorola Bravo 2.2.2 factory system and different stock kernel\devtree. Us old school Bravo users really, really want that.
Click to expand...
Click to collapse
Unfortunately I did not back up the system, but I reordered another one. I will upload it once I get it.
But why Defy soft-unlocking method does not work with Bravo?
Even with the same baseband version(EPU93_U_00.59.01)'s CM72 did not work for me.
After applying soft-unlock patch, it kept rebooting, and factory reset made the device not detect any sim.
Radio.img seems to be different from Defy, or maybe need just some simple tweaks.
purpleid said:
Unfortunately I did not back up the system, but I reordered another one. I will upload it once I get it.
But why Defy soft-unlocking method does not work with Bravo?
Even with the same baseband version(EPU93_U_00.59.01)'s CM72 did not work for me.
After applying soft-unlock patch, it kept rebooting, and factory reset made the device not detect any sim.
Radio.img seems to be different from Defy, or maybe need just some simple tweaks.
Click to expand...
Click to collapse
That would be awesome.
Soft sim unlock doesn't work because of radio.img. The soft sim patch replaces a few files under /system. You'll have to reinstall whatever rom you were previously using to get the radio working again. Factory reset shouldn't be necessary.
It's August of 2013. Needing more room on my SD card, I decide to delete my Consumer Cellular 2.2.2 backup. A week passes, and I find this thread. I originaly deleted it because I thought nothing of it, I figured all Bravo's had 2.2.2 froyo. Boy was I wrong. If I still had it, I sure as hell would have uploaded all that I could to help you guus out. If only I had found this a week earlier.
Just felt like I had to share that little story with the world, how I was so close to actually doing something monumental in the developing community.
---------- Post added at 10:18 PM ---------- Previous post was at 09:59 PM ----------
*BUMP*
You know, if anyone out there has 80 bucks they are willing to put forth to the good cause of 2.2.2...
http://www.amazon.com/gp/aw/d/B00B8B3G9W/ref=mp_s_a_1_1?qid=1398305766&sr=8-1&pi=SY200_QL40
Sent from my Rugby Smart SGH-I847 on the official XDA app!
Apologies for bumping an old thread, but I have two bravos: 2.2.2 and 2.2.1 ..Do you guys still need backups? I have no idea what's going on here or why it's considered so monumental in the developing community, but I'd like to know and I'm willing to help you guys out if it's still needed.
I also have a system dump and a CWM backup of an original 2.2.2 Consumer Cellular Bravo. Let me know if you guys still want it.
Markus
Well, most of us have move to newer phones, I have a Droid Ultra and a Razr M and with gingerbread working 100%, any froyo version its not very useful at this time.
Related
Hello, I just got a Motorola Milestone X. Its running on ACS alaska network. From reading I've done this phone appears to be the moto x but just not the vws branded phone? My question does anyone know of a way to root it and or any custom roms for it? Its filled with bloatware and no way to remove it and the stock rom is very ugly.
Ive tried z4root, superoot, androot and various other rooting guides that were supposed to work on the Moto X but all have failed me. Its running 2.2.1 and from what I gather this might be the problem?
Any help or info from anyone else familiar with this phone would be greatly appreciated as I hate it in its current stock form and would like to at least be able to remove the bloatware and crap I dont use even if there arent any custom roms for it. Thank you
Possible root
I also have a milestone x from a local carrier, and was able to root it.
I downloaded and installed all the Motorola drivers.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Hooked the phone up and went through each mode to ensure all the drivers were installed.
I then installed the latest version of SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682
I then extracted and ran SuperOneClick, chose the psneuter exploit and clicked root. This was able to root the phone. I did need to reboot the phone before the superuser application would work though.
I haven't looked into custom roms yet.
thank you very much for the information. I tried super one click but it would always lock up but maybe i'll give it another try. Is your phone running 2.2.1? Thanks again for the reply.
Inciner8Fire said:
I also have a milestone x from a local carrier, and was able to root it.
I downloaded and installed all the Motorola drivers.
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Hooked the phone up and went through each mode to ensure all the drivers were installed.
I then installed the latest version of SuperOneClick from http://forum.xda-developers.com/showthread.php?t=803682
I then extracted and ran SuperOneClick, chose the psneuter exploit and clicked root. This was able to root the phone. I did need to reboot the phone before the superuser application would work though.
I haven't looked into custom roms yet.
Click to expand...
Click to collapse
I must have used a older version of SuperOneClick before. This one you linked worked with no problems at all. Thank you so much!
No prob, glad it worked for ya.
Thanks for the post. I was going through the same frustrations with my new ACS Milestone X. I see now that there is a new version of SuperOneClick ... anybody else trying to make this work, make sure you use v1.7.
So back to JDinAZ74's second question ... now that we've rooted are there custom roms for our CDMA version of this phone? I see tons of roms but none that I've noticed specify GSM or CDMA, which usually means it's GSM. Anybody know for sure?
the dx is on verizon, so its all cdma. i not sure it would matter though...
Yeah I'm not sure it matters either ... I know on my HTC Desire it mattered. If I flashed it with a GSM rom it would not boot.
Okay so somewhat unrelated ... i've got bootstrap installed and was able to do a rom backup via clockwork recovery. Is there a way to boot into recovery from the device being off? I tried every combination of buttons while pressing the on button but nothing works. I've looked all over the forum (and googled) but can't find anything.
I want to start installing custom roms but am affraid of something going wrong and me not being able to reflash my backup.
Then again maybe I'm just confused because I'm coming from a Desire which I've discovered Motorola and HTC modding differs significantly.
Im still looking for roms as well and kinda afraid to just start trying things like you said. If you come across anything that works let me know and ill do the same.
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
mattmartin77 said:
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
Click to expand...
Click to collapse
Wouldn't the SBf only work on a Droid x?
mattmartin77 said:
to get to stock recovery, hold power and home till the moto logo appears, then release the power button until you get an exclamation point, then let go and click the search button.
to get to cw recovery, do a battery pull and reboot.
if you completely **** your phone, sbf.
Click to expand...
Click to collapse
Fantastic! Thank you.
I don't know that they could do an sbf being on a non Verizon carrier. The sbf files out are all for Verizon. If you do screw up your phone you would have to take it into the store and have them sbf it. And they might not. I think you guys just need to be a little careful. Unless you can find an sbf file from your carrier. Try apex, rubix, or liberty roms for flashing. All the roms are cdma. Good luck and be careful.
Sent from my DROIDX using XDA App
The milestone x uses the same RSA key for its bootloader as the original Droid X. You CAN flash a Verizon SBF into it and it will work, HOWEVER, it will NO LONGER work with your carrier. It is also important to note that ANY SBF will overwrite the baseband AND the baseband configuration (unless specifically noted NOT to do so) rendering the phone useless, requiring re-programming, which for the voice part is no big deal, but to get EVDo working again you'll need to edit some non-user accessible parameters with QPST and what not to get it to connect back to the non verizon carrier.
What you CAN do with this phone is non-baseband patching updates/roms. If you've got a Milestone X you're not on verizon, so you're not able to use the leaked SBF's and what not, which removes a decent safety net. So flash with caution. If your carrier is small enough they are likely to re-sbf your phone for you if you brick it.
One last word of caution.. Verizon's DX on leaked GB's updates the BL to a newer version than is on the Milestone X. This will turn your phone into a Droid X, with no ability to go backwards until the same BL is available on the Milestone X.
In short, we non VZW DX owners have a lot less fun..
Bollocks to that.
really wish I knew if someone had tried, I really want to try that leaked gingerbread.
went ahead and took the plunge with... SUCCESS. I installed Liberty 2.0.1 and nothing went wrong, you just got to be more careful than others who have the sbf backup.
Went to ACS today because i'm considering this phone, ACS is partnering with Verison(GSM), and GCI is partnering with Sprint (CDMA).
Just incase it's not clear i'm sure roms for Verizon will work for ACS and roms for sprint should work with GCI.
Double check incase i have the two "bands mixed up" i know i have the carrier relationships right.
Does anyone know if we can overclock with out romming?
I tried droid overclock a few times which always sent the phone into a boot loop. Id have to pull the battery and do a factory reset to get it running again.
Hey there, I recently purchased a Bell Atrix 4G. I rooted it and everything was going fine, so I thought I'd try the gingerblur rom for the device, the tutorial site didn't mention anything about not using it on a Bell Atrix, which I found out later was a bad idea (I did make a backup though at the backup prompt). So needless to say the phone is now at the "M screen flashing red led boot loop". What I wanted to know, is if that since I have access to fast boot, if there's any way to restore from that backup.tar file, or if I can use an at/t sbf file to restore to (I didn't try it in fear of making things worse). Thanks in advance!
Grimacexl said:
Hey there, I recently purchased a Bell Atrix 4G. I rooted it and everything was going fine, so I thought I'd try the gingerblur rom for the device, the tutorial site didn't mention anything about not using it on a Bell Atrix, which I found out later was a bad idea (I did make a backup though at the backup prompt). So needless to say the phone is now at the "M screen flashing red led boot loop". What I wanted to know, is if that since I have access to fast boot, if there's any way to restore from that backup.tar file, or if I can use an at/t sbf file to restore to (I didn't try it in fear of making things worse). Thanks in advance!
Click to expand...
Click to collapse
Whatever you do DO NOT USE THE ATT SBF! That is not meant for bell devices and will definetly make your situation even worse!
Yeah, I figured that would be the case.
Working on trying to push my backup files to my device atm
Grimacexl said:
the tutorial site didn't mention anything about not using it on a Bell Atrix,
Click to expand...
Click to collapse
dude, it's in CAPITAL RED LETTERS on both the tutorial website and the forum thread.
this guy had a similar situation, but i don't know if he got it fixed.
http://forum.xda-developers.com/showthread.php?t=1033184&highlight=bell+sbf
EDIT: attached
Yeah, the tutorial I used didn't say to not use it on bell atrix, but when it messed up, I went to all the other tutorials that have it in red, so I do feel pretty stupid.
Well, it's all good now, After pushing bell backup app and framework folders, I managed to get a working device (all be it with some force close crap which I'll iron out later) The device is working.
I tried to use the rooted 3.2.2 rom that was listed under development, but I could never get my wifi to connect. Now I am unable to get my 4G to work. I used to have the option to choose preferred network mode LTE/CDMA, but now that no longer shows. I am on 3.2.2 using build HLK42B.
I was wondering if someone who received their xoom back from the upgrade has the latest image I can try.
Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
Sent from my Xoom using xda premium
I wish I knew.. I will have to research that.
Sent from my PG86100 using xda premium
I just posted an upload link over at http://forum.xda-developers.com/showpost.php?p=18204881&postcount=13
hammer4203 said:
Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
You need to flash the modded recovery, then in adb shell, run
mount /data
mkdir /data/media/Stock
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/data/media/Stock/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/media/Stock/boot.img
sync
Then reboot and pull the files, should be in a "Stock" folder on the internal storage.
*Thanks to solarnz for these instructions
Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P
4G LTE
I got my Xoom back some time ago. I've been waiting to root it until it came back. (Really didn't want to go through it, and have to undo it just to figure out how to do it again)
I'm trying to find the official file from Moto for the HLK42B build that came back on my 4G Xoom. I'm on the Moto Dev site, but they only have up through the 3G upgrade listed. Anybody know where I can get the official file in case anything goes wrong? I want to make sure I have it, before I start.
Thanks
Thanks Ace, it worked for me. It wasn't rooted because I imediately got and updated to HLK57D
AceXMachine said:
Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P
Click to expand...
Click to collapse
Thanks for the img files. They will save many headaches for a lot of people.
It is a damn shame that Motorola will not post the updated img files though...
I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).
I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.
zarkuu said:
I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).
I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.
Click to expand...
Click to collapse
This is my same exact problem. Can't seem to figure out the baseband problem.
I wonder if anyone has contacted Motorola regarding a way to flash the baseband to the LTE 4G version?
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
You can get the hlk75c which is rooted then take the hlk75d update and reroot using the universal root method. That will put you back.
Sent from my ADR6400L using xda premium
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
Oh, duh, it's so simple. I'll definitely be trying this when I get home from work today.
If it works - you will be my savior.
Scratch that - it didn't even reactivate my 3G.
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
I don't think that will work unless you open it up and physically remove the LTE modem. my understanding is once the LTE modem was installed the internal 3g modem is deactivated. Even if this did work it would deactivate your SIM card so you wouldn't be able to use LTE in the future without getting a new one. I had the idea to switch my currently useless Xoom data plan over to my old OG Droid and then wifi tether. I asked VZW about switching and found I *could* do this but going from a 4g device back to 3g would deactivate the SIM card and I won't be able to switch without getting a new one. Too much trouble in my opinion.
I spent about 2 hours in a Verizon store yesterday after 2 hours on the phone the previous night and eventually ended up with an RMA with Motorola. I'll be returning it to them and hopefully it will come back correct in about a week. Such a hassle when I could probably flash this myself if I had the right files but at this point I don't know what else to try.
Can you repost link please. I am trying to get this on a Mac running OSX and I cant seem to unzip the file. Any suggestions?! PLease HELP!!!
---------- Post added at 09:22 PM ---------- Previous post was at 09:09 PM ----------
how do you unzip HLK75Csystemboot.7z on Mac OSX??? Please Help!!!
download 7zip or use winrar
Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.
zone23 said:
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.
Click to expand...
Click to collapse
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.
Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.
Jewremy said:
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.
Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.
Click to expand...
Click to collapse
It restores your device but it will not bring back 3G/4G. If it does please tell me how because I've flashed it a few times and it did not bring back 3G.
Actually in reading your post a few times you say it yourself that its a borked bootloader. Flashing HRI66 will not fix this. If it did we would be finished and we could close this thread.
So here's my deal. The other day I was doing fine, and I had a version of CM9 that I got from here. I tried the dev's latest version and it was a little wonky so I tried to restore my ClockworkMod backup if his previous version that worked better. And I bumped the cable while it was in process, and that stopped the flash and got me stuck with a non-booting system.
So then I decided I'd reset the phone, re-root, and then I could restore a backup. The first part went good, and then without thinking I accepted Verizon's update.
I found someone saying that I could flash this non-Verizon SBF to it, and it worked but it's for some "nTelus" carrier that apparently isn't here in Michigan and I can't figure out how to put Verizon on it. I tried *228 and it gave me the "Activating your phone" screen but the robovoice on the phone just told me that I wasn't authorized to do something and then said something in Spanish.
I know I can just put Verizon's new ROM on there and it'll work but I prefer to have CM7 or CM9, and either way I definitely don't want their crapware. ClockworkMod is the only backup I have but it obviously does me no good when the phone isn't rooted so I can install ClockworkMod.
So my question is this: is there a way I can root Verizon's new ROM, or revert to an old ROM, and if not then is there a way to make the nTelus ROM know that it should be using Verizon's network?
You have to flash the non Verizon SBF (version .604) but you cannot use RSD Lite, you just use the Linux method.
Now you need to use RSD Lite to return your phone to stock Verizon .621. This will fix your activation problem.
Then, download 1KDS's .604 Live Linux CD and use it to flash the rootable SBF.
Sent from my DROIDX using Tapatalk 2
Thanks, I'll try that when I get home.
Anyways, something I'm about to try, I'll let you know the results. I've found a small section of text in these files that appears to have the Access Point Names and connection data for the carriers. In the nTelos file there's only one carrier, in the Verizon file there's Verizon, ATT, and others. So I'm going to copy-paste-pray and I'll let you know how it works. If it goes smoothly I'll post the resulting file somewhere.
EDIT: Nope, it didn't work. C'est la vie.
OK so it sorta worked... I guess. But now I have no data connection...
Great.
I was flashing ROMs and had DLed a bunch from a site exclusively for RAZR M phones and some guy had put a bunch of stuff for the XT910 and I accidentally flashed a AOKP GSM zip and now I can't flash anything or RSDLite back to stock, which was always my failsafe out of a soft brick. I still have TWRP and I was able to restore my backup but boot and system files only, data wouldn't restore. Now my phone will boot to the custom splash screen but it just loops. And I first get the red Moto M circle and do NOT get the unlocked boot loader warning. So any help? I will post the RSDLite results when I get home.
ok heres the site I got the file from, this guy should be hung...surdu_petru...http://www.androidfilehost.com/?w=developers&did=70
noone? help is needed please! OK well I restored to a TWRP recovery i had and it worked partially, as long as i unchecked the data partition, the boot and system partitions stuck, so now my unlocked bootloader warning is back as is my custom ROM splash screen, but in a bootloop. I tried RSDLite flashing it again and the 4.1.1 firmware seemed to work but still loops. 4.1.2 and 4.0.4 wont flash because of the "get var, OEM" issue. I had this happen once before aswhile back but was using CWM recovery and juyst switched to TWRP, which fixed it, but not so lucky this time around. So I am wondering if i flash some other partitions like the persist forthe radio, esp since i flashed a xt910 GSM file which is why my phone now thinks its a xt910. Any ideas? please!!!
ok PROBLEM SOLVED. aFTER LOSING THE CUSTOM RECOVERY BY TRYING TO FASTBOOT WITH RSDLITE I DID THE "delete the Getvar and OEM LINES FROM THE FACTORY FIRMWARE OF 4.1.2 (THE .78 VERSION) AND SINCE THE xt910 ROM WAS 4.2.2 AND MY RADIO HAD PREVIOUSLY BEEN UPDATED TO .78, I FIGURED THE .78 4.1.2 WOULD BE MY BEST SHOT, AND SO IT WAS. THAT "GETVAR" ISSUE IS DEFINATE PROBLEM THAT SHOULD BE RESOLVED ANYWAY. wELL ANOTHER TRAGEDY AVERTED, AND IM GETTING PRETTY GOOD AT THIS, LOL, AVOIDING MISTAKES WOULD BE BEST THO. sO BEWARE OF THE "ANDROIDFILEHOST" SITE, THEY HAVE A GUY POSTING XT910 ROMS UNDER XT907 FOLDER! almost cost me a phone Close this thread
Edit does not work on either of my razr m phones
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Here is my Feedback for you...
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The phones will accept the edit and will work on GSM if you unlock with RadioComm. He ran into issues because he didn't unlock with RadioComm.
Sent from my Droid RAZR MAXX HD using xda app-developers app
ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
Sorry but they both unlocked. The issue was (I think) that I was typing "01" but only needed to actually type "1" and then the window shows "01". It was something like that anyway.
soft bricked now
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
rocketrazr99 said:
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
Click to expand...
Click to collapse
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
RikRong said:
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
Click to expand...
Click to collapse
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
rocketrazr99 said:
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
Click to expand...
Click to collapse
OK, Rik was right, I didnt have to wait for a new firmware release. I kept trying to flash the most recent version of 4.1.2 and kept hitting a wall at 17/21, which is the flashing of the system image. Occasionally it would fail before that at 16/21, which is CDROM files. That always happened the first attempt after I unhooked the phone and restarted everything, so I started thinking, what is causing the flash to fail for no apparent reason. Then it finally hit me....it was as if my phone was running out of storage space. But that just isnt possible when you are flashing with RSDLite since it wipes out everything first. So I then remembered that my PC has very little room left on its hard drive. Could it be that RSDLite needed more space to work? Hmmmmm, so I deleted a few videos and moved the firmware file to that area (it may or may not help) of the drive and tried again. After the initial fail at 16/21 I was met with a successful flash, although it took a very long time to flash the system image, which I attribute to low disk space. So there you have it.... of course I had to modify the XML file and remove the "getvar" line, and realized I had forgot a golden rule.... all programs and apps need a certain amount of disk drive space in order to operate, and RSDLite is no exception! So now my locked phone will get the carrier unlock edit and Safestrap installed with an extra ROM in slot 1, then it goes on eBay, lol. I have my other RAZR M in semi retirement, it has the BL unlocked as well as the carrier, but I couldnt pass up a new Nexus 5 for $250, but I will surely be swapping the SIM card back and forth because I really miss my RAZR M already. Wish they would make a RAZR M with the processing power of the Nexus 5. Anyhow, PLEASE CLOSE THIS THREAD, TY.
Use this I used it when I bricked mine
Sent from my XT907 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2249773
Sent from my XT907 using Tapatalk
I'm having a similar problem with my xt907. The phone will boot and loop on the boot loader. I have tried to restore with rsd lite bit haven't had any luck. Any suggestions, I know it may not be enough information. If you ask I might be able to give you more details.
---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------
Also I can't get into recovery.
ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
I am sorry to say that you are uninformed and the XT907 CAN have van NV edit which allows it to be used on GSM networks. The phone is already setup to be comparable with GSN since Verizon made it a "global" handset, but....they also blocked any GSM capabilities in the U.S., until of course you do the NV edit. So please remove your post.