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.
Related
Hi,
I bought today a 701T ww, with bootloader version 10.26.1.7.
I've been able to unlock the bootloader, root the rom, and install a custom CWM (now 6.0.4.6).
I installed the custom rom CROMi-X 6.0b2
But I'm now unable to upgrade the bootloader to 10.26.1.18.
I reverted to stock 10.27.1.7 rom thanks to the nandroid backup I made prior CROM install, I've tried downloading the official update package from Asus, which is supposed to be the only way to upgrade the bootloader. I've put the UL-K00C-WW-10.26.1.18-user.zip file on the root of a MicroSD, the tablet recognized the update file, and rebooted to install it. Problem is that, after reboot, the tablet enters in the CWM with the following error :
{
"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"
}
Off course if I try "Yes - install untrusted.zip" it doesn't rework, and the tablet reboots ....
many thanks if you can help !
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
berndblb said:
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
Click to expand...
Click to collapse
Hi Berndblb, thanks for your reply.
Toggling the signature verification didn't help, I've already tried that.
I didn't miss this, but as I've never been able to upgrade the bootloader thanks to the official update, I thought that with CROMI the bootloader would be upgraded too. I noticed that was'nt the case, that's why I restored my nandroid backup to revert to the stock 10.26.1.7.
Now I'm in 10.26.1.7, and precisely want to upgrade the bootloader to be able to install CROMI with the correct bootloader. Therefore my question.
Would a "fastboot flash boot boot.img" using the boot.img file included in the official asus 10.28.1.18 package be a good idea ?
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
usoska said:
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
Click to expand...
Click to collapse
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Calp said:
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Click to expand...
Click to collapse
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
berndblb said:
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
Click to expand...
Click to collapse
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Calp said:
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Click to expand...
Click to collapse
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
berndblb said:
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
Click to expand...
Click to collapse
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Calp said:
THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
You're very welcome !
That looks correct.
Calp said:
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
WooHoo! excelent. Glad you got everything all sorted out.
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
2 days, how dare you. You should be concentrating on b4 and only b4.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
Wow, you're crazy! I really appreciate your help, mate.
For anyone else needing to do these stips, here's the download link for the stock recovery which you have to flash first: http://droidbasement.com/db-blog/?p=3210 ( i also tried a different one but only this one did work in the end)
Also, thanks a lot for the ROM, sdbags. I've been using it for a couple of hours now and it seems to work like a charm. Great work, mate!
Sent from my K00C using xda app-developers app
How can I tell which bootloader (BL) and firmware (FW) I run currently? When I hold power/volume down, the top of the screen says user BL released by "US_epad-10.26.1.7". When I boot into Android and go into settings -> about -> software, I see Build number "JSS15J.US_epad-10.26.1.18". Is the 1.18 the firmware (FW) version?
Finally, is there a way to upgrade BL/FW to ...1.18 version without using an external SD card?
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Thanks. Just to verify, you don't think doing "fastboot flash boot boot.img" will work? (using boot.img from UL-K00C-US-10.26.1.18-user.zip).
Also, by SD-card method, are you talking about the rename “WW_10_26_1_18_SDupdate” to “T4_SDUPDATE.zip" process etc.? It seems that I have the US SKU, and not sure if this would work, being that it mentions WW in the file name.
Sleeepy2 said:
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Click to expand...
Click to collapse
I am no expert but I am pretty sure that the fastboot method doesn't work as there have been several people with the wrong bootloader issue and and the only way to do it was with the official update.
I am not sure about using the WW file or not. I am in canada and I used the other file to update and that did the bootloader also. With the status your in now I am not sure if the US one will work or not. I would try the US one first and then if not go with the steps from pershoot
http://forum.xda-developers.com/showpost.php?p=52187532&postcount=87
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
MilesWilford said:
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
Click to expand...
Click to collapse
It's still there, try this link
http://droidbasement.com/asus/tf701t/stock/
Q&A for [ROM] VS980 39A Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] VS980 39A Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
NalNalas said:
Here's a fix for the LED being constantly on
1. Disable notification light
2. Reboot
done
Click to expand...
Click to collapse
That works but kills the front one too.
I flashed the rom, bootstack, and supsersu (in that order) and I get a kernel crash when booting.
"kernel panic - not syncing L2 master port error detected"
Any ideas?
zone117x said:
I flashed the rom, bootstack, and supsersu (in that order) and I get a kernel crash when booting.
"kernel panic - not syncing L2 master port error detected"
Any ideas?
Click to expand...
Click to collapse
Flash bootstack, then rom n supersu.
MicroMod777 said:
Flash bootstack, then rom n supersu.
Click to expand...
Click to collapse
Alright I did that but its been on the Verizon boot animation for over 20 minutes now. Is something still wrong?
Do I have to have anything installed that wasn't mentioned in the post?
Thanks
zone117x said:
Alright I did that but its been on the Verizon boot animation for over 20 minutes now. Is something still wrong?
Do I have to have anything installed that wasn't mentioned in the post?
Thanks
Click to expand...
Click to collapse
U full wipe?
Am I missing it or is knock code still not here? Is it in the manual ota method or neither? Any ways thanks for the Rom because grola was starting to mess up.
So, I'm on the forced OTA 39A and everything is running great, I also just rooted it using this method here http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Anyway to install TWRP onto this yet? I did a stupid thing and installed AutoRec and flashed recovery just to try it, and it worked fine. Until I rebooted out of recovery, then I got the dreaded LG Security Error. So I had to restore back to 27A and go back to 39A.
LetsHaveSomeAndroidFun said:
So, I'm on the forced OTA 39A and everything is running great, I also just rooted it using this method here http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Anyway to install TWRP onto this yet? I did a stupid thing and installed AutoRec and flashed recovery just to try it, and it worked fine. Until I rebooted out of recovery, then I got the dreaded LG Security Error. So I had to restore back to 27A and go back to 39A.
Click to expand...
Click to collapse
This is a bit of a guess, so proceed at your own risk, but could you use AutoRec to install recovery, then once in recovery, flash the 39A bootstack from this thread, which also contains a bumped TWRP? I'm thinking the patched kernel that AutoRec installs is what's breaking things
Don't do this. Doesn't work
detonation said:
This is a bit of a guess, so proceed at your own risk, but could you use AutoRec to install recovery, then once in recovery, flash the 39A bootstack from this thread, which also contains a bumped TWRP? I'm thinking the patched kernel that AutoRec installs is what's breaking things
Click to expand...
Click to collapse
Well, I just spent the last few hours re-setting up my device again, but I'll try it. Might as well, if it doesn't work I'll just re-do everything again lol. I wish I would of known that the bootstack for 39A was available, I would of tried it then but oh well. Will let you know how it goes.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
Nope, just tried it. After installing the recovery then the bootstack I restart and I get secure booting error boot certification verify and the only thing I can do is get back into recovery, so no good.
LetsHaveSomeAndroidFun said:
Well, I just spent the last few hours re-setting up my device again, but I'll try it. Might as well, if it doesn't work I'll just re-do everything again lol. I wish I would of known that the bootstack for 39A was available, I would of tried it then but oh well. Will let you know how it goes.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
Nope, just tried it. After installing the recovery then the bootstack I restart and I get secure booting error boot certification verify and the only thing I can do is get back into recovery, so no good.
Click to expand...
Click to collapse
Well thanks for being the guinea pig at least. In retrospect, AutoRec loki's your boot.img, but those bootstack zips don't include a bumped boot.img (since they are rom specific I think) so you get the security error still. I'll leave this up to the experts from now on
detonation said:
Well thanks for being the guinea pig at least. In retrospect, AutoRec loki's your boot.img, but those bootstack zips don't include a bumped boot.img (since they are rom specific I think) so you get the security error still. I'll leave this up to the experts from now on
Click to expand...
Click to collapse
You're welcome, not a problem! I see, I have all the partitions of this ROM including boot.img, maybe if I name it update.zip and flash it via TWRP I can get it to boot? I think I'll try it...It's worth a shot.
LetsHaveSomeAndroidFun said:
You're welcome, not a problem! I see, I have all the partitions of this ROM including boot.img, maybe if I name it update.zip and flash it via TWRP I can get it to boot? I think I'll try it...It's worth a shot.
Click to expand...
Click to collapse
All else fails, and you still want to be the closest to stock 39a with root and recovery, I suppose you could just wipe, flash the 27A bootstack, flash this 39A ROM, then flash the 39A bootstack (should't need to KDZ or anything assuming you're still able to get into TWRP). According to this post the differences in this rom and stock are the basically the components that we couldn't pull before root was available, but now they're availabe and in that bootstack zip - once again, no guarantees though, I think I'll try to be patient and wait for the devs to release something
detonation said:
All else fails, and you still want to be the closest to stock 39a with root and recovery, I suppose you could just wipe, flash the 27A bootstack, flash this 39A ROM, then flash the 39A bootstack (should't need to KDZ or anything assuming you're still able to get into TWRP). According to this post the differences in this rom and stock are the basically the components that we couldn't pull before root was available, but now they're availabe and in that bootstack zip - once again, no guarantees though, I think I'll try to be patient and wait for the devs to release something
Click to expand...
Click to collapse
You can't install the recovery because you need the 4.4 aboot. You can adb the the 27A aboot.img through a terminal on your pc or on your phone, then adb blastagator's recovery, and you will be able to have recovery. I'm running twrp no problems right now.
EDIT:
Need a bumped boot.img too. I was bootlooping until I applied one.
bouchigo said:
You can't install the recovery because you need the 4.4 aboot. You can adb the the 27A aboot.img through a terminal on your pc or on your phone, then adb blastagator's recovery, and you will be able to have recovery. I'm running twrp no problems right now.
EDIT:
Need a bumped boot.img too. I was bootlooping until I applied one.
Click to expand...
Click to collapse
Thanks for this.
So I need to be on rooted 39A and then adb flash aboot.img and then adb flash recovery? And any help for a bumped boot.img? I've only had my LG G2 about 2 weeks. Thank you.
bouchigo said:
You can't install the recovery because you need the 4.4 aboot. You can adb the the 27A aboot.img through a terminal on your pc or on your phone, then adb blastagator's recovery, and you will be able to have recovery. I'm running twrp no problems right now.
EDIT:
Need a bumped boot.img too. I was bootlooping until I applied one.
Click to expand...
Click to collapse
Where did you get the bumped boot.img from? Also, all the bootloader files in the resource thread are bins, not imgs, does that matter?
To get to stock rooted 39A with TWRP, it sounds like the process is:
-manually apply 39A OTA
-root using new exploit
-push 27A (or 28A) aboot
-push bumped 39A boot.img
-push TWRP
LetsHaveSomeAndroidFun said:
Thanks for this.
So I need to be on rooted 39A and then adb flash aboot.img and then adb flash recovery? And any help for a bumped boot.img? I've only had my LG G2 about 2 weeks. Thank you.
Click to expand...
Click to collapse
Yes. See below.
detonation said:
Where did you get the bumped boot.img from? Also, all the bootloader files in the resource thread are bins, not imgs, does that matter?
To get to stock rooted 39A with TWRP, it sounds like the process is:
-manually apply 39A OTA
-root using new exploit
-push 27A (or 28A) aboot
-push bumped 39A boot.img
-push TWRP
Click to expand...
Click to collapse
Yeah, either 27A or 28A (confirmed by xdabbeb) should work. I bumped the 39A boot image myself (not hard to do, the info. is readily available on how to do it).
Just change the .bin to .img.
Here is the boot image (adb push it, not a flash file): http://www.mediafire.com/download/pele8oikzesdn39/bumped_boot-image.zip
MD5Sum (of zip file): 6b1f793cdf00db3ef52d1fd08f7b3af2
MD5Sum (of boot.img itself): b4254d5aebe30ad4f1d5e924f45e9bff
bouchigo said:
Yes. See below.
Yeah, either 27A or 28A (confirmed by xdabbeb) should work. I bumped the 39A boot image myself (not hard to do, the info. is readily available on how to do it).
Just change the .bin to img.
Here is the boot image (adb push it, not a flash file): http://www.mediafire.com/download/pele8oikzesdn39/bumped_boot-image.zip
MD5Sum (of zip file): 6b1f793cdf00db3ef52d1fd08f7b3af2
MD5Sum (of boot.img itself): b4254d5aebe30ad4f1d5e924f45e9bff
Click to expand...
Click to collapse
If it's not too much trouble, could you give me some step by step instructions? I am trying to push the aboot.img but it's saying device not found, when it is etc..Thank you.
LetsHaveSomeAndroidFun said:
If it's not too much trouble, could you give me some step by step instructions? I am trying to push the aboot.img but it's saying device not found, when it is etc..Thank you.
Click to expand...
Click to collapse
Download this file; inside are the instructions that I wrote up, and links to the files on how to do it: http://www.mediafire.com/download/h7544eak22lp2c9/Install_TWRP_Recovery_on_vs980_LP_39A.zip
bouchigo said:
Download this file; inside are the instruction that I wrote up, and links to the files on how to do it: http://www.mediafire.com/download/h7544eak22lp2c9/Install_TWRP_Recovery_on_vs980_LP_39A.zip
Click to expand...
Click to collapse
Thank you so much, this worked perfectly!
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
Help me guys so i have my phone rooted via patched boot.img provided by Magisk but then decided to grab my stock boot.img to patch it again so i can update to v22.0 then i restart my device to access for fastboot and everything went blackscreen(i can't even see anything literally) luckily for me i memorize the key command to access fastboot so i flashed my stock boot.img , recovery.img and vendor.img but now my phone won't start
This thing shows up
https://imgur.com/a/fVDp06e
yes it's provably stupid to flash stock boot.img , recovery.img and vendor.img but i panic everything went all black even the BLU logo is black (no backlight phone)
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Oliie23 said:
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Click to expand...
Click to collapse
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
ineedroot69 said:
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
Click to expand...
Click to collapse
If I'm thinking correctly you won't lose data. Just dirtyflash it and it should work fine
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
{
"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"
}
ineedroot69 said:
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
Click to expand...
Click to collapse
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Oliie23 said:
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Click to expand...
Click to collapse
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
ahh it fixed now my mother won't kill me
ineedroot69 said:
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
Click to expand...
Click to collapse
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Oliie23 said:
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Click to expand...
Click to collapse
look like completely factory default the bloatware are back
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
ahaha this Magisk update v22.0 is bonker
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
Let me know how it goes, please
ineedroot69 said:
look like completely factory default the bloatware are back
Click to expand...
Click to collapse
Are your apps all gone? It's basically like clean flash, right?
Oliie23 said:
Let me know how it goes, please
Click to expand...
Click to collapse
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Sebi673 said:
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Click to expand...
Click to collapse
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Oliie23 said:
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Click to expand...
Click to collapse
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
[updatee] screens attached
Sebi673 said:
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
Click to expand...
Click to collapse
Mine won't go into TWRP from the Fastboot unfortunately. It just stays there. I've managed to get TWRP to launch from ADB but I'm not sure if I should just flash the ROM that way. Should I?
[duplicate]
Disclaimer: NOT RESPONSIBLE FOR ANY BRICKED DEVICES
YOUR DEVICE MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS TO WORK
My first tutorial, gonna keep this short and sweet
1. Go to settings > About Phone > check your version number (eg 10.5.9 for mine)
2. Go to this thread and download the global zip with the corresponding number https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
3. Use payload dumper to extract the payload.bin file in the zip (you don't have to extract the whole thing, I killed mine when I got my boot.img file)
4. Install Magisk on your device and patch the just extracted boot.img
5. Copy patched boot.img to your computer
6. Reboot into bootloader, run this command and NOTHING ELSE
fastboot boot <location of patched boot.img>
7. Now your device should be booted into a rooted state and if your wifi or cellular doesn't work, have no fear. This is only temporary and we need root for the next few steps
8. Install Partitions Backup https://www.apkmirror.com/apk/wanam/partitions-backup/partitions-backup-2-3-0-release/
9. Use that to dump boot.img from both slots to your device
10. Use Magisk to patch both boot.img files just dumped from Partitions Backup
11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!
Leave a thanks if this helped you, this is for folks like me who couldn't find a backup of their OS build on the internet and needed a temp way to root their carrier devices
I'm going to try this now. Thank you for the idea!
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
Unfortunately, I can't even get into EDL mode. So this brick might be permanent. I'm asking for help from the community here: https://forum.xda-developers.com/t/nord-n100-edl-mode-dead-gone.4341305/
bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
luridphantom said:
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
Click to expand...
Click to collapse
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
bouyakasha said:
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
Click to expand...
Click to collapse
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
bouyakasha said:
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
Click to expand...
Click to collapse
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
luridphantom said:
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
Click to expand...
Click to collapse
Oh, thank you! That makes sense. I will try to UN-Tar it
I used Zarchiver to unarchive the TAR into boot.img for both, and this all worked! Thanks so much. Awesome guide.
@onlycash You should try this!
luridphantom said:
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
Click to expand...
Click to collapse
I tried several times and it's not working for me.
Everything appears to be fine till I try to "fastboot boot patched.img".
I'm trying to do this on an Metro N100 which is on 11.0.1BE82CF
I downloaded the global: 11.0.1: OnePlusN100Oxygen_14.O.21_GLO_0210_2107241056 MD5: a895312987628f21d0232d44575d0742
I extracted the payload and dumped the boot.img
I patched it in Magisk
I successfully "fastboot boot" that patched file but then it just hangs at the at the Metro boot screen.
I waited a minute or two but it didn't move past that screen, should I have waited longer?
In any event, I could hold down the power key and reboot into the unrooted stock 11.01 without issue.
Does anyone have an idea what I'm doing wrong?
{
"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"
}
.
onlycash said:
I tried several times and it's not working for me.
Click to expand...
Click to collapse
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
thomaskmaagaard said:
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
Click to expand...
Click to collapse
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
onlycash said:
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
Click to expand...
Click to collapse
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
luridphantom said:
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
Click to expand...
Click to collapse
I posted a good deal on the TWRP thread. I can fastboot the TWRP on my phone but I can't see any files only folder tree, even with my SD card I don't see any files either with TWRP.
I should add I'm running TWRP on a Metro N100 which is both SIM and bootloader unlocked. Also I didn't flash the TWRP I only fastbooted it, could that be the problem?
I really would rather flash the zip and root that way if I could get the TWRP to work.
I'm unsure what "disable dm-verity by flashing an empty vbmeta image" means in my case. What does this do?
Again I'm truly grateful for any help, thank you.
bouyakasha said:
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
Click to expand...
Click to collapse
Just to be clear I have a Metro N100 BE2015 running 11.0.1BE82CF.
With that being said, did you only get root when you went back to 10.5.8?
Are you rooted now on 11 and if so how did you get there?
Did you brick and go back to 10 then root 10 and update to 11 and keep root? How did you patch the img file after going to 11?
Any help and info would be much appreciated.
.
@onlycash I have constructed a small/random theory with no real basis. Could your problems be related to OOS 11? It sounds as dumb to me as it probably does to you, but I'm getting a nagging sensation that folks with success on your model aren't running the new update.
Just a weird hunch with no proper research, but I find it weird that you have these "unique" problems so I'm just spitting random junk at this point.