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.
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
Backstory I'm running PureNexus rom with Experimental kernel. Yesterday out of nowhere the phone started bootlooping, usually this is fine and i'll just restart the phone. Well after trying this the bootloop stayed for 15mins. I cleared cache and dalvik and still the same results. I ended up trying to restore a previous nandroid and nothing changed. Frustrated I backuped my titanium backups to my PC and cleared everything, factory reset and data format from twrp. I tried flashing the PureNexus rom clean and still bootloops. It just hangs on the white Google screen with the black background.
I'm following Heisenberg's tutorial (section 10) and after using fastboot and following the directions, i'm getting stuck on flashing the system. I'll get, "load_file: could not allocate 2014388768 bytes
error: cannot load 'C:\angler\images\system.img'
I read restarting the computer might help and i tried that and nothing has changed. It seems this is not rom related, since I downloaded a couple different ones and pushed it to my phone/flashed and it still bootloops. Any suggestions or help? Thanks!
Subiegsr said:
Backstory I'm running PureNexus rom with Experimental kernel. Yesterday out of nowhere the phone started bootlooping, usually this is fine and i'll just restart the phone. Well after trying this the bootloop stayed for 15mins. I cleared cache and dalvik and still the same results. I ended up trying to restore a previous nandroid and nothing changed. Frustrated I backuped my titanium backups to my PC and cleared everything, factory reset and data format from twrp. I tried flashing the PureNexus rom clean and still bootloops. It just hangs on the white Google screen with the black background.
I'm following Heisenberg's tutorial (section 10) and after using fastboot and following the directions, i'm getting stuck on flashing the system. I'll get, "load_file: could not allocate 2014388768 bytes
error: cannot load 'C:\angler\images\system.img'
I read restarting the computer might help and i tried that and nothing has changed. It seems this is not rom related, since I downloaded a couple different ones and pushed it to my phone/flashed and it still bootloops. Any suggestions or help? Thanks!
Click to expand...
Click to collapse
Just download NexusRoot Toolkit to flash back to stock or boot into recovery TWRP and flash PN rom again. It should work fine after that.
luckyfate said:
Just download NexusRoot Toolkit to flash back to stock or boot into recovery TWRP and flash PN rom again. It should work fine after that.
Click to expand...
Click to collapse
Just updated the SDK tool and it actually did let me install the system.img file now after it allocated some. But phone still boot looped.
Downloading the NexusRoot Toolkit now! Thank you for the suggestion, I'll update with the results.
So I installed the toolkit and did the flash stock + Unroot and checked soft-bricket/bootloop and phone is still bootlooping 30 mins later. It's doing the same bootloop as before. Just the black and white Google logo and then the orange pause boot screen. Although, as I type this the Google is not just there and it doesn't flash back to the orange screen..
Not sure if this helps but the live log said:
"Nexus Root Toolkit v2.1.6
Masterlists:
- LatestToolkitFiles.ini 3124
- AndroidDeviceListFull.ini 3124
- AndroidDeviceListFlash.ini 3124
ANGLER-ANGLER: Android 6.0.0 - Any Build
Live log initiated [2016-07-31]:
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
5VT7N15A25003518 fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: angler
finished. total time: 0.012s
Launching flashstock.bat"
Subiegsr said:
So I installed the toolkit and did the flash stock + Unroot and checked soft-bricket/bootloop and phone is still bootlooping 30 mins later. It's doing the same bootloop as before. Just the black and white Google logo and then the orange pause boot screen. Although, as I type this the Google is not just there and it doesn't flash back to the orange screen..
Not sure if this helps but the live log said:
"Nexus Root Toolkit v2.1.6
Masterlists:
- LatestToolkitFiles.ini 3124
- AndroidDeviceListFull.ini 3124
- AndroidDeviceListFlash.ini 3124
ANGLER-ANGLER: Android 6.0.0 - Any Build
Live log initiated [2016-07-31]:
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
5VT7N15A25003518 fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: angler
finished. total time: 0.012s
Launching flashstock.bat"
Click to expand...
Click to collapse
Have you tried just downloading the nexus6p IMG and using the flash-all command? I've always been able to recover that way. It restores everything to stock and wipes everything. If it still doesn't work then I would assume a hardware issue. Unless your PC drivers are messing with the process. Some USB hardware can have issues.
Gizmoe said:
Have you tried just downloading the nexus6p IMG and using the flash-all command? I've always been able to recover that way. It restores everything to stock and wipes everything. If it still doesn't work then I would assume a hardware issue. Unless your PC drivers are messing with the process. Some USB hardware can have issues.
Click to expand...
Click to collapse
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
*edit: I downloaded the latest version from https://developers.google.com/android/nexus/images did the flash all command and it still hangs on the white Google screen. Although, it did say it couldn't flash boot.sig, recovery.sig, vendor.sig, and etc.. but still completed the flash? I did have all the files unzipped in the same folder of the platform-tools. I just held shift + right clicked the folder and opened the run command window. Am I missing something?
duplicate*
Subiegsr said:
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
Click to expand...
Click to collapse
You should try to flash by choosing different stock rom N
Except any stock rom. I will try to flash any android N stock rom by checking Device is normal or no soft brick. If phone boots up fine, u can flash back any to different stock rom like 19X....
luckyfate said:
You should try to flash by choosing different stock rom N
Except any stock rom. I will try to flash any android N stock rom by checking Device is normal or no soft brick. If phone boots up fine, u can flash back any to different stock rom like 19X....
Click to expand...
Click to collapse
doesn't seem any rom is working when booting clean from twrp.
Subiegsr said:
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
*edit: I downloaded the latest version from https://developers.google.com/android/nexus/images did the flash all command and it still hangs on the white Google screen. Although, it did say it couldn't flash boot.sig, recovery.sig, vendor.sig, and etc.. but still completed the flash? I did have all the files unzipped in the same folder of the platform-tools. I just held shift + right clicked the folder and opened the run command window. Am I missing something?
Click to expand...
Click to collapse
Usually you would want to run it from an elevated command prompt and navigate to folder and just type flash-all.bat, as long as adb tools are in environment variables it will work. But if it made it all the way to flashing vendor, wiping data and then rebooting it should have worked. This seems like the symptoms of a bad chip. Bad luck I'm guessing. You could try another PC just to be sure but I would trade it in if it was me.
Gizmoe said:
Usually you would want to run it from an elevated command prompt and navigate to folder and just type flash-all.bat, as long as adb tools are in environment variables it will work. But if it made it all the way to flashing vendor, wiping data and then rebooting it should have worked. This seems like the symptoms of a bad chip. Bad luck I'm guessing. I would try another PC just to be sure but I would trade it in if it was me.
Click to expand...
Click to collapse
Yeah, the command prompt installed everything successfully. The only other computer I have is a MacPro that I could try to use, but honestly I spent 7 hours today trying to fix the phone and 4 last night.. i think my eyes are done lol. Good call on the bad chip, probably was too hot over the weekend for it. I did talk to Google and they're sending me a replacement. Sucks though, I took care of my battery life crazy to preserve the life, hopefully the refurb one is just as good. Thanks for the help anyways. :good:
Subiegsr said:
Yeah, the command prompt installed everything successfully. The only other computer I have is a MacPro that I could try to use, but honestly I spent 7 hours today trying to fix the phone and 4 last night.. i think my eyes are done lol. Good call on the bad chip, probably was too hot over the weekend for it. I did talk to Google and they're sending me a replacement. Sucks though, I took care of my battery life crazy to preserve the life, hopefully the refurb one is just as good. Thanks for the help anyways. :good:
Click to expand...
Click to collapse
The exact same thing happened to me over the weekend, and I've tried all the steps you did. I'm now at the same conclusion of hardware failure, so will be calling google today for an RMA.
zamula said:
The exact same thing happened to me over the weekend, and I've tried all the steps you did. I'm now at the same conclusion of hardware failure, so will be calling google today for an RMA.
Click to expand...
Click to collapse
That's crazy it happened to you too. Good luck with the replacement. I hope the replacement doesn't have scratches/scuffs. Mine is seriously immaculate.
I've tried about a dozen sets of threads about go into Fastboot, run Fastbook OEM Lock or Fastboot Flashing Lock etc and every time I just get a message saying its not allowed on the PC. In the Fastboot on the phone it says Secure Boot = Yes, Device State = unlocked. It was a long while back that I unlocked and then flashed it and although I never used a custom ROM I can't remember exactly what I did or the order I did it in.
I just want to take the phone back to its original vanilla state.
Sorry if this has been covered elsewhere.
When the phone is in Fastboot mode - in Windows 10, it is not seen using the command adb devices but it is using fastboot devices
When the phone is fully booted up - in Windows 10, it is seen using adb devices but not using the command fastboot devices
USB debugging is enabled on the phone
As I say, sorry if its a daft question and I'm sure I'm overlooking something obvious but going round in circles here.
Thanks in advance,
David
adb and fastboot is not set properly on you system
and for usig Stock ROM you dont need to lock bootloader
surajloharia said:
adb and fastboot is not set properly on you system
and for usig Stock ROM you dont need to lock bootloader
Click to expand...
Click to collapse
Thanks, but with respect that's pointing out the obvious rather :/ what I am looking for is advice on how to do it properly... its already clear that I haven't done so thus far.
So what do I do to enable my phone to automatically update again? Every time it attempts to it fails it downloads fine, but always fails when it attempts to install the update. Surely there must be something else I need to do to remove all the previous stuff I've done?
DavidElders said:
Thanks, but with respect that's pointing out the obvious rather :/ what I am looking for is advice on how to do it properly... its already clear that I haven't done so thus far.
So what do I do to enable my phone to automatically update again? Every time it attempts to it fails it downloads fine, but always fails when it attempts to install the update. Surely there must be something else I need to do to remove all the previous stuff I've done?
Click to expand...
Click to collapse
Updates fail when System partition is altered
either manually with file replacements or you have rooted your phone with magisk/Su
The best way is to flash latest Full ROM zip and device will return to get updates automatically
surajloharia said:
Updates fail when System partition is altered
either manually with file replacements or you have rooted your phone with magisk/Su
The best way is to flash latest Full ROM zip and device will return to get updates automatically
Click to expand...
Click to collapse
Phone was rooted. So there's no way to unroot at all? Or does flashing a full ROM do that? Thanks for the advice
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.
Hi all, I really messed up my 6T today, after messing with the new update and root, I ran the flash_all.bat file (from https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516) to restore images but didn't realize it would clear all my data, I stopped the process after it ran for a few seconds in a panic but now my phone only has the fastboot screen and fastboot.exe from my cmd shell is unable to do anything (just errors out for most commands), is there a way for me to at least retrieve my photos from my phone? I've tried 3rd party software and they all require usb debugging which I can't activate due to my phone not having a boot image. Any help would be a miracle, thanks.
I would try fastbooting a TWRP image. From there you may get access to your internal storage. You can then copy it off to a PC. I say may because you could encounter encryption issues when trying to first boot into TWRP.
If you do hit encryption issues, you could modify the "flash all" batch file to remove the -w command so it doesnt format. However, I thought that it gave you an option to wipe or not?
If it did wipe first, your a gonner my friend. You are too late.
Hope this gives you some insight on where to go from here.
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
christmasdesparation said:
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
Click to expand...
Click to collapse
THe -w command does a very fast wipe. So if it was at the beginning of the scrip that more than likely like your files are gone.
Run the script again, this time delete the -w command. This will be your best chance of finding any data.
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Anyway, I took it to a shop today since I couldn't do much else my self, we'll see what happens. Lesson learned to always back up before messing with the boot.
Thanks
christmasdesparation said:
Lesson learned to always back up before messing with the boot.
Click to expand...
Click to collapse
And to properly read and understand what it is you're attempting to do.
sssarg said:
And to properly read and understand what it is you're attempting to do.
Click to expand...
Click to collapse
lol yes but in my defense I was already kind of freaking out since the fastboot wasn't working like it did previous times and messed up my normal boot
christmasdesparation said:
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Click to expand...
Click to collapse
Probably not possible as user data are stored in a virtual filesystem, mounted over an encrypted partition.
That's the reason why police forces regularly ask phone makers to put a backdoor, it's very hard even for a high tech forensic specialist to find data on a phone
So I actually re-ran the flash_all.bat script without the -w flag and I was able to fast boot flash into twrp (twrp-3.3.1-30-fajita-Q-mauronofrio to be specific). I can see what i believe are my files in the internal storage, but encrypted, however twrp never prompted me for a password, also going to the twrp terminal and entering twrp decrypt <passcode> did not work. Anybody know how to get twrp to decrypt? For some reason flash_all.bat did not restore my original boot or anything so I am only able to boot into recovery mode or twrp from the fastboot on my PC. doing fastboot getvar all shows that my slot-unbootable:a is "yes" if anyone knows how to make sense of this, it would be appreciated, even if I just need to copy my phones internal storage on to my computer and run 3rd party software to decrypt it that is fine
Thank you
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Could have used msm tool. You would have lost everything but at least phone would have worked
jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Yeah, he was trying hard to avoid that.
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Scott said:
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Click to expand...
Click to collapse
Thanks, I owe it to you, your original advice was spot on and all I failed to do was check the version number
jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Well to me "everything" on my phone was worth more to me than the phone itself