Database Info

[GUIDE] How to PermaRoot your Desire HD

I have just complied this Step-by-Step guide on how to root your Desire HD.
I by no means created the root, I simply used my own and others knowledge to put this guide together to help everyone.
Hopefully this is more of a beginners guide so we can ease new Android users into a bit of coding rather than relying on Apps to do the work
Step By Step Guide - Download link below
11/11/10 V2
http://www.multiupload.com/KK66WUNUWS
See the main thread for details on the root:
http://forum.xda-developers.com/showthread.php?t=805327

Evostance said:
I have just complied this Step-by-Step guide on how to root your Desire HD.
I by no means created the root, I simply used my own and others knowledge to put this guide together to help everyone.
Step By Step Guide
http://www.multiupload.com/1UFOZTBOZQ
See the main thread for details on the root:
http://forum.xda-developers.com/showthread.php?t=805327
Click to expand...
Click to collapse
hey evostance
why do we have two post? i mean adwinp already wrote one?
not saying your works unapperciated lol
could they not be merged to keep it all tidy? two posts that do the exact same thing in the exact same way?
anyways back to trying CWM

El_Nino9 said:
hey evostance
why do we have two post? i mean adwinp already wrote one?
not saying your works unapperciated lol
could they not be merged to keep it all tidy? two posts that do the exact same thing in the exact same way?
anyways back to trying CWM
Click to expand...
Click to collapse
There was a lot of people asking how to do it since they couldn't figure it out from adwinp's post and any advice was getting lost in the thread.
I just put my own work into a new thread so it was easy for people to find

And this method avoids terminal or adb so is a bit more beginner friendly I was going to wait for the visionary update tomorrow but now thanks to evostance's guide I have permaroot on the day it was found/exploited/invented.

jambamkin said:
I was going to wait for the visionary update tomorrow
Click to expand...
Click to collapse
is the new visionary will do the same work with one click ?

liorra3 said:
is the new visionary will do the same work with one click ?
Click to expand...
Click to collapse
Yes and No.
I don't know if VISIONary will just be able to root one Kernel Version, or if it will be able to modify the wpx.ko file depending on your Kernel Version.

awesome recap of how to permaroot!
Made a mirror of it here http://www.logarie.nl/android/Desire_HD_Root.zip

UNROOT ?
Excellent guide
Before I permanently root my DHD I want to know who would I UNROOT if needed (just in case if I want to send it off for repair)?

ATZ-007 said:
Excellent guide
Before I permanently root my DHD I want to know who would I UNROOT if needed (just in case if I want to send it off for repair)?
Click to expand...
Click to collapse
Run a stock RUU found on here

Excellent guide. Worked first time.

This is just awesome. I can't wait to get around to it

worked like a charm, thx @all who made this possible!! )
now for example adfree works as it should - bye bye ads!
Sent from my *permarooted* Desire HD using XDA App

This is a great guide thank you for taking your time to simply it.
I got to the step where I have to run wpx from the Gscript home screen and when I do run it I do not get the function error, all I get is a blue screen with the option to close it, Any idea what this means?
Thanks.

isopiso said:
I got to the step where I have to run wpx from the Gscript home screen and when I do run it I do not get the function error, all I get is a blue screen with the option to close it, Any idea what this means?
Thanks.
Click to expand...
Click to collapse
Reboot your phone and re-root it. I had the same issue.
Thanks for the guide, worked a treat!

insty said:
Reboot your phone and re-root it. I had the same issue.
Thanks for the guide, worked a treat!
Click to expand...
Click to collapse
Are we supposed to have run VISIONary before we run the scripts? The guide PDF doesn't say to run it until after, but the original forum topic says run it before... because I'm getting that blue screen that does nothing.
Edit: Okay I got it, maybe prefix the part about running the Gscrips with "Open VISIONary, tick "Run on Boot" and then click "Root Now!" before you continue to running the GScript actions.

You need sudo access before running GScripts.

I have longed for this day for 8 days now
Thank you so much.
Does this mean we can now push/pull to /system/app?

worked like a charm
many thanks to all involved

insty said:
Reboot your phone and re-root it. I had the same issue
Click to expand...
Click to collapse
you have full warrenty from htc even if you ulock the device, i sand to them 3 device that root and get my warrenty so...

scottastic88 said:
Are we supposed to have run VISIONary before we run the scripts? The guide PDF doesn't say to run it until after, but the original forum topic says run it before... because I'm getting that blue screen that does nothing.
Edit: Okay I got it, maybe prefix the part about running the Gscrips with "Open VISIONary, tick "Run on Boot" and then click "Root Now!" before you continue to running the GScript actions.
Click to expand...
Click to collapse
Ah of course. I will update the guide tomorrow
Sent from my Desire HD using Tapatalk

