Related
Greetings,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I rebooted the phone. This morning, I tried to restore the superuser permissions by following the steps I found here on xda but after running the terminal script I rebooted my phone and when my phone wouldn't boot beyond the Google screen.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
I can't access clockwork recovery from the bootloader.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamaratee
__________________
Phone: Nexus
Rooted with problems
This post might help:
http://forum.xda-developers.com/showthread.php?p=9866675
It has the adb commands on how to replace the existing boot loader with cwm and all.
Hope it helps.
EDIT: If all else fails, you can try flashing a nandroid backup (2.3.3). This post would guide you:
http://forum.xda-developers.com/showthread.php?t=979851
Greetings Cygnum,
Thanks for the suggestion. I have a question: will these commands work on a Mac?
Thank you to AllGamer for suggesting that I post this question here and for the following suggestion:
AllGamer said:
please post the same question in QA or General, then we can all help you
PM is not the best place to ask for help.
The first thing to do is to download the full set of Android SDK 2.3+ for MAC
then we'll continue from there.
Click to expand...
Click to collapse
How do I proceed AllGamer? I downloaded the mac SDK from here (http://developer.android.com/sdk/index.html).
Follow steps 1-7 from here to get back Clockwork Recovery.
http://forum.xda-developers.com/showthread.php?t=878446
If your bootloader is already unlocked, you can skip those steps.
Do steps 8-9 to copy this file over to your USB drive.
http://devsforandroid.com/ip.board/index.php?/files/file/94-stock-deodexed-233-voodoo-rooted/
This rom is Master's Stock 2.3.3 ROM that is already rooted which should get you up and running.
Unmount, go back. Wipe system data, wipe cache. Go to advanced, Wipe Dalvik-cache.
Go back, choose to install zip from SD card. Locate Master's stock ROM. Flash that.
In the end, you'll have a stock deodexed rom that is rooted. Keep in mind that you will lose all your data, but that at least puts you back on track.
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
peeturr said:
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
Click to expand...
Click to collapse
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Yeah my bad. Just whatever had worked for me. Pretty new to mac myself.
Sent from my Nexus S using XDA App
krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
kenvan19 said:
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
Click to expand...
Click to collapse
No. ~/ specifies your home directory
Thanks Everyone
Thanks for all the suggestions and help I received. I PM'd KenVan and he provided me with the script and my Nexus S is up and running.
I just had this problem on the weekend I could not get past the lockscreen so I flashed cyanogen nightly and bam booted fine
Sent from my Nexus S using XDA App
Problem Solved Over the Weekend
Thanks for the help everyone. I posted this in a couple places, so I forgot to update this thread.
I fixed the problem with detailed steps from KenVan. Thanks again though to all of you for your suggestions.
HTC Thunderbolt Windows One Click Root
This is a simple batch file that will guide you in rooting your device.
It is pretty easy to follow along but please take your time and read everything. It has only been tested a few times so please report any errors or issues you find.
Huge thanks to NetForce-TX on IRC for testing along with helping, I owe you!
Also thanks to Jcase for guidance
TeamAndIRC and Captainkrtek (Me) are NOT responsible for any bricks, fires, or damaged/broken hardware due to this process
If you wish to read the batch files contents either open it with notepad or check the pastebin
Instructions are included in the file when running it along with where to get the necessary files.
Prerequisites:
Drivers Installed & Working
SDK Installed with ADB
Exploits.zip with contents extracted to your ADB dir
PG05IMG.zip
Downgrade RUU
A Thunderbolt running 605.6 or 605.9 Firmware
You can download the OneClickRoot here
I will update this from time to time if needed, If you have issues with the batch file please PM me on XDA or find me on irc.andirc.net #Thunderbolt.
I will not reply to your PM if you want me to help you root your phone!
UPDATE: If SU acts up (IE: Force closes) flash this via CWM
Reserved for Linux version
Wow, looks easy! But I'm glad I did it through ADB. Nice job!
pinhead875 said:
Wow, looks easy! But I'm glad I did it through ADB. Nice job!
Click to expand...
Click to collapse
Thanks! It is pretty simple, only a few things you have to do manually (no possible workaround) such as flashing from the bootloader.
Anyone try this yet?
sent using Tapatalk on the TB.
egeorgia said:
Anyone try this yet?
sent using Tapatalk on the TB.
Click to expand...
Click to collapse
Already a few people have tested it, all successes
so we set the phone to debug mode and the usb mode to just charging?
i was going to to the other root ;set up my ADB earlier but chickened out... i already have the files downloaded
Cg006 said:
so we set the phone to debug mode and the usb mode to just charging?
i was going to to the ot her root and set up my abd earlier but chickened out... i already have the files downloaded
Click to expand...
Click to collapse
Yeah exactly, just debug and charging, until you have to copy over the roms then you will set the USB mode to mount SD
I did the long method but I missed the step to get s-off. Can I still use the one click root method sk I can obtain s-off?
alphatectz said:
I did the long method but I missed the step to get s-off. Can I still use the one click root method sk I can obtain s-off?
Click to expand...
Click to collapse
Yes you can, but I reccomend unrooting whatever you have done so far using this http://forum.xda-developers.com/showthread.php?t=1009423
Captainkrtek said:
Yes you can, but I reccomend unrooting whatever you have done so far using this http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Ok, I'll unroot and use the one click method. Thx
can we get a poll maybe to see success rate
Can we get a Step by Step Instruction Guide? it would be nice for us beginners
ok so after i choose my path where my android sdk platform tools folder is i get
Pushing files via ADB...
This process may take some time, if it takes longer than 30 seconds
Make sure the drivers are install and USB debugging is on.
cannot stat 'psneuter': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'misc.img': No such file or directory
Unable to chmod /data/local/psneuter: No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
so what did i do wrong? i get my serial number when i get type adb devices....
b33zy682 said:
ok so after i choose my path where my android sdk platform tools folder is i get
Pushing files via ADB...
This process may take some time, if it takes longer than 30 seconds
Make sure the drivers are install and USB debugging is on.
cannot stat 'psneuter': No such file or directory
cannot stat 'busybox': No such file or directory
cannot stat 'misc.img': No such file or directory
Unable to chmod /data/local/psneuter: No such file or directory
Unable to chmod /data/local/busybox: No such file or directory
so what did i do wrong? i get my serial number when i get type adb devices....
Click to expand...
Click to collapse
You need to put the contents of exploits.zip in the same directory ADB is in
ok what in that zip needs to go where?
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
b33zy682 said:
ok what in that zip needs to go where?
Click to expand...
Click to collapse
take everything that is in exploits.zip and move it to your android sdk directory specifically the location of adb.exe (will either be in platform-tools or tools) as for the two RUUs, they can be anywhere but you will have to move them at one point to your SD card. That is about it
Cg006 said:
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
Click to expand...
Click to collapse
Yes you should
Cg006 said:
Phone Has been Succesfully Rooted.
Did most of the steps while doing some WoW Raiding. lol
Thank you so much.... now.. should i flash a new rom on this baby?
Click to expand...
Click to collapse
damn right! lol
Accidental OTA on custom rom. I have tried other posts but nothing works so far. Can someone please help.
Does the phone turn on and show LG?
Sent from my LG-VS980 using Tapatalk
lilxman said:
Does the phone turn on and show LG?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
What happens when you use anything in CWM?
SmurFFF said:
Accidental OTA on custom rom. I have tried other posts but nothing works so far. Can someone please help.
Click to expand...
Click to collapse
the link below will allow you to revert back to stock unrooted 11A.
after that you can take the OTA to 12B, reroot via IORoot and then use FreeGee to install recovery of your choice.
This has saved my phone a couple times from me getting too cocky with screwing around with things i don't fully understand but think I do.
http://forum.xda-developers.com/showthread.php?t=2448960
no download mode
WolfmanJack said:
the link below will allow you to revert back to stock unrooted 11A.
after that you can take the OTA to 12B, reroot via IORoot and then use FreeGee to install recovery of your choice.
This has saved my phone a couple times from me getting too cocky with screwing around with things i don't fully understand but think I do.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
cant boot into download mode
lilxman said:
Does the phone turn on and show LG?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
it boots straight into cwm usually, sometimes stuck in lg logo
Hmm OK. At work now, I will look into it when I get home. Just throwing this out there cause it caught me, you just press the volume up button, hold it down, then plug in the USB cable with the LG flash tool open and configured. I kept holding the power button down as well.
Sent from my LG-VS980 using xda app-developers app
staticx57 said:
What happens when you use anything in CWM?
Click to expand...
Click to collapse
i tried flashing new rom but says loki not supported or something
WolfmanJack said:
Hmm OK. At work now, I will look into it when I get home. Just throwing this out there cause it caught me, you just press the volume up button, hold it down, then plug in the USB cable with the LG flash tool open and configured. I kept holding the power button down as well.
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
how do i log into flash tool
SmurFFF said:
how do i log into flash tool
Click to expand...
Click to collapse
Reread the thread there is a file you need to replace that corrects that. Uninstall it, reinstall, replace the file and then attempt to open.
WolfmanJack said:
Reread the thread there is a file you need to replace that corrects that. Uninstall it, reinstall, replace the file and then attempt to open.
Click to expand...
Click to collapse
still no download mode
SmurFFF said:
still no download mode
Click to expand...
Click to collapse
Ok man here ya go, did some digging around here and found these two threads that may help you.
First is a means of pushing TWRP via ADB, not sure if that is the answer for you by you never know till you try.
Second is a means of using Ubuntu or a VM to replace the corruption caused by OTA
http://forum.xda-developers.com/showthread.php?t=2449670
http://forum.xda-developers.com/showthread.php?t=2582142
If those do not work either the only other thing I could think to do would be to get on the lg-g2 IRC channel and request help from a dev that is online.
WolfmanJack said:
Ok man here ya go, did some digging around here and found these two threads that may help you.
First is a means of pushing TWRP via ADB, not sure if that is the answer for you by you never know till you try.
Second is a means of using Ubuntu or a VM to replace the corruption caused by OTA
http://forum.xda-developers.com/showthread.php?t=2449670
http://forum.xda-developers.com/showthread.php?t=2582142
If those do not work either the only other thing I could think to do would be to get on the lg-g2 IRC channel and request help from a dev that is online.
Click to expand...
Click to collapse
i have never done an adb before is there any way u could help
SmurFFF said:
i have never done an adb before is there any way u could help
Click to expand...
Click to collapse
There is a pretty detailed guide somewhere on the forum. I will locate it, read through it and add to it if need be bro.
WolfmanJack said:
There is a pretty detailed guide somewhere on the forum. I will locate it, read through it and add to it if need be bro.
Click to expand...
Click to collapse
thanks sorry about all the questions
SmurFFF said:
thanks sorry about all the questions
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2141817
No worries on the questions man, here is the guide I was talking about. It is pretty straight forward but some areas you may have questions I will let you know what I did.
At one point it talks about setting up system variables or something to that effect. I did not perform this step.
When you open the SDK manager and look at all the packages that are listed it can get a little confusing, for me I just selected all and let the install run it's course. ( took about 20mins ).
Once the install is good it talks about moving a copy of command prompt to the platform tools folder. Not trying to insult your intelligence but it is that simple. Just locate where the .exe for command promt on your computer is, copy it and paste in the platform tools folder.
Once that is done turn your phone on and then plug the phone into your computer. Open the command prompt from the platform tools folder and then type the following:
adb devices
it should populate some brief info about your phone. If not then usb debugging is not enabled on the device. This is why I think this one may not work for you because if it isn't already enabled not sure if there would be a way for you to enable it with the state your device is in, but there are two other ways in the TWRP guide that i already posted about that may work plus the second thread talking about using ubuntu.
WolfmanJack said:
http://forum.xda-developers.com/showthread.php?t=2141817
No worries on the questions man, here is the guide I was talking about. It is pretty straight forward but some areas you may have questions I will let you know what I did.
At one point it talks about setting up system variables or something to that effect. I did not perform this step.
When you open the SDK manager and look at all the packages that are listed it can get a little confusing, for me I just selected all and let the install run it's course. ( took about 20mins ).
Once the install is good it talks about moving a copy of command prompt to the platform tools folder. Not trying to insult your intelligence but it is that simple. Just locate where the .exe for command promt on your computer is, copy it and paste in the platform tools folder.
Once that is done turn your phone on and then plug the phone into your computer. Open the command prompt from the platform tools folder and then type the following:
adb devices
it should populate some brief info about your phone. If not then usb debugging is not enabled on the device. This is why I think this one may not work for you because if it isn't already enabled not sure if there would be a way for you to enable it with the state your device is in, but there are two other ways in the TWRP guide that i already posted about that may work plus the second thread talking about using ubuntu.
Click to expand...
Click to collapse
Ive done everything it said but i cant get it to recognize adb as a command
SmurFFF said:
Ive done everything it said but i cant get it to recognize adb as a command
Click to expand...
Click to collapse
Does it say:
"adb" is not recognized as an internal or external command, operable program or bath file
If so the command promt isnt executing from the platform tools.
attatched is a screenshot of two CMD windows, look at the location listed before where what you type in shows up.
the location on the left is from the cmd opened from the platform tools folder, the one on the right is from opening up command prompt from where it is originally located on my computer. when you open yours compare the locations and let me know what you got.
WolfmanJack said:
Does it say:
"adb" is not recognized as an internal or external command, operable program or bath file
If so the command promt isnt executing from the platform tools.
attatched is a screenshot of two CMD windows, look at the location listed before where what you type in shows up.
the location on the left is from the cmd opened from the platform tools folder, the one on the right is from opening up command prompt from where it is originally located on my computer. when you open yours compare the locations and let me know what you got.
Click to expand...
Click to collapse
im on windows 8 and when i try to find the cmd application i only get a shortcut?
not sure if it differs in windows 8 or not but I know i 7 and older versions it is located C:/windows/system32
also when you copied it did you select paste shortcut or just paste? If you selected paste shortcut that may be your issue, i selected paste and it populates as its own .exe not a short cut. Let me know what you get.
Hi everyone. As I found out there's root for the G4 but doing this isn't easy especially if your variant is hard to find or has less users. This may result in you waiting for longer than you should. This thread is for those who can take things into their own hands and do it themselves. The tools are available everywhere but I'll give you the best order and steps. I'm using the China LG G4 H818 Dual SIM variant but this method is UNIVERSAL FOR ALL LG G4s.
The process will involve extracting a system image, injecting root and reflashing this image. Most of the steps are effortless and need just copy and paste with keen eyes. Do it slowly. You need an Ubuntu installation for step 2 of this 3-step tutorial. I used universal USB installer and put in on my 8GB USB. Anywhere will do so far as it boots&works. Beware this thread is not dumb-proof but this will not wipe your data or void your warranty if done successfully.
Step 1 -> Getting the proper system image.
Check here and skip to step 3 if you have your rootedsystem.img
>Don't worry because this doesn't require searching. It is from your device. Every device has a system partition and this method will pull it out as an image without root required.
1--Make sure all drivers are installed properly. I'll not be talking about this. We're on XDA not kindergarten.
2--Download the LG_root file or send command file from here and extract it. US Carrier specific check here
3--Put your device in download mode and connect it to your PC.
4--Open(double-click duh) port.bat and make sure to write down the number after com. There maybe different com numbers but choose the com on the DIAG1 line and write down that number. This is important.
5--Hold shift and right-click in any empty space in the extracted folder. Choose open command windows here.
6-- In that copy and paste this
Code:
[FONT=Lucida Console][COLOR=#ff8c00]Send_Command.exe \\.\COM[/COLOR][COLOR=#00ff00][*insert your number here][/COLOR][/FONT]
7--Now you're in send command mode. Nothing looks different on your phone but that's ok. It should just remain in download mode.
8-- On the computer screen in the window you now see #.
9--Now in this post copy the Backup system to internal storage command specific to your device model number. Check in you settings >general >about if in doubt. This is the most important step. Copy the whole line of code. Highlight with your mouse, select everything on the line and copy.
10--You didn't come all this way to fail so do it. Remember it is device model specific.
11-- Paste it in the command window and hit enter. It should take a while so wait until you see#reappear.
12--Now typeLEAVEall in capital letters. Your device will reboot. Check using the file manager if you have a file called system.img in your internal storage. If yes step 2 is next and you did well. If no repeat it and follow the steps properly. Make sure drivers are installed especially windows 10/8/8.1 users. Check device manager
Step 2 -> Root injection.
1--Prepare your Ubuntu USB or virtual machine or computer.
2--Download inject_root zip from here and extract.
3--Copy the system.img from your phone to the extracted inject_root folder on your PC.
4-Reboot into Ubuntu.
5--Here open a terminal.
6--Gain root access on Ubuntu by typing or copy and paste sudo -i
7--You should either be asked for your password which you have to enter or if you used a USB drive like me you'll see the name change to[email protected]
8--Navigate to the inject_root folder by using cd commands. This can also be done by typing cd then [space] then dragging and dropping the folder into the terminal and hitting enter.
9--You'll now see the name in the terminal become longer with the name of the folder in it.
10--Now type chmod +x autoroot.sh
11--Hit enter then sudo ./autoroot.sh
12--If you get any thing like command not recognized or something of the sort use sudo sh autoroot.sh
-That worked for me.
13--If you're successful the name of the file should change from system.img torootedsystem.img
-Please note don't rename the files. Leave them as they are.
14--Now go back to Windows let's finish this.
Step 3 ->Root
1--Transfer the rootedsytem.img to your phones internal storage.
2--Put your phone in download mode and connect it to your PC.
3--Get into send command mode as in step one.
-Put your device in download mode and connect it to your PC.
-Open port.bat and make sure to write down the number after com. There maybe different com numbers but choose the one that has DIAG1 on the same line as it. Note it down this is important.
-Hold shift and right click in any empty space in the extracted folder. Choose open command windows here.
- In that copy and paste this
Send_Command.exe \\.\COM[*insert your number here]
-Now you're in send command mode. Nothing looks different on your phone but it's find. It should just remain in download mode.
4-Now grab your command to flash system.img line of code from this post. It isn't the same as step one. Copy that an paste in the command window. Make sure it is for your device. They are model specific.
5--This should take a while so wait until you see the # again.
6--After thatLEAVEand upon reboot you should have root.
To Un-root just flash a KDZ file compatible with your device here.
Testimonies
Spudnubs said:
Rooted H812 10g for my fellow Canadians. Enjoy!
https://www.androidfilehost.com/?fid=24052804347821979
Click to expand...
Click to collapse
Wildsheep said:
This root method works for my G4 purchased in Singapore (H815 SEA)
Click to expand...
Click to collapse
luongquang said:
Thanks to @hackarchive, H818p10f done with tut.
Click to expand...
Click to collapse
player911 said:
Fantastic. This method will also ease devs for future rooted firmwares. I really cannot see LG being able to patch this, since this is basically a 3rd party LG Flashing tool. If they block this method, then their own tool will ultimately die with it.
Click to expand...
Click to collapse
GavTheStoner said:
Fantastic! I had almost given up hope of root on my EE LG G4. Have just used this method and now rooted perfectly!
hackarchive You rock! Have a thanks!
Click to expand...
Click to collapse
articular said:
everything worked fine and i successfully got my g4 rooted
my variant is H815TR
all steps easy only the ubuntu part was a bit hard especially for a windows user ( finding an ubuntu version and usb install etc. not root injection part)
ty ty ty again )
Click to expand...
Click to collapse
rirozizo said:
if it were for me to decide if we should delete the low effort root method, i'd totally delete it.
"The more 'manual', the better"
Click to expand...
Click to collapse
Moe5508 said:
Only method that roots my device successfully...I updated to 10e of the H815P and using this method (and only this!0 I was able to root my phone...ah felt so good...
The other 1-click rooting methods I came across in other parts of this forum just fail on the G4...
Click to expand...
Click to collapse
Marshmallow and root situation read here
Hit thanks if you appreciate. Hope I helped.
Credits to them whom without this won't be possible :good:
Thecubed
Team Codefire
ManhIT
This is a good method, thanks for writing this up.
I would like to add a few points....
I recommend you do keep your original system.img on your phones regular internal storage. If you encounter any boot issues you can then re-enter download mode and write the original system.img over the top of the failed root attempt. Use the same command from "step 3: root" but replace rootedsystem.img with system.img. This should still be on your phone from step 1 and will recover your phone from a failed root injection attempt. Note that it will not recover your phone if you messed up the dd command and overwrote other partitons. Be sure to use the right dd command and cut n paste to prevent seek/offset typeos.
I also recommend that you keep a backup of your system.img on your pc. When you run autoroot.sh in step 2 the copy on your pc will be renamed and patched. I suggest copying system.img somewhere else first, or re-copy it off your phone.
Additional credits to blog.lvu.kr. This is the blog of the hobbyist who reverse engineered the download mode protocol, created send_command.exe and gave it to the world. Kudos to you.
How is this any easier than the original method....if anything this requires even more work
kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
It's for those who have rare variants.
psycho_asylum said:
It's for those who have rare variants.
Click to expand...
Click to collapse
Then you should probably take out the claim that this method is easier from the OP
Can this be used to inject Xposed as well for those of us with locked BLs.
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
No, we need to wait for a custom recovery.
psycho_asylum said:
No, we need to wait for a custom recovery.
Click to expand...
Click to collapse
Just used flash fire it worked rocking xposed now on 810!
djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
Oh nice! I wasn't adventurous enough to try it. I'll make a system backup and give it a whirl!
Very nice thread, thank you. The steps were short, few, and fairly concise.
I was waiting for something like this where I could modify my own image and I wouldn't have to wipe everything or replace it with a new image.
One thing you might want to mention is that if your phone is encrypted, you'll need to unencrypt it first.
Can anyone link me to some instructions on how to disable OTA updates for an unlocked/international H815T?
kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
the_scotsman said:
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
Click to expand...
Click to collapse
Thanks. I guess people don't know what XDA is about. Seeing noobs and others trying to spit on hard work when I used my time and device as Guinea pig. Also people don't know this is almost brick-proof because the system image if from their devices. Unless they use wrong commands but all here is just copy and paste. They see lot's of text and get cold feet. Anyways will be updating the OP with system images. If yours is available please share. If you see your image available and you have drivers and LG_root downloaded proceed to step 3.
The only downside is that I have to drag out my windows laptop instead of doing everything on the ubuntu machine I use at work.
But if that's the biggest of my problems then I don't really have a problem
hi, thx for this tutorial, looks good
when flashing back the rooted img,does it wipe everything ? apps, data ... etc
thx
EDIT: just correct me if im wrong
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
must make sure before i go ahead
thx
How to calculator extractly bs/seek/count ?
Is there a possibility of any personal data being written to /system on a phone during normal use? I can provide 10c Optus AU (carrier 505-02) if I can be sure its not identifying, but ive been using the phone a couple of weeks.
Download link:
https://www.androidfilehost.com/?fid=24052804347799013
optiplex2012 said:
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
Click to expand...
Click to collapse
correct.
---------- Post added at 06:01 PM ---------- Previous post was at 05:29 PM ----------
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
HTCuser90 said:
How to calculator extractly bs/seek/count ?
Click to expand...
Click to collapse
I would also like to know this. You can resolve system by running the following. Note that this is for the H815T and is not the same on all variants.
# ls -lZ /dev/block/bootdevice/by-name/system
You'll get something like:
lrwxrwxrwx root root ubject_r:block_device:s0 system -> /dev/block/mmcblk0p47
Which tells you the actual block device (partition its on).
And you can see the size of that with:
# cat /proc/partitions
where you see:
major minor #blocks name
<snip>
259 15 4239360 mmcblk0p47
<snip>
However I dont know how to identify how large a block is or how to calculate the start offset in the main partition.
ok, it worked great
wasnt easy, since im not so familiar with using ubuntu, but all is ok
the explanation of the how to... was great and nothing lost
my H815L is now rooted
thx guys
djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
I know it's kind of going off topic, but I figured I'd mention that Flash Fire doesn't work on VS986. It just goes to a black screen and sits there forever. I left it sit for almost an hour. I saw elsewhere it has something to do with automount, I'll have to mess with it further.
hackarchive said:
Hit thanks if you appreciate. I spent hours trying to root so hope I helped.
Click to expand...
Click to collapse
Appreciated but you should include a way to unroot (undo) as well, ie how do we get back to stock (if required) ?
Okay guys first off sorry if there's a thread for this but XDA has become so over crowded and full of comments it's just to much to read through and try to remember. But anyway
Can anyone point me in the right direction or simply explain real quick how to properly root the T-Mobile variant. I'm running full stock (Obviously) I'm on H91810j and would like to debloat a little and use greenify. Any help is appreciated.
StonerSteve420 said:
Okay guys first off sorry if there's a thread for this but XDA has become so over crowded and full of comments it's just to much to read through and try to remember. But anyway
Can anyone point me in the right direction or simply explain real quick how to properly root the T-Mobile variant. I'm running full stock (Obviously) I'm on H91810j and would like to debloat a little and use greenify. Any help is appreciated.
Click to expand...
Click to collapse
There is literally speaking a thread dedicated just for the sake of rooting and twrp lol. Here:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
It should take about 3 to 5 minutes to complete the whole process if you know what you are doing. If you are a noob it might take sometime to figure out were to go from one step to another
Also, just remember, there is a search function on the v20 section's main screen. You can always use keywords and the function will search what you are looking for (if someone has posted something related to That). As French prople says... "Bon chance|"
P.s: yes. The rooting method by jcadduono works for 10j
jinkerz9430 said:
There is literally speaking a thread dedicated just for the sake of rooting and twrp lol. Here:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
It should take about 3 to 5 minutes to complete the whole process if you know what you are doing. If you are a noob it might take sometime to figure out were to go from one step to another
Also, just remember, there is a search function on the v20 section's main screen. You can always use keywords and the function will search what you are looking for (if someone has posted something related to That). As French prople says... "Bon chance|"
P.s: yes. The rooting method by jcadduono works for 10j
Click to expand...
Click to collapse
ive downloaded everything and when i extract the adb fastboot it extracts just fine but when i go to run it as administrator a box opens then closes immediately. what am i doing wrong
StonerSteve420 said:
ive downloaded everything and when i extract the adb fastboot it extracts just fine but when i go to run it as administrator a box opens then closes immediately. what am i doing wrong
Click to expand...
Click to collapse
Oh. The adb i used was from a pixel thread... The one posted in the rooting thread seems to either be missing a file called lib.... Something i forgot the name lol; or they did open and close immediately like it happened to you.
jinkerz9430 said:
Oh. The adb i used was from a pixel thread... The one posted in the rooting thread seems to either be missing a file called lib.... Something i forgot the name lol; or they did open and close immediately like it happened to you.
Click to expand...
Click to collapse
Can you link me to the adb you used. It just keeps opening and closing.
StonerSteve420 said:
Can you link me to the adb you used. It just keeps opening and closing.
Click to expand...
Click to collapse
Let me see if i can find it. If not i will zip it and send it to you
jinkerz9430 said:
Let me see if i can find it. If not i will zip it and send it to you
Click to expand...
Click to collapse
Thank you
StonerSteve420 said:
Thank you
Click to expand...
Click to collapse
Well. I couldnt find it. Anyway, i made a zip with all the files. Here:
View attachment 4070081
jinkerz9430 said:
Well. I couldnt find it. Anyway, i made a zip with all the files. Here:
View attachment 4070081
Click to expand...
Click to collapse
Still doing it. I must be the one person who's screwed lol
StonerSteve420 said:
Still doing it. I must be the one person who's screwed lol
Click to expand...
Click to collapse
Have you tried to run it in administrative mode?
jinkerz9430 said:
Have you tried to run it in administrative mode?
Click to expand...
Click to collapse
Right click run as administrator? Yes I have. Still can't get this to work. I'm using WinRar idk if that's the culprit or not. It's always been reliable.
Here, use this.
https://forum.xda-developers.com/showthread.php?t=2588979
Best for noobs.
It it asks about system wide say yes.
Then hit Windows key and R and type cmd. Then run your commands. The installer should also work.
StonerSteve420 said:
Right click run as administrator? Yes I have. Still can't get this to work. I'm using WinRar idk if that's the culprit or not. It's always been reliable.
Click to expand...
Click to collapse
Wait. I forgot to tell you. You cant double click the files. The files can be accessed only by using cmd. (command promt). So, extract the files into a folder, and use cd or pushd in dorect it to the directory where the files are. That is the proper way.
jinkerz9430 said:
Wait. I forgot to tell you. You cant double click the files. The files can be accessed only by using cmd. (command promt). So, extract the files into a folder, and use cd or pushd in dorect it to the directory where the files are. That is the proper way.
Click to expand...
Click to collapse
I know what you mean but how does the command go. I know I have to type something then add the file name sorry like I said I'm used to the old way maybe use adb for one step then the rest does it itself lol trying to catch up
StonerSteve420 said:
I know what you mean but how does the command go. I know I have to type something then add the file name sorry like I said I'm used to the old way maybe use adb for one step then the rest does it itself lol trying to catch up
Click to expand...
Click to collapse
For starter... Whats the directory where you downloaded and extracted adb fastboot? Assuming you are using the file i sent you. Was it on the downloads directory? If so open cmd (not in administratibe mode) and type pushd Downloads . Then ise all the start the adb server by using adb start-server to recognize your device. Or if you want to even see if your device is even present type adb devices
jinkerz9430 said:
For starter... Whats the directory where you downloaded and extracted adb fastboot? Assuming you are using the file i sent you. Was it on the downloads directory? If so open cmd (not in administratibe mode) and type pushd Downloads . Then ise all the start the adb server by using adb start-server to recognize your device. Or if you want to even see if your device is even present type adb devices
Click to expand...
Click to collapse
I have it in a folder on the desktop. So I type pushed Desktop/(folder name)? Or can it not be in a desktop folder. Sorry your spelling is confusing me with the second part how do I start adb server? Do I type adb start-server? Thanks for helping it's greatly appreciated
StonerSteve420 said:
I have it in a folder on the desktop. So I type pushed Desktop/(folder name)? Or can it not be in a desktop folder. Sorry your spelling is confusing me with the second part how do I start adb server? Do I type adb start-server? Thanks for helping it's greatly appreciated
Click to expand...
Click to collapse
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
jinkerz9430 said:
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
Click to expand...
Click to collapse
Thank you. I'll try that when I get home.
jinkerz9430 said:
You could use the desktop but it is more troublesome to type the directory. Thats why i suggest to put it on the downloads folder and asked you to not start the cmd as administrative. Because when you dont start it as administrative, cmd will start right from the users folder and then is only a matter of writting pushd Downloads. Focus on the first part first. Otherwise you will go nowhere lol.
Click to expand...
Click to collapse
Okay I got into the download folder using cmd (pushd download) i tried doing adb and hitting enter after and it brought up a bunch of lines after that. I did adb devices and it shows my phone but when I do fastboot oem unlock it just hangs at waiting for devices. USB debugging is on and so is OEM unlock.
StonerSteve420 said:
Okay I got into the download folder using cmd (pushd download) i tried doing adb and hitting enter after and it brought up a bunch of lines after that. I did adb devices and it shows my phone but when I do fastboot oem unlock it just hangs at waiting for devices. USB debugging is on and so is OEM unlock.
Click to expand...
Click to collapse
but are you in fastboot mode now? because after you have done the OEM unlock and then after that use usb debbugging then accept the prompt it shows about giving authorization to your computer, then after that you must go to fastboot mode to start the process of root