Related
Very much a noob when it comes to Android phones and I have been working through the process to get a custom Rom on my HTC Sensation. I started following the instructions in this thread [Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on and successfully completed step one, achieving s-off on the phone.
In step two things went badly wrong. Following the instructions I downloaded clockwork recovery and copied the PG58IMG onto my sd card, at least I thought I did. What I now realize is that since I had been doing a lot of reading and research on this topic before attempting it for the first time I had downloaded several relevant files in advance, one of which is the PG58IMG file from this thread [DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [01.03.2012 and it was this file that I put on the sd card. Obviously not what I should have flashed at all. Especially since it seems that the tool which would help me out of this mess is the one I just failed to install properly.
So the situation is that the phone loops constantly on startup when booting normally. When I boot into HBOOT with the SD card in it tries to update again and when that fails, gives no option but to reboot. If I remove the SD card then I get access to the following screen -
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-10.14.9035.01_M
eMMC-boot
and below the options -
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
I have tried connecting the phone to my computer at this stage but I cant get FASTBOOT USB and adb cant find any devices either. Am I completely stuffed at this point? If not, if anyone can help me out with some instructions on what to do here I would be extremely grateful.
Thanks,
Webba
So have you tried to go into recovery once your in bootloader ? what happens then ?
If you get the correct files onto your sd card via a card reader, then put it in the phone, bootloader should attempt to update the new correct files.
I have tried going into recovery, it comes up with a pic of a phone with a green circle, followed by a phone with a red triangle, followed by going into the boot cycle. This is with the sd card removed. Am I right in thinking that if I get the right files onto the card and then run recovery with the sd card in it will work?
If you run BOOTLOADER then it should do... Make sure you remove the old PG58IMG before putting the new one on.
Thanks so much, I will try it as soon as I can. I assume I will find the right stock rom somewhere on these forums?
webster84 said:
Thanks so much, I will try it as soon as I can. I assume I will find the right stock rom somewhere on these forums?
Click to expand...
Click to collapse
you will find anything and everything you will ever need on these forums
My Sensation was purchased in Hong Kong, after looking at the lists at shipped-roms this one - RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198358_signed.exe
seems to be most likely correct. Can anyone more knowledgeable confirm this? I would hate to flash the wrong thing again.
did you successfully get superCID ? if so i do believe that you can flash any RUU / ROM
Im not 100% on this as im still new to the sensation myself, But im sure thats the whole point in having SuperCID
Unfortunately I dont have superCID. I was following the instructions pretty slavishly and the superCID setup is one step after clockwork
Is there a way to get superCID in my phones current state? From what I am reading I need it to at least hook up to adb which it is not doing at the moment so I assume I just have to get the right onto the sdcard to have any chance of it working, right?
Yes, You need clockwork mod before SuperCID. Have you tried to re download CWM and put it on sd card ? It could have just been a bad download, it happens to us all.
Download it again, Remove the previous PG58IMG from SD Card via a card reader (if you have one) Put the new PG58IMG on SD card. Pull battery out, Put SD Card back into the phone, put battery back in and boot into bootloader (volume down + Power)
Bootloader should automatically find the PG58IMG and ask if you want to update it, Select yes and theoretically you should be fine..
EDIT: Use this one http://forum.xda-developers.com/attachment.php?attachmentid=706572&d=1314848127
Yeah, I have re-downloaded CWM and made sure it is the right one I have to wait until the shops open here so I can pick up a micro sdcard reader but I will try the new CWM first, and if that fails then I will try the stock rom. Am I right in thinking that neither of this is likely to make the situation worse, even if they dont work?
No providing bootloader still works everything is fix-able..
We aint messing with bootloader so u will be ok.
Cant believe you dont have a card reader lol....
lol, up until today the only thing I needed to be able to read micro sd cards was the phone. Well, I will be better prepared next time anyway.
The thing that had me worried is that since I originally didn't realize PG58IMG was not a unique file name I am almost certain that the one on my sd card at the moment is not even CWM at all but one of the updated firmware ones I mentioned in the OP that I very stupidly mistook for it. It feels like a really serious mistake to make, but happy to know that if the boot loader is working then it should be fixable. I wasn't sure even about that.
I think the PG58IMG is a unique code that the phone reads and recognises as something to be flashed / updated.
Ive seen various things CWM / Firmwares / Updates with the same PG58IMG title. so maybe youre right and the original file you downloaded wasnt the correct one.
Dont panic, Keep calm, Ask questions, Get answers...... This is the only way to avoid a bricked phone
Yeah, you've saved me a lot of stress already. Ill be back in a few hours with the results of the next attempt. Thanks again!
Ok, the news is not great. I got hold of a micro sd adaptor so I could plug it into my computer and removed the old PG58IMG. I put the correct one (downloaded from this thread) on the sd card and rebooted the phone into HBOOT. It recognizes the file on the sd card but gets a cid fail and there is no option but to reboot which goes into the boot cycle.
Whats worse is that doing this apparently fries the sdcard. I tried it twice, because I am sucker for punishment and in both cases the sdcard is unreadable afterwards.
Maybe I should try and explain more clearly that I am now sure the PG58IMG that I first put on the card and flashed I am sure is the Firmware from 3.32.401.x & 3.32.401.10x RUU from this thread. It appeared to successfully update before rebooting the phone into its current state, causing me to realize I had the wrong file. I dont understand enough to know exactly whats going on but it seems pretty bad. Do you think I should try a 3rd sdcard with the Shipped ROM on it or is there something else I should do at this point?
Edit - The second sd card wasn't fried after all, but I am still searching for a shipped rom that isnt in .exe format, since the phone isnt connecting to the computer by usb at all right now. Anyone know where I can find one?
Edit - Ok, now I have fastboot usb which means I can use .exe shipped roms. adb devices cant find the phone though which means I cant superCID it which means I still have to find the right ROM. Since I brought the phone from HK I am trying all the asian ones first. Anyone know specifically which file at shipped-roms.com is the right one?
You flashed firmware for ics rom, so the stock rom won't boot and you have bootloop. If you flash the 3.12 firmware ( works for both ics and gb) that will resolve the loop and you will be able to continue with the guide and flash cwm.
Sent from my HTC Pyramid using xda premium
Hey Stringer7, do you mean this Firmware from 3.12.401.2/102 RUU available in the same thread? I will download it and give it a try.
edit - Gave it a try, I get CID incorrect from it too. Seems like CID incorrect for everything I try to flash atm.
What is your CID ??
Unfortunately I dont know. I didn't know I needed it before I started and now since the phone isn't talking to adb I cant use it to find out. All I know is that I bought the phone from Hong Kong about 6 months ago. Is there a way to check the CID with the phone the way it is now?
firstly, Im not asking for a detailed explanation of what to do here.. I can read up on various sections, but I do need steps to follow. This phone is the most complicated thing to flash, give me ODIN and a galaxy S any day.
Im trying to upgrade to the latet open Europe.HTC-SAGA 401_9 not a custom rom, my DS is the same Radio Version so thats ok.
After following the various guides, What I have so far is:
1) the Stock HTC 401_9 Rom from File Factory.
2) Ive downloaded Goldcard Helper, fitted my 2GB SD and gotten the reverse ID
3) Ive d/l'd the GoldCard Image for my DS reverse ID
4) Ive d/l'd the HexD editor for making the goldcard.
5) I know about having FastBoot OFF, USB debugging ON and the phone USB set to Disk Mode for making the Goldcard and the USB to "Charge only" when flashing.
So, now what. Can I just flash the HTC Stock 401, or do I root it first. My Hboot is 2.000.002 and its S-ON.
The phone has Virgin UK Software, but its not Locked.. Ive had both O2 and Orange sim cards in and they work fine.
I just need to know the 1, 2, 3 .. steps for flashing this stock rom
Thanks in advance
Always helps to write your full bootloader screen.
ben_pyett said:
Always helps to write your full bootloader screen.
Click to expand...
Click to collapse
Im all for protecting your product against time wasting "bricked" returns, but Whoever at HTC thought of this system wants slapped... hard, Bootloader says:
### Locked ###
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822. 10. 08. 04_M
eMMC-boot
Aug 22 2011, 15:22:11
HBOOT
Then it lists on screen:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Hope that helps and hope you can give some steps. Seriously, Ive looked on here for days but there seems to be so many questions about different aspects and parts of the flashing, its confusing.
Thanks in advance
First of all, forget all about radios you know from Samsung.
At htc you can use every radio on every rom, there are only 3 possibilities you need to change radio:
It is shipped with a ruu you want to use
You face issues with radio related hardware
You want to be up to date
Ok, now to your question.
At HTC the bootloader version is important (only at stock roms).
If your bootloader has the same or a smaller version than the one from the ruu and your device had no branding, just reboot to bootloader plug it to your pc, enable fastboot usb and start the ruu.
If a branding is present and you want to stay with it, do the same with the fitting ruu.
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).
Tectas said:
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).
Click to expand...
Click to collapse
Ok I used this guide for the goldcard:
http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
So, because Im not changing anything about the kernel, just debranding to an offical ROM, once I set up my Goldcard, I activate debugging, copy the RUU 401_9 to SD Root of my Goldcard, click "Image CRC" from bootloader menu and it should install it.
Is that correct?.
Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?
NightOrchid said:
Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?
Click to expand...
Click to collapse
Image crc just checks your rom, got nothing to do with updating.
The ruu itself is a exe, means a windows program , do the steps i described before with fastboot, the only difference is that you need to create the goldcard before, otherwise the bootloader won't allow (if your lucky) you to flash the ruu with the different branding.
If it fails that way run the ruu without attached device as far as you can go without closing, don't close it and search for the rom.zip at your temp folder, copy it to another folder and close the ruu, rename it, copy it to the root of your sd and reboot to bootloader and let it flash it directly, just to say it, you also need a goldcard before you do it this way.
One additional thing, be sure you got a ruu for the desire s, i just say it, because your goldcard guide is for the desire, what is no real problem there, but a wrong ruu will always fail and if it won't lead to a brick at worst case.
Sorry Tectas.. Just wont work.. I created my goldcard, extracted the RUU, changed the rom name from "disk1" to PG88IMG as you said, copied to root of goldcard, selected Fastboot then bootloader, but it just doesnt detect any image or file.
I am struggling a little with your english because you are telling me too many different ideas, Im confused... instead of telling me.. just 1, then do 2, then do.. 3, but Thank you for trying, i appreciate your help..
I will try again later..
Small thing the file you copy to the sd card must be called (case sensitive) PG88IMG.zip
Swyped form ym Dersie S unsig XAD Permuim
First method:
1. Create goldcard
2. plug in your device
3. Reboot to bootloader and enable fastboot
4. Start the ruu at your desktop and follow the instructions
5. Enjoy
If it fails make sure the drivers are installed, by downloading and installing htc sync, but uninstall it straight after you installed it, the drivers will still be present but the program itself can cause problems with ruus and/or adb.
If it still fails, try the second method.
Second method:
1. Create goldcard
2. Start the ruu without attached device
3. Go on till the only remaining possibility is to close the program, but don't close it
4. hit the windows button + r, a window should pop up
5. Type %TEMP% into the textbox of this window and hit enter, the explorer should open up and show your temporary folder
6. Search for the rom.zip (make sure hidden files are down if you can't find it)
7. Copy it to another folder i.e. the desktop
8. Close the ruu
9. Rename the rom.zip to PG88IMG.zip (case sensitive)
10. Copy it to the root of your sd
11. Reboot to bootloader
12. Choose bootloader
13. Confirm the update with vol +
14. Let it update
15. Reboot by hitting power
16. remove the PG88IMG.zip, otherwise it will update your device every time you access the bootloader
17. Enjoy
Thank you very much tectas for taking the time to sort and explain this. The 2nd methord worked just fine. However, at the end of the update flash, bootloader said:
"image on device is newer, update aborted"..
It does say that my virgin software is 2.13.351... the image is 2.10.401, so, in computer world, the numbers 2.13 is newer than 2.10. This may not be the case of the ROM itself, becasue the date is 22 Aug 11, but theyve engineered it that way probably so you cant flash it Open Europe.
The great thing is, youve taught me about the desire s and how the flash updater works, plus I have a 2GB goldcard out of it for future custom roms.. so all is not lost.. thanks for the lesson, its much appreciated.. Im gonna have a go at routing next.
It would be great to sticky this or copy it as a very Basic guide to flashing an HTC Rom.
Many Thanks again Tectas
This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.
I have now found that my phone is actually Locked to Virgin Mobile (has a Virgin media splash screen on boot up). Sorry for the confusion about that:
I followed the advice of Tectas and followed this:
http://forum.xda-developers.com/showthread.php?t=1399331
everything went great until I got to the end of the procedure and I only go the
"$" which after typing line 5: adb shell /data/local/tmp/misc_version -s
said "access denied" then mentioned "blue flames".
On page 6 or 7 of that thread, someone mentions this "blue flames" as being a new security mod that HTC have implemented to stop modding at all.
Is this true?.
Also, Virgin mobile and other places have quoted me £15 to unlock my DS. £15 seems alot of money, but would an unlock help (would it be worth it) for me being able to flash both Stock and custom ROMS.
I do enjoy the challenges of modding, so to me this is frustrating.
cheers
The $ indicates you have no root access, i must confess i never heard about the blue flame before, but also have to say, i never got deep into the downgrade stuff, because i used xtc clip to unlock my device, which made my device s-off and debranded.
If those Sellers use the same method, your good to go and spend the money, it saves you from a few traps you can run into with other methods (i paid €20 about a year ago), but you need to be aware that this is a hardware unlock which is irreversible, what can bring problems at warranty purpose (but must not).
Your second choice would be to use htcdev at first step and get root and so on afterwards, the downside here is also warranty, because your device is stated as unlocked at the htc database and if you leave it this way and won't use it to gain full s-off you also need to flash the kernel for each new ROM yourself with fastboot, because the recovery got no write permissions there.
If the seller would also use htcdev, safe the money, you can do it yourself, at xtc i can recommend it, but it's your choice.
Thanks for the advice Tectas. The guy in the street said it would take about 1 hour.. not sure if that helps to know. I suppose with Virgin, theyll be removing their own locks, so the virgin way might be better.
Also, the phone was bought from a 2nd hand shop, it was an unwanted upgrade someone just traded in without using it, the box it came in and the outer shell of the phone has no branding whatsoever.. thats why i was confused about it being locked.
Anyway, Ill have a think about who to go with and ill ask which methord they use before I hand it over.
Thanks again.
Tectas said:
This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.
Click to expand...
Click to collapse
Its Done.. phew.. hehe. After I got back to Virgin 1.31, just used the goldcard with rom.zip and it worked fine. 1 thing though, doing it this way flashes the rom in 7 stages, so what ever you do, when it reboots after the 1st install, do not think its repeating itself.. leave it. i Nearly did that, anyway, I sorted things using this thread:
http://forum.xda-developers.com/showthread.php?t=1443636
As long as you follow it to the letter, it all goes fine, the whole thread is really good support as well, so if anyones interested, read through the whole 13 pages (so far).
Also had access to the phones Recovery menu, so wiped Cach partition and did a factory reset, also probably not necessary, but backed up my SD card and formated it under the new OS.. I find this is always good on a new rom, for the file table and prevents app errors.
Happy i now know how to flash a rom, didnt quite root it yet, just flashed a stock RUU first.. which is what you should do if, like me, your new to this.
Anyway, Open Eu 2.10.401.9 is sweet and slick smooth.
Have a good one all, Thanks Tectas.
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
First, what phone do you have? We will need the first five lines of your bootloader to help you later.
If all you need right now is to try and recover the files and you are on windows, here is a freeware file recovery program I've used in the past. You will need to be able to mount your sd card in TWRP.
http://www.softpedia.com/get/System/Back-Up-and-Recovery/Recuva.shtml
Once you get that done, you do have some problems to work through (Android Revolution Rom is not for our phone.)
beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
Ok, first, you're all over the place. Why did you install a radio+RIL when it explicitly tells you not to? It's actions like this that get people like you into a lot of trouble and destroys phones.
Secondly, there is no Android Revolution HD for this device. I believe you have the HTC One XL / at&t One X (Evita) judging from your post, but like I said there's no ARHD ROM for the Evita, only for the HTC One X (Endeavoru). This leads me to believe that you're jumping between the two device forums, very bad idea, none of the stuff from the Endeavoru forum is compatible with our phone.
You're lucky the ROM install stopped otherwise you would have bricked your phone. Long story short, you have no OS because the ROM install didn't complete, you have a corrupt boot partition because you flashed the ARHD boot.img which isn't compatible. In future do not stray outside our device forum for any reason at all. Here's our forum main page, bookmark it:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Next. Performing a factory reset in TWRP recovery does not wipe user data (images/music etc). I'm not sure what you've done but the factory reset in recovery wasn't it. A factory reset performed in the bootloader does however corrupt the sd card, so never do a factory reset from the bootloader.
You might have a chance at saving some of your data using a data recovery tool in Windows. You'll need to mount usb storage in TWRP for Windows to access the sd. Do not under any circumstances do any writing to the sd card before you attempt to save your data.
In conclusion, you've made numerous mistakes with your device. You need to slow down a bit and educate yourself a bit better, a lack of knowledge when it comes to modifying devices is a very dangerous thing.
Please post the first five lines of your bootloader.
Sent from my Evita.
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
ok guys thanks so much so far i will pick up again after work today.
bootloader says:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.19as.32.09.11_2
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012,21:08:24
I'm 99.9% i was s-off before this all...
There isn't and never has been an Android Revolution ROM in this forum. It's kinda easy to make the mistake, the forums are named similarly.
I'm 99.9% sure you weren't s-off before all this. A phone can't change the security status without you doing it manually. It just can't happen. Did you actually go through either the Facepalm or Rumrunner s-off processes?
Well, you definitely have the Evita (HTC One XL / at&t One X) so make sure you stay within the forum I linked to earlier.
Good luck with attempting to recover your data, I hope you get at least some of it back.
Sent from my Evita.
Ok so as far as mounting my sd card in twrp, there's something up with my screen touch input I think... I am not able to click that particular box in the 'mount' menu. It seems like that part of the screen was not clickable when installing roms and such but once I get into android everything works perfectly.
Is there a way to rotate the screen in twrp?
Also by looking at my bootloader info once I get my sd card mounted and recovered best as I can, what is my best plan of action? Re-lock and flash a stock att ruu and begin from scratch or what? Or just try and load a correct radio and rom? I'm not a complete newbie I know I made a foolish mistake but I have done this quite a few times playing on the inspire, cha-cha, my kids nabi 2 tablets and on this att one x. This is the first time I have gotten really stuck in probably 35 flashes. Just this time I might be over my head...
To be honest I've never tried rotating the screen while in recovery, so I'm not sure about that. Exactly which recovery type (CWM/TWRP) and version number are you using?
I think your best plan of action would be to run an RUU, this will bring everything back to the way it should be. You're lucky in the sense that you're still on quite an early firmware version, so you should have a couple of RUU options. One thing to be careful of though, absolutely do not run a jb RUU if you have SuperCID, it will brick your device. SuperCID + s-on + jb RUU = brick. We should check your CID just in case, connect your phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita.
beppomarx said:
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
Click to expand...
Click to collapse
There is absolutely no ARHD ROM for EVITA. You've made a grave error, and as timmaaa mentioned, you are lucky your phone isn't a paperweight now.
EVDEAVORU is partitioned completely differently from EVITA, so all bets are pretty much off on whether your data is still intact or not. The ROM itself may have overwritten your data. Also, if you happened to do a factory reset in hboot instead of TWRP (as you mentioned) this will corrupt the SD card on modded EVITAs (known issue, and somewhat common error).
Your best bet is to get the phone back up and running using timmaaa instructions. Then see if the files are still on the SD. If the data files aren't easily visible, you can also try data recovery programs to see if they can be salvaged (sometimes corrupted files get dumped to a temp folder, or otherwise recoverable).
But I wouldn't hold my breath on recovering the files. This is what always puzzles me (why folks never back their data, then freak out when its gone of damaged). If your data is important to you, its important enough to back up. And there are so many easy methods to do so (with built-in cloud backup apps and whatnot) yet so many folks neglect to do that. And all you are left with is regret when things do south. Its pretty much a no-brainer to backup anything important to you when modding the phone. I'm puzzling why so many folks never do it.
So since I have the 1.09.000 hboot i am going to download and install this:
1.85.502.3
File Timestamp: 25/05/12
Publically Seen: 06/06/12
Android: 4.0.3
Kernel: 3.0.8-01155-gca24d1e
hboot: 1.09.0000
radio: 0.17.32.09.12_10.86.32.08
adsp: 28.1.0.32.0504
wcnss: 1031120A
tp_syn3202: 3.0_PR1100755
tz: 001.031.511
sbl1: 001.031.503
sbl2: 001.031.501
sbl3: 001.031.502
OTA: OTA_Evita_UL_Cingular_US_1.85.502.3_R2_NEW_NFCPHON ESTORAGE-1.73.502.1_release_263287jkmeqj8u75z409z9.zip
RUU: RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe (Download)
Source: evita-ics-crc-3.0.8-271616b.zip
is this my best bet? I am going to try and check my CID status right now just need to download the android SDK and get that going...
**EDIT**
my CID is 11111111. is that superCID?
**EDIT**
looking for a way to remove superCID. If i just go S-off am i OK to run a RUU or should I keep looking to change my CID back?
**EDIT**
just downloaded WinDrid HTC One XL Toolkit and seems to be up and running fine. my plan so far is to S-off and run the RUU I posted above but I will wait for someone to chime in before I do anything else.. I feel like I am on the edge here and don't want to brick it... I can't find any way so far to return my CID but from what I read if I am S-off it should keep me safe.
S-off won't work unless you're able to boot into a ROM. I'd forget about using a toolkit for now, it completely bypasses some much needed learning, and doesn't always work anyway. I believe all you need to do is relock your bootloader and then run the RUU.
Sent from my Evita.
Ok I will look into how to re-lock that after work today. Can anyone else confirm this? Not that I don't trust you but wording it like 'I believe this will work' makes me ask again...
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Sent from my Evita.
timmaaa said:
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Click to expand...
Click to collapse
ICS RUUs are free of the S-on and SuperCID bug. Plenty of folks have flashed that RUU (such as 2.20) with SuperCID with no issue.
so I am going to relock the bootloader, it's as simple as 'fastboot oem lock'? that's it? before doing so should i bother s-off first? here's my plan of action:
s-off
relock bootloader
run 2.20.502.7 ruu
unlock bootloader again
install twrp
load custom rom
that should work correct?
If you s-off first, I believe you do not need to relock the bootloader to run the RUU. Just s-off, then run the RUU.
As I've previously mentioned, you won't be able to get s-off unless your phone will boot a ROM. The above process looks right.
Sent from my Evita.
got back to stock just fine, now to work my way back to modded. You guys are the best thank you a million.
Please hit the thanks button on any post that you've found helpful on XDA.
Sent from my Evita.
Remember also to either s-off or change cid back to normal, it will assist in the future if you get in a jam like this.
Although s-off and flashing a rom for a different phone(like you did) may have ended up much worse as some of the checks that likely saved you will be disabled.
At very least do not OTA/RUU update to Jellybean while you are s-on and supercid!
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
iceterminal said:
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
Click to expand...
Click to collapse
I gotchu my friend ;D http://www.htc.com/us/support/htc-one-mini-att/news/ That is the ruu for the htc one mini
abzboi said:
I gotchu my friend ;D That is the ruu for the htc one mini
Click to expand...
Click to collapse
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
iceterminal said:
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
Click to expand...
Click to collapse
Ah I read that it will work too if it is fastboot which is why you were suggesting it. I'm wrestling with fastboot drivers and windows 8.1 so it is recognized so I dualbooted into ubuntu which can communicate via fastboot so I'm hoping WINE will run and flash the RUU .exe
So I ended up rebuilding an older laptop to Windows 7 and ran the RUU executable and it looked promising at first with the updater recognizing the device and displaying what software version and stuff.... but then when it rebooted into hboot with it's process, the update failed.. not sure if it matters but it was "updating" from the same version as the current version. I was hoping this would be a fresh install. So now I'm looking into maybe doing a fastboot oem unlock and flashing a rom myself. Not sure if this will help me get the phone back from the dead, but going to do some more reading and exploring. If anyone has some shots-in-the-dark they would like to offer, I'm up for trying them.
I hope you would be able to fix it.
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
iceterminal said:
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
Click to expand...
Click to collapse
Have sent you a PM re your issue.....
Re flashing recovery without fastboot (locked bootloader), it can be done, but only, as far as I know, via the phone os using CWM manager or Flashify (which is a cool app!)
wanted to close the loop on this thread that nelvinchi and I literally tried everything we could think of to bring the phone back to life with no avail. Much respect out to nelvinchi for taking his time to help me out! We've determined that the device has a faulty memory chip and cannot be recovered...
Mine just did the same thing and I can't get through to anything I need help also if you have found a solution
Help my
provided you solve a problem with one htv mini.my I have the same problem, please help me
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
stampy101 said:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
Click to expand...
Click to collapse
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
FUBAR?
timmaaa said:
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
Click to expand...
Click to collapse
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
stampy101 said:
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
Click to expand...
Click to collapse
There's no point in attempting s-off at the moment because s-off requires that a working OS is installed. You can tell whether you're s-off by looking at your bootloader, it'll say s-on or s-off in the first line under the unlocked and tampered banners.
Your problem with your sd might be that the version of TWRP you have installed is too old, only the newer versions are able to fix a corrupt sd card. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now try wiping and mounting the sd card again. Once we have that sorted out we can move onto getting your firmware updated.
Sent from my Evita
OK! Looks like we are getting somewhere! It is now mounted.
Now you can copy files across to flash. You'll need to get s-off now so you can update your firmware. You'll need a bootable OS installed to do that, I'd suggest installing Kickdroid and then you can attempt getting s-off via the Rumrunner method.
Sent from my Evita
You are awesome! Thank you so very much for your help. Up and running.
How far have you gotten?
Sent from my Evita
S-Off and firmware updated and running with different ROM's. I'm golden man. Unless you can think of something I should consider?
As long as you're on the 2.15 firmware or higher, you are indeed golden. I was just curious.
Sent from my Evita
Hey there, I just noticed you made a donation to me with this thread as the reference. I just wanted to thank you, that's very generous of you. Donations aren't expected in return for my assistance but are greatly appreciated. Anyway, thanks again and have a great day.