Related
Hi hope I have come to the right place for help. My Nexus 7 16GB 2012 wifi is freezing after the google logo during the boot animation of the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kitkat, but not sure which version, and have a locked bootloader, not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
alscott51 said:
High hope I have come to the right place for help. My daughters Nexus 7 16GB 2012 wifi is freezing after the google logo when booting at the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kit kat, but not sure which version, and have a locked bootloader, and not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull command
Ok Im not familiar with this programme but have read a bit about it. I will try and venture into this alien world of abd and see what happens.
Sent from my GT-I9100 using XDA Free mobile app
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
You can't use adb in fastboot mode. It seems possible to pull files with fastboot, but it isn't fun.
Maybe you can flash something via fastboot to make it boot again? That would be the best way imho.
alscott51 said:
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Go to recovery and try adb commands. In bootloader you can use only fastboot commands.
Ok I booted to the bootloader, from here selected recovery where the little Android is laying on its back. Now device manager showed nothing connected. Used the power + volume-up combo to get to the four recovery options, still nothing in device manager. Selected side load adb option and bingo welcome sound of device being connected. Windows didn't find a driver so downloaded adb driver from Asus but device manager refused to use it. Did some reading and downloaded Koush's universal driver and now device manager showed device connected and driver installed. The ADB devices command now shows the Nexus info. Now to learn the pull command. ....
Sent from my GT-I9100 using XDA Free mobile app
Done lots if reading on this and think I am beat. From what I have read the with the Nexus 7 in its current state (stock, locked bootloader, unrooted, no usb debugging) the sdcard is not reachable through the stock recovery sideload option in any way. I had a ray of hope from the above link to pull files via fastboot but I have read the thread and it seems the person says it was misleading information that they posted. I followed information in another thread and tried extracting boot, recovery and system files from a nexus factory image and flash them via fastboot but it fails stating the bootloader is locked. If I unlock the bootloader I will lose the sdcard data I want, as I will have to perform a factory reset. So as suggested I could install a CWM/TWRP recovery, but to do this via fastboot I need to unlock the bootloader......
I am thankful for people taking the time to help and for all suggestion posted but unfortunately I can not find a fix. I would be sooo grateful if someone could prove my finding wrong....
Off to do some reading about mounting the sdcard via adb shell but don't think this will work via stock recovery
Sent from my GT-I9100 using XDA Free mobile app
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
jkkk88 said:
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
Click to expand...
Click to collapse
Can't get the nexus to boot up, just bootloader and recovery accessible so don't think I'll be able to do this.
Sent from my GT-I9100 using XDA Free mobile app
Fixed it and saved all data.
Sent from my GT-I9100 using XDA Free mobile app
Sideload fix
Managed to fix this without losing anything (sdcard, docs, pictures, apps, setting etc). Took a while mostly due to lack of understanding of fastboot and ADB sideload from the recovery options.
Lots of posts advising to boot into the bootloader and use adb and fastboot. Everything I read to do with using fastboot commands via the nexus bootloader (insatalling boot/system/recovery etc) involved having an unlocked bootloader or having to unlock it as in my situation. This of course involves a factory reset of the Nexus resulting in a loss of the data that I was trying to retrieve, so i ruled this option out.
As suggested I should try the ADB pull command, but because I had not previosly enabled the USB debugging option via the setting menu everything I read said this was not an option. Read in one forum post something like "As you have not enabled USB debugging ADB is dead to you, just flash a factory image via recovery".... and lose all your data... this is not what I wanted to hear so I abandoned this option aswell.
Then I discovered sideloading. With this you can manually install an OTA update (the ones that pop up in your notification window saying something like "System update available") via the Nexus recovery option "apply update from adb". This does not invlove wiping any data , apps etc as it would just install the differences between what you are currently running eg. 4.4.2 and the updated android you want to go to eg 4.4.3. This is different to flashing a full factory image via fastboot were everything would be erased/formatted and an entirely new install would be flashed. Of course... simple when you know what the option is for and what you are doing. Of course I had had no clue what sideloading was all about.
So with my new knowledge I downloaded an OTA update from here:
http://forum.xda-developers.com/showthread.php?t=1745781&highlight=4+23
but wasnt sure what version of KitKat was running prior to the bootloop. I knew it was somewhere around 4.4.2.. so took a chance and tried KTU48L from KOT49H (4.4.3 from 4.4.2) and copied it to the Minimal ADB folder.
I booted the Nexus to the recovery mode and selected "apply update from adb". The tablet then conected to the PC (windows) as shown by Device manager. (I used Koush's universal ADB driver as windows failed to find anything of use). https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I opened Minimal ADB downloaded from here
http://forum.xda-developers.com/showthread.php?t=2317790
and typed "adb devices" which showed the Nexus was connected.
I then typed "adb sideload nexus OTA file name.zip"
Lots of sending files messages appeared in the adb window the Nexus disconnected from the PC and showed this...
Finding update package...
Opening update package...
Verifying update package...
Insatlling update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image....
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions..
Patching remaining system files...
script succeeded: result was [/system]
Install fromADB complete.
All looked good so I rebooted the Nexus but I was still stuck in a bootloop at the four spinning circles. I tried clearing the cache from the recovery menu several times powering it down and leaving it to boot but after half an hour accepted failure.
So I tried downloading KTU84P from KTU84L (4.4.4 from 4.4.3) and repeated the procedure. this time not as much files seemed to be sent to the Nexus, I guess this was just a small update. Again it showed "script succeeded" but still failed to get past the spinning circles of the boot animation.
Thinking I was defeated again I was going to give up but tried downloading LRX21P from KTU84P (5.0 from 4.4.4). This time when I sideloaded a mass of files were sent to the Nexus much much more then the other two updates, obviously KitKat 4.4.4 to lollipop 5.0 was a big update. Again I got the "script succeeded" but this time I got the new Lollipop boot animation and the Nexus fully booted.
I can only guess that the big update to Lollipop removed or replaced files or did something to replace the faultly part of my install that other OTA updates did not change.
Anyway I did not find any other fix that advised sideloading an OTA update to fix a bootloop, maybe I just looked in the wrong places. I tried to write this in laymans terms for non techie people in the hope that it may help someone else in the same situation who like me knows very little about android.
Thanks to the forum for the information...
Also link here with some info about half way down page on effects of usb debugging being enabled for sideloading, and near the bottom of the page a good link to a sideload pdf guide.
https://productforums.google.com/forum/#!topic/nexus/Fhl6VVb0kio
Hey everyone, I'm currently on B29, non-rooted and locked bootloader.
I would like to root and make my up to stock 7.1.1. The issue I'm having, is that there is an absolute ton of conflicting info and ways to do things that I'm just not sure at all how to proceed.
What I've tried so far was starting with this guide: https://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234. But the tool from step three wouldn't download and the hosting site threw a ton of popups and redirects at me (yes, I have uBlock).
Then continuing through that same thread I found this tool https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 that is apparently safer, but I have no idea how to use it.
Then I started hearing about this EDL mode stuff https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 which I attempted to do when I tried the Axon7Toolkit yesterday, but my phone just wouldn't go into EDL mode (or I just had no idea how to tell if it was or not) and the MiFlash thing didn't do anything.
So my real questions are:
1: Which version of TWRP and SuperSU do I need?
2: How do I unlock the bootloader?
3: What steps should I take so that I eventually end up rooted on stock 7.1.1 (currently still on B29)?
Thanks!
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Choose an username... said:
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Click to expand...
Click to collapse
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
CookedBooks said:
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
Click to expand...
Click to collapse
No access with adb or fastboot in edl mode. It' strictly for use with low level tools like miflash. Your environment will make the difference. I couldn't get miflash on my main pc (win8/x64) to see the device. Likely an issue of drivers even through the proper driver is installed, and phone is showing up properly in device mgr. I used a spare pc with a relatively fresh win10/x64 install. Miflash saw the phone right away.
Also, for edl mode, my u model will just flash the led once then go blank.
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
gpz1100 said:
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
Click to expand...
Click to collapse
Okay thanks, I'll give it a go again. Would you be able to clarify which version of TWRP I should use? I'm thinking 3.0.2-0 but I've seen other guides mention different versions and other people say the wrong version is going to be a massive headache.
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
gpz1100 said:
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
Click to expand...
Click to collapse
Okay thanks. As for the rest, am I correct in my understanding that I need to:
First: Use Axon7tool to flash TWRP https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Second: Unlock bootloader
Third: flash the official 7.1.1
Hmm you could use a7tool to flash TWRP, then install the twrp app and upgrade to 3.1 or whatever, and then get to nougat after some backups. I'm not sure but I think tenfar's twrp FUBAR'd some partitions when you tried to backup
Okay thanks. I think I'll give it a rest for today, I've been scouring threads since yesterday trying to get a clear picture of what to do. I think I'll spend the week researching further and give it a go next weekend.
I just miss having AdAway and CF Lumen installed on my phone. And I really want to give Substratum a try.
Thanks for all the tips and info!
Hang in there. You are on the right track. The edl thing can take a few attempts to get recognized.
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
lafester said:
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
Click to expand...
Click to collapse
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
If you have to use axon7tool then you might find this useful
https://forum.xda-developers.com/showpost.php?p=71206394
But I think that the US version has a different way to root and stuff, so i wouldn't be able to help...
bkores said:
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
Click to expand...
Click to collapse
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
CookedBooks said:
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
Click to expand...
Click to collapse
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
bkores said:
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
Click to expand...
Click to collapse
Okay, I just walked into work though. When I get home and settled this evening I'll give it a whirl and let you know what happens.
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
bkores said:
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
Click to expand...
Click to collapse
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
lafester said:
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
Click to expand...
Click to collapse
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
bkores said:
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
Click to expand...
Click to collapse
I used the toolkit to flash b15 full with miflash and it worked fine, however I already had miflash installed.
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.
Guys, I'm at my wits end here. I don't know what to do. And it's driving me crazy.
After saving for 3 months, I got a used Essential Ph-1 from craigslist (for sprint). It came with Android 9, and a February 5, 2019 security patch.
All I want to do is to root the phone. And I have tried everything in my power to get it to work. It just does not. I have unlocked the bootloader, I'm seeing the device in adb and fastboot, but unable to sideload, or flash anything. I've been following different threads on here and youtube looking for directions, but my phone will just not do it.
Can someone please help me? I will send my phone over to you and pay you to have it done. I've tried almost everything to do it, and nothing works. I've even tried to flash android 8 and 7, it still doesn't do it. Someone please help me. I don't know what more i can do. Any guidance is appreciated.
Can someone please help me? I don't know what more to do. Please.
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
goofball2k said:
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
Click to expand...
Click to collapse
No. I can't sideload or boot into anything other than the android 9
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
kt-Froggy said:
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
Click to expand...
Click to collapse
I tried that too. But it kept saying unable to unpack boot image | installation failed.
I tried it with the stock images from the Essential website, both the OTA and fastboot versions. I'm getting the error for both files.
I would suggest checking out the PH1 Dev telegram group https://t.me/EssentialPH1DEV . not only will you find pre rooted stock boot images along with ones with TWRP as well you will also find help flashing them if you need it. Hope this helps you out.
Thank you everyone for all your help. Special thanks to kt-Froggy. I got it to work. I had to change my usb port from 3 to 2 and i was able to get it to work!
Hello all,
I am trying to help my son fix some of his Oneplus 6t phones. Please bear with me as I am not the most tech savvy. He uses the phones for a business and I like to try to help out.
He has 5 Oneplus 6t devices, 3 are stuck in fastboot and 2 went into qualcomm crash dump errors. These issues happened when he tried to install a custom rom, Arrow OS.
I wanted to help him factory restore the phones so that we could try again. I downloaded the following:
1) Oneplus 6t USB drivers - https://oneplususbdrivers.com/oneplus-6t-usb-driver-download/
2) Qualcomm USB drivers - https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3) A decrypted Oxygeon OS MSM download tool - https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
We ran the MSM tool as administrator and plugged in the phone with a black screen, while holding the up and down volume button. Only sometimes it was recognized / connected. When we clicked start in the MSM tool, I ran into a few potential issues.
1) Image files do not match device
2) Waiting for device (just keeps counting)
Also, often the device was not recognized, and we could not get it to work.
In the device manager, it does not show the correct device. It gives some error / device not recognized issue. I am not sure if this is related. I tried re-installing the drivers, as well as trying on a second computer. The cable we are using is able to detect non-corrupt Oneplus 6t devices fine, so I do not believe that is the issue. Also an important note, some of the devices may be T-mobile branded but I am not sure which, if any.
Does anyone know what are the next steps or things I can try? I would really like to get these devices working for him so he can continue with his business. Sadly I cannot afford to replace or rebuy the devices. I fear I am making a simple mistake somewhere but am not sure where.
Thanks for your help in advance.
It's highly likely you may need the Verizon version of the factory image you can reset with MSM Tool
Do NOT Use the patched version of the MSM Tool unless you are sure you are flashing a correct compatible image with your phone
Following what I have written here to install the correct drivers may help you
[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who...
forum.xda-developers.com
HelpOneplus6t said:
Hello all,
I am trying to help my son fix some of his Oneplus 6t phones. Please bear with me as I am not the most tech savvy. He uses the phones for a business and I like to try to help out.
He has 5 Oneplus 6t devices, 3 are stuck in fastboot and 2 went into qualcomm crash dump errors. These issues happened when he tried to install a custom rom, Arrow OS.
I wanted to help him factory restore the phones so that we could try again. I downloaded the following:
1) Oneplus 6t USB drivers - https://oneplususbdrivers.com/oneplus-6t-usb-driver-download/
2) Qualcomm USB drivers - https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3) A decrypted Oxygeon OS MSM download tool - https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
We ran the MSM tool as administrator and plugged in the phone with a black screen, while holding the up and down volume button. Only sometimes it was recognized / connected. When we clicked start in the MSM tool, I ran into a few potential issues.
1) Image files do not match device
2) Waiting for device (just keeps counting)
Also, often the device was not recognized, and we could not get it to work.
In the device manager, it does not show the correct device. It gives some error / device not recognized issue. I am not sure if this is related. I tried re-installing the drivers, as well as trying on a second computer. The cable we are using is able to detect non-corrupt Oneplus 6t devices fine, so I do not believe that is the issue. Also an important note, some of the devices may be T-mobile branded but I am not sure which, if any.
Does anyone know what are the next steps or things I can try? I would really like to get these devices working for him so he can continue with his business. Sadly I cannot afford to replace or rebuy the devices. I fear I am making a simple mistake somewhere but am not sure where.
Thanks for your help in advance.
Click to expand...
Click to collapse
Did you figure it out?
FireRattus said:
It's highly likely you may need the Verizon version of the factory image you can reset with MSM Tool
Do NOT Use the patched version of the MSM Tool unless you are sure you are flashing a correct compatible image with your phone
Following what I have written here to install the correct drivers may help you
[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, thank you for your response.
I'm not sure the issue you had is the same as mine. My Oneplus 6T does not show up in the device manager at all.
I tried doing the unsigned device drivers thing, but when I select the folder that contains the onplus_android_winusb folder, it says it cannot find the drivers.
Sadly I think I have to give up on this one I am not very tech savvy and really don't know what else I can do.
I was able to fix one of the phones. I tried using fajita_41_J.50_210121 as my MSM recovery and it worked.
The fact that it worked implies to me my issue doesn't lie with the drivers, but rather which MSM file I am using, is this a good assumption?
If so, how can I figure out which files to use? I tried that same file on the 4 other phones, but would always get Sahara communication error.
HelpOneplus6t said:
I was able to fix one of the phones. I tried using fajita_41_J.50_210121 as my MSM recovery and it worked.
The fact that it worked implies to me my issue doesn't lie with the drivers, but rather which MSM file I am using, is this a good assumption?
If so, how can I figure out which files to use? I tried that same file on the 4 other phones, but would always get Sahara communication error.
Click to expand...
Click to collapse
This is what I was trying to say, you probably have the Verizon version, you need to make absolutely sure the MSM recovery files you are using are for that phone model
I bought my phone as global but they sent me a unlocked Verizon model, I found out because I couldn't flash it with MSM tool until I used the Verizon versions files
FireRattus said:
This is what I was trying to say, you probably have the Verizon version, you need to make absolutely sure the MSM recovery files you are using are for that phone model
I bought my phone as global but they sent me a unlocked Verizon model, I found out because I couldn't flash it with MSM tool until I used the Verizon versions files
Click to expand...
Click to collapse
Hi,
I believe you are right, that makes sense.
I see that the 1 phone that was fixable is very slightly different than the other 4- it doesn't have an IMEI code on the back, so likely it was a different version or something.
Where do I find the right recovery files? I searched for Verizon Oneplus 6t MSM Download Tool but I don't see anything different.
Sorry for my incompetence, I appreciate your help
I was able to fix a few more phones using the Tmobile 9.0.13 MSM Tool here:
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com
2 of the phones didn't work, they have Sahara communication errors still. I am not sure how to locate the right MSM tools for these- any ideas?
Furthermore, I flashed 9.0.13 from the MSM tool, but I would like to update to specifically 10.3.11, how can I do that?
HelpOneplus6t said:
Furthermore, I flashed 9.0.13 from the MSM tool, but I would like to update to specifically 10.3.11, how can I do that?
Click to expand...
Click to collapse
That is the same version I flash with MSM Tool I think
You should follow the instructions here for the Verizon version https://forum.xda-developers.com/t/guide-sim-unlock-t-mobile-version-all-type-of-imei-supported.3915269/
You can unlock the verizon variant by using a custom patched MSM Tool
After you have followed those instructions to have it unlocked on the international version rom
Then you are able to just flash the Normal OOS Flashable Update Zips via TWRP or the built in updater
Download them here https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3865396/
This allows you to update to the latest OOS 10 or 11
I really don't know about your other phones, Are they definitely OnePlus 6Ts ? I am only aware of the global and verizon variants, so if it's not either of those, I am not sure it's a OnePlus 6T
I managed to fix them by flashing the T-mobile version. This worked, but then I needed to unlock them since they were T-mobile locked. I converted them to the international version earlier successfully.
I am on 9.0.11 stock now! All I need to do really is update to 10.3.11
I will try following the links you have provided.
They are definitely 6ts
Thanks for your continued help.
FireRattus said:
That is the same version I flash with MSM Tool I think
You should follow the instructions here for the Verizon version https://forum.xda-developers.com/t/guide-sim-unlock-t-mobile-version-all-type-of-imei-supported.3915269/
You can unlock the verizon variant by using a custom patched MSM Tool
After you have followed those instructions to have it unlocked on the international version rom
Then you are able to just flash the Normal OOS Flashable Update Zips via TWRP or the built in updater
Download them here https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3865396/
This allows you to update to the latest OOS 10 or 11
I really don't know about your other phones, Are they definitely OnePlus 6Ts ? I am only aware of the global and verizon variants, so if it's not either of those, I am not sure it's a OnePlus 6T
Click to expand...
Click to collapse
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
HelpOneplus6t said:
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
Click to expand...
Click to collapse
Yes you are right but you do not need to download Every single update
I have found that these are the files I need to upgrade, I keep them saved for easy access
Code:
1-OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905(9.0.17).zip
2-OnePlus6TOxygen_34_OTA_047_all_2007171912_ac6dc9b(10.3.5).zip
3-OnePlus6TOxygen_34.J.48_OTA_048_all_2010042240_dbd576b615(10.3.6).zip
4-OnePlus6TOxygen_34.J.55_OTA_055_all_2107132253_b2cbbb97b4eee(10.3.12).zip
If you wanted 10.3.11 instead of 10.3.12, I don't see why that wouldn't work
These are all the full upgrade zips, but if you have a locked bootloader and use the official update method through the settings, I have been able to use the smaller OnePlus6TOxygen_34.J.55_OTA_048-055_patch_2107132253_b96081(10.3.6-10.3.12).zip Upgrade Zip to go from 10.3.6 to 10.3.12
HelpOneplus6t said:
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
Click to expand...
Click to collapse
I have actually found from testing that I did not need to flash the 10.3.5 or 10.3.6 Zips and could go from 9.0.17 to 10.3.12 if I used the full flashable update zips
so I am not sure why it failed for you
You are so awesome, thank you that worked flawlessly (the 4 separate upgrades). Throughout this thread I was able to:
Go from a soft bricked device, use the Tmobile MSM download tool to restore it, use a normal MSM download tool to convert it to the international variant, then upgrade it to 10.3.11.
My last question is regarding root, we are looking to root the device with magisk/twrp. I haven't done it in a few years so am a bit rusty on the process. It is a Oneplus 6t on 10.3.11, do you know where I can find the relevant files?
I see the latest fajita (oneplus 6t) files here: https://dl.twrp.me/fajita/
I'm a bit hesitant to use them because:
1) I'm not sure if I should use the latest ones, or an older version. I think I tried using the latest ones for something before and it messed something up.
2) I see people post online that I may need Enchilada files instead, even though that is for the Oneplus 6t, or that I need a mauronofrio twrp file instead, so I would prefer to wait for a decisive answer.
Thanks again for your help, you saved the day and my son is so elated
HelpOneplus6t said:
You are so awesome, thank you that worked flawlessly (the 4 separate upgrades). Throughout this thread I was able to:
Go from a soft bricked device, use the Tmobile MSM download tool to restore it, use a normal MSM download tool to convert it to the international variant, then upgrade it to 10.3.11.
My last question is regarding root, we are looking to root the device with magisk/twrp. I haven't done it in a few years so am a bit rusty on the process. It is a Oneplus 6t on 10.3.11, do you know where I can find the relevant files?
I see the latest fajita (oneplus 6t) files here: https://dl.twrp.me/fajita/
I'm a bit hesitant to use them because:
1) I'm not sure if I should use the latest ones, or an older version. I think I tried using the latest ones for something before and it messed something up.
2) I see people post online that I may need Enchilada files instead, even though that is for the Oneplus 6t, or that I need a mauronofrio twrp file instead, so I would prefer to wait for a decisive answer.
Thanks again for your help, you saved the day and my son is so elated
Click to expand...
Click to collapse
I am glad I could help and I do understand the hesitation, it is smart to be careful and not flash the wrong recovery file, the only time I have truly bricked a phone was by flashing the wrong recovery
I use the fajita twrp from the official source that you linked but the version you want to use does depend on your android version
You can get a crash dump error by using the latest TWRP on older OOS
I have been using Jaguar ROM for the OnePlus6T
My own installation process is as follows and WILL WIPE ALL DATA ON THE PHONE
Assuming you are coming from Latest Official OOS 10 (10.3.12)
Enable Developer mode and OEM Unlocking (In the Hidden Developer Settings)
(Optionally enable USB Debugging to adb reboot to bootloader)
(You may have to Disable Driver Signature Enforcement on Windows 10/11 to install correct drivers)
Reboot your phone to Fastboot by holding volume up and down during power up or with "adb reboot bootloader" in terminal, allowing the connection on your phone.
In Terminal
fastboot flashing unlock
FastBoot to TWRP 3.5.2
fastboot boot twrp.img
Install TWRP 3.5.2 .zip and Reboot to TWRP
WIPE Data Factory Reset and type YES to confirm and Reboot to TWRP
Flash the ROM and then flash TWRP 3.5.2
Reboot to TWRP Again
Flash ROM again then TWRP again
Reboot once then flash magisk etc via twrp
The process is more simple to just install magisk on stock OOS and I hope soon Jaguar will update to android 12, then the latest twrp should work with it
You will of course also need to have the android platform tools installed
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Worst case scenario I have found with OP6T, like not able to boot into recovery or anything
I can just do a factory flash with MSM tool using the patched version and then follow the above steps again
Everything is working, thanks so much for your help- I will pay it forward.