Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
HTC Desire S GSM
unclocked via htcdev
S-ON
hboot: 2.02.0002
Radio: 3831.19.00.110
Latest CMWR
Gets stuck @ white screen
Tried:
factory reset / wipe / dalvik / batt stats
reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.
Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.
fstarockr said:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
Click to expand...
Click to collapse
There are so many people, blindly walking in to troubles just because they do not read,
and you seem to be one of them....
When you unlock your device via htc dev, your device stays s- on,
it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )
via fastboot
through command:
fastboot flash boot boot .img
Without it your phone will never boot...
Recovery you flash via fastboot as well via command:
fastboot flash recovery recovery.img
Then , when you have it, reboot your device to recovery
and flash superuser and its binaries
And that woud be all you have to do in order to have rooted and booting device...
Edit: Now i've seen your other post- it is a 100% the one im reading now,
You should know it is enough to post your question once,
people'll find it...
Because of impatience you're in trouble already with your phone
tx -
tx for that info - ill give it a go.
I reposted because some1 there said i was in the wrong section and supplied a link for the correct section (here) - so yes, i reposted to get the correct replies.
not to digress:
but as for not reading - i can assure u ive read alot. Been a freelance developer for 15 years. That doesnt mean that rooting often requires a handful of little hacks when things dont go smooth. Just like alot of programming tuts, the rooting ones have a similar "assumption" that u know whats half potting, and what will cause what and what wont. All the articles i read i made sure were either 2012 or 2013 - there is ALOT of old non applicable info around, I stick to xda of course as i really trust this place. as usual, not all is 1-2-3. thats all.
asgardr said:
There are so many people, blindly walking in to troubles just because they do not read,
and you seem to be one of them....
When you unlock your device via htc dev, your device stays s- on,
it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )
via fastboot
through command:
fastboot flash boot boot .img
Without it your phone will never boot...
Recovery you flash via fastboot as well via command:
fastboot flash recovery recovery.img
Then , when you have it, reboot your device to recovery
and flash superuser and its binaries
And that woud be all you have to do in order to have rooted and booting device...
Edit: Now i've seen your other post- it is a 100% the one im reading now,
You should know it is enough to post your question once,
people'll find it...
Because of impatience you're in trouble already with your phone
Click to expand...
Click to collapse
Well thats true, obvious things for me do not have to be obvious for
somebody else- one sometimes forgets that- begging your pardon
If not for XDA, i'd've known not much at all...
I've given the shortest and simpliest way that never failed me before
so, i truly hope, for you it'll turn out to be usefull as well- with no further accidents...
As for comming back to stock: you must relock device's bootloader before flashing,
otherwise procedure will always be throwing an error....
Success
details details
As for coming back to stock: you must relock device's bootloader before flashing,
otherwise procedure will always be throwing an error....
Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed - my apologies as i try wrap this up..
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
#S-on/Off
I have been unable to get mine to off -
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.
If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.
Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Success[/QUOTE]
fstarockr said:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
HTC Desire S GSM
unclocked via htcdev
S-ON
hboot: 2.02.0002
Radio: 3831.19.00.110
Latest CMWR
Gets stuck @ white screen
Tried:
factory reset / wipe / dalvik / batt stats
reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.
Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.
Click to expand...
Click to collapse
i think u have MDDI pannel (not the one compatible with cianogen) try to flash a sense rom
have a look of THIS
Hi
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
Click to expand...
Click to collapse
On HTC devices, the bootloader is called HBOOT. This is a 100% device-specific program whose sole purpose is to initialize the hardware so that an operating system (such as Android, i.e. Linux) can load. If your bootloader is damaged, your device is 100% bricked.
To prevent tampering with the system, HTC have locked ("S-ON") their bootloaders so that they won't accept unsigned ROM images. So, on your HTC phone, you cannot install any operating system other than what's provided by HTC. You can partially lift these restrictions by unlocking via htcdev, as you have, or you can fully lift all restrictions on your device by going S-OFF. S-OFF-ing the Desire S is done by exploiting a bug in HBOOT version 0.98 and overwriting the bootloader with a patched version ("Revolutionary") that has all write protection disabled.
In order to flash official HTC upgrade packages ("RUU"s), you can be either S-ON or S-OFF, but if you're S-ON you MUST lock the bootloader. Anything that's not a RUU can (only) be flashed without re-locking the bootloader.
Having an unlocked bootloader is only relevant when flashing new ROMs or recoveries. Having an unlocked or locked bootloader per se will not affect booting at all, with one well-known exception: if you're S-ON and htcdev unlocked, the write protection installed by the bootloader is still on for the bootloader, radio, and kernel partitions. This means that you can't flash kernels from a running OS -- only from the bootloader. This means that when you flash a custom ROM, it will not be able to flash the kernel automatically, you have to do that manually via fastboot. Failing to do that will result in your phone freezing on the white HTC screen when it tries to boot.
#S-on/Off
I have been unable to get mine to off -
Click to expand...
Click to collapse
That's expected, because you're most likely not running a ROM that has a HBOOT version that is vulnerable to the exploit used by Revolutionary.
edit: nope, your HBOOT is newer than 0.98 and is therefore not exploitable.
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
Click to expand...
Click to collapse
Only official HTC RUUs require that the bootloader be locked.
Cyanogenmod can only be installed with the bootloader unlocked, but you may always re-lock after installing it. Remember to manually flash the boot.img (that's the kernel) via fastboot directly after flashing CM through your custom recovery.
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
Click to expand...
Click to collapse
A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Click to expand...
Click to collapse
The recovery is a specialized mini-Android OS that allows you to flash new software (such as unofficial ROMs such as CM) to your device. What recovery you have installed has no bearing on your main OS. If you're htcdev unlocked, the only way you can install a custom (i.e. non-stock and non-crippled) recovery is via fastboot; if you're S-OFF you can use the 4EXT updater app from Google Play.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
Click to expand...
Click to collapse
Why do you want to install stock?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Click to expand...
Click to collapse
boot.img is inside the zip of the ROM you're going to flash.
I hope I've been able to answer most of your questions. If you require more help, please search first, and if you can't find what you're looking for, please do ask.
fstarockr said:
Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed - my apologies as i try wrap this up..
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
#S-on/Off
I have been unable to get mine to off -
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.
If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.
Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Click to expand...
Click to collapse
# bootloader
The bootloader must be locked to install an RUU (stock rom), it must be unlocked to install a custom rom.
# s-on / s-off
If you unlock your bootloader through htcdev.com, the phone stays s-on. This means you can't install a different radio or hboot (mostly not necessary anyway), or write to the /boot partition or recovery apart from in fastboot.
That means, after every rom installation, you have to reboot to bootloader (fastboot), and flash the boot.img (extracted from the rom you installed)
# recovery
A custom recovery is a must for flashing custom roms (it's where you flash the zips) , I recommend 4ext, other known recoveries are Cwm and twrp. Be aware that you can only flash recoveries in fastboot (not through an app) , if your device is s-on
1.s-off means you can flash anything you want to all partitions on the phone..
S- on (htc dev unlocked) bootloader is unlocked so you gain acces to system partition,
but neither to radio partition nor bootloader itself, so you cannot freely change them at will.
While flashing rom via recovery, ( when s-on) each time you'll have to flash boot.img of that rom -via fastboot as well, because kernel partition is not reachable from recovery ,
Boot img is to bo found in the rom zip ( namely boot.img).
and is absolutely necessary to flash that particular one
or, if existing- other that is compatible with rom of you choice and phone model..
Assuming- to flash any custom:
-bootloader has to be unlocked
-you need custom recovery ( 4ext or clockworkmod)
-rom is packed in zip format ( flashing via recovery)
-each time you change roms, you have to flash boot img of that particular rom,
( to be found inside that rom.zip)
from recovery must reboot to bootloader (adb reboot bootloader)
then flash boot.img...
If it says ok you may now begin booting in to system
Recovery:
To flash anything like roms or mods etc.
custom recovery is required,
stock htc recovery is been there for slightly different purpose,
and is, well.. rather useless for any device customizing...
1.when s-on: is necessary to flash recovery via fastboot-as an < .img > file
so, when it is zipped- extract the file: xxxyy_recovery .img,
change its name just to recovery.img, and flash it...
2.when s-off : is possible to update it via market app (but only when s-off)
RUU: is a stock phone image, and ussualy contains radio and bootloader itself,
flashing it, may upgrade your device's components that normally -while s-on-
you'd not be able to touch, but there is a price:
1.you must relock bootloader: fastboot oem lock
otherwise you'll always be getting an error
(but if you still keep unlock_token from htc dev-can unlock it again)
2.you must establish
A) your device's CID - Customer IDentification number (whether is generic or carrier branded)
B) your phone's software version region ( wwe or asia or..etc)
C) software version ( froyo, gb, ics )
because, normally bootloader will not let you flash lower RUU version
than itself,
( every RUU contains bootloader, so the one working on the device
will never let downgrade itself- well not without a little trick of course-this is XDA)
Bootloader:
It is advised to use only bootloaders for your device- if you try to flash something slse,
you'll end up with a dead phone ( no fastboot no nothing- paperweight)
While s-on you cannot upgrade bootloader in any other way but by flashing official RUU...
While s-off it is possible to write to bootloader partition ( but always a bit risky)
There are:
- stock bootloaders
- patched ( revolutionary )
- eng bootloaders ( modified - possible to overwrite it by different one in case it is necessary)...
...well... now, there is much more to it if one wants to know everything
if there is something you'd like to know in particular- write back...
fantastic answers and explanations last 3 chaps!!!!
Guys - excellent answers thank you SO much! i have a MUCH better idea now thanks to your no attitude clear answers! I think this should be a sticky as it clears SOOO much confusion for a multitude of users - and fills the forums with the same problems over and over - simply because ppl lack this base understanding b4 opening the darn prompt lol (like me!!)
So to recap"
While flashing rom via recovery, ( when s-on) each time you'll have to flash boot.img of that rom -via fastboot as well, because kernel partition is not reachable from recovery ,
Click to expand...
Click to collapse
so by following these directions:
Assuming- to flash any custom:
-bootloader has to be unlocked
-you need custom recovery ( 4ext or clockworkmod)
-rom is packed in zip format ( flashing via recovery)
-each time you change roms, you have to flash boot img of that particular rom,
( to be found inside that rom.zip)
from recovery must reboot to bootloader (adb reboot bootloader)
then flash boot.img...
If it says ok you may now begin booting in to system
Click to expand...
Click to collapse
im basically working around the S-On / kernel & partition issue i take it?
Im gonna try all this now - reason i wanted to flash stock
Why do you want to install stock?
Click to expand...
Click to collapse
is so that i can apply the earlier exploits to gain S-Off - but ill try the steps above and see.
fwiw - at this point im only downloading roms specifically for my phone - its my 1st so im going with stable ones, cyanogen for now. Once I have a better grip ill explore after that
btw:
A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.
Click to expand...
Click to collapse
I was trying to figure out if the OS / roms / RUU had to be tied to boot images - as it appears they do, and whether there was a specific sequence to installing them). Since u clarified the RUU's are all-in-ones i guess the installer takes care of that, where as the others have pointed out - flashing custom roms require the boot.img to be flashed AFTER installing the rom - not the best question i admit!!
If your bootloader is damaged, your device is 100% bricked.
Click to expand...
Click to collapse
So if i can access fastboot etc then i can assume mine is fine right?
Thanks again guys - if there was a ribbon bar instead of just thanks id hit all of u a few times - im SURE many noobs will find all this info really really helpful. Its hard to tie the parts together and get an idea of how they all fit - its really puzzling.. and I know u gotta break something before u really understand it - but its nice to avoid this if possible!
Ill keep u posted on progress/results
no luck .... yet
got it working guys - had to flash boot img BEFORE rom, not after.
cyanogen mod 10.1 running on Desire s.
2 days of pain over
fstarockr said:
so by following these directions:
im basically working around the S-On / kernel & partition issue i take it?
Click to expand...
Click to collapse
Exactly.
Im gonna try all this now - reason i wanted to flash stock
is so that i can apply the earlier exploits to gain S-Off - but ill try the steps above and see.
Click to expand...
Click to collapse
That's a valid reason, but in that case you don't need to flash a custom rom first. You just need to use misc_version to lower your mainversion (a fastboot variable) and then you must flash an old (exploitable) RUU. There are numerous guides on how to do this.
I was trying to figure out if the OS / roms / RUU had to be tied to boot images - as it appears they do, and whether there was a specific sequence to installing them). Since u clarified the RUU's are all-in-ones i guess the installer takes care of that, where as the others have pointed out - flashing custom roms require the boot.img to be flashed AFTER installing the rom
Click to expand...
Click to collapse
Correct, but only if you're S-ON and htcdev unlocked. If you're S-OFF the recovery has no problem writing the boot image by itself.
So if i can access fastboot etc then i can assume mine is fine right?
Click to expand...
Click to collapse
Hell, the mere fact that you can turn on your device means your bootloader is fine
got it working guys - had to flash boot img BEFORE rom, not after.
Click to expand...
Click to collapse
No you don't? The order doesn't matter, as long as you've flashed both.
Related
I unlocked my MT4GS's bootloader a few months ago using HTC's tool, but I now find myself in a place where I need to reflash a stock ROM due to miscellaneous malfunctions. It's not for warranty/damage, I tried to restore my ROM to factory settings and couldn't due to removing the Sense UI for ADWLauncher. I tried to reflash my ClockWorkMod stock ROM backup, but it had a MD5 mismatch (and, sadly, was deleted accidently last night in organizing my SD card).
I am on an unlocked bootloader with S-ON RL showing on the boot screen. I have tried downloading one of the SG59IMG.zip files (both the latest 1.63 release, and the 1.55 release), but those do not work. I place them on my SD Card's root and allow HBOOT to find them, but it reports "Wrong ZIP!". I've read that re-locking my bootloader will fix this; any confirmation?
At this point, what I really want to do is get my phone back on a stock ROM, with or without ClockWorkMod, and start over again with the rooting process. As I said, this isn't for warranty service; I want to make sure I have a good stock recovery image available and that I have a solidly working phone while I wait for an ICS ROM that's stable for everyday use to come around.
Thanks in advance for any help.
WinterHalliwell said:
I unlocked my MT4GS's bootloader a few months ago using HTC's tool, but I now find myself in a place where I need to reflash a stock ROM due to miscellaneous malfunctions. It's not for warranty/damage, I tried to restore my ROM to factory settings and couldn't due to removing the Sense UI for ADWLauncher. I tried to reflash my ClockWorkMod stock ROM backup, but it had a MD5 mismatch (and, sadly, was deleted accidently last night in organizing my SD card).
I am on an unlocked bootloader with S-ON RL showing on the boot screen. I have tried downloading one of the SG59IMG.zip files (both the latest 1.63 release, and the 1.55 release), but those do not work. I place them on my SD Card's root and allow HBOOT to find them, but it reports "Wrong ZIP!". I've read that re-locking my bootloader will fix this; any confirmation?
At this point, what I really want to do is get my phone back on a stock ROM, with or without ClockWorkMod, and start over again with the rooting process. As I said, this isn't for warranty service; I want to make sure I have a good stock recovery image available and that I have a solidly working phone while I wait for an ICS ROM that's stable for everyday use to come around.
Thanks in advance for any help.
Click to expand...
Click to collapse
Get the stock recovery from the devs section, Change " SG59IMG.zip" to " PG59IMG.zip", relock the bootloader so that hboot will see the zip. I think the lock command is "fastboot oem lock". To unlock it again you would have to flash the unlock token again
Sent from my DoubleShot Lite using Tapatalk
ac3theone said:
Get the stock recovery from the devs section, Change " SG59IMG.zip" to " PG59IMG.zip", relock the bootloader so that hboot will see the zip. I think the lock command is "fastboot oem lock". To unlock it again you would have to flash the unlock token again
Sent from my DoubleShot Lite using Tapatalk
Click to expand...
Click to collapse
Whoops, it is PG59IMG already, just at work and wasn't in front of my phone at the time to confirm the file name. Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.
WinterHalliwell said:
Whoops, it is PG59IMG already, just at work and wasn't in front of my phone at the time to confirm the file name. Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.
Click to expand...
Click to collapse
Theres no other way that i know of sry
Sent from my DoubleShot Lite using Tapatalk
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
That covers everything.
WinterHalliwell said:
... Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.
Click to expand...
Click to collapse
Ask and ye shall receive - I put together a package with the bare minimum you need to use ADB or fastboot. At about 736kb I think it's exactly what you were looking for.
(windows machine)
You don't need to install the entire SDK just to get the ADB or fastboot tools - all you need is what's here.
doubleshot_adb-fastboot.zip
Download Link
MD5: 47e72c0a2e2c1caaabd95b5df83e8913
Size: 736.03 KB
I also included a command prompt .bat file (Command.bat) so that when you unzip the archive to a folder, open that folder and double-click the Command.bat file and it will open you up to a command prompt already in the folder with the tools, wherever it is.
No more typing in some annoying CD command to get to the directory with the tools - simply open the folder (wherever it is at the time) and run Command.bat.
You will be ready to just dive right into ADB or fastboot commands (which is all you want, anyway, right?)
You will need the fastboot drivers for the doubleshot installed if they are not - get them here:
HTCDriver.exe
Download Link
MD5: 7fe1a01a816722718c6d369a3dc49166
Size: 13.08 MB
...and these are the same drivers that originally came on the SDcard of the doubleshot when you first got it. If you lost them, you can grab them again.
Enjoy!
Hello.
I'm coming from HD2 and Sensation recently and wanted to get a custom rom for my new One S. I'm inexperienced with this model.
I followed the unlock / cwm / root procedure in the excellent guide sticky. Everything went very well and I tried Jellybam. Got the boot anim but no full boot. I forgot to back up the stock rom so there I was with no working rom and no way to copy a new one onto the sdcard partition.
After some research I've been able to push new rom files to the sdcard partition through adb but I can't seem to get anything to boot on this thing.
I also tried relocking but I cant find which RUU to match my CID (HTC__Y13), I tried all the EU RUU's but they all give me the signature error upon flashing.
So I'm not bricked, I can still install different recoveries and use fastboot. It's just that nothing boots. What am I missing out on here? Oh, and QuickADB tells me that I am not rooted and busybox is missing although I've ran SuperSU CWM.
Any thoughts?
QuickADBPusher is unable to acquire root because you are on stock rom/kernel. The Q&A section tells you that
Have to fastboot flashed boot.img? Its required for hboot above.... urm.. Dunno, but 1.14 needs it anyway.
Goatshocker said:
QuickADBPusher is unable to acquire root because you are on stock rom/kernel. The Q&A section tells you that
Have to fastboot flashed boot.img? Its required for hboot above.... urm.. Dunno, but 1.14 needs it anyway.
Click to expand...
Click to collapse
I now tried to follow the instructions for flashing custom rom on HBOOT > 1.09. So I extracted the boot.img from my desired ROM package. Then I went for another adb push of the rom file (I had done a clear memory in the meantime) and now I'm getting protocol error all over the place.
I miss my HD2. I even miss my Pyramid now...
EDIT: The boot.img flashed fine though.
Wait wait! It worked!
Finally got MIUI (my secret lover) pushed and boot.img extracted and flashed.... and voila!!
Goatshocker! Major respect and bigups for your little advice for the n00bs but first and foremost for all the work you do for our community. You rock man.
Oh thanks. I dont think I do that much though but I try to help where I can
Goatshocker said:
Oh thanks. I dont think I do that much though but I try to help where I can
Click to expand...
Click to collapse
It's always those little things that pass us by.
Hope this thread can help other EU users though. Many of the posts on One S kind of imply that your'e on a low hboot. (Other markets, branded and so forth) But the phones we get these days up here are unbranded 2.15 by stock and you'd always have to manually flash boot as I understand.
Hopefully theres enough food in here for the search engines so that others might find it. Ah. A great day after all.
I attempted to install clockworkrecoverymod on my HTC Desire S but I hadn't realized that it was s-on. I tried first though ROM Manager which didn't work, it just kept loading htc's recovery. Then I tried from another source, this time when I tried to access recovery it just came up saying htc and froze there. I then tried a factory reset it showed htc and froze again. Now every time I try to access recovery it just shows htc and freezes.
Can someone help?
Flash the recovery in fastboot:
fastboot flash recovery recovery.img
teadrinker said:
Flash the recovery in fastboot:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Sorry. I think I gave you the impression that I know what I'm doing I'm a noob so I have no idea where to start with that. Where do I find the recovery.img, is it a download, is it somewhere on the phone. Also, how do I then flash the recovery. Please, it would really help. I don't want to risk winging it only to have my phone explode on me (knowing my luck).
You could've used FlashIMG app to flash things like recovery or a kernel right away from the device itself, no need to use command prompt
Fatal1ty_18_RUS said:
You could've used FlashIMG app to flash things like recovery or a kernel right away from the device itself, no need to use command prompt
Click to expand...
Click to collapse
Not quite sure how this helps. I used ROM Manager to flash my phone from the device without using commands.
Q1uasa said:
Not quite sure how this helps. I used ROM Manager to flash my phone from the device without using commands.
Click to expand...
Click to collapse
That doesn't work when you're s-on.
teadrinker said:
That doesn't work when you're s-on.
Click to expand...
Click to collapse
Yes. I know that now. That's why I'm here I'm looking for some way to recover... the recovery... or install the recovery again or completely reinstall everything on the phone, ANYTHING! The recovery is gone completely and now whenever I turn off my phone the next turn on is a complete restart of the phone. I've tried reinstalling the ICS ruu that I used before but it keeps on failing part way through.
Are you htcdev unlocked?
Re: Crashes for reason I don't understand
Well mate....
I presume your device has been htc dev unlocked and still s- on,
if the bootloader was still locked, you wouldnt have problems with flashing ruu...
so lets start:
1.download the rom of your choice
-copy boot.img from its contents
and place it in a folder with ADB
-place the rom.zip on your phone`s sd card-
1a.download recovery for saga ( clockworkmod or 4ext )
-make sure it has the .img extention
-rename it to: recovery.img , and place it in a folder with ADB
2.start adb on pc and navigate to the location where it is stored,
let say you`ve put it on a drive c, in folder: android-tools,
issue command:
cd c:\android-tools [enter]- ( the folder name after back slash, must correspond with one on your pc- of course)
3.reboot your phone to bootloader and connect to pc,
issue command:
fastboot devices [enter]
if the phone is been recognised, you`ll see something like:
list od devices attached
scf00421.... device
4.issue command:
fastboot flash recovery recovery.img
and see what`s the output in terminal-
5.in bootloader menu there is an option: reboot bootloader...
- use it- reboot bootloader, and from among its option choose
< recovery > ....
In recovery:
- install zip from sd card
-choose zip from sd card
find the rom you`ve downloaded and placed on sd card before,
confirm by clicking < yes > and let it finish flashing
6.in command prompt, issue command:
adb reboot bootloader [enter]
7.issue command:
fastboot devices
and when your device`s ID is listed under < list of device attached >
8.issue command:
fastboot flash boot boot.img [enter]
and when it finishes, issue command:
fastboot reboot
and if all above has been fulfilled to the letter,
after htc boot screen you should see bootanimation of your new rom,
and all else that ussualy follows
for the first time i`d recommend a sense rom,
since flashing non sense one, requires to know whether your device
goes equipped with sony or hitachi panel- no tragedy in either case,
but knowing that saves you from another bootloop.....
Thanks asgardr I'm yet to try this out but it looks promising. The reason this all started was because I wanted to install a certain rom found here http://forum.xda-developers.com/showthread.php?t=2070704
There are two versions of it. Not sure if they both have sense or not but one of them is called 'Sense/Data++ version' so I'm assuming that one will definatly have sense on it. I'll try to install it. I'll let you know how it goes.
Q1uasa said:
Thanks asgardr I'm yet to try this out but it looks promising. The reason this all started was because I wanted to install a certain rom found here http://forum.xda-developers.com/showthread.php?t=2070704
There are two versions of it. Not sure if they both have sense or not but one of them is called 'Sense/Data++ version' so I'm assuming that one will definatly have sense on it. I'll try to install it.
Click to expand...
Click to collapse
This is a rom for htc desire,,, not for htc desire s,,
difference in name is small but you should never flash anything else than roms for desire s!
If you try flasing rom from different device, you're running very high risk of bricking your device...
If you tried to flash that rom already and the phone is still able to boot to bootloader:
1.download any sense rom for DESIRE S- SAGA
copy boot img from that rom to a folder where adb is
2.put it on your phone's sd card
3.in recovery:
-wipe cache
-data
-system
( clockworkmod recovery)
-wipe all except sd card
( 4ext recovery )
4.flash rom you've placed on an sd card ( in recovery )
5. From recovery : reboot to bootloader and
flash boot img via fastboot....
Then you can reboot your device...
ummm. I followed your instuctions using this rom http://forum.xda-developers.com/showthread.php?t=1859700 and now when the phone starts it stays blank
Never mind. I was just being inept again. The problem was that with my version of Hboot I would need to edit the updater-script of the ROM for it to install properly.
Now my only issue is that when the phone boots I get the htc ring menu.... whatever it's called and when I pull the ring up it says com.htc.bg has stopped working and then I get a screen that just says htc
Never mind. I was just being inept again. The problem was that with my version of Hboot I would need to edit the updater-script of the ROM for it to install properly.
Now my only issue is that when the phone boots I get the htc ring menu.... whatever it's called and when I pull the ring up it says com.htc.bg has stopped working and then I get a screen that just says htc
Click to expand...
Click to collapse
You mean: htc lockscreen?
I haven't got any expearience with that particular rom,
but why don't you try some other one, like:
- viper saga
- desireXS
- SVHD
- iceDS
These are sense based roms,
there is a kernel thread from a briliant dev,
where you can find alternative boot images
for sense based roms
http://forum.xda-developers.com/showthread.php?t=1845039
Always remember of a < full wipe > before rom flashing,
and flashing boot img after,
even if flashing kernel provided by amidabuddha ( from the link provided above )
Most of the errors and bootloops is happening, due to the wrong or incorrectly flashed boot img...
( except those native to the rom itself- bugs )
asgardr said:
You mean: htc lockscreen?
I haven't got any expearience with that particular rom,
but why don't you try some other one, like:
- viper saga
- desireXS
- SVHD
- iceDS
These are sense based roms,
there is a kernel thread from a briliant dev,
where you can find alternative boot images
for sense based roms
http://forum.xda-developers.com/showthread.php?t=1845039
Always remember of a < full wipe > before rom flashing,
and flashing boot img after,
even if flashing kernel provided by amidabuddha ( from the link provided above )
Most of the errors and bootloops is happening, due to the wrong or incorrectly flashed boot img...
( except those native to the rom itself- bugs )
Click to expand...
Click to collapse
Thank you for all the infomation you're giving me I'm going to try the viper saga ROM. Are the alternative boot images necessary? I don't really understand much about kernels.
Q1uasa said:
Thank you for all the infomation you're giving me I'm going to try the viper saga ROM. Are the alternative boot images necessary? I don't really understand much about kernels.
Click to expand...
Click to collapse
Wiper saga rom is been driven by BtB kernel from amidabuddha,
this is basic, almost stock but cleaned and little improved branch,
meaning no overclocking or undervolting of cpu is possible with it...
If yoi'd wish to oc or uw your central processing unit ( processor ),
tweaked or patched kernels must be aplied instead
Sorted!!!
asgardr said:
Wiper saga rom is been driven by BtB kernel from amidabuddha,
this is basic, almost stock but cleaned and little improved branch,
meaning no overclocking or undervolting of cpu is possible with it...
If yoi'd wish to oc or uw your central processing unit ( processor ),
tweaked or patched kernels must be aplied instead
Click to expand...
Click to collapse
My phone.... it works again! Thank you so much asgardr! Thanks to you I have a fully functional phone again :highfive:
I didn't bother with the alternative kernel. I don't really have an interest in overclocking or undervolting but thank you for the extra info.
It is not so scary after all
Would you please, mark this thread as: ( solved )
asgardr said:
It is not so scary after all
Would you please, mark this thread as: ( solved )
Click to expand...
Click to collapse
Sure thing Thanks again.
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Hkyx said:
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Click to expand...
Click to collapse
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
astar26 said:
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
Click to expand...
Click to collapse
Hi,
It's not possible to use 4ext, because the phone doesn't boot. he's stop at the boot loader.
I've try with adb for mac but I think I don't do the good command to flash by adb the kernel
ADB does not work, you have to use fastboot! Just follow the instructions by astar26. Connect your phone to your PC/mac and type "fastboot reboot-bootloader" and then "fastboot flash boot boot.img"
Regards
Gesendet von meinem HTC Sensation mit Tapatalk 4
astar26 said:
You need HTC driver for the phone to work on windows.
Anyway, the problem is that since you're S-On, you need to flash the kernel manually. You place it in the same directory as adb and fastboot (I don't know if you have it on mac, I guess that yes, or else use windows), and when booted to fastboot (on the bootloader), type the following command:
fastboot flash boot boot.img
Where boot.img is the name of the kernel of the ROM (it's inside the .zip of the ROM).
Alternatively, if you have 4EXT recovery (and if you don't, I suggest you get it), enable smartflash, and then you will be able to flash ROMs regularily.
Good luck.
Click to expand...
Click to collapse
Hi, I'm trying to flash a Cyanogenmod ROM for a friend on his HTC Sensation Z710e (rooted, bootloader unlocked) - my own phone is an Xperia Ray so I'm not too familiar with the process. Do I need to flash the Kernel before I flash the ROM? What's the best way to do it? If it's a matter of following the process you outlined above then I'm afraid I can't really follow it - I really need an idiot-proof 'how-to' guide I'm afraid, like I said, I'm a total noob when it comes to the HTC Sensation.
Hope you can help.
seamo123 said:
Hi, I'm trying to flash a Cyanogenmod ROM for a friend on his HTC Sensation Z710e (rooted, bootloader unlocked) - my own phone is am Xperia Ray so I'm not too familiar with the process. Do I need to flash the Kernel before I flash the ROM? What's the best way to do it? If it's a matter of following the process you outlined above then I'm afraid I can't really follow it - I really need an idiot-proof 'how-to' guide I'm afraid, like I said, I'm a total noob when it comes to the HTC Sensation.
Hope you can help.
Click to expand...
Click to collapse
Usually the ROM is flashed before the kernel, this is what I did
Babyhustle said:
Usually the ROM is flashed before the kernel, this is what I did
Click to expand...
Click to collapse
I have no idea how to flash a kernel on the HTC - that's my main problem
seamo123 said:
I have no idea how to flash a kernel on the HTC - that's my main problem
Click to expand...
Click to collapse
astar26 explained how it works. If the sensation of your friend has 4ext recovery use smartflash, if twrp use htc dumlock then you don't need to flash the kernel seperately.
Hkyx said:
Hi there,
Sorry for my bad english. I've looked for a answer but I don't understand all of solution :/
I'm on a mac and I have a Sensation Xe (Europe) S-On.
When I've change MIUI to Cyanogenmod. My mobil phone change the rom and bug with the kernel O_O ?
Now I got the bad Kernel for the room :S and the phone doesn't boot (stop at bootscreen).
I got the same problem if I try to install a new room by the boot loader.
At this time I want to back on the factory room and Kernel for my facility.
But the .exe of RUU doesn't work on mac (of course). And when I try on a windows; I connect the phone to the computer with boot tools but it's not work.
Sorry, I think it's not the first time someone ask this question but too much result to find the good way to do that
Click to expand...
Click to collapse
To flash a ROM on the Sensation:
Go to recovery
(Wipe. Then) flash the .zip of the ROM
That's it. There is, however, a catch for S-ON devices. HTC hasn't allowed flashing of /boot from recovery. This means that, for S-ON devices, the kernel cannot be flashed.
The best way around this is to use 4ext recovery. It has a option called Smartflash. That will flash your kernel even if you're S-ON.
(Some roms, like ViperS 3.1.x require an additional kernel flasher as SmartFlash doesn't work there).
The other way is to manually flash the boot image (kernel). Go to fastboot USB (this is NOT ADB), and execute:
Code:
fastboot flash boot boot.img
The boot.img is your new boot image.
Thanks for the reply!
We've already tried flashing the ROM as normal [using ROM Manager] but it doesn't work.
1. How do I know the device is 'S-on?' or not? Can it be changed? What's 'S-on' anyway?
2. Do you have a link handy for that recovery system you mentioned that allows flashing of kernels?
3. I haven't a clue how to manually flash the boot image - with my Xperia Ray I just use the Sony flash tool and fastboot. Can you give me an idiot's guide to doing this?
Far_SighT said:
To flash a ROM on the Sensation:
Go to recovery
(Wipe. Then) flash the .zip of the ROM
That's it. There is, however, a catch for S-ON devices. HTC hasn't allowed flashing of /boot from recovery. This means that, for S-ON devices, the kernel cannot be flashed.
The best way around this is to use 4ext recovery. It has a option called Smartflash. That will flash your kernel even if you're S-ON.
(Some roms, like ViperS 3.1.x require an additional kernel flasher as SmartFlash doesn't work there).
The other way is to manually flash the boot image (kernel). Go to fastboot USB (this is NOT ADB), and execute:
Code:
fastboot flash boot boot.img
The boot.img is your new boot image.
Click to expand...
Click to collapse
seamo123 said:
Thanks for the reply!
We've already tried flashing the ROM as normal [using ROM Manager] but it doesn't work.
1. How do I know the device is 'S-on?' or not? Can it be changed? What's 'S-on' anyway?
2. Do you have a link handy for that recovery system you mentioned that allows flashing of kernels?
3. I haven't a clue how to manually flash the boot image - with my Xperia Ray I just use the Sony flash tool and fastboot. Can you give me an idiot's guide to doing this?
Click to expand...
Click to collapse
Ah, I see:
Power off and pull out the battery. Press Power + Vol down. Once the bootloader screen comes up it'll either say S-ON or S-OFF.
For flashing ROMs S-ON use this (also includes 4ext recovery). Read about S-ON here.
Just use smartflash (see link in 1). For the special cases I mentioned in previous post (no smartflash), just see the ROM's thread for S-ON flashing.
Note that if you want just want to flash ROMs the above method is good. For S-OFF, either use this, in case you followed above steps, or use this, in case you want to S-OFF first. S-OFF is not needed for flashing ROMs.
htc sensation z710e wifi problem
Hello friends!
Two months I have a problem with my HTC SENSATION! The problem is due to wifi,I read many forums about this problem, I tried many solutions, but without success! I assumed that the problem is due to "wifi country code". I tried this solution "WiFix Manager", but did not help.
I tried this option http://forum.xda-developers.com/showthread.php?t=1469428,
because my phone is unlocked with HTCdev, back to factory rom 2.3.3 hboot 1.17.11 to be able to achieve S-OFF method revolutionary s-off.
I did everything, but after a while the problem still occurs. The only way to fix it is by re-install the Rom again.Most often breaks when I restart phone while is connected to the wifi network,when my phone starts, this wifi error appears.I can not write scripts or fix them, so I can not do this option: http://forum.xda-developers.com/showthread.php?t=2368501 . My phone is from England, Orange UK is the operator of which is purchased,I do not know if there is any difference!? And now my phone is rooted, revolutionary s-off, got super CID, 4ext recovery....
What else do I need to have no more this wifi problem?
I'm not very good at Development or haking, so if someone can explain to me what to do to solve my problem, I would appreciate it!
I just want to install "Revelation 1.0.3" and only use it! I am from Bulgaria by the way.
VS23BG said:
Hello friends!
Two months I have a problem with my HTC SENSATION! The problem is due to wifi,I read many forums about this problem, I tried many solutions, but without success! I assumed that the problem is due to "wifi country code". I tried this solution "WiFix Manager", but did not help.
I tried this option http://forum.xda-developers.com/showthread.php?t=1469428,
because my phone is unlocked with HTCdev, back to factory rom 2.3.3 hboot 1.17.11 to be able to achieve S-OFF method revolutionary s-off.
I did everything, but after a while the problem still occurs. The only way to fix it is by re-install the Rom again.Most often breaks when I restart phone while is connected to the wifi network,when my phone starts, this wifi error appears.I can not write scripts or fix them, so I can not do this option: http://forum.xda-developers.com/showthread.php?t=2368501 . My phone is from England, Orange UK is the operator of which is purchased,I do not know if there is any difference!? And now my phone is rooted, revolutionary s-off, got super CID, 4ext recovery....
What else do I need to have no more this wifi problem?
I'm not very good at Development or haking, so if someone can explain to me what to do to solve my problem, I would appreciate it!
I just want to install "Revelation 1.0.3" and only use it! I am from Bulgaria by the way.
Click to expand...
Click to collapse
flash the boot.img of your current rom and see if wifi works
rzr86 said:
flash the boot.img of your current rom and see if wifi works
Click to expand...
Click to collapse
And I tried, I installed program KGS Utility,did not help! I tried with the "ADB" command to flash the boot.img, just flashed it, but it did not help!
And now, whenever my wifi give me error, I installed a new Rom! So I solved the problem, but this solution is temporary. The problem manifests itself sooner or later. End i chenge Rom again, there is a good side, will test all Roms which is on this site!
Thank you for your attention!
VS23BG said:
And I tried, I installed program KGS Utility,did not help! I tried with the "ADB" command to flash the boot.img, just flashed it, but it did not help!
And now, whenever my wifi give me error, I installed a new Rom! So I solved the problem, but this solution is temporary. The problem manifests itself sooner or later. End i chenge Rom again, there is a good side, will test all Roms which is on this site!
Thank you for your attention!
Click to expand...
Click to collapse
May be a firmware problem. Do a Ruu and see what happens.
Happy to help.
Far_SighT said:
May be a firmware problem. Do a Ruu and see what happens.
Happy to help.
Click to expand...
Click to collapse
RUU? Recommend me to back factory Rom using Ruu.exe? Already done it! Return factory Rom 2.3.3 HBOOT 1.17.11,to achieve revolutionary s-off. :good:
VS23BG said:
RUU? Recommend me to back factory Rom using Ruu.exe? Already done it! Return factory Rom 2.3.3 HBOOT 1.17.11,to achieve revolutionary s-off. :good:
Click to expand...
Click to collapse
lift up gently the antenna which is responsible for wifi in the back cover
I think I finally found the solution to the wifi problem!
The solution is in this post:
http://forum.xda-developers.com/showpost.php?p=23554125&postcount=1804
Now I use Android Revolution HD 7.3,sometimes the problem occurs again, but now I have a solution!
Just repeat the procedure described in the post and wifi working again.
When you delete a file "wpa_supplicant.conf", I have to re-enter all the router's password which I linked, but this is not such a big problem!
Hi,
I'm having problems with my HTC one SV. it powers on then it will show "htc quietly brilliance logo" and after that it shows black screen then stuck on it. i had this problem before so I remove the battery then power it on solves the problem but lately it does not work anymore lets say it's like 1/100 before it goes thourgh. i really dont know what to do tried searching for solutions just cant get it. I'm kinda newbie on terms so if anyone can help me I'm very thankful.
Thank you in Advance!
Seems like a common problem for many HTC One SV's.
Take a look in the Q&A section, there should be many threads, where i described what to do. As long as it's no US carrier phone, then things are different.
Basically:
- unlock your phone with htcdev.com (all data is lost)
- flash TWRP recovery with fastboot
- flash a rom for your model
old.splatterhand said:
Seems like a common problem for many HTC One SV's.
Take a look in the Q&A section, there should be many threads, where i described what to do. As long as it's no US carrier phone, then things are different.
Basically:
- unlock your phone with htcdev.com (all data is lost)
- flash TWRP recovery with fastboot
- flash a rom for your model
Click to expand...
Click to collapse
my phone is from middle east. i assume that its all in htcdev.com? like step by step on what to do? honestly i really don't know how to flash TWRP, flash a rom and etc. I'm just having a hard time learning maybe because it's 1st time for to do it plus I'm not yet familiar with it.
You needto learn, how to use fastboot cmd, otherwise i guess your phone is lost.
But its not so hard, if you can use a computer
At htcdev you can get the basic fastboot files you need.
Try to read and follow the unlock guide, then we see how far we come.
old.splatterhand said:
You needto learn, how to use fastboot cmd, otherwise i guess your phone is lost.
But its not so hard, if you can use a computer
At htcdev you can get the basic fastboot files you need.
Try to read and follow the unlock guide, then we see how far we come.
Click to expand...
Click to collapse
Hi,
im having hard time. tried to follow the steps on htcdev but im having error. here is the message.
"the program can't start because adbwinapi.dll is missing from your computer. Try reinstalling the program to fix the problem.
any idea on how fix this?
phuge17 said:
adbwinapi.dll is missing
any idea on how fix this?
Click to expand...
Click to collapse
This dll should be in the package that you have downloaded from htcdev.
old.splatterhand said:
This dll should be in the package that you have downloaded from htcdev.
Click to expand...
Click to collapse
Hi,
I managed to unlock my phone , TWRP and all that. i also downloaded your "[ROM]Stock odexed Android 4.2.2 Sense 5 " for k2_ul. i followed your instruction on how to install by the way mine is S-on so flash with fastboot (fastboot flash boot boot.img) am I correct? i see some okay it was kinda fast so i feel weird i thought the installing will take a minute or so because its almost 1gig file download. anyway the only thing i did not do is this part "Don't forget to flash Superuser file (look into my index thread) if you want root!" actually i really dont know what you mean by that sorry. my phone still not yet booting still stuck at blackscreen.
UPDATE** phone is just restarting over over again from htc quietly brilliant >> power off >> htc quietly brilliant >> power off.
phuge17 said:
Hi,
I managed to unlock my phone , TWRP and all that. i also downloaded your "[ROM]Stock odexed Android 4.2.2 Sense 5 " for k2_ul. i followed your instruction on how to install by the way mine is S-on so flash with fastboot (fastboot flash boot boot.img) am I correct? i see some okay it was kinda fast so i feel weird i thought the installing will take a minute or so because its almost 1gig file download. anyway the only thing i did not do is this part "Don't forget to flash Superuser file (look into my index thread) if you want root!" actually i really dont know what you mean by that sorry. my phone still not yet booting still stuck at blackscreen.
UPDATE** phone is just restarting over over again from htc quietly brilliant >> power off >> htc quietly brilliant >> power off.
Click to expand...
Click to collapse
Why install an odex 4.2.2 Rom when your 4.2.2 Rom is odex by stock?
phuge17 said:
Hi,
I managed to unlock my phone , TWRP and all that. i also downloaded your "[ROM]Stock odexed Android 4.2.2 Sense 5 " for k2_ul. i followed your instruction on how to install by the way mine is S-on so flash with fastboot (fastboot flash boot boot.img) am I correct? i see some okay it was kinda fast so i feel weird i thought the installing will take a minute or so because its almost 1gig file download. anyway the only thing i did not do is this part "Don't forget to flash Superuser file (look into my index thread) if you want root!" actually i really dont know what you mean by that sorry. my phone still not yet booting still stuck at blackscreen.
UPDATE** phone is just restarting over over again from htc quietly brilliant >> power off >> htc quietly brilliant >> power off.
Click to expand...
Click to collapse
Have you done a wipe in recovery before flashing the new rom?
SHM said:
Why install an odex 4.2.2 Rom when your 4.2.2 Rom is odex by stock?
Click to expand...
Click to collapse
Usually it it is.
old.splatterhand said:
Have you done a wipe in recovery before flashing the new rom?
Usually it it is.
Click to expand...
Click to collapse
sorry it took me weeks before i reply. anyway i did wipe the phone. are there any like reset command while on fast boot or something so that i can start from the beginning? actually im a bit lost.
Boot to recovery -> Wipe menu -> Advanced Wipe and wipe System, data, cache, dalvik cache.
Then go to Install and flash the rom for your model.
Then boot to fastboot and flash the boot.img of the rom with fastboot cmd fastboot flash boot boot.img
If that does not bring your phone back to life, something else is wrong.