Related
Hi guys. I'm hoping my post hasn't broken any forum rules... but anyway, i am very new to android, and i'm still trying to read up on/learn about rooting a phone + flashing a ROM to it. I have a few questions that i'm hoping some experienced people could answer for me =]
1. Does my HTC sensation need to have a certain update before i can try archieve S-Off? (I'm on the Three network [UK] and my software number is 1.34.771.1)
2. How easy is it to brick a device? Im good with computers, and can follow instructions, but seeing as i have no past experience with android, i'm anxious to try flash new ROMs to my phone without insurance - as £500 for a new device would kill me... =P
3. When flashing a new custom ROM to my phone, what kind of 'wipe' do i need to perform? I've read a few articles, all of which say to perform different wipes.
4. I dont understand ' Radio Flashing' could someone kindly explain that to me please?
5. What exactly does CWM backup? =P
I hope i'm not wasting anyones time here, i have read through the articles for noobs, just need some clarification =]
Thanks for everyones time.
~Tbestie~
tbestie said:
Hi guys. I'm hoping my post hasn't broken any forum rules... but anyway, i am very new to android, and i'm still trying to read up on/learn about rooting a phone + flashing a ROM to it. I have a few questions that i'm hoping some experienced people could answer for me =]
1. Does my HTC sensation need to have a certain update before i can try archieve S-Off? (I'm on the Three network [UK] and my software number is 1.34.771.1)
2. How easy is it to brick a device? Im good with computers, and can follow instructions, but seeing as i have no past experience with android, i'm anxious to try flash new ROMs to my phone without insurance - as £500 for a new device would kill me... =P
3. When flashing a new custom ROM to my phone, what kind of 'wipe' do i need to perform? I've read a few articles, all of which say to perform different wipes.
4. I dont understand ' Radio Flashing' could someone kindly explain that to me please?
5. What exactly does CWM backup? =P
I hope i'm not wasting anyones time here, i have read through the articles for noobs, just need some clarification =]
Thanks for everyones time.
~Tbestie~
Click to expand...
Click to collapse
1. As long as you are on Android 2.3.3 there shouldnt be a problem. 2.3.4 donesnt have a S=off just yet, i think
2. Bricking is actually very hard to do, if u follow instructions you should be good
3. all you need to wip is the system data, cache, and i reccomend wiping the battery status too
4. Radio flashing is chaning your radio number. this is actually a very easy process. Dont worry about this, all you do is put a zip on ur sd card, and the phone does the rest.
5. ClockWork Mod backs up quite literally everytrhing. Think "Macrium Reflect" for a PC. Or a "Ghost Backup" for a PC.
6. I just added this. don worry about wasting peoples time. We are here to help each other like a community. Let me know if u have any other questions.
I am following this thread, and when u reply i will answer you again. So feel free to ask any more questions.
If you feel like ur ready to root just go to the Development forum and see the 1st sticky thread. Or if u ask i will send u a few links on how to root.
Alankrut said:
1. As long as you are on Android 2.3.3 there shouldnt be a problem. 2.3.4 donesnt have a S=off just yet, i think
2. Bricking is actually very hard to do, if u follow instructions you should be good
3. all you need to wip is the system data, cache, and i reccomend wiping the battery status too
4. Radio flashing is chaning your radio number. this is actually a very easy process. Dont worry about this, all you do is put a zip on ur sd card, and the phone does the rest.
5. ClockWork Mod backs up quite literally everytrhing. Think "Macrium Reflect" for a PC. Or a "Ghost Backup" for a PC.
6. I just added this. don worry about wasting peoples time. We are here to help each other like a community. Let me know if u have any other questions.
I am following this thread, and when u reply i will answer you again. So feel free to ask any more questions.
If you feel like ur ready to root just go to the Development forum and see the 1st sticky thread. Or if u ask i will send u a few links on how to root.
Click to expand...
Click to collapse
Thank you very much =] Think i'll give rooting a go within the next week... just want to make my sensation that much faster and improve the battery life!
If you don't mind me asking;
What exactly is a Radio number for?
I am on android 2.3.3 , just my software number seemed different to other peoples phones =P
So if i use this 'Clockwork Mod' to backup everything, once the new ROM has installed, will everything just be the same (apart from the changes on the ROM obv) such as app placements on homescreens etc. Or will i have to put everything back?
Also, say android releases 2.3.5 , im assuming i would just flash an updated ROM over the top of an older 2.3.4 ROM when it is released?
I've read through the 1st sticky a few times already, just to familiarise myself with certain words/actions =]
Finally, what is hboot =]
Thanks again for your time!
~Tbestie~
tbestie said:
So if i use this 'Clockwork Mod' to backup everything, once the new ROM has installed, will everything just be the same (apart from the changes on the ROM obv) such as app placements on homescreens etc. Or will i have to put everything back?
Click to expand...
Click to collapse
Clockwork Mod is just a recovery program to allow you to install new ROMs to your device, but most importantly, to let you backup and restore your current device configuration (like a sort of time machine). Most developers recommend Clockwork Mod (CWM) because it is so good at what it does. If anything fails, and you need to use your phone in a pinch, just revert to a CWM backup, and all's well!
So, to answer your question, unfortunately, no. One of the only ways to do that is with Titanium Backup, a program from the Android Market.
CWM is for reverting to previous incarnations of your phone's software and firmware.
Sorry I only answered one question, but it was the only one I knew how to in an effective manner.
Sorry, I can answer another!
tbestie said:
What exactly is a Radio number for?
Click to expand...
Click to collapse
A radio is the way that your device communicates with your mobile networking. (wifi, 3G/4G, etc) Different Radio versions (numbers) work better for different people. Most developers will release a matched radio with their ROMs, which is usually what works best for them. Depending on your area, different radios may work better for you. Ultimately concerning radios, Your Mileage WILL vary. it's one of the other big trial and error pieces to flashing custom ROMs.
tbestie said:
Thank you very much =] Think i'll give rooting a go within the next week... just want to make my sensation that much faster and improve the battery life!
If you don't mind me asking;
What exactly is a Radio number for?
I am on android 2.3.3 , just my software number seemed different to other peoples phones =P
So if i use this 'Clockwork Mod' to backup everything, once the new ROM has installed, will everything just be the same (apart from the changes on the ROM obv) such as app placements on homescreens etc. Or will i have to put everything back?
Also, say android releases 2.3.5 , im assuming i would just flash an updated ROM over the top of an older 2.3.4 ROM when it is released?
I've read through the 1st sticky a few times already, just to familiarise myself with certain words/actions =]
Finally, what is hboot =]
Thanks again for your time!
~Tbestie~
Click to expand...
Click to collapse
Radio Number/Version is the version of ur radio. This is signal related.
So when updates come out they typically update the
radio and make the signal strength better.
This is something to be careful with, when changing ROMs
make sure that the some you are about to change into
supports ur radio version.
When u use ClockWork Mod to backup it will backup your current settings. So if u backup it consists of your rom , apps, settings, etc. so if u restore that then everything would be like the old one. So Yes, u would have the set everything back on the homescreen. Its ok, u will get used to that.
When they release android 2.3.5 you might have to "wipe" your phone and do it again. Maybe, depending on your rom, you might be able to flash on top of 2.3.4
H-Boot is similar to the Bios of the computer. And you know how carefully you have to be to change that.
But the H-Boot version that the 1st sticky says allows changing of certain things, thus allowing you to have root.
Feel free to ask away, im here to help you
Andresehn said:
Sorry, I can answer another!
A radio is the way that your device communicates with your mobile networking. (wifi, 3G/4G, etc) Different Radio versions (numbers) work better for different people. Most developers will release a matched radio with their ROMs, which is usually what works best for them. Depending on your area, different radios may work better for you. Ultimately concerning radios, Your Mileage WILL vary. it's one of the other big trial and error pieces to flashing custom ROMs.
Click to expand...
Click to collapse
lol. you posted both while i was writing up my response.
Its good though, because then the OP will get to read 2 times as much, which will make him even better at the terminology and the process
Lol. I'm just trying to be helpful so i can get to posting on the Dev. forums. There are plenty of easy questions there...
Appreciating the help guys =] Starting to understand a bit better!
So when i flash a new ROM, i must flash a new Radio? If i flash the recommended radio, how likely am i to get a good signal? And if im getting poor signal, i just have to keep trying new Radios? ( I Heard flashing radios is one of the ways you can brick your device)
Also with CWM - When the backup is made... do i have to keep it on the Sd card? Or can i move it to the computer so it takes up less space?
And if i understand correctly - CWM basically creates a backup just incase things go wrong you can always revert back?
... If i use titanium backup, what benefits does that bring over CWM? - Is it worth the money?
Thanks again
~Tbestie~
Also, how do i find my hboot version?
Ive started trying to get S-Off... just be reading ahead, it says that Custom ROMs come with root already? Does that mean i just need CWM with S-Off to flash a ROM? Or do i need to Root + Do the Super-Cid thing?
tbestie said:
Also, how do i find my hboot version?
Click to expand...
Click to collapse
- Hold the power button, untill you get Shut Down, Airplane Mode or Restart.
- Click on Restart then Yes.
- Wait until all the lights on your device turn off.
- Hold the Vol. Down Button until a white screen shows.
There you'll find HBOOT-XXXXXX
This is your HBOOT version.
To get to your OS again:
- Make sure FASTBOOT is hightlighted.
- Press the <Power> button.
- Go to REBOOT by pressing Vol. Down.
- Press the <Power> button.
Hope it helps
tbestie said:
Ive started trying to get S-Off... just be reading ahead, it says that Custom ROMs come with root already? Does that mean i just need CWM with S-Off to flash a ROM? Or do i need to Root + Do the Super-Cid thing?
Click to expand...
Click to collapse
You don't need Root to install a custom Root.
Just S-OFF, CWM and SuperCID I believe..
Just note down your old CID before writing the new SuperCID as you may need it later if you want to flash RUU and afraid of doing something wrong
Later on, if you want to flash RUU (Rom Upgrade Utility) without the fear of flashing a wrong one, you can just write the old CID to your device again
Check this post to know more
Sorry for the silly amount of posts... i cant find how to delete them!
Just so you know - I've archieved S-Off now , and installed CWM successfully.
Am i ready to flash a ROM?
-Also i have save files in games... such as FF7 - FPse , which a really dont want to lose... is their anyway i can copy them/save them somewhere ?
claudenegm said:
You don't need Root to install a custom Root.
Just S-OFF, CWM and SuperCID I believe..
Just note down your old CID before writing the new SuperCID as you may need it later if you want to flash RUU and afraid of doing something wrong
Later on, if you want to flash RUU (Rom Upgrade Utility) without the fear of flashing a wrong one, you can just write the old CID to your device again
Check this post to know more
Click to expand...
Click to collapse
How do i find/note down my old cid?
tbestie said:
Sorry for the silly amount of posts... i cant find how to delete them!
Just so you know - I've archieved S-Off now , and installed CWM successfully.
Am i ready to flash a ROM?
-Also i have save files in games... such as FF7 - FPse , which a really dont want to lose... is their anyway i can copy them/save them somewhere ?
Click to expand...
Click to collapse
To flash a ROM, you mean Stock ROM (RUU) or Custom ROM?
If Custom Rom, please read my post #13 then do the SuperCID thing as you will need it for custom ROM..
About your saved games, the only way I know you can backup your saved data with is using Titanium Backup, which can be found in the Market.
Obviously, if you still don't know what you're doing, research more and then do whatever you want.
I take no responsibilities about anything that may happen to your phone using any of the methods above.
Good luck
tbestie said:
How do i find/note down my old cid?
Click to expand...
Click to collapse
I posted all the instructions in the other link I posted.
You'll find CID: XXXXX, keep this code with you, in-case you need it later for installing RUU and confused about which one to use.
claudenegm said:
To flash a ROM, you mean Stock ROM (RUU) or Custom ROM?
If Custom Rom, please read my post #13 then do the SuperCID thing as you will need it for custom ROM..
About your saved games, the only way I know you can backup your saved data with is using Titanium Backup, which can be found in the Market.
Obviously, if you still don't know what you're doing, research more and then do whatever you want.
I take no responsibilities about anything that may happen to your phone using any of the methods above.
Good luck
Click to expand...
Click to collapse
Im going to try install Android Revolution 3.0.0 =]
Starting to understand what im doing. About to make a backup using CWM. =]
*UPDATE* - Performed backup with CWM - Everything seemed to go fine... however i noticed it said ''No sd-ext found, skipping backup of sd-ext''...
Does that mean my SD card isnt backed up?
tbestie said:
Im going to try install Android Revolution 3.0.0 =]
Starting to understand what im doing. About to make a backup using CWM. =]
*UPDATE* - Performed backup with CWM - Everything seemed to go fine... however i noticed it said ''No sd-ext found, skipping backup of sd-ext''...
Does that mean my SD card isn't backed up?
Click to expand...
Click to collapse
That's exactly what happened to me when I backed up.
I think you should ignore it, as it is trying to backup an extension in the SD-Card, as you can re-partition your SD-Card using CWM as I understand.
I would be pleased if someone explained to me what exactly sd-ext is and what I'm missing
Good day to you all
claudenegm said:
I would be pleased if someone explained to me what exactly sd-ext is and what I'm missing
Click to expand...
Click to collapse
Ignoring it is ok. sd-ext not being backed up is most likely an indicator that an EXT4 formatted portion of your SD card was not found. By default, your SD card is formatted as FAT32 because of its universal acceptance by all OSs. Some users report a performance boost/personal preference toward EXT4, YMMV.
tbestie said:
Does that mean my SD card isnt backed up?
Click to expand...
Click to collapse
Most importantly, ClockworkMod does not back up your SD card. that is something you have to do manually on your computer, should you choose to do so. CWM is only responsible for backing up the internal storage of the phone that can be changed or wiped by ROMs (or mike1986's SuperWipe.) ROMs shouldn't change the contents of the SD card.
Ok before I get skewered by the tenured members of this esteemed site, I just wanted to say that I did my research as many of you suggested, and I feel like I've read every thread about the following topic to no avail, my phone is in the same state, I digress;
Like many on here before me, I have been handed the "white screen of death" on my HTC Inspire 4G. Some call it a soft brick, even though that's a frowned upon term. Either way, I have it and I'd really like to get rid of it. I can access my Hboot no problem, my phone is S-OFF, so that's not an issue. I tried running an RUU on here to update the image, but when it rebooted, the HTC white screen of death reappeared. Tried running the PD98IMG.ZIP image and reflashing a custom pre-rooted stock rom, didn't work.
Threads I've tried:
http://forum.xda-developers.com/showthread.php?t=1286832
http://forum.xda-developers.com/showthread.php?t=1390677
http://forum.xda-developers.com/showthread.php?t=1396229
These were the three that ware most similar to the problem I had I felt like, yet neither had the solution I was looking for. Clearly, the phone isn't bricked since I can get into the HBoot, but besides that, I'm stuck. For all I know, I'm a complete idiot and missing a vital step, but I'm almost at my wits end and I really just need my smartphone back. Any assistance, regardless of how condescending it may be, will be received with immense gratification if it indeed helps my problem. Thank you, and please help me .
And little more info, please. Can you get into recovery from hboot? If so, is it a stock or custom recovery? What version of hboot are you running?
This thread will probably be moved to Q&A. Stick with it and we will try to help.
Sent using the power of the dark side.
fballplyr92 said:
Ok before I get skewered by the tenured members of this esteemed site, I just wanted to say that I did my research as many of you suggested, and I feel like I've read every thread about the following topic to no avail, my phone is in the same state, I digress;
Like many on here before me, I have been handed the "white screen of death" on my HTC Inspire 4G. Some call it a soft brick, even though that's a frowned upon term. Either way, I have it and I'd really like to get rid of it. I can access my Hboot no problem, my phone is S-OFF, so that's not an issue. I tried running an RUU on here to update the image, but when it rebooted, the HTC white screen of death reappeared. Tried running the PD98IMG.ZIP image and reflashing a custom pre-rooted stock rom, didn't work.
Threads I've tried:
http://forum.xda-developers.com/showthread.php?t=1286832
http://forum.xda-developers.com/showthread.php?t=1390677
http://forum.xda-developers.com/showthread.php?t=1396229
These were the three that ware most similar to the problem I had I felt like, yet neither had the solution I was looking for. Clearly, the phone isn't bricked since I can get into the HBoot, but besides that, I'm stuck. For all I know, I'm a complete idiot and missing a vital step, but I'm almost at my wits end and I really just need my smartphone back. Any assistance, regardless of how condescending it may be, will be received with immense gratification if it indeed helps my problem. Thank you, and please help me .
Click to expand...
Click to collapse
Can you get into recovery? If not, follow the Ace Think Tank guide on post #7 starting on the bottom of page 9, the section "S-OFF no recovery," to get a recovery back; then use that recovery to flash a ROM. If so, just flash a ROM from recovery.
bananagranola said:
Can you get into recovery? If not, follow the Ace Think Tank guide on post #7 starting on the bottom of page 9, the section S-OFF no recovery, to get a recovery back; then use that recovery to flash a ROM. If so, just flash a ROM from recovery.
Click to expand...
Click to collapse
This
Sent from my Inspire 4G using xda premium
Please post all questions in the Q & A section. Thanks. Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
I tried an S-off as per the procedure everything went well
Supercid 11111111
and Finally A bootloader with S-Off
but when The device booted,it showed the home screen with the unlock screen and as soon as the screen unlocks its gives and error "Process system failed" (somethng almost similar) and gave an option to wait or close the program, choosing either of the two would result in a continuous bootloop
Attempts Made So far
-reflashed the kernals,ROMs, with Factory reset, Wipes Via fastboot commands
-Did A factory reset from Bootloader to clear all the Corrupt files
-Re-locked the bootloader to Install a fresh RUU
Attempted the S-Off from Win8 PC, but later RUUs were also tried Via Win7
Thannks to beaups and jcase so far for all the Help, Appreciated:good:
All the above steps couldnt bring back the cell to normal.Therefore,would Appreciate any help
#Latest attempt was Installing a Recovery via fastboot, it showed 'failed" Error
Thank You
Don't factory reset from bootloader, that corrupts the SD card. Have you tried flashing stock recovery? If your SD card is corrupted, that's the only way to fix it. Also, keep in mind next time that you should post questions in Q&A, people tend to get a little upset when they show up here.
C'mon man, wrong section.... Use Q&A.... :facepalm:
trathiang said:
Don't factory reset from bootloader, that corrupts the SD card. Have you tried flashing stock recovery? If your SD card is corrupted, that's the only way to fix it. Also, keep in mind next time that you should post questions in Q&A, people tend to get a little upset when they show up here.
Click to expand...
Click to collapse
You shouldnt help people that dont follow rules. I have already reported this post. Reasons like this I just want to kill a kitten.
droidkevlar said:
You shouldnt help people that dont follow rules. I have already reported this post. Reasons like this I just want to kill a kitten.
Click to expand...
Click to collapse
but.. I like kittens
Sent from my One S using xda premium
rufh_s said:
I tried an S-off as per the procedure everything went well
Supercid 11111111
and Finally A bootloader with S-Off
but when The device booted,it showed the home screen with the unlock screen and as soon as the screen unlocks its gives and error "Process system failed" (somethng almost similar) and gave an option to wait or close the program, choosing either of the two would result in a continuous bootloop...
...Error
Thank You
Click to expand...
Click to collapse
You obtained S-Off but corrupted phone's internal card b/c perhaps you did not wait enough time when did the last step (adb shell su -c "/data/local/tmp/soffbin3" before reboot) when did S-Off.
1. Now, Re-lock your bootloader and then reboot into RUU flash mode: fastboot oem rebootRUU
2. Flash either HTC RUU or OTA Update from here
3. Reboot - you will have stock ROM
4. Now unlock bootloader, flash custom recovery, root, do backup, (you still have Super CID) and then do S-Off (if you really need)
P.S. Q should be in General Thread
droidkevlar said:
kill a kitten.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=uvqJ1mTkEuY
To be fair, if he hadn't posted in QA, he probably wouldn't have got the response. All the good people are here. QA is mostly full of 'how to I get into my bootloader' crowd.
(I follow the rules though )
ipit said:
To be fair, if he hadn't posted in QA, he probably wouldn't have got the response. All the good people are here. QA is mostly full of 'how to I get into my bootloader' crowd.
(I follow the rules though )
Click to expand...
Click to collapse
My thoughts exactly. If you want less Q&A posts here, go to Q&A and help some noobs out.
dr_rick13 said:
but.. I like kittens
Sent from my One S using xda premium
Click to expand...
Click to collapse
Lmao...
WOW look at this right in developing (shakes head) always try q&a first if a few days go by and no response then maybe try in the rom but don't start a question here.
P. S. Next time you loop your phone Google it first then read till your blue in the face if no luck that way then come here, please.
Sent from my HTC one s running rootbox 4.2.2 unofficial, bubba kernel v3.5 fix oc using XDA app
good to see the noobs are the harshest critics.
#iamatroll
Sent from my HTC One S using xda app-developers app
droidkevlar said:
You shouldnt help people that dont follow rules. I have already reported this post. Reasons like this I just want to kill a kitten.
Click to expand...
Click to collapse
Em why not? So what its in the wrong section its a bit late to ***** about it so why not help and just let him know he did wrong like trathiang did and he only has 17 posts so shame on you.
I've factory reset from bootloader and stepped on other land mines as well. Don't worry, as long as you don't mess up your bootloader I think it is pretty hard to brick this phone.
I would suggest you flash TWRP recovery if you don't already use that, wipe everything including internal SD card, mount it and copy over the ROM and flash it again. Maybe it's something wrong with the ROM you are using?! Perhaps try a different one and of course make sure it's for an HTC One S (ville) phone.
If you try mount the internal SDcard and Winbloz says the sdcard needs to be formatted then do that using all defaults (fat32).
mustardman29 said:
I've factory reset from bootloader and stepped on other land mines as well. Don't worry, as long as you don't mess up your bootloader I think it is pretty hard to brick this phone.
I would suggest you flash TWRP recovery if you don't already use that, wipe everything including internal SD card, mount it and copy over the ROM and flash it again. Maybe it's something wrong with the ROM you are using?! Perhaps try a different one and of course make sure it's for an HTC One S (ville) phone.
If you try mount the internal SDcard and Winbloz says the sdcard needs to be formatted then do that using all defaults (fat32).
Click to expand...
Click to collapse
I apologize for posting in the wrong section, but in the past had an experience that my questions remained un-answered in Q &A Section so had to post it here to attract the best minds to comment
As far as i remember there was no issues with S-Off.. as i waited for some time then did an Adb reboot and later it showed S-Off in Bootloader
I also Googled alot before posting it here .. In case Someone missed out the procedures i followed to get it back, its a long list of tries
I Already tried the RUU process ( will give it one more try now)
I also tried with different ROMs but the same issue
Sorry for the wrong section
rufh_s said:
I apologize for posting in the wrong section, but in the past had an experience that my questions remained un-answered in Q &A Section so had to post it here to attract the best minds to comment
As far as i remember there was no issues with S-Off.. as i waited for some time then did an Adb reboot and later it showed S-Off in Bootloader
I also Googled alot before posting it here .. In case Someone missed out the procedures i followed to get it back, its a long list of tries
I Already tried the RUU process ( will give it one more try now)
I also tried with different ROMs but the same issue
Sorry for the wrong section
Click to expand...
Click to collapse
Which RUU are you trying? If it's 2.35, try something older, like 1.84. I could never get 2.35 to work.
Darknites said:
Em why not? So what its in the wrong section its a bit late to ***** about it so why not help and just let him know he did wrong like trathiang did and he only has 17 posts so shame on you.
Click to expand...
Click to collapse
why not? i guess rules arent needed, r they? he isnt the first, and wont be the last, but there is a reason for rules. if ppl continue to help them, they wont listen to the rules and continue to post in the wrong sections and clog up dev and general with crap. i help on here and irc and been around for quiet some time. tired of ppl just feeling entitled. i always check in q&a as i try to help when i can. but when ppl refuse to follow the rules, i will not help and will report the post.
droidkevlar said:
why not? i guess rules arent needed, r they? he isnt the first, and wont be the last, but there is a reason for rules. if ppl continue to help them, they wont listen to the rules and continue to post in the wrong sections and clog up dev and general with crap. i help on here and irc and been around for quiet some time. tired of ppl just feeling entitled. i always check in q&a as i try to help when i can. but when ppl refuse to follow the rules, i will not help and will report the post.
Click to expand...
Click to collapse
The way I see it, this guy is not asking how to change his wallpaper or install a Hello Kitty theme. His phone won't boot. The night I got my phone, I did a factory reset from the bootloader and spent 4 hours having a panic attack trying to fix it. It's a ****ty feeling, we've all been there, and when we were there, all we wanted was to figure out how to save our phones. Helping people while reminding them to post in the right section will make people have a more positive experience with xda. Telling them wrong section and refusing to answer them is petty and alienating.
The way I see it, this guy is not asking how to change his wallpaper or install a Hello Kitty theme. His phone won't boot. The night I got my phone, I did a factory reset from the bootloader and spent 4 hours having a panic attack trying to fix it. It's a ****ty feeling, we've all been there, and when we were there, all we wanted was to figure out how to save our phones. Helping people while reminding them to post in the right section will make people have a more positive experience with xda. Telling them wrong section and refusing to answer them is petty and alienating.
Click to expand...
Click to collapse
Thank you for the Support, believe that's the same feeling I am going through, I would Generally follow All the Rules, this time had to take different path as it was a bit severe
Which RUU are you trying? If it's 2.35, try something older, like 1.84. I could never get 2.35 to work.
Click to expand...
Click to collapse
I did a 2.35, Ill go for something else now, As I am Using a US t-mobile, but I am from India, will the country specific RUU matter? like can I us Europe's version as well?
Downloading 1.84 now, will get back as soon as its done
Sorry to put this here but first post after joining,and I can't post in the required section.
I have been trying to resurrect my bricked HTC Pico. I followed this thread http://forum.xda-developers.com/showthread.php?t=2048312 and found the rom to be very good and fast but one issue so if someone can let the developer know, After following all the instructions and installing the rom I can't do anything else due to it saying there is no more space even though I have set up the extra partition as ext3 before installing the rom.
Is that you IHATEHIPSTERSSS?
Anyways check out this thread
http://forum.xda-developers.com/showthread.php?t=1500165
I'd factory restore the phone and start the process over. As long as the computer sees the phone when it connects.you're not bricked.
Sorry, don't know who you are talking about and I tried the RUU but get a certificate failure. As I said, I tried everything suggested, even a full factory reset.
Oh and I have already done the suggested with extracting the files from the RUU
OK I talked to another guy on a tech site last night who is new to the pico and flashing ROMs.
Its been years since I delt with an HTC device. Google around using 'certificate failure' in the keywords. Hopefully somebody had a similar problem and figured it out.
Sorry I can't be of more help.
Thanks, it seems that because the phone was originally a T-Mobile phone, there are no RUU's that will go onto the phone because it won't accept a generic RUU. It would need to be a T-Mob RUU for the Pico, I have scoured the net but nothing so i'll just keep trying to sort the memory issue somehow.
I have scoured the internet for a solution, but my phone is from Hell. Every single thing I have ever done has ended in errors, ranging from trying to flash the rom zip and getting a "data length is too large" to errors while my phone did still have an OS and flashing through fastboot or double clicking in an exe would give me errors regarding the version or whatever other bs. I have been actively trying to fix this phone for well over a year! When I first started, it was still under warranty, and now it's just a paperweight that continues to waste days of my time at a time.
I am by no means a noob to electronics, but it seems I must be missing something I didn't learn, as I must be a noob in rooting/unrooting/flashing phones. I hope to God nobody suggests that I should have posted this in another thread, as I have searched all similar threads (all over the internet, different phones, any website that Google could find) and tried every single method anybody suggested. Most methods would be completely useless as I wouldn't meet the prerequisites, but I tried even those methods once I exhausted all serious methods.
I have officially gone mad and am about to say goodbye to all technology and go live in a Amish community for the rest of my life. I became so desperate and crazy that I managed to mess up my phone further than it was to begin with. PLEASE HELP! I am at your humble service, and I await any and all instruction.
A little background:
I got the phone from a family member once they cracked their screen, as I am much more of a hardware techie and I got the phone as a present to fix and use for myself. My family member is trigger happy and likes to root everything he could get his hands on. I am much happier with the stock versions of things as they give the best performance for my needs, not to mention the much less hassles and headaches with updates and reception and so on and so forth. I got the phone when it had 1.73.502.1 software on it. I wanted to upgrade to the 3.18.502.6 software version that was available, unroot the phone, and take everything back to dead stock. Since then, 5.18.502.1 has become available. (Side story about this: when double clicking the 5.18.502.6 RUU exe to go into my temp folder and extract the ROM zip, this version doesn't execute for some reason when downloaded from the "HTC OTA and RUU collection" thread (http://forum.xda-developers.com/showthread.php?t=2119610), and the previous version mentioned does execute and show up in my temp folder in Windows, but there are two roms (rom 1 and rom 2), and when extracting them, I get errors, so I had to download and extract 2.20.502.7, which executed and extracted without any problems)). I tried unlocking the bootloader through HTC's website (yes, I believe I relocked it about a year ago in a stupid move because I read that in order to execute an RUU you have to be relocked), but I guess AT&T is a big douche, so I had to superCID (cid 11111111) before doing so, but simply doing "fastboot oem writecid 11111111" wouldn't work, so I literally tried a million different tools I found until magically (literally, I don't know what happened or what I did), I got to superCID, in which case I unlocked with no problem. I then tried every method possible of updating, flashing, everything, but when things got to the actual rom zip part or executing RUU or basically the last steps, I would always be presented with errors and fails. In an angry move, I went to TWRP and erased everything I could get my hands on (I know, I messed up, kill me), and so I deleted the OS and whatever else was on the phone. Since then, I also managed to relock the bootloader (which I locked and unlocked multiple times with no problem and had the unlock code, so I figured I'm safe forever), and take my CID back to cws__001 (which I thought might be the cause of all of my errors, but found that now I can no longer unlock my bootloader).....
I now have an HTC One X from AT&T that is relocked, CID is cws__001,stock recovery, no operating system to boot into adb, and not able to flash anything on it to get into TWRP at least to try and adb sideload or some other things to take back the screw-ups I did since last night.
Info on bootloader:
TAMPERED
RELOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Nov 26 2012, 18:37:14:-1
I apologize beforehand for even touching the phone's software and trying to mess with it and maybe learn a thing or two in the process. Again, I thank you greatly beforehand for all your input, and I hope to hear back soon!
Erik
You can run the 3.18 att ruu to fix the phone to the point of it booting. If you want to learn a few things (such as custom ROMs and the like) you can visit threads on how to root, unlock the bootloader, get supercid, and then s-off.
Sent from my One XL using XDA Premium 4 mobile app
Thanks for the prompt response
I tried what you suggested just now (downloaded the 3.18.502.6 RUU exe from the thread http://forum.xda-developers.com/showthread.php?t=2119610, went into fastboot, right-clicked the exe and chose to run as administrator), and I got "ERROR [158]: Image Error"
I had tried that numerous times in the past as well, with either the same error or various other errors, through fastboot and through the phone being on and fully operable.
On a side note: for some reason it's recognizing my current image version as 3.18.502.6, but there is no operating system on there now, and when there was, it was definitely 1.73.502.1
Any other suggestions?
edit: also, please don't tell me that I should have changed my CID to CWS__001 instead of cws__001....does it make a difference if the CID is lowercase or uppercase?
Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita
timmaaa said:
Ok, wow. I'm not sure where to start here. I think perhaps your main problem is that you rushed, and you've tried "every single method" for doing things, when there is usually only one specific method for each scenario you encounter on each device. The key is to be patient and do the proper research, and find the method that is going to fix the problem you're facing. The other key is to stay within XDA, and more specifically to stay within your device forum. Venturing onto other websites is a bad idea, they don't properly distinguish between phone models (and the information is usually plagiarised from XDA anyway). If you can't find the method that's going to fix your problem, then ask here, don't wait until you've royally screwed the device to ask for advice.
I believe the CID is case sensitive so there's why the RUU you want to run isn't succeeding. Go to the Compilation Roll-Up thread in my signature, find the 3.18 root method, achieve SuperCID again using that method, unlock your bootloader again, flash TWRP 2.6 from here, flash a ROM from our development section, get s-off, boom, done. Getting s-off is optional but trust me, you're gonna want it.
Sent from my Evita
---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------
Actually, just realised the 3.18 root method won't work because it requires a working OS. Try flashing your unlock token again to see if it'll unlock your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
You're correct about me having rushed the process. Well, I didn't at first, but after the first few days, I began to just try anything I could get my hands on, and believe it or not, that was a year ago, so every once in a while I'll grab the phone and try searching some new things, but it's not like there are an infinite number of ways to go about things :\ Thanks for the help so far though, really
edit after seeing your edit: hahaha! yeah, you caught yourself perfectly! Also, in response to your question: I've tried flashing the unlock token through multiple different programs, but to no avail. As you said, I royally screwed myself in thinking that I could put back my CID (but my stupid self didn't put uppercase letters), and I thought I'd still be able to use my unlock token since I had gotten the code beforehand and it worked multiple times before, but I was mistaken
To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita
timmaaa said:
To be honest, I think your only option right now is a jtag repair. I don't think your unlock token is going to work because you no longer have SuperCID.
Sent from my Evita
---------- Post added at 12:33 PM ---------- Previous post was at 11:55 AM ----------
The reason your unlock token isn't working is because it's looking for the same CID you had (11111111) when you unlocked the first time. So jtag is the only thing that's gonna resurrect your phone.
Sent from my Evita
Click to expand...
Click to collapse
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time
Ruu while in fastboot mode.no?
Edit my bad just noticed the part about lower case cid
Sent from my One XL using xda app-developers app
EsoteRIcalfreaK said:
Please tell me it isn't so! I hate myself...I'm stuck with my girlfriend's HTC Droid DNA (absolutely love this phone, but no LTE for T-Mobile since it's a Verizon exclusive phone), and now I'm finding out I screwed myself over and have an awesome paperweight that I need to pay someone else to repair (I'm assuming JTAG repair is some sort of service facilities offer? That's what my search online showed)
I hope maybe somebody else could chime a differing view on this, but thank you timmaaa for your help and time
Click to expand...
Click to collapse
Unfortunately for you there is no differing view. You've gotten the phone to a point where it cannot be resurrected via traditional means. Jtag is indeed your only option, and yes it's a repair service. They hook your motherboard up to a riffbox and push the partitions to it, you can even request things like s-off. There's a user here on XDA called zarboz who does jtag repairs, and I believe he's the cheapest you'll find. He's based out of Ohio I think. Contact him via PM for details.
Sent from my Evita
Great, I have an awesome paperweight that I made myself, and the person that I could talk to so that I could get help doesn't accept private messages from someone who has less than ten posts, hahaha
I'm so hoping that the head of HTC's development department somehow joins the forum and tells me that I just need to fastboot some crying smiley face symbol and the phone will start dancing for me until everything goes back to it's original factory settings...why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!
The RUU is HTC's version of software reset. The problem isn't a lack of reset program from the manufacturer, the problem is the fact that you changed the CID incorrectly.
Sent from my Evita
I can't believe uppercase and lowercase make a difference though
Also, I tried executing the RUU in multiple different ways, even when the OS was operable, in the last year, multiple times, with multiple different versions, but I was always presented with an error of some sort and the RUU setup would cancel and close. The first thing I tried after every exploit that I did was to run the RUU, so I really don't know what else I could have done differently to have gotten the RUU to run without errors, or else I wouldn't have gone this far and tried unorthodox measures to try and revive the poor guy
Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Sent from my Evita
EsoteRIcalfreaK said:
Nice, I was hoping hear from you timmaaa, but unfortunately, looking at that root method, as well as any that I have seen in my searches, requires that I be in adb, which as far as I know cannot be done unless the phone boots up, but I do not have an OS, so the phone will not boot up for me to go through with adb commands. Is there something I'm missing? or is there a workaround?
Click to expand...
Click to collapse
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
EsoteRIcalfreaK said:
I have scoured the internet for a solution, but my phone is from Hell.
Click to expand...
Click to collapse
EsoteRIcalfreaK said:
why hasn't HTC adopted Samsuck's and Crapple's software reset through their syncing program yet?!?!
Click to expand...
Click to collapse
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
EsoteRIcalfreaK said:
I can't believe uppercase and lowercase make a difference though
Click to expand...
Click to collapse
How is that so unbelievable? As timmaaa mentioned, case is often crucial when it comes to computers. Since when is syntax not important when typing computer commands?
For the CID in particular, its obviously all hinging on a handful of crucial characters. So it needs to be typed exactly right.
redpoint73 said:
Is this true? The root method needs to have the phone booted into the OS? adb should work in bootloader (but I never had to do the 3.18 root method personally), so I'm unsure of the answer myself.
Click to expand...
Click to collapse
adb works in recovery or while the phone is stuck at loading screen but not in bootloader. Ofcourse, without an OS there's nothing to grant su. Though, he MAY be able to rewrite his CID using the 3.18 method anyway since I imagine the recovery must have SU or equal permissions..
I am less inclined to want to help after all his whining though :/
exad said:
I am less inclined to want to help after all his whining though :/
Click to expand...
Click to collapse
timmaaa said:
Of course upper case and lower case makes a difference, this is computing after all. There was always a way to get the RUU to run, right up until the point of writing the CID wrong, if you had asked for help here earlier I'm positive I could have figured it out. It's a matter of having done the right research, and being well versed with the device you're working with.
Click to expand...
Click to collapse
redpoint73 said:
Stop blaming the phone, HTC, etc. Its pretty clear that the main problem was your lack of research and understanding. For any phone, the proper research (preferably a few hours at least) needs to be done before attempting any mods. You've found the consequence of rushing the process, and have only yourself to blame.
No offense intended, but its clear you have a lack of understanding of many of the basic concepts, rules, etc., and have also been rushing forward trying a lot of methods that are not completely applicable to your case. This is absolutely not the correct methodology when modding a phone.
Click to expand...
Click to collapse
Guys, guys, please do understand that I did many many hours of research before attempting anything. It wasn't until just recently that I began to just go plain crazy and just throw whatever I could get my hands on into commands and such (and that was all done in the matter of one frustrating night actually, so for almost two years I researched and learned things from mostly this board and tried different methods I found useful). You should see the bookmarks I have created on my browser (I deleted a bunch of useless ones recently, but I have 24 as of right now just explaining One X things)!
If you read closely (I know, I have written a lot, because I have seen people get completely flamed for not writing enough information), I mentioned that I have been trying to revive this phone for over a year now (two years this month). The reason I didn't ask for help earlier, which I wanted to do from day one, is for respect to exactly you guys...
1. I was about to make an account on here and post the very first day I got the phone, but after watching the introduction/noob video on YouTube for this website that explains the rules and what to do before EVER posting ANYthing, I decided to do a little more research and do my best to listen and learn from all the tutorials and great help you guys have given to others.
2. I wanted to make sure, as the video and as many of you mention on this forum, to try every avenue and method before coming for help. I did so precisely for the reason of not wanting to look as though I'm "whining". I might have exaggerated a bit in saying that I threw everything I found at the phone, because I did not just blindly do things without the proper research.
The OS I "accidentally" deleted in hoping to get rid of whatever software was on there that really was not changing or allowing me to RUU or anything. I thought that if I deleted it, it would be easier to put a fresh genuine stock copy on it. I was mistaken, and by the time I realized, I had done the damage to the phone. The biggest mistake that caused this irreversible damage was MY OWN unfortunate way of thought of thinking that uppercase and lowercase wouldn't make a difference (actually the truth is, I thought the original CID was lowercase, but seeing as how I had spent almost two years on this project, and I had had a very long day, I didn't double check to make sure, and I figured that I would be able to go back and change it worst case scenario...this my MY mistake, and I am by no means whining or complaining for MY OWN MISTAKE).
All that being said, please gentleman, if there is anything I could do to revive this phone and reverse my wrong-doings, I would appreciate it greatly and be forever grateful. I assure you, I will not perform a single step without confirming that I am doing the right thing. I am definitely wanting your help, and I definitely do seek to leave behind something that other people who make similar mistakes to mine can look back on for future reference.
Long story short, I messed up, it's my fault, I'm not complaining or whining, my Crapple and Samsuck comments were just to poke fun at those companies, and I would really appreciate it if anyone could help me in any shape way or form. Thank you beforehand
Erik
Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086
exad said:
Good, then try this. You should have adb access within TWRP.
http://forum.xda-developers.com/showthread.php?t=2285086
Click to expand...
Click to collapse
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand
To be honest I think this was dubious at best, it was worth a try but I didn't hold much hope for it actually working. The only place it might have worked would have been in TWRP, even then your system was wiped so the structure required for the commands doesn't even exist in the partition. Someone else chime in here if I'm wrong, but I still believe jtag is the only option out of this.
Sent from my Evita
EsoteRIcalfreaK said:
Thanks for the info, but I tried doing adb commands while the phone was stuck at the "HTC quietly brilliant" boot screen, as well as in recovery, but the phone isn't detected. I do not have TWRP. I have a stock recovery (Android system recovery <3e>). Any other way to do adb commands in my situation? Thanks beforehand
Click to expand...
Click to collapse
You have stock recovery!? -_- I think timaaa is right then -_- I will flash stock recovery and test ADB just to be sure, just for you homeboy. I will post an update shortly.
---------- Post added at 03:21 PM ---------- Previous post was at 03:05 PM ----------
Yeah, sorry man, Jtag only.