Database Users

[3g STOCK .IMG] VZ WIRELESS MX600 5/3/2011

Here are the .IMG files that Motorola has posted on their MOTODEV site. .
ATTENTION: DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
These files are from Motorola's Development site but I take no liability with anything that happens with your device if something goes wrong.
Official HRI39 Motorola .IMG files:
http://www.multiupload.com/9XP1B8LSWC
Official HRI66 Motorola .IMG files:
http://www.multiupload.com/POUDJY1255
The following are the steps from the MOTODEV site
1. Extract files into android sdk /tools folder.
2. Start command prompt/ terminal from the android sdk tools folder. (How this is done on Mac I do not know, Windows: shift+left click and select "open command window here")
3. adb reboot bootloader
4. fastboot flash boot boot.img
5. fastboot flash system system.img
6. fastboot flash recovery recovery.img
7. fastboot flash userdata userdata.img
8. fastboot erase cache
9. fastboot oem lock
The device will lock and reboot.
You are now back to out of box state. However I do not know if it is still detectable by VZ Moto if you have unlocked the device after doing this.
Also fyi the sbf file is still an option but you will have to go in and do the fastboot oem lock after it completes

u mispelled cache

Fixed. Thanks had a long day and missed that at proof reading

Thanks for the files, does seem a lot simpler to just use the sbf file though.

bwcorvus said:
Thanks for the files, does seem a lot simpler to just use the sbf file though.
Click to expand...
Click to collapse
Its always good to have more options and the Xoom gives us many and hopefully soon sdcard support will provide the final key piece, the CM recovery!
In the meantime it is very good to have all of the official files at our disposal.
If anyone is wondering what the the reflash file from the first leak is, it is an SBF format installation of the stock boot image and a blank user data image to wipe data and return to stock via RSD Lite without touching the system partition.
This provides yet another way to reset that should be examined, especially if it works over a modified system partition.
We also may be able to use any or all of these files to build our own SBF files and other one step solutions for recovering and or modifying the Xoom. This can be very valuable and must also be thoroughly explored along with the NVM so we can really start to tak better control of the radio functions.
Lots to look at...

I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.

jmc2543 said:
I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.
Click to expand...
Click to collapse
Yea having these images is one BIG step...now we just need sdcards

Just finished doing this. I'm back at stock. Of course no I'll b the last to get an update. And by the same time tomorrow I'll be unlocking and re-rooting.

by doing this does it erase everything on your xoom?

bishop72 said:
by doing this does it erase everything on your xoom?
Click to expand...
Click to collapse
Yes it would. Itll bring it back to what it was like when you first bought it.

For those that updated, were you able to reroot?

17akota said:
Yes it would. Itll bring it back to what it was like when you first bought it.
Click to expand...
Click to collapse
I saw multiple threads about Titanium backup not working with the Xoom. Are there alternative apps that will save all my configuration like home screen layout etc? It was a lot of work B-)
Sent from my Xoom using Tapatalk

It is just Android 3.0
3.0.1 is HRI66

Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?

Aaron636r said:
Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?
Click to expand...
Click to collapse
Oh no. I did the "fastboot oem lock" and now I get "Failed image LNX 0x0002". Cant boot past Dual Core logo screen.

Ok, re-unlocking it fixed it.

Ok so we have the original flash so we can get the OTA thats great. And Moto confirmed on their forum they will upgrade devices that have been unlocked and rooted. If they cannot install the software they will ship it back with just the new hardware. Can't wait to see what people can really start doing now.

For those of you that are like me and hate having to using mega upload and crap to download things here is a direct link on my web server to the file released by Moto.
DMCA Noticed by Moto
This was taken directly from the Moto Dev site myself.
If you browse the directory, which I think I left on for this one... There is also the sbf archive and RSD there to download. If anyone needs a place to store some files let me know. I have unlimited storage and bandwidth. When some of the OG Droid releases came out I was pumping over 11GB a week in downloads with no issues. It's the least I can do to help the community.

I got to be honest I don't know what the hell i should do to get the update and what will cause me to either have a clean install or lose root

All reports so far indicate it will not break root and rooted users have been getting the notification. They are also probably doing a controlled rollout if you have not yet gotten the notification. My XOOM is at home right now which sucks I won't be able to get my hands on it for about 6 hours and see what I can all do.

Need help fixing bricked moto x pure (will pay if it gets fixed)

So yesterday I picked up my brand new moto x pure.
I unlocked it no problem using the guide on Motorola site no problem here.
I then installed twrp without any hitches.
I then decided to install supersu which then bricked my phone, me panicking I then decided to wipe the device (including the OS and recovery) so now I am stuck with a very expensive paper weight.
I have tried connecting to the phone with adb but all I get is no devices found.
If anyone can help me fix my phone be it through pm or Skype or w.e. I will happily throw some money there way just because it is urgent I get my phone up and running.
Oh yeah and my moto x is the unlocked international version as I live in the uk.
Sorry of this is in the wrong place but I really am not sure what else to do.

santacl4ws said:
So yesterday I picked up my brand new moto x pure.
I unlocked it no problem using the guide on Motorola site no problem here.
I then installed twrp without any hitches.
I then decided to install supersu which then bricked my phone, me panicking I then decided to wipe the device (including the OS and recovery) so now I am stuck with a very expensive paper weight.
I have tried connecting to the phone with adb but all I get is no devices found.
If anyone can help me fix my phone be it through pm or Skype or w.e. I will happily throw some money there way just because it is urgent I get my phone up and running.
Oh yeah and my moto x is the unlocked international version as I live in the uk.
Sorry of this is in the wrong place but I really am not sure what else to do.
Click to expand...
Click to collapse
Boot into bootloader.
fastboot devices
Should return device connected just like you did unlocking bootloader and flashing recovery.
Flash recovery through fastboot.
Flash rom through recovery (mtp, otg, from device sdcard, etc)
If you have mm bootloader, it's mfastboot.
mxpe 6.0

santacl4ws said:
So yesterday I picked up my brand new moto x pure.
I unlocked it no problem using the guide on Motorola site no problem here.
I then installed twrp without any hitches.
I then decided to install supersu which then bricked my phone, me panicking I then decided to wipe the device (including the OS and recovery) so now I am stuck with a very expensive paper weight.
I have tried connecting to the phone with adb but all I get is no devices found.
If anyone can help me fix my phone be it through pm or Skype or w.e. I will happily throw some money there way just because it is urgent I get my phone up and running.
Oh yeah and my moto x is the unlocked international version as I live in the uk.
Sorry of this is in the wrong place but I really am not sure what else to do.
Click to expand...
Click to collapse
I have bricked my Droid OG, Droid 2, and Droid Turbo just tell Motorola you didnt want the most recent OTA update and you accidentally installed it, but you were happier with the stock image and you would like to go back to that image. Then they will send you a shipping label and they will fix your phone in about a week turn around. Motorola is pretty good about this, dont mention your phone bootloader is unlocked just say its not booting up and you want the stock image back.
Otherwise go here. and download all the items in the description, then just go step by step
Good Lucky. Hope this helps. https://www.youtube.com/watch?v=6avEPGWB8E0

InFamousD147 said:
...
Otherwise go here. and download all the items in the description, then just go step by step
Good Lucky. Hope this helps. https://www.youtube.com/watch?v=6avEPGWB8E0
Click to expand...
Click to collapse
Exactly how is firmware for the droid turbo going to help the OP with a moto x pure??
Might really end up with a hard brick after that
To the OP, I hope you recorded your system version number from the about screen before starting down this path. If not, grab the marshmallow ota firmware from one of the threads.

gpz1100 said:
Exactly how is firmware for the droid turbo going to help the OP with a moto x pure??
Might really end up with a hard brick after that
To the OP, I hope you recorded your system version number from the about screen before starting down this path. If not, grab the marshmallow ota firmware from one of the threads.
Click to expand...
Click to collapse
Whoops!.:highfive: Thanks for the catch (used to own turbo). Use this video link for instructions.
https://www.youtube.com/watch?v=qjbU72RH_Rk&spfreload=10

OK, this is a loooong story. Can someone save my xperiac4?PLS...........

I have a xperia c4 e5303, is a awesome device and 5-6 days ago i wanted to use xposed firmware to enable a fake gyroscope.
AND THE HELL STARTED.
I had the device rooted with custom recovery twrp when i was in lollipop 5.1, i installed the firmware for xposed and the phone was stucked in "android optimization", for hours. I restarded it sometimes but nothing, so i formatted my device and when i rebooted it, i was stucked in "sony" logo screen, some minutes ago i founded that my phone was totally empty.
c: *internal screaming*
I waited the next day, i downloaded the ftf of original marshmallow 6.0 firmware for sony xperia c4 and i installed it on my device, then everything worked perfectly luckely.
Easy peasy lemon squeezy, or not?
Some hours after i founded that i couldn't use the recovery mode!
I searched and searched and i founded that the problem could be the bootloader,so i used a sony official guide to unlock that.
I couldn't finished that guide becouse with any connection, on any computer, android sdk can't install his components(such as google usb driver, that are required for that method), and the program just install everytime the same package in loop. I tried aaaallll the method in the universe for that, i tried also to install once per once the zip files of the downloaded package but it was totally useless.
So i founded another method after some days of searching (with flashtool) and now my bootloader is fully unlocked, if i use flashtool to unlock the bootloader, it says that is unlocked and ask me if i want to relock it so i think now the bootloader unlock is done. FINALLY.
Then, i turned off the phone and started it by pressing the volume down+power botton, and all the device did was reboot himself repitetly until i release hard keys and when i do it the phone start automatically.
I think my device now reboot himself instead of going in recovery mode.
What can i do i am totally frustrated about this and i really don't want to buy a new device becouse i don't have a gyroscope. I love my xperia c4, i just don't know why i can't get the recovery mode back to install twrp, for rooting the device, for retry to get xposed virtual sensor and then finally enjoy my vr experience...
In the end, i have a Xperia C4 5303 with original Marshmallow 6.0 firmware installed, that can't go in recovery mode in any ways.
Pls someone help me..

no one?..
No one here know hot to save my smartphone?

update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..

asnachan said:
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
Click to expand...
Click to collapse
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs

thx
Bludwurst said:
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..

asnachan said:
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
Click to expand...
Click to collapse
Ah. You should've mentioned it (i.e. linked to the guide). Sorry sorry!
Read further down. The "recovery.from.boot.p" is this thing that overwrites TWRP with the stock recovery. Following the «THIS IS IMPORTANT» indication are instructions to get rid of the thing, and so being able to keep TWRP permanently.
You need that last step to succeed.
Sent from my Motorola Moto G using XDA Labs

in the other thread they said to me to roll back to 5.1 i am doing it now

nvm i got hard brick, the phone is dead and i can't enter in download mode....

asnachan said:
nvm i got hard brick, the phone is dead and i can't enter in download mode....
Click to expand...
Click to collapse
I'm very sorry to hear that ?
Sent from my Motorola Moto G using XDA Labs

Is fine, i had to buy another phone that is why is tarted to root the xperia.
just..i'm out from the world of rooting i think. i broke 2 devices 1 by flashing a original rom with sony original flashtool and 1 by installing a root with kigroot, and now on that i can't read the sim.
i wait until the world of rooting will be more stable and with more official custom roms...

RIP

HELP: Rooting Essential PH-1 on android 9

Guys, I'm at my wits end here. I don't know what to do. And it's driving me crazy.
After saving for 3 months, I got a used Essential Ph-1 from craigslist (for sprint). It came with Android 9, and a February 5, 2019 security patch.
All I want to do is to root the phone. And I have tried everything in my power to get it to work. It just does not. I have unlocked the bootloader, I'm seeing the device in adb and fastboot, but unable to sideload, or flash anything. I've been following different threads on here and youtube looking for directions, but my phone will just not do it.
Can someone please help me? I will send my phone over to you and pay you to have it done. I've tried almost everything to do it, and nothing works. I've even tried to flash android 8 and 7, it still doesn't do it. Someone please help me. I don't know what more i can do. Any guidance is appreciated.