New to all this.

I have a SGS3 at home in the mail. I want to try rooting or whatever, do I have to root first or can I download the app that unlocks the bootloader and do that first? Can someone give a noob some advice and what steps I need to do? What does unlocking the bootloader do anyways?

bhags8 said:
I have a SGS3 at home in the mail. I want to try rooting or whatever, do I have to root first or can I download the app that unlocks the bootloader and do that first? Can someone give a noob some advice and what steps I need to do? What does unlocking the bootloader do anyways?
Click to expand...
Click to collapse
If you're new: start reading. Best advice.

Zalithian said:
If you're new: start reading. Best advice.
Click to expand...
Click to collapse
I have been, there's just stuff scattered everywhere. Trust me I know how to use search function, but I don't even know where to start. Do you unlock bootloader first or try rooting first?

bhags8 said:
I have been, there's just stuff scattered everywhere. Trust me I know how to use search function, but I don't even know where to start. Do you unlock bootloader first or try rooting first?
Click to expand...
Click to collapse
You root first. There are some guides stickied in Android Development.

bhags8 said:
I have been, there's just stuff scattered everywhere. Trust me I know how to use search function, but I don't even know where to start. Do you unlock bootloader first or try rooting first?
Click to expand...
Click to collapse
you root, unlock bootloader, install recovery (Clockwork mod non-touch seems to always be preferred) - after that you can contemplate installing custom roms, but I think installing recovery is just a good thing to do regardless.

sir/mam, I normally would have no problem helping a fellow member out, but I gurantee that I could go through the first page in each section of this forum and find all the answers/information one needs to get started. Point is your question has been asked 10 times alone today...so please spare us the "I already searched routine" because we all no you didnt!! /rant

droidstyle said:
sir/mam, I normally would have no problem helping a fellow member out, but I gurantee that I could go through the first page in each section of this forum and find all the answers/information one needs to get started. Point is your question has been asked 10 times alone today...so please spare us the "I already searched routine" because we all no you didnt!! /rant
Click to expand...
Click to collapse
I actually did. But there is no place where it tells me what I need to do in order. As well as giving advice. I'm only a member of like 14 different forums. I know how to search. And I didnt force you to click on this thread, did I? And thank you very much to poster above this person.

Start by rooting your phone with droidstyle's guide in the android dev stickies
Sent from my SCH-I535 using xda app-developers app

bhags8 said:
I have a SGS3 at home in the mail. I want to try rooting or whatever, do I have to root first or can I download the app that unlocks the bootloader and do that first? Can someone give a noob some advice and what steps I need to do? What does unlocking the bootloader do anyways?
Click to expand...
Click to collapse
I used this method to root successfully:
http://forum.xda-developers.com/showthread.php?t=1792342
I used this method to manually install CWM to my phone:
C:\android-sdk_r20-windows\platform-tools>adb push d2vzw_recovery.img /sdcard/
3233 KB/s (5681152 bytes in 1.716s)
C:\android-sdk_r20-windows\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/d2vzw_recovery.img of=/dev/block/mmcblk0p18
dd if=/sdcard/d2vzw_recovery.img of=/dev/block/mmcblk0p18
11096+0 records in
11096+0 records out
5681152 bytes transferred in 1.197 secs (4746158 bytes/sec)
[email protected]:/ # reboot recovery
reboot recovery
C:\android-sdk_r20-windows\platform-tools>

djrbliss releases AT&T S4 bootloader vuln.

I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki

this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.

spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom

its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...

shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.

Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with

fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have

alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.

just means soon we will have bootloader unlocked.... patience

lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.

Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET

TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.

fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.

fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:

Incoming update from Samsung in 3....2....1.....

I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!

mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.

fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.

mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.

Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

[kill write protection] MotoWpNoMo

