Related
New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/showthread.php?t=2182792) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.
jumi1174 said:
New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/show...182792&page=21) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.
Click to expand...
Click to collapse
i would ike many of the same answers
experts help us!
https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium
Im still very new to all of this as well, but i wanted to share this toolkit with you just encase you havent seen it yet. http://forum.xda-developers.com/showthread.php?t=2183942 Its been a tremendous help to me, hopefully it will be to you.
As far as the AT&T bloatware is concerned, It was very easy to remove once i was rooted and had flashed a new ROM. Ive used both Titanium Backup, and Rom Toolkit Pro to remove the junk.
Best of luck with your devices, Ive had a great time learning with mine so far.
jumi1174 said:
New to the forums and the rooting scene. From me researching, it seems I can get rid of the ATT bloatware on my HTC One by rooting the phone. I've never rooted a phone in my life, and the vast majority of the tutorials on the site assume a working knowledge of what the heck they're talking about (which I don't...).
I was able to follow the tutorial in this thread (http://forum.xda-developers.com/show...182792&page=21) to successfully unlock the bootloader.
(1) What does unlocking the bootloader mean?
(2) When I unlocked the bootloader, my phone completely reset. Is that normal?
(3) The tutorial continues as if your phone didn't reset. Should I reboot back into the fastboot mode and plug back in to the comp to continue the tutorial?
(4) By unlocking the bootloader, will I receive OTAs from ATT?
(5) If I root, will I receive OTAs from ATT?
(6) If I root, how can I still use the stock OS and just get rid of the ATT bloatware?
(7) I see things talk about "NAND backups" before one should root. What are those?
(8) What are RUUs?
(9) What does "Odexed" and "De-Odexed" mean...?
Thanks in advance for the help. I want to learn this stuff and can't find any explicit answers in these forums. I don't want to damage this brand new awesome phone.
Click to expand...
Click to collapse
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
2. This is 100% normal. It is strongly advised you backup everything before unlocking due to this.
3. The link in your post to that tutorial is broken so there is no way to see what you mean. Sorry.
4. You cannot receive OTA while the bootloader is unlocked. You would need to relock your bootloader to continue with an OTA update.
5. As of now, no due to having to unlock your bootloader. Please see answer 4.
6. You would need to flash a zip file in a custom recovery to debloat your phone. There are other ways but this is the best way for a very new user. Link to debloat zip: http://forum.xda-developers.com/showthread.php?t=2250403
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
9. Odexed is the default state of the stock ROM. What it means is that a separate .odex cache file is stored away from a system app. It allows the app to load faster as upon boot your phone loads these cache files into the Dalvik VM. When a developer De-Odexes a ROM it means they have taken away those cache files and instead compiled them within the system app. This, in theory is a bit slower, but only when you clear your Dalvik and cache from recovery, otherwise you will notice no difference. The reason a developer does this is it makes the system app easily modifiable and themable. In summary, Deodex equals easily modifiable, whereas odex means the app is more locked down.
Sent from my HTC One using xda app-developers app
Thanks RPelham,
I hate to piggyback on someone else's thread, but they may want the answer to my question as well.
Is it a good idea to clear system and Dalvik cache from within recovery every now and then? Im used to the PC world, where clearing cache from time to time helps keep things in order.
Snakemanc6 said:
Thanks RPelham,
I hate to piggyback on someone else's thread, but they may want the answer to my question as well.
Is it a good idea to clear system and Dalvik cache from within recovery every now and then? Im used to the PC world, where clearing cache from time to time helps keep things in order.
Click to expand...
Click to collapse
No. You only need to clear Dalvik and Cache when flashing a new ROM, Kernel or basically any ZIP package. It won't serve any good purpose to randomly clear it. =)
Android has a great built in way of keeping your phone running great and killing any app that has not been recently used to keep everything running smooth.
Sent from my HTC One using xda app-developers app
behrouz said:
https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Awesome videos, thanks!
RPelham said:
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
2. This is 100% normal. It is strongly advised you backup everything before unlocking due to this.
3. The link in your post to that tutorial is broken so there is no way to see what you mean. Sorry.
4. You cannot receive OTA while the bootloader is unlocked. You would need to relock your bootloader to continue with an OTA update.
5. As of now, no due to having to unlock your bootloader. Please see answer 4.
6. You would need to flash a zip file in a custom recovery to debloat your phone. There are other ways but this is the best way for a very new user. Link to debloat zip: http://forum.xda-developers.com/showthread.php?t=2250403
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
9. Odexed is the default state of the stock ROM. What it means is that a separate .odex cache file is stored away from a system app. It allows the app to load faster as upon boot your phone loads these cache files into the Dalvik VM. When a developer De-Odexes a ROM it means they have taken away those cache files and instead compiled them within the system app. This, in theory is a bit slower, but only when you clear your Dalvik and cache from recovery, otherwise you will notice no difference. The reason a developer does this is it makes the system app easily modifiable and themable. In summary, Deodex equals easily modifiable, whereas odex means the app is more locked down.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the awesome reply!
This is the link: http://forum.xda-developers.com/showthread.php?t=2182792
Sorry it was dead, I'll edit my original post.
Another question if you don't mind (may be a stupid question), if I root, will I still be able to purchase apps from the play store without any trouble?
behrouz said:
https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
https://www.youtube.com/watch?v=QU7vi388dMk&feature=youtube_gdata_player
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
These videos are an absolute perfect example of how to unlock and root. Step by step. If you are new, this will be the perfect go to for help.
Sent from my HTC One using xda app-developers app
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
jumi1174 said:
Another question if you don't mind (may be a stupid question), if I root, will I still be able to purchase apps from the play store without any trouble?
Click to expand...
Click to collapse
Yes, you absolutely can. The only thing Root is giving you is administration level access to your phone. Obtaining root gives you the ability to modify, remove or add core system files and gives apps a lot more functionality as they can integrate themselves into the system.
And to answer question 3:
Yes the phone resets after you unlock your bootloader and it boots back into your phone. Simply reboot back to your bootloader and enter fastboot mode to continue flashing your recovery.
After you flash the recovery, it will boot back into your phone again (once you select recovery from the bootloader menu for the first time after the flash). Don't be alarmed by this, just reboot once more, select your recovery option again and this time it will truely take you to recovery.
Sent from my HTC One using xda app-developers app
RPelham said:
Yes, you absolutely can. The only thing Root is giving you is administration level access to your phone. Obtaining root gives you the ability to modify, remove or add core system files and gives apps a lot more functionality as they can integrate themselves into the system.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for all the help. One more if you don't mind (I appreciate your patience with helping a beginner like myself), will my phone be reset again when I root?
jumi1174 said:
Thanks for all the help. One more if you don't mind (I appreciate your patience with helping a beginner like myself), will my phone be reset again when I root?
Click to expand...
Click to collapse
No. Once you unlocked your bootloader your phone will not reset unless you flash a custom ROM or specifically wipe your device. Rooting will retain all settings and apps.
P.s. I'm heading off for the night. I hope I answered everything for you and helped you obtain a better understanding over this whole process. Ill follow up tomorrow to see if everything worked out for you and answer any additional questions. =)
Sent from my HTC One using xda app-developers app
RPelham said:
No. Once you unlocked your bootloader your phone will not reset unless you flash a custom ROM or specifically wipe your device. Rooting will retain all settings and apps.
P.s. I'm heading off for the night. I hope I answered everything for you and helped you obtain a better understanding over this whole process. Ill follow up tomorrow to see if everything worked out for you and answer any additional questions. =)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them and will I ever need to use them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
(3) The instructions for this ROM: http://forum.xda-developers.com/showthread.php?t=2192324
-Download ROM
-Copy ROM to your sdcard
-Fullwipe in AROMA if you come from another ROM or base
-Flash the ROM
-Let the ROM boot (After a Fullwipe this takes some time)
-Enjoy TrickDroid
I understand the first 2 steps, but what does "Fullwipe in AROMA" mean?
(4) Difference between a ROM and a KERNEL?
(5) Are you familiar with Titanium Backup? I've tried reading their wiki, but I'm still not 100% sure what exactly it backs up and how that is different than the TWRP back up.
jumi1174 said:
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
Click to expand...
Click to collapse
Hi.
1) they are just ruu for many different carriers, countries, etc. There is a specific ruu for your device. That's why so many ruu there
2) no need for that. Just install titanium backup pro from play store after rooting and you can delete all bloatwares or freeze them. Which will also get rid of those unwanted apps from your phone.
---------- Post added at 03:06 AM ---------- Previous post was at 03:03 AM ----------
RPelham said:
1. Unlocking the bootloader allows you to flash a custom recovery onto your device. It's a necessary step in the rooting process until s-off is obtained
7. Nandbackup or Nandroid are complete backups of your phone's firmware. It's recommended to have one good up to date backup so if something goes wrong on a new ROM you flashed, you can easily revert. Nandroids are created in custom recoveries like TWRP.
8. An RUU is a package for your phone that contains a set of stock images used to unroot your phone and return it to complete stock. It stands for ROM Update Utility.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hello mate
I have 2 questions.
Number 7, how do I make backup of your rom if you still haven't installed custom recovery?
Number 8 to unroot my phone I can also use the nandroid backup instead of ruu right?
Edit: 1 more Lol. Sorry.
I asked many places but didn't get an answer for it.
Let's say I have custom ROM, and I need to relock boot loader and flash stock ruu to go back to stock in order to receive ota update. Does the ruu contains the stock recovery? Cuz I read somewhere that in order to get ota update I also needed to flash stock recovery?
Thanks a lot! I think I'm all set after this kkk
If anyone has an answer to this question I'd appreciate it very much. I've rooted many phones but all of them have had SD cards. The HTC One is lacking an SD Card so when I back up data/apks etc is there a spot on the phone's storage that doesn't get wiped when wiping from recovery to install new roms?
gotrandom said:
If anyone has an answer to this question I'd appreciate it very much. I've rooted many phones but all of them have had SD cards. The HTC One is lacking an SD Card so when I back up data/apks etc is there a spot on the phone's storage that doesn't get wiped when wiping from recovery to install new roms?
Click to expand...
Click to collapse
Nope. All gets wiped. Backup on ur PC.
Uh oh. I just told him the opposite in another thread. I could swear I read that selecting a "wipe userdata" option in recovery would erase everything in the /data partition *except* whatever is below /data/media?
Did I get this wrong?
Sent from my PC36100 using xda app-developers app
Ive flashed a couple of different ROMs, and my media has not been erased when selecting "wipe user data". Im using CWM, if that's of any consequence.
Snakemanc6 said:
Ive flashed a couple of different ROMs, and my media has not been erased when selecting "wipe user data". Im using CWM, if that's of any consequence.
Click to expand...
Click to collapse
Sorry then. I saw a video on yt saying all would be deleted. I will try to find and post it here.
Edit. https://www.youtube.com/watch?v=7hvbwWTbZOU&feature=youtube_gdata_player
He was using TWRP, no idea if that makes a difference. Just passing on my experience, Im by no means well versed in all of this lol
Its great having such an active forum to learn from though :good:
ksarius said:
Hi.
1) they are just ruu for many different carriers, countries, etc. There is a specific ruu for your device. That's why so many ruu there
2) no need for that. Just install titanium backup pro from play store after rooting and you can delete all bloatwares or freeze them. Which will also get rid of those unwanted apps from your phone.
---------- Post added at 03:06 AM ---------- Previous post was at 03:03 AM ----------
Hello mate
I have 2 questions.
Number 7, how do I make backup of your rom if you still haven't installed custom recovery?
Number 8 to unroot my phone I can also use the nandroid backup instead of ruu right?
Edit: 1 more Lol. Sorry.
I asked many places but didn't get an answer for it.
Let's say I have custom ROM, and I need to relock boot loader and flash stock ruu to go back to stock in order to receive ota update. Does the ruu contains the stock recovery? Cuz I read somewhere that in order to get ota update I also needed to flash stock recovery?
Thanks a lot! I think I'm all set after this kkk
Click to expand...
Click to collapse
Im not 100% sure as I do not use Titanium, if someone could check that would be great, but I don't think titanium can permanently remove bloat yet. Freeze, yes, remove I'm unsure.
Our device has not achieved s-off which means that the partition the system apps sit on is not accessible to be altered from within the ROM, only by recovery / adb.
7. To my knowledge you must have a custom recovery to make a nandroid. You can't make a complete one without it. And once you nandroid, that backup is specifically for that recovery. I.e. you fly use a cwm nandroid in twrp
8. As long as your nandroid was created before installing the root package, yes.
RUUs will reflash stock recovery.
Sent from my HTC One using xda app-developers app
---------- Post added at 07:56 AM ---------- Previous post was at 07:52 AM ----------
jumi1174 said:
Excellent! Thanks for all the help, I really appreciate it! I'll edit this post if I have any more questions.
More questions:
(1) All the files on this thread: http://forum.xda-developers.com/showthread.php?t=2207874
What is the purpose of all these different files? Should I be familiar with them and will I ever need to use them?
(2) This package: http://forum.xda-developers.com/showthread.php?t=2250403
I'm not exactly sure how to install it. Any advice or tips?
(3) The instructions for this ROM: http://forum.xda-developers.com/showthread.php?t=2192324
-Download ROM
-Copy ROM to your sdcard
-Fullwipe in AROMA if you come from another ROM or base
-Flash the ROM
-Let the ROM boot (After a Fullwipe this takes some time)
-Enjoy TrickDroid
I understand the first 2 steps, but what does "Fullwipe in AROMA" mean?
(4) Difference between a ROM and a KERNEL?
(5) Are you familiar with Titanium Backup? I've tried reading their wiki, but I'm still not 100% sure what exactly it backs up and how that is different than the TWRP back up.
Click to expand...
Click to collapse
1 and 2 were answered above. I also elaborated on 2 above.
3. Aroma is an installation software made for recovery. It's a wizard that walks you through the ROM setup. You'll see an option for it while setting up the ROM
4. Kernel is the software that allows your hardware to communicate with your ROM as well as control boot screens, splash screens and overclocking and undervolting.
ROM is the phones operating system.
5. TWRP is a FULL backup, titanium is just an app, it can't backup 100% of everything like a recovery can. Titanium backs up your app and user data. Basically your settings and apps.
Sent from my HTC One using xda app-developers app
Hello, everyone, I'm in a bit of a bind here.
I own an HTC One on Sprint's network and have decided tonight to finally root it. I unlocked the bootloader and successfully installed TWRP Recovery v.2.6.3.0. (downloaded from here: http://techerrata.com/browse/twrp2/m7wls) I ran into a bit of an issue, though, when trying to install Paranoid Android (Which I had downloaded from here: http://forum.xda-developers.com/showthread.php?t=2315236); it was saying it couldn't mount my sd card. Note that the HTC One doesn't have any external storage, so it meant the internal one. And it also said something along the lines of "some symlinks failed," my apologies that I can't be more specific.
Anyway, I had my phone all backed up (Important files such as photos, audio files have already been backed up with Dropbox, so no concern there) and I read that it was a problem with TWRP after version 2.3.3.0. So I tried to install that recovery, but it didn't stick. So I tried switching to Clockworkmod Recovery, which I downloaded from here: http://www.clockworkmod.com/rommanager. I scrolled down to HTC One (Sprint) and selected the classic 6.0.3.6.
All was well, I backed up again, until I tried to install PA again. I had the same basic issue. Long-story short, in between the switching recoveries, I had forgotten to restore my data before I switched recoveries, so I lost the backup and I'm 99% there is no OS on my phone at the moment.
I've heard that I can, using TWRP (which I flashed back to), sideload a ROM onto my phone to flash. I tried this, however it had be check that my device was attached by typing "adb devices" in the command prompt (open in the folder where adb.exe is), and no devices are listed.
It appears that there's a loading bar on my phone when i click ADB Sideload, and it says "Starting ADB sideload feature...", however, nothing seems to be happening.
Any help would be super greatly appreciated, and I'm sorry if I left out any information.
Rooting my old Moto Droid was easy, but something was bound to get messed up i guess
The first problem I see is the link for PA is not from the Sprint forum.
Sen me a PM i can get you fixed up
If he does t get you fixed all up I can help you out also but he is a smart one so I'd imagine he will get you up and going. Either way, possibly the greatest partial thread title ever... "Mistakes may have been made"
bigdaddy619 helped me considerably, thank you He got me back to basically having a new, store-bought phone. Which was much better than I had!
Just time to start over, I suppose, and not make any mistakes. I definitely was using a Paranoid Android for the Samsung Galaxy Nexus and didn't realize it (Though my main mistake was flashing a new recovery before restoring my backup. Rookie mistake!)
Uh oh, well all you need to know is what I have always said is if you root, ALWAYS S-Off in order to undo your mistakes no matter what and that will almost always kep you safe.
Sent from my HTCONE using Tapatalk 4
I once ended up with wiped internal storage, could not get my computer to load correct driver for adb so I flashed ruu then redid rooting process, s-off, etc
Sent from my Nocturnal Google Edition CDMA 5.0 using XDA Premium 4 mobile app
With the new 4.3 OTA I thought I might be good to delve into updating my phone today. That was around Noon, it's now 9PM, and I just don't know where else to turn. I know where I screwed up a few things and I feel like I've tried everything. Hopefully you guys will have some helpful suggestions, if not I guess I'll have to bite the bullet.
I'm a noob at rooting. I did root my HTC Evo Shift a year or two ago. Put CM 7.something on it, but I really wasn't happy with the performance so I just RUU'd back to stock and haven't messed with it since. I did leave it rooted for some root required apps though.
I rooted my HTC One a couple months ago using this method:
On gizmodo how-to-root-your-nexus-htc-one-or-samsung-galaxy-s4-990847878 (can't link it because I just signed up)
With 4.3 out I thought I would be able to find a modified update and keep my phone Stock rooted or try InsertCoin or something. My first mistake, I believe, was thinking that root was fine without S-Off.
I've got Drivers and Android SDK on my Win7 machine (I have a Mac and Fedora box if anyone knows any solutions using those OS's). I have on the phone TWRP 2.5.0.0, root, S-On. I try to upgrade to TWRP 2.6.0.0 and that doesn't work so well. I read somewhere that the M7WLS doesn't like that build, and I should try 2.6.0.1, I just strait to 2.6.3.0.
Read some articles on TWRP, watched some videos, so I go to do factory data wipe, cache wipe, dalvik cache wipe, and I do system wipe thinking I need to do that too. Whenever I reboot I basically stop at the HTC splash screen. Mistake number two, I have no OS now.
I hunt down a recovery.img from a site that is supposedly offical Sprint, flash it, try to do a factory restore, no good.
I try getting it back to stock with this:
How to Unroot / Unbrick the HTC One M7: Back to Stock by C4Etech
youtube.com C0G0hKY4P9Y
fastboot oem rebootRUU
fastboot flash zip <rom>.zip
I get errors whether locked or unlocked. I still have S-On and I'm guessing that's why I'm getting signature validation errors.
I try TWRP and ClockworkMod 6.0.4.3 to see if I can mount to my PC, no go.
Fastboot devices recognizes the M7WLS so after more reading I'm going to try ADB sideload. ADB devices does not see my phone. HT Sync is already installed, I remove it and try HTCDriver_4.2.0.001, no go. I remove it and try Universal_Naked_Driver_0.73, still nothing on adb devices. Whether TWRP or ClockworkMod Recovery I can't side seem to sideload.
I go to the store and pick up a cable:
Staples.com Belkin-4-Ports-USB-20-External-Flex-Hub product_IM1QZ5590 (Can't link)
Put
insertcoin-m7-4.0-4.zip AND
Guru_Reset_M7_Sprint_1.29.651.10.zip
on a USB stick, but the phone doesn't recognize it so I can load from either recovery.
I'm sure I've missed a few things in there. Right now I'm sunk, I'm tired, and suggestions are appreciated.
Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask
Demo3827 said:
Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask
Click to expand...
Click to collapse
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.
your welcome
pwjohnston79 said:
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.
Click to expand...
Click to collapse
your welcome =] anytime :good:
Hi there,
I have searched high & low on the interwebs for a possible solution to my problem but have yet to yield any significant results.
I was on 4.2.2 Stock, Rooted, with bulletproof, and I had started to get random reboots and then 4 nights ago during the night it decided to get into a reboot loop. It would power up for about 20 mins and then restart again & again so when I woke up it was super hot.
So I thought it was time to update it to 4.3 now in the hope that this would resolve the issue but it didn't. I obtained the relevant RUU (Guru Reset M7 2.24.980.2 for HTC__039) from htc1guru and since I was only wanting to get the OTA in the hope that this would fix any other software issues, I only flashed the recovery. I then proceeded to do the large OTA update. This was successful. Then the reboots started again.
Time for a factory reset now, (which I realise I should have just done in the first place) but after setting up my details in the phone I am unable to get network over 3G/4G and when I go into look at the APNs, it says that no sim card is installed when it definitely is. When I go into Phone Info, it states that my EMEI is 00000000.
After looking around for what feels like hours, I read somewhere that I might need to flash the radio but I only have the radio from the previous RUU(Guru Reset M7 2.24.980.2) or can I use that since I can not find anything around RUUs for 3.63.980.2.? I don't want to make the situation any worse than it already is.
I am hoping that there is a simple explanation and fix & any help or guidance would be much appreciated.
Thanks in advance :good:
So you think the problem is that your software is upgraded and not your firmware? If so, you can solve that by dowgrading your software. If you can't find an updated RUU (nothing except a signed file from HTC should be called a RUU), there is still a solution:
- Find a system dump from a phone that is your CID and the version of Android you want. It will be a CWM or TWRP backup.
- Flash the appropriate custom recovery.
- Push the files to your phone in the appropriate directory (you may need to make a backup just to see what the right directory is).
- Restore the backup you just pushed to your phone.
Then factory reset and install the stock recovery. You may need to re-lock the bootloader (I'm not sure). Try to get the correct OTA. If you can't find it, try to download one and save as /sdcard/update.zip. Use the stock recovery to flash it. (You'll need to search for instructions on how to do that. It involves key combinations.) Finally, unlock the bootloader, make a backup, and (optionally) root. Don't install a custom kernel. If your problem persists, you likely have a hardware problem.
Thanks for your reply.
I have no idea if its software/firmware but its showing its on 4.3. I was speculating on the radio possibly needing to be reflashed due to one comment I read on a forum I randomly came across?
So I could use my very first backup I used through TWRP and push that to the phone?
While I am fairly new to Android(had to switch for the HTC ONE), I have been around idevices for a long time and have learnt to always keep multiple backups just in case
I left the bootloader unlocked as most guides say that you don't need to have it locked to get the OTA. I actually tried to find the manual OTA file and do it the way you suggested but at the time I had no luck.
I'll see what I can accomplish tonight.
Apologies on the noobness in regards to RUU.
Is it possible to use a RUU for lets say T-Mobile on an international variant? I see HTC released an RUU for T-Mobile for 4.3 but as far as I can see there isn't any others.
[email protected] said:
So I could use my very first backup I used through TWRP and push that to the phone?
Click to expand...
Click to collapse
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
fenstre said:
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
Click to expand...
Click to collapse
Hahahaha Well I trust your guess way more then mine
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)?
I tried last night to run rumrunner and it continually failed and basically told me I had 2 different scenarios to resolve it(the following is coming from memory and its very hazy). One was to use a different kernel and the other was to use another ROM, but that wasn't the preferred option.
At work now so will try and restore my original backup tonight at home. Thanks for your help.
[email protected] said:
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)? .
Click to expand...
Click to collapse
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
fenstre said:
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
Click to expand...
Click to collapse
No need to apologise, I'm just happy that someone has been able to assist me.
I have used one of my previous TWRP backups, unfortunately I couldn't use my very very first one as it was missing some files, it obviously didn't copy it all across for some reason
I now have my EMEI back (woohoo) but I think the backup I used has something wrong in the kernel as I think it has bulletproof installed. I am going to return it to stock but following a procedure here as I need to return it to HTC as the phone will not read any sim cards. I have tried 3 different sim cards and have also tested them in a firends HTC ONE and they all work in his. SO it looks like I do have an actual hardware issue with the phone which isn't cool just before Xmas.
I already have major withdrawals from being able to play ingress :crying:
Thanks heaps for your help.
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to flash the ruu. Full disclosure I no longer stand behind this due to lack of wifi. I went ahead and flashed with the RUU and fastboot flashed twrp back. This solution was only a temporary fix for me. As it should be for anybody if its used at all
You reckon this'll work with Boost Mobile?
TeamLiquid.koyo said:
You reckon this'll work with Boost Mobile?
Click to expand...
Click to collapse
There's already a flashable MM ROM for the boost 626s, http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
Yeah. On boost that's all you need
Genius... Simply Genius
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
i2andog said:
Genius... Simply Genius
Click to expand...
Click to collapse
Thanks man. Lol....
Did you try? If so, any issues?
IsaacGuti said:
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
Click to expand...
Click to collapse
I really don't know what causes the red letters. Personally speaking, I can still manage with or without them.
talksickisil said:
Thanks man. Lol....
Did you try? If so, any issues?
Click to expand...
Click to collapse
No I have a working PC... I just really admired your use of magiver like resources
Gotcha. . Yeah, it's not the first time. And not just phones. I Jimmy rig my way thru a lot of life haha. To be honest I'd probably still do this even if I had my PC. I'm just not a fan of fastboot and adb commands. And I don't want to lock my bootloader again
Yes.. those mother f'in boot loaders would burn in hell if I had any say ... in uh.. boot loaders souls or whatever... ... *crickets*.... hey check that out
Sent from my HTC Desire 626s using Tapatalk
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
s3llz said:
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
Click to expand...
Click to collapse
As far as which sprint ROM you flash debloated version or regular it doesn't really matter, since once you restore the twrp backup you're going to be on the standard non debloated metro official MM. As far as UI differences, there's a few things here and there. Nothing mind blowing. What was advantageous for me is the expanded internal storage. I love it.
I tried installing with the RUU and always got error 155 all the time some I am trying this method out. I would like to know will this method still work on a phone with exposed binary, and for those with MetroPCS, does the service still work as well.
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
bnawolf said:
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
Click to expand...
Click to collapse
In my instructions you don't stay on the sprint rom. You're supposed to restore the backup after installing that rom. But I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to re lock your bootloader and flash the ruu