Ok with a lot of requests for different solutions, I built this tool which will put you TOTALLY stock on K1_A301_02_02_110725_US with or without a permanent root. From here, you should be able to root or stock ALL flavors of the K1.
The permanent root will stay through OTA’s therefore you should be able to root every K1 on the market with this tool. Note, the permanent root(#) is su and busybox only. If you want Superuser.apk (GUI in apps), then you will have to download one from the Marketplace and install it.
Why this version: You should be able to use this version to update to any version located at http://download.lenovo.com/slates/k1/OTA/ AS LONG AS you pay attention and READ these instructions. You can load a stock SG version or CA version, or just stay with US. The stock can be rooted(#) or totally stock with no root(#). It's up to you. The 02_02 has a US bootloader which might NOT work with other versions so you have to find an OTA zip file that contains a blob and is at least the same version or newer than the US 02_02. Then manually copy it to your tablet and have the recovery install the update for your particular OTA. The blob is the key to flashing to your country version. Make sure you get an OTA with a blob.
///////////////////////////////////////////
Example: Lets say you want to flash to a CA version, then do the following:
Make sure your battery is charged to at least 70%. This will NOT work unless it is charged to at least 70%
1. Looking on the Lenovo OTA website, you will see there is K1_A301_02_02_110930_CA.zip. It is at least the same version or newer.
2. Download the zip
3. After it is downloaded, look inside the zip for a file called blob. It will be in the root of the zip. You will see boot.img and blob. DO NOT continue if there is NO blob. Look for another OTA zip.
4. ONLY continue if the zip has a blob
5. Download this tool and run it which will flash you to 02_02 US
6. Now plug your tablet’s USB cable into your computer and it should show up as a device under computers as a k1 device.
7. Copy the downloaded file to this folder on your tablet “Computer\K1\Device Storage\Download”.
8. Rename the file to update.zip
9. Power off the tablet
10. Now you must boot to recovery by doing the following. Press down and hold the volume(+) key and while pressing down the volume(+) key press down and hold the power button. Wait for the tablet to power on and then release the power button while still pressing down the volume(+) key.
11. You should see text on the tablet "booting recovery kernel", stop pressing the volume(+) key, and the Green Android guy will appear.
12. The tablet should load the update, and reboot.
13. You’re done, now just allow your tablet to update to the latest version using OTA.
///////////////////////////////////
===============================================
Cautions and warnings:
===============================================
-- The base 02_02 flash will load US base user applications, so if for example, you want CN apps then you’ll have to ensure they will be added via the OTA you update too or eventually update to via OTA. Or, save and or download them manually.
-- All data on your tablet will be erased, so make sure you have anything you want backed up.
-- I’ve only tested this on going to US, SG and CA updates. Others should work, but I haven’t tested them.
-- Permanent root(#) does stay permanent through the updates that I tested.
-- If you use the permanent root(#) be advised there is NO Superuser.apk GUI. Since each OTA you might want to upgrade to would require a different Superuser.apk, it therefore has been left out. You will have to download a Superuser.apk GUI from the Marketplace if you want one. Root(#) su and busybox still will work without the Superuser.apk.
-- When selecting an OTA get an 02_02 version or the very first version with a blob. Do NOT jump to the latest version. It is best to just let OTA's upgrade you once you get onto your OTA. If you update using an update.zip without a blob and then your system just reboots only showing the lenovo logo then you have loaded incompatible boot loaders. The blob that is in an update.zip is your country's boot loader. When you flash with the US 02_02 it loads the US boot loader (blob). Therefore when you switch to a non US OTA you will need a different boot loader. Therefore,you'll want to make sure that you use the very first OTA with your country's blob (boot loader) and then let OTA's update you to the current version.
--------------------------------------------------
If this helps, click the thanks button to let me know
--------------------------------------------------
Here's the link to the tool:
http://depositfiles.com/files/qcnhlcznq
++++++++++++++++ UPDATE ++++++++++++++++++
If you roll the OTA's on the US version (and want to stay rooted), I have discovered that when you go from 04_04 using OTA it will flash you to 11_11 and remove root and then when you go to 12_12US it rewards you again with another dump removing root again. In going from 04_04 to 11_11 they expand the /system partition by lay it down NEW. They seem to happily do it again going from 11_11 to 12_12. Since they do this, they wipe out permanent root. So, when you get to 04_04US you will need to turn on the backdoor, the backdoor should let you back in as root therefore you can re-root(#) after taking 11_11US and 12_12US. Also, going from 12_12 to 13_13 is yet another system reload, so again you'll need to use the backdoor method.
Moral of the story: Permanent root isn't so permanent especially if they wipe the tablet's /system folder. But there's more than one way to skin a banana.
++++++++++++++++++++++++++++++++++++++++++++
TD
timmyDean said:
Ok with a lot of requests for different solutions, I built this tool which will put you TOTALLY stock on K1_A301_02_02_110725_US with or without a permanent root. From here, you should be able to root or stock ALL flavors of the K1.
The permanent root will stay through OTA’s therefore you should be able to root every K1 on the market with this tool. Note, the permanent root(#) is su and busybox only. If you want Superuser.apk (GUI in apps), then you will have to download one from the Marketplace and install it.
Why this version: You should be able to use this version to update to any version located at http://download.lenovo.com/slates/k1/OTA/ AS LONG AS you pay attention and READ these instructions. You can load a stock SG version or CA version, or just stay with US. The stock can be rooted(#) or totally stock with no root(#). It's up to you. The 02_02 has a US bootloader which might NOT work with other versions so you have to find an OTA zip file that contains a blob and is at least the same version or newer than the US 02_02. Then manually copy it to your tablet and have the recovery install the update for your particular OTA. The blob is the key to flashing to your country version. Make sure you get an OTA with a blob.
///////////////////////////////////////////
Example: Lets say you want to flash to a CA version, then do the following:
Make sure your battery is charged to at least 70%. This will NOT work unless it is charged to at least 70%
1. Looking on the Lenovo OTA website, you will see there is K1_A301_02_02_110930_CA.zip. It is at least the same version or newer.
2. Download the zip
3. After it is downloaded, look inside the zip for a file called blob. It will be in the root of the zip. You will see boot.img and blob. DO NOT continue if there is NO blob. Look for another OTA zip.
4. ONLY continue if the zip has a blob
5. Download this tool and run it which will flash you to 02_02 US
6. Now plug your tablet’s USB cable into your computer and it should show up as a device under computers as a k1 device.
7. Copy the downloaded file to this folder on your tablet “Computer\K1\Device Storage\Download”.
8. Rename the file to update.zip
9. Power off the tablet
10. Now you must boot to recovery by doing the following. Press down and hold the volume(+) key and while pressing down the volume(+) key press down and hold the power button. Wait for the tablet to power on and then release the power button while still pressing down the volume(+) key.
11. You should see text on the tablet stating recovery launching, stop pressing the volume(+) key, and the Green Android guy will appear.
12. The tablet should load the update, and reboot.
13. You’re done, now just allow your tablet to update to the latest version using OTA.
///////////////////////////////////
===============================================
Cautions and warnings:
===============================================
-- The base 02_02 flash will load US base user applications, so if for example, you want CN apps then you’ll have to ensure they will be added via the OTA you update too or eventually update to via OTA. Or, save and or download them manually.
-- All data on your tablet will be erased, so make sure you have anything you want backed up.
-- I’ve only tested this on going to US, SG and CA updates. Others should work, but I haven’t tested them.
-- Permanent root(#) does stay permanent through the updates that I tested.
-- If you use the permanent root(#) be advised there is NO Superuser.apk GUI. Since each OTA you might want to upgrade to would require a different Superuser.apk, it therefore has been left out. You will have to download a Superuser.apk GUI from the Marketplace if you want one. Root(#) su and busybox still will work without the Superuser.apk.
-- When selecting an OTA get an 02_02 version or the very first version with a blob. Do NOT jump to the latest version. It is best to just let OTA's upgrade you once you get onto your OTA. If you update using an update.zip without a blob and then your system just reboots only showing the lenovo logo then you have loaded incompatible boot loaders. The blob that is in an update.zip is your country's boot loader. When you flash with the US 02_02 it loads the US boot loader (blob). Therefore when you switch to a non US OTA you will need a different boot loader. Therefore,you'll want to make sure that you use the very first OTA with your country's blob (boot loader) and then let OTA's update you to the current version.
--------------------------------------------------
If this helps, click the thanks button to let me know
--------------------------------------------------
Here's the link to the tool: http://www.multiupload.com/NQJ6LVTA5Y
TD
Click to expand...
Click to collapse
Can you root TPT with this??
There are more than 500$ waiting for you if you can root TPT
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
now it's 700$
http://thinkpadtabletforums.com/thi...pment/bounty-for-rooting-the-thinkpad-tablet/
yirsung said:
Can you root TPT with this??
There are more than 500$ waiting for you if you can root TPT
Click to expand...
Click to collapse
No dice, the K1 had it's key accidentally released. The TPT is still locked tight. It's kinda cruel for you to have to share the same XDA forum with us but hopefully it'll give you hope that the TPT will eventually get root.
If you want to test, then test if the leaked keys work
yirsung said:
Can you root TPT with this??
There are more than 500$ waiting for you if you can root TPT
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
now it's 700$
http://thinkpadtabletforums.com/thi...pment/bounty-for-rooting-the-thinkpad-tablet/
Click to expand...
Click to collapse
Not with this. But in theory, you could use this principle. The key would be does the thinkpad recognize the ASUS leaked key? Which is what makes 'time-travel to any OTA possible' (flux capacitor).
Here's my questions:
1. Does the thinkpad have Nvida chipset therefore Nvflash is supported?
2. If yes, then does this command work "./nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync"
Note, this will NOT cause any damage to your tablet. It will just test if we can unlock the boot loader. If this unlocks it, then YES, you can dump off what we need to build tools to flash it. I've attached the transformer files you'll need to test the keys. You just need the Nvflash tool installed. So, give this a try, if it works then we should be able to build a root flash. If not, then we'll need to wait for a set of leaked keys or for someone to find a hole in the OS to exploit to gain root.
TD
timmyDean said:
1. Does the thinkpad have Nvida chipset therefore Nvflash is supported?
Click to expand...
Click to collapse
Yeah, it has the Tegra 2 just like ours.
gallahad2000 said:
Yeah, it has the Tegra 2 just like ours.
Click to expand...
Click to collapse
Ok, so can you load the transformer bootloader ??? Someone will have to test the leak with the transformer boot. These keys probably won't unlock the TPT boot loader but would allow us access to the data. Then we could build a different boot loader, root it, and then flash in TPT boot loader. Sort of like booting to a CD with Linux and then mounting your C: drive and putting an exploit in it. Then booting back to Windows. Anyway, the key is can we get the TPT to recognize another boot loader that we have the keys for?
NOTE: To test this you'll have to put the TPT into APX (flash/fastboot) mode. So, someone will have to say what the key combination is for it.
Also, does anyone know if the boot loader for the TPT was every unlocked?
If so, what version, or has it always been locked? I mean way back as anyone can recall. Not what they have. If it was ever unlocked then all we'd have to do is get our hands on the nvida unlocked boot loader. That would be easier than building one.
Also, what version (exact tablet and a link would be helpful) is everyone trying to root? If the boot loader test works, I'll go buy one and root it, so I'll need to know what to get.
Thanks,
TD
timmyDean said:
Also, does anyone know if the boot loader for the TPT was every unlocked?
If so, what version, or has it always been locked? I mean way back as anyone can recall. Not what they have. If it was ever unlocked then all we'd have to do is get our hands on the nvida unlocked boot loader. That would be easier than building one.
Also, what version (exact tablet and a link would be helpful) is everyone trying to root? If the boot loader test works, I'll go buy one and root it, so I'll need to know what to get.
Thanks,
TD
Click to expand...
Click to collapse
I think it is unlocked.
Here:
http://forum.xda-developers.com/showthread.php?t=1231771
---------- Post added at 01:16 AM ---------- Previous post was at 01:15 AM ----------
timmyDean said:
Not with this. But in theory, you could use this principle. The key would be does the thinkpad recognize the ASUS leaked key? Which is what makes 'time-travel to any OTA possible' (flux capacitor).
Here's my questions:
1. Does the thinkpad have Nvida chipset therefore Nvflash is supported?
2. If yes, then does this command work "./nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync"
Note, this will NOT cause any damage to your tablet. It will just test if we can unlock the boot loader. If this unlocks it, then YES, you can dump off what we need to build tools to flash it. I've attached the transformer files you'll need to test the keys. You just need the Nvflash tool installed. So, give this a try, if it works then we should be able to build a root flash. If not, then we'll need to wait for a set of leaked keys or for someone to find a hole in the OS to exploit to gain root.
TD
Click to expand...
Click to collapse
I will try it tonite. See what i can get.
Thanks for helping. Let's root this.
---------- Post added at 01:19 AM ---------- Previous post was at 01:16 AM ----------
APX (flash/fastboot) mod?
How do i get in here?
Same as Recovery?I guess not.
I can get into Recovery mod.
yirsung said:
I think it is unlocked.
Here:
http://forum.xda-developers.com/showthread.php?t=1231771
---------- Post added at 01:16 AM ---------- Previous post was at 01:15 AM ----------
I will try it tonite. See what i can get.
Thanks for helping. Let's root this.
---------- Post added at 01:19 AM ---------- Previous post was at 01:16 AM ----------
APX (flash/fastboot) mod?
How do i get in here?
Same as Recovery?I guess not.
I can get into Recovery mod.
Click to expand...
Click to collapse
I do NOT know how to get into APX mode. On the K1 you power off and then hold press and hold the + and - volume keys and press and hold the power button. You will see Windows detect the device and should see the APX driver loaded. But, for the TPT, no idea.
TD
Another thing you could try, after testing the keys for the ASUS is can you talk to the device via adb when you are in recovery? I doubt they left the hole open, but when you boot to recovery you are actually loading from the SOS partition another copy of Linux. On some tablets, you force the recovery to boot and of course it crashes with yellow !, which is normal. But at this time you are able to connect to it via adb shell. If you can, you will be root(#) on the SOS partition (there is no security on SOS, or at least there shouldn't be). Then you mount p6 rw put in your su, and reboot. But, I doubt they left that open, but it's worth a try. It would be easier than building boot loaders.
TD
timmyDean said:
Another thing you could try, after testing the keys for the ASUS is can you talk to the device via adb when you are in recovery? I doubt they left the hole open, but when you boot to recovery you are actually loading from the SOS partition another copy of Linux. On some tablets, you force the recovery to boot and of course it crashes with yellow !, which is normal. But at this time you are able to connect to it via adb shell. If you can, you will be root(#) on the SOS partition (there is no security on SOS, or at least there shouldn't be). Then you mount p6 rw put in your su, and reboot. But, I doubt they left that open, but it's worth a try. It would be easier than building boot loaders.
TD
Click to expand...
Click to collapse
Ok, I got into APX mode
However, can not find a driver for it.
Is the driver universal?
yirsung said:
Ok, I got into APX mode
However, can not find a driver for it.
Is the driver universal?
Click to expand...
Click to collapse
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/adb_driver_20110720.zip
Thanks but it is for ADB not APX
yirsung said:
Thanks but it is for ADB not APX
Click to expand...
Click to collapse
here it is:
http://android.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active/
Now I did "nvflash --sync"
It said
Nvflash started
Command send failed <usb write failed>
Damn it
yirsung said:
Now I did "nvflash --sync"
It said
Nvflash started
Command send failed <usb write failed>
Damn it
Click to expand...
Click to collapse
You have to use the complete command with the SBK keys and the transformer.bin
which I posted. Write failed means the bootloader is locked.
"./nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync"
This command ONLY mounts the transformer blob. IT WILL NOT destroy anything. I just don't want to waste money on buying one.
Also, try the recovery exploit now that you have the drivers loaded.
ALSO what's the secret key combination to get into APX mode????
timmyDean said:
You have to use the complete command with the SBK keys and the transformer.bin
which I posted. Write failed means the bootloader is locked.
"./nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync"
This command ONLY mounts the transformer blob. IT WILL NOT destroy anything. I just don't want to waste money on buying one.
Also, try the recovery exploit now that you have the drivers loaded.
ALSO what's the secret key combination to get into APX mode????
Click to expand...
Click to collapse
I can do it with "./"
So did nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync
here is what I got
Nvflash started
nvflash configuration file error: file not found
---------- Post added at 08:28 AM ---------- Previous post was at 08:27 AM ----------
I put Nvflash under my SDK files (same folder with ADB)
then I put all files you gave me to the same folder .
any thing wrong?
yirsung said:
I can do it with "./"
So did nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync
here is what I got
Nvflash started
nvflash configuration file error: file not found
---------- Post added at 08:28 AM ---------- Previous post was at 08:27 AM ----------
I put Nvflash under my SDK files (same folder with ADB)
then I put all files you gave me to the same folder .
any thing wrong?
Click to expand...
Click to collapse
Got the correct files http://forum.xda-developers.com/showpost.php?p=21373483&postcount=4 the files I posted???
It should be only three files and you will need them in your folder, so can you check they're there?
timmyDean said:
Got the correct files http://forum.xda-developers.com/showpost.php?p=21373483&postcount=4 the files I posted???
It should be only three files and you will need them in your folder, so can you check they're there?
Click to expand...
Click to collapse
Yes, that's what I did. I guess the key won't work on TPT
yirsung said:
Yes, that's what I did. I guess the key won't work on TPT
Click to expand...
Click to collapse
Missing file is a filing missing not that the keys don't work? Sounds like the keys work, but it's hard to tell remotely.
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
Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.
Click to expand...
Click to collapse
Please Lock!
Placeholder reserve
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)
Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu
Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror
Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.
Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?
I originally posted this method at AddictiveTips. The method I posted there is targeted at everyone including the absolute beginners and I have also included instructions there for setting up the required tools, and for reverting back to the original recovery and boot image in case anything goes wrong. All external credits should be given to that guide (it does link back to this thread). Here is the link: How To Root Nexus 4 and Install ClockworkMod Recovery on it.
To my knowledge, this is the first confirmed working rooting method for Nexus 4 posted here at XDA. Though my knowledge is limited, so please correct me if I am wrong.
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
This method requires an unlocked bootloader. You can find instructions for unlocking it at XDA, or at the AddictiveTips guide linked above (the link to the bootloader unlock guide is in the requirements section there).
UPDATE 2: If your device does NOT get wiped after unlocking the bootloader, fret not. While this isn't expected behavior, several users have experienced the same on the Nexus 4. This could be due to some error at Google's end, but unlocking still works perfectly fine.
That said, let's get on with rooting and flashing CWM.
ClockworkMod Recovery Method:
Download the latest official ClockworkMod recovery from CWM website and rename it to recovery.img
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Download the recovery flashable SuperSU package with Busybox and transfer it to your phone's internal SD card.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Enter this command in a command prompt to flash the ClockworkMod recovery (making sure you are in the directory where you downloaded the recovery file):
Code:
fastboot flash recovery recovery.img
OR
If you simply want to root without flashing a custom recovery and want to stick to your stock recovery, simply boot this recovery once using this command:
Code:
fastboot boot recovery.img
If you flashed the recovery in the previous step, you can now boot into recovery by pressing volume-up or volume-down twice to select the recovery option, and then the power button to enter it. If you simply booted into the recovery file without flashing it in the previous step, you should already be in recovery now.
Once in recovery, take a backup to be on the safe side.
Flash the downloaded SuperSU and busybox package zip file from recovery.
Clear cache and dalvik cache just in case (not required but won't hurt).
Reboot the device.
ADB and Insecure Boot Image Method:
Grab the insecure boot image from this thread.
Also download these root files. This package includes the latest SuperSU 0.98, latest su binary that comes with it, and working busybox (not sure if latest).
Extract the contents of the downloaded zip file to your computer.
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Get back into bootloader mode and boot into the downloaded insecure boot image:
Code:
fastboot boot boot.img
Don't worry, this will not replace your existing boot image and will only boot from the insecure one once.
If it does NOT work for you and you get stuck in a boot loop, simply reboot your phone into bootloader and use the above command again. Some users had issues with booting from it the first time, but a second attempt worked.
Once booted into Android successfully using the insecure boot image, simply enter these commands one by one in command prompt (making sure you are in the directory where you downloaded the files):
Code:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
Reboot your device.
You will now have root access. Tested and confirmed working by Stryder5 and many others.
Credits:
Stryder5 for testing, confirming, tipping me about working CWM, providing the required drivers, and helping others on the thread. :highfive:
Harry GT-S5830 for the insecure boot image.
fkrone for his recovery revert disabler script and his unofficial working CWM before an official one became available.
Kstarz for posting this same recovery method with his own working CWM in this thread before an official one was out.
evaradar for informing about the release of official ClockworkMod recovery.
Koush for developing ClockworkMod recovery.
Chainfire for developing SuperSU.
Everyone else on this thread for testing, providing feedback and hitting the 'THANKS' button. =)
I have tried my best to give everyone the due credit but if I have missed out on anyone, please do remind me.
Yep, worked like a charm. Got Titanium running and restored all my apps
Btw, check your PM.
Checked...thanks. =) Added the links.
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
jshaw06 said:
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
Click to expand...
Click to collapse
You need to boot the unsecure boot.img first.
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
HQRaja said:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
Click to expand...
Click to collapse
I'm pretty sure I used the one Harry GT-S5830 provided.
I used the one in the OP of that thread.. is there a different one I'm supposed yo use?
Sent from my SGH-T999 using Tapatalk 2
---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------
It works
Sent from my SGH-T999 using Tapatalk 2
jshaw06 said:
It works
Click to expand...
Click to collapse
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Stryder5 said:
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Click to expand...
Click to collapse
No issues with installing the OTA after root?
Edit: Just noticed in your sig that you did not install the update.
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
jshaw06 said:
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You mean you gained root after you installed the OTA?
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
apzalo said:
No issues with installing the OTA after root?
Click to expand...
Click to collapse
I gained root, but haven't installed the OTA yet.
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Yes sorry gained root after OTA
Sent from my SGH-T999 using Tapatalk 2
Elemenopee said:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Click to expand...
Click to collapse
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Ngo93 said:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
Click to expand...
Click to collapse
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)
0.0 said:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Click to expand...
Click to collapse
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
HQRaja said:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
Click to expand...
Click to collapse
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
fran1563 said:
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Click to expand...
Click to collapse
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
fran1563 said:
I?m the worst to follow what you write, because i'm just barely know press the button ON in my tablet but upgrade what I did this time far away, I taken to a tecnician who said I erased recovery's mode and then he can't handled any way to install the oldest or newest OS, im from Venezuela where ASUS havent support to tablets yet. I'll take what you said and bring it to somebody to know about software android to help me out. By the way I bought another memo pad 7 but model me170cx dual core, actually isnt bad but I want my me176cx back.
Click to expand...
Click to collapse
Just say what you do not understand, I can explain
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
Mis012 said:
Just say what you do not understand, I can explain
Click to expand...
Click to collapse
Thank you mate, I'm going to try. I'll write you wherever going to happens. I aprecciate!
Mis012 said:
Download the lollipop firmware from asus site. Copy the droidboot.img from within this file. Download newest version of tethered cwm recovery. Go to command line and cd to directory with adb.exe in it. Place droidboot.img in this folder. Within cmd, write fastboot boot droidboot.img
It should reboot rto droidboot. Now open the .bat file, type ACCEPT, and T4. You should boot into cwm recovery. Now install zip/from external sd/WW_lollipop....zip
Then reboot and you should have lollipop
Click to expand...
Click to collapse
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
christelle868 said:
tried fastboot boot droidboot.img several times, device just reboots to fastboot and throws the same errors
Fastboot Starting....
Fastboot Starting....#1
Fastboot Starting....#2
Fastboot Starting....#3
i've searched and found different ways of flashing ME176CX but never a complete solution. With the INtel flash tool I can't find the DNX or IFWI files, with the Asus Flash Tool, cant find the raw firmware file. Can you help???
Click to expand...
Click to collapse
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Mis012 said:
I can try to. Firstly, the droidboot.img has to be the one from ASUS firmware update downloaded from their site. If it doesn't work with it, well I don't know. Ask the support, take it to the store, or - if you really want to dig into it (it should be possible in your situation), then:
Firstly, buy this: (or something similar, but this is known to work well) http://www.amazon.de/gp/product/B00...qid=1440605402&ref_=sr_1_fkmr0_1&sr=8-1-fkmr0
Then, connect it to your tablet and connect usb keyboard to it. Also power it with another USB.
While starting your tablet, spam F2 key to get in UEFI setup. Then, follow some "tutorial" (search this forum for it, I saw it somewhere there) to run Windows/Ubuntu from flash disk. Run any linux distribution, and ask some kind person on lollipop to make an img with dd of entire mmcblk0 . Then use dd to copy it on your mmcblk0.
Warning! this is theoretical. It should work, but I cannot test it. CHECK MULTIPLE TIMES THAT THE img IS NOT CORRUPTED!!!
Lot of luck (even mine, luck will not help my problem anyway)
Sincerely, Mis012
Click to expand...
Click to collapse
i think he got lost on your tutorial XD
fastboot starting
Please, Please advice ..
And I'm one of those tablets which displays a message starting fastboot 1,2,3. I tried almost everything. Well at least I think that everything is okay or if vv. Please advice how to try it changed. Thank you in advance for answers
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