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.
Related
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?
BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568
nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.
znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/
Can I get the stock boot image
I just want to try that last option
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.
I'm a noob but I'd been trying my best understanding to ROOT T959W, I'd followed the steps as described in one of the forums here using odin 1.7 and stock+Voodoo-T959VKJ1.tar and the update in sdcard but unfortunately I don't understand, no matter what i do, when the phone turns on it shows the Recovery mode, I'm however able to boot into the downlod mode and my phone is detectable.
The phone was I guess bricked onetime but i'd used oneclick unbrick and it went back fine.
Please help me to at least get it to a running state not necessarily root.
I don't know if this is right, what should i do next ? Flash the rom CM9 ? or have i messed up ? :S
THANKS A TON!
Attached is a preview.
It seems a little odd. Did you clear everything and not flash a rom?
Sent from my SGH-T999 using xda premium
So you have the "W" phone from Wind and you flashed the bootloader? I can clearly see the Tmobile logo, which shouldn't be on a Wind phone. Just hold on, don't flash anything else and give a few, I'm working with bhundven at this very moment to try and dump my bootloader. Your phone still turns on, there is hope but the more you start clicking all over, etc the more damage you can do, so please wait.
getochkn said:
So you have the "W" phone from Wind and you flashed the bootloader? I can clearly see the Tmobile logo, which shouldn't be on a Wind phone. Just hold on, don't flash anything else and give a few, I'm working with bhundven at this very moment to try and dump my bootloader. Your phone still turns on, there is hope but the more you start clicking all over, etc the more damage you can do, so please wait.
Click to expand...
Click to collapse
Sure, I will be waiting, Yes it shows the Tmobile logo and when I connect it to Odinv1.85 it tells me this phone is T959V but infact its a wind mobile.
I'll be waiting for you guys and will be more than willing to donate.
cheers!
zaryan said:
Sure, I will be waiting, Yes it shows the Tmobile logo and when I connect it to Odinv1.85 it tells me this phone is T959V but infact its a wind mobile.
I'll be waiting for you guys and will be more than willing to donate.
cheers!
Click to expand...
Click to collapse
The T959V in odin is just a label in the ini file in the same directory.
You can change that to say anything you want.
I really recommend taking the time now to remove odin, and it's drivers, and install heimdall.
Look around in the wiki for help on that one.
bhundven said:
The T959V in odin is just a label in the ini file in the same directory.
You can change that to say anything you want.
I really recommend taking the time now to remove odin, and it's drivers, and install heimdall.
Look around in the wiki for help on that one.
Click to expand...
Click to collapse
After i replaced the drivers, and ran flash in heimdall, it gives me an error - I ran T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
"Local and device PIT files don't match and repartition wasn't specified
Ending session...
Rebooting device "
zaryan said:
After i replaced the drivers, and ran flash in heimdall, it gives me an error - I ran T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
"Local and device PIT files don't match and repartition wasn't specified
Ending session...
Rebooting device "
Click to expand...
Click to collapse
I didn't say to run it, yet. I'm making a new oneclick for t959w. Hang tight.
bhundven said:
I didn't say to run it, yet. I'm making a new oneclick for t959w. Hang tight.
Click to expand...
Click to collapse
Sure will be waiting
zaryan said:
Sure will be waiting
Click to expand...
Click to collapse
Me and Brian are working on it. He had to go out for a bit, so waiting for him to get back on IRC and I'm testing it and risking bricking my phone for the good of the 959W users, so please be patient until we have a test package that can restore the bootloaders, param's, everything full for a "W" model. I found a very complicated work around to get out of the loop but I rather wait till we have the 1 click tested and it's easier to use and do.
For now, the standard 1 click should get you back to stock, just don't flash the bootloader at all.
getochkn said:
Me and Brian are working on it. He had to go out for a bit, so waiting for him to get back on IRC and I'm testing it and risking bricking my phone for the good of the 959W users, so please be patient until we have a test package that can restore the bootloaders, param's, everything full for a "W" model. I found a very complicated work around to get out of the loop but I rather wait till we have the 1 click tested and it's easier to use and do.
For now, the standard 1 click should get you back to stock, just don't flash the bootloader at all.
Click to expand...
Click to collapse
You are awesome! It worked like charm, thank you getochkn and xda-dev
zaryan said:
You are awesome! It worked like charm, thank you getochkn and xda-dev
Click to expand...
Click to collapse
Glad I was able to help but I couldn't have done any of this with the guidance of bhundven and others from Team Acid. Hopefully I'll have the true stock modem our phone came with soon, full stock recovery, etc and be able to put out a full package to help people who are bricked or want to go back to stock.
getochkn said:
Me and Brian are working on it. He had to go out for a bit, so waiting for him to get back on IRC and I'm testing it and risking bricking my phone for the good of the 959W users, so please be patient until we have a test package that can restore the bootloaders, param's, everything full for a "W" model. I found a very complicated work around to get out of the loop but I rather wait till we have the 1 click tested and it's easier to use and do.
For now, the standard 1 click should get you back to stock, just don't flash the bootloader at all.
Click to expand...
Click to collapse
any luck with the 1 click for the T959W yet? I am more than willing to donate also, my phone is stuck in download mode only so I desperately need this!!!!
munsen55 said:
any luck with the 1 click for the T959W yet? I am more than willing to donate also, my phone is stuck in download mode only so I desperately need this!!!!
Click to expand...
Click to collapse
Give me a few mins, let me see what I can do.
getochkn said:
Give me a few mins, let me see what I can do.
Click to expand...
Click to collapse
Please bro i have the same problem
please can you help me with the t959w bootloader or 1click solution
Hello, those of you who have soft bricked and can still access download mode, there is a method a user and I @giantpear discovered to bring your phone back to life by flashing the KDZ of the Peurto Rican 810.
Instructions can be found at this thread:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Kudos to @hyelton for his original thread
Note: Remember you are flashing the Puerto Rican Firmware for your phone, not the original stock US KDZ as there is not one yet.
Note: I am not the creator of this thread I am merely re-posting what we found through test in that thread tonight.
Note: I am not sure moving forward if you were to continue to try to root or flash what model method you would want to try. I would say we should wait for a TOT method before trying anything else.
On the positive note, I now have a heavily debloated phone with zero ATT apps on it.
Hope this helps any who have lost their phone attempting root these past few days.
I approve But yeah it should be posted here in the mean time. Until we do get an official A&T TOT.
But this is great for either needing to go back to stock due to soft-brick, or if you like that pure software feeling.
Please make it known that this method isnt compatible for Low Effort Root AT&T H810 10g. I just tried and failed. Reflash the kdz and it all went well. I already submitted a system dump file to #thecubed. Hope we can get a rooted system img shortly.
Kudos @giantpear
user787 said:
Kudos @giantpear
Click to expand...
Click to collapse
@user787 Thank you! Your KDZ link saved at least a dozen ATT 810s. Power to XDA!
This is awesome news! I wish I would have found @user787 post earlier! Hopefully all the other lost H810 souls will see this post soon.
If anyone discovers downsides of using this KDZ, please post what you find in this thread. I've got a replacement phone coming and need to decide if I should keep this one or the AT&T phone. So far I'm liking this variant much better!
You guys should enter donation information in your profile. I'll buy you a beer or two!
would be awesome to make a combo rom with this and root for stateside AT&T phones. A factory heavy debloat rom would be nice since you are guaranteed that the removed apps won't cause issues.
phineous said:
I've got a replacement phone coming and need to decide if I should keep this one or the AT&T phone. So far I'm liking this variant much better!
Click to expand...
Click to collapse
I am with you, I think I will be sending back the warranty replacement they are sending me!
Although the process of bricking and pulling back (thanks to you guys) was a pain in the ass! I really like this ROM. I like it better than the one that came with my phone and so far I have no issues. When this version gets root I think it is the best case scenario. Thank you again for helping us all out!
Next I need to decide if I should take the updates available for it. I see there are ones available but none are being forced.
Edit never mind just app updates.
Sent from my LG-H810 using XDA Free mobile app
keeper22 said:
When this version gets root I think it is the best case scenario.
Click to expand...
Click to collapse
There's a root script out we can run on our system.img file, it just needs to be run on Linux. I'll try to set up a machine tonight if someone doesn't beat me to it.
phineous said:
There's a root script out we can run on our system.img file, it just needs to be run on Linux. I'll try to set up a machine tonight if someone doesn't beat me to it.
Click to expand...
Click to collapse
That's over my head, but I looking forward to it. Let me know if there is anything I can do to help.
Has anyone checked to see if they get good 4G LTE speeds with H810PR? I don't have good 4G coverage (or much data left) to test on. I just ran an LTE speedtest and I maxed out at 11.35 Mbps.
phineous said:
Has anyone checked to see if they get good 4G LTE speeds with H810PR? I don't have good 4G coverage (or much data left) to test on. I just ran an LTE speedtest and I maxed out at 11.35 Mbps.
Click to expand...
Click to collapse
Testing just now
noamaniac said:
Note: I am not sure moving forward if you were to continue to try to root or flash what model method you would want to try. I would say we should wait for a TOT method before trying anything else.
On the positive note, I now have a heavily debloated phone with zero ATT apps on it.
Hope this helps any who have lost their phone attempting root these past few days.
Click to expand...
Click to collapse
Another soul back from the dead.
Has anyone re-tried the Low Effort Root again?
informpage said:
Another soul back from the dead.
Has anyone re-tried the Low Effort Root again?
Click to expand...
Click to collapse
I tried and failed. However i already send a system img of PR to thecubed so we can get root
I've tried low effort root on my H810 last night and it worked perfectly. I've already installed a bunch of root apps and everything is working great.
---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------
bobimbap said:
I tried and failed. However i already send a system img of PR to thecubed so we can get root
Click to expand...
Click to collapse
It worked perfectly fine for me on my H810. At what point did it fail for you?
keeper22 said:
I am with you, I think I will be sending back the warranty replacement they are sending me!
Click to expand...
Click to collapse
I got the warranty replacement phone today. It's brand spanking new with H81010b firmware. I may pull an image off it later in case someone needs it, but I still think I'm sending the phone back. My original works too well to take a chance with new hardware.
probaina said:
It worked perfectly fine for me on my H810. At what point did it fail for you?
Click to expand...
Click to collapse
You probably used the 10g file on 10g system. I tried the 10g root file on PR system since my phone bricked earlier. I had to flash PR kdz to bring it back to life
bobimbap said:
You probably used the 10g file on 10g system. I tried the 10g root file on PR system since my phone bricked earlier. I had to flash PR kdz to bring it back to life
Click to expand...
Click to collapse
Oh I see. Ouch. Yeah I do have 10G system but I see what you're saying now.
phineous said:
My original works too well to now to take a chance with new hardware.
Click to expand...
Click to collapse
It might be because it was dead and now anything is better than that, but I feel like my phone is running better than before I tried to run Low Effort Root!
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.
Dear All,
2 days back I was trying to unlock my LG-V20 phone using DirtySanta Method on this thread
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296?nocache=1
For me it is not working & I want to return it to original LG ROM something goeas wrong & I was stuck on grey ribbon on screen (which I can't read anything) or I can boot it to fastboot command. I was trying to put phone on download mode to use it with LGUP but the program give me unknown device. When I check the forum they said I have to flash kernel. I was trying alot but nothing works with me. Suddenly LGUP define my device as US996 instead of H990DS. So I download the official ROM of US996 & flash it to my device it accept it & screen works normally but the device keeps restarting. It boots to welcome screen or even LG logo then restart. I can't even set it up. anyone can help on this problem??? How can I return it back to original H990DS ROM???:crying::crying::crying:
Another thing is that fastboot commands can't do anything like format & wipe it says device is locked
Hey, no worries. Your device can be saved. Dirty santa can be a bit** to get it to work. Took me like 2 days and several tries...
I'm quite sure I came across this ribbon screen. For me it looked like grey static from a tv without signal, quite scary.
So, the only not good thing you did was to flash the US996 ROM. You have a H990DS, it will not work... But it can be fixed, don't panic.
It's normal that the H990 is seen as US996 by LGUP after flashing the engineering bootloader. Every rooted H990 runs on this one, because there is no unlocked BL available other then this. So that means you came quite far with dirty santa...
I believe the reason that you phone can't start is, LGUP changed your partition layout from H990 to US996 (which will not work)
I'm going from memory here, so I'm not sure about the details. There is a thread in the forum explaining well how to recover a V20 with LGUP / (Uppercut could be important to fix unknown device / allow to cross flash). Follow this one and use the right H990DS Rom to reflash everything and repartition your device correctly. Maybe you have to play with the options like upgrade or repartition. BUT DON'T DO ANYTHING THAT IS NOT MENTIONED AS SAFE TO DO. You could even erase you BL. Then you have a nice brick...
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
You should be able to try with dirtysanta again, I promise it will work, and then you effort wasn't for nothing.
Here in the guide it even tells you that that phone will be detected as US996, the tipps here are good as well..
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
Let me know how it went...
Best regards
Daniel
NoName! said:
Hey, no worries. Your device can be saved. Dirty santa can be a bit** to get it to work. Took me like 2 days and several tries...
I'm quite sure I came across this ribbon screen. For me it looked like grey static from a tv without signal, quite scary.
So, the only not good thing you did was to flash the US996 ROM. You have a H990DS, it will not work... But it can be fixed, don't panic.
It's normal that the H990 is seen as US996 by LGUP after flashing the engineering bootloader. Every rooted H990 runs on this one, because there is no unlocked BL available other then this. So that means you came quite far with dirty santa...
I believe the reason that you phone can't start is, LGUP changed your partition layout from H990 to US996 (which will not work)
I'm going from memory here, so I'm not sure about the details. There is a thread in the forum explaining well how to recover a V20 with LGUP / (Uppercut could be important to fix unknown device / allow to cross flash). Follow this one and use the right H990DS Rom to reflash everything and repartition your device correctly. Maybe you have to play with the options like upgrade or repartition. BUT DON'T DO ANYTHING THAT IS NOT MENTIONED AS SAFE TO DO. You could even erase you BL. Then you have a nice brick...
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
You should be able to try with dirtysanta again, I promise it will work, and then you effort wasn't for nothing.
Here in the guide it even tells you that that phone will be detected as US996, the tipps here are good as well..
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
Let me know how it went...
Best regards
Daniel
Click to expand...
Click to collapse
Thanks a looooooooooot Daniel. Finally my LG is back to normal. I don't want DirtySanta anymore. My device was out for more than 20 days because of this.
Im very glad, that I could help you. It's a nice device and even better when working correctly.
Thanks for letting me know that it worked.
All the best to you too
Philadelphia said:
Thanks a looooooooooot Daniel. Finally my LG is back to normal. I don't want DirtySanta anymore. My device was out for more than 20 days because of this.
Click to expand...
Click to collapse
Its a bit of an op for real, but worth it when done
dornz said:
Its a bit of an op for real, but worth it when done
Click to expand...
Click to collapse
Does it pass SafetyNet with edXoposed installed?
iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Nope,
iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Worth the root
dornz said:
Nope,
Click to expand...
Click to collapse
Are you using the edXposed canary?
iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Glad you mentioned that about safety net, flashed me the Oreo rooted to check that, :silly: