Related
Long story short, I was trying out new kernels, got stuck in a boot loop, nothing would fix it, so I tried to restore back to stock rom. I did it manually in fastboot mode, but the bootloader .img would not write. It gave an error saying mismatched signatures. I redownloaded the image, I tried using a couple of different methods, like using toolkits and various commands, and finally, without thinking, erased the bootloader using the fastboot erase command with the intent of re-writing it, which obviously I can not do or I would no longer be here. It still boots, in the sense that I hear the notification on the computer that a device has been connected, but it shows up as NVidia APX in my list of devices on windows instead of Nexus 7 now, and the screen shows nothing. So... how screwed am I? If it is hopeless, is there any way to return/replace it (without using questionable methods)? Thanks.
Kaphix said:
Long story short, I was trying out new kernels, got stuck in a boot loop, nothing would fix it, so I tried to restore back to stock rom. I did it manually in fastboot mode, but the bootloader .img would not write. It gave an error saying mismatched signatures. I redownloaded the image, I tried using a couple of different methods, like using toolkits and various commands, and finally, without thinking, erased the bootloader using the fastboot erase command with the intent of re-writing it, which obviously I can not do or I would no longer be here. It still boots, in the sense that I hear the notification on the computer that a device has been connected, but it shows up as NVidia APX in my list of devices on windows instead of Nexus 7 now, and the screen shows nothing. So... how screwed am I? If it is hopeless, is there any way to return/replace it (without using questionable methods)? Thanks.
Click to expand...
Click to collapse
You flash your bootloader? That's the last thing one should do. We only need to unlock it, not flash it.
angellsl said:
You flash your bootloader? That's the last thing one should do. We only need to unlock it, not flash it.
Click to expand...
Click to collapse
It was already unlocked and rooted, etc, but I kept getting an error about it every time I tried flashing a rom, and the device wouldn't boot anyway, so I got frustrated and derped. I know that was pretty stupid, just wondering if there is any hope.
http://forum.xda-developers.com/showthread.php?t=1883737
sounds just like your situation... unfortunately you will most likely have to return/exchange/RMA
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
There's a bunch of threads about the bootloader unlock tool existing, not any real place to aggregate reports of problems with it. So, if you've attempted to unlock your bootloader using the official ASUS tool and are having problems, please post your situation.
Reported instances:
myself
DeathStolas
ASUS_Khang
Rattraps123
m3t4lw01f
creison
both are experiencing bootloader unlock limbo. The tool seems to have worked, but going into fastboot shows two progressive screens:
1) Unlock Successfully reboot in 5 seconds
2) FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Clearing the cache goes through the loop again. Mind you, this loop only happens when you're trying to get to the bootloader. If you go to recovery or normally boot, you won't have any issues.
However, any commands sent via fastboot fail, so the bootloader is still locked. Attached is an image of the second bootloader screen.
ASUS_Khang is already getting in touch with technical folks to investigate as well, but I figure it best to see if anyone else is having issues with the official tool.
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
I have to laugh at the fact that someone on XDA unlocked the bootloader successfully with none of these problems and then ASUS give an "Official Unlock Tool" that screws up the phone of any who uses it... In the words of Alanis Morrisett - "Isn't it Ironic"...
m3t4lw01f said:
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
Click to expand...
Click to collapse
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Same problem here. I used the official unlocker tool and it did what it said it was going to do, but... I got the mythical "Bootloader 5 sec reboot".
asus is working on a fix.
playingmax said:
asus is working on a fix.
Click to expand...
Click to collapse
I'm sure that they are, but it would be interesting to see a source for that claim.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
m3t4lw01f said:
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
Click to expand...
Click to collapse
Sounds good. Can't wait till this is all sorted out and I can continue on with installing Cyanogenmod for my SO. She is really excited since it's her first Android phone.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
here you go
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
look at Khang Thai (ASUS REP) reply. they are working on a fix.
Kona67 said:
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Click to expand...
Click to collapse
Same issue ... I tried without a pin .. now added a pin and it asked me for it when trying to run the app again ... but that didn't help !
Help Ausus!!!
Mine says unlock failed rebooting in 5,4,3,2,1.
any way to relock bootloader as zenfone 6,5,and 4 have
When the 5 second bootloader issue is fixed you should hear about it here first, we have an Asus employee helping us: http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
https://fsfe.org/news/2012/news-20121106-01.en.html
Enviado do meu iPhone usando o Tapatalk
Looks like a user has solved the 5 second reboot issue. Check out the rather convoluted method here: http://forum.xda-developers.com/showthread.php?p=63498472
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Did you verify the checksum of the image prior to executing the flash-all script?
redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
I don't use flash all script. I flashed each img individually like it's posted in the guide
redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
Yes the checksum was verified
XMayhem2099 said:
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Click to expand...
Click to collapse
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
v12xke said:
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
Click to expand...
Click to collapse
Did both still the same bootloop
XMayhem2099 said:
Did both still the same bootloop
Click to expand...
Click to collapse
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
v12xke said:
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
Click to expand...
Click to collapse
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
XMayhem2099 said:
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
Click to expand...
Click to collapse
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
v12xke said:
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
Click to expand...
Click to collapse
I did the flash all command it ran successfully. Looks like im still getting a bootloop. I'll let it sit for an hour or so. If it doesn't run ill flash an older factory image. Thanks for the help, Ill let you know what happens.
Mine started doing the same thing last night, so far nothing I have tried has worked. Wireless provider is no help maybe Huawei will replace.
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Sent from my Nexus 6 using XDA-Developers mobile app
CyberpodS2 said:
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Click to expand...
Click to collapse
Huawei seems to have done a crappy job manufacturing them. Mine bootloops every time I update to a new ROM build, every time I switch ROMs and every time I try to restore a backup. Thankfully I've been able to get out of it every time so far but I've owned a lot of phones and none went into bootloops as often as the 6P. I've resigned myself to the fact that this phone is a time bomb and that it likely won't have a very long life. Would never buy another phone made by Huawei.
Problem google and hawuei (hardware) RMA
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
fapste said:
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
Click to expand...
Click to collapse
1. In general or when it happened? Averaged 4 hours SOT in 14-16 hours total.
2. 128 Toshiba
3. 3-29-2016
4. No
5. No
Same issue on a buddies 6p.. Fastboot commands go through the script with no errors but no results.. Still stuck in this bootloop. Has to be hardware causing this bootloop.
I'm having the same issue
Sent the device to Huawei and they say they'll repair it but I'm not sure if that's possible
My question is when they replace them, is the defect still waiting to pop up again??
Sent from my Nexus 6 using XDA-Developers Legacy app
Bought 2nd hand phone, managed to coax original sales receipt from Google store out of seller. Sent it in for an RMA and they swapped out my motherboard. Was also out of warranty by 2 months
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.