Introducing MotoWpNoMo. The purpose of this application is to disable the pesky write protection on BL-locked motorola devices. After successfully running this application, you will no longer need to boot recovery or use other methods to temporarily remove write protection. This exploit is permanent in the sense it will survive factory resets, reflashing the device, etc. However, like with any exploit, you should not expect it to survive OTA's or other updates. This application will work with many motorola devices, however I'm only posting it here to keep the files and feedback consolidated (plus, I'm lazy). THIS IS NOT A BOOTLOADER UNLOCK, IT ONLY REMOVES WRITE PROTECTION. Let's get started....
Credits and terms:
beaups and fuses for MotoWpNomo application. jcase for root and gunnyman and brianr134 for testing. MotoWpNomo MAY NOT BE REHOSTED, REPACKAGED, INTEGRATED INTO A ONE-CLICK, BAT, SHELL SCRIPT, OR ANY OTHER APPLICATION. THE ONLY PLACE TO ACQUIRE THIS APPLICATION SHALL BE RIGHT HERE, IN THIS THREAD. THIS IS NOT OPEN SOURCE, DON'T ASK!
Pre-requisites:
1.) Working root (su). Jcase's methods are fully supported here
2.) Working adb and fastboot drivers. Yes, that means WORKING. Don't clutter this thread with driver issues
3.) Linux (32 bit) or windows
4.) Disable all firewalls/internet security/antivirus before running. This is the #1 issue encountered when running the application
Instructions:
Linux (preferred):
1.) download the application: motowpnomo
2.) extract the archive: tar -xf [filename]
3.) run the application: sudo ./wpbegone
4.) follow the on-screen prompts
Windows:
1.) download the application: motowpnomo
2.) extract the archive
3.) run wpbegone.exe as administrator
4.) follow the on-screen prompts
After the application is complete, you can verify with:
adb shell getprop ro.boot.write_protect
If you see "0", that pesky write protection is gone
Donations are appreciated and can be made to (paypal): [email protected]
support is available in #MotoWpNoMo on the freenode and andirc networks.

Wow... Sounds great.
So... What part of the phone is changed? How do you revert to stock?
Thanks!

Ctrl-Freak said:
Wow... Sounds great.
So... What part of the phone is changed? How do you revert to stock?
Thanks!
Click to expand...
Click to collapse
1.) a magical part
2.) you don't

It works! Thanks Beaups

Nice. Will try when I get home
Sent from my XT1058 using Tapatalk

If you are running this on a Mac in a VM, each time the phone reboots and the program is waiting for adb, unplug the phone and plug it back in once the phone is started up again or else the process will fail.

Sounds great but is there no way to get back to write-protected other then OTA? Will flashing the FXZ restore it?
Sent from my XT1049 using Tapatalk

would this work on the droid line up?

TheWhiteChallenger said:
would this work on the droid line up?
Click to expand...
Click to collapse
possibly. try it.

RobertsDF said:
Sounds great but is there no way to get back to write-protected other then OTA? Will flashing the FXZ restore it?
Sent from my XT1049 using Tapatalk
Click to expand...
Click to collapse
in what case would you want write-protection back? also, no, flashing FXZ will not restore it.

PERFECT!!! Hated that i couldnt write protect off even with an unlocked bootloader!! Now everything is fine!!! :good:

beaups said:
possibly. try it.
Click to expand...
Click to collapse
cool. i will. if it works ill let you know so you can setup a thread in the droid ultra/maxx forum if you would like
---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------
oh, so are you guys flashing your stock recovery back after this w/o issues?

TheWhiteChallenger said:
cool. i will. if it works ill let you know so you can setup a thread in the droid ultra/maxx forum if you would like
---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------
oh, so are you guys flashing your stock recovery back after this w/o issues?
Click to expand...
Click to collapse
Recovery will not affect this. If you get issue on other device, pm me. Should be able to add support.
Sent from my HTC6435LVW using Tapatalk

beaups said:
Recovery will not affect this. If you get issue on other device, pm me. Should be able to add support.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
ok ill let u know via pm, im trying something else right now if that works i should be able to tell you in a couple hours. and i was wondering if stock recovery could be re-flashed to re-enable a standard factory reset not to remove mod. so that should work right?

TheWhiteChallenger said:
ok ill let u know via pm, im trying something else right now if that works i should be able to tell you in a couple hours. and i was wondering if stock recovery could be re-flashed to re-enable a standard factory reset not to remove mod. so that should work right?
Click to expand...
Click to collapse
Yes you can flash stock recovery after this.
Sent from my HTC6435LVW using Tapatalk

Do you thing this would work on the Droid RAZR?

After running it said no su fu after rebooting su binaries weren't up to date and su couldnt fix. Ran adb and got the 0 so it worked then had to run a couple commands from the root thread and all is well again.

Ran into an issue and jumped in your IRC. Hopefully someone is around to help.

Code:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (4/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must play a little while longer...
it's so cold in here
hmm, hold please
..............................................
[*********************************************]
ERROR: looks like device is not rooted. su or FU!!!
[email protected] ~ $ adb shell getprop ro.boot.write_protect
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1
Any idea what would cause it to not work? If there's a way for me to pull a log of what failed specifically, I could probably be of more help.
VZW Moto X locked BL running 4.4.

Are you rooted?

Bricked my phone using Low Effort Root Method

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.