Ok. First let me say a long time ago when Coredroid 8.1 had kinda first came out. I tried to flash the Unity Kernel I believe. It just stuck my phone at the HTC logo screen. So i said forget it and tried to go back but couldnt. So sumbody helped me to get pdgimg.zip (think thats how u spell it im in a rush) file and told me how to install it so my phone would come back up normally. <--now its slip my mind how too.. So any who.
Well i am having the same problem again except i flashed lordmod 5.6. Now that has stuck my phone as well. So once again i need help to clear this situation by gettin the pdgimg.zip file or answerin a questionable thought i have. Could i actually reflash Cordroid 8.1 over the Same CD 8.1 again and not loose text messages or anything installed up to this point ?
Meercy said:
Ok. First let me say a long time ago when Coredroid 8.1 had kinda first came out. I tried to flash the Unity Kernel I believe. It just stuck my phone at the HTC logo screen. So i said forget it and tried to go back but couldnt. So sumbody helped me to get pdgimg.zip (think thats how u spell it im in a rush) file and told me how to install it so my phone would come back up normally. <--now its slip my mind how too.. So any who.
Well i am having the same problem again except i flashed lordmod 5.6. Now that has stuck my phone as well. So once again i need help to clear this situation by gettin the pdgimg.zip file or answerin a questionable thought i have. Could i actually reflash Cordroid 8.1 over the Same CD 8.1 again and not loose text messages or anything installed up to this point ?
Click to expand...
Click to collapse
Please search first since there are a lot of threads that will get you that pd98img.zip. I'm pretty sure Ze has a stock thread open that gives you links to the PD98IMG.zip that can be flashed through HBOOT...if not like I said search as there are a lot of threads out there that can get you what you need.
As for stuck, please be more specific so we can better help you out. Can you get into HBOOT? can you get into recovery through HBOOT? do you have pd98img.zip already on your sdcard?
well actually i did research. but its not actually wat i was looking to do in general.
i was specific about how i was stuck and a thought i had to see if it could be done. But i would rather you just say be more detailed. With that said. Im running Coredroid 8.1. I have been having the stuck at the htc logo screen and having to pull the battery when i do decide to restart my phone. (which i been had the problem but it was never fixed) I have seen multiple of kernels to flash to stop the stuck at the htc logo screen. Basically i tried this b4 and it didnt work and i tried it again and it didnt work. I flashed lordmod 5.6 kernel this time by the way. So my question was is this fixable to the point where i actually could flash a kernel and it wouldnt stay stuck at the htc screen *FOREVER* or is there no chance ? But since i didnt wait i ended up reflashing Coredroid 8.1 again so i could get my phone back working thinking i might not loose anything. But i did.
but to answer yo question i can get into recovery.
You can't just flash any kernel.I have a feeling that your trying to flash an aosp kernel on a sense rom, which as you have discovered your not suppose to do. I'm not sure which kernels work with coredroid but I would read up on the thread to see what other people have tried
Any reason why you have not backed up apps and SMS, full wipe, and install fresh? I use Titanium Backup for backing up my apps and system data, and SMS Backup & Restore (free on market) to backup and restore my texts. Use google or HTC Sync or whomever to keep your calendar and contacts backed up.
It's a little bit of a process, but I'm more than certain it would help fix your issue. Seems there's something latent that's causing a hang up that needs to be cleared out. You could troubleshoot that all day long and never get a fix. Just start fresh.
Meercy said:
well actually i did research. but its not actually wat i was looking to do in general.
i was specific about how i was stuck and a thought i had to see if it could be done. But i would rather you just say be more detailed. With that said. Im running Coredroid 8.1. I have been having the stuck at the htc logo screen and having to pull the battery when i do decide to restart my phone. (which i been had the problem but it was never fixed) I have seen multiple of kernels to flash to stop the stuck at the htc logo screen. Basically i tried this b4 and it didnt work and i tried it again and it didnt work. I flashed lordmod 5.6 kernel this time by the way. So my question was is this fixable to the point where i actually could flash a kernel and it wouldnt stay stuck at the htc screen *FOREVER* or is there no chance ? But since i didnt wait i ended up reflashing Coredroid 8.1 again so i could get my phone back working thinking i might not loose anything. But i did.
but to answer yo question i can get into recovery.
Click to expand...
Click to collapse
HAHA, I absolutely love how every person gets sooo defensive when someone tries to help them. Stop taking everything so personal. I said research more because it seems you flashed an AOSP kernel to a sense ROM. This is a common mistake for Lordmod kernel flashers and I'm guilty of it myself. I answered everything but the MMS back-up. There is no need for a PD98IMG.zip if you can into recovery, which is exactly why I asked if you could provide more detail because if you can get into recovery, you don't need to go through the HBOOT method of flashing a stock ROM. Did you back-up your ROM before flashing the kernel like recommended, because if you did then you could just restore your back-up from recovery and back-up your MMS.
marsdta said:
You can't just flash any kernel.I have a feeling that your trying to flash an aosp kernel on a sense rom, which as you have discovered your not suppose to do. I'm not sure which kernels work with coredroid but I would read up on the thread to see what other people have tried
Click to expand...
Click to collapse
and thats proly wat happened. ill try to see if i can find a kernel that i could flash to return it to working condition. If thats possible ?
anudist said:
Any reason why you have not backed up apps and SMS, full wipe, and install fresh? I use Titanium Backup for backing up my apps and system data, and SMS Backup & Restore (free on market) to backup and restore my texts. Use google or HTC Sync or whomever to keep your calendar and contacts backed up.
It's a little bit of a process, but I'm more than certain it would help fix your issue. Seems there's something latent that's causing a hang up that needs to be cleared out. You could troubleshoot that all day long and never get a fix. Just start fresh.
Click to expand...
Click to collapse
well honestly the only thing i was initially was worried bout was my text. cause i had sum important things to keep. i did have wat i want saved but not quite up to date. i usually back up all the time but i was a bit in a hurry process because im about to get a new phone and i wanted to make sure this one runs smooth. so this was a mistake i made with out thinkin it all the way through.
MMM-BACONSTRIPS said:
HAHA, I absolutely love how every person gets sooo defensive when someone tries to help them. Stop taking everything so personal. I said research more because it seems you flashed an AOSP kernel to a sense ROM. This is a common mistake for Lordmod kernel flashers and I'm guilty of it myself. I answered everything but the MMS back-up. There is no need for a PD98IMG.zip if you can into recovery, which is exactly why I asked if you could provide more detail because if you can get into recovery, you don't need to go through the HBOOT method of flashing a stock ROM. Did you back-up your ROM before flashing the kernel like recommended, because if you did then you could just restore your back-up from recovery and back-up your MMS.
Click to expand...
Click to collapse
sorry if u thought that was defensive O_O ? i just responded more directly because u asked. i sort of had a quick question and thought i would get a quick answer. that is all really. But i did not back up my room before the kernel flash because i was actually in the coredroid forum and was seeing ppl sayin wat room to flash to stop the hang at the boot screen. So i thought maybe it would work. But since it didnt my nly question would be which kernel would work at this point so i could ? if possible ? if not then i can deal with it. not problem. mistakes are made and lessons are learned.
Meercy said:
and thats proly wat happened. ill try to see if i can find a kernel that i could flash to return it to working condition. If thats possible ?
well honestly the only thing i was initially was worried bout was my text. cause i had sum important things to keep. i did have wat i want saved but not quite up to date. i usually back up all the time but i was a bit in a hurry process because im about to get a new phone and i wanted to make sure this one runs smooth. so this was a mistake i made with out thinkin it all the way through.
sorry if u thought that was defensive O_O ? i just responded more directly because u asked. i sort of had a quick question and thought i would get a quick answer. that is all really. But i did not back up my room before the kernel flash because i was actually in the coredroid forum and was seeing ppl sayin wat room to flash to stop the hang at the boot screen. So i thought maybe it would work. But since it didnt my nly question would be which kernel would work at this point so i could ? if possible ? if not then i can deal with it. not problem. mistakes are made and lessons are learned.
Click to expand...
Click to collapse
Understandable, like I said I've flashed AOSP kernels to Sense ROMs and it's never a great combo. ever, lol. When I used CD 8.1 I was using the Unity Kernel as well, but that was like 3 months ago and since i believe there has been some updates to that kernel. I know I had some good luck with RCMix kernels as well.
MMM-BACONSTRIPS said:
Understandable, like I said I've flashed AOSP kernels to Sense ROMs and it's never a great combo. ever, lol. When I used CD 8.1 I was using the Unity Kernel as well, but that was like 3 months ago and since i believe there has been some updates to that kernel. I know I had some good luck with RCMix kernels as well.
Click to expand...
Click to collapse
So could the Unity Kernel Or RCMix Kernel cure my problem ? Thats the only thing left for me to try i believe. Plus it would be which kernel update is the right one.
Meercy said:
So could the Unity Kernel Or RCMix Kernel cure my problem ? Thats the only thing left for me to try i believe. Plus it would be which kernel update is the right one.
Click to expand...
Click to collapse
Tough to say really, I know I had this problem when I flashing kernels when i first started with AOSP ROMs, what I learned was to not mess with them. I would say try to latest RCMIX kernel and see if that helps. If it doesn't. Full wipe and reflash CD 8.1 and see if the problems persists..It may just be worth it not to flash a kernel haha, I know that's not really a solution but at least your phone won't be hanging on the white screen.
MMM-BACONSTRIPS said:
Tough to say really, I know I had this problem when I flashing kernels when i first started with AOSP ROMs, what I learned was to not mess with them. I would say try to latest RCMIX kernel and see if that helps. If it doesn't. Full wipe and reflash CD 8.1 and see if the problems persists..It may just be worth it not to flash a kernel haha, I know that's not really a solution but at least your phone won't be hanging on the white screen.
Click to expand...
Click to collapse
yea ill try that out. See if it works. Ill jus save all my stuff this time because i actually just reflashed CD 8.1 and its been fine. Actually its not getting hung up on the white screen at all. But hopefully a kernel flash will work. if not then wats done is done.
Meercy said:
yea ill try that out. See if it works. Ill jus save all my stuff this time because i actually just reflashed CD 8.1 and its been fine. Actually its not getting hung up on the white screen at all. But hopefully a kernel flash will work. if not then wats done is done.
Click to expand...
Click to collapse
Yeah backing up is always a great idea haha, another lesson for me learned the hard way. Glad to hear its working in the interim though, good luck sir!
MMM-BACONSTRIPS said:
Yeah backing up is always a great idea haha, another lesson for me learned the hard way. Glad to hear its working in the interim though, good luck sir!
Click to expand...
Click to collapse
well i did a advance back up and actually got back wat i was looking for. but now its back to hanging up on the white screen. but a battery pull will bring it back up. i actually did a full wipe and all that. so atleast im back on point,
Related
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
tyhodge07 said:
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
Click to expand...
Click to collapse
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Post what problems you are having. Good luck.
Sent from my PC36100 using XDA App
Dredge said:
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Click to expand...
Click to collapse
im not even sure which rom to use, i have tried a couple but the adk is where i am stuck at, when i go to command prompt it isnt at the c://adk/etc.. like what all the write ups are at, its at c://user/applications or something of that nature and i type what should be typed in on the /adk part of it and says it can not be found. i tried reinstalling the adk again and same problem, im doing something wrong somewhere i assume or stuck in a spot that i keep doing wrong and not noticing. i just rooted it, so whatever rom i have i am assuming is the stock one since i havent gotten past this yet.
Your in over your head man, seriously, YOU put the sdk where you want it, me, I just put it in C:\sdk to make my life easy when changing directories.
If command line work is not something your familiar with, have patience, enjoy your rom as it is right now and wait until the super easy one click gui programs are created.
Did you buy the phone already rooted, or did you root it yourself?
Dredge said:
Did you buy the phone already rooted, or did you root it yourself?
Click to expand...
Click to collapse
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
tyhodge07 said:
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
Click to expand...
Click to collapse
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
TJDuckett said:
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
Click to expand...
Click to collapse
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Dredge said:
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Click to expand...
Click to collapse
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
tyhodge07 said:
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
Click to expand...
Click to collapse
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
TJDuckett said:
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
Click to expand...
Click to collapse
think what you would like, im not a kid. ive answered your questions. computers or phones is nothing new to me. family works for sprint, but will not mess with the rooting part of it. so i was left alone on this. ive searched and searched and what u have read is where i am at. basically i am wanting a custom theme. i have tethering and all that crap that works fine. but a theme wont work and a rom to be 1.47 or whatever was never put on, i have what i posted and have everything a rooted phone should have. obviously im stuck on that rom part of it. no reason to be a **** or call someone a troll or say their trolling, when their asking questions. if ur intentions wernt to help, than dont reply. u wasted ur own time.
Is there anyway to deodex the Infuse yet?
probably the same as a galaxy s. gtg465x posted one but we are haveing trouble getting a successful odin package to fix the phone when things go wrong so people were not willing to try it.
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
sinan2010 said:
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
Click to expand...
Click to collapse
well with samsung we are lucky enough to have odin which is a factory flash tool. unfortunately it is not working on the infuse 100%, there may be a new build of it just for the infuse but it hasnt been leaked yet as far as we know. there is also an opensource application called heimdall that works in place of odin. there has been some success with heimdall but the one user that restored with it is having random vibrate issues.
there are still things to figure out, but there is no reason you cant flash with cwm, there are just no proven roms or reliable methods to restore if it goes wrong.
Thanks again. I'll just wait since I'm not good in doing these kind of things.
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
beatblaster said:
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
Click to expand...
Click to collapse
So there are already some people brick their devices and good to know that you have successfully flashed it back.
I just have no idea how to do these kind of things this is my first Android device. I had HD2 and was so easy to do anything. I'm just afraid to brick my infuse, so I'll just wait
I just need to deodex it so I can be able to read and write in Arabic.
Thanks
Hey guys, THIS IS URGENT!
Ok, here's my problem. Over the past week i have been forced to reinstall my ROM/ROM'S several times. My Infuse will at times shut itself down and i will have to restart my phone. after i restart my phone i notice that all of the apps that i have on the phone that i have gotten from the marketplace will be grayed out and really not on my phone at all. this is getting really frustrating and if i had the money i would be visiting my AT&T store to get a windows phone. I love android and want to stay with it but i am getting pissed.
Do I need to ODIN back to stock or what? The phone will run for about a day and then it will just do what i described above. If I have to ODIN to stock then could someone please tell me how to do it because i have not had to deal with that yet. I would like to be running Zeus on my phone but that is when this whole ordeal started.
If someone could please help me with this i would greatly appreciate it. I really hope that someone has had this same problem. Any help would be awesome!
Thanks,
Bassman
running on Zeus?
no running on dlevrom now...was running zeus and caty
bassman198721 said:
no running on dlevrom now...was running zeus and caty
Click to expand...
Click to collapse
how did you get to dlev from zeus or caty?
what app were u running when it rebooted or crashed?
well i have a feeling that the way you worded that last post that i may fave effed this up myself.....heres how it went....i was on dlev first, then i flashed zeus, zeus did the missing apps, then i said screw this and went to caty, caty did it, and now back on dlev and it is losing apps....i know it's a crazy vicious circle but please tell me that i didnt do this myself and that it is just a fluke...
bassman198721 said:
well i have a feeling that the way you worded that last post that i may fave effed this up myself.....heres how it went....i was on dlev first, then i flashed zeus, zeus did the missing apps, then i said screw this and went to caty, caty did it, and now back on dlev and it is losing apps....i know it's a crazy vicious circle but please tell me that i didnt do this myself and that it is just a fluke...
Click to expand...
Click to collapse
I have notice that crash mostly on zeus. sometimes it is triggered by tibu backups or different launcher or different setting of TW launcher with special animations etc.
This effect probably carried over from flashing other roms over zeus without proper factory reset or wipes.
go to my post on the q/a rom; use jordan's method of flashing the rom you want.
edit: here ya go
http://forum.xda-developers.com/showthread.php?t=1318160
i looked at the post that you gave me. is the method done by ODIN or heimdall? i am getting ready to bootcamp my mac so that i can try his method. after i do that method will i be able to run zeus again?
bassman198721 said:
i looked at the post that you gave me. is the method done by ODIN or heimdall? i am getting ready to bootcamp my mac so that i can try his method. after i do that method will i be able to run zeus again?
Click to expand...
Click to collapse
his method is with odin.
(if you are familiar with heimdall, you can take the package apart and use heimdall).
on the last part, flash Zeus ROM
OK, I will give that a shot. Correct me if I am wrong but I have been reading about ODIN and a lot of the stuff that I have seen says that it is not safe for your phone. Is that the case? i would rather just take it back to stock and leave it there if i have a high risk of bricking my phone. Also I would like to thank you for helping me with this issue.
bassman198721 said:
OK, I will give that a shot. Correct me if I am wrong but I have been reading about ODIN and a lot of the stuff that I have seen says that it is not safe for your phone. Is that the case? i would rather just take it back to stock and leave it there if i have a high risk of bricking my phone. Also I would like to thank you for helping me with this issue.
Click to expand...
Click to collapse
you're welcome.
SOFT bricking the infuse is pretty common. Easy to restore. According to Adam Outler, a bad bootloader flash is possible to HARD brick it.
I think if you're interested in using ROMs other than stock (what comes with the phone), learning how to use odin or heimdall is a must.
These tools will be need to restore your phone to it's original state.
There are some risks, but if used correcly, most are minimal.
I would venture to guess the devs and flashaholics odin their device more times than you can imagine.
It's a matter of comfort level.
In reality, I think the stock froyo or one of the GB leak stock is just fine.
I had a "funny post" in the q/a section you should read.
again thanks for all of your help. you definitely gave me a lot of insight and knowledge that i needed to know that i probably wouldn't have gotten anywhere else. i managed to get caty running. i tried to flash zeus and it bootlooped the samsung screen. so i just decided to go with caty. dlev just wasnt cutting it for me. you have been a huge help and i will definitely recommend this thread to other people who have had this problem.
bassman198721 said:
again thanks for all of your help. you definitely gave me a lot of insight and knowledge that i needed to know that i probably wouldn't have gotten anywhere else. i managed to get caty running. i tried to flash zeus and it bootlooped the samsung screen. so i just decided to go with caty. dlev just wasnt cutting it for me. you have been a huge help and i will definitely recommend this thread to other people who have had this problem.
Click to expand...
Click to collapse
If you did get caty running again,
Before you do a whole lot, boot into cwm recovery.
Factory reset. Then wipe cache. Then goto advance. Wipe dalvik. Fix permission. Then reboot.
This should give you a relative clean slate.
Caty is also a very nice infuse base ROM. You're not really missing out on much. Just enjoy the phone. Leave the frequent flash to the flashaholics.
Gl
I did do all of that and the ROM seems to be running flawlessly. Thanks for your help man.
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.
I was wondering if someone could detail to me a sure-fire way to make the jump from GB to ICS. I've tried twice now and both times I got stuck booting into a blue CWM without being able to load a ROM at that point. I was able to boot Aroma but after trying to recover from there I got stuck at the Galaxy S screen. Yes I followed the instructions very carefully. Is there a way to do this via Odin or Heimdall?
Any help would be tremendously appreciated.
Stock GB with CWM > CM 9 flash twice first from red recovery and then again from blue > then JB.
Do a full wipe before and after all the flash.
I know u said u tried this way buy it did not worked for u just give it a try from scratch one more time.
Sent from my MB855 using Tapatalk 2
rkkaranrk said:
Stock GB with CWM > CM 9 flash twice first from red recovery and then again from blue > then JB.
Do a full wipe before and after all the flash.
I know u said u tried this way buy it did not worked for u just give it a try from scratch one more time.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Thanks rkkaranrk. The one thing I didn't do in your instructions was a wipe before and after each flash. Instead I wiped once before I began. Could this be the problem? Is this a common problem? I've seen some mention the same issue in the Dark Knight ROM thread that said they have the same issue but wasn't sure this has to do with the ROM or the migration from GB to ICS in general.
It could be any thing which cause bootloop so its always better to wipe, I always do anand never faced any bootloops Just give it try.
Sent from my MB855 using Tapatalk 2
I'm going to give it a go today too. I've had a hard time convincing myself to leave Aeon though. It's been a rock solid / stable ROM..............
D-Trixxx said:
I was wondering if someone could detail to me a sure-fire way to make the jump from GB to ICS. I've tried twice now and both times I got stuck booting into a blue CWM without being able to load a ROM at that point. I was able to boot Aroma but after trying to recover from there I got stuck at the Galaxy S screen. Yes I followed the instructions very carefully. Is there a way to do this via Odin or Heimdall?
Any help would be tremendously appreciated.
Click to expand...
Click to collapse
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.
captemo said:
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.
Click to expand...
Click to collapse
Thanks for all the replies so far.
@captemo: I followed the instructions in the Dark Knight thread exactly but maybe those instructions need to be updated because they never mentioned multiple wipes. There is no mention of getting stuck @ Galaxy S screen either but that isn't what happened at first. It kept bootlooping into blue CWM. It was only after that I tried to recover with Aroma that I got stuck, probably not the the wisest move on my part however.
I will try the Paranoid ICS build next since it sounds like you have had success with it and it looks like a good one. Just so I am clear on doing this can you list the steps you took to load this ROM? I noticed there are two variants, one with and one without the Aroma installer.
Thanks in advance!
The Aroma installer is nice but in my opinion, based on my experience and reports from others it is too problematic on the Infuse. Would really suggest not using versions with it, at least not on your first flash.
Pony Express said:
The Aroma installer is nice but in my opinion, based on my experience and reports from others it is too problematic on the Infuse. Would really suggest not using versions with it, at least not on your first flash.
Click to expand...
Click to collapse
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.
D-Trixxx said:
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.
Click to expand...
Click to collapse
+ 10.
I had another thought, could Voodoo lagfix be the source of my issues? At the time I had the /Voodoo/disable-lagfix folder on my SDCard
D-Trixxx said:
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.
Click to expand...
Click to collapse
WOW, somebody waiting for MY advice??? are you sure you havent been sipping on grandpa's cough syrup?
Pony i'm sure has more experience than myself and is merely expressing experiences that others and maybe he himself have had. truth is every phone is different and will react different.
i do like the Aroma myself. allows you to install some apps automatically.
i did nothing special than follow OP slowly and carefully to the T. doing this, i have never had problems flashing anything.
if i do anything special it is carefully choosing what i wish to flash. when lookin for new ROM, i go to the last page and start reading backwards. that shows me the most recent problems and issues people may be having. if its a problem i cant handle, i dont flash.
i am not taking away from developers here because they are ALL amazing and i wish i could do some of these things. as for the Dark Knight rom, i download, but never flashed. i just didnt think the development was progressing enough for me.
thats just me.
good luck hope you like Paranoid Android. i like the tablet mode, though print can be small for old eyes like mine just changed the font to something BOLD.
captemo said:
WOW, somebody waiting for MY advice??? are you sure you havent been sipping on grandpa's cough syrup?
Pony i'm sure has more experience than myself and is merely expressing experiences that others and maybe he himself have had. truth is every phone is different and will react different.
i do like the Aroma myself. allows you to install some apps automatically.
i did nothing special than follow OP slowly and carefully to the T. doing this, i have never had problems flashing anything.
if i do anything special it is carefully choosing what i wish to flash. when lookin for new ROM, i go to the last page and start reading backwards. that shows me the most recent problems and issues people may be having. if its a problem i cant handle, i dont flash.
i am not taking away from developers here because they are ALL amazing and i wish i could do some of these things. as for the Dark Knight rom, i download, but never flashed. i just didnt think the development was progressing enough for me.
thats just me.
good luck hope you like Paranoid Android. i like the tablet mode, though print can be small for old eyes like mine just changed the font to something BOLD.
Click to expand...
Click to collapse
The reason I wanted your advice was because you had successfully made the jump from GB to ICS. The Paranoid thread assumes you are starting from ICS so there are no instructions to go from GB to ICS even thought the ICS ROMs are still there.
D-Trixxx said:
The reason I wanted your advice was because you had successfully made the jump from GB to ICS. The Paranoid thread assumes you are starting from ICS so there are no instructions to go from GB to ICS even thought the ICS ROMs are still there.
Click to expand...
Click to collapse
anybody on ICS or JB as made that jump, obviously with sucess. since Paranoids development has jumped to JB there are a couple of small differences in install (GAPPS for ex.) the first 80 pages still deal with the ICS developments of the ROM.
even though the OP has changed to address install of JB, if you go past the first couple of pages and all the congrats of the new ROM, you will get to where any of your questions will be answered. Scott and team are very attentive and if you read read read, questions and concerns are all addressed.
if then you are happy with ROM and are dying to try JB, i think page 80 is where JB discussion begins.
The GB to ICS process should be the same for any rom. You can use cm9 or uniyumaporn to get to ics and then flash jb.
First, be aware once you are in ICS, your recovery will be filled with rainbows due to the lack of GB bootloaders (I'm assuming you don't have those).
1) wipe data, cache, dalvik (format /system is optional)
2) flash ics rom
3) reboot (Not "reboot into recovery")
4) you should hang at kernel splash (galaxy s screen).. remove battery and use 3 finger combo to boot into recovery.
5) wipe again and flash
Sent from my sweet & buttery Infuse
I did this process two days ago. I went from factory att GB to ICS following the instructions for uniporn. Once I had uniporn fully booted and running I then rebooted back into CWM and followed the instructions in the cm10 thread.
The only thing to watch for is in the uni instructions. It still says to flash gapps. You don't have to do that now because they are included in build 40.
How did you update to GB by the way? That will tell us if you have GB or froyo boot loaders
Sent from my SGH-I997 using xda app-developers app
Goneeuro said:
I did this process two days ago. I went from factory att GB to ICS following the instructions for uniporn. Once I had uniporn fully booted and running I then rebooted back into CWM and followed the instructions in the cm10 thread.
The only thing to watch for is in the uni instructions. It still says to flash gapps. You don't have to do that now because they are included in build 40.
How did you update to GB by the way? That will tell us if you have GB or froyo boot loaders
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Hi Goneeuro,
I just saw your post but I did exactly what you did. Basically I read the instructions of a bunch of ROMS and decided to follow uniporns steps and it worked just fine including the gapps installation. Seems to be working fine still but I wonder if its a matter of time if I see issues.
I don't recall how I went to GB, its been so long ago but I don't have the rainbow CWM. Probably because I loaded them during a recovery.
Anyway all is good now. Big THANKS to all of you.
D
Dude thank you so much!
captemo said:
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.
Click to expand...
Click to collapse
Really awesome I've been working on this for like 4 hours and all it took was pulling the battery instead of rebooting to get out of the bootloop. really appreciate it.