Related
Here's a guide on how to restore to stock using the FXZ for OS X/Linux users.
1. Download one of the following fastboot binaries: fastboot-OSX or fastboot-linux and rename it to just "fastboot"
2. Download the FXZ and untar it anywhere.
3. Plug in your phone to your computer (preferably a back USB port if you're on a desktop, don't use a front USB port if possible) and shut it down (leave it plugged in).
4. Hold down the vol-down button on the rocker and boot the phone up, it should boot into AP Fastboot Flash Mode and it should say "OK to Program".
5. Run the following commands in terminal
Code:
./path/to/fastboot flash system /path/to/system.img
./path/to/fastboot flash boot /path/to/boot.img
./path/to/fastboot flash recovery /path/to/recovery.img
./path/to/fastboot -w
6. Shut off the phone by pressing the power button.
7. Boot back up and you should be back to stock!
Thanks for posting this for us linux users. Hopefully I won't have to use it any time soon haha
I keep gettiing permission denied when entering the first command. Any suggestions? Thanks
Will this run without a Bionic attached? I'm just trying to get everything set up and run it to make sure it starts...
dscottjr81 said:
I keep gettiing permission denied when entering the first command ./fastboot flash system system.img. Any suggestions? Thanks
Click to expand...
Click to collapse
BUMP...........
have you tried sudo?
Has anyone had any success with this yet?
1KDS said:
Has anyone had any success with this yet?
Click to expand...
Click to collapse
I am doing it right now. There are some issues. Without sudo, you'll get permission denied. With sudo, you'll get "./fastboot: command not found". After changing fastboot to be executable without sudo, you'll get "./fastboot: cannot execute binary file". With sudo, you'll get "./fastboot: 3: Syntax error: "(" unexpected"...so short story, this does not work properly yet
---------- Post added at 03:37 PM ---------- Previous post was at 03:24 PM ----------
1KDS said:
Has anyone had any success with this yet?
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1279825
There is a one click Linux/Mac return to stock and root method there and it works. Hope that helps. It is extremely easy!
Bionic Restorer for Linux/Mac
OK, I'm finished with the new MotoRooter for Mac/Linux - naming it BionicRestorer because it's completely different. Right now it's in my Dropbox Folder, still no where to put it - lol.
Here's the link to BionicRestorer.zip
For Mac and Linux people - it's BionicRestorer v1.0
A way to flashboot restore your Bionic to 5.5.893
Download it, unzip it, cd into the BionicRestorer directory and type ./BionicRestorer.sh to run it. Mac folks can double click on the Mac-BionicRestorer.command file in that directory.
Linux People - this is solid, I've run it on LinuxMint (Ubuntu) and Scientific Linux (Redhat) and it worked everytime without a glitch.
Mac People - This is tempermental on the Mac, I've tried it on 3 different
Mac's and it worked sporadically on a Macbook Air running 10.7.2, didn't work on the iMac at all running 10.7.2,
and worked consistently on a Macbook running 10.6.8. Use at your OWN RISK!!!! If it hangs, all I
can is - try it again, or, run Linux, or, use RSDlite on Windows.
I can say that it worked consistently on a Macbook running 10.6.8
Option 3 (restore system, boot, recovery seems to work well on a Mac, but,
NOTE that these files are from v5.5.893! If you select option 3 you had better have flashed or updated to that version perviously, or, it will most likely bootloop when it finishes.
Note - This does NOT contain the actual files needed for flashing,
just the brains to flash them. You will need to download the zipfile
VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml.zip from
http://rootzwiki.com...893-fxz-leaked/
then unzip it into the BionicRestorer directory.
Once it is extracted there should be a directory named:
VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml
which contains all the files needed to do a flash restore.
And the menu looks like this:
BionicRestorer.sh (1.0) by crpeck
1. Restore a Bionic to 5.5.893 - NOT FOR 5.9.901 BIONICS!
-restores EVERYTHING to official 5.5.893
-wipes data
2. Restore a 5.9.901 Bionic to 5.5.893
-restores EVERYTHING EXCEPT for the cdt.bin to 5.5.893
-cdt.bin is restored using the 5.9.901 file
-wipes data
** YOU SHOULD ONLY USE THIS IF YOU ARE OR HAVE BEEN ON 5.9.901 **
3. Minimal Restore of system, boot, and recovery only
-restores ONLY the system,boot and recovery to official 5.5.893,
4. Root and ForeverRoot a non-rooted Bionic
-roots and installs the ForeverRoot hack
5. Copy 5.9.901 update file to sdcard
-this copies the unoffical 5.9.901 update file to your sdcard
chances are, your Bionic will bug you to do an update when it see's it
there, you can usually force it via the 'Check for Updates' screen.
6. Verify MD5sums of the flash image files (you should do this at least once)
7. Help - More detailed Information
q. Quit
NOTE: Selections 1-3 do NOT root the phone! Run 4 after running them.
By Your Command (1-7,q):
I took the .xml file from the VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml.zip and re-wrote it into shell scripts (i also took out the piece in there that erases the internal sdcard - who wants to lose that - lol). There is a considerably amount of error-checking as well, but, I'm sure I missed something (which will result in v 1.1).
I encourage you to look through the scripts, feel free to modify and make it better! This may be the last release of this from me, as work is replacing my Bionic with a gnex in the near future - gonna miss the Bionic, it's been a fun learning tool.
Enjoy....
Oh - look at the 00_README_1ST.txt file - it's similar to this writeup, and, select the help option for more detailed information.
I've have to give this a try. I keep forgetting I have Ubuntu(dual-boot) on this thing. Heh
i'm running SafeStrap 3.11 and wiped my safe partition in a late night flashing frenzy. is it possible to flash certain partition images to restore the stock ROM without loosing SafeStrap?
mechanizedmedic said:
i'm running SafeStrap 3.11 and wiped my safe partition in a late night flashing frenzy. is it possible to flash certain partition images to restore the stock ROM without loosing SafeStrap?
Click to expand...
Click to collapse
Flash system.IMG
fastboot flash system /path/to/system.img
fastboot flash boot path/to/boot.img
Any other partition you might want to flash flashing recovery partition will erase safe strap might lose safestrP after flashing system you will lose root regardless
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
[SOLVED]
Verizon Developer Edition. I just did a complete reset to 4.4, stock recovery and all. Booted up, got the 4.4.2 update, installed that. Flashed custom boot logo, then flashed TWRP again. Went to go wipe data/cache and accidentally wiped system. Now I've got no OS.
What do I do now? I've updated to 4.4.2 from 4.4 and can't revert back.
You'll need a good friend who can make a backup in TWRP of just the System partition. This friend probably should have an identical phone, in my case, we both have Verizon Developer Editions. He also needs to be giving you a TWRP system backup that matches what you most recently had flashed. In my case, I had just taken the 4.4.2 update. Luckily he had too already. A TWRP backup of the system partition from someone on 4.4 or 4.2.2 would, I'd guess, brick you. So best to find someone with an identical phone to you and matching software, otherwise I don't know what'd happen. There should be 3 files, a recovery.log, system.ext4.win, and system.win.md5. This is about 1GB so it'll take time to transfer/download/upload around the place.
I had downloaded the adb tools a while back from step 1 here: http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
You need adb and all the drivers and crap working for this
Put the 3 files in that folder, where adb is.
Next, boot into TWRP on your phone with no OS and make a backup of everything, should go quick as there's no system and I'd guess data is probably pretty empty...
Next, go back to TWRP main page and go to mounts, then mount the /Data partition.
Shift and right click in Windows Explorer where adb is and open command prompt, type in adb shell and you should get a prompt. Type ls and hit enter, should see contents of the /Data partition
Type cd sdcard/TWRP/BACKUPS and hit enter, then type ls and hit enter, you should see another folder named T something, this is the phone's serial number. Type "cd serial" where serial is the name of that T folder and hit enter again.
Type ls again and you should see a folder starting with 2014- or whatever year you may be reading this in... that's the folder that has the backup files you just made.
Type mkdir A and hit enter followed by typing ls again, now you should see that 2014- folder and another folder named A
Type exit to get out of shell. Now type adb push recovery.log /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like .005s or something.
You can type adb shell again, enter, and navigate to the directory to make sure there's a recovery.log file in the A folder. If there is, good. If not, no good, you did something wrong. Don't forget to type exit to get out of shell and back into Windows command.
Now do the same for the next small file, so type adb push system.ext4.win.md5 /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like .007s or something.
Finally, the big file. Don't panic like I did, it'll take some time, like 4 minutes maybe. Type adb push system.ext4.win /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like 380s or something.
So, now you should have your TWRP system partition backup files in the A folder in the proper folder hierarchy. Now on the phone, just back out of mounts (hit middle button) and shut phone down and it'll warn you about there not being an OS.
Reboot recovery, Restore, you should now see the folder named A as an option. Hit that, and it should auto select System and nothing else. I did md5 check option. Slide to restore. Wait. Wait. Wait. Reboot.
If you're lucky, you'll see the boot animation and hopefully boot back into Android. It'll take a while the first go too so be patient.
Or, I have a buddy with a Verizon Dev Edition in close proximity... can he just make a backup in TWRP and then I could restore it?
Or is there a way to pull the System.img from his device and flash to mine?
Or how about the system.img from T-mobile? Could I flash that? Or... that wouldn't help would it...
CartlandSmith said:
according to this thread, you can:
[Q] Can you restore a nandroid backup on a different device?
But he needs to be on 4.4.2.
Click to expand...
Click to collapse
Yeah, he's on 4.4.2 already as well. He's making a TWRP backup of just System. So I guess I need to figure out how to get the folder hierarchy and the TWRP backup files onto my device. I assume through ADB somehow?
Also, I did grab the 4.4.2 OTA zip file before doing all this, so I have the update zip, but I don't think that helps me either does it?
Am I missing something, can't you just flash back system images from moto?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Just realized only 4.4 images are posted.
fml
yeah, I realized I could just make a TWRP backup of my empty partitions to get the folder hierarchy made. So now all I should need to do is figure out how to either:
A. Push a folder and sub-folders/files via ADB or
B. Create folders in ADB then push the files to the folders
Sounding good?
GloryUprising said:
Am I missing something, can't you just flash back system images from moto?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
From all I've read and understand, once you upgrade to 4.4.2, the bootloader also gets updated, and the new bootloader isn't backwards compatible, so you can't flash any images older than 4.4.2 else you'll brick somehow.
Just out of curiosity, anyone know how long it takes for factory images to be posted? I assume a metric &#@$ tonne of crap has to be done to get the files and poo from Verizon to Motorola to host.
Yeah. I'm pretty sure TWRP has already made the folder hierarchy for me. I think I just need to get my buddy's TWRP files and then push that folder to the device via ADB with "adb push /TWRP/BACKUPS /mnt/sdcard/TWRP/BACKUPS"
Yeah, I think maybe it's a folder with the device's serial number? T-something?
Okay so can you post the hierarchy I need to make? TWRP>BACKUPS>SERIAL#>BACKUPNAME>Backup Files?
Okay, I've got his TWRP backup of just system downloaded, 3 files. I booted into TWRP recovery and in the mounts sections, I mounted data. Now I can navigate the data folders via ADB shell. I've created a new backup folder "B". Now I think I just need to push the 3 backup files into that folder. Backup folder "A" was the one I made to get TWRP to auto-make the folder hierarchy.
How do I unmount now that I've pushed files?
Not that I can find.
I've got all the files/folders pushed and made. My phone is connected via USB and is in TWRP recovery. If I hit a volume button I get a gray screen with just "Updating partition details... Full SELinux support is present." I don't know what to do from here. I can still do "adb shell" and see my data partition in my command window...
Haven't tried, afraid to lose what I've done so far. If I back out to Restore in TWRP, the directories/backups don't show. I think it's cause my /data is mounted and being used by my PC so TWRP can't see the partition?
Believe it or not, I did this exact something, not paying attention and boom system wiped. I have been a lurker on XDA for years and years and never needed an account because I have never made a stupid mistake like this in the past.
I contacted Moto to see if they would bail me out, but if not I will just wait out the factory image its a tough lesson.
I have reverted back to my my old AOKPs3 until i can get this all figured out.
*I will be watching this to see if you figure it out, and if so maybe you can help me.
GL.
Fingers crossed. Backed out to main TWRP home screen, powered off. Booted back into recovery, Restore tab, my folder showed up with the System backup in there, restoring now...
Success!!!
CartlandSmith said:
there should be a popup warning saying when you wipe your system you run the risk of losing your OS or whatever something shorter, but enough of a warning that it would cause people to stop and think if this was what they intended to do.
Click to expand...
Click to collapse
There wasn't one for me. That or I just completely missed it flying through like I thought I owned those menus...
Mike7143 said:
There wasn't one for me. That or I just completely missed it flying through like I thought I owned those menus...
Click to expand...
Click to collapse
Me either.
Mike, Could you send me the file? Im in the same boat as you "were"
Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks
Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!
Yeah that sorted it thanks a lot
Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,
jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!
Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it
@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.
First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit
As tennear has noted, do NOT backup or restore the EFS partition.
Never restore EFS using TWRP. You will lose its contents and probably your IMEI.
@tennear Thanks for the heads up. I'll remove that part from my guide.
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.
Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk
i can't found same file u can upload again?
Yeah.... most links are dead. Does anyone else have them?
Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.
Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.
Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.
Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?
I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.
Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.
Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now