Related
How do you root the Thunderbolt after the 7/8/11 OTA?
Rooting using the old method doesn't work anymore?
flooritnfly said:
How do you root the Thunderbolt after the 7/8/11 OTA?
Click to expand...
Click to collapse
you would use the same process as before.
lostnuke said:
you would use the same process as before.
Click to expand...
Click to collapse
Yeah, use the same method. After your rooted, flash the rooted OTA stock Rom (google it) and also flash the its radio. That's what I did.
Sent from my rooted stock OTA MR2 Thunderbolt
So.... I can use this (http://forum.androidcentral.com/thu...unroot-windows-updated-5-20-w-mr1-update.html) like I did before then just flash the new radio that was released on 7/8 ?
Well now after 7/8, you have to flash while standing on your head. Yeah, its crazy like that.
bthomp21 said:
Well now after 7/8, you have to flash while standing on your head. Yeah, its crazy like that.
Click to expand...
Click to collapse
That is too funny.
I am unable to install the 7/8 Combo Radio package after installing DasBAMF Stripped 1.8.6
Constantly says "Installation Aborted."
Anyone else with this experience? I thought that I had read that this combo worked.
Got this sorted. I was using an MR1 package, not MR2, apparently. Using a different packaging of the OTA update flashed in via HBOOT.
BoulderGeek said:
I am unable to install the 7/8 Combo Radio package after installing DasBAMF Stripped 1.8.6
Constantly says "Installation Aborted."
Anyone else with this experience? I thought that I had read that this combo worked.
Click to expand...
Click to collapse
Your flashing it through the bootloader right? You can't use clockwork to flash it.
Sent from my rooted stock OTA MR2 Thunderbolt
Thunderbolt/Android Noob
OK .. I have this HTC Thunderbolt .. I want to root it .. I have read the forums up and down ... I saw the link above to AndroidCentral that shows how to root it, and one over in the Thunderbolt Development forum that says MR1 Perma Root ...
I would like to know the best route for me to go with minimal risk of bricking. I have flashed my wife's LG Ally a couple of times .. was easy enough, just ran an exe
All of the ones I have found for the thunderbolt seem to be a lot more complex. Is there a OneClick method I can run that will include the new radio (so i can get the latest fixes)?
If not, I am willing to go the ADB route (I have the Android SDK installed) but I dont know how to update the radio.
Thanks, and sorry to ask a question that seems to have already been answered, I am only asking b/c I did not understand your answers above ..
Use adb to root. Radio is done through hboot. Power off phone. Then hold vol key down and power on. Will bring you to hboot. Make sure radio is at root of SD card and is named properly. There is a sticky in the DEV section that will walk you through it.
courtesy of my rooted bolt
I just used the XDA development one. The key point is to read it carefully several times and be sure you understand each step. Ask questions beforehand if you are not sure about something. And be sure to follow each step exactly. Typos are the biggest risk, so go slow and read what you've typed on each line before hitting enter.
The radio file needs to be renamed to PG051IMG.zip and placed on the root of the SD card. Then power off and boot into bootloader. It'll load automatically after you hit +volume to confirm "yes ".
I had several flashes that resulted in the Exclamation Point warning triangle. Pulling the battery and USB cable and reinstalling power got me back to a running build.
It took me a while to do every step. I wanted to skip steps, not realizing that you needed the downgrade and RUU flashes to get S-OFF and unlock.
Once that was all done, I went to DasBAMF Stripped and found the OTA radio in this thread http://forum.xda-developers.com/showthread.php?t=1160346.
So far, so good. Calibrating battery now and trying to personalize and optimize to my best ability.
Ok so from what I gather there are no issues that would prevent any of the previous methods from working post 7/8 update? That includes the one click app thats been floating around for a few months right?
I've been holding off root for months, but my patience has finally run out, time to do what I should have done from the beginning.
EDIT
on second thought, I think I'll just do it the good old fashioned way
I did the 7/8 update, and was fine with it. I just wanted to get the Verizon bloatware off. I had problems installing the stock debloated ROMs, so i ran with BAMF to test, and since it worked, I kept it. My rooting came after the recent OTA.
The once-click and .bat methods didn't work so well for me, so I followed the full instructions in a CMD window (I can't call that POS in DOS a shell).
Most of my time was installing a correct Java JDK (had to use x86 instead of x64) and getting ADB dialled in.
KO'B said:
Ok so from what I gather there are no issues that would prevent any of the previous methods from working post 7/8 update? That includes the one click app thats been floating around for a few months right?
I've been holding off root for months, but my patience has finally run out, time to do what I should have done from the beginning.
EDIT
on second thought, I think I'll just do it the good old fashioned way
Click to expand...
Click to collapse
I had the same thinking and wanted it the quick and easy way. Doing the research and taking the time (and beers ) to do it manually was very informative and satisfying when i got done. It was said already but ive been able to apply any feature that an official OTA would give long before its normally released to verizon customers. I love my Tbolt and wouldnt have it any other way.
BryanB32 said:
I had the same thinking and wanted it the quick and easy way. Doing the research and taking the time (and beers ) to do it manually was very informative and satisfying when i got done. It was said already but ive been able to apply any feature that an official OTA would give long before its normally released to verizon customers. I love my Tbolt and wouldnt have it any other way.
Click to expand...
Click to collapse
Doing things the long way has never really scared me, but some of the horror stories I kept hearing a month or two back about instability of GB roms had me a bit hesitant to go for it.
It does appear to be a bit more involved than what I am accustomed to, but I have used ADB before, I was just trying not to this time.
Can someone give me a bit of advice actually.
I'm on the end of Step 4 found in the Developement section, and when I hit Bootloader, it brings up a second menu not mentioned in the posts, what do i do from here?
Nevermind once again, screwed up the name of the zip file
I used the auto root method 3 times so far and worked great. I did the full last update and lost root so I had to redo it load Rom and just added the radio file in hboot.
try auto root its fast and simple just follow the commands on the screen!
UPDATE: The latest update still is safe. I just installed it and I am still s-off.
UPDATE: The update to Jellybean does not write the secure flag and this method is safe to apply the OTA update with this method and still maintain root access afterwards.
First and foremost, a couple disclaimers.
FIRST, YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
SECOND, FOR THE OTA UPDATE 1.22.651.3 YOU WILL FOR SURE RETAIN S-OFF. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
To obtain s-off please see this thread: http://unlimited.io/jewel.htm
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup but was able to solve that.
So, here is the process. This is kind of a hodge podge of different threads, ideas, devices, and versions of android so if I didn't give you credit, please let me know and I will put you in this thread.
Process for installing a stock recovery. I have already created some stock recovery files so see at the bottom of this post for the zip file that includes the stock recovery. If you wish to use these files, just start with step #10.
IF YOU CHOOSE TO JUST DOWNLOAD THE STOCK RECOVERY AT THE BOTTOM OF THIS POST, SKIP TO STEP #10.
Creating Stock Recovery File Manually
1. Install a stock recovery if you don't already have one.
2. To do so, get the RUU for the version you are running.
3. Run the RUU (don't connect to your phone at all)
4. Navigate to your temp directory on your computer (on windows 7 it is C:\Users\your_user_name\AppData\Local\Temp)
5. Find a folder that looks like it is in the following format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" It might help to sort by date modified. The folder should have the current date
6. Inside the folder might be a couple other folders. Navigate through the folder to find a zip that says "firmware" or "rom" (mine said rom)
7. Extract the content to a folder in the same directory called rom
8. Navigate into the rom folder and find two files android-info.txt and recovery_signed.img. Copy those to a directory of your choice.
9. Send those files to a zip folder and name the file "PJ75IMG.zip" without the quotes. Make sure zip is only listed once. If you have file extensions hidden in windows yours will only say "PJ75IMG".
Installing the stock recovery, OTA, and regaining root
10. Place the stock recovery file on the root of your sd card
11. On your phone, head into settings and power and make sure the fastboot option is unchecked
12. Power down phone
13. Once phone is completely shut down, hold the volume down button and press the power on button while keeping the volume down button pressed.
14. It will boot into your hboot (verify it says s-off at the top or don't proceed) and find the file you placed on your sd card and ask you if you want to update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
15. Go to settings>check for updates and check to see if there is an update. Download the update. Once it verifies, click install now. It should install just fine.
16. Once you are up and running, download one of the dirty racun hboots. I used hboot 2.09 img found here. Follow the instructions on the unlimited.io website how to flash the hboot by using fastboot (flashing the zip doesn't seem to be working.
update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
17. Make sure usb debugging is checked under settings>developer options
18. Go download a su zip file. I used this one here and place it on the root of your sd card.
19. Go grab a custom recovery flashable zip (could not find the latest twrp zip) or img (I used TWRP found here. Take the image and place it in your platform tools folder for ADB.
20. Plug in phone while powered on and type in adb devices to make sure you are connected.
21. If you see a device type in
Code:
adb reboot bootloader
22. Your device will boot into your bootloader and you will see fastboot usb (make sure usb debugging was checked if you don't see that).
23. Then type fastboot flash recovery [filename] of the recovery img you downloaded. Once flashed, toggle with the volume up buttons to bootloader and then select recovery. This should boot you into TWRP
24. Once in recovery, install the su zip you downloaded in step 18.
25. Reboot and Enjoy!!!!
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. The only thing you will have to find is the current RUU to create the stock recovery. If this helped, feel free to thank! Go XDA!
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't know. So you don't have to wait at all? Or for the people that aren't accustomed to flashing ROMs or don't care to. I prefer this method for whatever reason and it seems just easier. Personal preference though. The beauty of android and their strong developer network is that it gives the users choices. I can take the OTA update as soon as it comes out and don't have to worry about waiting for anything. Just another method I guess.
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
msimindlessmsi2 said:
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
Click to expand...
Click to collapse
The update firmware is the part that hangs me up. I believe when it was back in the original EVO days that some people were having problems updating their PRI version and it screwed up some things with wimax. That is when I decided I would just accept the OTA to get everything they included in the update and then gain root access through this method.
Again, to each their own. Please try not to clutter up the thread with off topic items. Thanks.
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
im coming from the rezound, i just want the updated firmware! on my rez being s-off i could run ANY firmware ICS, or GB and then go back to whatever rom i was running. im wondering if im s-off, i should b able to do the same thing right.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
The devs state that so that they don't have to spend their valuable time troubleshooting because you didn't flash right. Its always best to do a full wipe, but not always required when flashing an updated version of the same ROM.
1) Nandroid.
2)Wipe Dalvik cache & cache
3) Flash
You retain all data.
If you have issues, then you nand restore and do a full wipe before bugging the devs
bpdamas said:
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out.
Click to expand...
Click to collapse
Lmao! You find that whole process "easier" than waiting for a day? I think it might take the better part of a day to do all that.
Sent from my EVO using xda premium
Thanks for taking the time to do a write-up OP!
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
Agreed.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Definitely agreed.
greyopaque said:
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
Click to expand...
Click to collapse
I know. This is exactly why I root and I can't believe there are so many people against this method. It seems very simple to me and I can have a stock recovery waiting to flash as soon as an OTA update comes out. Oh well.
Thanks for this info. I think I'm like you and not only like the stock experience and its benefits but also prefer diy when possible.
Of course I never seem to stay stock like you but I like doing the steps my self. To each their own is the beauty of android.
Go android!
Sent from my EVO
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
zounduser said:
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Click to expand...
Click to collapse
Very curious on this. Nothing in this method should affect this.
Robbie_G said:
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
Click to expand...
Click to collapse
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Rxpert said:
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Click to expand...
Click to collapse
That's fair, rooting and s-off could also inject malicious code. But so can ROM makers.
I think there's a difference between trying to be safe and being paranoid. If there is a way for someone to make money off of you/steal your identity, eventually they will try. I'm not suspicious of any of the current devs, but it's something we should maybe be more aware of. Look at all the warez Windows out there with malware built in to steal your information.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Totally agree. Its a good thing to learn in my opinion. I broke my Evo 4G, fixed it then rerooted it. Now on the 4G LTE got it rooted with custom rom. Love learning new things plus some of the good things that come with rooting and custom roms are worth it for me.
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Hi guys my girlfriend bought a LG Viper 4G LTE and she told me to root it to remove the sprint crap, so I was wondering if anyone has already done this and if yes, can they tell me how to s-off + root + custom recovery + and probably custom ROM.
If anyone can help, please I'll appreciate it. Since I searched here for that phone and is not even listed.
The phone is running android 4.0.4, is this ICS or Jelly bean?
I do not know how to get into fast boot boot loader cause I don't think it is POWER + VOL DOWN.
Thanks in advanced
Have a nice day
:what::what::what::what::what::what:
Sent from my Nexus 10 using Tapatalk HD
Im trying to root mine right now and can't seem to get it to work, I've tried Root_with_Restore_by_Bin4ry_v21 and LG-Viper-ICS-Root-tool with no luck. If i get it to run all the way though and reboot it still comes up without root and with no super user. I am starting to think I may have to find a way to downgrade it and root from there.....Did you ever have any luck?
Update:
Check out post 17 here
http://forums.androidcentral.com/lg-viper-4g-lte/253022-cannot-root-viper-ics.html
here is the link for LS840ZVI :https://docs.google.com/file/d/0BzPBX7oKPGLOcno0dFVNUXByMVE/edit
I've downgraded and rooted so far and its working, I may look for a rom before i upgrade again.
Confirmed above!
jared_schaefer said:
Im trying to root mine right now and can't seem to get it to work, I've tried Root_with_Restore_by_Bin4ry_v21 and LG-Viper-ICS-Root-tool with no luck. If i get it to run all the way though and reboot it still comes up without root and with no super user. I am starting to think I may have to find a way to downgrade it and root from there.....Did you ever have any luck?
Update:
Check out post 17 here
http://forums.androidcentral.com/lg-viper-4g-lte/253022-cannot-root-viper-ics.html
here is the link for LS840ZVI :https://docs.google.com/file/d/0BzPBX7oKPGLOcno0dFVNUXByMVE/edit
I've downgraded and rooted so far and its working, I may look for a rom before i upgrade again.
Click to expand...
Click to collapse
I can confirm that the above will work. I have a refurbished Viper from Sprint that I got because my 3G radio quit sending. It would receive great, but couldn't send any MMS or upload anything while on 3G. 4G was great, just no joy on 3G. Strangest thing. Anyway, got the phone replaced, and on the replacement was of course the dreaded unrooted ZVK. Gotta have my root back...
So I decided to try all this stuff out, and It worked.
To add a little further info, if you've got a relatively bare install of Windows, especially XP, you might need BOTH the VisualC++ Runtime Redistributables from 2010 (mentioned in the above thread) AND the one from 2008! If you don't have both, the LG FlashTool will not run. You can find them on Microsoft's site.
Once the flash tool has successfully downgraded your Viper, make sure you perform a factory reset, as indicated in the instructions for the FlashTool. Then use the "Activate" app to get your 3G/4G on. After that, set up your Google account under "Accounts and Sync" in "Settings".
I did the whole operation completely on a linux system, using a virtual machine running Windows XP for the FlashTool, then the bash script from here: http://forum.xda-developers.com/showpost.php?p=43530152&postcount=3253 with the v.31 rooting tool from the original post in that thread.
I had to edit the script in a very minor way, as was pointed out by its author, so it could find my adb command. I just placed the path to that command in the line that said:
Code:
for test_adb in "adb" "stuff/adb"
in the place of the first "adb", so I got:
Code:
for test_adb in "/home/user/android-sdk-linux/platform-tools/adb" "stuff/adb"
Make sure to replace "user" with your username, without the quotes.
Then I stuck the script in the same folder as the runme.bat file. After the script and root tool had done their work, my phone had rebooted a total of three times, and I had a perfectly functional Superuser app!
Huge thanks to LoveMyAndroid2010 in the post linked above. Great script - some love for linux!
Now to get RootKeeper and upgrade back to ZVK...
The aforementioned root method worked for me. Since I've rooted, I've compiled my findings into another thread. I haven't been able to unlock the bootloader yet, unfortunately.
how to upgrade LG Viper to Jelly bean or higher
After I root as per instructions, how can I upgrade the OS?
Please help. I'm a newbie and would appreciate any help you may offer. Haven't rooted any phone before.
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
doctor-cool said:
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
Click to expand...
Click to collapse
AdamOutler's Root is obsolete, Thanks for the good times
Click to expand...
Click to collapse
Adam has done A LOT for this community especially for Samsung phone in general.. His work is NOT obsolete and he still very involved on this forum. I am not friends with him or do I know him but he was the master mind behind unlocking/exploiting Verizons bootloader.. which currently on 4.3 and 4.4.3 is still not possible. This is most likely do to him not having the phone and the phones age..
SOo I hope I got the wrong impression from your statement.. Bc that man you mentioned.. Is a LEGEND.. Hands down
Just to confirm, Ghettoroot does not work on 4.4.2 baseband ND7. Is that correct?
Sent from my Galaxy Note 2 using Tapatalk
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
jtsmall said:
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
Click to expand...
Click to collapse
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Yes, that's it. Samsung's drivers work for me.
Sent from my Galaxy Note 2 using Tapatalk
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
crossing fingers
shissler said:
crossing fingers
Click to expand...
Click to collapse
woot woot im rooted..lol now what way to go
shissler said:
woot woot im rooted..lol now what way to go
Click to expand...
Click to collapse
I used it to replace the APN config file in my wife's phone for use on other carriers (T-Mobile & international use):
http://forum.xda-developers.com/showpost.php?p=57070787&postcount=7
It worked great for up to HSDPA+ speeds, but no LTE.. ..then she left the phone on top of her car; it fell off in traffic and got run over.. maybe this will help someone else!
Before it got smashed, I had planned on trying the following thread out next (for the VZW Note 3) to see if I could get LTE working on T-Mobile:
http://forum.xda-developers.com/showthread.php?t=2530523
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
samloves said:
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
Click to expand...
Click to collapse
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
zbomb5610 said:
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
Click to expand...
Click to collapse
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Thanks for the reply. I figured that was the case. I had 4.1.2 a few days ago also and figured "hey, i haven't updated in over a year" and didn't read into it enough and then upgraded to stock ota 4.4.2 so that sucks. I guess I can live with it like this for now till a fix comes out if one does.
also having trouble
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
UPDATE: Just got it to work. Will post soon what I was doing wrong and what I did to correct it.
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
IceCo1d said:
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
Click to expand...
Click to collapse
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
The part you are talking about does not come up until after the command prompt finds your device. Then you get the message to accept. That message came up the very first time but now it will not find the device for me to get to that part.
zbomb5610 said:
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
Click to expand...
Click to collapse
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
I had similar issues with some of my trials.. ...try turning developer mode off and on, plug in and then give the phone 30-90 seconds or so for installer mode to time out and verify the device is in MTP or PTP mode.
Just rooted my Note 2 running 4.4.2
Ok gang, so after about a week of trying every method to root my phone I finally got it to work. I'm going to tell you what I was doing wrong and what you can check to see where you are messing up. Hope this helps someone.
The issue I kept running into was that my device could not be found. I would run Ghettoroot and it would just tell me error device not found. This made no sense because I could get Kies to work and the bubble in the lower right corner that says installing device drivers would always succeed. However if I went into Device Manager (on the computer) there was a little yellow exclamation point next to my device. After looking in to the properties it said there were no drivers installed.
Also if you open a command prompt and type "adb devices" (with your phone plugged in) it should show you your device, if nothing comes up then the drivers are not properly installed.
So... First check that drivers are properly installed in your Device Manager (again this is on your computer), and then open a cmd window and type adb devices to see if your phone shows up. If it does then you are ready to use Ghettoroot.
I used this Ghettoroot:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
and the drivers I used were called:
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0 (I can't remember where I DLed it from, sorry)
Also, if you are interested. My method for figuring out what was wrong started by right clicking on the GhettoRoot .bat file to see the sequence cmd commands. They began with adb commands and I then googled to see how to check that the command would work. That is when I stumbled on the comman "adb devices" to make sure my phone was properly connected.
I hope this helps someone and if I can help in any other way just ask!
Heimdahl? Odin?
mattnmag said:
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Click to expand...
Click to collapse
I've only had this phone a week. My vs980 fractured :crying: now I'm stuck with this "thing" which I've done nothing with as I'm still trying to figure out WHAT never mind how. There's so much bloat I'm thinking AOSP. But how?
So far, ghetto-root hasn't worked for me but have removed Kaspersky etc to see if that was the problem. Then worry abt boot loader. Am on Pageplus Carrier so there wont be any OTA updates
Is there any merrit in the "Heimdahl" (??) method shown here CYANOGENMOD
I've read some of people using Odin to load pre-rooted stock image (and have found the images... but... )
I bricked the vs980 playing too fast and not waiting for answers. (learned a thing or 2 unbricking it)
So am I correct in understanding that you can no longer "Drop" an Un****** version of the factory image into the phone? By any means?
THANKS
VW