Can someone please help me? I don't know what more to do. Please.

Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?

goofball2k said:
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
Click to expand...
Click to collapse
No. I can't sideload or boot into anything other than the android 9

I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...

kt-Froggy said:
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
Click to expand...
Click to collapse
I tried that too. But it kept saying unable to unpack boot image | installation failed.
I tried it with the stock images from the Essential website, both the OTA and fastboot versions. I'm getting the error for both files.

I would suggest checking out the PH1 Dev telegram group https://t.me/EssentialPH1DEV . not only will you find pre rooted stock boot images along with ones with TWRP as well you will also find help flashing them if you need it. Hope this helps you out.

Thank you everyone for all your help. Special thanks to kt-Froggy. I got it to work. I had to change my usb port from 3 to 2 and i was able to get it to work!

Cant get OTAs to install on Perry

Problem is in the title. Here are the Cliff's Notes:
1) got Moto E4 from Textnow
2) fastboot boot TWRP.img (cant recall which image I used but pretty sure it was proper. if this makes a difference I can dig out the TWRP I used and attach it, but I really cannot recall which one it was. Pretty sure I got it from xda though, not the official TWRP page)
3) took TWRP backup of bone-stock device.
4) unlock bootloader at Motorola.com
5) check out the custom roms and found out about the LTE problem. Seanstars fix didnt work for me on several roms, but in his defense I may have done something wrong. I didnt want to mess with it anymore and decided to go back to stock.
6) I found out that I lost my bone-stock-TWRP backup through my own idiocy. I honestly have no idea how I got back to stock but I managed it. Seems to be awful hard to get a stock rom to work with. I must not be looking hard enough but it seems like all the links for Perry stock roms here are dead.
Now to the problem.... after all that I cant get OTA updates. I get notifications, the update downloads,, but no joy.
Device does *not* restart after the update downloads.
Manual restart begins the update process, but then I get the Android on the Operating Table screen. I relocked the bootloader thinking that might be the issue, but now I fear that there is some sort of signature verification issue that is stopping the update.
Trying to give relevant info from the bootloader:
Baseband: M8920_15000.280.06.58.02R PERRY_NA_CA_CUST
Product/Variant: perry XT1766 16GB P3B
I really dont know where to go from here though. Any help is appreciated, thanks in advance.

knoober said:
Problem is in the title. Here are the Cliff's Notes:
1) got Moto E4 from Textnow
2) fastboot boot TWRP.img (cant recall which image I used but pretty sure it was proper. if this makes a difference I can dig out the TWRP I used and attach it, but I really cannot recall which one it was. Pretty sure I got it from xda though, not the official TWRP page)
3) took TWRP backup of bone-stock device.
4) unlock bootloader at Motorola.com
5) check out the custom roms and found out about the LTE problem. Seanstars fix didnt work for me on several roms, but in his defense I may have done something wrong. I didnt want to mess with it anymore and decided to go back to stock.
6) I found out that I lost my bone-stock-TWRP backup through my own idiocy. I honestly have no idea how I got back to stock but I managed it. Seems to be awful hard to get a stock rom to work with. I must not be looking hard enough but it seems like all the links for Perry stock roms here are dead.
Now to the problem.... after all that I cant get OTA updates. I get notifications, the update downloads,, but no joy.
Device does *not* restart after the update downloads.
Manual restart begins the update process, but then I get the Android on the Operating Table screen. I relocked the bootloader thinking that might be the issue, but now I fear that there is some sort of signature verification issue that is stopping the update.
Trying to give relevant info from the bootloader:
Baseband: M8920_15000.280.06.58.02R PERRY_NA_CA_CUST
Product/Variant: perry XT1766 16GB P3B
I really dont know where to go from here though. Any help is appreciated, thanks in advance.
Click to expand...
Click to collapse
A number of partitions need to be pure stock for OTAs to work on Moto devices - including many that are not normally mounted. Likely one or more was altered by previous tinkering. Obviously system (never mounted r/w) and recovery; data must not have had dm-verity disabled. Etc, etc.