Related
I guess I need to brush up on my phone modding skills because I haven't had to root/unlock/modify a phone for a while now as you can see I'm on a D2 and had an INC1 before that, I've messed with a NC and a Touchpad on the tablet side, all of these procedures seem simple and straight forward with few steps or lots of simple steps.
With my Rezound coming on Friday, I realize I'm a bit out of touch on things, when I hear about renaming files to x or y, using fastboot, boot.img, or flashing recoveries separately (including using Amon Ra, which I've never used) I'm quite confused.
I would appreciate if someone could lay it out for me a little more simplier for me or am I just overthinking?
-Sent from my Droid 2-
Yeah, I can see how reading posts in here at this time could be confusing. A lot of issues lately are due to people having flashed an ICS leak that caused their mainver to update, making it so that they could not simply flash back to GB. But now there are ICS ROMs out that you don't have to worry about that happening with, but if you are going to go for one of those I would confirm that in the thread of the ROM you pick.
Also, it's possible you may have to flash an ICS kernel before flashing an ICS ROM. I haven't gone to ICS yet but have read that when you go back to GB from ICS you have to flash a GB kernel first, so I would just check on that and make sure first if you're going with ICS.
And due to not having s-off I guess things are a bit different than if you do have it but it's not as bad as it seems.
So basically you are going to:
- unlock the phone by obtaining an unlock code from HTCDev [adb]
- flash Amon Ra, a recovery being used instead of CWM since that one's been buggy on the Rezound [adb - put recovry img file in same folder you used for unlocking]
- root [you will download a self contained toolset in its own folder and use that]
- flash ROM [put the zip file on your external sd card and flash in recovery]
- flash kernel [put the zip file on your external sd card and flash in recovery]
Here is a thread that will take you through the steps,
BUT When you get to the recovery part, at this time the latest version of recovery is not in the first post, get it here:
http://forum.xda-developers.com/showpost.php?p=21730681&postcount=235
AND this guide skips flashing a ROM and also says it's for ziggy's kernel, so once you get past flashing Recovery go to the thread of the ROM you've selected and follow their instructions, then same thing with whatever kernel you've chosen.
[GUIDE] Super-noob guide to unlocking, rooting, and flashing Ziggys kernel
Hope this helps. Good luck and happy flashing!
I guess never have used adb doesn't help?
-Sent from my Droid 2-
I Am Marino said:
I guess never have used adb doesn't help?
-Sent from my Droid 2-
Click to expand...
Click to collapse
If you do a little searching, there are a few great adb tutorials on this website. Try the DInc 2 threads.
Sent from my ADR6425LVW using Tapatalk
Couple of tips:
- Don't worry about rooting if you're going to flash a ROM or at least not before you flash a new ROM. If for some reason your new ROM isn't rooted, you can root it later.
- "adb reboot bootloader" is your friend. Saves you from having to pull the case off for the battery a million times.
I came from an OG droid so all this fastboot stuff was new for me too, but I got the hang of it pretty quick. It really just adds one more layer between the recovery.
killsforpie said:
Couple of tips:
- Don't worry about rooting if you're going to flash a ROM or at least not before you flash a new ROM. If for some reason your new ROM isn't rooted, you can root it later.
- "adb reboot bootloader" is your friend. Saves you from having to pull the case off for the battery a million times.
I came from an OG droid so all this fastboot stuff was new for me too, but I got the hang of it pretty quick. It really just adds one more layer between the recovery.
Click to expand...
Click to collapse
The ROM roots for me or did I just understand that wrong?
-Sent from my Droid 2-
I Am Marino said:
The ROM roots for me or did I just understand that wrong?
-Sent from my Droid 2-
Click to expand...
Click to collapse
Yes I would say 99% of custom ROMs are already rooted.
killsforpie said:
Yes I would say 99% of custom ROMs are already rooted.
Click to expand...
Click to collapse
That's the first I've heard of that here in the Rezound forums. Not saying it's not true, just never read that here.
In any case, I would root first so you can make nandroid of your stock rooted phone in case the ROM flashing doesn't go smoothly. Then you can always go back to rooted stock easily and start over. I have mine saved for any future needs as well.
As to using adb. MrSmith317 (I think I got his numbers right) put up a nice little mini sdk which has the files you need for using adb for the purposes you will need to use it. I've attached it below since I can't find his original post that had it attached. Unzip that, rename the folder to something easy and put it in the root of your C: directory for easy navigation from the command prompt. You will use that to unlock and flash recovery.
Oh, another thing... there is an updated version of Amon Ra buried in the thread that never got put in the first post, so don't use versions listed in that first post. The latest version is now 3.13 found here: http://forum.xda-developers.com/showpost.php?p=21730681&postcount=235 . I'll update my other post to mention this.
And one last thing, it's possible you may have to flash an ICS kernel before flashing an ICS ROM. I haven't gone to ICS yet but have read that when you go back to GB from ICS you have to flash a GB kernel first, so I would just check on that and make sure first if you're going with ICS. I'll mention this too when I edit previous post.
I always do my backups from recovery where you don't need root (at least I didn't with the Rezound, been too long since my droid was unrooted). 99% is completely made up, but are there actually custom ROMs out there without root...? Not leaks or backups, but actual custom ROMs people have built.
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.
Hello,
I have an AT&T HTC One X+ (plus). Currently, I have unlocked the bootloader, rooted, and now have the TWRP recovery on my phone. I will admit I am a n00b at Android, but some help on the following issue will be greatly appreciated. I believe I got the proper cyanogenmod and gapps files, and I then push them to my device via Terminal (Mac). However, when I go to install them, they come back as failed. It says "E:Unable to open zip file." If someone could tell me what the issue is, that would be great. I feel that I am very close to flashing a new rom, but I am in desperate need of assistance. If you could possibly link proper gapps and cyanogenmod (or other custom rom) files, I would really appreciate it.
Thanks,
JCarrot
JohnCarrot said:
Hello,
I have an AT&T HTC One X+ (plus). Currently, I have unlocked the bootloader, rooted, and now have the TWRP recovery on my phone. I will admit I am a n00b at Android, but some help on the following issue will be greatly appreciated. I believe I got the proper cyanogenmod and gapps files, and I then push them to my device via Terminal (Mac). However, when I go to install them, they come back as failed. It says "E:Unable to open zip file." If someone could tell me what the issue is, that would be great. I feel that I am very close to flashing a new rom, but I am in desperate need of assistance. If you could possibly link proper gapps and cyanogenmod (or other custom rom) files, I would really appreciate it.
Thanks,
JCarrot
Click to expand...
Click to collapse
First try re-downloading the zip file to rule out a bad download
Jonnibravo said:
First try re-downloading the zip file to rule out a bad download
Click to expand...
Click to collapse
If I download it and it decompresses and becomes a folder, should i compress it? Could the file not be compatible with Macs?
JohnCarrot said:
If I download it and it decompresses and becomes a folder, should i compress it? Could the file not be compatible with Macs?
Click to expand...
Click to collapse
You MUST NOT uncompress the zip file you have downloaded.
Check the MD5 checksum, as said by the previous user, it might be a bad download.
I hope you have taken care of moving all your data to the 0 folder...
Also, before trying non Sense ROMs on ATT - see the thread carefully (I have heard there are isues.. but I am not sure the truth because I don't own one )
Addicted2xda said:
You MUST NOT uncompress the zip file you have downloaded.
Check the MD5 checksum, as said by the previous user, it might be a bad download.
I hope you have taken care of moving all your data to the 0 folder...
Also, before trying non Sense ROMs on ATT - see the thread carefully (I have heard there are isues.. but I am not sure the truth because I don't own one )
Click to expand...
Click to collapse
I was able to get the file uncompressed. Then, I used adb push to put the file on my phone. I wiped the phone. When I tried to install the .zip file, it fails. Any suggestions?
If I do "adb push" for the files I want on my phone and I boot into recovery before it show something like "1309 KB/s (1050533 bytes in 0.783s)," the files may not have fully loaded onto the phone. Should I just wait a until they display something like that? Could this the source of my issues (that the files are not fully loaded)?
JohnCarrot said:
If I do "adb push" for the files I want on my phone and I boot into recovery before it show something like "1309 KB/s (1050533 bytes in 0.783s)," the files may not have fully loaded onto the phone. Should I just wait a until they display something like that? Could this the source of my issues (that the files are not fully loaded)?
Click to expand...
Click to collapse
I am assuming you have TWRP? Use adb sideload and not adb push. Since you want to install CM - I am assuming you have downloaded a file called CM10.1xxxxxxxxxxxxxxxxxx.zip (may be cm-10.1-20130607-UNOFFICIAL-enrc2b).
Use adb sideload to copy this zip file to your pone
Now use adb side load the ROM, the file should be renamed sideload.zip when it is copied on your phone.
Addicted2xda said:
I am assuming you have TWRP? Use adb sideload and not adb push. Since you want to install CM - I am assuming you have downloaded a file called CM10.1xxxxxxxxxxxxxxxxxx.zip (may be cm-10.1-20130607-UNOFFICIAL-enrc2b).
Use adb sideload to copy this zip file to your pone
Now use adb side load the ROM, the file should be renamed sideload.zip when it is copied on your phone.
Click to expand...
Click to collapse
I was able to get cm to work using advice push. I am using TWRP. Could it be possible that cm is really buggy because I used adb push. Sorry question mark not working. CM literally ceases and reboots every five minutes. It is practically not usable.
JohnCarrot said:
I was able to get cm to work using advice push. I am using TWRP. Could it be possible that cm is really buggy because I used adb push. Sorry question mark not working. CM literally ceases and reboots every five minutes. It is practically not usable.
Click to expand...
Click to collapse
nope, it's just super unstable right now. Not by any means a daily driver. Most of the other issues are not really being looked at currently until the devs manage to fix the current lack of call audio.
NasaGeek said:
nope, it's just super unstable right now. Not by any means a daily driver. Most of the other issues are not really being looked at currently until the devs manage to fix the current lack of call audio.
Click to expand...
Click to collapse
Are there devs still working on it? I thought they abandoned the HTC One X+.
There is certainly still work being done, as evidenced by this thread, though it is slow going. Lloir in particular should be commended for doing as much work on AT&T HOX+ as he does considering he doesn't even use the phone. All of that being said, from the looks of it our hopes of call audio being fixed (among other things) are slim
NasaGeek said:
There is certainly still work being done, as evidenced by this thread, though it is slow going. Lloir in particular should be commended for doing as much work on AT&T HOX+ as he does considering he doesn't even use the phone. All of that being said, from the looks of it our hopes of call audio being fixed (among other things) are slim
Click to expand...
Click to collapse
Could my issue of CM being so buggy and rebooting every 5 minutes be because I did not change the kernel? I am somewhat of an Android n00b, but I did get CM working on my HOX+ and unlock the bootloader. I just don't entirely understand why I need to change the kernel. Thanks for responding btw.
It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.
NasaGeek said:
It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.
Click to expand...
Click to collapse
Oh...I've already done that. I got my CM from lloir.com and I downloaded the boot.img along with the rom. I didn't know what the fastboot flash boot boot.img did. I just knew that I had to do it. I didn't know that was the kernel.
Different HOX+ ROM
NasaGeek said:
It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.
Click to expand...
Click to collapse
Do you know of any different roms (AOKP/Paranoid/others) that are less glitchy for the AT&T HOX+? The CM10.1 that is currently on my phone just is not daily driver material by any stretch of the imagination. I want a somewhat stable (it can reboot like twice a day but not every 5 minutes) kind of stock rom because Sense 4+ is killing me. Well, I've been using CM, but that constant rebooting is killing me, as well.
JohnCarrot said:
Do you know of any different roms (AOKP/Paranoid/others) that are less glitchy for the AT&T HOX+? The CM10.1 that is currently on my phone just is not daily driver material by any stretch of the imagination. I want a somewhat stable (it can reboot like twice a day but not every 5 minutes) kind of stock rom because Sense 4+ is killing me. Well, I've been using CM, but that constant rebooting is killing me, as well.
Click to expand...
Click to collapse
AFAIK all non Sense ROM are little unstable in ATT
I have CM 10.1 on the HOX+ International and it works just fine. no random reboots and pretty smooth. excellent battery life. Snappier than Viper, which I was on before this.
surfatwork said:
I have CM 10.1 on the HOX+ International and it works just fine. no random reboots and pretty smooth. excellent battery life. Snappier than Viper, which I was on before this.
Click to expand...
Click to collapse
The problem is with the ATT version...
We are lucky
I've recently purchased a Thunderbolt from eBay (which I know is always a bit sketchy, and that the device is getting a bit older) but so far it's been a relatively good little phone. I'm definitely enjoying the LTE over the 3G my iPhone 4 had before I accidentally murdered it. I have the HTC Dev unlock on this phone, but the stock ICS rom pushed out by Verizon and HTC feels bloated and slow to me, having come from the iPhone 4 running a jailbroken iOS 6.1.2.
Would someone be so kind as to point me towards a fast, stable ICS or Jellybean ROM and instructions on how to install it and a proper recovery on my phone? I'm not all that picky about appearances, and I wouldn't mind running stock Android either if someone can tell me how to get it running on this phone. Currently I'm running all of the latest updates courtesy of the previous owner (I'm up to HBOOT 1.08, ICS 4.0.4, software version 7.02.605.10 710RD).
Thanks in advance for any help you can provide.
EDIT: After much more tinkering, I have managed to get Clockwork Mod Recovery running on my phone, but I would still very much appreciate if someone had a suggestion for a ROM that runs quickly and efficiently.
Look through the Development forum here and head over to Infected Roms. Lots of answers to your questions in both places. Just takes a little time go through the threads to find what you need.
Sent from my ADR6400L using Tapatalk 4
Raddatzjos said:
I've recently purchased a Thunderbolt from eBay (which I know is always a bit sketchy, and that the device is getting a bit older) but so far it's been a relatively good little phone. I'm definitely enjoying the LTE over the 3G my iPhone 4 had before I accidentally murdered it. I have the HTC Dev unlock on this phone, but the stock ICS rom pushed out by Verizon and HTC feels bloated and slow to me, having come from the iPhone 4 running a jailbroken iOS 6.1.2.
Would someone be so kind as to point me towards a fast, stable ICS or Jellybean ROM and instructions on how to install it and a proper recovery on my phone? I'm not all that picky about appearances, and I wouldn't mind running stock Android either if someone can tell me how to get it running on this phone. Currently I'm running all of the latest updates courtesy of the previous owner (I'm up to HBOOT 1.08, ICS 4.0.4, software version 7.02.605.10 710RD).
Thanks in advance for any help you can provide.
EDIT: After much more tinkering, I have managed to get Clockwork Mod Recovery running on my phone, but I would still very much appreciate if someone had a suggestion for a ROM that runs quickly and efficiently.
Click to expand...
Click to collapse
I just mashed my Rezound, so I'm back on the TBolt as well and had to go through the same thing. Before I go all out on this, I can tell you that the process to get this done isn't that bad considering I will compile all the instructions here, but you have to flash a patch through HBOOT then relock the phone, take it back to an older ROM, run revolutionary on it for s-off, load radios, then back to ICS lol. If you think it will be worth it to you, let me know an I will post the links. It's just a bunch of back and forth and I took me about a week to find all the pieces.
FirePsych said:
Look through the Development forum here and head over to Infected Roms. Lots of answers to your questions in both places. Just takes a little time go through the threads to find what you need.
Sent from my ADR6400L using Tapatalk 4
Click to expand...
Click to collapse
Yeah, there's a lot of pages to go through, and apparently I'm not searching for something the right way.
DiaboliqAngel said:
I just mashed my Rezound, so I'm back on the TBolt as well and had to go through the same thing. Before I go all out on this, I can tell you that the process to get this done isn't that bad considering I will compile all the instructions here, but you have to flash a patch through HBOOT then relock the phone, take it back to an older ROM, run revolutionary on it for s-off, load radios, then back to ICS lol. If you think it will be worth it to you, let me know an I will post the links. It's just a bunch of back and forth and I took me about a week to find all the pieces.
Click to expand...
Click to collapse
Hey, works for me! I really want to like Android, but Verizon's firmware is so bloated and slow it makes it hard to do. I'm willing to go through the work if it means I can get a phone that runs the way I want.
My cousin keeps telling me I need to run pure Android, and honestly, that's what I'd like to do if at all possible, but any ROM that runs efficiently is good for me.
Raddatzjos said:
Yeah, there's a lot of pages to go through, and apparently I'm not searching for something the right way.
Hey, works for me! I really want to like Android, but Verizon's firmware is so bloated and slow it makes it hard to do. I'm willing to go through the work if it means I can get a phone that runs the way I want.
My cousin keeps telling me I need to run pure Android, and honestly, that's what I'd like to do if at all possible, but any ROM that runs efficiently is good for me.
Click to expand...
Click to collapse
Go to this page to start the journey http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/8695-guide-how-gain-root-s-off-after-taking-ics-ota.html and just FYI, I use 4ext recovery now and love it, but you have to be s-off and rooted to get it. use the QR code found here http://forum.xda-developers.com/showthread.php?p=31966447 It will download and app to your SD card (typically) under "Downloads" and you will need a file manager or root explorer to install it, and I had to download "4EXT Recovery Touch v1.0.0.5 RC5" twice before it took.
Then once you have gone through those steps (I had TWRP recovery and it worked) you will be on GB. To save some time, go to http://forums.infectedrom.com/ and create an account. I doesn't have to be verified by the admin to download. Once your account is created, go to http://forums.infectedrom.com/showthread.php/1912-ROM-Official-Thunderbolt-ICS-Rooted-Deodexed-Stock?p=67120&viewfull=1#post67120 and download the radio and flash it, then download the ROM of your choice. I used the "DEBLOATED Rom Deodexed version: 7.02.605.10 710RD". It's stock with all of the VZW crap pulled out and deodexed. I'm haveing to revert back to a custom GB ROM because the new ICS kernel doesn't have the built-in support for the 2-way call recording feature, but everything else works like a dream. I agree, that for the TB, staying close to stock on ICS is a good idea since development has dwindling for this device. Cheers and let me know if you need any help with this. just reply here
DiaboliqAngel said:
Go to this page to start the journey http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/8695-guide-how-gain-root-s-off-after-taking-ics-ota.html and just FYI, I use 4ext recovery now and love it, but you have to be s-off and rooted to get it. use the QR code found here http://forum.xda-developers.com/showthread.php?p=31966447 It will download and app to your SD card (typically) under "Downloads" and you will need a file manager or root explorer to install it, and I had to download "4EXT Recovery Touch v1.0.0.5 RC5" twice before it took.
Then once you have gone through those steps (I had TWRP recovery and it worked) you will be on GB. To save some time, go to http://forums.infectedrom.com/ and create an account. I doesn't have to be verified by the admin to download. Once your account is created, go to http://forums.infectedrom.com/showthread.php/1912-ROM-Official-Thunderbolt-ICS-Rooted-Deodexed-Stock?p=67120&viewfull=1#post67120 and download the radio and flash it, then download the ROM of your choice. I used the "DEBLOATED Rom Deodexed version: 7.02.605.10 710RD". It's stock with all of the VZW crap pulled out and deodexed. I'm haveing to revert back to a custom GB ROM because the new ICS kernel doesn't have the built-in support for the 2-way call recording feature, but everything else works like a dream. I agree, that for the TB, staying close to stock on ICS is a good idea since development has dwindling for this device. Cheers and let me know if you need any help with this. just reply here
Click to expand...
Click to collapse
Excellent! Thank you for this. I guess I know what my project is for tonight.
Raddatzjos said:
Excellent! Thank you for this. I guess I know what my project is for tonight.
Click to expand...
Click to collapse
No problem, and if you need any help or it's unclear, just let me know. Oh, and if I helped you out, please hit the "Thank" button on that post Cheers
Yeah, I strongly recommend ditching clockwork mod for 4ext.
Sent from my ADR6400L using Tapatalk 2
Shadow Death said:
Yeah, I strongly recommend ditching clockwork mod for 4ext.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I've been attempting to do just that, and every time I try to load my recovery, I keep getting ClockworkMod. 4ext fails to install, despite the app saying it was successful.
Raddatzjos said:
I've been attempting to do just that, and every time I try to load my recovery, I keep getting ClockworkMod. 4ext fails to install, despite the app saying it was successful.
Click to expand...
Click to collapse
Email the Dev. He's extremely responsive and very helpful.
Sent from my ADR6400L using Tapatalk 2
Raddatzjos said:
I've been attempting to do just that, and every time I try to load my recovery, I keep getting ClockworkMod. 4ext fails to install, despite the app saying it was successful.
Click to expand...
Click to collapse
I don't quite remember how I got to the end result of 4ext actually working but I remeber I had to download it twice from the installer app, and told the app to wipe cache + dalvik... but just to make sure, check these steps:
1) make sure you're rooted with s-off and have SU and busy box installed.
2) download the updater app file from the link provided in the QR code (from previous post).
3) make sure "unknown sources" is enabled in settings so you can install the updater app, then find the app in your download folder on your SD card and install it.
4) open the updater app and give it SU permissions, then run the install/update option and select the proper file. This will also be stored on your SD card (in a 4ext folder I think...don't quote me on that though).
after install you should be good, but I believe you can push via ADB as well. Attached is a PDF from the Dev on this as well.
---------- Post added at 12:32 PM ---------- Previous post was at 12:26 PM ----------
Sorry, I guess the PDF was too large. just remove the "http://forum.xda-developers.com/" out of the link and replace it with "http://www.". http://forum.xda-developers.com/4ext.net/install.pdf I can't post external links yet.
Now that I am thinking about it. Did you update super user or super su after getting root? The app itself probably needs it and the binary as well. You can update the binary by opening the app. It should prompt you to update it.
Sent from my ADR6400L using Tapatalk 2
Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!