H812 Rogers Canada Rooted System Image - G4 General

ROGERS H812 v10h ROOTED SYSTEM IMAGE
Here ya go, gents!
I know there are some Rogers users here, and most of us don't have easy access to Ubuntu to inject root.
I got Ubuntu up and running via VM, so I thought i'd root the new Rogers version 10h for us.
Thanks to greganka for the system image for me to root.
The instructions for how to flash it can be found in hackarchive's "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread. Thanks to him for that.
The correct strings can be found in autoprime's thread HERE.
As usual, I will not be held responsible if you happen to brick your phone flashing this image, by picking the wrong command, etc.
ROGERS 10h Rooted System Image.
Enjoy!

Been looking around for this. Thank you so much!

If I'm currently on the rooted 10b update can I just flash the system image and call it a day?

spartan268 said:
If I'm currently on the rooted 10b update can I just flash the system image and call it a day?
Click to expand...
Click to collapse
Yep. It will be a day...a day of fixing all the issues you will have, lol.
You need to flash the full 10h KDZ first, THEN the rooted System Image, or you will have tons of issues.

If I'm currently on the 10f Telus rooted firmware, and wanna get my Rogers rooted 10h firmware back, how do I go about it?
Do I just follow the same steps I did to update to the Telus? 10h KDZ then flash new image?

850T5m said:
If I'm currently on the 10f Telus rooted firmware, and wanna get my Rogers rooted 10h firmware back, how do I go about it?
Do I just follow the same steps I did to update to the Telus? 10h KDZ then flash new image?
Click to expand...
Click to collapse
Yep! I recommend a factory reset after though. I know it's a pain, but VoLTE isn't working for some of us after using the Telus 10f then going to the Rogers 10h.
I tried everything to figure it out. I finally did a factory reset, and VoLTE and video calling is working again. I think since Telus doesn't support it, their software breaks it on Rogers phones, even after you flash a Rogers KDZ again.
Just FYI. You can dirty flash the Rogers 10h KDZ and then my rooted system image, and if VoLTE works (and you are actually with Rogers), then leave it. If it doesn't, try a factory reset.

GibMcFragger said:
ROGERS H812 v10h ROOTED SYSTEM IMAGE
Here ya go, gents!
I know there are some Rogers users here, and most of us don't have easy access to Ubuntu to inject root.
I got Ubuntu up and running via VM, so I thought i'd root the new Rogers version 10h for us.
Thanks to greganka for the system image for me to root.
The instructions for how to flash it can be found in hackarchive's "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread. Thanks to him for that.
As usual, I will not be held responsible if you happen to brick your phone flashing this image, by picking the wrong command, etc.
ROGERS 10h Rooted System Image.
Enjoy!
Click to expand...
Click to collapse
Thanks a lot! I downloaded it.
I am wondering though, if I were to root after backing up stock system image, how can I restore my phone to stock without root to take OTAs? Can I simply flash stock system image? or do I really need to flash the kdz?

You should just be able to use the "full unroot" option in Supersu, but yes, flashing your original image would also do it.

I work in Burnaby you wanna root it for me haha jk
10h better be worth it for the trouble we have to go through

spartan268 said:
I work in Burnaby you wanna root it for me haha jk
10h better be worth it for the trouble we have to go through
Click to expand...
Click to collapse
Lol it's easy to root if you read the instructions in the root thread. As long as you have windows. I did the hard work already for you by installing Ubuntu and actually injecting root into the system image. All you have to do is flash it.
As for the update, it fixes the touchscreen and the lag. Definitely worth it.

GibMcFragger said:
ROGERS H812 v10h ROOTED SYSTEM IMAGE
Here ya go, gents!
I know there are some Rogers users here, and most of us don't have easy access to Ubuntu to inject root.
I got Ubuntu up and running via VM, so I thought i'd root the new Rogers version 10h for us.
Thanks to greganka for the system image for me to root.
The instructions for how to flash it can be found in hackarchive's "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" thread. Thanks to him for that.
As usual, I will not be held responsible if you happen to brick your phone flashing this image, by picking the wrong command, etc.
ROGERS 10h Rooted System Image.
Enjoy!
Click to expand...
Click to collapse
Should we rename the system image to to the current update or do we just use "rootedsystem" as the img. name in the send command?

