Related
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.
Hello, so this is my first time trying to root an android device, and I think I messed up. I watched a tutorial on youtube on how to do it and successfully installed superuser and twrp from a batch file ( I had to install adb drivers first ). I wasn't really sure I did it in the correct steps, so I wanted to revert back to the stock os. I booted into twrp and wiped the data ( cache, system, etc) from twrp. I then mounted it and transfered the kindle fire update 6.3.1 to my KF. I used the option on twrp to revert back to stock using the newly transferred zip. It ran for awhile then prompted me to click reboot. So I did. And this is where it gets tricky
After the reboot, all I see is the boot screen displaying "kindle fire." It never booted and lasted like this for hours. I tried to boot into twrp but I think it got deleted. I googled the problem and found it was in some sort of fastboot loop. I tried many fixes, using adb and other fastboot commands. Every time I tried anything, all I got was "waiting for device." Also, I couldn't use adb shell because it said system/bin/sh was not found. I went to my computer and found that the kindle fire no longer showed up as a removable device, but it showed up in device manager as adb composite interface under android phone. I thought that somehow all of my system files got deleted and thats why it says system/bin/sh not found. I tried to use the adb push command to manually send the update.zip to the KF but it is no longer a mounted drive, so there is nowhere to send it to. I'm at a loss here, Ive tried numerous utilities such as KFU, firekit, unbrick utility. I just need to figure out a way to remount the KF and copy over the folder "system" in the update.zip. If anyone could help me that would be great, as I have been trying to fix this for three days now.:fingers-crossed:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
tazmanhawaii said:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
Click to expand...
Click to collapse
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Marblesnake said:
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Click to expand...
Click to collapse
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
soupmagnet said:
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help. Yeah, I tried the firekit method but didn't use the shorting trick. I have scoured the internet for information and tricks and it seems like these are my last two options before I throw this thing out the window. I have seen your posts in other threads and you have been a great help throughout this ordeal.
factory cable
thank you for this information. I am in the same predicament. I am purchasing a factory cable from Amazon $1.27.
It is sold by Earlybirdsavings and is a 3ft micro USB factory cable for kindle fire and Motorola Xoom.
thank you for all the helpful information!
I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.
cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?
Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!
More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.
Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.
Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:
Edit : Sorry I asked stupid question!
Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.
Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick
I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:
Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck
Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app
olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you
Hey team.
Hoping to shed some light on this.
Device: Essential Ph-1, November Pie Security Update
Macbook, with oh my zsh (so I think the commands are same as Powershell)
In the process of Root, TWRP, and Magisk.
Let me see if I can backtrack this:
I followed the directions on the guide with help from the docs. I did this with the latest TWRP, not the TWRP-SEP. I get into TWRP no problem, except for the no-touch issue. So, I am able to flash the TWRP-SEP and get into TWRP with it working just fine.
Then Magisk runs into the "zip invalid format" issue inside TWRP. I look and look, determine I have either too new a Pie version or wrong Magisk/corrupt file. I get the 091 downgrade and try a new Magisk (my macbook extracts zips as I download them, and I have to recompress them, so this time I downloaded the zip on my Arch machine, transferred it to the macbook).
I tried flashing the img from TWRP, using the img, not zip, and had no luck with Magisk, same error. For a brief moment I get into my device, and I can't touch anything. Reboot several times, finally registers my touches, where I assume it reverts to some previous "recovery" with the AB, which I'm unfamiliar with.
Now, I'm stuck in a fastboot, and I'm having a hard time writing anything to the phone. I have access via ADB, I'm missing some simple solution I just know it, but I have tunnel vision and just need some help. When I write anything I get a FAILED (remote: 'Error flashing partition.') dialogue. Somcom3x's response here worked one time but doesn't anymore.
My goal is to just have root. I thought I had to downgrade to get it, so I tried unsuccessfully, and I'm having a hard time getting out of this one.
EDIT: fastboot devices outputs a completely different number than it did earlier in this process (70943811)
Seems the AB partition is saving me here, and something kicked in for me to be able to boot my phone normally, and now have access to the device.
Build number PPR1.181005.076
Now able to use ADB commands, I'm on the twrp.me page, using "adb shell getprop ro.boot.slot_suffix" with the output of "_b" I go into fastboot, and still using twrp.me type "fastboot --set-active=_a, and "Slot _a does not exist. supported slots are: a, b" So, I set current slot to "a". I don't know if this is how it works, but I tried to go into recovery under A slot, no TWRP-booted me to device, then I repeated under slot B and same thing. So presumably no TWRP at all. In which case, I am reinstalling the TWRP-SEP.img and starting the process fresh, is that safe to assume?
Assuming that, I did method 2, deleting all previous files, redownloading and transferring everything, virtually the same as method 1 up until the point I got stuck at which was "fastboot flash boot_a twrp-mata.img and it outputs "Failed (remote: 'Error flashing partition.') Switched USB ports, this is the same cable it was working on earlier.
I'm out of ideas, and gotta wake up early in the morning.
Sorry for the live updates but posting this kind of puts a fire under my rear and helps me think out the problem, so hopefully this is useful to someone.
forgive me if i'm wrong as i didn't read through the wall of text. If you only want a rooted device, you could try to clean restore november build and then flash a patched boot img without having to flash twrp.
https://drive.google.com/file/d/13GLyPiCaHbOx5aGEAGHEHr026x3D4Llv/view?usp=sharing
jrc058 said:
Hey team.
In the process of Root, TWRP, and Magisk.
Let me see if I can backtrack this:
I followed the directions on the guide with help from t
Click to expand...
Click to collapse
Okay... You don't mention (or I don't see) if you unlocked critical partitions? Let's assume you did because you never would have tried this if you didn't.
What USB C cable are you using? I had all types of problems with this phone till I purchased a good Belkin USB C. I got one and it's been clear sailing after that. I don't know if that's for sure your problem, but for sure you should start over from below. I highly recommend ditching the Linux and Unix machine and using windows. I use all three myself and I have a had a WAY better experience modding this phone on Windows.
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484
Good luck
Sent from my mata using XDA Labs
swiftbones74 said:
Okay... You don't mention (or I don't see) if you unlocked critical partitions? Let's assume you did because you never would have tried this if you didn't.
What USB C cable are you using? I had all types of problems with this phone till I purchased a good Belkin USB C. I got one and it's been clear sailing after that. I don't know if that's for sure your problem, but for sure you should start over from below. I highly recommend ditching the Linux and Unix machine and using windows. I use all three myself and I have a had a WAY better experience modding this phone on Windows.
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484
Good luck
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I did in my first attempt, I must not have in my following attempts. I tried to restart all over again, including critical partitions, and it soft bricked not being able to pass the logo splash screen. It bootlooped for a while, and now has just shut off entirely and won't turn on.
EDIT: I was able to shut it down correctly with the power + u + d, and it is properly shut down it appears, afraid to turn it on.
jrc058 said:
I did in my first attempt, I must not have in my following attempts. I tried to restart all over again, including critical partitions, and it soft bricked not being able to pass the logo splash screen. It bootlooped for a while, and now has just shut off entirely and won't turn on.
EDIT: I was able to shut it down correctly with the power + u + d, and it is properly shut down it appears, afraid to turn it on.
Click to expand...
Click to collapse
So are you using a good USB C?
Sent from my mata using XDA Labs
Try booting off a on the go image
Sent from my PH-1 using XDA Labs
jrc058 said:
Hey team.
Hoping to shed some light on this.
Device: Essential Ph-1, November Pie Security Update
Macbook, with oh my zsh (so I think the commands are same as Powershell)
In the process of Root, TWRP, and Magisk.
Let me see if I can backtrack this:
I followed the directions on the guide with help from the docs. I did this with the latest TWRP, not the TWRP-SEP. I get into TWRP no problem, except for the no-touch issue. So, I am able to flash the TWRP-SEP and get into TWRP with it working just fine.
Then Magisk runs into the "zip invalid format" issue inside TWRP. I look and look, determine I have either too new a Pie version or wrong Magisk/corrupt file. I get the 091 downgrade and try a new Magisk (my macbook extracts zips as I download them, and I have to recompress them, so this time I downloaded the zip on my Arch machine, transferred it to the macbook).
I tried flashing the img from TWRP, using the img, not zip, and had no luck with Magisk, same error. For a brief moment I get into my device, and I can't touch anything. Reboot several times, finally registers my touches, where I assume it reverts to some previous "recovery" with the AB, which I'm unfamiliar with.
Now, I'm stuck in a fastboot, and I'm having a hard time writing anything to the phone. I have access via ADB, I'm missing some simple solution I just know it, but I have tunnel vision and just need some help. When I write anything I get a FAILED (remote: 'Error flashing partition.') dialogue. Somcom3x's response here worked one time but doesn't anymore.
My goal is to just have root. I thought I had to downgrade to get it, so I tried unsuccessfully, and I'm having a hard time getting out of this one.
EDIT: fastboot devices outputs a completely different number than it did earlier in this process (70943811)
Seems the AB partition is saving me here, and something kicked in for me to be able to boot my phone normally, and now have access to the device.
Build number PPR1.181005.076
Now able to use ADB commands, I'm on the twrp.me page, using "adb shell getprop ro.boot.slot_suffix" with the output of "_b" I go into fastboot, and still using twrp.me type "fastboot --set-active=_a, and "Slot _a does not exist. supported slots are: a, b" So, I set current slot to "a". I don't know if this is how it works, but I tried to go into recovery under A slot, no TWRP-booted me to device, then I repeated under slot B and same thing. So presumably no TWRP at all. In which case, I am reinstalling the TWRP-SEP.img and starting the process fresh, is that safe to assume?
Assuming that, I did method 2, deleting all previous files, redownloading and transferring everything, virtually the same as method 1 up until the point I got stuck at which was "fastboot flash boot_a twrp-mata.img and it outputs "Failed (remote: 'Error flashing partition.') Switched USB ports, this is the same cable it was working on earlier.
I'm out of ideas, and gotta wake up early in the morning.
Sorry for the live updates but posting this kind of puts a fire under my rear and helps me think out the problem, so hopefully this is useful to someone.
Click to expand...
Click to collapse
Do not re-zip the files.
Retreive them from your trash. Once the Mac expands them on download they are in the trash.
Re-zipping the files will lead to all kinds of issues.
swiftbones74 said:
So are you using a good USB C?
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Presumably, yes. It's a brand new one I bought from Fry's, worked well for the first steps.
avd said:
Try booting off a on the go image
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Forgive my ignorance, is the go image just the stock?
tech_head said:
Do not re-zip the files.
Retreive them from your trash. Once the Mac expands them on download they are in the trash.
Re-zipping the files will lead to all kinds of issues.
Click to expand...
Click to collapse
I think this has been my main issue. This is what I realized and started switching from the arch machine to the macos. I wasn't aware of the macos zips going into the trash?
The current state of the phone is that it's just boot looping, I can't get past the splash screen, and haven't been able to get ADB or fastboot commands to work on it. After a while, it just turns off. I turned it back on and got the same results.
EDIT: Following OP from here, I followed his steps on getting lucky since neither of us could access anything and it looped forever. Basically, just pressing the power button in a weird series of sequences until magic happened.
I think something with oh my zsh on my macos is funky about the scripts, so I had to individually do all flash scripts and tweak them along the way. Now I have a stock phone, just unlocked.
I got out of bootloop, flashed the stock img manually (i think oh my zsh isn't helping), and got it running. It's now bootloader unlocked, i tried flashing unlock critical and it said device already unlocked. From there, I have been trying to install TWRP September img and it just keeps saying FAILED (remote: Error flashing partition.) I tried methods 1 and 2, and same failed result on both.
jrc058 said:
I got out of bootloop, flashed the stock img manually (i think oh my zsh isn't helping), and got it running. It's now bootloader unlocked, i tried flashing unlock critical and it said device already unlocked. From there, I have been trying to install TWRP September img and it just keeps saying FAILED (remote: Error flashing partition.) I tried methods 1 and 2, and same failed result on both.
Click to expand...
Click to collapse
You need a new cord. I'm telling you, I went through the same thing till I got a GOOD high-end USB C 3.0
Sent from my mata using XDA Labs
swiftbones74 said:
You need a new cord. I'm telling you, I went through the same thing till I got a GOOD high-end USB C 3.0
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Used a cord my friend uses, did the flashall script. Same exact thing, failed to write on specific parts like boot and system.
Now the device is unresponsive, plugged in to it's stock charger, hoping to turn on.
I'm hoping it is just the cable. However, if that's not the case, just to entertain me, what is the issue?
jrc058 said:
I'm hoping it is just the cable. However, if that's not the case, just to entertain me, what is the issue?
Click to expand...
Click to collapse
I honestly don't know what could be going on for you but I highly recommend going to this thread/ good USB C 3.0 or 3.1 cable/ widows computer/ working fastboot environment/ asking @aer0zer0 what he thinks ?
Good luck!
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484
Sent from my mata using XDA Labs
jrc058 said:
Used a cord my friend uses, did the flashall script. Same exact thing, failed to write on specific parts like boot and system.
Now the device is unresponsive, plugged in to it's stock charger, hoping to turn on.
I'm hoping it is just the cable. However, if that's not the case, just to entertain me, what is the issue?
Click to expand...
Click to collapse
Double check that the device is "flashing unlocked"
swiftbones74 said:
I honestly don't know what could be going on for you but I highly recommend going to this thread/ good USB C 3.0 or 3.1 cable/ widows computer/ working fastboot environment/ asking @aer0zer0 what he thinks ?
Good luck!
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I used said post for stock firmware multiple times. My current issue is that I can't flash anything because it's turned off, without being able to turn on, and I haven't found a way to flash anything while it's off.
rignfool said:
Double check that the device is "flashing unlocked"
Click to expand...
Click to collapse
Device has been flashing unlocked the whole time.
I'm inclined to believe it's not charging? It's not responding to being plugged in.
Again, I tried a cable that my friend used to root his oneplus. I don't think it's a cable issue.
We were both running macos, I also tried from my Arch machine, I don't have a windows pc, so it's nothing windows.