Database Users

How I got s-off on bootloader 1.05

Those getting new warranty replacement Thunderbolts from Verizon are getting a little surprise. They are now coming pre-loaded with the 1.05 bootloader and with the exploits patch already applied. What does this mean? It means if you try to run revolutionary to root your phone or use the old fashioned way with psneuter, you will not be able to gain s-off or root.
I'm going to share with you how I was able to foil Verizon's attempt to keep us in their sandbox.
Before you get started, you'll need to make sure you have some things: HTC drivers installed, Java JDK (fastest download is on download.com), Android SDK with platform tools installed. Also, I've zipped up a package for you that includes ADB, Clockwork Recovery Mod, Revolutionary, Fastboot, etc in one zip found here: http://www.multiupload.com/MU4482GBCF and grab this rooted stock rom http://www.multiupload.com/QEBIXCUFJG .
1) Head over to HTC's new bootloader unlock website at http://www.htcdev.com/bootloader/ You'll want to register, login, install the prerequisites listed & follow the instructions. After this process you will have an unlocked bootloader, but it will still be S-On meaning you can flash custom roms, but no kernels and no radios (so pretty much worthless), but a necessary step for this guide.
2) Install Clockwork Recovery Mod via fastboot. Unzip the file you downloaded above to a folder. Open a command prompt & navigate to the folder you just unzipped, then to the adb subfolder. Make sure you don't have a PG05IMG.zip on the root of your SDcard. If you do, delete it. Now power down your phone. Once all the way off, put your phone into bootloader mode (by holding down the volume down button and the power button). Select fastboot & make sure your phone is plugged into the USB cable. Your phone should display Fastboot USB or something to that effect. Now let's make sure you're online. Go to your command prompt (you should still be in your adb subfolder) and type fastboot devices. You should see your device listed. Now type
fastboot flash recovery clockwork.img
and hit enter. You should see a message telling you it was successful. You're almost there. You now have an unlocked s-on bootloader and clockwork recovery installed.
3) Next we flash any pre-rooted early rom that does not contain a kernel or radio (can be hard to find these days) via CRM. I used a debloated rooted otherwise-stock rom 1.70.605 as linked above. Grab that if you want. Move the rom to your sd card then shut down your phone, reboot to bootloader, then select recovery. Now you'll want to flash the file you just put on your sd card via recovery. Make sure you wipe first & a battery pull afterwards can't hurt. You now have a rooted, unlocked s-on bootloader and clockwork recovery installed, but we want S-off so we can flash whatever radio or kernel we want.
4) Head to the revolutionary subfolder in the folder you unzipped. Run revolutionary and head to http://revolutionary.io to get a beta key. Follow the instructions. You now have a rooted s-off thunderbolt with Clockwork Recovery.
5) Flash your favorite radio, kernel & custom rom. You're done!
I personally recommend MR2 radio with the BAMF Son of a Bliss 1.04, which includes a custom kernel. It's a rock solid combination with functionality & eye candy, but it's up to you!
{
"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"
}
MR2 Radio: http://www.multiupload.com/PCGIPX6C0E
BAMF SOAB 1.04 download: http://www.multiupload.com/6RZUKA9AWU
Enjoy

More details added. Hope this helps

Here is another, if you don't mind getting everything erased but your sdcard. It seems alittle easier with less steps.
http://forum.xda-developers.com/showthread.php?p=20498393
[HOW-TO]Downgrade to get S-OFF after updating to latest OTA 2.11.605.9
from my ADR6400L using Tapatalk

just wanted to point out that HTCdev unlock does techincally void "all or parts of your warranty" so if you used an upgrade and have warrantly left,id advise against using their unlock until the method above had failed.
basically youve just unlocked,and installed firmware that revolutionarys exploit works on. an extremely clever idea providing you have a used,no warranty device,or just dont care about the warranty aspect.
if you have warranty,and cant simply run the ruu to get back to 2.11.605.5,id reccomend waiting,another exploit may be available soon. jcase has indicated that a root hes working on should work for mecha and not void your warranty in the process
also,dont misunderstand that im knockin your efforts. i just want folks to fully realize what using HTCdev unlock means.

