Related
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 cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
6.0 is the current update...
Flash twrp then try flashing a custom ROM. Honestly it sounds like you might be doing something wrong, or maybe a bad USB cable? Keep trying I don't think you're screwed
Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Do you still have an custom recovery installed? TWRP?
Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.
acejavelin said:
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.
Click to expand...
Click to collapse
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.
Steeleio said:
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.
Click to expand...
Click to collapse
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk
acejavelin said:
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Pure. I figured if I start all the way over from the beginning it would work out. Like I said, even one of the OTA's failed. I tried flashing the BTFM.bin file but that didn't work either. I will try some other stuff when I get off work today.
So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?
Steeleio said:
So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?
Click to expand...
Click to collapse
No, in fact it is quite common to get that message with the partition information... Ignore it, if everything else went fine and you having no more problems, your good to go.
After using the megapixel rom. I tried flash back to stock with root tool kit.
During the process it told me I had to manual boot in recovery to a factory restore. That would not work so I ended up soft bricking my phone. I was able to side load twrp and the latest build and flash it (thank god). No when I do oem lock boot loader, my nexus 6p won't boot. As soon as I oem unlock, it will boot. Any ideas what could be cause that?
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
This is a perfect time to remind folks that "locking" the bootloader is something that should be done with great care. There are dozens, if not hundreds of "my phone is bricked" threads centered around locking their bootloader without understanding the requirements and risks. If you don't have a reason to do it, leave it unlocked. If I need to do it, I flash 100% back to stock using a full factory image before locking.
Sent from my Nexus 6 using XDA-Developers Legacy app
BostonDan said:
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
Click to expand...
Click to collapse
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Blackfish77 said:
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Click to expand...
Click to collapse
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
You should only lock bootloader when you are on stock factory image from nexus developers site. Either use flash_all script or flash everything manually. As others said keep away from toolkits.. You never know what can go wrong or what they re doing in background.
As I understand you restored TWRP and Megapixel rom and tried to lock the bootloader when you had that combination installed on your phone? That can not be done. You are either full stock (rom, kernel, recovery...) and locked bootloader or unlocked bootloader and any combo of kernel, rom, recovery that you want.
RoyJ said:
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
Click to expand...
Click to collapse
I ended up using fastboot to flash factory. I then re locked bootloader and everything booted without and issue. I was happy about that. I re rooted and everything is working great. :good:
I can say I learned a lot from this experience. Thanks to everyone for your advice. I am now comfortable using the fastboot method. Almost bricking my phone was scary but it taught me a lesson. Cheers everyone.
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.
Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.
Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..