Hi,
I have a rooted NEM-L51 (with TWRP 3.1.1-0 as recovery) running Android 7.0/EMUI 5.0 (build number NEM-L51C432B350).
A new OTA update is available (build number NEM-L51C432B355) but after downloading and rebooting to recovery (TWRP) to apply it, it fails with the following error:
Code:
script aborted: assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
Updater process ended with ERROR: 7
I googled it but couldn't find anything that seems useful. You'll find attached the complete log (I was using TWRP 3.1.0-2 at the time and has since upgraded, thinking it could be related to it).
Does anyone have any idea about what's going wrong here?
Could it be because the system partition has been modified in the process of rooting the phone (I'm thinking about that because of the 'block_image_verifiy(.../system...)') — note that I was able to apply OTA updates on my rooted device in the past?
Thanks!
You have magisk or SuperSU?!
why you trying to install updates on twrp....
Try useing stock recovery from the update.
PalakMi said:
You have magisk or SuperSU?!
Click to expand...
Click to collapse
SuperSU, v2.82.
thelous said:
why you trying to install updates on twrp....
Click to expand...
Click to collapse
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
AlexMihai26 said:
Try useing stock recovery from the update.
Click to expand...
Click to collapse
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?
Try magisk!
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?
fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?
Click to expand...
Click to collapse
Update.app with stock recovery, zip with twrp
sclarckone said:
SuperSU, v2.82.
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?
Click to expand...
Click to collapse
Yep
PalakMi said:
Try magisk!
Click to expand...
Click to collapse
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash.
Click to expand...
Click to collapse
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_data_public.zip (around 13 MB) which seems to contain updates for Honor system apps.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
fishnchips2 said:
Are you using the openkirin twrp?
Click to expand...
Click to collapse
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^
I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Twrp and root were lost during the update because the rom replaces them with its own files in the first boot. I don't know why the ota updates worked before.
Because you can hide root with magisk.
fishnchips2 said:
I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
Click to expand...
Click to collapse
Just to be clear, these files I mentioned in my previous post are the one downloaded by the OTA updater of EMUI (and TWRP fails on flashing the first one, update.zip) so I shouldn't flash them with TWRP, right?
I'm a bit confused about this because if ZIP files are supposed to be used with TWRP and the APP files with the stock recovery, why did the EMUI OTA updater download ZIP files (I would expect it to download files as if I had a stock recovery)?
fishnchips2 said:
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Click to expand...
Click to collapse
So these are the files flashable with TWRP (in that case I don't need the stock recovery)? The ones corresponding to the upgrade I'm looking for seem to be the following:
The OTA one seems to be exactly the same update.zip that was downloaded by the EMUI OTA updater. Should I try the FullOTA variant?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry if I sound a bit meticulous but I'd rather not brick my phone and understand what I'm doing. ^^
The error you're getting is error 7 which means the rom is supposedly incompatible with your device. As this is the official update, I have no idea why this error is coming up. I think that once you get past that error, twrp should be fine flashing the zip file.
The difference between ota files and fullota files is that a fullota contains most of the files needed by the rom while the ota only replaces files that have changed. As you are on b350 nougat already, an update to b355 should only need a normal ota update.
Don't worry about asking questions, it's good that you're cautious with your phone.?
---------- Post added at 09:52 PM ---------- Previous post was at 09:45 PM ----------
EDIT!!!
Sorry I was wrong in the previous reply. Twrp can't flash an ota update because it only replaces some files, whereas twrp will flash the entire system. However, a fullota file should work (haven't tried??).
This also explains why it had error 7: the manufacturer doesn't want someone accidentally flashing an incremental update as a full rom.
More info is here : https://twrp.me/faq/officialota.html
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
Further edit : I believe that you have to wipe certain partitions (system and cache?) before flashing an update because 'dirty flashing' doesn't always fully replace everything and causes issues later. However this may be different for stock roms. Nevertheless, always make a backup!
Hopefully final edit: a dirty flash means that you don't wipe data first. This should be fine for an official update. Opinions vary on wiping system, cache and dalvik but I think the recovery should do that for you.
Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.
PalakMi said:
Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.
Click to expand...
Click to collapse
Yup I believe so
Honor devices are one of the most complicated when it comes to flashing ROMs.
I know ? at least it isn't the s8 exynos version. I hear you can't even unlock the bootloader on that.
Yeah, however, I wish honor makes it simple with upcoming devices (like OnePlus)
sclarckone said:
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^
Click to expand...
Click to collapse
Use Huawei update extractor,and you should find a recovery.img
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some users like to keep their phones running the most official and stock system. Sadly, current Superuser installation process is a little bit more complicated then it was in the past (f.g. su binary needs to be running as a daemon). Flashing official SuperSu package makes OTA updates for the particular device impossible to be installed, because every OTA package during the installation process checks the integrity (with SHA-1) of each file on the system partition. Current SuperUser packages are modifying at least one file on the system partition: system/etc/install_recovery.sh. With that modified file, OTA installation will fail and you won't be able to update your device with the latest software. Additionally, SuperUser access is not always enough. It's good to have adb secure disabled and this can be done in the ramdisk inside boot.img.
Device rooted with the above method should have no problems installing latest official OTA update because:
a) OTA update checks for files integrity, but it doesn't check if any extra files were added to the system partition
b) OTA update doesn't check the integrity of the boot.img, so you can even flash a custom kernel if you want
Keep in mind that once you change or remove any file from the system partition you won't be able to receive OTA updates. You can only add new files, but you can't modify/remove existing ones.
Details:
boot.img source: 4.16.401.10
Target device: HTC One M8 (0P6B10000)
Target device OS version: 4.16.401.10
Included in the package:
Latest SuperSu app (Superuser.apk) and binaries (su, daemonsu)
Proper init.d script to run daemonsu binary as a daemon
Special wp_mod.ko kernel module to disable HTC system RW protection
Proper init.d script to insert the wp_mod.ko module into the kernel
Busybox
Sysrw/sysro binaries
Custom boot image:
Disabled ro.adb.secure and ro.secure
Disabled USB debugging icon on statusbar
Enabled USB debugging by default
Init.d support
Removed trigger command to execute install_recovery.sh to prevent stock recovery from being re-installed after each system reboot
Installation guide (bootloader has to be unlocked)
Extract the downloaded .rar package (boot.img, stock_recovery.img, Root_and_BusyBox.zip and Read_Me.txt)
Flash custom recovery of your choice
Flash boot.img using fastboot flash boot boot.img command in the fastboot mode
Flash Root_and_BusyBox.zip package in the custom recovery
Flash stock_recovery.img using fastboot flash recovery stock_recovery.img command in the fastboot mode
Reboot the device
Credits:
Chainfire for the SuperSu
flar2 for the wp_mod.ko module
XDA:DevDB Information
[GUIDE] How to add root access & and keep official OTA updates | 4.16.401.10, Tool/Utility for the HTC One (M8)
Contributors
mike1986.
Version Information
Status: Stable
Created 2014-05-18
Last Updated 2015-02-28
Cheers for this Mike but which file is it in your downloads section?
Cheers Mike, Informative as always!
lasikie said:
Cheers for this Mike but which file is it in your downloads section?
Click to expand...
Click to collapse
Will be there very soon!
Uploaded http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I was under the impression this would be an all in one tool but looks like I still need to do a few things in preparation of this.
I am currently completely stock. What are the exact steps I should take to install this?
lasikie said:
I was under the impression this would be an all in one tool but looks like I still need to do a few things in preparation of this.
I am currently completely stock. What are the exact steps I should take to install this?
Click to expand...
Click to collapse
Could this be any simpler?
Installation guide (bootloader needs to be relocked)
Extract downloaded .rar package
Flash boot.img using fastboot flash boot boot.img command in the fastboot mode
Flash Android_Revolution_HD_Root_and_BusyBox.zip package in the custom recovery of your choice
Reboot the device
Installation guide (bootloader needs to be relocked) - How do I do this?
Extract downloaded .rar package
Flash boot.img using fastboot flash boot boot.img command in the fastboot mode - How do I access Fastboot mode?
Flash Android_Revolution_HD_Root_and_BusyBox.zip package in the custom recovery of your choice - When do I install this custom recovery?
Reboot the device
I'm not trying to be awkward just not use to some of this terminology and don't want to ruin my phone.
Maybe an idiots guide is what I need.
lasikie said:
Installation guide (bootloader needs to be relocked) - How do I do this?
Extract downloaded .rar package
Flash boot.img using fastboot flash boot boot.img command in the fastboot mode - How do I access Fastboot mode?
Flash Android_Revolution_HD_Root_and_BusyBox.zip package in the custom recovery of your choice - When do I install this custom recovery?
Reboot the device
I'm not trying to be awkward just not use to some of this terminology and don't want to ruin my phone.
Maybe an idiots guide is what I need.
Click to expand...
Click to collapse
http://www.htcdev.com/bootloader
Also typo in my guide, bootloader needs to be unlocked. Correcting now.
Just a question, I remember that when i rooted my m7 or my one x, i had to reinstall all apps, and contacts were lost.. with this process does the info also is erase?
jorzavfa said:
Just a question, I remember that when i rooted my m7 or my one x, i had to reinstall all apps, and contacts were lost.. with this process does the info also is erase?
Click to expand...
Click to collapse
Unlocking the bootloader will remove all your data. If you have bootloader already unlocked, no data will be lost.
mike1986. said:
Unlocking the bootloader will remove all your data. If you have bootloader already unlocked, no data will be lost.
Click to expand...
Click to collapse
Ok great yes thats true, well im not sure i just bought the phone and i havent touch it for anything, i will check if the bootloader is unlocked, which i think no ..
jorzavfa said:
Ok great yes thats true, well im not sure i just bought the phone and i havent touch it for anything, i will check if the bootloader is unlocked, which i think no ..
Click to expand...
Click to collapse
If it's a brand new device then it has locked bootloader.
If I already have rooted M8 and s-off ,supercid, but with another method is safe to flash boot.img and Android_Revolution_HD_Root_and_BusyBox.zip package? will assume can install OTA after?
4onu said:
If I already have rooted M8 and s-off ,supercid, but with another method is safe to flash boot.img and Android_Revolution_HD_Root_and_BusyBox.zip package? will assume can install OTA after?
Click to expand...
Click to collapse
Yes it's safe but I can't guaranty that the previous method you used won't prevent your device from installing official OTA update.
I rooted my phone using thod: https://www.youtube.com/watch?v=WuHFcGvUjwA and s-off using this method: https://www.youtube.com/watch?v=--Hlms1BuPg
If I do everything that is in this topicfrom you, will I be able to update through OTA? And do you maybe know when int. version will get the 1.54.401.9 update? I would like to do an ota and then flash latest arhd when it will be available...
CrazyCypher said:
I rooted my phone using thod: https://www.youtube.com/watch?v=WuHFcGvUjwA and s-off using this method: https://www.youtube.com/watch?v=--Hlms1BuPg
If I do everything that is in this topicfrom you, will I be able to update through OTA? And do you maybe know when int. version will get the 1.54.401.9 update? I would like to do an ota and then flash latest arhd when it will be available...
Click to expand...
Click to collapse
Yes, you will be able to receive OTA. I'm now doing a little update to the first post.
1.54.401.9 or newer will be soon available, also next ARHD will be based on it.
mike1986. said:
Yes, you will be able to receive OTA. I'm now doing a little update to the first post.
1.54.401.9 or newer will be soon available, also next ARHD will be based on it.
Click to expand...
Click to collapse
I have a brand new HTC ONE M8, which is unlocked only. I didn't do any rooting yet
the details of the firmware are below:
HTC ONE M8 version 1.54.401.5
CID HTC_001
Can i flash the philz recovery then and do all your steps afterwards using the rooting_tools_htc rar file?
thanks
mike1986. said:
Yes, you will be able to receive OTA. I'm now doing a little update to the first post.
1.54.401.9 or newer will be soon available, also next ARHD will be based on it.
Click to expand...
Click to collapse
Thx for the quick answer... Also, the OTA will update everything, including firmware and everything right?
So after that I can easily flash the new version of ARHD without separately flashing new firmware, radio, etc?
krihoum said:
I have a brand new HTC ONE M8, which is unlocked only. I didn't do any rooting yet
the details of the firmware are below:
HTC ONE M8 version 1.54.401.5
CID HTC_001
Can i flash the philz recovery then and do all your steps afterwards using the rooting_tools_htc rar file?
thanks
Click to expand...
Click to collapse
yep
this for htc one m7 s-on international, dont know may be others too
first download odexed zip frome here >>> http://stockroms.net/file/HTCOne/rooted/4.4Sense/One_4.06.1540.2_odexed.zip
Then copy to phone to install it
You must have custum recovery twrp or clockworkmod
after you installed odexed zip Rom, in twrp will ask u install supersu to root selct dont install
and then flash stock recovery to phone in cmd fastboot on pc,and now u can update ota
i just want help those who cant update ota ,
ahmed blue said:
this for htc one m7 s-on international, dont know may be others too
first download odexed zip frome here >>> http://stockroms.net/file/HTCOne/rooted/4.4Sense/One_4.06.1540.2_odexed.zip
Then copy to phone to install it
You must have custum recovery twrp or clockworkmod
after you installed odexed zip Rom, in twrp will ask u install supersu to root selct dont install
and then flash stock recovery to phone in cmd fastboot on pc,and now u can update ota
i just want help those who cant update ota ,
Click to expand...
Click to collapse
set_metadata recursive: some changes failed
E: Error executing updater binary in zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Error flashing zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Downloaded and followed all your instructions, tried to flash using TWRP as I am having problems installing OTA on my rooted stock rom but debloated.
Any further assistance would be greatly appreciated.
Big Bread said:
set_metadata recursive: some changes failed
E: Error executing updater binary in zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Error flashing zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Downloaded and followed all your instructions, tried to flash using TWRP as I am having problems installing OTA on my rooted stock rom but debloated.
Any further assistance would be greatly appreciated.
Click to expand...
Click to collapse
Read this info on OTA: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
Big Bread said:
set_metadata recursive: some changes failed
E: Error executing updater binary in zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Error flashing zip '/sdcard/data/one_4. 06. 1540. 2_odexed.zip'
Downloaded and followed all your instructions, tried to flash using TWRP as I am having problems installing OTA on my rooted stock rom but debloated.
Any further assistance would be greatly appreciated.
Click to expand...
Click to collapse
try removing all the spaces from the file name .. or just rename it rom.zip
majmoz said:
Read this info on OTA: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
Click to expand...
Click to collapse
The modifications I made are mostly for battery and performance purposes:
- Disable services app to disable 73 google play store services. 3 google play services services, 6 google services framework services
- System tuner to disable some google play services receivers
- Team seven kernel to downclock cpu and gpu, hotplug e.t.c. (I have used a stock kernel reset to reset back to stock)
- TWRP (Flashed stock recovery)
- Disabled some bloatware crap preinstalled including htc weibo, google play newsstand, books, e.t.c. (Didn't delete them on titanium backup)
- Rooted (SuperSU not sure if it modified any system files)
- Unlocked bootloader
- S-On
Perhaps also some other things I have missed.
Is there anything else that might be interferring with my OTA update?
---------- Post added at 01:45 PM ---------- Previous post was at 01:02 PM ----------
clsA said:
try removing all the spaces from the file name .. or just rename it rom.zip
Click to expand...
Click to collapse
Renamed it to rom and i'm still receiving the same error notification.
Big Bread said:
The modifications I made are mostly for battery and performance purposes:
- Disable services app to disable 73 google play store services. 3 google play services services, 6 google services framework services
- System tuner to disable some google play services receivers
- Team seven kernel to downclock cpu and gpu, hotplug e.t.c. (I have used a stock kernel reset to reset back to stock)
- TWRP (Flashed stock recovery)
- Disabled some bloatware crap preinstalled including htc weibo, google play newsstand, books, e.t.c. (Didn't delete them on titanium backup)
- Rooted (SuperSU not sure if it modified any system files)
- Unlocked bootloader
- S-On
Perhaps also some other things I have missed.
Is there anything else that might be interferring with my OTA update?
---------- Post added at 01:45 PM ---------- Previous post was at 01:02 PM ----------
Renamed it to rom and i'm still receiving the same error notification.
Click to expand...
Click to collapse
just unlocking the bootloader alone will stop any OTA updates
post your fastboot getvar all so i can find the stock rom you need
also how old is you version of TWRP and adb / fastboot, if your using old versions you can have problems
clsA said:
just unlocking the bootloader alone will stop any OTA updates
post your fastboot getvar all so i can find the stock rom you need
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used TWRP 2.8.1.0 (I think this is the latest). Not sure how can how old the adb/fastboot is, how can i check?
Big Bread said:
I used TWRP 2.8.1.0 (I think this is the latest). Not sure how can how old the adb/fastboot is, how can i check?
Click to expand...
Click to collapse
Flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and push this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
adb push One_6.09.401.5_odexed.zip /sdcard
install that and you should be up and running
in the meantime you need 6.09.709.5 HTC__621 Nanadroid and stock recovery to return to stock for OTA updates
This is all i found for your phone
http://translate.google.com/transla...2014/10/sai-onem7v30-6097095.html&prev=search
clsA said:
Flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and push this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
adb push One_6.09.401.5_odexed.zip /sdcard
install that and you should be up and running
in the meantime you need 6.09.709.5 HTC__621 Nanadroid and stock recovery to return to stock for OTA updates
This is all i found for your phone
http://translate.google.com/transla...2014/10/sai-onem7v30-6097095.html&prev=search
Click to expand...
Click to collapse
Do you mean a current nandroid backup of the my current system or a fresh stock unmodified nandroid backup for my software number?
Big Bread said:
Do you mean a current nandroid backup of the my current system or a fresh stock unmodified nandroid backup for my software number?
Click to expand...
Click to collapse
yes that one ... unlocking the bootloader deletes the pirv-app folder you need those back
clsA said:
yes that one ... unlocking the bootloader deletes the pirv-app folder you need those back
Click to expand...
Click to collapse
Thank you for the help thus far, I initially tried to search for the nandroid backup yesterday for HTC__621 and couldn't find a specific one. Do you know of any other nandroid backup that could also work for the HTC__621 CID version?
Big Bread said:
Thank you for the help thus far, I initially tried to search for the nandroid backup yesterday for HTC__621 and couldn't find a specific one. Do you know of any other nandroid backup that could also work for the HTC__621 CID version?
Click to expand...
Click to collapse
No but you should try the Stock odex rom I posted above. It may work out fine
clsA said:
No but you should try the Stock odex rom I posted above. It may work out fine
Click to expand...
Click to collapse
Downloaded, pushed, flashed, success!
Reinstalled all those crapware apps i disabled/deleted, reinstalled stock kernel, seems to have reverted my root access somehow, but maintained my data, installed apps e.t.c.
So far, so good except the previous pending OTA notification is now saying there is no update available to be installed.
Thanks a lot for the help, much appreciated. Do you know if I will be receiving my OTA back anytime soon? lol
Big Bread said:
Downloaded, pushed, flashed, success!
Reinstalled all those crapware apps i disabled/deleted, reinstalled stock kernel, seems to have reverted my root access somehow, but maintained my data, installed apps e.t.c.
So far, so good except the previous pending OTA notification is now saying there is no update available to be installed.
Thanks a lot for the help, much appreciated. Do you know if I will be receiving my OTA back anytime soon? lol
Click to expand...
Click to collapse
hopefully your fully up to date .. only time will tell if the next OTA will work or not
clsA said:
hopefully your fully up to date .. only time will tell if the next OTA will work or not
Click to expand...
Click to collapse
When i reboot into TWRP it provides me with the opportunity to install root by installing SuperSU, would doing so affect any possibilities of installing future OTAs?
Big Bread said:
When i reboot into TWRP it provides me with the opportunity to install root by installing SuperSU, would doing so affect any possibilities of installing future OTAs?
Click to expand...
Click to collapse
Root is no problem ..TWRP is
clsA said:
Root is no problem ..TWRP is
Click to expand...
Click to collapse
Another question, I already have the OTA downloaded on my phone prior to flashing the odexed ROM. Would it be possible for me to apply the update via adb sideload? Would this be feasible regardless of the unlocked bootloader with stock rom, stock kernel and stock recovery?
Big Bread said:
Another question, I already have the OTA downloaded on my phone prior to flashing the odexed ROM. Would it be possible for me to apply the update via adb sideload? Would this be feasible regardless of the unlocked bootloader with stock rom, stock kernel and stock recovery?
Click to expand...
Click to collapse
what update ? isn't 6.09.709.5 the last version ?
but yes with s-off you can manually flash OTA.zip with a totally stock system
clsA said:
what update ? isn't 6.09.709.5 the last version ?
but yes with s-off you can manually flash OTA.zip with a totally stock system
Click to expand...
Click to collapse
My HTC One was purchase from taiwan, the latest update is 6.09.709.7, I was running 6.09.709.5 before. now with this odexed rom, it seems I have been downgraded to 6.09.401.5.
I have tried to S-OFF but my HBOOT is 1.57 and so only the firewater method could work for me, I also discovered that the firewater method won't work because my eMMC begins with 4501xxx so therefore, I'm in a position where I can't install updates or S-OFF to revert completely to stock.
Big Bread said:
My HTC One was purchase from taiwan, the latest update is 6.09.709.7, I was running 6.09.709.5 before. now with this odexed rom, it seems I have been downgraded to 6.09.401.5.
I have tried to S-OFF but my HBOOT is 1.57 and so only the firewater method could work for me, I also discovered that the firewater method won't work because my eMMC begins with 4501xxx so therefore, I'm in a position where I can't install updates or S-OFF to revert completely to stock.
Click to expand...
Click to collapse
I thought you were using this file - SAI-OneM7_v3.0 | 6.09.709.5
http://translate.google.com/transla...2014/10/sai-onem7v30-6097095.html&prev=search
it's no big deal you can flash roms your fine ...getting OTA is not everything
The OTA has just come. I have rooted phone with twrp recovery installed.
What to do now?
As I have read the forum, I should from http://forum.xda-developers.com/ascend-p7/development/recovery-t2811965 install back “Huawei Ascend P7-L10 thanks to XQC”, and that is it?
The phone will be unrooted, so I have to root it again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there anything else?
=kriticar;59281321
Is there anything else?
Click to expand...
Click to collapse
Yes,on B.609 twrp doesn't work,you must use chinese cwm translated to english and you will have not full root with stock kernel unless you flash via adb custom kernel.
gregysk said:
Yes,on B.609 twrp doesn't work,you must use chinese cwm translated to english and you will have not full root with stock kernel unless you flash via adb custom kernel.
Click to expand...
Click to collapse
For now I would like to try stock rom.
The zip file (* Huawei Ascend P7-L10 thanks to XQC) on [RECOVERY][ Unofficially Open Recovery TWRP 2.8.1.0 ][ 09/11/2014 ] thread consists of two recoveries: recovery.img and recovery2.img.
I believe that I should flash recovery.img, shuldn't I?
After flasnih recovery I will just start the update.
Regards,
Zoran
kriticar said:
I believe that I should flash recovery.img, shuldn't I?
After flasnih recovery I will just start the update.
Regards,
Zoran
Click to expand...
Click to collapse
1.Yes,flash (stock)recovery.img
2.Tap download and install and let the phone do the upgrade
gregysk said:
1.Yes,flash recovery.img
2.Tap download and install and let the phone do the upgrade
Click to expand...
Click to collapse
OK, thanks. I will do the procedure now.
Regards, and thanks again.
Well, the update has failed.
I am informed to go to the http://www.emui.com/motiondownload.php?mod=restore which doesn't work.
I was able to shutdown the phone and to reboot it again.
Apon booting the phone I got the message that update has failed and by clicking on it I went to the update screen.
Looks like huawei is checking wheather the phone is rooted or something else.
What to do now?
Install stock recovery and then update through OTA. You cannot use OTA with custom recovery.
You didnt read update notes ("make sure your phone has not been rooted...").
Ne citas upute zemo
ibeqa said:
Install stock recovery and then update through OTA. You cannot use OTA with custom recovery.
Click to expand...
Click to collapse
I have installed stock recovery in the following way:
1. I have downloaded a zip file (* Huawei Ascend P7-L10 thanks to XQC) from [RECOVERY][ Unofficially Open Recovery TWRP 2.8.1.0 ][ 09/11/2014 ] thread
2. I have unpacked recovery.img from zip file
3. As a root, I have used adb reboot bootloader, fastboot flash recovery recovery.img, fastboot reboot
4. Now I have downloaded and started the update
I believe that this is enough.
Do I have to unroot the phone before update?
Is the stock recovery from the twrp thread OK for this update?
gregysk said:
You didnt read update notes ("make sure your phone has not been rooted...").
Ne citas upute zemo
Click to expand...
Click to collapse
How to unroot the phone?
kriticar said:
How to unroot the phone?
Click to expand...
Click to collapse
Try with RootGenius,unroot option.
I have, but the update is still failing.
Does someone know what update procedure checks before upgrade?
kriticar said:
I have, but the update is still failing.
Does someone know what update procedure checks before upgrade?
Click to expand...
Click to collapse
check this http://forum.xda-developers.com/ascend-p7/help/unable-to-downgrade-ascend-p7-l10-b609-t3050761
for this guy it worked (you don't need to downgrade to 2.3 if you don't want)
ibeqa said:
check this http://forum.xda-developers.com/ascend-p7/help/unable-to-downgrade-ascend-p7-l10-b609-t3050761
for this guy it worked (you don't need to downgrade to 2.3 if you don't want)
Click to expand...
Click to collapse
Well, I am still on 2.3, but I cannot go up.
After starting the update, the phone boots to the recovery, than:
finding update package
opening update package
verifying update package
instaling update
huawei factory resizing
update failed please try again
I have option to shutdown the phone and that is basically it.
kriticar said:
Well, I am still on 2.3, but I cannot go up.
After starting the update, the phone boots to the recovery, than:
finding update package
opening update package
verifying update package
instaling update
huawei factory resizing
update failed please try again
I have option to shutdown the phone and that is basically it.
Click to expand...
Click to collapse
man tell me what recovery you have currently on ?
How to check that?
Download full ROM 609 and copy dload folder to SD card. Start install process by holding vol+ vol- and power button at the same time
Sent from my novo9-Spark using Tapatalk
I cannot install official download in that way.
kriticar said:
I cannot install official download in that way.
Click to expand...
Click to collapse
Let's go in this step by step!
1. Confirm which recovery you have installed, 2.3 or 3.0. If you did not flash official Emui 3.0 than you need emui 2.3 official recovery. Official recovery you can extract from official Emui 2.3 ROMs (you will need 2.3 ROM also for flashing).
2. Flash the needed recovery (if needed).
3. After downloading official 2.3 ROM, open it and check if there is a folder "dload". On that folder should be a file "update.app". Copy the folder "dload" together with it's content on the root of your SD card.
4. Go to settings -> update -> local update and start update (local update) , if local update does not work than try force update.
5. Confirm on the forum
How to confirm recovery version?
<3e>?
I want to unlock my bootloader and try a custom ROM, but I don't want to get stuck without a camera. I remember reading somewhere that XperiFIX would need to be updated for the most recent patch to be compatible.
Anyone tried it?
Pickx said:
I want to unlock my bootloader and try a custom ROM, but I don't want to get stuck without a camera. I remember reading somewhere that XperiFIX would need to be updated for the most recent patch to be compatible.
Anyone tried it?
Click to expand...
Click to collapse
Have you thought of asking in the Xperiafix thread ?
Didgesteve said:
Have you thought of asking in the Xperiafix thread ?
Click to expand...
Click to collapse
No, because nobody in that thread has answered that question for the March update either.
Pickx said:
No, because nobody in that thread has answered that question for the March update either.
Click to expand...
Click to collapse
Well if no one has answered then it's probably a no then
I patched XperiFix myself to use it with the .119 FW and it works.
Currently i'm running FW .119 with XperiFix DRM-patch and TWRP from 05.03.18.
I haven't installed the .145 FW atm, because I couldn't boot into Android with TWRP from 05.03.18.
But I read that TWRP came out for the april patch, so I will try to update at the weekend and check again with XperiFix.
Proof FW .119:
Phone Settings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone Security Settings:
XperiFix:
Edit - After Upgrade .145:
I used the April TWRP and I could boot into Android and TWRP.
Phone Settings:
XperiFix:
Thank you very much! So what is the process like to do this with an "unsupported" firmware? How do I patch this for .145, or do I even need to do anything special other than using a newer version of TWRP?
Raz0Rfail said:
I patched XperiFix myself to use it with the .119 FW and it works.
Currently i'm running FW .119 with XperiFix DRM-patch and TWRP from 05.03.18.
[...]
Click to expand...
Click to collapse
Thank you very much! So what is the process like to do this with an "unsupported" firmware? How do I patch this for .145, or do I even need to do anything special other than using a newer version of TWRP?
Raz0Rfail said:
Edit - After Upgrade .145:
I used the April TWRP and I could boot into Android and TWRP.
Click to expand...
Click to collapse
Is upgrading the XperiFix just as simple as replacing the TWRP in the XperiFix folder with the most recent one? If not, what else is required? If so, what do I do with the xz1c-twrptemp.img file? I'm assuming I rename the downloaded TWRP file to xz1c-twrp.img.
It's mentioned at https://www.xperifix.com/2018/03/06/update-2-2-xz1-and-xz1-compact-update/#comment-40 that a guide for this will be released but I haven't found it yet, and given that it looks above like you've already done this I'd be most appreciative if you'd share the process. Thanks!
nataelj said:
Is upgrading the XperiFix just as simple as replacing the TWRP in the XperiFix folder with the most recent one? If not, what else is required? If so, what do I do with the xz1c-twrptemp.img file? I'm assuming I rename the downloaded TWRP file to xz1c-twrp.img.
It's mentioned at https://www.xperifix.com/2018/03/06/update-2-2-xz1-and-xz1-compact-update/#comment-40 that a guide for this will be released but I haven't found it yet, and given that it looks above like you've already done this I'd be most appreciative if you'd share the process. Thanks!
Click to expand...
Click to collapse
I wrote you a pm to modify xperifix.
You need only the current kernel for the fw installed. It comes with flashing firmware.
The temp TWRP inside the data folder is only get booted from the XperiFix tool.
The XperiFix tool boot this temp TWRP to change the libs, install magisk and so on.
If you change the TWRP temp through another TWRP image, all commands to flash magisk etc. Won't work, so for the work is the temp TWRP required.
Important is that you use the correct kernel before you use xperifix, because this kernel get flashed and TWRP temp got booted as recovery, so nothing changes what you have currently installed as boot or recovery image.
So the second TWRP I let It as it be. After flashing the XperiFix files and the phone restart correctly, I boot into bootloader and flash the new TWRP recovery and then I reboot into TWRP to check if all files shown in /sdcard are correctly named. If the names are correct, you use the right TWRP to the installed security patch from Google. If you have only cryptic names inside /sdcard you have the wrong TWRP to the installed security patch. If it's so that the wrong TWRP is installed download the correct one and flash the recovery again.
Edit: sorry I forget I wrote am pm to pickxx.
I send it to you too.
I can't post it here, because it's not save and if the owner find out, he would fix it, that patching is not possible.
Raz0Rfail said:
I wrote you a pm to modify xperifix.
I can't post it here, because it's not save and if the owner find out, he would fix it, that patching is not possible.
Click to expand...
Click to collapse
I still haven't gotten a PM.
Also, the link I posted above was one to the creator of Xperifix (@sToRm// (Heiko Frenzel) on this forum) mentioning that he was going to publish a guide on how to do this update on the XperiFIX website, so I think you'd probably be fine to publish that yourself. Far from causing him to fix it, I think you'd just save him some work. If anyone knows otherwise please feel free to correct me.
Finally, the above discussion is helpful in clarifying what to do (or not to do) with the temp, but I'm still not sure what I need to replace or update in the XperiFIX to enable it to work on the most recent firmware.
nataelj said:
I still haven't gotten a PM.
Also, the link I posted above was one to the creator of Xperifix (@sToRm// (Heiko Frenzel) on this forum) mentioning that he was going to publish a guide on how to do this update on the XperiFIX website, so I think you'd probably be fine to publish that yourself. Far from causing him to fix it, I think you'd just save him some work. If anyone knows otherwise please feel free to correct me.
Finally, the above discussion is helpful in clarifying what to do (or not to do) with the temp, but I'm still not sure what I need to replace or update in the XperiFIX to enable it to work on the most recent firmware.
Click to expand...
Click to collapse
I couldn't share the PM, because my PM settings wasn't configured to save it in send mails.
I will write a Tutorial after my work 19:00 (UTC +1), how to patch XperiFix.exe to use it with the new firmwares. I won't share my patched .exe files. If you want it, you have to follow the tut.
You should leave the files in XperiFix folder as it currently is.
You only need TWRP for current Security Patch if you want to change files inside /sdcard, flash files from /sdcard, or create a working Nandroid Backup.
Raz0Rfail said:
I couldn't share the PM, because my PM settings wasn't configured to save it in send mails.
I will write a Tutorial after my work 19:00 (UTC +1), how to patch XperiFix.exe to use it with the new firmwares. I won't share my patched .exe files. If you want it, you have to follow the tut.
You should leave the files in XperiFix folder as it currently is.
You only need TWRP for current Security Patch if you want to change files inside /sdcard, flash files from /sdcard, or create a working Nandroid Backup.
Click to expand...
Click to collapse
Cool; will look forward to the details!
To be clear though, I have an unpatched, unrooted device that's on the most recent firmware. I'm not just updating to access the sdcard and create backups, I'm updating to crack the phone in the first place (without having to do a downgrade, which I haven't worked out the full process for yet). Not sure if that changes anything or not but figured I'd mention in case.
I had .34 firmware, used Xperifix, than upgraded to .119 and indeed it stopped working.
This is a Tutorial about patching XperiFix from Storm// to use it with new Firmwares.
It's not officially provided or allowed by him!
At first I have to be clear at the following points:
The Patch has the same requirements as XperiFix itself (without the old firmwares)
Your Device must have a unlocked bootloader.
With unlocking your bootloader, you will loose your DRM Keys for this phone forever!
The XperiFix is only simulating DRM-Keys, so the camera and other things can be used again.
You should have installed the correct drivers for bootloader and USB-Debugging
Get Software
Download and install XperiFix first on your PC:
https://www.xperifix.com/download/xperifix-latest/ Version2.2
For patching XperiFix download DnSpy on Github(https://github.com/0xd4d/dnSpy/releases/tag/v4.5.3)
Get TWRP for your FW: https://androidfilehost.com/?w=files&flid=232371 (current for .145 FW is twrp-3.2.1-0-lilac-10-patchlevel-2018-04-05.img)
Get and install Firmware
At first you need the Current firmware on your Device.
I use FlashTool to download and flash the Firmware: http://www.flashtool.net/downloads.php
Download new XZ1c-Firmware trough XperiFirm inside FlashTool.
After the download close XperiFirm to create the new FTF-file from FlashTool automaticly.
In FlashTool click Flash --> Flashmode --> Select new Firmware (don't change anything at wiping or excluding), execute the flash.
After flash reboot phone into system, it needs time just wait!
If reboot is from Android needed to finish upgrade, let the phone do it.
Patch XperiFix
Extract DnSpy from zip-file.
open DnSpy.exe, Open XperiFix.exe under File --> Open (C:\XperiFix\XperiFix.exe).
In "Assembly Explorer" switch to XperiFix (2.2.0.0) --> XperiFix.exe--> (XperiFix (Yellow Color) --> Form1 in tree structure.
Right Click on public Form1(), "edit Method".
In the new Window, you are able to change the source code.
replace the following variable
this.validfw = new List<string>
{
"47.1.A.8.49",
"47.1.A.12.34",
"47.1.A.12.75"
};
with
this.validfw = new List<string>
{
"47.1.A.8.49",
"47.1.A.12.34",
"47.1.A.12.75",
"47.1.A.12.119",
"47.1.A.12.145"
};
Click on the Button compile. You will see the changes in the main Window from DnSpy.
Click on File -> Save Module --> enter name, save the .exe-file.
Start the patched XperiFix.exe
reboot phone into Bootloader and connect it to your pc, because there XperiFIX can detect it without crashing.
If everything was correct patched with DnSpy you should be allowed to use it.
Set the hook and click on "FIX my Device!" then let XperiFIX do it's work.
if you see magisk and XperiFIX get flashed inside twrp everything is fine.
if the phone restarts into system, reboot phone into bootloader to flash your twrp recovery.
Flash Recovery
reboot phone into Bootloader and connect it to your pc.
"Path to fastboot\fastboot.exe" flash recovery "Path-to-Twrp\twrp-3.2.1-0-lilac-10-patchlevel-2018-04-05.img"
"Path to fastboot\fastboot.exe" reboot
Phone should start into android, first time needs time because it has wiped dalvic and cache.
In Android take a photo and check album if there is a green picture or not (shouldn't be).
You can start telephone APP call *#*#SERVICE#*#* or *#*#7378423#*#* and inside the Service Menu switch to "service tests" and there to Security.
Should be near identically to mine, some Thread entries before.
You have now the new Firmware and XperiFIX installed.
Afterwards I'm using root Explorer and Titanium Backup to clean the Bloatware which come from installing the new Firmware.
If something is not clear or detailed, please write it to me.
Raz0Rfail said:
This is a Tutorial about patching XperiFix from Storm//
Click to expand...
Click to collapse
Thank you so much; that's amazing!!!
One note; you mention manually flashing the new firmware with flashtool. Is there any difference between this approach and using a device that has been updated to that firmware via OTA update from Sony?
Related to that, where does the new TWRP connect in? I see that you download it, and later you mention that it gets loaded; presumably it needs to get saved somewhere specific in XperiFIX or linked to via the dnSpy changes?
I'm concerned because it sounds like everyone else here is upgrading an already flashed system and can re-flash the new twrp from the old one. I've got a fresh OTA rom I'm patching and rooting so it doesn't yet have twrp. As XperiFIX installs TWRP I assumed I'd have to link it to the correct twrp file somehow (perhaps replace the one in the XperiFIX file structure?), but I don't see that here. Something additional required in this case?
nataelj said:
Thank you so much; that's amazing!!!
One note; you mention manually flashing the new firmware with flashtool. Is there any difference between this approach and using a device that has been updated to that firmware via OTA update from Sony?
You only need the Firmware, how you get to the Firmware is secondary. But if you unlocked your bootloader you can't install the new OTAs.
Related to that, where does the new TWRP connect in? I see that you download it, and later you mention that it gets loaded; presumably it needs to get saved somewhere specific in XperiFIX or linked to via the dnSpy changes?
The TWRP recovery is only in your phone. XperiFix pushes it's own twrp trough the process.
The XperiFix TWRP is located at C:\XperiFIX\DATA\TWRP\xz1c-twrp.img.
But if you flash your own recovery as in step 5 described, the xperiFix twrp is obselete.
I'm concerned because it sounds like everyone else here is upgrading an already flashed system and can re-flash the new twrp from the old one. I've got a fresh OTA rom I'm patching and rooting so it doesn't yet have twrp. As XperiFIX installs TWRP I assumed I'd have to link it to the correct twrp file somehow (perhaps replace the one in the XperiFIX file structure?), but I don't see that here. Something additional required in this case?
I understand your concern. You will be able to forget about the OTA updates as soon as you unlock the bootloader.
My recommendation is to wait as soon as a new firmware is out until TWRP has been adapted.
Because I had to redo my mobile 3 times because I didn't wait and couldn't flash XperiFix.
This means you need to download 2.5 GB+- for each update, patch XperiFix, and start the process from the beginning.
This is the price to use the phone with root and Magisk.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
Do you understand better now?
@Raz0Rfail everything worked. I had to wipe and install janjan's ROM because magisk wasn't working after XperiFIX, but other that your guide worked perfectly. Thanks again.
Raz0Rfail said:
Do you understand better now?
Click to expand...
Click to collapse
Seems to have failed for me. I now get green camera images and have no root; something went wrong somewhere... :-/
Try using xperifix again. Boot into bootloader, plug phone into pc, start modified xperifix, execute it again. And check if in TWRP is flashing magisk and xperifix kernel.
Did you flash recovery with fastboot flash recovery or fastboot flash boot?
If you use the second variant, it is clear that this was your mistake, because magisk and xperifix kernel is patched into the installed kernel.
Raz0Rfail said:
Try using xperifix again. Boot into bootloader, plug phone into pc, start modified xperifix, execute it again. And check if in TWRP is flashing magisk and xperifix kernel.
Did you flash recovery with fastboot flash recovery or fastboot flash boot?
If you use the second variant, it is clear that this was your mistake, because magisk and xperifix kernel is patched into the installed kernel.
Click to expand...
Click to collapse
Hmm, maybe I could use more clarification on that step then. I actually just went into TWRP and then hit install and pointed it to install the new file (copied to the phone) as a new recovery. Would that not work? If not, is the above meant to say I should use flashtool and flash that new TRWP with it?
EDIT: Hey!!! Something worked! I checked the logs and saw some failed file copies and permission errors so I played around with it some and reran as you suggested and it seems to have worked now! I'm up and running and my photos are no longer green!!
I am not seeing Magisk as an app though, and when I try and open Titanium Backup it just cycles while looking for SU and Busybox. If I get the Root Checker app it says not rooted too even though it finds an Su; does that actually mean not rooted or does Magisk work in some other way to give permission?
T-Mobile G6 H872 20E Stock Collection
Based on OEM 20e KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
These Zips were not tested (no longer own a G6). Post any problems you have in the thread
20e Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
SysBoot ROMs will only work with 20a or 20d bootloaders
FILE BREAKDOWN
The following Zips DO NOT include stock LAF or Recovery
You must flash the provided LAF separately if you wish to go back to stock DL mode.
Bootloader: 20e Stock Bootloader ONLY
FullStock: Full 20e Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
If you are already on any of my other Stock ROM's, you should be able to Dirty Flash these.
If you are asked for a passcode in TWRP or are unable to mount System, Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
If you Flashed FullStock with Magisk, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:e534a2acb66ac0596c7b0594e717cff5
FullStock ROM - d53ce39c5a76ac622d5c2bf9c3e2d839
FullStock with Magisk Installer - md5:961dd56c1c81f232a22da7494691ec0db11d9deb
StockLAF - md5:ba05b2e4d7d73016272463aef177dad3
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
Please let me know if you run into any problems with them. Thanks!
Other H872 Projects
H872 11G Stock Collection
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
H872 20D Stock Collection
For my friends
I wanted to put this out quickly, so I did not create any SysBoot ROMs for this build. As of now, I don't plan on it. However, if some of you ask nicely then maybe I'll make some time
Hope everybody is doing well. Have a great day.
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h87220e, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 20e KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-12-04
Created 2018-12-04
Last Updated 2018-12-04
Just FYI, I was not able to test these since I no longer have a G6. There are some assert checks that look at your device model and file checksums. If flash fails for anyone, please let me know.
what the difference between SysBoot ROMs and FullStock with Magisk Installer???
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
aquinoer said:
what the difference between SysBoot ROMs and FullStock with Magisk Installer???
Click to expand...
Click to collapse
lol I'm sorry if I sound dumb :silly
aquinoer said:
what the difference between SysBoot ROMs and FullStock with Magisk Installer???
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
lol I'm sorry if I sound dumb :silly
Click to expand...
Click to collapse
SysBoot only includes boot and system images, whereas FullStock includes all of the stock firmware images (bootloader, modem, boot, system)
When I make a SysBoot zip it's normally for deodexing and debloating the stock system and integrating Magisk.
I didnt make any SysBoot zips for this, but I did integrate Magisk into one of the FullStock zips so it will flash Magisk automatically after flashing the firmware.
weakNPCdotCom said:
SysBoot only includes boot and system images, whereas FullStock includes all of the stock firmware images (bootloader, modem, boot, system)
When I make a SysBoot zip it's normally for deodexing and debloating the stock system and integrating Magisk.
I didnt make any SysBoot zips for this, but I did integrate Magisk into one of the FullStock zips so it will flash Magisk automatically after flashing the firmware.
Click to expand...
Click to collapse
ok, but if I use the fullstock with magisk does that mean that I have to reflash twrp again using the runningnak3d root method?? again I'm sorry if it sounds dumb
aquinoer said:
ok, but if I use the fullstock with magisk does that mean that I have to reflash twrp again using the runningnak3d root method?? again I'm sorry if it sounds dumb
Click to expand...
Click to collapse
ahh I see what you mean. none of these packages touch your laf or recovery partitions unless you flash the stock laf zip. all that hard work will still be in tact.
just flash the zip with magisk and you're done
weakNPCdotCom said:
ahh I see what you mean. none of these packages touch your laf or recovery partitions unless you flash the stock laf zip. all that hard work will still be in tact.
just flash the zip with magisk and you're done
Click to expand...
Click to collapse
oh my god thank you I've been wait for the h8720e :laugh::laugh:
sadly it didnt work for me idk if it was the my phone or the zip files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
aquinoer said:
sadly it didn't work for me idk if it was my phone or the zip files
Click to expand...
Click to collapse
aquinoer said:
aquinoer said:
sadly it didn't work for me idk if it was my phone or the zip files
Click to expand...
Click to collapse
Interesting, I haven't flashed this latest yet myself just got done backing things up.
Is this from clean or dirty flash?
I'm running his 20d right now and was going to flash the full stock + magisk zip dirty caught this post just before doing it.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Ken C said:
aquinoer said:
Interesting, I haven't flashed this latest yet myself just got done backing things up.
Is this from clean or dirty flash?
I'm running his 20d right now and was going to flash the full stock + magisk zip dirty caught this post just before doing it.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
I did both just to see which one would work but at least I'm back to h8720D
Click to expand...
Click to collapse
I'm getting an "invalid entry size" message when I try to look in the zip file using es file explorer. It then behaves like your inside the file but I don't see anything. I haven't tried flashing yet. I have an idea what's up but don't know how it would be fixed or if I'm even correct. I haven't tried opening the zip on a pc yet.
@weakNPCdotCom
Not pushing or anything but if you could take a peek at it. Hopefully nothing major. I was looking at the message you sent me and your talk about the updater script. Maybe it's just that? I'm admittedly guessing here.
Sent from my LG-H872 using Tapatalk
Ken C said:
@weakNPCdotCom
Not pushing or anything but if you could take a peek at it. Hopefully nothing major. I was looking at the message you sent me and your talk about the updater script. Maybe it's just that? I'm admittedly guessing here.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
It sounds like the ZIP is corrupted. Might have happened during the upload. I'll check it out this morning
Either of you guys try the standard FullStock? it's the same you just have to manually flash magisk after flashing the ROM
weakNPCdotCom said:
It sounds like the ZIP is corrupted. Might have happened during the upload. I'll check it out this morning
Either of you guys try the standard FullStock? it's the same you just have to manually flash magisk after flashing the ROM
Click to expand...
Click to collapse
I haven't flashed a thing yet. I'll give it a try in a bit and get back to you. No stress man just figured I'd pass it on. Pulling down full stock now.
Update : still haven't flashed yet but straight full stock is giving me that same invalid size message. I'd give it a try but I'm fairly sure it would throw the same error.
Sent from my LG-H872 using Tapatalk
Ken C said:
I haven't flashed a thing yet. I'll give it a try in a bit and get back to you. No stress man just figured I'd pass it on. Pulling down full stock now.
Update : still haven't flashed yet but straight full stock is giving me that same invalid size message. I'd give it a try but I'm fairly sure it would throw the same error.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
So I tested the zip and it was fine, not corrupt at all. So if it was corrupted it would have been during the download.
aquinoer said:
I did both just to see which one would work but at least I'm back to h8720D
Click to expand...
Click to collapse
If you try again, can you send me the TWRP logs? There should be a button in TWRP to save the flash logs. I can't see anything wrong with the package.
you mean this????
aquinoer said:
you mean this????
Click to expand...
Click to collapse
No, that's not what i was looking for. But i was able to correct an issue in the zips and re-upload them.
However, they are gonna be pretty useless as 20f is now out and ill be working on that release now.
Ok so since we're bouncing around so much between threads. (I'm using Tapatalk and only get those first few words or the thread title) lol almost comical. Anywho... And as always no stress I'm just laughing right now. Saw lg dropped 20g for the 870. So I think we can say they've upped their game at least when it comes to security updates?
Like I said it's such a shame that there isn't some way to just add the updates. Somebody got 20f to root using the tried and true method overnight or looks like.
Just thinking out loud here. But, if we had some way to revert the device to register to the update as a valid device. (thinking all the laf & recovey stuff would need to be stock.) Would that or something in not thinking of keep it from updating? I get if it sees magisk it'll probably act up. I'm just wondering is all.
Remember multirom? So have one straight stock, one rooted, then if it's possible (I realize this is easier said than done) push the root stuff over to the straight stock using some python or some such script to remove and replace files that would be necessary to keep root but have the update also.
Totally 3am or so thinking, but just popped in my mind and couldn't help sharing the thought since we were just talking about it.
Sent from my LG-H872 using Tapatalk
@Ken C
I have some news kinda. I'm creating a utility that will build FullStock and Bootloader zips from the extracted kdz files. that will make the process much faster and if it works well I might even share it.