I haven't flashed either of these so I don't promise that they work. They ought to though.
I suggest you follow the instructions in the original root post under Commands to dump system.img and dump an image from your working phone. Name it something you'll remember and keep it on your internal storage. If something goes wrong from flashing the rooted image you can hopefully recover by changing the filename in the flash command to your original image. Don't run a factory reset or the original image will be deleted.
You'll want to rename the image file you extract from the RAR file. I named them with detail so I wouldn't get them confused.
Good luck!
A user reported that the H81010b image bootlooped their phone. Use at your own risk. You can flash the H810PR KDZ to recover but there's no going back to AT&T stock then. Keep a good copy of your original system.img on internal memory to recover and don't factory reset!
ATT_H81010b_Rooted.system.rar
ATT_H81010e_Rooted.system.rar
Why'd I use RAR? Why not? I'm one of those weirdos that paid for it. A site license even!
Here's my H810 repository on Androidfilehost if you're looking for other H810 files.
It says the img is not mountable, is it safe?
Edit: For 10e, yes it works.
thanks
and winrar 5 is awesome, love it. I've always been a fan of winrar
yoavst said:
It says the img is not mountable, is it safe?
Edit: For 10e, yes it works.
Click to expand...
Click to collapse
Here's a way to open the img file in Windows, but it's much easier to make an Ubuntu boot flash drive and mount it in Linux.
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Norcalz71 said:
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Yes I did with the original params for the G version (I had e).
Norcalz71 said:
@phineous, it seems the 10e file works so I will give it a try tomorrow morning.
For my personal knowledge of the whole process, how did you determine the dd command parameters (block size, count, skip, etc) for the system.img dump command as well as the flashing command that fit the 10e software version? Are all 810 software versions (10e, 10b, 10g, etc) all the same command parameters of is there a way to determine the correct parameters to enter. Regardless of if all 810 versions are the same parameters, I'm sure there is a process to figure out the right things to enter into the dd command?
Thanks!
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
@autoprime posted the commands to flash the different versions in the original root thread. All the AT&T H810 versions use the same command to flash.
The variables for the flash command are determined based on the location of the partition you want to overwrite in the partition table on the phone. There's a little discussion about it in the original root thread, but I'm sure it's discussed more in depth in rooting threads for earlier phones and threads about Android rooting in general.
phineous said:
@autoprime posted the commands to flash the different versions in the original root thread. All the AT&T H810 versions use the same command to flash.
The variables for the flash command are determined based on the location of the partition you want to overwrite in the partition table on the phone. There's a little discussion about it in the original root thread, but I'm sure it's discussed more in depth in rooting threads for earlier phones and threads about Android rooting in general.
Click to expand...
Click to collapse
Got it, thanks @phineous. I can follow directions like these pretty easily (it is all indeed low effort) but I like to try and understand the process behind the commands. So the seek/count/block size parameters, whether dumping a system.img or flashing a stock or rooted system.img are all the same for each command and for each software version across the H810? In this case they are:
bs=8192
seek=65536
count=579584
I'll have to dig a little more to learn how they figured out the proper parameters for each model.
Thanks again
Norcalz71 said:
Got it, thanks @phineous. I can follow directions like these pretty easily (it is all indeed low effort) but I like to try and understand the process behind the commands. So the seek/count/block size parameters, whether dumping a system.img or flashing a stock or rooted system.img are all the same for each command and for each software version across the H810? In this case they are:
bs=8192
seek=65536
count=579584
I'll have to dig a little more to learn how they figured out the proper parameters for each model.
Thanks again
Click to expand...
Click to collapse
It's the same for the AT&T H810s. The Claro H810pr that some us used after we killed our AT&T phones is different.
Look for posts about android partitions. @rightonred has a couple of posts where they show the partition table from our phones.
Here's the man(ual) page for dd where the commands (BS,SEEK,COUNT) are documented.
phineous said:
It's the same for the AT&T H810s. The Claro H810pr that some us used after we killed our AT&T phones is different.
Look for posts about android partitions. @rightonred has a couple of posts where they show the partition table from our phones.
Here's the man(ual) page for dd where the commands (BS,SEEK,COUNT) are documented.
Click to expand...
Click to collapse
Have a question for OP, this is just came into my head but flashing this img into 810pr fw will break the system itself as the seek and count partition are totally different..or what if we used code seek and count from PR??
faizalotai said:
Have a question for OP, this is just came into my head but flashing this img into 810pr fw will break the system itself as the seek and count partition are totally different..or what if we used code seek and count from PR??
Click to expand...
Click to collapse
That could work, but I don't know much about how the system checks itself and the bootloader. I think it would probably end up with the security error boot screen.
phineous said:
That could work, but I don't know much about how the system checks itself and the bootloader. I think it would probably end up with the security error boot screen.
Click to expand...
Click to collapse
autoprime said:
I just looked into the H810PR 10A files and it seems it's about equal to the AT&T H810 10G (newest ATT OTA). The H810PR 10A and the H810 10G (and I think 10E as well) have updated bootloaders with the "1" version... which was updated from the initial version out of box.. i think it was 10A (or 10b/10c/d.. not e/f).
So... obviously for people who were "bricked" (stuck in download mode) you should use this KDZ as that's about you're only hope at this point. KDZ will upgrade bootloader and you will be set at "1".. never to be at "0" again. 0 vs 1 doesnt mean anything yet... so it may not matter. But any possible bootloader exploit that may happen in the future that somehow only works on v0 bootloaders... you'll be out of luck. But lets hope that isn't the case. And who knows if there will even be an unofficial unlock.
For those who ARENT stuck in download mode but don't care about being on an updated "1" bootloader.. feel free to flash H810PR KDZ all you want.
For those who are on the original AT&T sw (10a/b/c/d) with a "0" bootloader who want root and wanna stay at "0"... someone with your 10a/b/c/d sw will need to dump and upload that system.img and then someone will have to root it.. then upload that img... then H810 10a/b/c/d users will have a safe root method that won't cause a security error and also won't update the bootloader. And maybe it'd be safe for now to keep the pre-rooted system.img (the one that doesnt yet exist as of the moment i am typing this) on your internal storage so if anything were to happen you could reflash system.. never needing an H810 KDZ/TOT (as long as you don't mess with other partitions).
Click to expand...
Click to collapse
@autoprime
I forgot about that post. It wouldn't work then. There was a version # in the build.prop that made me think H810PR had an older bootloader.
How do we determine/confirm if a software version bootloader count is at 0 or 1? I thought 10e was at 0 still but maybe not? Hopefully it is...
Sent from my LG-H810 using Tapatalk
Have we confirmed this works with 1010e? I just got the phone and that is the version installed and I want me some root
Edit, nvm it worked perfectly, thanks!
Rooted my at&t 10e with your image. Work great. Thanks.
Sent from my LG-H810 using Tapatalk
Obsolete
GvIn2it said:
Has anyone rooted their H81010b with this file?
---------- Post added at 09:01 AM ---------- Previous post was at 08:48 AM ----------
How can this work with the original root post, that file is 4GB. This one is only 1.6GB. Just interested to know. It's a little scary when someone posts:
"I haven't flashed either of these so I don't promise that they work. They ought to though." Where did they come from? Did you make them, or someone else who tested them? I would really like to try the H81010b but need a little verification.
Click to expand...
Click to collapse
You must extracted zip/rar to image..than copy to internal memory.
have you tried the H810 10b yet. I tried it on my phone and i keep getting a bootloop......
I really want my 4g back
scabbie1980 said:
have you tried the H810 10b yet. I tried it on my phone and i keep getting a bootloop......
I really want my 4g back
Click to expand...
Click to collapse
I don't think anyone has tested it yet.
Are you flashing it on an AT&T H810 with 10b or on the H810PR? It won't work on the H810PR.
If my 10b image really is broken I'll take it down.
Since none of the updates have prevented root, I doubt LG has made security changes to the bootloader. It's probably safe to upgrade to a new version. They're having a hard enough time making the phone work. I hope they're not wasting time patching, especially when we haven't even found a bootloader unlock. I could be wrong though.
Related
Good Afternoon,
I'm not sure what I did incorrectly but I am stuck at the screen with the Android belly open when trying to boot after using the Low Effort Method. I tried doing a factory restore and got nowhere with it. I do not see a stock KDZ for the ATT variant, what can I do at this point? Am I SOL until a dump is released for stock ATT or should I take my chances and bring it to ATT.
I'm assuming flashing the KDZ for any other variant would be a giant no no at this point.
(update) I see i'll need to wait for a TOT or take my chances with ATT, still anyone with a suggestion I appreciate it.
Any help is appreciated.
I am in the same boat, as of now there is no fix.
keeper22 said:
I am in the same boat, as of now there is no fix.
Click to expand...
Click to collapse
See the link below, i'll be trying in a little bit.
http://forum.xda-developers.com/g4/...are-to-stock-kdz-t3107848/page10#post62072832
EDIT: Confirmed WORKING. No issues so far.
Do you have root after your fix? (Thank you for the info and fix)
keeper22 said:
Do you have root after your fix? (Thank you for the info and fix)
Click to expand...
Click to collapse
No root yet, but I read the system.img was available to the developers. Possibly will see a file shortly.
Please post if you find any issues with your phone while using H810pr. So far I think I'm keeping it.
Just to let yall know that i've already submitted an image of PR to thecubed so we can get root
Mine bricked also. Not sure what went wrong. It went through the process like everything worked, the phone rebooted and that was it.
you can try the H810PR kdz to get you out of bootloop
phineous said:
Please post if you find any issues with your phone while using H810pr. So far I think I'm keeping it.
Click to expand...
Click to collapse
The only issues that I have had is not being able to get my LTE working. Other than that it seems to be running better than it was.
So just a heads up, I took a system image(PR version) and injected root but after flashing the image back I ended up with a bricked device (screen doesn't turn on, device recognized as Qualcomm HS-USB QDLoader 9008. I'm almost certain I didn't mess up in terms of the commands I entered when in send command mode. Anyways, I'm going to see if I can either fix this or get it replaced.
playgameo said:
So just a heads up, I took a system image(PR version) and injected root but after flashing the image back I ended up with a bricked device (screen doesn't turn on, device recognized as Qualcomm HS-USB QDLoader 9008. I'm almost certain I didn't mess up in terms of the commands I entered when in send command mode. Anyways, I'm going to see if I can either fix this or get it replaced.
Click to expand...
Click to collapse
Thanks for trying mate. I've been trying to find a Linux to do this myself. I guess there is more than to just follow the instruction of injection.
playgameo said:
So just a heads up, I took a system image(PR version) and injected root but after flashing the image back I ended up with a bricked device (screen doesn't turn on, device recognized as Qualcomm HS-USB QDLoader 9008. I'm almost certain I didn't mess up in terms of the commands I entered when in send command mode. Anyways, I'm going to see if I can either fix this or get it replaced.
Click to expand...
Click to collapse
Check the second post on the root thread. H810PR seems to be partitioned differently (see below). I'm glad they posted this and I checked the thread this morning because I was almost screwed again. The devs had said that the partition info was easy to view so we could figure it out for ourselves, but all the one click rooting has made me a lazy rooter.
H810PR
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
H810
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
Sorry for your loss!
Good news is that the warranty phone I got was a pristine H81010b. Hopefully you'll get the same. I made an image of it and now have dev upload on androidfilehost.com.
I'm posting unrooted images of H81010b, H81010e, and a hopefully properly extracted H810PR10a-310-410 now. If I have time today I'll give root injection another shot and upload the rooted files too.
phineous said:
Check the second post on the root thread. H810PR seems to be partitioned differently. I'm glad they posted this and I checked the thread this morning because I was almost screwed again.
H810PR
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
H810
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
Sorry for your loss!
Good news is that the warranty phone I got was a pristine H81010b. Hopefully you'll get the same. I made an image of it and now have dev upload on androidfilehost.com.
I'm posting unrooted images of H81010b, H81010e, and H810PR10a-310-410 now. If I have time today I'll give root injection another shot and upload the rooted files too.
Click to expand...
Click to collapse
I actually did see that and used the command they provided for getting the image and flashing it back. The inject script might have done something weird though because it failed at the umount command but i just ran that one command manually and figured everything would be okay but I guess it wasn't. I called ATT like 2 days ago before i flashed the PR kdz and they told me I can go to their device support store and that they would replace my device right there for me so hopefully that can still happen. I have an appointment at 5pm today
playgameo said:
I actually did see that and used the command they provided for getting the image and flashing it back. The inject script might have done something weird though because it failed at the umount command but i just ran that one command manually and figured everything would be okay but I guess it wasn't. I called ATT like 2 days ago before i flashed the PR kdz and they told me I can go to their device support store and that they would replace my device right there for me so hopefully that can still happen. I have an appointment at 5pm today
Click to expand...
Click to collapse
There's a new root injection thread here I'm going to try.
Let us know how it goes at with Device Support. I was told the one nearest me wouldn't have G4s yet.
Good luck!
Hopefully we can get these files tested by another sucker so you don't have to risk it!
playgameo said:
I actually did see that and used the command they provided for getting the image and flashing it back. The inject script might have done something weird though because it failed at the umount command but i just ran that one command manually and figured everything would be okay but I guess it wasn't. I called ATT like 2 days ago before i flashed the PR kdz and they told me I can go to their device support store and that they would replace my device right there for me so hopefully that can still happen. I have an appointment at 5pm today
Click to expand...
Click to collapse
I'm willing to test it out. I have a fully functioning h810pr and a backup phone in case my G4 toasted, it wont be a problem
bobimbap said:
Can you try this root injection instruction. It seem pretty well instructed. I dont have a Linux around to try
Click to expand...
Click to collapse
Well I don't have a working device right now to test on. I'm currently at work and need to stay on windows (all my IDEs are set up on windows). After work I'm going to head to the AT&T store to try and get my phone replaced. If no one was tried it by then I can. Also, it's not that hard to set up a bootable USB ubuntu drive (and is actually quite useful to have) so you could always do that.
playgameo said:
Well I don't have a working device right now to test on. I'm currently at work and need to stay on windows (all my IDEs are set up on windows). After work I'm going to head to the AT&T store to try and get my phone replaced. If no one was tried it by then I can. Also, it's not that hard to set up a bootable USB ubuntu drive (and is actually quite useful to have) so you could always do that.
Click to expand...
Click to collapse
I thought you can flash h810pr to unbrick your h810?
Well i dont have any knowledge in ubuntu either
bobimbap said:
I thought you can flash h810pr to unbrick your h810?
Well i dont have any knowledge in ubuntu either
Click to expand...
Click to collapse
No, I'm not stuck in the same mode I was before. I can't get into download mode. My screen stays black and I basically can't do anything (Which hopefully means ATT won't be able to see I had the PR firmware on there.)
playgameo said:
No, I'm not stuck in the same mode I was before. I can't get into download mode. My screen stays black and I basically can't do anything (Which hopefully means ATT won't be able to see I had the PR firmware on there.)
Click to expand...
Click to collapse
I've read through ubuntu pendrive instruction and root injection instruction. Looks like i might be able to do it. I will give it a shot when i get off work tonight.
bobimbap said:
I've read through ubuntu pendrive instruction and root injection instruction. Looks like i might be able to do it. I will give it a shot when i get off work tonight.
Click to expand...
Click to collapse
Good luck! Feel free to PM me if you need any help and I'll respond if I can.
All right you losers and screwups! Everyone who sucked hard at rooting has reason to rejoice!
Soft-bricking your phone may have been the best thing to happen to you.
Luck smiles on the unfortunate and the stupid today!
Use a download manager to get these files, and check the MD5 of your downloaded file against AndroidFileHost.
Here's the latest rooted version from @diedemus
Here's the original rooted image for the H810PRa-310-410.
Know what you are doing before attempting to flash these files! Flashing the H810PR firmware is done mostly as a last resort for people who have bootlooping AT&T H810s.
Read all the instructions carefully, then follow the instructions in the root thread 1 through 6, except ignore the parts in step 4 where it mentions tar.gz and the filename since you have a rar file and already had to extract the image file from it and rename it to system.img.
You'll see that we have a different command to flash the H810PR compared to what was used on the H810. Here is the code to copy and paste at the # prompt in the command window:
Code:
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
Paste the above code in the command window, then hit enter and pucker your butt.
Wait for the # prompt to reappear.
Type LEAVE and hit enter.
Prepare to crap your pants again or savor the sweet taste of victory!
Good luck!
Feel free to ask questions, but try searching for an answer first please. XDA is loaded with information, but it's squirreled away deep in various threads. Learning to search XDA is a valuable skill. Even if you don't find an answer to your specific question, you'll learn something anyway.
H810PR is much better IMO than stock AT&T except for the danger of the green blob in the camera. There's hardly any bloat (like 100 less packages on the phone, seriously!), and no CarrierIQ to have to bother disabling. All the stuff AT&T broke is working too.
Cons so far:
Big ol' green dot in the camera. I wouldn't flash this rom unless I had to because of this issue.
No VoLte (voice over LTE). The phone drops to 3G in phone calls. Follow this post to enable LTE outside of a voice call.
Voicemail settings are grayed out. To set up, put your SIM in another phone or call ATT.
Editing options in camera are overwhelming! There's too many things you can change!
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 100 less.
The stuff AT&T removed or broke is not broke.
Editing options in camera are amazing! There's so many things you can change!
No CarrierIQ
Here's my H810 repository on Androidfilehost if you're looking for other H810 files.
This is pretty sweet! I always wanted to post in the dev folder, and make a reserve post. Not that I really did anything worthy of it, but I'm leaving the post here anyway.
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
It worked! It was a bumpy road, thank you for all your help! (oh sweet ad blockers, how I love you)
faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Yes to all your questions.
I repeated the code to flash here to make sure people noticed it was different for H810PR. It's the same in both posts.
Just noticed i no longer have volte with this image. (yes, i have lte)
faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
user787 said:
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
Click to expand...
Click to collapse
Copy OP's code @up..for me i follow till step 9 from THIS then follow this PAGE from 6 to 9 then paste OP code to flash image root
Please read carefully before anything bad happened
faizalotai said:
Please read carefully before anything bad happened
Click to expand...
Click to collapse
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
No problem bud
user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
I edited the OP to make the instructions more clear. Hope it helps!
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
noamaniac said:
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
Click to expand...
Click to collapse
Yes.
What is the LTE icon for this build? I have the 4G icon, but not sure this means LTE.
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
bobloadmire said:
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
Click to expand...
Click to collapse
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T (I don't know why I keep thinking this is possible, it isn't, bootloader is flashed by the KDZ and not compatible with the ATT versions anymore), but I'm going to stick it out on this image for awhile.
I'm keeping an updated list of the pros and cons in the OP.
phineous said:
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T, but I'm going to stick it out on this image for awhile.
Cons so far:
No VoLte (voice over LTE). The phone drops to 3G in phone calls.
Possible problems with voicemail.
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 150 less.
Click to expand...
Click to collapse
Would you Say the phone is snappier overall or is it mainly just to save storage?
bobloadmire said:
Would you Say the phone is snappier overall or is it mainly just to save storage?
Click to expand...
Click to collapse
I ran Debloater and blocked around 98 packages when I was on the AT&T H81010e non-root image. The phone was pretty fast, but something had a memory leak and I'd have to reboot it every morning. This image hasn't had that problem yet, but I've only been using it for a couple of days.
You might want to wait a little while for the people who had to use it to discover any more downsides. I think it'll be easy to switch back to an AT&T image, but I'm not 100% sure because I haven't tested it yet. (not possible till there's a TOT.)
In any case, I think it's a good idea to follow the instructions in the original root thread to extract an image of your working phone, name it something you'll remember, and keep it on the internal storage as an emergency recovery image.
Totes mah gotes. Thanks man.
Anyone that's on this Firmware having issues with voicemail? I can't seem to get google voice to work and when people call my regular voicemail it is saying i'm not available. I've tried entering the code into the dialer and i'm getting an error saying connection error or wrong MMI code.
I went into the forwarding settings in the phone and entered my GV # and received unexpected error from network.
I have seen root is now available for that H810. My software version is H81010g. Is root possible with my phone yet?
Yea check the root thread in the general lg g4 thread.
Sent from my LG-H810 using XDA Free mobile app
I need help! LGG4
I have Software Version. H81010I
I was unaware if a root exploit to unlock bootloader and also to root my phone
was available for my phone yet. I also would prefer a different flashing utility than TWRP.
I dont like it when I used it with my Optimus G.
Thanks in advance.
BH1984 said:
I have Software Version. H81010I
I was unaware if a root exploit to unlock bootloader and also to root my phone
was available for my phone yet. I also would prefer a different flashing utility than TWRP.
I dont like it when I used it with my Optimus G.
Thanks in advance.
Click to expand...
Click to collapse
Right now there is no TWRP for the AT&T variant. Also can you pull your system.img of your stock 10I software? To do that do this:
1. Download these drivers
2. Download the root tools (make sure you mouse over the download button and the bottom of your browser says LG_Root.zip)
3. On this page follow steps 1,2,3,6,7,8,and 9 ONLY also make sure you run the ports.bat and are using the port that says DIAG
4. Then run this command
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
5. When the command prompt returns to # type LEAVE to reboot your phone. Has to be in all caps.
6. On you computer navigate to your phones internal storage and you will see a file called system.img. Upload this to google drive.
Status: Root unsuccessful
I ran the script through cmd. I watched everything happening and I was unable to gain img or root. What do I do next?
BH1984 said:
I ran the script through cmd. I watched everything happening and I was unable to gain img or root. What do I do next?
Click to expand...
Click to collapse
If you followed my steps exactly as above then you shouldn't have root. there should be a file in your phones internal memory called system.img
If you don't have this try it again. when you issue the command
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
it should take 2-3 minutes to come back to the # sign. if it is instant then it didn't work. keep retrying until you get the system.img file.
When you get that and upload it I can root it for you then you can flash it to your phone.
Thanks.
It was able to create a system img for me. I can root it if you just let me know the steps. Should I not just follow all of the steps 1-10?
BH1984 said:
It was able to create a system img for me. I can root it if you just let me know the steps. Should I not just follow all of the steps 1-10?
Click to expand...
Click to collapse
No, that is not how you root it. It needs to be rooted in a linux environment. that's why I asked you to upload, because it isn't a simple process to root.
GMAIL
What is your GMAIL. I will share it through drive?
BH1984 said:
It was able to create a system img for me. I can root it if you just let me know the steps. Should I not just follow all of the steps 1-10?
Click to expand...
Click to collapse
BH1984 said:
What is your GMAIL. I will share it through drive?
Click to expand...
Click to collapse
just post the link here and make it so only people who have the link can see it. once i download it I will post here so you can remove the link if you want. It is safe to share through drive on XDA, I do it all the time.
Here is the IMG
[It won't let me share outside link. PM me your gmail
[
QUOTE=uly609;62657493]just post the link here and make it so only people who have the link can see it. once i download it I will post here so you can remove the link if you want. It is safe to share through drive on XDA, I do it all the time.[/QUOTE]
hey guys, I'm running h*1010g rooted software and I just got a message on my phone saying an update is available anyone have an idea what the update is and if there is a rooted image of it? and if I take the update I would asume I will lose root but is the update itself worth it? the texting bugs and lad on the 1010g are worse than the 1010e. thanks for the response.
---------- Post added 10th September 2015 at 12:30 AM ---------- Previous post was 9th September 2015 at 11:57 PM ----------
hey, just a note to let everyone Know, got home from work plugged my phone is and let it charge to 70% then i was about to run a debloater from my pc but as soon as I plugged in the usb cable the phone said shutting down to install updates! I thought oh hell I'm bricked but the screen came on and said my phone is rooted and unable to install the update. no clue what it was or if it would have been worth it. just thought Id let everyone know.
Hi,
I'm using an unlocked 810 on TMobile, so I can't get any OTA past 10g. Please guide me on how to get 10l and root. Thanks!
mankand007 said:
Hi,
I'm using an unlocked 810 on TMobile, so I can't get any OTA past 10g. Please guide me on how to get 10l and root. Thanks!
Click to expand...
Click to collapse
I don't think you can without ATT sim
Yeah I went to an AT&T store and updated to 10l from there.
mankand007 said:
Yeah I went to an AT&T store and updated to 10l from there.
Click to expand...
Click to collapse
How did you do that? Did it download automatically over their wireless? I wonder if it works work over any att WiFi access point.
Now that the new ZVB security update is out for Sprint LG G Flex 2, is there anyway we can root when we have ZVB installed? Like a rootedZVBsystem.img?
If you can provide the system.img, I can root it.
Run below dd command, then upload the resulting system.img.
dd if=/dev/block/mmcblk0 bs=8192 skip=58368 count=522240 of=/data/media/0/system.img
Click to expand...
Click to collapse
Sent from my LGLS996 using Tapatalk
ls996zvb
The system image is uploaded here:
https://mega.nz/#!fkxjxSpL!WckL2OX7WENO1sGBxSluqK-ggqPkhCnAMUDrdZfcDx8
etirkca said:
Run below dd command, then upload the resulting system.img.
Sent from my LGLS996 using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------
kevin3688 said:
If you can provide the system.img, I can root it.
Click to expand...
Click to collapse
nitroshot said:
The system image is uploaded here:
https://mega.nz/#!fkxjxSpL!WckL2OX7WENO1sGBxSluqK-ggqPkhCnAMUDrdZfcDx8
---------- Post added at 10:14 PM ---------- Previous post was at 10:13 PM ----------
Click to expand...
Click to collapse
Thanks for this! Hopefully now @kevin3688 with grace us with a rooted image. I would have gladly uploaded a ZVB image myself, but I have not yet updated to ZVB from ZV9 as I am rooted. And to be honest, root is so great that I was hoping to get my hands on a rooted ZVB before I update myself
Uploaded
https://drive.google.com/file/d/0B0UblGbOPFYBcUNmQlVPazdGWE0/view?usp=sharing
I can't make it work. following the steps of the thread: ROOT LG G FLEX 2 (LS996-ZV6-ZV7-Sprint/H955-V15a-INT/H950-V11x-ATT) 5.1.1 but using the img you guys uploaded and the dd command on this thread. I have an LG G FLEX 2 LS996 running on 5.1.1 VZB. I can make it through the process but after I finish... no root.
Using the img file posted by kevin3688 in post #6 above this is what I did earlier today with my LS996:
- use LG Flash Tool to flash the ZV8 TOT file to the LS996 (instructions are elsewhere if needed - you might (I'm saying you might here) have to do a Board DL mode flash first then reflash using the Upgrade DL mode immediately afterward - if you get stuck in MiniOS wait for it to load, tap the screen one time as requested, wait for the menu to appear then hold Power and tap "Normal" to reboot normally - this happens after the Board DL flash process, if you get stuck with the blue screen and the big red 2 hold Volume Down+Power for 20+ seconds to totally power the device off - 20+ full seconds or it'll just keep looping, after which you do the same thing again: Board DL mode flash again, then immediately flash using Upgrade DL mode)
- after that's done, set up the phone as usual but stop before adding a Google account, etc (skip all that, just get to the home screen)
- copy the rootedsystem.img for ZVB to the internal storage of the device
- power down, reconnect device in bootloader mode (hold Volume Up while plugging in the USB cable)
- open a Command Prompt where you have the LG_Root files
- verify the diagnostic COM port using ports.bat
- use the Send_Command.exe \\.\COM(port number) command to start the mode necessary - it works if you see the # prompt
- while you don't have to do it, type id (and press Enter) and you should see a string of device ID information - if the command doesn't work and you see nothing at all I'd start over again (you can disconnect the LS996, power it down, then put it back in bootloader mode and try again - the only reason the command might not work is a mismatch in COM ports but again you don't have to use the id command at all, it's completely optional)
- use the command which is for the LG G Flex 2 LS996 Sprint model ONLY:
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=58368 count=522240 of=/dev/block/mmcblk0
to flash the rootedsystem.img (assuming that's the filename, you may have renamed it differently, I don't know) from the internal storage file you copied over to the system partition. Each of the Flex 2 models has a slightly different dd command so MAKE ABSOLUTELY SURE you're using the one I just posted for the LS996 Sprint Flex 2 - if you use one of the other model's dd lines you could do damage to the partition structure so, again, the command I just posted above is for the LS996 only.
When you execute the command you will see nothing but the flashing cursor in the Command Prompt which is normal, no other activity will be noted, nothing on the LS996 either. After maybe 1-2 minutes or so (sometimes less, sometimes a bit more, depending) the flashing cursor will jump down a line, you'll see the # prompt again, and that's the signal the process has completed - it won't tell you anything else, just the # prompt and the flashing cursor.
Type LEAVE (all caps) and press Enter and you're done, the LS996 will then reboot and you should be good to go after the reboot is complete. It will do the full "Android is upgrading..." thing as all the files are inspected/modded/compiled (because it's ART now) as required during the boot process.
After that's done and the phone is properly booted, you'll probably get the notification from SuperSU within a few minutes that it needs to be upgraded, or you can run SuperSU manually and it'll tell you - do the Normal upgrade method, then reboot when required (immediate reboot, don't do anything else with the device after you've done the SuperSU upgrade). After that reboot, get your Google account set up and hit the Play Market to get the latest version of SuperSU (yes another upgrade) and then you should be complete and ready to go with the rest of the device setup as you see fit.
That's the process I've done 15x or more so far with my Flex 2, it's never had issues, never had problems, never failed, so I can't imagine there will be any issues for anyone else as long as they're following the steps accurately. If you do this right and there's still a problem then it typically means something is probably wrong with the device itself for whatever reason and that's the kind of troubleshooting that can't be done in a forum post, unfortunately.
Good luck...
Rooted! Now havin troubles to unlock the LS996 to GSM
Managed to root the phone with the extra instructions provided by br0adband (Thank you very much), now having issues unlocking the phone for a GSM use. Any ideas? I already follow 2 different guides for 2 other forums.
br0adband said:
Using the img file posted by kevin3688 in post #6 above this is what I did earlier today with my LS996:
- use LG Flash Tool to flash the ZV8 TOT
(snip)
- copy the rootedsystem.img for ZVB to the internal storage of the device
Click to expand...
Click to collapse
This is fine, but will only update system to ZVB. radio and possibly other components (bootloader, boot, recovery?) if changed since ZV8 won't be updated.
OTA to ZVB before writing rootedsystem.img to be complete.
etirkca said:
This is fine, but will only update system to ZVB. radio and possibly other components (bootloader, boot, recovery?) if changed since ZV8 won't be updated.
OTA to ZVB before writing rootedsystem.img to be complete.
Click to expand...
Click to collapse
So, I've got a question. I am on rooted ZV9 right now. I was just now planning on using the dd command to flash my backed up UNrooted ZV9 system. From there I was going to update "normally" (I believe this is "OTA" method that you refer to) to ZVB. Then I was going to use dd to install rootedZVB.
Would this be the "complete" method?
jplum22 said:
So, I've got a question. I am on rooted ZV9 right now. I was just now planning on using the dd command to flash my backed up UNrooted ZV9 system. From there I was going to update "normally" (I believe this is "OTA" method that you refer to) to ZVB. Then I was going to use dd to install rootedZVB.
Would this be the "complete" method?
Click to expand...
Click to collapse
That works well. Happy upgrading.
Sent from my LGLS996 using Tapatalk
jplum22 said:
So, I've got a question. I am on rooted ZV9 right now. I was just now planning on using the dd command to flash my backed up UNrooted ZV9 system. From there I was going to update "normally" (I believe this is "OTA" method that you refer to) to ZVB. Then I was going to use dd to install rootedZVB.
Would this be the "complete" method?
Click to expand...
Click to collapse
As I noted in the steps I did above, I went from ZV8 to ZVB directly (rooted, of course). I installed the ZV8 TOT file, then flashed the rooted ZVB image directly without having ZV9 on the device at all and it works just fine.
I did have to flash the updated radio.img file as noted also but that was done manually using FlashFire, but from what I can tell there's no issues aside from me not being able to get this phone of mine working with T-Mobile - that has nothing to do with the methodology I described however which works.
etirkca said:
That works well. Happy upgrading.
Sent from my LGLS996 using Tapatalk
Click to expand...
Click to collapse
Thanks! Worked great, now running rooted ZVB.
jplum22 said:
Thanks! Worked great, now running rooted ZVB.
Click to expand...
Click to collapse
Did you have any apps frozen before updating? Wondering if it matters. I have lots of stuff frozen...
hallucinate said:
Did you have any apps frozen before updating? Wondering if it matters. I have lots of stuff frozen...
Click to expand...
Click to collapse
I didn't have any of my apps frozen. I would have (because I hate bloat) but instead I just live dangerously and flat-out remove all the bloat apps I can.
Another successful update and root here. Thanks guys!
jplum22 said:
I didn't have any of my apps frozen. I would have (because I hate bloat) but instead I just live dangerously and flat-out remove all the bloat apps I can.
Click to expand...
Click to collapse
my phone is freezing like hell , everytime in 20-30 seconds , reflashed zv8 tot many times , wiped data/cache , flashed rootedsystem , system images , still the freezing is present !! before following @br0adband method i.e f=before updating , there were no freeze.
Also camera and phone are not working !!!(currently on zvb).
br0adband said:
Using the img file posted by kevin3688 in post #6 above this is what I did earlier today with my LS996:
- copy the rootedsystem.img for ZVB to the internal storage of the device
- power down, reconnect device in bootloader mode (hold Volume Up while plugging in the USB cable)
- open a Command Prompt where you have the LG_Root files
- verify the diagnostic COM port using ports.bat
- use the Send_Command.exe \\.\COM(port number) command to start the mode necessary - it works if you see the # prompt
- while you don't have to do it, type id (and press Enter) and you should see a string of device ID information - if the command doesn't work and you see nothing at all I'd start over again (you can disconnect the LS996, power it down, then put it back in bootloader mode and try again - the only reason the command might not work is a mismatch in COM ports but again you don't have to use the id command at all, it's completely optional)
- use the command which is for the LG G Flex 2 LS996 Sprint model ONLY:
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=58368 count=522240 of=/dev/block/mmcblk0
to flash the rootedsystem.img (assuming that's the filename, you may have renamed it differently, I don't know) from the internal storage file you copied over to the system partition. Each of the Flex 2 models has a slightly different dd command so MAKE ABSOLUTELY SURE you're using the one I just posted for the LS996 Sprint Flex 2 - if you use one of the other model's dd lines you could do damage to the partition structure so, again, the command I just posted above is for the LS996 only.
When you execute the command you will see nothing but the flashing cursor in the Command Prompt which is normal, no other activity will be noted, nothing on the LS996 either. After maybe 1-2 minutes or so (sometimes less, sometimes a bit more, depending) the flashing cursor will jump down a line, you'll see the # prompt again, and that's the signal the process has completed - it won't tell you anything else, just the # prompt and the flashing cursor.
Type LEAVE (all caps) and press Enter and you're done, the LS996 will then reboot and you should be good to go after the reboot is complete. It will do the full "Android is upgrading..." thing as all the files are inspected/modded/compiled (because it's ART now) as required during the boot process.
After that's done and the phone is properly booted, you'll probably get the notification from SuperSU within a few minutes that it needs to be upgraded, or you can run SuperSU manually and it'll tell you - do the Normal upgrade method, then reboot when required (immediate reboot, don't do anything else with the device after you've done the SuperSU upgrade). After that reboot, get your Google account set up and hit the Play Market to get the latest version of SuperSU (yes another upgrade) and then you should be complete and ready to go with the rest of the device setup as you see fit.
That's the process I've done 15x or more so far with my Flex 2, it's never had issues, never had problems, never failed, so I can't imagine there will be any issues for anyone else as long as they're following the steps accurately. If you do this right and there's still a problem then it typically means something is probably wrong with the device itself for whatever reason and that's the kind of troubleshooting that can't be done in a forum post, unfortunately.
Good luck...
Click to expand...
Click to collapse
Followed the instructions above without the flash tool or tot and rooted perfect. Rooted with zvb update.
Dirty 'dd' flashed rooted zvB image directly on top of rooted zv9. Only had to update the 'Super SU' afterwards.
No need to go back to unrooted zv9 or unrooted zvB. Just go directly.
All the settings and apps are intact and working fine. No problems. This is for a T-Mobile set up LS996.
If you want to do it even quicker, install and use 'Terminal Emulator' app to issue the 'dd' command directly from your phone. Type 'su' for a # prompt in the terminal then type in the exact 'dd' command. No need to use a PC to run the 'dd' command.
[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix)
Team
After a flash gone very bad, I got myself a brick with a locked bootloader & wrong viariant in LGUP [US996-->H990ds].
In my attempt to recover I tried several silly things including flashing another variants firmware, however I managed to find a way to unbrick & restore the original firmware.
I ran into the G5 thread by @smitel, and did something similar for our V20 by patching LGUP.exe & our phones LGUP_common.dll with HxD Hex editor (my patched files attached).
After doing this I was able to force-flash either partial or full stock kdz using the [PARTITION DL] option, bypassing the variant mismatch warning (Phone was fully recognised as US996).
It even corrected the partition layout (H990DS is different to US996).
Credits about the original patch should go to @smitel
Press the THANKS button if you have found this thread helpfull
Prowler_gr said:
I ran into the G5 thread by @smitel by patching LGUP.exe & our phones LGUP_common.dll with HxD Hex editor (my patched files attached)
After doing this I was able to force-flash either partial or full stock kdz using the [PARTITION DL] option, without getting the dreaded variant mismatch.
Click to expand...
Click to collapse
I very glad to read you managed to save your phone! What you've found though may potentially be rather more powerful than you think (I don't know how powerful you think this is).
Instead of the complex DirtySanta procedure using DirtyCOW/CVE-2016-5195, it should be possible to use this to directly rewrite aboot. At which point you've greatly simplified the procedure, as well as opening it up for phones which lack a sufficiently early KDZ (Sprint which has no KDZ, H990TR which January is earliest).
Does still need a bit of experimentation to confirm though...
emdroidle said:
I very glad to read you managed to save your phone! What you've found though may potentially be rather more powerful than you think (I don't know how powerful you think this is).
Instead of the complex DirtySanta procedure using DirtyCOW/CVE-2016-5195, it should be possible to use this to directly rewrite aboot. At which point you've greatly simplified the procedure, as well as opening it up for phones which lack a sufficiently early KDZ (Sprint which has no KDZ, H990TR which January is earliest).
Does still need a bit of experimentation to confirm though...
Click to expand...
Click to collapse
I'm aware of the great value of my discovery. (Almost makes us unbrickable)
I was able to upgrade official firmware without loosing root or twrp.
To be honest I haven't tried flashing aboot or unofficial kdz, but if possible it unlocks full potential....
Prowler_gr said:
I'm aware of the great value of my discovery. (Almost makes us unbrickable)
I was able to upgrade official firmware without loosing root or twrp.
To be honest I haven't tried flashing aboot or unofficial kdz, but if possible it unlocks full potential....
Click to expand...
Click to collapse
I'd hardly rate it as "almost unbrickable" (`dd if=/dev/zero of=/dev/block/bootdevice/by-name/xbl2`; you're toast), but does give additional tricks.
There are a few other methods of doing firmware upgrades without losing root or TWRP. Both extracting the KDZ and turning into a flashable .zip, or my tool for directly writing the contents of a KDZ file.
The real potential here is if this can be used to install the DirtySanta aboot image, then it is a much simpler installation method. This should also be able to avoid the unreliable installing TWRP via `fastboot flash`. Additionally since this isn't relying on DirtyCOW/CVE-2016-5195 even up to date phones should be able to use this.
You're on a vanilla H990 single-SIM? Rooted via my method? Other method?
I agree that this method won't save you once you lose "Download Mode" that's why I used the word "Almost"
I have a dual-sim H990DS, originally rooted with your method (even paid for your bounty. although hadn't pledged).
I had a US996 rom fully flashed on my phone (with different partition layout), & I was still able to go back using this method.
Well, I will be the guinea pig
I got my H910 back from LG, and of course dirtycow was patched, so if this can flash the us996 debug aboot and not brick my phone, that will be something.
EDIT: @emdroidle I am not at home, but looking at your repo, it looks like you are now able to package back up a v20 format KDZ. If that is true, and this patched LG UP can ignore the signature of the KDZ -- this may very well be one of the greatest finds in a long time. Really looking forward to testing it to see....
It worked on my device. thank you very much
---------- Post added at 02:07 PM ---------- Previous post was at 02:02 PM ----------
runningnak3d said:
Well, I will be the guinea pig
I got my H910 back from LG, and of course dirtycow was patched, so if this can flash the us996 debug aboot and not brick my phone, that will be something.
EDIT: @emdroidle I am not at home, but looking at your repo, it looks like you are now able to package back up a v20 format KDZ. If that is true, and this patched LG UP can ignore the signature of the KDZ -- this may very well be one of the greatest finds in a long time. Really looking forward to testing it to see....
Click to expand...
Click to collapse
I have a h910 device and I have kdz to h910pr version. But I can not unlock device to root. And I used this way. It can kdz us996 files without problems
@bilong9 So you flashed a stock US996 KDZ onto your H910 with this method, or did you repackage a KDZ with the US996 debug aboot?
-- Brian
runningnak3d said:
Well, I will be the guinea pig
I got my H910 back from LG, and of course dirtycow was patched, so if this can flash the us996 debug aboot and not brick my phone, that will be something.
EDIT: @emdroidle I am not at home, but looking at your repo, it looks like you are now able to package back up a v20 format KDZ. If that is true, and this patched LG UP can ignore the signature of the KDZ -- this may very well be one of the greatest finds in a long time. Really looking forward to testing it to see....
Click to expand...
Click to collapse
runningnak3d said:
@bilong9 So you flashed a stock US996 KDZ onto your H910 with this method, or did you repackage a KDZ with the US996 debug aboot?
-- Brian
Click to expand...
Click to collapse
Yes. I used this method for my h910 device. My english is very bad sorry
---------- Post added at 02:50 PM ---------- Previous post was at 02:26 PM ----------
---------- Post added at 02:54 PM ---------- Previous post was at 02:50 PM ----------
I already knew that you can flash any V20 variants stock rom if the kdz is officially signed by LG (my phone was fully recognised as US996 when bricked & was able to flash H990DS firmware).
What I don't know is if an unofficial .kdz (not signed by LG - eg compiled with KDZ extractor) can be flashed.
I strongly suspect it would but haven't tried it yet.
I wish this had worked for me. Both LGUP and LG Flashtool 2014 both fail every time. With your patched files for LGUP I got stuck at 4% and then it crashes. Before I used the patched files I got stuck at 9% and then it crashes. I'm on US99610H and I want to downgrade but have had no luck and I can't seem to find how to solve the issues I'm having.
@me2151
Slashbeast24 said:
I wish this had worked for me. Both LGUP and LG Flashtool 2014 both fail every time. With your patched files for LGUP I got stuck at 4% and then it crashes. Before I used the patched files I got stuck at 9% and then it crashes. I'm on US99610H and I want to downgrade but have had no luck and I can't seem to find how to solve the issues I'm having.
Click to expand...
Click to collapse
Perhaps try one partition at a time, or try disabling antivirus (my hex edit invalidates the files signature hence some antivirus may classify it as malware).
To be sure I would try flashing US99610H again (to rule-out anti-rollback)...
pro_granade said:
@me2151
Click to expand...
Click to collapse
already attempted it yesterday. it dumps partitions fine but installing partitions is wonkey. it wouldnt flash my boot.img but would flash its header so the phone refused to boot. crashes when you try to flash aboot on.
Prowler_gr said:
Perhaps try one partition at a time, or try disabling antivirus (my hex edit invalidates the files signature hence some antivirus may classify it as malware).
To be sure I would try flashing US99610H again (to rule-out anti-rollback)...
Click to expand...
Click to collapse
Alright, so I downloaded the US99610H KDZ and I just hit Upgrade and It did say something about Anti-Rollback check passed and the LGUP program didn't crash. Is there any way to go back to a previous firmware version or am I stuck with an Unrootable V20?
Slashbeast24 said:
Alright, so I downloaded the US99610H KDZ and I just hit Upgrade and It did say something about Anti-Rollback check passed and the LGUP program didn't crash. Is there any way to go back to a previous firmware version or am I stuck with an Unrootable V20?
Click to expand...
Click to collapse
That hints that anti-rollback is active on your phone (you can flash your current firmware or a higher version - not an older one). Try flashing system only & see what happens (cannot guarantee you won't get a brick, but I believe its highly unlikely - you have been warned)
me2151 said:
already attempted it yesterday. it dumps partitions fine but installing partitions is wonkey. it wouldnt flash my boot.img but would flash its header so the phone refused to boot. crashes when you try to flash aboot on.
Click to expand...
Click to collapse
Is your phone still recognised?
I suggest you retry with another cable (try the lg stock), updated drivers etc. I have flashed aboot many times on my H990DS.
Prowler_gr said:
Is your phone still recognised?
I suggest you retry with another cable (try the lg stock), updated drivers etc. I have flashed aboot many times on my H990DS.
Click to expand...
Click to collapse
lol my phones bricked now(different reason than this) and im leaving the v20 scene
Prowler_gr said:
Perhaps try one partition at a time, or try disabling antivirus (my hex edit invalidates the files signature hence some antivirus may classify it as malware).
To be sure I would try flashing US99610H again (to rule-out anti-rollback)...
Click to expand...
Click to collapse
Prowler_gr said:
That hints that anti-rollback is active on your phone (you can flash your current firmware or a higher version - not an older one). Try flashing system only & see what happens (cannot guarantee you won't get a brick, but I believe its highly unlikely - you have been warned)
Click to expand...
Click to collapse
Alright, so if I just flash the system while clicking Partition DL, I run the risk of having a brick. If I don't get a brick would that somehow deactivate anti-rollback if I just flash the US99610H System?
me2151 said:
lol my phones bricked now(different reason than this) and im leaving the v20 scene
Click to expand...
Click to collapse
lol. You got me sweating. I farewell you (in your thread), & then I read your post here thinking it's because of this...
Enjoy your new toy!!!