Related
Hi all, well i was playing with my Desire S trying to install the generic wwe rom on it since it is brands, and ended up messing up the phone real badly.
Well i used the good old way of creating a gold card and then flash the RUU. The first time went well, i flashed the generic 1.28.401.1 rom on it, retaining the 0002 boot it had.
Then i went to flash the 2.10 wwe RUU and this time things went bad. For some reason the gold card powers were not evoked and it gave me "CID error" but, the all mighty 2.00.0002 hboot was flashed on the phone before it gave the error. So i had to downgrade the bootloader and i used this great guide as a help but once again things went wrong.
I flashed a pre rooted RUU 2.10 rom using 4EXT recovery as the guide tells to do but, i have no wi-fi and usb connection on the rom. This means i got no way to connect the phone to a pc to change the misc_version file and don't even have wi-fi. So i end up asking for any help here as the phone is left in a very bad situation that i can't see the way out...
Try to reflash same ROM again.
Sent from my Desire S
I believe you should have named your thread "I really messed up my Desire S", as the current title is sort of misleading ;-).
In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.
Rapier said:
In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.
Click to expand...
Click to collapse
Well the initial ROM i had on the phone was a branded Vodafone PT and i can't find that ROM anywhere and for some reason goldcards are not working after the bootloader was flashed by the RUU.
I still have the 4EXT recovery and usb works in it. Flashing a ROM via the PG88IMG only works if the RUU has the right CID as the phone is branded, now i don't know if flashing a rooted ROM using that procedure will work. The other thing i may try is flashing an older rooted ROM, like the 1.28.401.1 and see if the wi-fi and usb works.
Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.
smash_07 said:
Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.
Click to expand...
Click to collapse
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.
Skanob said:
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.
Click to expand...
Click to collapse
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?
smash_07 said:
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?
Click to expand...
Click to collapse
It would really help if you have given your bootloader details.\
Things you still can do:
1. If hboot is updated to 2.00.0002, then you need to unlock it, flash custom recovery via fastboot, flash custom rom, usable phone.
2. If hboot is S-OFF, same as 1 but skip unlocking. Again, usable phone.
Also, there are a lot of ways for you to change your hboot once you are S-OFF. Use search.
You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium
I my case, that was may of this year, I send my desire (not s) back because of bootproblems, and they reflashed it for free. This was in the Netherlands so don't know how easygoing they are in Portugal, but it's worth a shot I guess.
lowveld said:
You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Well i can say that this has worked. I flashed the boot.img form the CM7 rom and it worked perfectly, it booted CM7 rom and have wi-fi and usb connection. Now the only thing left is to be able to flash official RUUs passing tne CID error which for some reason the Goldcards are not bypassing.
But many thanks for your help
(ou como se poderia dizer, obrigado pela ajuda)
OK.. here is the deal: HTC One S, T-MO, flashed recovery (TWRP), NO ROM would work in the WiFi dept. I tried flashing the radio and no matter what I couldnt get it to flash the 1.5 or 1.84 radio. TWRP would take forever and say it was complete, but the radio version still said 1.04 (or something) in hboot.
Also, I tried going back to a Stock Tmo RUU and it would ALWAYS fail at the signature part of the install EVEN THOUGH I relocked my bootloader.
SO- I unlocked my bootloader, I flashed CWM. Works like a charm.. or so it seems. I flashed the radio and it will only boot into CWM. I can flash a ROM but it still only boots into CWM. I cant even get into fastboot. This sucks.
Ideas anyone?
What happens if you do adb reboot bootloader from your computer while the phone is in CWM?
It reboots, the screen flickers for a millisecond or so (I am sure its probably trying to load hboot and gives some type of error so fast that I can't see) and then it goes to CWM. I am thinking about flashing it back to team win recovery...
mbolden said:
OK.. here is the deal: HTC One S, T-MO, flashed recovery (TWRP), NO ROM would work in the WiFi dept. I tried flashing the radio and no matter what I couldnt get it to flash the 1.5 or 1.84 radio. TWRP would take forever and say it was complete, but the radio version still said 1.04 (or something) in hboot.
Also, I tried going back to a Stock Tmo RUU and it would ALWAYS fail at the signature part of the install EVEN THOUGH I relocked my bootloader.
SO- I unlocked my bootloader, I flashed CWM. Works like a charm.. or so it seems. I flashed the radio and it will only boot into CWM. I can flash a ROM but it still only boots into CWM. I cant even get into fastboot. This sucks.
Ideas anyone?
Click to expand...
Click to collapse
mbolden said:
It reboots, the screen flickers for a millisecond or so (I am sure its probably trying to load hboot and gives some type of error so fast that I can't see) and then it goes to CWM. I am thinking about flashing it back to team win recovery...
Click to expand...
Click to collapse
Try flashing the boot.img thats compatible with your ROM. As for going back to stock try this http://forum.xda-developers.com/showthread.php?t=1927939 If you're on Hboot 1.14 then the T-Mo RUU's wont work for you. I had that problem.
antny said:
Try flashing the boot.img thats compatible with your ROM. As for going back to stock try this http://forum.xda-developers.com/showthread.php?t=1927939 If you're on Hboot 1.14 then the T-Mo RUU's wont work for you. I had that problem.
Click to expand...
Click to collapse
OK.. I thought about that.. but my question is: How can I flash a boot.img if I cant get into fastboot? I installed the trickdroid ROM and I have the boot.img from the zip. I DID try to go back to stock (when I could still access everything pretty easily), but It got stuck on the signature part of the RUU. I went back to trickdroid and all was well sans the WiFi not working.
Can I flash a boot.img via ADB since that is the only thing really working right now?
Thanks
-M
If you still need help...
I'm sure you guys have figured this out by now, but I Solved a problem very similar to this one in my Thread. I was able to return to Stock while still being Rooted.
New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL
citats said:
New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL
Click to expand...
Click to collapse
Have you tried flashing with an older version of twrp
Verstuurd van mijn HTC One S met Tapatalk
citats said:
New to HTC One S.
Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
Click to expand...
Click to collapse
Use 2.3.3.0 instead...
Thanks guys, I have actually tried 2.3.3.0 due to reading that in another thread. What I see is I can get various aroma installers to start, but at the actual install they seem to fail gaining access to areas on the phone. It's worth mentioning that I have reflashed stock boot img and stock recovery, relocked and attempted various RUU's but I understand that the hboot at 2.15 is most likely why that method fails.
I'm unlocked again but I think I'm going to try reflash stock recovery relock clear and reset all storage etc. then unlock use twrp and re-attempt a flash.
Any suggestions on a rom that should'nt have issues with hboot 2.15?
To flash RUUs you need to be on stock recovery, not custom.
2.15 came with JB. Trickdroid or ViperOneS would be sense roms, else you could flash CM 10.1 or derivates (AOSP/AOKP).
As long as you flash the according kernels in fastboot mode you can also use ICS roms. That doesn't matter.
--- edit
as with 2.15 you could only flash the 3.16 RUU which still isn't available (the one here is for ONE S SE and exits with errors. To flash earlier RUUs you will need an earlier bootloader version. There are two ways: To downgrade bootloader or s-off. As downgrading is a pain you should think about s-off.
Thank You
Yes I was on stock recovery and stock boot img and relocked during that attempt.
does the hboot version matter?
(based upon what I have read it won't flash if my hboot is newer)
Ok, just answered this as edit while you posted. lol
Thank You again!
I have looked into downgrading and a pain might be an understatement I'm looking into the One S toolkit to see what i can do for me... Here's hoping the RUU with hboot 2.15 gets leaked soon.
Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:
rootrider said:
Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:
Click to expand...
Click to collapse
OK that would be great thanks!
WiL
Holy crap that was painful...
I once again have a rom running! I did so many things but in the end I pushed Energy Rom to the device and it's boot.img after wiping multiple times reformating. Energy Rom is the only one that would complete install without write errors. Very strange stuff but for now i am happy.
Thanks again man!
Damn, I searched this thread for 20 minutes... :cyclops:
Which recovery are you using?
Anyway you should better use TWRP <= 2.3.3.0 for flashing roms.
(gonna write your pm now, will take some time and sorry for the delay!)
I'm all good now. Running Venom and very happy. I appreciate your efforts.
The recovery question tho I had to swap back and forth between twrp 2.3.3.0 and the most recent cwm. Mainly because of I could only send adb via twrp and I could only use adb shell with cwm, the nightmare is over!
Sent from my HTC One S using xda app-developers app
I'm at a loss I've been trying for hours with not luck at restoring my phone. there is no backup. no roms will seem to boot. my SD card was wiped. i can boot into recovery and see my SD card and everything. and when trying to revert to a stock rom I use "fastboot getvar version-main' to find what version i need but it comes back blank. i have tried relocking and running a ruu with no luck
I have it unlocked
CID is stock with telus
hboot is 2.14
radio -0.18a.32.09.01_2
Cbaird said:
I'm at a loss I've been trying for hours with not luck at restoring my phone. there is no backup. no roms will seem to boot. my SD card was wiped. i can boot into recovery and see my SD card and everything. and when trying to revert to a stock rom I use "fastboot getvar version-main' to find what version i need but it comes back blank. i have tried relocking and running a ruu with no luck
I have it unlocked
CID is stock with telus
hboot is 2.14
radio -0.18a.32.09.01_2
Click to expand...
Click to collapse
I'm going to guess you're S-ON. Also, Good thing Telus doesn't make a 3.17 RUU or you'd have a shiny paperweight. You're messing with dangerous things and have no idea what you're doing.
To get a rom to boot, flash it and then extract the boot.img from the rom and
fastboot flash boot boot.img
then S-OFF once you get a rom to boot so you can RUU in the future if you need to
Still stuck in the boot loop at the white htc screen. does it matter the rom? as well when flashing the rom it comes back successful however says there is no md5 file found
Cbaird said:
Still stuck in the boot loop at the white htc screen. does it matter the rom? as well when flashing the rom it comes back successful however says there is no md5 file found
Click to expand...
Click to collapse
the rom should not matter.
Did you check the MD5 after downloading?
There is never an md5 file within the rom so it will always say that. You have to manually check the md5 with an md5 checker.
What rom are you flashing?
exad said:
I'm going to guess you're S-ON. Also, Good thing Telus doesn't make a 3.17 RUU or you'd have a shiny paperweight.
Click to expand...
Click to collapse
Brick from RUU while S-on and the Telus CID?
the nightly cm rom 10.2 from the 27th
redpoint73 said:
Brick from RUU while S-on and the Telus CID?
Click to expand...
Click to collapse
Ack true I forgot no supercid *facepalm* im rusty.
You should ba able to boot it. Did you check the md5?
checked and tried a different rom (slimbeam) and still stuck in boot loop. does it matter the order in which i flash the boot.img and the rom in?
It shouldn't matter what order you flash them in, before or after the ROM is fine. Can you elaborate on what you were doing to the phone before all this happened?
Sent from my Evita
http://forum.xda-developers.com/showthread.php?t=2450305&highlight=no+main+version
I was having this issue then I got it to boot into recovery mode so I figured i got it fixed but its stuck in a boot loop now with no rom
Ok but what caused all this to happen? Phones don't usually just get stuck in that situation on their own.
Sent from my Evita
timmaaa said:
Ok but what caused all this to happen? Phones don't usually just get stuck in that situation on their own.
Sent from my Evita
Click to expand...
Click to collapse
exactly the same way as the post says relocking the phone to go back to upgrade the hboot to flash roms that required them.
Ok, but you need to be more specific if you want help, linking to someone else's problem isn't really ideal. I'm gonna have to guess that you relocked the bootloader and ran an RUU? Which RUU exactly did you use? What's the filename?
Sent from my Evita
relocked the phone through fastboot. then tried to run this ruu RUU_Evita_UL_TELUS_WWE_1.91.661.4_Radio_0.18a.32.09.01_2_10.94.32.20L_release_266645_signed.exe to update hboot to 2.14 which is where it is now. however like the other forum my install failed and only got half the update. used the fix in the other forum to get it to at least recovery. where i discovered the my sd card had become corrupted fixed that issue and everything seem to be working in recovery when i went to flash a new rom. attempted to flash new rom and now all i get is a boot loop
Ok, the RUU only partially succeeded? You might need to try running an RUU again in that case, as that's probably what's causing your issues at the moment.
Sent from my Evita
tried running it again and get error 155 but for telus there is only 1 ruu and one ota
You'll have to research what error 155 means and try to rectify the problem.
Sent from my Evita
its says its the wrong ruu however there is only this ruu and an older ota for telus
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Click to expand...
Click to collapse
Cbaird said:
its says its the wrong ruu however there is only this ruu and an older ota for telus
Click to expand...
Click to collapse
you cannot run that RUU because you're hboot is from 3.17 and that's an older RUU you need to be S-OFF to run an older RUU. You can try running the OTA for 3.17
You will need to download the 3.17 telus ota zip. Extract the recovery.img, copy the 3.17 OTA zip file to the phone, flash the recovery img in fasboot, boot to recovery, it will say cant load sd card, this is normal as it's looking for an external sd card of which there is none. select install from phone storage or install from internal storage. If you pick install from sd card it will error as there is no external sd card. then select the telus ota zip file.
I dont see and recovery.img in the file. there is a boot.img though
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk