Related
I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.
I downloaded the OTA zip and have tried to install it in 2 different ways:
In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"
From TWRP on the device, going to Install, and selecting the downloaded zip.
In both cases, I get the same error:
Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has google/razor/flo:4.3/JSS15Q/779366:user/release-keys.
Click to expand...
Click to collapse
I'm not real sure what that error means, or how to go about addressing it. Any suggestions?
Thanks
You can't flash the OTA in TWRP, at least I don't think so, but I do know that 5.0 requires the latest version of TWRP, think it's 2.8.1.0
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
Tried updating to TWRP 2.8.1.0, I couldn't even get adb to recognize the tablet when in sideload. Just gave me device not found.
But, based on your other comment, I grabbed Wug's Nexus Root Toolkit and reflashed the stock recovery. Sideload is now in progress, I think I'm good to go (I probably just jinxed it!)
Thanks a lot for the help. I had thought it would just replace the recovery - I didn't realize that actually prevented it from running.
Update TWRP in bootloader. Fasboot flash recovery recovery.img
cabadam said:
I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.
I downloaded the OTA zip and have tried to install it in 2 different ways:
In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"
From TWRP on the device, going to Install, and selecting the downloaded zip.
In both cases, I get the same error:
I'm not real sure what that error means, or how to go about addressing it. Any suggestions?
Thanks
Click to expand...
Click to collapse
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.
You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
jj14 said:
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.
You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
Click to expand...
Click to collapse
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
cabadam said:
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
Click to expand...
Click to collapse
Weird - did you modify your build.prop for any reason?
jj14 said:
Weird - did you modify your build.prop for any reason?
Click to expand...
Click to collapse
Nope. When I got the tablet, I rooted it, flashed TWRP, but didn't modify anything else. And basically the root was just so I could do full backups.
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
Build fingerprint error when flashing 5.0 OTA via stock recovery
ImjuzCY said:
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue
Same problem
Hey guys!
I have the exact same problem as OP.
tried installing the zip using the latest version of TWRP and got the same error as OP.
I reverted back to stock recovery and tried to install the OTA update and I got a similar error (image attached).
I'm stuck, could someone help?
Rooted Nexus 7 2013 running 4.4.4 with TWRP 2.8.1.0
Same here. Build.prop has the desired release keys but cwm is giving me the exact same error. Anyone have any suggestions?
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
You need to be in kk stock with all apps from Google. !
I used NRT with sideload and no problem to flash 5.0 !
ahmao said:
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
Click to expand...
Click to collapse
ahmao, when you say comment you mean this
Code:
/*comment goes here*/
as they do with CSS?
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
Click to expand...
Click to collapse
As suggested, I tried that. Commented out the lines. Now when trying to flash it just says "Installing Update" then "Installation Aborted" gives no further details. Thanks for the suggestion though.
I had same problems on n4.
I tried flashing stock recovery. Doesn't work. So, I flashed the whole stock 4.4.4 rom, and then apply the Ota. And it worked.
But I had to wipe my user data. (maybe not necessary)
Envoyé de ma Nexus 7.2 depuis tapatalk
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
comment means add a hash "#" in front of the script line.
if further check fails, just find the line and comment out the app_check line.
bwat1009 said:
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
Click to expand...
Click to collapse
Thanks man!
That worked perfectly!
I lost all my data (which is fine) plus I really needed to start from scratch at some point.
I'm trying to install TWRP custom recovery, but it seems to be crashing all the time.
Does TWRP support Android 5.0 yet?
For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.
Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps
I'm having the exact same problem. I'm attaching what's appearing on TWRP.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app
^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.
newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx
mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Edit : Nougat running on my op3.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.
anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.
dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....
Thanks! Will try and let you know
abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.
Hello
After I got the OTA update of my rooted Chinese Mate 8 AL10, I obviously lost root access, but luckily the update didn't wipe my data. I also had TWRP
Now I have Android 7 and EMUI 5. I recall there were different TWRP versions depending on the version of EMUI, whether it was 4.0 or 4.1.
So is there a specific version of TWRP for Android 7 running with EMUI 5? If yes, what is it? I tried searching with scarse results! I want to avoid boot loops and phone recovery.
Also, is there a specific version of SuperUser to flash?
Thanks
HuaweiMate8 said:
Hello
After I got the OTA update of my rooted Chinese Mate 8 AL10, I obviously lost root access, but luckily the update didn't wipe my data. I also had TWRP
Now I have Android 7 and EMUI 5. I recall there were different TWRP versions depending on the version of EMUI, whether it was 4.0 or 4.1.
So is there a specific version of TWRP for Android 7 running with EMUI 5? If yes, what is it? I tried searching with scarse results! I want to avoid boot loops and phone recovery.
Also, is there a specific version of SuperUser to flash?
Thanks
Click to expand...
Click to collapse
I have L09C432B560. I use the following twrp:
http://sillanwali.com/downloads/twrp-3.0.3.img
I boot into twrp, mount system and vendor then flashed the following patched boot.
https://mega.nz/#!Yx4h3LwL!XNdOjpo-J...j6opIqSemyqI80
I now have full root on my mate 8. Remember, this might not work with your phone. If you want to try it out you should be able to reflash the current boot.img of your phone if necessary.
If the above link does not work, try the link in #3573 or #3572 of the following page:
https://forum.xda-developers.com/mate-8/development/rom-kangvip-slim-t3318572/page358
Thanks. I'll try this when I can
[email protected] said:
I have L09C432B560. I use the following twrp:
https://forum.xda-developers.com/mate-8/development/rom-kangvip-slim-t3318572/page358
Click to expand...
Click to collapse
Hi
Official TWRP is 3.0.2.0 as per https://twrp.me/ and it doesn't seem to work on Chinese Mate 8 AL10 and EMUI 5.0. So I tried the TWRP version you mentioned and it does work up to a certain point. I mean I can successfully install it, and boot to TWRP, but it seems that it doesn't recognize any file system, even my data partition cannot be seen. Yet if I just reboot the phone, I can successfully see my data partition and my data.
Maybe this unofficial version still has problems and doesn't recognize the data partition because it is somehow encrypted? I really don't want to format the phone, I have loads of data I don't want to lose and taking a backup takes ages.
All I want now is to be able to see any partition that has the SuperUser.zip to flash. I really don't care about TWRP as much as I care of gaining root access. I still didn't try with an OTG key as I am travelling, but once I get back home, I'll try that, but if TWRP cannot mount the SYSTEM partition I guess then it cannot flash SuperUser.zip even with OTG...
Right?
HuaweiMate8 said:
Hi
Official TWRP is 3.0.2.0 as per https://twrp.me/ and it doesn't seem to work on Chinese Mate 8 AL10 and EMUI 5.0. So I tried the TWRP version you mentioned and it does work up to a certain point. I mean I can successfully install it, and boot to TWRP, but it seems that it doesn't recognize any file system, even my data partition cannot be seen. Yet if I just reboot the phone, I can successfully see my data partition and my data.
Maybe this unofficial version still has problems and doesn't recognize the data partition because it is somehow encrypted? I really don't want to format the phone, I have loads of data I don't want to lose and taking a backup takes ages.
All I want now is to be able to see any partition that has the SuperUser.zip to flash. I really don't care about TWRP as much as I care of gaining root access. I still didn't try with an OTG key as I am travelling, but once I get back home, I'll try that, but if TWRP cannot mount the SYSTEM partition I guess then it cannot flash SuperUser.zip even with OTG...
Right?
Click to expand...
Click to collapse
This twrp cannot mount the data partition but you can mount the system partition and vendor. You then can flash the patched boot mention which also contain superSU that gives you root.. Do not use this twrp to format the data partition.
---------- Post added at 03:29 PM ---------- Previous post was at 03:00 PM ----------
HuaweiMate8 said:
Hi
Official TWRP is 3.0.2.0 as per https://twrp.me/ and it doesn't seem to work on Chinese Mate 8 AL10 and EMUI 5.0. So I tried the TWRP version you mentioned and it does work up to a certain point. I mean I can successfully install it, and boot to TWRP, but it seems that it doesn't recognize any file system, even my data partition cannot be seen. Yet if I just reboot the phone, I can successfully see my data partition and my data.
Maybe this unofficial version still has problems and doesn't recognize the data partition because it is somehow encrypted? I really don't want to format the phone, I have loads of data I don't want to lose and taking a backup takes ages.
All I want now is to be able to see any partition that has the SuperUser.zip to flash. I really don't care about TWRP as much as I care of gaining root access. I still didn't try with an OTG key as I am travelling, but once I get back home, I'll try that, but if TWRP cannot mount the SYSTEM partition I guess then it cannot flash SuperUser.zip even with OTG...
Right?
Click to expand...
Click to collapse
This twrp cannot mount the data partition but you can mount the system partition and vendor. You then can flash the patched boot mention which also contain superSU that gives you root.. Do not use this twrp to format the data partition.
View attachment SuperSU-v2.79-201612051815-EMUI5.0.zip
TWRP_N.img https://mega.nz/#!9ZEhgALb!uzffZsUi6bJXev2pymFE2Bb_v1Zs949PY8amtALNStc
We are having the same issue with the Mate 9. Have a look the forums there as a lot of things are very similar up to this point. In emui 5 flashing SuperSU will put you in a bootloop. I'm sure KangVIP had a modded boot with root available for the Mate 8 that you guys can flash to have root. They do for the Mate 9.
[email protected] said:
This twrp cannot mount the data partition but you can mount the system partition and vendor. You then can flash the patched boot mention which also contain superSU that gives you root.. Do not use this twrp to format the data partition.
Click to expand...
Click to collapse
You're right, this TWRP can't mount /data and you cannot use it to make a backup but it can perfectly flash system images.
If you flash this one https://mega.nz/#!Yx4h3LwL!XNdOjpo-JmTXCPXz5wcuSGzxtHLVyj6opIqSemyqI80 you will be rooted with phh's SuperUser/ OpenSource SELinux-capable SuperUser (https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394).
For me this is better because it allows me to use YeloPlay, a Belgian Telenet TV watch program that doesn't work on rooted devices but now it does
I tried flashing unsecured boot.IMG for b577 but I had fingerprint I'd on. After flashing I couldn't get into my phone. Do I have to turn off fingerprint to flash modified boot.img?
Sent from my HUAWEI NXT-AL10 using Tapatalk
bidi1234 said:
I tried flashing unsecured boot.IMG for b577 but I had fingerprint I'd on. After flashing I couldn't get into my phone. Do I have to turn off fingerprint to flash modified boot.img?
Sent from my HUAWEI NXT-AL10 using Tapatalk
Click to expand...
Click to collapse
The answer is in your question YES
I did with magisk,
Super easy
Sent from my HUAWEI NXT-L29 using XDA-Developers Legacy app
It is a little annoying that I can't use OTA because of my custom recovery (TWRP).
As of now I need root for 1 thing: backing up my apps.
Is there any way to backup apps the same as in Titanium backup (with the data of the apps) but without root?
This way I could use the OTA to update the phone
Thanks,
orma
Try out Helium Backup. It's free on the app store. You need to install this app on a PC however to enable backing up.
I tried it, but some apps cannot be backed up and the one I need the most is also in the list.
Is there any other way?
Here's what to do, root your phone and then get flashfire. You'll be able to flash the ota with it maintaining root and a custom recovery if you use it. You can also create backups with flashfire. You get the best of both worlds. Don't forget you can also download the ota's from Google if you can't wait for them to be pushed to your phone. It's also easier this way.
Can't I just use TWRP to flash the ota image?
I already have it installed
You'll loose root and twrp for sure and I don't think it will flash because you have twrp installed.
jd1639 said:
You'll loose root and twrp for sure and I don't think it will flash because you have twrp installed.
Click to expand...
Click to collapse
I looked in the comments about the app and a lot of people say that it's not working in Android Oreo.
I want to use it to flash the new oreo September security update.
Should I still use it?
It's working on my 5x with Oreo. I flashed Oreo with it and the sept update.
jd1639 said:
It's working on my 5x with Oreo. I flashed Oreo with it and the sept update.
Click to expand...
Click to collapse
okay, i will try and update. so i just download it from the playstore?
Yes. Some of its self explanatory. You're going to want to inject supersu, everoot, and in reboot have normal and preserve recovery checked.
jd1639 said:
Yes. Some of its self explanatory. You're going to want to inject supersu, everoot, and in reboot have normal and preserve recovery checked.
Click to expand...
Click to collapse
I downloaded the zip file from google site to my nexus 5x and the app doesn't recognizes it to be flashed.
it does recognize the zip file of supersu (already have it installed)
what should i do?
orma1 said:
I downloaded the zip file from google site to my nexus 5x and the app doesn't recognizes it to be flashed.
it does recognize the zip file of supersu (already have it installed)
what should i do?
Click to expand...
Click to collapse
That doesn't make any sense. I've done this 20 or more times with various nexus devices. It's possible the file was corrupted while downloading. Can you find the file on your device. It'd try downloading it again.
You're using the flash zip or ota and not firmware package?
jd1639 said:
That doesn't make any sense. I've done this 20 or more times with various nexus devices. It's possible the file was corrupted while downloading. Can you find the file on your device. It'd try downloading it again.
You're using the flash zip or ota and not firmware package?
Click to expand...
Click to collapse
Downloaded it from here: https://developers.google.com/android/images
from factory images tab
edit: downloaded from the Full OTA Images tab and it does recognize it should i flash it?
i used flash zip or ota
orma1 said:
Downloaded it from here: https://developers.google.com/android/images
from factory images tab
edit: downloaded from the Full OTA Images tab and it does recognize it should i flash it?
i used flash zip or ota
Click to expand...
Click to collapse
Yes. The full ota is the right file.
jd1639 said:
Yes. The full ota is the right file.
Click to expand...
Click to collapse
I have those 3 options to check:
auto-mount
mount /system read/write
restore boot and recovery images
which one to check
orma1 said:
I have those 3 options to check:
auto-mount
mount /system read/write
restore boot and recovery images
which one to check
Click to expand...
Click to collapse
Only have restore boot and recovery
jd1639 said:
Only have restore boot and recovery
Click to expand...
Click to collapse
sorry for all of those question but the description of this make it sound like it would install the stock recovery instead of twrp
the description: Attempt restore stock boot and recovery images before flashing. May be required for some OTAs. Disable for non-OTA updates.
When you hit the check mark on that screen you'll be brought to another screen. On that one you'll see reboot. Click on that and you'll have the option to preserve recovery. That's were it'll keep twrp on your device. So restore boot and recovery is the correct setting
jd1639 said:
When you hit the check mark on that screen you'll be brought to another screen. On that one you'll see reboot. Click on that and you'll have the option to preserve recovery. That's were it'll keep twrp on your device. So restore boot and recovery is the correct setting
Click to expand...
Click to collapse
oh ok Thank you very much!
edit: it worked fine Thanks
orma1 said:
oh ok Thank you very much!
Click to expand...
Click to collapse
No problem