TB- S-OFF
Go over to http://goo.im and download Thunderbolt tool, it will get you in and do s-off for you.
it will make you smile

boilermanAres said:
Go over to http://goo.im and download Thunderbolt tool, it will get you in and do s-off for you.
it will make you smile
Click to expand...
Click to collapse
It won't work if you're on the ICS ota update. The new hboot patched the exploit.
Sent from my ADR6400L using Tapatalk 2

disconnecktie said:
It won't work if you're on the ICS ota update. The new hboot patched the exploit.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
That answered my question. Thanks!
Sent from my ADR6400L using Tapatalk 2

I don't know what to do now

hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,

I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.

Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app

If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method

sfetaz said:
I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.
Click to expand...
Click to collapse
I hope there is program like that
Backwardsblade said:
Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think so.
I try but don't find the device
frederuco said:
If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method
Click to expand...
Click to collapse
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21

1090t said:
I hope there is program like that
I don't think so.
I try but don't find the device
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21
Click to expand...
Click to collapse
unzip first. inside another zip file.

goodintentions said:
unzip first. inside another zip file.
Click to expand...
Click to collapse
Yah, i do that

.........................

why is the only rom i can install and work is the: Android Revolution HD ?!

1090t said:
why is the only rom i can install and work is the: Android Revolution HD ?!
Click to expand...
Click to collapse
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.

1090t said:
hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,
Click to expand...
Click to collapse
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.

goodintentions said:
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.
Click to expand...
Click to collapse
it doesn't work i just wait there
{
"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 that right why to boot in to rom (from cold-boot) ?
horndroid said:
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.
Click to expand...
Click to collapse
I try many time with these the Recovery still same
even with the old version ..nothing

1090t said:
it doesn't work i just wait there
is that right why to boot in to rom (from cold-boot) ?
I try many time with these the Recovery still same
even with the old version ..nothing
Click to expand...
Click to collapse
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.

feisty_noodle said:
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.
Click to expand...
Click to collapse
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.

The op's problem is very similar to this one http://forum.xda-developers.com/showthread.php?t=1549062 which has been resolved.

goodintentions said:
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.
Click to expand...
Click to collapse
You are right, I may have misinterpreted the OP.
Still, I think the solution is the same.
When the device boots into recovery and can be cold-booted into ROM, the most likely culprit is the 'boot-recovery' flag which is set in the /misc partition. When the system sees that upon boot, it goes straight into recovery.
It should be the recovery's job to blank out that flag at some point, but CWM 5.5.0.4 (and, perhaps this recovery the OP is using) does not do this.
So, the solution is to reset it with the 'echo ...' command (or blanking out the first few bytes of /dev/block/mmcblk0p3) in shell.
My suggestion is very conservative.

I'll gave try and let u know

when i connect to the computer nothing shows up
even the Asus sync don't found it
I'll gave try on Linux

any help

[Q] flashing cwm recovery

I have flashed skrilax v8 unlocked BL with v8pubA50 recovery
I flashed it using blackthund3r ATX flashtool
My question is
1. Why I can't enter boot recovery, it's just show green robot with exclamation at its body
2. How I can flash cwm recovery since it's extension is .Img
(fyi). I use UNroot A501 with stock HC 3.2.1
Thanks
Sent from my A501 using xda app-developers app

Help help :'(

gigacats said:
Help help :'(
Click to expand...
Click to collapse
IF you are sure you have the v8 bootloader installed, you should be able to install a recovery.
You must have an ICS rom installed, or on the Ext SD card, have an ICS rom ready to flash.
If you currently have a stock ICS rom installed, then you need to be rooted, and delete the "boot recovery" file (or similar name). Or else when you boot your tab, the custom recovery gets overwritten.
You can look at Civato's Bootloader and Recovery guide for the exact name of the file.
Note that v8 bootloader and ICS recoveries, DO NOT work well with HC based roms. You must have an ICS Rom.
MD

I'm on HC 3.2.1 stock ROM and unroot
Here i give some picture
View attachment 1218773
{
"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"
}
When i choose boot recovery, that robot will go out and my tab restart after a minute.
Please guide me how to open recovery.img
Sent from my ST25i using xda app-developers app

gigacats said:
I'm on HC 3.2.1 stock ROM and unroot
Here i give some picture
View attachment 1218773
View attachment 1218774
When i choose boot recovery, that robot will go out and my tab restart after a minute.
Please guide me how to open recovery.img
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
1) the robot is the 'stock recovery.img'
2) you must be rooted before you can flash 'anything'
3) The only way to do this (on HC) is by installing a custom pre-rooted rom
4) If you want ICS your tab should update itself, you will need acer enhancement app from the market. then Settings>About Tablet>System Update
5) you can install a stock or custom ICS rom BUT you must have root to update to the patched bootloader which some of the custom roms require.
6) you cannot "open" recovery.img.

