A day or two ago I unlocked my ChaCha using the HTCDev.com instructions. I then used DooMLoRD_v4_ROOT-zergRush-busybox-su to root it. Everything was going fine until I apparently deleted one too many system apps and now my phone is in extremis.
The problem: As the phone boots up and reaches the HTC logo screen, just when the main interface should appear, an error pops up. It says:
Code:
Sorry!
The process com.htc.bg has stopped unexpectedly. Please try again.
[Force close]
When I close it, the HTC logo appears again as the main GUI is reinitialised, which leads to the same error popping up again, thus entering into an infinite loop.
I can just about manage to connect the phone to my PC as a disk drive, but it's not connected in such a way that RUU or unrooting applications can "find" it from within Windows, so if I'm to fix this it's gotta be from the SD card/Hboot.
Details:
* HTC ChaCha with the latest Android firmware.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
* Factory resets and recovery boots don't seem to have any effect.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Is there any hope of fixing this issue given my obvious lack of critical faculties?
Thank you for reading this.
You can always install clockworkmod recovery and from there a custom rom. Check the relevant thread, it is pinned.
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
Click to expand...
Click to collapse
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
Click to expand...
Click to collapse
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
Click to expand...
Click to collapse
You can't restore a system app if there is a conflict. Try and identify the conflict.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
Click to expand...
Click to collapse
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
* Factory resets and recovery boots don't seem to have any effect.
Click to expand...
Click to collapse
See above about freezing.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
Click to expand...
Click to collapse
Doesn't matter, you'll fix it, guarantee it.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
Click to expand...
Click to collapse
See what I said above.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Click to expand...
Click to collapse
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
For a safe to remove list, check the Themes and Apps section.
skezza said:
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Click to expand...
Click to collapse
Music to my ears!
skezza said:
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
Click to expand...
Click to collapse
In Titanium Backup I tried restoring the backups I made; the "Recovering Backup" notice would just hang indefinitely until I forced TB to close. This only happened with system apps. The backed up files are still on my PC hard drive from when I copied them from my SD card, but I'm not sure they're of any use at this stage.
skezza said:
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
Click to expand...
Click to collapse
Ahhh, this is probably my problem then. I ignored most of the fixes and workarounds listed as [S-OFF] because I didn't think they'd work for my device haha.
skezza said:
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
Click to expand...
Click to collapse
I'm disappointed in myself for being so haphazard in my deleting, I'm usually not that stupid but I think I was a little overexcited to have finally gotten rid of some of the bloatware that'd irritated me for so long haha. I was like "oh boy, I can save even more battery power and internal space if I just remove a little more!". Lesson learnt
skezza said:
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
...
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
Click to expand...
Click to collapse
As I said above I didn't realise I could make use of [S-OFF] materials so I didn't even attempt them for fear of making matters worse. I just now attempted to flash CWM and it hung on "parsing" which is what happened with previous flash attempts. If a flash attempt doesn't hang on "parsing" it parses for a second and then goes back to the main menu, apparently having no effect.
I'd be lying if I said I'm not overwhelmed by all of this; the tutorials I've read seem to assume a fair degree of prior knowledge that I definitely don't have haha. I hope I don't stretch anyone's patience here, but if you could explain it to me like a 6-year-old whose mother drank heavily during pregnancy I think it will help move things along!
Thank you for the thorough reply, much appreciated
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
dapaua said:
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
Click to expand...
Click to collapse
Unfortunately I can't do anything via my computer; my phone isn't "discovered" by the command line, unrooting tools or anything else. It does allow me to access the SD card as a hard drive but that's all it does. Obviously this wasn't the case before my problems started, because I used my PC to root and unlock the phone originally, but now the phone's boot process can't reach a point where it becomes receptive to the PC's commands. I don't know why it lets me access the SD card though.
Is there any way to do this without my PC being involved beyond transferring files to the SD card? If not, am I screwed? haha
Thanks mate!
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
The fastboot binary is here C:\Program Files (x86)\Android\android-sdk\tools , if you installed the android SDK, which I asume you did.
Good luck, I hope this works!
dapaua said:
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
Click to expand...
Click to collapse
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
dapaua said:
Good luck, I hope this works!
Click to expand...
Click to collapse
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
PaddyM said:
Dear CHRIST thank you for that - I didn't...
Click to expand...
Click to collapse
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
PaddyM said:
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
Click to expand...
Click to collapse
I'm happy it worked. Let's hope WiFi technology improves in the future
skezza said:
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
Click to expand...
Click to collapse
I knew about the recovery menu (the stock one, at least) but I didn't realise I could go into the Fastboot option and for the phone to then be recognisable to the PC, thus making it possible to flash via the command line. If I had known that I probably wouldn't have needed to post this thread at all haha.
skezza said:
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
Click to expand...
Click to collapse
Yeah... I think if it happened to one of you guys you probably would have had it sorted in about 6 minutes. 3 days isn't bad for my first attempt though! hahaha
skezza said:
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
Click to expand...
Click to collapse
Thanks for the advice man, I'll definitely be looking into the Nandroid backup option, although I hope I've learnt enough from this experience to have no need for it
Thanks to everyone who posted here, I appreciate the patience and the tolerance of my noobery.
Funnily enough, I tried TitaniumBackup today and the original poster is correct. While you can freeze, remove apps etc, you can't return them. especially system. I've not tried any of the alternative install methods that TB uses, but it's quite interesting.
TB is a bit quirky, I think. The system apps won't restore at all, but sometimes apps that I've downloaded myself will restore and other times they won't (the "Restoring App" notice just hangs there indefinitely). I usually find that forcing TB to close and then trying again does the trick, but I can't figure out why it happens in the first place.
Im wondering if anyone else has worked out a good configuration that will allow it to work every time?
Related
Forgive me if I'm posting in the wrong section. Forgive me if I'm not allowed to post here yet. Just forgive me in general. I don't want to be banned or anything like that. I'm Extremely interested in android development.
I made a working port of ClockworkMod Recovery v5.0.2.8 for the Pantech Crossover. I wanted to do this before I started tinkering around with porting cm7.2. So that I would have a way to backup, restore, and flash new roms, etc... Or else when I make a noob mistake like yesterday and have a non booting phone resulting in having to flash my old boot.img with fastboot...anyways..
DANGER: DRAGONS AHEAD
FLASH AT YOUR OWN RISK
YOU HAVE BEEN WARNED
The method I used to flash the recovery was:
1)adb push recovery.img /sdcard/recovery.img
2)flash_image recovery /sdcard/recovery.img
3)repeat step 2 (for some reason it gave me a read error out of memory the first time)
Here's the link to the custom recovery:
http :// dl. dropbox .com /u/20070520/ recovery.img
I know I'm not supposed to post links yet. Remove spaces
I just hope that there are others with the Pantech Crossover that are interested in this and the possible future development of custom roms.
Also if anyone knows if there is a good way to get ahold of koush let me know, so I can give him what he needs to hopefully add this to Rom Manager. I couldn't message him on github because he doesn't have an email set up with it
And while I'm at it. Here's the method for rooting your crossover. I'm not going to provide the files since they can easily be found with a google search.
1: Find a copy of gingerbreak.apk and copy it to your sd card
2: Enable usb debugging and allow installation of non market apps
3: Install gingerbreak
4: Root device with Gingerbreak
5: You can uninstall Gingerbreak when its completed.
Sent from my rooted PantechP8000 using XDA
Thanks so much for this! I have a friend with a crossover and is always looking for my help with making it work better. I realize this is a newer thread, I was wondering how things were coming along with CM? Anything I can do to help perhaps?
crap i need a rom to fix my crossover the buttons are no longer mapped after a hard reset. please help.
Slow
Well, it's been slow goings so far. I downloaded the open source files for the p8000 and it looks like they just built the original rom from a generic build. I've been trying to get a more customized build setup but I need to do some more reading so far. One of the problems is that instead of an akmd(2) binary for orientation and compass it uses three separate modules. Plus the hci_attach is a bit different as well and so is the bluetooth. So that significantly hampers the ease of even a basic port.
As far as the gentleman with the question about a rom to fix your device. The best I can do right now is to upload a clockwork mod backup after I do a factory reset. I don't get much time to work on this between my wife and daughter.
Also, do you have adb access to your device? Surely it wouldn't be too difficult to adb push the correct keymapping files back to your phone.
You say a hard reset messed up your mappings? What problems were you experiencing prior to the reset?
Crossover
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Yup
kaylus said:
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Click to expand...
Click to collapse
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
stevotdo said:
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
Click to expand...
Click to collapse
I'm actually completely stuck at this point. I'm rooted, unlocked, different carrier, APN set correctly. I can access data and voice -- but it just hangs at "Downloading..." on the market. If I factory reset it works initially but after reboot it fails. I'm not quite sure why this occurs and if it is just this phone or a side-effect of using it on a different carrier.
Strangely Wi-fi doesn't resolve it.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
Click to expand...
Click to collapse
I'll give your recovery a run and let you know, if you manage CM7 let me know I know it's a big undertaking. Thanks for the response.
Market Error
As far as the Android Market hanging. I see a few references to it being cause by the .android_secure folder becoming corrupted on the sd card.
One temporary fix suggest moving all the installed apk's back to the phone memory and deleting the .android_secure folder. Then rebooting and moving those apps back to the sd card.
That seems like some wasted time if it doesn't happen to work. I would just turn the phone off, remove the sdcard, and restart (granted any apps that were moved to the sdcard wont work until it is reinserted.) Then I would try to download and install an app. If that works then shutdown, insert sd, and reboot.
I'm really curious if the problems with .android_secure that you and i are having aren't just more bugs in the original rom.
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Well I appreciate the support. I just hope to be able to offer a rom sometime soon. Unfortunately I won't have anymore free time till Tuesday
crimson12 said:
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Click to expand...
Click to collapse
Not an issue, life first, then android development.
Sent from my Galaxy Nexus using Tapatalk
Pantech Crossover Update
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
stevotdo said:
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
Click to expand...
Click to collapse
Oh hell yes finally. Thanks for the notice!
Sent from my Galaxy Nexus using Tapatalk
Mildly related, but have you figured out how to root the gingerbread ROM? I've tried ginger break to no avail.
Sent from my Galaxy Nexus using Tapatalk 2
anyone have a stock image of the 2.2 for android my phone came preupgraded to 2.3.6 and i would like to have it rooted over being on gingerbread since a root method hasnt been found yet for the new firmware
Bricked?
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
formattdd said:
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
Click to expand...
Click to collapse
Nevermind, bad usb cable.
formattdd said:
Nevermind, bad usb cable.
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Galaxy Nexus using Tapatalk 2
Yeah now I'm having the same regrets as above. No root.
Sent from my PantechP8000 using XDA
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Worked great for me
Sent from my HTC VLE_U using xda premium
So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1
androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.
First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help
I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium
yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.
nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.
the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.
I sent you a PM, trying to find a solution.
On July 20th 2013, I bought a new Verizon Galaxy S3 i535 (no contract due to I need unlimited data). As a 50 year old guy, I admit that I never rooted before. I decided to do some research on the web which also included this XDA site. By the way, this is the best site!!
As someone who never rooted, I found multiple different ways of rooting which caused great confusion. Some told me to download Odin, while some did not. Some told me to download a superSU or something like that, while other directions did not, and so on and on......
But what really concerns me is that most of the directions were written back in 2012. Should this be a concern?
I don't want to seem like a retard or impose, but would someone do a video skype with me and walk me thru rooting my phone for the very first time? Perhaps during that skype session I could ask a few questions? I would pre download all files so that the session would not take too long.
Any volunteers?
Respectfully,
Bryan
All you need to Do is visit this link:
http://forum.xda-developers.com/showthread.php?p=42791826
Those are the most straight forward directions you can find. And it will Root, unlock your bootloader, and install a custom recovery.
thank you for the reply. this is yet another way off rooting. why does this not use Odin? will this method allow me to undo or fix something if something goes bad?
BKSinAZ said:
thank you for the reply. this is yet another way off rooting. why does this not use Odin? will this method allow me to undo or fix something if something goes bad?
Click to expand...
Click to collapse
It doesn't use Odin because it doesn't need to. The one click solution includes all the tools needed to make the necessary changes to your phone.
If something goes wrong, then you would use Odin to go back to stock no matter what root /unlock method you used. This is because Odin has the lowest level access to your phone, and can rescue it as long as you can boot into download mode.
As long as you don't flash files intended for other phones (including s3s from other carriers) your phone should be safe.
Sent from my SCH-I535 using xda app-developers app
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
funnyperson1 said:
It doesn't use Odin because it doesn't need to. The one click solution includes all the tools needed to make the necessary changes to your phone.
If something goes wrong, then you would use Odin to go back to stock no matter what root /unlock method you used. This is because Odin has the lowest level access to your phone, and can rescue it as long as you can boot into download mode.
As long as you don't flash files intended for other phones (including s3s from other carriers) your phone should be safe.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
BKSinAZ said:
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
Click to expand...
Click to collapse
I'm going to pop in here and help out. Once you do the casual root process, it will also install a recovery for you. You can make a nandroid backup with your recovery and just keep that somewhere safe. There are also directions on how to recover and return your phone to Verizon here. Hope that answers your question.
BKSinAZ said:
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
Click to expand...
Click to collapse
No, as I said above, as long as you can reach download mode on your phone you can always Odin back to stock. If you somehow break download mode, then your phone is pretty much bricked without sending it out to someone with a JTAG programmer. The risk of that happenning though is minimal unless you flash a ROM intended for a different device (such as the international i9300 S3).
funnyperson1 said:
No, as I said above, as long as you can reach download mode on your phone you can always Odin back to stock. If you somehow break download mode, then your phone is pretty much bricked without sending it out to someone with a JTAG programmer. The risk of that happenning though is minimal unless you flash a ROM intended for a different device (such as the international i9300 S3).
Click to expand...
Click to collapse
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
BKSinAZ said:
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
Click to expand...
Click to collapse
It sounds like you were successful in rooting and unlocking your phone's bootloader. The program you are seeing (TWRP recovery) allows you to flash roms/mods (install), backup your phone, wipe and restore your phone. However, this shouldn't be what you see on bootup unless you pressed volume up while booting. Your stock ROM may have been wiped during the root process.
I suggest you dive into the world of Custom ROMs with CleanROM which is basically a de-bloated and tweaked version of the stock ROM.
Download the file from here:
http://forum.xda-developers.com/showthread.php?t=1832070
Use your PC to put it on a microSD card. In TWRP recovery, perform a Factory Reset (from the Wipe Menu), then navigate to the external_sdcard and install CleanROM (from install menu). Wipe caches and reboot once installation is finished. You should boot straight into CleanROM.
funnyperson1 said:
It sounds like you were successful in rooting and unlocking your phone's bootloader. The program you are seeing (TWRP recovery) allows you to flash roms/mods (install), backup your phone, wipe and restore your phone. However, this shouldn't be what you see on bootup unless you pressed volume up while booting. Your stock ROM may have been wiped during the root process.
I suggest you dive into the world of Custom ROMs with CleanROM which is basically a de-bloated and tweaked version of the stock ROM.
Download the file from here:
http://forum.xda-developers.com/showthread.php?t=1832070
Use your PC to put it on a microSD card. In TWRP recovery, perform a Factory Reset (from the Wipe Menu), then navigate to the external_sdcard and install CleanROM (from install menu). Wipe caches and reboot once installation is finished. You should boot straight into CleanROM.
Click to expand...
Click to collapse
It seems that when I went into the backup area and made a backup (a backup of what, I do not know because I am totally new to this) and after the backup the phone rebooted to the normal home screen with all the normal icons. I even just received a phone call so I guess all is good.
I don't know what to do now that my phone is rooted. My goal was just to uninstall unwanted programs etc, So when I get the courage, I will use the CLEANROM.
Question.... do I now have to constantly update my existing root or Cleanrom once installed? Do I now avoid Verizon or Samsung updates?
BKSinAZ said:
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
Click to expand...
Click to collapse
If you're not ready to flash roms just touch reboot and you'll be back to your stock jellybean. In regards to the padlock, I also got that after using CASUAL and underneath the padlock it says custom. I haven't gotten a definitive answer about that but the general consensus is that it's nothing to worry about. I suppose it's just Verizon letting you know that they detected changes to your phone.
Do yourself a favor and read for days and days before you start flashing roms. You'll find the answers here and YouTube.
BKSinAZ said:
It seems that when I went into the backup area and made a backup (a backup of what, I do not know because I am totally new to this) and after the backup the phone rebooted to the normal home screen with all the normal icons. I even just received a phone call so I guess all is good.
I don't know what to do now that my phone is rooted. My goal was just to uninstall unwanted programs etc, So when I get the courage, I will use the CLEANROM.
Question.... do I now have to constantly update my existing root or Cleanrom once installed? Do I now avoid Verizon or Samsung updates?
Click to expand...
Click to collapse
Great. The backup you made is what is called a "nandroid" backup. By default it includes the Android System, your apps, and associated application data and settings. This is great because it basically includes everything you need to restore your phone to it's previous state. So if you were to flash a custom ROM and ended up not liking it you could always restore this backup and it would restore your phone to how it is now.
Being rooted allows you to install and use applications from the Play store that require root. There are tons of them. The one I use most often is called Titanium Backup. It's primary purpose it to backup and restore your data and applications on an individual basis. I use it mostly to save my text messages and game save data between ROM flashes. It also allows you to uninstall, wipe data, and freeze (disable) any application on your phone.
Right now since you are still running stock rooted, you want to avoid installing any official updates, otherwise you may have to re-root. Beanstown may have disabled system updates through the rooting method, but I am not sure. If a new update is released, keep your eyes on the forums here, someone will create a flashable zip of the new firmware that maintains root/unlocked bootloader, you can then flash that in TWRP. Also once you flash a custom ROM like CleanROM, they removed the Samsung Firmware updater most likely so you don't have to worry about it.
Hello, I'm a new owner of the AT&T HTC One X(L), purchased just yesterday from a previous owner. I'll try and make this thorough.
The problem is, I'm having a really hard time charging the device today after I let the battery drain all the way down from yesterday from when I purchased it. I've tried charging via USB to my laptop, directly to the wall, while its shut down, sleeping/idle, etc.. and nothing seems to get it charging quick at all. I'm using the stock HTC charger it came with, the previous owner had everything in the box and it's in great cosmetic condition.
The phone does charge some, but it was literally struggling to get between 20% and 35% for most of the day, and then later increased to 50% only to then drop back down again. And I haven't been using it at all, it's just sitting there trying to charge. How long should it reasonably take to charge this phone using the wall adapter?
Is there any chance the installed Android software (is there a custom ROM on the phone perhaps?) is causing this problem? The battery usage report says that 72% has been due to Android.. is that abnormally high by chance?
I've disabled all syncing, WiFi, screen brightness is on low, airplane mode, etc. In fact, the phone isn't even activated yet on my carrier. I've only used it thus far for WiFi at home, the browsing speed of which I'm happy with.
Some other stuff...
Recovery/bootloader reads:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26,2012
On the prior screen it also says "This build is for development purposes only, do not distribute outside of HTC, etc.." and then there's this little flashing "T" logo on the next white screen which shows up briefly before the phone boots up.
Any help would be much appreciated! Thanks for your time and patience.
You mentioned the "T" logo showing up during the boot process which leads me to believe it's running the T-Mobile Germany 4.2.2 stock ROM, which is technically a custom ROM in this context. The device should take about 3-4 hours to charge from zero to full. I personally think you've got a dodgy device. Have you contacted the seller regarding the issues you're having? Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
Sent from my Evita
timmaaa said:
You mentioned the "T" logo showing up during the boot process which leads me to believe it's running the T-Mobile Germany 4.2.2 stock ROM, which is technically a custom ROM in this context. The device should take about 3-4 hours to charge from zero to full. I personally think you've got a dodgy device. Have you contacted the seller regarding the issues you're having? Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. 3-4 hours from 0 to full is somewhat reassuring to hear, I assumed it wouldn't take more than an hour for some reason.
It's not the T-Mo "T" logo, it's a really different looking "T" that has a circle under it and the T flashes different colors. The T almost looks the same as the T in HTC. It only appears for a second or two and then the phone boots up. I need to take a picture of it with another device since it didn't work when I tried screen capturing that boot screen from the phone.
Is there anything else you can confirm one way or another from the info I've provided?
- So this isn't a different 3rd party custom ROM, just possibly one from T-Mo eventhough it's a branded ATT phone?
- Is this bootloader "unlocked" and is that why it says that and "tampered"? From what I've read, that's the standard msg it gives when that's the case, but isn't necessarily a red flag. Am I mistaken in my understanding though?
- Is 72% battery usage allocated to Android too high? If so, what should it be?
- Should I just try factory resetting it from the recovery screen?
droydr said:
Thanks for the reply. 3-4 hours from 0 to full is somewhat reassuring to hear, I assumed it wouldn't take more than an hour for some reason.
It's not the T-Mo "T" logo, it's a really different looking "T" that has a circle under it and the T flashes different colors. The T almost looks the same as the T in HTC. It only appears for a second or two and then the phone boots up. I need to take a picture of it with another device since it didn't work when I tried screen capturing that boot screen from the phone.
Is there anything else you can confirm one way or another from the info I've provided?
- So this isn't a different 3rd party custom ROM, just possibly one from T-Mo eventhough it's a branded ATT phone?
- Is this bootloader "unlocked" and is that why it says that and "tampered"? From what I've read, that's the standard msg it gives when that's the case, but isn't necessarily a red flag. Am I mistaken in my understanding though?
- Is 72% battery usage allocated to Android too high? If so, what should it be?
- Should I just try factory resetting it from the recovery screen?
Click to expand...
Click to collapse
Oh, I'm so dumb. I failed to look at your screenshots properly. The ROM that is installed is the Kickdroid ROM, which is a fully custom ROM that's based on the official Telstra release. The flashing T is the Telstra boot splash.
-Yes, if you see "unlocked" and "tampered" in your bootloader screen it means your bootloader is unlocked and you have root privileges. That's totally normal for a modified device.
-Under normal circumstances that amount of usage attributed to Android System world be considered high, but it all depends on how the phone is being used. If it's only been charging and nothing else has been active then I wouldn't worry very much.
-Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
What would you like to get out of this device? Are you wanting to use custom ROMs or do you want to return it to stock?
Sent from my Evita
timmaaa said:
Oh, I'm so dumb. I failed to look at your screenshots properly. The ROM that is installed is the Kickdroid ROM, which is a fully custom ROM that's based on the official Telstra release. The flashing T is the Telstra boot splash.
-Yes, if you see "unlocked" and "tampered" in your bootloader screen it means your bootloader is unlocked and you have root privileges. That's totally normal for a modified device.
-Under normal circumstances that amount of usage attributed to Android System world be considered high, but it all depends on how the phone is being used. If it's only been charging and nothing else has been active then I wouldn't worry very much.
-Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
What would you like to get out of this device? Are you wanting to use custom ROMs or do you want to return it to stock?
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply.
- Ok cool. I searched online for the Telstra logo and their T logo is for sure the one that I'm seeing. I'm assuming you don't suspect this to be the cause of the charging issue.
- So the device is unlocked and rooted, sounds fine as long as it isn't the source of the problem.
- I know this is a dumb question, but is there an ideal way for the phone to be charged? Does it need to be shut down completely for it to charge the fastest or even fully? Or can it be sleeping/idling and charge at the same rate? I've read about a variety of battery draining issues with respect to the HOX, but most are centered around WiFi and LTE uses where people were getting connected and disconnected which then caused a massive drain and bad overheating. I've yet to read something specifically about incredibly slow charging however.
My goals with this device:
- Just for it to function well and do the basics, I'm a very simple user.. calls, texts, and mild data use. I want to be able to charge it nightly within that 3-4 hour estimate and don't want any major battery issues and overheating. Today is literally my first full day with it and the first thing I needed to do was charge it, so I feel stuck at the beginning until this is resolved.
- I want to activate it on a wireless plan so it can really become my new phone, but I don't want to start this process if there's a permanent hardware or software issue with the device.
- I don't need to be on any custom ROM or on kitkat. I'm not a developer or anywhere close to being an Android wizard. I read that 4.2.2 is the last official update the HOX will receive, so I'd be absolutely fine with that. Sure, running kitkat or later Android versions might be nice down the road, but if it becomes clear that any custom ROM (now or in the future) is doing more damage than good, then I'd just want to be able to get it back to the 4.2.2 version HTC has released. I want to have that safety measure at bare minimum.
Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
Ok thanks, I won't select the factory reset option from bootloader. However, I don't have an SD card in the phone and I don't think there's an SD slot on it unless I'm totally missing something?
I need to read about what TWRP recovery is and see if it's installed on my phone. Will need to get back to you on that once the phone has had more time to charge - I just want to let it sit undisturbed for 3-4 hours in shut down mode and see if it can increase past a 50% charge rate.
I only inquired about a factory reset thinking that it might be the safest way for me to start trying to troubleshoot the charging problem. It was just a random question I threw out there. I'm willing to do anything that could potentially improve my charging situation.
Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
- After reviewing my screenshots again, do you feel this is still the case? Is there mismatched software and radios afterall? And if so, would the factory reset via TWRP be one of your first suggestions to try and fix it?
- Do you think such mismatching software could potentially be the cause of its slow battery charging?
- Finally, is there any way for me to check to see if the battery itself is in good shape or faulty? Is there an app you could recommend I download where it can give me a detailed performance report which I could then share the results?
Thank you so much for your time, help, and continued patience.. it means a lot!
droydr said:
Thanks for the reply.
- Ok cool. I searched online for the Telstra logo and their T logo is for sure the one that I'm seeing. I'm assuming you don't suspect this to be the cause of the charging issue.
- So the device is unlocked and rooted, sounds fine as long as it isn't the source of the problem.
- I know this is a dumb question, but is there an ideal way for the phone to be charged? Does it need to be shut down completely for it to charge the fastest or even fully? Or can it be sleeping/idling and charge at the same rate? I've read about a variety of battery draining issues with respect to the HOX, but most are centered around WiFi and LTE uses where people were getting connected and disconnected which then caused a massive drain and bad overheating. I've yet to read something specifically about incredibly slow charging however.
Click to expand...
Click to collapse
The phone should charge fine while powered on, in fact I probably would recommend that because that way you can periodically check the progress. The slow charging could be due to a faulty battery or charger, not usually by a ROM though. The fact that it's unlocked should have absolutely nothing to do with it.
My goals with this device:
- Just for it to function well and do the basics, I'm a very simple user.. calls, texts, and mild data use. I want to be able to charge it nightly within that 3-4 hour estimate and don't want any major battery issues and overheating. Today is literally my first full day with it and the first thing I needed to do was charge it, so I feel stuck at the beginning until this is resolved.
- I want to activate it on a wireless plan so it can really become my new phone, but I don't want to start this process if there's a permanent hardware or software issue with the device.
- I don't need to be on any custom ROM or on kitkat. I'm not a developer or anywhere close to being an Android wizard. I read that 4.2.2 is the last official update the HOX will receive, so I'd be absolutely fine with that. Sure, running kitkat or later Android versions might be nice down the road, but if it becomes clear that any custom ROM (now or in the future) is doing more damage than good, then I'd just want to be able to get it back to the 4.2.2 version HTC has released. I want to have that safety measure at bare minimum.
Click to expand...
Click to collapse
You can leave Kickdroid on the phone, it will serve your needs and then some. However, you do need to do a little work to get the firmware up to date. You'll need to get s-off, which can be done pretty easily using the Rumrunner method. Then you need to flash the 2.15 firmware found in the beginning of this thread. You will need adb/fastboot installed on your PC, the easiest way is to Google search "minimal adb and fastboot", the first result will be the thread you're looking for. In order for adb/fastboot to work you need HTC drivers installed on your PC too, you can get those by installing HTC Sync Manager.
Under no circumstances should you ever perform a factory reset from the bootloader, it will corrupt your sd card. A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader. At this stage I don't think you should perform a factory reset until we've determined what you want from the device.
Ok thanks, I won't select the factory reset option from bootloader. However, I don't have an SD card in the phone and I don't think there's an SD slot on it unless I'm totally missing something?
Click to expand...
Click to collapse
There is no physical sd card slot. When people refer to the sd card we mean the virtual sd card (or internal storage).
I need to read about what TWRP recovery is and see if it's installed on my phone. Will need to get back to you on that once the phone has had more time to charge - I just want to let it sit undisturbed for 3-4 hours in shut down mode and see if it can increase past a 50% charge rate.
I only inquired about a factory reset thinking that it might be the safest way for me to start trying to troubleshoot the charging problem. It was just a random question I threw out there. I'm willing to do anything that could potentially improve my charging situation.
Click to expand...
Click to collapse
TWRP is a custom recovery that can be used for various tasks. You can make a full backup of your current system, you can restore a backup you've made. You can wipe the entire system (a task that takes place prior to flashing a ROM), or just parts. You can install a ROM, kernel, radio, or various other things.
Whoever had it previously didn't know what they were doing, it has a mismatched radio/firmware version for the ROM that's installed.
- After reviewing my screenshots again, do you feel this is still the case? Is there mismatched software and radios afterall? And if so, would the factory reset via TWRP be one of your first suggestions to try and fix it?
Click to expand...
Click to collapse
A factory reset won't help that issue, a factory reset basically removes all user data from the device. The mismatch is happening at a much lower level and can only be remedied by flashing the 2.15 firmware I mentioned above.
- Do you think such mismatching software could potentially be the cause of its slow battery charging?
Click to expand...
Click to collapse
No, I don't believe that is the case. Have you tried using a different charger and/or cable? It might be the charger that's the issue. You should only charge from an AC outlet as charging via usb from a PC or the like takes longer due to restrictions on the output.
- Finally, is there any way for me to check to see if the battery itself is in good shape or faulty? Is there an app you could recommend I download where it can give me a detailed performance report which I could then share the results?
Thank you so much for your time, help, and continued patience.. it means a lot!
Click to expand...
Click to collapse
I'm not familiar with any apps myself but I know there are many that claim to be able to report the health of the battery.
Sent from my Evita
timmaaa said:
You can leave Kickdroid on the phone, it will serve your needs and then some. However, you do need to do a little work to get the firmware up to date. You'll need to get s-off, which can be done pretty easily using the Rumrunner method. Then you need to flash the 2.15 firmware found in the beginning of this thread. You will need adb/fastboot installed on your PC, the easiest way is to Google search "minimal adb and fastboot", the first result will be the thread you're looking for. In order for adb/fastboot to work you need HTC drivers installed on your PC too, you can get those by installing HTC Sync Manager.
Click to expand...
Click to collapse
Thanks again for the reply and all the detail. This section appears to be my 'to do' list but I've been going around in circles with it for a few hours now with no results. The first problem is that Sync Manager on my computer won't recognize my device, it says no phone is plugged in yet my computer makes that alert sound when something new is connected via USB. I'm on a new Windows 8.1 laptop and can't figure it out for the life of me. Apparently this is an issue for others, as I've found out by cross reading HTC and Android forums about it. I don't know if there's some setting on the HOX itself I'm missing in order to start the sync process with my laptop or if it's a Windows issue, but I'm not getting anywhere.
I've read and followed the other pages you listed as well to do the S-off, ADB and fastboot, and ultimately the 2.15 firmware update, but even the 2nd step (S-off) fails because I can't get the darn Sync Mgr to work.
At this point, I would just like to get it back to how it was when the device was opened for the first time with Android 4.0.3. This is an AT&T branded phone for the USA, I don't want it to have anything to do with Telstra or Australian regions. I don't want any kind of custom ROM, radios, kernels, etc.
If I'm understanding you correctly, I can't factory reboot this to the way it originally came out of the box. By it being unlocked and rooted with technically a custom ROM, apparently it's past the point of no return.. I either get it to work via custom ROM or it'll be stuck as is.
I just want it to be true stock. And then once I'm comfortable with that and it's hopefully functioning better, I can then update it to the next Android releases that come directly from ATT. It's crazy how impossible that seems to achieve at this point.
droydr said:
Thanks again for the reply and all the detail. This section appears to be my 'to do' list but I've been going around in circles with it for a few hours now with no results. The first problem is that Sync Manager on my computer won't recognize my device, it says no phone is plugged in yet my computer makes that alert sound when something new is connected via USB. I'm on a new Windows 8.1 laptop and can't figure it out for the life of me. Apparently this is an issue for others, as I've found out by cross reading HTC and Android forums about it. I don't know if there's some setting on the HOX itself I'm missing in order to start the sync process with my laptop or if it's a Windows issue, but I'm not getting anywhere.
I've read and followed the other pages you listed as well to do the S-off, ADB and fastboot, and ultimately the 2.15 firmware update, but even the 2nd step (S-off) fails because I can't get the darn Sync Mgr to work.
At this point, I would just like to get it back to how it was when the device was opened for the first time with Android 4.0.3. This is an AT&T branded phone for the USA, I don't want it to have anything to do with Telstra or Australian regions. I don't want any kind of custom ROM, radios, kernels, etc.
If I'm understanding you correctly, I can't factory reboot this to the way it originally came out of the box. By it being unlocked and rooted with technically a custom ROM, apparently it's past the point of no return.. I either get it to work via custom ROM or it'll be stuck as is.
I just want it to be true stock. And then once I'm comfortable with that and it's hopefully functioning better, I can then update it to the next Android releases that come directly from ATT. It's crazy how impossible that seems to achieve at this point.
Click to expand...
Click to collapse
I should have been more clear, you don't actually want Sync Manager to work, you only wanted to install that to get the drivers. Your main obstacle is actually Windows 8.1, it isn't compatible with fastboot drivers. If you can get access to a PC with a lower version of Windows you should be fine. Then getting s-off should be pretty easy.
Kickdroid doesn't really have anything to do with the Australian region or Telstra as such. The dev merely used a Telstra ROM as a base to build Kickdroid onto.
Are you sure you actually want an at&t release? You may not be aware but at&t releases actually have features that are missing and deliberately broken. That's the only difference between running an at&t ROM and a non at&t ROM, you'll be missing features.
You can easily flash a ROM that is an earlier Android version without having to update the firmware on the device. You don't have to go back to ICS, anything that's from 4.0 up to and including 4.1 will be perfectly fine without any further modification. Have a look through our Android Development section and find one you think will suit you. There are plenty of ROMs in our development section that range from completely stock to customised. That's about as close to stock as you can get without getting s-off first.
Sent from my Evita
timmaaa said:
A factory reset should only be performed from within TWRP recovery, you can check if this is installed by selecting the recovery option from your bootloader.
Click to expand...
Click to collapse
I forgot to mention that I checked on this. When I selected Recovery from the bootloader screen, it took me to ClockworkMod Recovery v6.0.4.6 which I imagine you're familiar with in one way or another. It has 7 different options from its menu.. "reboot system now, install zip, wipe data/factory reset, wipe cache partition, backup and restore, mounts and storage, advanced". After researching it, I know it's a different app than TWRP so I didn't do anything with it per your advice.
You can use CWM if you want to, TWRP is better but it's entirely up to you. You can easily change by using this app:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Sent from my Evita
timmaaa said:
Kickdroid doesn't really have anything to do with the Australian region or Telstra as such. The dev merely used a Telstra ROM as a base to build Kickdroid onto.
Click to expand...
Click to collapse
Thanks for clearing that up. So it makes no difference if I have a Telstra or ATT logo on boot up. It just threw me for a loop is all because when you asked about it initially, I started thinking.. "yeah, why doesn't it have the ATT logo and does that have anything to do with my charging problem?"
timmaaa said:
Are you sure you actually want an at&t release? You may not be aware but at&t releases actually have features that are missing and deliberately broken. That's the only difference between running an at&t ROM and a non at&t ROM, you'll be missing features.
Click to expand...
Click to collapse
No, I'm not sure at all, that's why this is such a guessing game for me at this point. I'm just thinking that if I can just get things back to 'stock' first, then later I can move on and get involved in the custom ROM stuff if it sounds promising.
Ideally, I want to have freedom with my device and not be at the mercy of any carrier.. that's what interests me about Android to begin with, but right now I'm a little weary of what may be going on with my 'new' HOXL.
timmaaa said:
You can easily flash a ROM that is an earlier Android version without having to update the firmware on the device. You don't have to go back to ICS, anything that's from 4.0 up to and including 4.1 will be perfectly fine without any further modification. Have a look through our Android Development section and find one you think will suit you. There are plenty of ROMs in our development section that range from completely stock to customised. That's about as close to stock as you can get without getting s-off first.
Click to expand...
Click to collapse
Thanks, I will look at that section next. I like the idea that I can potentially get back to something earlier right now even with my current situation. I've been focused on trying to do all the steps you outlined yesterday to fix what I have currently. Of course I would like to be on the 'latest' ROM that makes the HOXL run most efficiently, but perhaps baby steps to start off with would be best.
My goal right now is to simply make sure all my software, firmware, radios, kernels match up. What you said in the beginning about my phone currently being mis-matched really stood out to me and I badly want to fix that. Logically, I absolutely must have a stable, synchronized OS at bare minimum.
droydr said:
Thanks for clearing that up. So it makes no difference if I have a Telstra or ATT logo on boot up. It just threw me for a loop is all because when you asked about it initially, I started thinking.. "yeah, why doesn't it have the ATT logo and does that have anything to do with my charging problem?"
No, I'm not sure at all, that's why this is such a guessing game for me at this point. I'm just thinking that if I can just get things back to 'stock' first, then later I can move on and get involved in the custom ROM stuff if it sounds promising.
Ideally, I want to have freedom with my device and not be at the mercy of any carrier.. that's what interests me about Android to begin with, but right now I'm a little weary of what may be going on with my 'new' HOXL.
Thanks, I will look at that section next. I like the idea that I can potentially get back to something earlier right now even with my current situation. I've been focused on trying to do all the steps you outlined yesterday to fix what I have currently. Of course I would like to be on the 'latest' ROM that makes the HOXL run most efficiently, but perhaps baby steps to start off with would be best.
My goal right now is to simply make sure all my software, firmware, radios, kernels match up. What you said in the beginning about my phone currently being mis-matched really stood out to me and I badly want to fix that. Logically, I absolutely must have a stable, synchronized OS at bare minimum.
Click to expand...
Click to collapse
The mismatch I mentioned earlier exists only for 4.2.2 ROMs, basically any 4.2.2 ROM requires a certain set of firmware to be installed otherwise the phone will suffer signal losses and random reboots.
As another easier option you could just install the Beastmode Reloaded kernel, which is also a workaround for those problems. That way you can keep the ROM that's already installed and be up to date.
Sent from my Evita
timmaaa said:
The mismatch I mentioned earlier exists only for 4.2.2 ROMs, basically any 4.2.2 ROM requires a certain set of firmware to be installed otherwise the phone will suffer signal losses and random reboots.
As another easier option you could just install the Beastmode Reloaded kernel, which is also a workaround for those problems. That way you can keep the ROM that's already installed and be up to date.
Sent from my Evita
Click to expand...
Click to collapse
I found this thread, I assume this is what you're talking about?
http://forum.xda-developers.com/showthread.php?t=2165880
I see on page 73 the link for the 3.5 version. Now I need to figure out how to install this. Do I first DL something onto my computer and then send it to the phone somehow with the USB cable, or am I suppose to do this directly on the HOXL? I've never flashed or installed anything like this before. I'll I've done thus far is install some apps from Google Play.
Yes that's the right one. You can download it directly to the phone, or download it to the PC and transfer it to the phone.
If downloading it to your PC and using TWRP recovery, you can connect your phone to the PC using a usb cable, select mount from the TWRP main menu, then select mount usb storage and your phone will show up as a removable drive on your PC. Copy the file across, eject the removable drive, unmount usb storage from the phone screen and then you can install.
Go back to the TWRP home screen and select install, navigate to the file and select it, swipe to install (at this point an aroma installer will commence, select the options you would like, don't let it reboot system at the end), select wipe cache/dalvik, swipe to wipe, hit back, hit reboot system. Now the phone will reboot into the OS again and that's it.
Sent from my Evita
timmaaa said:
Yes that's the right one. You can download it directly to the phone, or download it to the PC and transfer it to the phone.
If downloading it to your PC and using TWRP recovery, you can connect your phone to the PC using a usb cable, select mount from the TWRP main menu, then select mount usb storage and your phone will show up as a removable drive on your PC. Copy the file across, eject the removable drive, unmount usb storage from the phone screen and then you can install.
Go back to the TWRP home screen and select install, navigate to the file and select it, swipe to install (at this point an aroma installer will commence, select the options you would like, don't let it reboot system at the end), select wipe cache/dalvik, swipe to wipe, hit back, hit reboot system. Now the phone will reboot into the OS again and that's it.
Sent from my Evita
Click to expand...
Click to collapse
I downloaded the 3.5 zip file from page 73 directly to my phone.
And then I followed your install instructions exactly and now my phone keeps turning on and off without being able to boot all the way. It starts on the white "T" logo Telstra screen and then goes to the white HTC screen and then turns off again. It's been doing this nonstop for the last 20 minutes or so now. I'm assuming I have a big problem? The device is unusable at this point, it just keeps turning on and off and is getting very warm all over.
droydr said:
I downloaded the 3.5 zip file from page 73 directly to my phone.
And then I followed your install instructions exactly and now my phone keeps turning on and off without being able to boot all the way. It starts on the white "T" logo Telstra screen and then goes to the white HTC screen and then turns off again. It's been doing this nonstop for the last 10 minutes or so. I'm assuming I have a problem? The device is unusable at this point, it just keeps turning on and off.
Click to expand...
Click to collapse
There are a small number of devices for which Beastmode isn't compatible, it looks like you've lucked out and have one of those devices. Out of interest, which settings did you choose during the installer?
You can get out of the boot loop by just continuing to hold the volume down button, the next time the loop starts it should enter the bootloader.
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
PS. I noticed you posted the same thing in the Beastmode thread too, duplicate posts are against the rules here on XDA.
Sent from my Evita
---------- Post added at 03:29 AM ---------- Previous post was at 03:24 AM ----------
Because you're s-on you are going to need to get access to a PC that runs a lower version of Windows, you need to have a working adb/fastboot environment. Flashing a ROM is going to require you to also flash the boot.img from the ROM zip using fastboot, this is a limitation on s-on devices with a hboot later than 1.14.
Sent from my Evita
timmaaa said:
There are a small number of devices for which Beastmode isn't compatible, it looks like you've lucked out and have one of those devices. Out of interest, which settings did you choose during the installer?
You can get out of the boot loop by just continuing to hold the volume down button, the next time the loop starts it should enter the bootloader.
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
PS. I noticed you posted the same thing in the Beastmode thread too, duplicate posts are against the rules here on XDA.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. I wasn't sure you were going to see this anytime soon, so I wanted to post it in that kernel thread as well just in case anyone was reading over there. I apologize for that.
I chose the default settings during installation.
Anyway, I've been holding down the volume button now for the last few minutes and it's not entering bootloader. The loop continues.
There's no other way to get to the bootloader apart from holding volume down or trying the volume down + power combination. I also added a little to my previous post which you'll need to read.
Sent from my Evita
timmaaa said:
There's no other way to get to the bootloader apart from holding volume down or trying the volume down + power combination. I also added a little to my previous post which you'll need to read.
Sent from my Evita
Click to expand...
Click to collapse
I saw the added parts, thanks. Problem is, this forum isn't allowing me to post or edit my previous posts until 5 mins have past, so it's a struggle trying to communicate.
I've also edited my post in the beastmode thread.
Anyway, I finally got into bootloader with the volume + power combo. Feels good to at least achieve that.
FYI, my bootloader screen looks the same as when I first got the phone a few days ago. Just wanted to include this info here.
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26,2012
Just curious, now that I'm in bootloader, would it do me any good if I selected Recovery so it can then take me to Clockwork? And from there I could try rebooting? Or one of the other menu options?
At this point you have no choice but to flash another ROM, so I'd head to the development section I linked you to earlier and find a 4.1 ROM that you think you might like and flash that.
Because you're s-on you are going to need to get access to a PC that runs a lower version of Windows, you need to have a working adb/fastboot environment. Flashing a ROM is going to require you to also flash the boot.img from the ROM zip using fastboot, this is a limitation on s-on devices with a hboot later than 1.14.
Click to expand...
Click to collapse
I've found this ROM which looks fine. I'm not picky. I'd be happy with anything as long as it can get my device to function again.
http://forum.xda-developers.com/showthread.php?t=2244445
If there's a better 4.1 ROM you'd like to suggest, please feel free to do so.
Hello,
Pretty new to rooting, tried to root my HTC Vivid to install some apps which are "incompatible" with my device. Unlocked bootloader and rooted successfully by installing TWRP recovery and installing the supersu zip. After copying the build.prop file to another folder I proceeded to make some minor changes to the build.prop file with ES File Explorer. Essentially changing the model ID of the phone to another device to try to prompt Google Play to show the incompoatible apps, didn't touch anything boot-related or anything else. Phone was working fine at that point, rebooting ok, but Google Play still showed the apps as incompatible, so I temporarily brought back the old build.prop file by copy/pasting it from the folder I made. The system indicated the copy was made successfully, and I tried to reboot once more. That is where the problem started.
When the power button is pressed for a second or so, the phone vibrates once and shows the starting splash screen (HTC) as it did when working, and then the screen goes blank, although the LED backlight is still on (so phone has power). Nothing comes after, no "HTC quietly brilliant" logo nor the chime that indicates it's booting up. At that point it stops responding to any stimulus except the removal of the battery, at which point the LED backlight finally goes off. Waiting for ~10min solved nothing, still blank black screen with backlight on. Upon reinserting the battery, the phone once again responds to the power button, with the same results.
I can boot to recovery by holding down Vol down and pressing power, and there I get the usual options including Fastboot, Recovery, etc. I tried doing a factory reset. It gives a bunch of error messages along the lines of "can't mount emmc", then says it's starting the reset, and gives a successful completion prompt after half a minute or so. However, that seems to do nothing at all to fix the problem (tried 4x times, with SD card in and out).
The only change that comes to mind is the last replacement of the build.prop file I did, which should have just restored the original. Assuming the factory reset doesn't actually reset that file (where would it get a copy to do so?) perhaps it being broken is preventing me from booting after the reset. Just my theory though, and could be something else.
From what I understand I could try putting a recovery image on the micro sd from a PC, then doing a recovery rather than a factory reset from the TWRP menu to replace all the files, including the potentially problematic build.prop. However, I didn't make a backup of the system before this happened (learning experience) and have no such image. Could anyone perhaps point me to a clean image for the Vivid that I could download and flash to my phone with recovery? Or otherwise shed some light on what could be causing the problem? I also realize there are various unbricking tutorials online, but after many hours of this I'm a bit too exhausted to follow all of those just to see if they work or not.
Edit: Upon further research I realize I can try to flash a new rom to the Vivid, but no matter how much I search I can't find a working link for a stock ICS .zip. There is a RUU .exe file from HTC but my phone can't get past fastboot, so I'd need to do this with a zip file. Anywhere I can get a working one? I could also try a custom rom, I just have 0 knowledge of those so don't know which would be a safe bet.
Would appreciate any help, and hope the post isn't overly long. Tried to give as much info as I could. I already spent a ton of time on both the root procedure and trying to fix this and would really like to hear professional opinions before breaking anything else. Thanks for reading.
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
jd1639 said:
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
Click to expand...
Click to collapse
Thanks for the advice, I basically got into rooting from scratch a day ago, so many resources I don't know about. Trying to return to stock, but I need a rom of the stock in .zip form since the phone can't get past recovery, and having trouble finding that. Perhaps due to age of phone, but most links to those seem to no longer be functional.
rohanreddy277 said:
Actually u shouldnt have rooted with that zip file containing supersu u actually should have done it with kingo root. anyway, the best waty to revive it is to install cyanogenmod. download the version for ur device and google how to install cyanogenmod. this will give a new life to ur phone. hope it helps.
Click to expand...
Click to collapse
Right, I basically learned as I went along for this root, haven't even heard of kingo before. I was very careful, but apparently something still went wrong. Thanks for the suggestion, I'll try that mod and see if it works.
Edit: I'm only finding a nightly build for the Vivid on the CyanogenMod website, with no stable versions. Nightly build is dated two years ago, so clearly no stable versions coming. While I'm in no position to be picky, and I'll try it if needed, I'd rather not break what's still functioning in my phone. Any mods out there that are stable for the Vivid?
Edit2: the nightly cyanogen build seems to have brought the phone back online, but besides the different look and feel from what I'm used to, it doesn't seem to have Google Play... so I can't download anything. It also isn't seen by HTC Sync so I can't run the RUU from there, but I did successfully extract the rom.zip file using some instruction on this forum from the stock ICS RUU .exe. However, installing that from twrp recovery fails as it cannot open the zip, and an attempt to use the "fastboot flash zip rom.zip" command fails saying it's not allowed. Integrity of zip fail is tested to be ok with an archiver program. The zip file extracts properly, and I can flash things like boot.img and recovery_signed.img to the phone, yet system.img cannot be flashed (data length too large error). Not sure what to try next.
Thread closed.