boywithabeard said:
[/HIDE]
Should we rename the system image to to the current update or do we just use "rootedsystem" as the img. name in the send command?
Click to expand...
Click to collapse
Nope. Leave it as is. The flash command is already set to flash it with that name. Just copy it to your internal SD, put your phone in download/send command mode, then copy/paste the correct string for the H812.
It's all in that thread I mentioned above. Just make sure you use the correct string for the H812, or you will create a nice leather backed door stop.

GibMcFragger said:
Nope. Leave it as is. The flash command is already set to flash it with that name. Just copy it to your internal SD, put your phone in download/send command mode, then copy/paste the correct string for the H812.
It's all in that thread I mentioned above. Just make sure you use the correct string for the H812, or you will create a nice leather backed door stop.
Click to expand...
Click to collapse
I think I understand the question of the person who posted before you. I'm about to root and need to know the following:
Should the command be this:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
or this:
dd if=/data/media/0/system.rooted.rogers.v10b.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Also, what is the command to RESTORE the stock image over rooted one? I want to document all of that on my PC.

I'm not at home to verify if that is the correct H812 string, but the image should be called "rootedsystem.img".
If you get look at the thread I mentioned in the first post, it has the EXACT string you need, just copy and paste it. That way there is no mistyping. bottom line, DO NOT RENAME THE ROOTED SYSTEM IMAGE FILE. It's all in that thread. Read it, and everyone's questions will be answered!

The restore string is the same, with the exception of the file name (system.img vs rootedsystem.img).
Again, all in that thread.

Ramsey said:
I think I understand the question of the person who posted before you. I'm about to root and need to know the following:
Should the command be this:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
or this:
dd if=/data/media/0/system.rooted.rogers.v10b.img bs=8192 seek=65536 count=548352 of=/dev/block/mmcblk0
Also, what is the command to RESTORE the stock image over rooted one? I want to document all of that on my PC.
Click to expand...
Click to collapse
http://forum.xda-developers.com/g4/...l-variants-soon-root-lg-t3164765/post62028523 This is the thread for injecting root and backing-up sytem .img on various g4 models. your first string is for rooting. but it is wise to backup your system.img first just in case the root flashing is not successful. the command to back-up your phone (h812)is all there just copy and paste. the command for flashing your backup, just erase the "rooted" line just put in "system.img" on the string command and you can flash your system.img backup.

GibMcFragger said:
I'm not at home to verify if that is the correct H812 string, but the image should be called "rootedsystem.img".
If you get look at the thread I mentioned in the first post, it has the EXACT string you need, just copy and paste it. That way there is no mistyping. bottom line, DO NOT RENAME THE ROOTED SYSTEM IMAGE FILE. It's all in that thread. Read it, and everyone's questions will be answered!
Click to expand...
Click to collapse
I did follow the thread in your first post but it tells us to go to another page to get the string and that string actually has the old "system.rooted.rogers.v10b.img" instead of rootedsystem.img!
That's why I wanted to confirm.
Thanks though, it worked fine.
The link posted by gerby has the correct string. Lots of strings online lol.

Um...I used that one too. The link it takes you to is HERE, and it's rootedsystem.img for all the models. I don't know where you read "system.rooted.rogers.10b.img", but it's not where it links you.

GibMcFragger said:
Um...I used that one too. The link it takes you to is HERE, and it's rootedsystem.img for all the models. I don't know where you read "system.rooted.rogers.10b.img", but it's not where it links you.
Click to expand...
Click to collapse
great job
tyfoxx

Oh wow. Thanks a ton! Not looking forward to downloading the whole 4.2gb though
Actually, now that I'm seeing that it's gotten to about 34MB in 5 minutes, it doesn't look like I'm going to be able to do this.
Thanks for doing it though!
Edit: After a router reset, it's going a bit quicker. Still gonna take a long while.

Related

[HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011

Stop, listen. Follow my directions, if you fail to follow directions I will no longer help you. Don't PM me and ask. If you screw up ask in the thread.
Rooted Users (Non - Root Users scroll down below):
MR1 RUU
http://www.multiupload.com/KU7GSF2EY0
PG05IMG_MR1_no_hboot.zip - c64b4367086fff4f51ec3d5d766a0456
Bootloader (FLASH THIS LAST) FLASHING THIS WITHOUT SUCESSFULLY FLASHING THE ABOVE FILE WILL CAUSE A SECURITY WARNING
http://www.multiupload.com/26WG1UZCXR
abda920f3e159fb05c00d8c54a5b8768 - PG05IMG_hboot_1.4.0000.zip
Flash the above PG05IMG_MR1_no_hboot.zip to restore everything to stock + OTA BUT still will have the s-off bootloader.
Rename PG05IMG_MR1_no_hboot.zip as PG05IMG.zip, and flash through hboot (like in the root guide).
To restore the bootloader, rename PG05IMG_hboot_1.4.0000.zip as PG05IMG.zip and flash through the bootloader. DO NOT FLASH THIS unless you are absolutely sure PG05IMG_MR1_no_hboot.zip flashed to your device, without issue.
Now you are done, enjoy. If you screwed up, and got a security warning contact me, don't stress. Then again, don't screw up.
Non root users wanting to return to 1.12.605.6 (Stock, pre OTA) can continue below:
NOT FOR ROOT USERS
Taken from AndroidPolice: [Tutorial] How To "Un-Root" The HTC ThunderBolt And Return It To Stock. Please check the site out.
One of the most popular questions about rooting the ThunderBolt is how to undo the process and return to stock, which renews your eligibility for customer support. Well, here you go:
Instructions:
Please read the whole tutorial first, and pay attention to every detail. Note that your battery needs to be charged to at least 40% at the beginning of the process, and remember to check the MD5 sums of all downloaded files before diving in. As always, neither Android Police nor Team AndIRC are responsible for any damage this may cause to your phone, and, needless to say, returning to stock means you will no longer be able to use root apps like ShootMe and Titanium Backup.
First, download the following files:
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img.
Code:
adb push misc.img /data/local/
adb push busybox /data/local/
adb shell chmod 777 /data/local/busybox
To gain root and flash misc.img:
Code:
adb shell
su
/data/local/busybox md5sum /data/local/misc.img
If the output is anything other than "c88dd947eb3b36eec90503a3525ae0de," stop and start over again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
Rename "PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_
release_174685_signed.zip" to "PG05IMG.zip" before placing it on your SD card.
Finally, reboot into bootloader mode by entering the following command. Allow the stock firmware to flash.
Code:
adb reboot bootloader
You’re done – your phone should now be stock, S-ON.
Bookmarking this, just in case. Thanks, Jcase!
Looks like I'll be going back to Froyo for now. I believe the Sense in GB leak is older than the stock on the device.. plus.. camera doesn't work, weather in clock widget doesn't work.. quadrant score is pretty low.. As for now.. I don't see any solid reason to upgrade to GB.. (though I wish I did).. sigh!
http://forum.xda-developers.com/showthread.php?t=1082114
Follow that to return to stock from gingerbread
I am getting No Image or Wrong Image Error In Final Step. I downloaded Stock Firmware Twice but same issue!
Can anyone help me out? I am not able to return to stock. I have BAMF remix 1.6.3 installed and trying to get back to stock as i have to send this device back to Verizon for replacement. I tried everything..file name is correct....md5 sum is correct however in final step when i tried to load the stock FW the boot-loader says wrong image!!
i downloaded stock FW from every possible source but no different!
Please Help!
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
spjoneser said:
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
Click to expand...
Click to collapse
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
jcase said:
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
Click to expand...
Click to collapse
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
spjoneser said:
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
Click to expand...
Click to collapse
Yes, because some radios seem to cause the files to flash in different orders, doing it like this keeps me from having to make multiple versions.
Sent from my LG Revolution
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Androidfreakz said:
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Click to expand...
Click to collapse
You need to consult the author of the program, because I don't know what it did, I can't support their application.
Sent from my LG Revolution
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
AnalyzeFaith said:
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
Click to expand...
Click to collapse
Reverts everything back to stock + OTA
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Droid_ALM2ND said:
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
Click to expand...
Click to collapse
yes
1234567890
droidrev71 said:
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Click to expand...
Click to collapse
Of course you lost root, this is for restoring to stock. It removes root.
jcase said:
Of course you lost root, this is for restoring to stock. It removes root.
Click to expand...
Click to collapse
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
droidrev71 said:
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
Click to expand...
Click to collapse
if you are S-off, you can just flash the MR1 upgrade from the root guide, otherwise you have to do a complete re-root.

Please Recovery Stock LG G PAD 7 LTE v410

Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks
exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.
dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.
Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...
please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs
Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs

[How to] Unbrick v410

I posted this in the original DEV discussion and I also posted it as a reply to some people with the question. I'm only making this thread to save people from searching through hundreds and hundreds of posts. As you may know there is no kdz or tot for the v410 gpad. Without any clue as to why I woke up and my v410 was in twrp, tried a restore, a wipe, installing custom roms, each time it would say it was successful yet each time it would just boot right back into TWRP. Then i stumbled across a thread made by "Thecubed" in 2013 that had nothing to do with this device, it was a thread about being stuck in TWRP after OTA, so I thought id give it a shot and it worked like a charm 8) here are my instructions
1. if you dont have adb setup adb you can get a minimal adb here
https://www.androidfilehost.com/?fid=385035244224386526
install it, navigate to program files (Or if your on a 64bit system program files(x86)
Right click and click "Open command window here"
2. plug in your device if it isnt already pluged in, and type the following commands pressing ENTER after each line
DO NOT COPY PASTE THE WHOLE THING EACH LINE MUST BE PRESSED ENTERED separately
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
exit
adb reboot
Your phone should boot into your rom now
You can hit thanks for my effort of days of searching and you can also thank the dev of the thread that I got these instructions from "thecubed" here at this link http://forum.xda-developers.com/show....php?t=2451696 Hope this helps someone
Saved my ass tonight! Thanks bud!!
I'm stuck in your boat as well, only booting to twrp. The google docs link dead... but I was able to find the minimal adb. I haven't been able to get a working v410 driver though. Any ideas? I'm on Win10, so perhaps that's my problem.
Edit: I tried another v410 and my pc recognized it, so it's something to do with this tab being stuck in twrp and not getting recognized. if that helps.
I'm in the same boat, nothing I have tried, including the steps listed here seems to work.
If you check the first page of the link majicmazo provided, there are instructions for using the TWRP terminal command, which will start the process of getting it out of its current state.
mikiemc73 said:
If you check the first page of the link majicmazo provided, there are instructions for using the TWRP terminal command, which will start the process of getting it out of its current state.
Click to expand...
Click to collapse
Both links are broken, which is a special feat given the post is only 4 months old and edited on 8/26. Anyway the link you mentioned is correctly posted here: http://forum.xda-developers.com/showthread.php?t=2451696
However, if like me, your device cannot be recognized in Windows, and you're stuck in TWRP, you should run try and run the following command while in TWRP by clicking "Advance" then "Terminal Command" and "Select"
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
The command should run, then tap the return button until you're back to the main screen. Reboot without installing SuperSU.
I have 6 v410 devices with nearly exact same setups. I say nearly, because there must be something different that I'm not aware of. 4 out of 6 updated fine, 2 were bricked. 1 had to be sent to LG for warranty replacement. Go figure.
"I have 6 v410 devices with nearly exact same setups."
Good day, Sir! I have v410 and accidentally bricked it when I tried to change something in build.prop. I have no recovery installed. Nothing at all. The only change I did is the root and I cannot flash it due to some errors. A friend of mine told me I should find back up of other good v410 (.tot file if I'm not mistaken) and it could be applied to my bricked v410. Will it work? What method should be used for the .tot file? Are there anyway I could unbrick it without returning it to service centre? I have no warranty since I bought it abroad. I'm looking forward for your answers. Thank you!
I also have a stock recovery image if anyone needs it. Performing the above steps while in twrp will allow you to reboot back into device, but any updates from ATT will cause the device to brick back to TWRP.
If you flash the stock recovery here using flashify,: https://drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0, you will be able to install the ATTT updates without softbricking into twrp.
ChristopherXDA said:
I also have a stock recovery image if anyone needs it. Performing the above steps while in twrp will allow you to reboot back into device, but any updates from ATT will cause the device to brick back to TWRP.
Click to expand...
Click to collapse
Good!
Sir could you please provide an LG G Pad 7 v410 stock recovery image? I'll try to use it. Thank you!
The Krugz said:
Sir could you please provide an LG G Pad 7 v410 stock recovery image? I'll try to use it. Thank you!
Click to expand...
Click to collapse
Here is the v410 stock recovery: https://drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0
It worked for me but your mileage may vary. I'm not responsible for any issues.
Thank you, kind sir! I'll inform you if it does worked. :good:
Unfortunately, it didn't work. Perhaps you have v410 stock rom I can flash using lg flash tool?
V410 KDZ or stock recovery request.
ChristopherXDA said:
Here is the v410 stock recovery: //drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0
It worked for me but your mileage may vary. I'm not responsible for any issues.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hello,
I have been flashing v410 lately and I have been unable to find a STOCK v410 kdz anywhere.
A stock recovery file would be great!. However, the one one at the above url looks pretty small (at 13MB) or am I missing something?
triathleteninja said:
Hello,
I have been flashing v410 lately and I have been unable to find a STOCK v410 kdz anywhere.
A stock recovery file would be great!. However, the one one at the above url looks pretty small (at 13MB) or am I missing something?
Click to expand...
Click to collapse
That file is just the recovery partition, not a whole system image.
To the best of my knowledge there has been no kdz released for the V410. Thank your carrier for that, because LG provides it for the V400.
please help my when i command adb shell have error device not found i have Qualcomm HS-USB QDLoader 9008 mode on lg gpad v410 ((
Alright this post is almost a year old...But i still went back and updated the Minimul ADB link, the second link on my post is simply a thanks to the original person, yes it was deleted theres nothing I can do but you guys do not need it it was only there for you guys to say thanks to him. This thread is only the solution to being stuck in TWRP, some people here asked me for the stock rom,At the time i wrote this thread no one had a kdz for the v410 however now there in fact is one, its android 4.4.2 http://www.mediafire.com/file/2433xqabj1k8b8d/V41007h_0.kdz and I found it here https://forum.xda-developers.com/g-pad-10/general/unbrick-v410-t3105091. Probably easier then my thread to simply flash this with the flash tools but If you decide to follow my old outdated method, and follow the steps %100 it should theoretly get you out of the TWRP bootloop, it worked for me and I was simply sharing, However if it doest work for you dont bite my head off, there are many reasons why you might be in a boot-loop and many factors that come into play so My solution might not be the best for you. Anyway I dont know why I'm reviving an almost year old thread but I just never read the responses as I havent been on XDA for a while and figured I would post in case anyone still wanted it. Again there is a much easier way now because there is a KDZ so this is outdated.

Official Boost LG G Stylo Unbrick Guide ZV5

I personally Tested this
This system.img works on both Virgen Mobile and Sprint Variants as well, I personally didn't test but other brave souls did
I can't believe i have to post this but if your on ZV4 rooted or not don't flash the ZV5 system.img as it only works if your on ZV5 the VZ4 guide is over here
Attention if you try this and end up with a brick or your device transforms and tries to destroy you; it's not my fault you did this not me. So just read all of this thread not just the O.P (and read the O.P more then once) to get out of a bind if you reply with "the thread is too long i wont read it please help" don't expect anything short of "there's a search bar use it"
here is the ZV5 update zip https://www.androidfilehost.com/?fid=24052804347825955
Continue only if you have messed with the /system partition (and don't remember what you changed) and you are on 5.1.1 this will remove root but you will keep your data
Okay well now
Make sure you have a Windows PC
Download the LG Drivers from here
Download this 5.1.1 System.img
Place downloaded img to your external SD via adapter or through a spare phone you have
Now place SD back into your phone
Reboot your device into download mode
Download this folder and unzip it to your desktop:
Run ports.bat from within the extracted folder, to find your correct port (use the one with: LGVZANDNETDIAG1)
In the LG_Root folder hold shift and right click and choose open command windows here
Type
Code:
Send_Command.exe \\.\COM6
(Make sure your COM port number is correct, it varies)
Type
Code:
dd if=/storage/external_SD/system.img bs=8192 seek=42816 count=327680 of=/dev/block/mmcblk0
you will see a flashing _ line instead of the # let it do it's thing you will know it finished when the # shows back up
Type
Code:
LEAVE
and press enter and let your device reboot
Updating to the ZV5 update wont break root right? And i dont have to unroot to update?
_Cristian_ said:
Updating to the ZV5 update wont break root right? And i dont have to unroot to update?
Click to expand...
Click to collapse
you must flash ZV4system.img to remove all traces of root then use ZV5 update.zip to make everything work without a hitch and yes you can root after the update
I flashed this rom and now im stuck at LG logo with Security Error. Do you know why?
bawanyh said:
I flashed this rom and now im stuck at LG logo with Security Error. Do you know why?
Click to expand...
Click to collapse
Were you already on ZV5?
6th_Hokage said:
Were you already on ZV5?
Click to expand...
Click to collapse
No ZV4 rooted.
---------- Post added at 01:09 PM ---------- Previous post was at 12:58 PM ----------
Does anyone have any KDZ file for this phone?
bawanyh said:
No ZV4 rooted.
---------- Post added at 01:09 PM ---------- Previous post was at 12:58 PM ----------
Does anyone have any KDZ file for this phone?
Click to expand...
Click to collapse
read the OP very carefully, why do people think that they can update with the ZV5 system.img :/ and the reason i made the ZV4 and ZV5 unbrick Guides is because the Boost Variant doesn't have a kdz file
Actually that is the guide I followed and flashed the Zv4 first and got that Security error. Thats why I tried ZV5.
Ok I just flashed the Zv4 again, it took away security error but got stuck on LG logo. I flashed the update.zip in this thread and still same thing. Anything else I can try?
bawanyh said:
Ok I just flashed the Zv4 again, it took away security error but got stuck on LG logo. I flashed the update.zip in this thread and still same thing. Anything else I can try?
Click to expand...
Click to collapse
you may permanent brick....did you copy and paste the commands i wrote?? cause every space matters...
6th_Hokage said:
read the OP very carefully, why do people think that they can update with the ZV5 system.img :/ and the reason i made the ZV4 and ZV5 unbrick Guides is because the Boost Variant doesn't have a kdz file
Click to expand...
Click to collapse
6th_Hokage said:
you may permanent brick....did you copy and paste the commands i wrote?? cause every space matters...
Click to expand...
Click to collapse
Yes I am fimiliar with Send Command I use it everyday to fix LG softwares and to root. The system img loads just fine but still stays stuck on LG. Do you think I should try what someone else is suggesting in other thread (load 5.0.2, then Zv4 and then Zv5 update.zip)?
bawanyh said:
Yes I am fimiliar with Send Command I use it everyday to fix LG softwares and to root. The system img loads just fine but still stays stuck on LG. Do you think I should try what someone else is suggesting in other thread (load 5.0.2, then Zv4 and then Zv5 update.zip)?
Click to expand...
Click to collapse
how long did it stay on the LG Screen cause after a unbrick it doesn't show the boot animation just Lg Screen then the updating apps screen
How long can I expect step 11 to take? I am going on 20 minutes now...
sorheim said:
How long can I expect step 11 to take? I am going on 20 minutes now...
Click to expand...
Click to collapse
yea that's too long it took me like 3-10 minutes
Are you guys sure you are using boost stylos? Since that system.img is from a boost mobile stylo...
Finally i can post! thanks man...your system.img and the update.zip got me goin again. really appreciate your time and hard work. need a tester? got two BOOST stylos...so fire away. anytime. THANK YOU!:good::good::good:
im on ls751 lg volt2
can i back up my system.img and using the method like this when it is bricked
iorikyo645123 said:
im on ls751 lg volt2
can i back up my system.img and using the method like this when it is bricked
Click to expand...
Click to collapse
I suppose you can if your system.img is untouched. But you would need to know the command to send your system.img, since they will be different sizes.
iorikyo645123 said:
im on ls751 lg volt2
can i back up my system.img and using the method like this when it is bricked
Click to expand...
Click to collapse
You need to backup your current system as a system.img before you try to restore with my method....this doesn't pull your system but restore the one I provided
@6th_Hokage so you used the zv4 system.img to go stock then update to zv5? I'm a little worrisome that i'll brick my stylo if i try to use the zv4 system.img, lol. Sorry about all the question btw.

[STOCK][N][ARB01] H830 20M ZIPs + KDZ (2017-10-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-H83020m firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020m-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-H83020m-Flashable.Bootloader-ARB01
LG-H83020m-Flashable.Modem-ARB01.zip
LG-H83020m-Flashable.Boot.zip
H830m_00_1017.kdz
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 for putting this together!
These are the MD5 sums for my downloads, for anyone to check:
LG-H83020m-Flashable.COMPLETE-ARB01.zip = 92885e941b7818a88b79703e38e2c40d
LG-H83020m-Flashable.Boot.zip = 1a3cfe71edbd6864a4a0bcf364b7785c
H830m_00_1017.kdz = 83d7e923b803e728ff16774080a18a27
how to root and recovery this lg g5 h83020m?
nguyenvantuc said:
how to root and recovery this lg g5 h83020m?
Click to expand...
Click to collapse
You need to first install 20A. Then root it and install TWRP using the recowvery exploit. Look that up and search.
Once TWRP is installed, you can flash this as the instructions above.
waylo said:
You need to first install 20A. Then root it and install TWRP using the recowvery exploit. Look that up and search.
Once TWRP is installed, you can flash this as the instructions above.
Click to expand...
Click to collapse
how?
nguyenvantuc said:
how?
Click to expand...
Click to collapse
By searching and reading...
Sent from my LG G5 using XDA Labs
I just f;ashed this in TWRP and it just reboots to twrp over and over
djerick3 said:
I just f;ashed this in TWRP and it just reboots to twrp over and over
Click to expand...
Click to collapse
The TWRP bootloop is an odd thing that pops up sometimes. Not sure if anyone knows exactly why it happens. The fix:
Go to TWRP terminal and punch this in:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
See here for more info:
https://forum.xda-developers.com/showpost.php?p=71797169&postcount=2
waylo said:
The TWRP bootloop is an odd thing that pops up sometimes. Not sure if anyone knows exactly why it happens. The fix:
Go to TWRP terminal and punch this in:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
See here for more info:
https://forum.xda-developers.com/showpost.php?p=71797169&postcount=2
Click to expand...
Click to collapse
Thanks, I did that last night. Now im on Fulmics ROM and love it.
Slightly off topic, but are you missing the Wifi-calling at all (on Fulmics)?
Off topic but is this LG G5 support custom rom? I just got my hand on this device. Thanks for any response.
Is there any surefire way to make a backup on twrp of this after installing a restore of apps, and then transferring it to my pc? I tried it and it seemed to work at first but when I went back only the lonely boot file was inside the backup folder..
im about to sell this phone and get a oneplus damn.. :cyclops:
downgrade
nguyenvantuc said:
how?
Click to expand...
Click to collapse
Link to help with downgrade
https://forum.xda-developers.com/tm...ock-h830-20a-rom-flashable-zips-imgs-t3511294
moe1708 said:
Off topic but is this LG G5 support custom rom? I just got my hand on this device. Thanks for any response.
Click to expand...
Click to collapse
Yes. Look in both the TMO G5 forum and the other G5 forum. There are a few options.
dwcasey said:
Yes. Look in both the TMO G5 forum and the other G5 forum. There are a few options.
Click to expand...
Click to collapse
Thank you for the reply, will start looking for it.
just wanted to mention that the modem download actually takes you to the complete download instead.. but if you go through the folder it works fine
Please forgive me if this isn't the place for this:
I am currently running LineageOS nightly for my h830 and enjoying it, but I'm interested in regaining NFC functionality while maintaining root. Is this something that I can do with a reversion to stock? What bloat should I expect?
Any instruction for how I can go from h83020m to 20n without losing root? Or how to capture an image of an unrooted 20n?
I tried a method of editing the update prop in 20n to work with twrp and it flashed but temporarily bricked my phone :3 thanks
Azul Baseem said:
Any instruction for how I can go from h83020m to 20n without losing root? Or how to capture an image of an unrooted 20n?
I tried a method of editing the update prop in 20n to work with twrp and it flashed but temporarily bricked my phone :3 thanks
Click to expand...
Click to collapse
You'll need to wait for either @bedwa, @autoprime or some other knowledgeable person to make a flashable zip to TWRP over your existing 20M installation.
Also they'd need a source of the new 20N KDZ file.
Hello tools
Deleted delete
---------- Post added at 08:34 PM ---------- Previous post was at 08:21 PM ----------
waylo said:
You'll need to wait for either @bedwa, @autoprime or some other knowledgeable person to make a flashable zip to TWRP over your existing 20M installation.
Also they'd need a source of the new 20N KDZ file.
Click to expand...
Click to collapse
I understand. So there's no current explantion as to how they capture the image, or any general instruction? I'm just looking for a way to capture a stock H83020n system image, honestly.
Is there a site where KDZs are published? The N update is on LG firmware

Categories

Resources