Ok, so please stop posting the same issue in other threads, or you will never get your problem solved.
Now. You say you have Skirlax_cz's V8 bootloader installed. Correct? If so, you should be able to boot into the menu system of it (vol+ and PWR). If you get the bootloader menu, good.
Now, you will need the Android SDK (google it and download and install it). After installation, go to c:\windows\program files (x86)\android\android-sdk\platform-tools. Open a command window here. (it may be installed in program files)
Boot your tablet like I described above, and at the bootloader menu, select "fastboot". The tablet should say fastboot mode.
Now, copy your recovery.img (or whatever you named it) into the platform tools folder on your PC. It has to be in the same folder as fastboot.exe
Now, make sure you have the rom you want to install on your EXT SD Card.
Next, plug in your tab to the USB (I always make sure in device manager that the tab is recognized as a fastboot device)
In the command window you opened earlier, type in the following;
fastboot flash recovery recovery.img
Remember, if your recovery image is named "public-recovery.img" for example, that is what you should type in the command above.
Once the recovery is successfully flashed, then turn tab off.
Unplug from USB
Hold PWR and Vol- untill you see the message "booting recovery kernel", then release both. You should boot into the custom recovery now. Then you can do your wipes and stuff as per the rom install instructions.
Of course, this is ONLY if you have the V8 bootloader running.
Also, I posted a better rom. Evil Alex Unleashed, so you should install this. It has problems fixed.
MD

OK MD, thanks for your guide.. now I have installed your ROM successfully, it's running very smooth. Thanks very much and sorry for double posts

gigacats said:
OK MD, thanks for your guide.. now I have installed your ROM successfully, it's running very smooth. Thanks very much and sorry for double posts
Click to expand...
Click to collapse
Wow! It worked!!!!!!!!!!!!
Damn, better than I thought.
Gotta love Skirlax_CZ and putting flashboot in the bootloader v8. Throw a thanks at him when you get the chance please. And if you used EZTerry's public recovery, please throw a thanks at him also. And anybody else who helps you. That's how it works here.
I hope you installed Evil Alex. She's much better than Alex V. Alex V is a good girl, but she need the wakelock app from the market. Evil Alex hopefully does not. After all, these are Acer leaks. AKA "beta". So we really don't know what to expect. And things "will" change in the next month, and new builds "will" be released.
Am glad you got it running.
And Dibbs, throw a thanks to him also His instructions were after all, correct (he didn't know your V8 was working).
Any issues, please put them in my rom thread.
MD

[Q] Problem with my A500

Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
{
"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"
}
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...

Vipe.teo said:
Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...
Click to expand...
Click to collapse
You need to unlock your bootloader and flash a recovery

blackthund3r said:
You need to unlock your bootloader and flash a recovery
Click to expand...
Click to collapse
Thanks for your reply, can you recommend threads to teach me how to go about doing it?
I believe Mlopik page did mention if I follow correctly, I would have already unlocked my bootloader, am I right?

First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD

Moscow Desire said:
First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD
Click to expand...
Click to collapse
Hi, thanks for coming to my aid, sorry for PM-ing U asking for help.... but I'm a super noob for this....:silly:
1) I have a boot screen by Skrilax_cz, but how do I fastboot a CWM recovery via a command prompt window?
2) A few min ago, I tried to use AfterOTA it got stuck at [3/4 flashing recovery] for a long time..... (Force restart)
3) I saw a solution <Click Here> then after downloading the recovery.img and running the code... It say done but after i restart nothing happen.
4) I continue using AfterOTA, again it got stuck at [3/4 flashing recovery] for a long time.....(Force restart)
I out of option....

