Related
**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!
I have a question whose answer I haven't found anywhere after a good while of searching.
I'm on TWRP 2.x and want to update to 3.x via flashing the latest TWRP image from within recovery, using the instructions given in the TWRP site.
In recovery, I hit install --> images... --> choose .img file, and then I'm asked which partition to flash?
Now, according to TWRP website, I have to choose "recovery" partition, but there is no "recovery" partition to chose, since I'm only presented one option: "kernel" partition.
My question is:
Q.- Must I choose that kernel partition and flash the twrp.img there? I'm afraid of doing it without being sure I'm not going to brick the phone.
Thank you in advance for a reply.
zogoibi said:
I have a question whose answer I haven't found anywhere after a good while of searching.
I'm on TWRP 2.x and want to update to 3.x via flashing the latest TWRP image from within recovery, using the instructions given in the TWRP site.
In recovery, I hit install --> images... --> choose .img file, and then I'm asked which partition to flash?
Now, according to TWRP website, I have to choose "recovery" partition, but there is no "recovery" partition to chose, since I'm only presented one option: "kernel" partition.
My question is:
Q.- Must I choose that kernel partition and flash the twrp.img there? I'm afraid of doing it without being sure I'm not going to brick the phone.
Thank you in advance for a reply.
Click to expand...
Click to collapse
That sounds so complicated, why not download z3cTWRP3020.zip from here, put the zip on your sd caard, start the phone into recovery (hold volume down while starting) go into install section and flash it.
If you need to get recovery installed from a PC there is an easy option here
Or have I missed something obvious?
Thank you, @Didgesteve. Let's blame my bad English. Actually what I'm trying to do is almost the same thing you suggest: flash the TWRP.zip from recovery; except that, instead of flashing the zip file (built by Who-knows-whom), I want to flash the original img file provided by TWRP themselves. The procedure should be quite similar, easy and straightforward, except that when flashing a zip we don't need to specify a partition, whereas when flashing a img we do. Here, according to TWRP's website instructions, we should choose "recovery" partition, but it turns out that, at least in my case, there's no such partition, only a "kernel" partition. Is this the one?
zogoibi said:
Thank you, @Didgesteve. Let's blame my bad English. Actually what I'm trying to do is almost the same thing you suggest: flash the TWRP.zip from recovery; except that, instead of flashing the zip file (built by Who-knows-whom), I want to flash the original img file provided by TWRP themselves. The procedure should be quite similar, easy and straightforward, except that when flashing a zip we don't need to specify a partition, whereas when flashing a img we do. Here, according to TWRP's website instructions, we should choose "recovery" partition, but it turns out that, at least in my case, there's no such partition, only a "kernel" partition. Is this the one?
Click to expand...
Click to collapse
I have read the instructions on the TWRP webpage, but I think you're being too literal with your interpretation. The way I read that is find the right version (.img) that you want and flash it in recovery.
But why not go for the ADB option? Or even easier the TWRP manger app from the play store?
I don't believe there's anything wrong with flashing or installing recovery from either of the first twwo links I posted above. If you think that developers on xda are going to start messing with TWRP code, for what advantage!?!? If the TWRP files peddled on the forums were corrupt or a securtiy risk, then it would have been spotted. by now. TWRP is a recovery partition, it doesn't have any network access or install any other files. I completely understand sourcing original software where you can, but saying TWRP might be a risk, it all sounds a bit tin foil hat to me
TWRP manager app didn't work on my phone. It installs but won't open. ADB commands wants connection to a computer, installing ADB on it, etc. Flashing a file via recovery should (and I'm sure is) straightforward. I have nothing personal against xda-developers' zip files, except that I've read somewhere here about someone who bricked his phone when trying to flash TWRP via a zip file he got here.
Anyway, though I appreciate your suggestions, this debate is actually off-topic. My question, which remains unanswered, is basically very simple: Is the kernel (and only) partition the right one to flash TWRP.img file to?
zogoibi said:
TWRP manager app didn't work on my phone. It installs but won't open. ADB commands wants connection to a computer, installing ADB on it, etc. Flashing a file via recovery should (and I'm sure is) straightforward. I have nothing personal against xda-developers' zip files, except that I've read somewhere here about someone who bricked his phone when trying to flash TWRP via a zip file he got here.
Anyway, though I appreciate your suggestions, this debate is actually off-topic. My question, which remains unanswered, is basically very simple: Is the kernel (and only) partition the right one to flash TWRP.img file to?
Click to expand...
Click to collapse
If you're flashing a kernel (.img) then you use flashtool in fastboot mode, there's no partition to chose.
Hello.
I'm having issues TWRP backups. Maybe I was undone system. I need a friend using the honor 7 PLK-L01 system backup of your phone by then compressed .zip TWRP.roi nk.len up for me to use. My machine is now no longer on the operating system.
*Help me.
thank you
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
Thank.
multi tool can use the phone while I was hanging not. and restore them in any way.
memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
hotboymen2026 said:
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
Click to expand...
Click to collapse
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
memht said:
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
Click to expand...
Click to collapse
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
hotboymen2026 said:
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
Click to expand...
Click to collapse
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
memht said:
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
Click to expand...
Click to collapse
Status phone rom I'm wrong. logo only lead to hang on is TWRP, connect PC and Fastboot. but when I rom stock (PLK-L01 C432B270) is successful but unable to reboot the operating system. H7 is due to the security, it's hard to be rescued. I also put it into the service center (not the local machine), they also confused with my H7. I need to find ways to revive it, no matter how well!
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
Hello! I was following the guide of wiping everything except internal storage and sdcard like the guide said. However now i only see TWRP folder on the /sdcard when trying to flash zip. How do i transfer files, or is there some fastboot file to flash or a guide which i can use to bring my device back alive? Fastboot and TWRP boots, but i cannot access some partitions. Thank you
Edit: Already tried to flash the boot.img that was on the EliteROM v4 zip, however the Product, Vendor, Version, Cust and Data versions are still messed up. I need help on repartinioning advice.
Also now i managed to flash system.imgi, but the partitions need to be resized probably to be used. How is the repartitioning possible the easiest way?
That's very wrong. You only needed to wipe system, data and cache,
sniperlife:D said:
That's very wrong. You only needed to wipe system, data and cache,
Click to expand...
Click to collapse
Hassanmirzans guide says " Wipe Everything in wipe section (dont wipe sdcard) and Format Data & Change FileSystem to f2fs otherwise phone wont boot,,, and reboot twrp and follow next steps,,," which is what i did.
Do you have any more tips? Currently i cannot even use the update.app method at all.
Edit: I just did try the update.zip method, and it says "Software install failed! The update package does not exist. Please download the package again." My computer recognizes the phone as Huawei honor 9p lite now, and i have checked that the UPDATE.APP is under dload folder. Tried with internal storage as well as external sd already.
Edit2: was corrupt UPDATE.APP, now it says "Software install failed! Incompabile package . Please download the package again." Or something similar, do i need to reflash OEM info or something to make my device Honor 5C again?
I solved this because of przemas2468 at modaco. He had posted the OEMinfo file if you manage to mess up your device, which can be found from here: http://www.mediafire.com/file/fn2pv4uucjh63xo/oeminfo_b100_c432.zip
onnz423 said:
I solved this because of przemas2468 at modaco. He had posted the OEMinfo file if you manage to mess up your device, which can be found from here: http://www.mediafire.com/file/fn2pv4uucjh63xo/oeminfo_b100_c432.zip
Click to expand...
Click to collapse
What was your version and model? We have some oeminfo file that may save you from such situations
shashank1320 said:
What was your version and model? We have some oeminfo file that may save you from such situations
Click to expand...
Click to collapse
Thanks man, however i already got the OEMINFO file, and will upload it into a mirror soon. Apperantly it is not possible on XDA to lock thread.
onnz423 said:
Thanks man, however i already got the OEMINFO file, and will upload it into a mirror soon. Apperantly it is not possible on XDA to lock thread.
Click to expand...
Click to collapse
Share the link i will update to my repository and anyone can use. Its locked and a common thread for all models.
shashank1320 said:
Share the link i will update to my repository and anyone can use. Its locked and a common thread for all models.
Click to expand...
Click to collapse
Here you go: https://mega.nz/#!QTZV2YJA!nZASaoDeTiGAx1bwNOu_pnTcGLiraGCqOXMwPkvffj8
This at least worked for NEM-L21. The UPDATE.APP process would not succeed without this file.
onnz423 said:
Here you go: https://mega.nz/#!QTZV2YJA!nZASaoDeTiGAx1bwNOu_pnTcGLiraGCqOXMwPkvffj8
This at least worked for NEM-L21. The UPDATE.APP process would not succeed without this file.
Click to expand...
Click to collapse
Thanks for sharing this. I will update the repository thread asap