erm... Help ???

Use fastboot to do a complete wipe.
Run ICSROOT. Zip to get rid of the boot.p file.
Reflash the v8 and cwm using apxflash tool
Boot straight to cwm and flash yr rom.
Do not use any type of rom manager apps to flash roms
Sent from my GT-I9300 using Tapatalk 2

FIXED !!!
Yeah !!! Got It to work !!!
Big THANKS to all who have help and spend time answering my noob questions...
THANK !!!!

[STOCK][N][ARB01] H830 20N ZIPs + KDZ (2017-12-01 Security Patch)

First off, a HUGE thank you to @autoprime (for paving the way) and @waylo (for his assistance on getting this going after I found the KDZ)
I am currently storing these in my google drive account, so please be gentle till I have a better host location:
Below are the downloads for the LG-H83020N firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020N-Flashable.COMPLETE-ARB01.zip
As always, COMPLETE is 100% stock
Flash COMPLETE zip -> wipe cache partition -> flash Magisk ZIP (or SuperSU if you insist) to root and keep TWRP
OPTIONAL: After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks
LG-H83020N-Flashable.Bootloader-ARB01
LG-H83020N-Flashable.Modem-ARB01.zip
LG-H83020N-Flashable.Boot.zip
H830N_00_1017.kdz (HUGE Thank you to @Azul Baseem for the upload)
For instructions, follow the same instructions as you would in any other KDZ/ZIP thread. For Example
Feel free to hit thanks.
Also feel free to hit up autoprime's All in One thread HERE

Thank you very much bedwa!

Kdz link updated!

Thank you @bedwa as always.
I fear my only true contribution here is MD5 confirmation of the files:
LG-H83020N-Flashable.COMPLETE-ARB01.zip 8a49733028bef23d775bf542eb62b726
LG-H83020N-Flashable.Boot.zip ddea9d814f66266de34a154f0c7f6b41
H830N_00_1017.kdz 732b717af8d77501342be445002c4fae
Edit: Also, since someone will definitely miss it in the title, this is confirmed to still be on Anti-Rollback 1. You're free to flash back and forth between 20A if you need to Dirtycow your phone again.

Keeping me honest, I swear I'll remember them next time.

Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.

shinji257 said:
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
Click to expand...
Click to collapse
Fixed. That's what I get for using the copypasta method. Missed the one. :silly:

help me
{
"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 had this issues when i try to flash it i already use uppercut

solved
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?

abced123 said:
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
Click to expand...
Click to collapse
That would be trickier. All of these are the partition images. To make a slim zip like that I'll have to either unpack and build or unpack and attempt to repack. I might, but not likely at this time.

Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)

fc3211 said:
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
Click to expand...
Click to collapse
Quite welcome... It's more time consuming than hard work, but the appreciation and thanks is greatly appreciated as well.

@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.

Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?

nizarp said:
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Click to expand...
Click to collapse
Backup is always good, shouldn't have to restore it as it's updating from a previous version and doesn't wipe data when upgrading. But that's the correct process with or without #6.
azizo07 said:
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
Click to expand...
Click to collapse
Shouldn't, but it would always be a good idea to backup beforehand. I would however only flash the bootloader, as the boot is the kernel and will be different than what LineageOS uses though.

I just boot into TWRP and flashed the complete zip and then flashed the latest SuperSU Zip. I pressed Reboot System after that, but, I am now stuck in a boot loop. Phone shows LG logo and reboots again and again.
I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?

Sounds like you will need to LGUP or Uppercut your phone back to stock 20A. Then dirtycow back TWRP. Then try flashing the new ZIP again. Skip Supersu this time and try Magisk instead.

Thanks. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?

No, rebooting into TWRP wouldn't do anything. There's a script you might need to get into and delete prior to rebooting. But that only ensures that TWRP stays.
"After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks"
That having been said, I've done this before and STILL not had TWRP stay. Some recommend wiping /cache as well.
OR, again, use Magisk instead and don't use SuperSU.
Even if TWRP didn't stick, you should have been booting into system fine. You wouldn't be rooted, TWRP would be gone, but system shouldn't have been messed up. So something got borked, I'd have to guess, because of SuperSU.

New security patch update alert