Delete
Normally you would be able to root the phone after downgrading to 0.80/1.21 from fastboot using this method:
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/
It seems this fails though. If it can be made to work then the misc partition could be fixed, allowing the RUU update.
I'm not really a dev, in fact i only got my first android phone on saturday, but i'll add the info i discovered today.
Phone is an SLCD on non-rooted OTA official froyo (0.92 hboot). Like the OP points out, I needed to enable usb debugging on a 0.83 or lower hboot so that i could install a rooted recovery image. To enable usb debug you need a working screen, so that limits it to 0.83 hboot.
First i tried the 1.21.405.2_T2 RRU installer on my 0.92 hboot. It's installer window showed i had 2.09.405, and then trying to proceed into the bootloader resulted in the patch failing just after the signature check.
Next up i installed the recent 0.80 hboot rom that's been signed as 2.09.405 to enable downgrading. Killed my screen naturally. The earlier windows 1.21.405.2_T2 RRU gave a different result against it, equal version numbers of 1.21.405, but the bootloader still cried foul just after comparing signatures.
I was curious, so i broke out adb and fastboot, and snatched the rom.zip from the RUU installer, then used fastboot to reboot the phone into RUU mode. Manually flashing the rom.zip showed the signature passed fine, but there was an error 43 on the main version check. I did a getvar all on my phone and there it was, version-main=2.09.405.
So i rebooted the phone and loaded the windows RRU installer to get a response to 'adb devices' from my blank-screened phone, and had a look in the shell using adb. I haven't used linux in years but a little googling caught me up to speed that the 'vars all' values i'd seen are stored in the misc partition of the memory found at /proc/mtd, and misc itself can be altered through /dev/mtd/mtd0 (if my shell had root privileges, that is, bugger).
So i got a little out of my depth, but before i quit, i tried flashing the 0.80 engineering rom in that modaco thread using fastboot via the pc (r6-desire-root-alt.zip), and no joy with that either.
The short of it is the misc nand partition's version-main value is blocking any HTC signed sub-2.09.405 rom install progressing beyond the main version check in the bootloader/recovery. So far as i can tell it's comparing the misc partition value to android-info.txt within the zip?
So the 4 possible solutions i can think of would be either a mysterious signed-as-2.09.405 version of a 0.83hboot rom just like the 0.80 one, or a method of messing with the misc partition via an exploit, or thirdly enabling usb debug mode in a way other than using the phone menu, or lastly finding a way to install a rooted recovery rom directly on a 0.92 hboot.
Sorry that's a little long, feel free to move this post out of the thread.
P.S. forgot to mention i flashed back to the official OTA froyo as an upgrade.zip when i was done.
Yeah, that sums up the situation. The r6 rooting method is blocked for the same reason as the RUU uploads, the wrong value in the misc partition.
It may somehow be possible to boot the phone from fastboot in a way that enables usb debugging, but I don't think it is. Alternatively it may be possible to install unrevoked3 after downgrading while in stock recovery mode, but that's unlikely (I can't try that, I have custom recovery).
Hopefully at some point 0.92/froyo will be rootable by unrevoked, which seems the most likely way of sorting this out.
Does the phone even boot up if you "brick" the screen..? if so you can use the trackpad to navigate the menus, kind a hard, but it possible.
Make sure you have disabled checking for SIM pin code. (possible to enter with trackpad, but extremely hard)
boot - wait - wait(wait long enough for sense and and usb menu do disappear but not the screen lock) - menu - down - left - down - down - trackpad - 10x down - trackpad - 3x down (bottom) - 2x trackpad
I was thinking about that NChief, maybe someone can test. But surely the downgrade re flashes the rom so it will be on the first run setup thing? need the steps to get through that?
teppic74 said:
Normally you would be able to root the phone after downgrading to 0.80/1.21 from fastboot using this method:
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/
It seems this fails though. If it can be made to work then the misc partition could be fixed, allowing the RUU update.
Click to expand...
Click to collapse
So you're saying step 1 from r6 root doesn't work either?
Mysterious 0.80 downgrade method was achieved by the chinese. Maybe they could do the same for the 0.83 .zip?
I have a great idea, but it needs r6 root to work.
1. Downgrade from 0.92 to 0.80.
2. Use r6 to root the phone (an SLCD version of fake-flash ClockworkMod would be handy).
3. Extract rom.zip from 0.83 RUU.
4. Use fake-flash to get to recovery.
5. Flash rom.zip from step 3.
6. Root using unrEVOked.
r6 won't work as it fails the version check. If it did it would all be very easy.
1. Downgrade to 0.80.
2. Use r6 to root the phone.
3. Apply update.zip misc partition fix in stock recovery.
4. Apply RUU.
Let me flash a stock 1.21.405.2 ROM and write up instructions on how to enable USB debugging.
lollylost100 said:
Let me flash a stock 1.21.405.2 ROM and write up instructions on how to enable USB debugging.
Click to expand...
Click to collapse
As you said though, it will boot you into the setup screens. I think it does that each time you restart until you finish it. Also it will boot up with a locked screen, though I think the menu key will get rid of that in 2.1.
The downgrade method seems to be a leak from a friendly person at HTC, since it's a signed ROM. That's the only way to get by the version check without rooting. Another one which is based on the SLCD-compatible RUU instead would be perfect.
I have an AMOLED screen. I will write up the steps, which will be the same for SLCDs.
I understand, but what I mean is that someone without a screen won't be able to complete the setup screens (unless this is possible using the trackpad too?)
I thought that the screen doesn't display anything, but touchscreen still works. Isn't that the case?
I wouldn't imagine it would work.
AFAIK the touchscreen is kept the same. Only the screen is changed.
layer 1 ____________________ <-- touchscreen
layer 2 ____________________ <-- screen (AMOLED/SLCD)
If the touchscreen is the same then it may be ok, but I don't think anyone with an SLCD phone is going to risk downgrading to test the procedure...
I have managed to do it without the touchscreen.
That should be enough to fix it then.
Now we just need someone on stock froyo and an SLCD screen who wants root again to test it
teppic74 said:
That should be enough to fix it then.
Now we just need someone on stock froyo and an SLCD screen who wants root again to test it
Click to expand...
Click to collapse
It's tempting!
Related
--- Updated and simplified
Updates from HTC are randomly released for countries and regions. These Update may lock your phone. As of today, phones can be unlocked again by using the GOLDCARD approach. However, there is a much simpler way to prevent bad things from happening:
If you like flashing HTC roms and have no intention to lock your phone, follow these steps:
On the PC
1. Double Click the .exe from the update. Wait for the first window to appear (DO NOT CONNECT YOUR PHONE). Don't close the application but do not continue
2. Open explorer and navigate to the hidden directory:
Windows 7: \users\$username$\AppData\Local\Temp\... followed by something like ...\{2A3DF7FC-1693-4C53-8883-6CF09DED700D}\...
Vista: documents and settings\.....
3. You should find the install application files along with a file "Rom.zip" (40 to 90 Megs)
4. Extract the ROM.zip to your SDK Tools directory, where fastboot.exe resides
5. open command shell and navigate to your Tools directory (supposing SDK, adb and fastboot are installed)
On the Phone
6. Enter recovery console on phone (press "home" + then "on")
7. Do a nandroid backup
8. Select Wipe your phone
9. Hold "back" and select "reboot system" in recovery to enter Fastboot mode
On the PC
10. Type: "fastboot flash boot boot.img" .... wait to complete
11. Type: "fastboot flash system system.img" .... wait to complete
12. Type: "fastboot flash userdata userdata.img" .... wait to complete
13. [Optional] Type: "fastboot flash radio radio.img" .... wait to complete (note: some HTC radios locked windows mobile phones. I am not sure whether this applies for Android)
14. Reboot your phone
15. Keep the update if you like it, revert to backup via recovery and nandroid in case you don't
And sorry for any confusion caused...
Regards,
fde
Thanks a lot mate... I will try the official sense for my magic then using this method first =D...
Are you sure....
That this will work? I have made the RUU Flash: RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_Nordic_release_signed_NoDriver
And that resulted in:
HBOOT-1-33-0014
CPLD-12
RADIO-3-22-23-18
I don't understand what you are meaning about the Radio.img file.
And what about the HBOOT file?
Yes it works. Just verfied it aigain. What the RUU package does is:
1. Extract the application to a temp file
2. Use ADB to flash the ROM to your phone
By the approach described in the first post, the application unpacks itself into a temp directory. This allows you to access the ROM-File which is stored as ROM.zip or something similar. By moving only the vital Boot, System and Userdata, you avoid flashing your Recovery console or Bootloader (Hboot).
It implies of course, that you DO NOT continue with the RUU application as soon as the first window becomes visible. (I will adjust the above Tutorial and make it simpler).
Problem
But the problem is that I allready have flashed my phone, is this the way to revert is så I can root it again and put custom roms on it again?
same here
ZeaDK said:
But the problem is that I allready have flashed my phone, is this the way to revert is så I can root it again and put custom roms on it again?
Click to expand...
Click to collapse
I also want to know how I can flash new ROM since people said that my spl is perfected after upgrading
I was learned that we need to use goldcard method to root again.
In our case, any idea which ROM to use as we gotta use higher ROM?
Or are we able to gain root access without touching the existing ROM?
Now even cannot boot to recovery mode.
So stupid to upgrade it although the ROM is stable and fast but no root access sucks.
any help would be appreciated.
thanks,
thihaz
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
feicher said:
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
Click to expand...
Click to collapse
The problem with the goldcard method is that you lose the roms as well...
Sir, would you please let me know how to flashing engineering SPL, right now i have HBoot-1.76.007 which shipped with the Singapore HTC sense rom.
BTW: i don't care i will lose the rom or not.
Many thanks!
I flashed using RUU_Sapphire_HTC_Asia_WWE_2.16.707.3_SG_release_signed_NoDriver.exe with golden card, but got "check main rom verion" error msg.
then flashed using RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe with golden card, same error msg again.
I really have no idea how to flash back to engineering SPL, i'm stuck in Singapore HTC sense rom.
feicher said:
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
Click to expand...
Click to collapse
i got 1 rom.zip(11mb) & another one rom1.zip(89mb).
But both I also can't unzip. Any idea? Thanks.
radonsg said:
i got 1 rom.zip(11mb) & another one rom1.zip(89mb).
But both I also can't unzip. Any idea? Thanks.
Click to expand...
Click to collapse
I did this twice on a Swiss Update, which btw wasn't worth applying. Just by the Size it's rom1.zip.
Let me download the Singapore and see what I can do.... But then looking at the guys post it seems the second file in the post is what you need. Download this package and only flash boot, system and data in fastboot mode. (From Step 4. onward in the guide). Anyway I will have a look.
phygee said:
Sir, would you please let me know how to flashing engineering SPL, right now i have HBoot-1.76.007 which shipped with the Singapore HTC sense rom.
BTW: i don't care i will lose the rom or not.
Many thanks!
I flashed using RUU_Sapphire_HTC_Asia_WWE_2.16.707.3_SG_release_signed_NoDriver.exe with golden card, but got "check main rom verion" error msg.
then flashed using RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe with golden card, same error msg again.
I really have no idea how to flash back to engineering SPL, i'm stuck in Singapore HTC sense rom.
Click to expand...
Click to collapse
Please follow the GOLDCARD method. I am not a recovery expert. I try to be cautious and was lucky until now (so I never tried it myself, but it is reported to work). Sorry for that. If :No-Frost: knows of a better guide with regard to GOLDCARD, please post!
Regards,
fde
feicher said:
Please follow the GOLDCARD method. I am not a recovery expert. I try to be cautious and was lucky until now (so I never tried it myself, but it is reported to work). Sorry for that. If :No-Frost: knows of a better guide with regard to GOLDCARD, please post!
Regards,
fde
Click to expand...
Click to collapse
For now the only method I know is the goldcard one... But in my country, using the goldcard method, makes the magics lose the 3g, edge or any internet mobile connection... =(...
Be careful, by using this method you can not upgrade to Snese UI (example TW). The reason being system image in Sense UI is larger than the previous 1.5 ROM system image, so system partition needs to be re-sized, which the RUU update does it for you. Otherwise you are struck with failed system image flashing.
signiture verifiaction fail
I get a signiture verifiaction fail when trying to write the .img files using fastboot. Any suggestions?
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!
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.
I hope there is still people on this mytouch forum lol? I need help rooting my mytouch 4g slide its on kitkat I looked around how to on kitkat first time tryna root. Also any help out there that can guide me to not brickin it or if other steps need to be takin because of kitkat?
Ive read 20+ pages so far and this is frustrating lol I want same rom just want to be perm rooted to be able to mount to sd card screenshot and use other rooted apps.
SOEBOMB said:
Ive read 20+ pages so far and this is frustrating lol I want same rom just want to be perm rooted to be able to mount to sd card screenshot and use other rooted apps.
Click to expand...
Click to collapse
Did you lose superuser, or did the bootloader relock?
If it's the former, you could try this:
...you could try pushing su to the device with adb (depends on how you lost root):
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
adb push su /system/xbin/
adb shell chmod 06755 /system/xbin/su
... with this file (extracted).
Source (with mount point changed)
Click to expand...
Click to collapse
joel.maxuel said:
Did you lose superuser, or did the bootloader relock?
If it's the former, you could try this:
Click to expand...
Click to collapse
Thanks fpr the reply I never had root nor have I rooted a phone noob here lol ive read also that kitkat needs to be downgraded.that true to root?
SOEBOMB said:
Thanks fpr the reply I never had root nor have I rooted a phone noob here lol ive read also that kitkat needs to be downgraded.that true to root?
Click to expand...
Click to collapse
I don't think it's possible to be able to install a ROM without the bootloader unlocked (prerequisite for CWM, and in turn KitKat ROM). Unless you got the phone with KitKat (eBay special?) but no root (which would be weird for a seller to do), you must have lost root along the way (it can happen).
In either case, we are not talking about the bootloader. The way to check that though, is to turn on the device while holding the Vol-Dn button. This will take you into fastboot. If it says ** RELOCKED ** up top, then you're in trouble. If it says ** UNLOCKED ** or * JuoPunutbear *, it looks like you just need superuser reinstalled, and you don't need to downgrade for that.
To do this, download and install the adb binary and drivers (if you're a linux user, all you need to do is an 'apt-get install adb' or whatever your distro uses). Turn on the device normally, go into Developer under settings (may need to go into About phone first and tap Build Number 7 or 8 times for Developer menu to appear). Turn on USB debugging. Now connect a cable between your device and your PC. Fire up a command prompt on the PC (can be left open after installing ADB, as you want to be in the same folder as it) and type:
Code:
adb devices
If you get a device, and is listed as online, you are ready to enter the commands for the second part, in the order as they appear in my previous post.
If the first command does not work (as I cannot find the appropriate folder on my 10.1 distro), try:
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/mmcblk0p22 /system
Or to see if that folder exists for you first, try:
Code:
adb shell ls /dev/block/platform/msm_sdcc.1/by-name/
If you get a list of partitions, (including system) you should be good to proceed with that command. If not (by-name not found), use the above command. Hope this helps.
Ok looked im on android 2.3.4 and also looked at the boot loader things says locked and I did get it off ebay lmao good call. 1.45.0013 bootloader also
SOEBOMB said:
Ok looked im on android 2.3.4 and also looked at the boot loader things says locked and I did get it off ebay lmao good call. 1.45.0013 bootloader also
Click to expand...
Click to collapse
Okay, so that's Gingerbread, not KitKat.
I used this guide when I did mine (second pin down in the MT4GS Developer forum):
http://forum.xda-developers.com/showthread.php?t=1801106
jjbz said:
Here’s a breakdown of the process:
1. INSTALL HTC DRIVERS ON YOUR PC.
2. INSTALL ADB AND FASTBOOT ON YOUR PC.
3. REGISTER AT HTC DEV.
4. UNLOCK BOOTLOADER THROUGH HTC DEV.
5. INSTALL A CUSTOM RECOVERY.
6. ROOT YOUR DEVICE.
7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).
-PREREQUISITES-
Before getting started, please visit the MT4GS Compendium and read over Section One to learn the XDA Lingo. You really need to know this stuff if you’re going to tinker with the MT4GS.
Also, all information in the guide assumes you are using a Windows PC and a MT4GS with the STOCK ROM AND HBOOT-1.45.0013. If you are not on the Stock ROM, please use Blue6IX’s post “How-To: Restore to Stock.” Be sure to use the latest OTA (1.63.531.2). Once you're all set, let’s begin, shall we?
Disclaimer: I am not responsible for anything that happens to your phone. You assume all risks associated with modifying your phone.
-1. INSTALL HTC DRIVERS ON YOUR PC.-
Install the HTC Drivers on your PC from here.
Before connecting your phone, make sure USB Debugging is enabled (Settings>Applications>Development>USB Debugging).
Tip: to save time later, turn off your phone, hold down Power & Volume Down simultaneously until you reach the bootloader. Use the volume buttons to navigate to FASTBOOT and select it with the power button. Connect your phone via USB and the bootloader should now say FASTBOOT USB mode. Allow your PC to install the required drivers automatically. It may take a few minutes for your PC to search for and install drivers, so be patient.
-2. INSTALL ADB AND FASTBOOT ON YOUR PC.-
Installing ADB and fastboot on your PC is easy. Follow this guide and you’re good to go. To confirm that you have successfully installed ADB and fastboot, connect phone (with USB Debugging enabled) to PC via USB, open command prompt, and type “adb devices”. Your device ID number should be listed. Here are some useful commands for ADB and fastboot.
-3. REGISTER AT HTC DEV.-
Self-explanatory. Visit HTCDev.com and sign up with a valid e-mail address, as you’ll be receiving your Unlock_code.bin from HTC through this e-mail. Use an alternate browser such as IE, Google Chrome, or Mozilla Firefox if HTC Dev doesn’t play nice with your current browser of choice. Personally, I had to switch between Chrome and Firefox to get the HTC Dev website to cooperate.
-4. UNLOCK BOOTLOADER THROUGH HTC DEV.-
Make sure you’re logged in to HTC Dev and follow on-screen instructions to unlock bootloader. FYI, our device is listed as “myTouch 4G Slide (T-Mobile US)”. You can skip HTC’s instructions until step 5 since they're just telling you how to install ADB and fastboot, but you should already have ADB and fastboot installed .
After you finish unlocking the bootloader, the first line in your bootloader should read “*** UNLOCKED ***”.
-5. INSTALL A CUSTOM RECOVERY.-
Download official ClockworkMod Recovery 5.0.2.7 from the ROM Manager website or download another custom recovery from the MT4GS Development section. For instruction purposes, I will assume that you use official CWM Recovery 5.0.2.7. Save the img file to C:\.
Put your phone in bootloader FASTBOOT mode and connect to PC. Go to command prompt on PC and type “fastboot devices”. Once your device ID is listed, type “cd\” to get to “C:\” directory. Then type “fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img”.
After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping.
NOTE: Use volume buttons or trackpad to navigate through CWM Recovery 5.0.2.7. Select items by pressing the trackball. Power button may make your screen go blank and Back button returns you to the previous menu.
-6. ROOT YOUR DEVICE.-
Now that you have a custom recovery, you can flash custom ROMs. These custom ROMs are already rooted with Superuser and binary files.
NOTE: If you are S-ON, installing a custom ICS ROM will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
HOWEVER, if you want to root the STOCK ROM and/or continue to step 7 to achieve JuopunutBear S-OFF, you’ll have to root the device yourself. This is very simple. Download Superuser ZIP from androidsu.com/superuser. I can only recommend version 3.0.7 efgh because that is the only one I have tested, but newer versions may work.
Place the “Superuser-3.0.7-efgh-signed” on the ROOT of your SD card. Go to CWM Recovery and use “install zip from sdcard” to flash the Superuser zip. If installation aborts or fails the first time, try to flash the zip again until installation is complete. Reboot your phone and check in your apps to see if Superuser app is there. If so, congratulations, you have successfully rooted your stock MT4GS!
-7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).-
Achieving S-OFF will make your life a lot easier if you want to flash custom ROMs, especially ICS ROMs. Follow instructions for JuopunutBear at unlimited.io and check out the JB S-OFF thread for other users’ experiences.
As I said before, if you are S-ON, flashing ICS ROMs will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
Click to expand...
Click to collapse
For step two, you can use the adb binary I mentioned earlier. Same thing, different location.
As said above, you don't need to do step 7. If you are afraid of potenitally ruining your phone with the "wire trick" I wouldn't bother with the step, just keep in mind when you do put KitKat on your phone, you will have to extract the boot.img from the package, go into the bootloaders fastboot mode and run the following command (from your PC):
Code:
fastboot flash boot boot.img
And you can apparently do this before or after (get CWM to reboot to bootloader) flashing with CWM (which you will need to upgrade to get KitKat) to avoid a bootloop. If that happens, pull the battery, reinsert, then power up into the bootloader (Pwr+Vol-Dn keys).
Ok bud thanks for all ur help so far I just have a few questions sorry 14 hr days dnt help me check in lol. Question 1 if I don't have kitkat y can't.I move apps to my sd card? Question 2 do I need to downgrade. Anything to root? Question 3 y can't I save apps on my sd?
SOEBOMB said:
Ok bud thanks for all ur help so far I just have a few questions sorry 14 hr days dnt help me check in lol. Question 1 if I don't have kitkat y can't.I move apps to my sd card? Question 2 do I need to downgrade. Anything to root? Question 3 y can't I save apps on my sd?
Click to expand...
Click to collapse
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.
joel.maxuel said:
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.
Click to expand...
Click to collapse
Well ima gna try to root it with what u posted I feel a bit better knowing I dont have to donwgrade and all that etc. im gna follow the steps.hopefully ill be posting in a rooted device in the near future lol paperweights this rookie dnt need
Any other tips I should know?
SOEBOMB said:
Any other tips I should know?
Click to expand...
Click to collapse
Be sure to make a backup in Clockwork Mod or whatever custom recovery you install. This will give you the chance to rollback should you encounter any problems swapping to a custom rom.
Alandra said:
Be sure to make a backup in Clockwork Mod or whatever custom recovery you install. This will give you the chance to rollback should you encounter any problems swapping to a custom rom.
Click to expand...
Click to collapse
Prolly not gna flash a rom should I still do a backup I read rooting clears ur whole phone is that true like sd card n all? I domt care for music n etc jus dnt wanna lose my sons photos off my sd
SOEBOMB said:
Prolly not gna flash a rom should I still do a backup I read rooting clears ur whole phone is that true like sd card n all? I domt care for music n etc jus dnt wanna lose my sons photos off my sd
Click to expand...
Click to collapse
Unlocking the bootloader does, yes, wipe your /data partition, but that should be all (besides /cache). If you are concerned about it wiping your MicroSD as well, can always pull the card before getting to that step.
joel.maxuel said:
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.
Click to expand...
Click to collapse
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?
SOEBOMB said:
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?
Click to expand...
Click to collapse
My H-BOOT is 1.45 as well (1.45.1313 since I went S-OFF) and I had no problem rooting. Probably talking about outdated information, like when everyone rooted their phone with Revolutionary. Rooting is possible, S-OFF is possible (via JuopunutBear). And the last bit about trouble flashing ROMs has to do with having to flash the boot.img file as well because you are still S-ON (please see my earlier post about that).
SOEBOMB said:
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?
Click to expand...
Click to collapse
I am also on H-Boot 1.45.0013 and have had no problems rooting and installing custom roms. I am still S-On, which has caused me no issues, but I simply have to use the method in this post to successfully flash a new rom:
http://forum.xda-developers.com/showpost.php?p=22774848&postcount=1
s off toolkit
has anyone used this to root and s-off there mt4gs???
http://forum.xda-developers.com/showthread.php?t=1532809
http://forum.xda-developers.com/show....php?t=1696373
SOEBOMB said:
has anyone used this to root and s-off there mt4gs???
http://forum.xda-developers.com/showthread.php?t=1532809
http://forum.xda-developers.com/showthread.php?t=1696373
Click to expand...
Click to collapse
Cannot say I have. Mind you I'm a linux user so I avoid windows programs where I can.
The second link was broken. I fixed it in the quote. In regard to version 2.0 (first link), the download links have been pulled and the thread closed. Don't bother asking anyone for it. Version 1.0 appears to be still up, although by the looks of the screenshot and changelog, you would be better off following the guide. It's not that difficult.
SOEBOMB said:
Any other tips I should know?
Click to expand...
Click to collapse
Superuser link appears dead. Here is a live one...
I have a Rooted and s off HTC one Sv from Boost mobile. I can download the OTA for Sense 5 and 4.2.2 but when I try to install it it cancels and says something like cant get ro.products.build = k2cl.. and something else ...
Im new to all of this, but Im really good with following a step by step guide if there is something I can read to fix this issue.
Im just trying to get the latest software available for this phone. And also if there is a way to edit the build.prop on this phone to make it run faster and increase the network speed too. that would be amazing. I have yet to find anything for this phon
Well, for boost mobile you can use a Ruu which they released for the latest available Software.
http://dl3.htc.com/application/RUU_...V_NV_Boost_2.20_150_release_389346_signed.exe
This will delete all of your data and your bootloader must be locked, if you are S-on (only as an info, in case you have unlocked at htcdev.com to gain root access).
Hi. Thanks.
So I need to turn the bootloader off and switch S off back to S on?
I dont remember what software I used to root it, it was on my other computer that got stolen.
How would I go about locking the bootloader? And turning the S back on? And once successful in getting the update will I be able to root it again?
Is there any other better roms I can flash on it now that is better? I would love to have KitKat on here if possible.. But as of now I know that cyanogen mod isnt supporting this device and all I know to do is update it to 4.2.2 with sense 5, if I could just figure out how.
Sorry for all the questions.
Last question is... I seen build.prop editing possiblities to be able to speed up 4g, 3g, and 2g networks speeds and even to bypass network caps, but no guides for htc one sv for boost. Are there any that I can be directed to to edit the build.prop to achieve this?
Don't know about boost specific tweaks.
Also there are no custom roms available for boost.
You are S-off, you didn't mention. But thats good! Don't go S-on, and no need to relock bootloader in this case, as far as i remember.
Backup everything you need, connect your device to your pc and run the Ruu. It will bring you to the latest software for your phone.
Ive been trying over and over to get the Ruu to work and I followed the instructions properly. And even deleted it and downloaded it again.
It keeps saying : Error 170 USB Connection Error. And wants me to check the USB sync cable or my connection to the PC.
But Both my cables work fine and my computer is new and nothing wrong with it. I am able to use my USB to Tether app just fine and im able to copy and paste to and from my phone and able to use HTC Sync manager too. SO Idk what the deal is.
Maybe some specifics about my setup may help.
My computer is an HP Envy Sleekbook with 8g of ram and i5 processor running windows 8.1 64bit.
My phone is the Boost mobiles version HTC One SV C525c with these details:
Android Version: 4.1.2
Sense: 4
Software number: 2.06.653.6 710RD
HTC SDK API: 4.65
HTC Extension Version: HTC Extension_Sense45_12
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: 2.06.653.6 CL209682 release-keys
I dont know if that helps with my situation but just in case I added it.
Thank you and I appreciate the help
Do a research on google with "htc ruu error 170".
You will get many results, like this:
http://forum.xda-developers.com/showthread.php?t=2553296
No matter what I do nothing seems to be helping
I have been googling for days. And been at it for hours today trying to figure this out.
I really just need a step by step guide. I dont understand this stuff.
So far, I downloaded and unistalled and reinstalled drivers for windows 8.1. I downloaded adb drivers and fastboot.
I tried to use RUU by going into Fastboot usb. I even tried to download the OTA update and then manipulate the update-script by deleting all the assert checks to stop getting the getprop errors. But still didnt work.
IDK what to do all I want to do is have my phone back to normal again and to be able to update it to the newest software version. Its annoying to see the update available notification in my tray and I cant do anything about it.
The closest I got so far was switching to the windows 7 computer and turning off the developer options menu. But then RUU starts to work but then stops at HTC fastboot.exe has stopped working. Im stuck.
Some more information about my phone just in case its helpful. :
Moonshine S-OFF
K2_CL PVT SHIP S-OFF RL
CID-SPCS_003
HBOOT-2.00.4444
RADIO-1.12.50.0516
OpenDSP-v9.2.0268.1214
eMMC-boot
I also got rid of CWM and put TWRP v2.8.4.0
I just went to the bootloader screen and tried to install the OTA file from there and also the OTA file that I deleted the assert build prop stuff from and I get the same error E: Error executing updater binary in zip
SO idk what to do but im determined to fix this.
Thank you much for helping me
Now my phone wont work at all.
Its stuck on the HTC screen and I cant figure out how to get it back. I know there is a way. This really sucks.
guitarjae said:
Now my phone wont work at all.
Its stuck on the HTC screen and I cant figure out how to get it back. I know there is a way. This really sucks.
Click to expand...
Click to collapse
Theres is not much what i can do, because i don't know much about boost, and i don't have any files for it.
Maybe @Modding.MyMind can help you here, he has much more knowledge in this kind of stuff, than me.
Ok. I managed to get my phone unbricked by using windows 7 and using fastboot to flash the same operating system I was already using. Now I don't have twrp or cwm. Its just a red triangle now if I try to log into recovery.
It is also switched from moonshine s off to locked.
So I'm assuming I'm S on now and bootloader locked.
I went back to the RUU program you told me to install and it started to work but then stop and gave an error 158 image error. I googled it but I don't understand how to fix it.
Is there any way I can just get sense 5 and 4.2.2. I'm starting to think its not possible. But would be nice if I could.
I don't know, whats wrong here. What have you flashed on your phone to get it running?
A RUU? This would explain, that you loose twrp, because it flashes everything to stock. But it don't set S-off to S-on! That step has to be done manually by yourself.
---------- Post added at 09:57 ---------- Previous post was at 09:13 ----------
Please check this website for more information and download of the RUU you need:
www.htc.com/us/support/htc-one-sv-boost/news/
guitarjae said:
Ok. I managed to get my phone unbricked by using windows 7 and using fastboot to flash the same operating system I was already using. Now I don't have twrp or cwm. Its just a red triangle now if I try to log into recovery.
It is also switched from moonshine s off to locked.
So I'm assuming I'm S on now and bootloader locked.
I went back to the RUU program you told me to install and it started to work but then stop and gave an error 158 image error. I googled it but I don't understand how to fix it.
Is there any way I can just get sense 5 and 4.2.2. I'm starting to think its not possible. But would be nice if I could.
Click to expand...
Click to collapse
https://www.dropbox.com/s/tacg3jdz84c6wlh/Pure_Jelly_Bean_4.1.2_TWRP_Backup.zip?dl=0
Download this pure 4.1.2 JellyBean backup made specifically for TWRP and extract the zip on to your desktop. Flash the TWRP recovery to your recovery partition using fastboot.
Code:
fastboot flash recovery twrprecovery.img
Reboot in to TWRP, make sure your device is plugged in to your computer.
Now before we move on further I need you to make a quick TWRP backup. You do not need to make a full backup. Just one will do since I am merely aiming to have the required TWRP backup directory be created on your device.
Did you make a quick backup? Good. Lets move forward.
Select the option to mount your usb (You should still be in TWRP). A window will pop up on your computer showing either your internal or external storage. Find the TWRP folder and look through it until you find the backup folder. Go inside the backup folder and you will see the files created to make your backup. Delete them all.
Copy my backup that you downloaded earlier over to that same directory. When done, unmount device from computer, then unmount device from phone. Select to restore your device using that TWRP backup. After completition, reboot your device, let the phone start up. Welcome back to 4.1.2.
Go to settings to manualkly update your device to 4.2.2 but before you accept the update you must make sure you flash back your stock recovery using the same instructions given at the beginning. DO not attempt to accept the OTA with TWRP installed, it will fail.
Hey thanks
Im on 4.1.2 now
Last night I went to this forum http://androidforums.com/threads/htc-one-sv-boost-stuck-on-splash-screen.826881. When I was there I followed the instructions that the guy gave the other guy for his problem, since I was bricked and stuck on the splash screen. I downloaded this https://www.dropbox.com/s/wqq04edwc844ufw/decrypted_k2_cl_2.06.653.6_rom.zip. And that got me back to 4.1.2 with sense 4.
Now since I did that it deleted the twrp I had on it and where it used to say moonshine S Off it now says LOCKED? So, I dont know what that means if Im s off or not anymore.
I went to download the update to 4.2.2 and it started to install but then just rebooted and it still asks me to update and im still on 4.1.2. I also tried the RUU again in fastboot mode and it will start to install and stops at error 158 image error. ? ... I also took the OTA update file that downloaded from the downloads folder and put it on my computer and tried to flash it with fastboot and it still stops after some kind of check. I even edited the update-script to delete the assert at the top and it started and stopped at a different error. So idk..
Right now my phone is back on and I can use it. I just want to get the update somehow. So maybe if you still think I should try again and do what you just mentioned, Ill do it tonight once i get to my desktop with win 7 since win 8.1 is stupid with this.
guitarjae said:
Hey thanks
Im on 4.1.2 now
Last night I went to this forum http://androidforums.com/threads/htc-one-sv-boost-stuck-on-splash-screen.826881. When I was there I followed the instructions that the guy gave the other guy for his problem, since I was bricked and stuck on the splash screen. I downloaded this https://www.dropbox.com/s/wqq04edwc844ufw/decrypted_k2_cl_2.06.653.6_rom.zip. And that got me back to 4.1.2 with sense 4.
Now since I did that it deleted the twrp I had on it and where it used to say moonshine S Off it now says LOCKED? So, I dont know what that means if Im s off or not anymore.
I went to download the update to 4.2.2 and it started to install but then just rebooted and it still asks me to update and im still on 4.1.2. I also tried the RUU again in fastboot mode and it will start to install and stops at error 158 image error. ? ... I also took the OTA update file that downloaded from the downloads folder and put it on my computer and tried to flash it with fastboot and it still stops after some kind of check. I even edited the update-script to delete the assert at the top and it started and stopped at a different error. So idk..
Right now my phone is back on and I can use it. I just want to get the update somehow. So maybe if you still think I should try again and do what you just mentioned, Ill do it tonight once i get to my desktop with win 7 since win 8.1 is stupid with this.
Click to expand...
Click to collapse
You should still be S-Off. If you boot up to your bootloader it will either say S-On or S-Off. You used a decrypted RUU so it is a good chance your bootloader is in fact locked. You lost TWRP because the "RUU" restored your device back with the original images as if your device came right out of the box. Which is the whole purpose of an RUU. As for the issue you are having with the OTA update, that seems a bit off, so just follow my instructions and you should be fine. Check to see if you are S-On or S-Off. Also insure that your bootloader is unlocked. If you are S-On then take the boot.emmc.win file from my backup and rename it to boot.img. Use fastboot to flash the boot.img to the boot partition.
Code:
fastboot flash boot boot.img
recovery.emmc.win is the stock recovery. Again, if you are S-On, then rename it to recovery.img and flash it using fastboot.
Code:
fastboot flash recovery recovery.img
This is required because being S-On will prevent you from writing to those partitions using DD. Requires you to be S-Off otherwise. If you are S-On, then that is fine. First focus on getting yourself up to 4.2.2. Once that has been accomplished then use rumrunner universal for HTC to gain S-Off again.
Modding.MyMind said:
You should still be S-Off. If you boot up to your bootloader it will either say S-On or S-Off. You used a decrypted RUU so it is a good chance your bootloader is in fact locked. You lost TWRP because the "RUU" restored your device back with the original images as if your device came right out of the box. Which is the whole purpose of an RUU. As for the issue you are having with the OTA update, that seems a bit off, so just follow my instructions and you should be fine. Check to see if you are S-On or S-Off. Also insure that your bootloader is unlocked. If you are S-On then take the boot.emmc.win file from my backup and rename it to boot.img. Use fastboot to flash the boot.img to the boot partition.
Code:
fastboot flash boot boot.img
recovery.emmc.win is the stock recovery. Again, if you are S-On, then rename it to recovery.img and flash it using fastboot.
Code:
fastboot flash recovery recovery.img
This is required because being S-On will prevent you from writing to those partitions using DD. Requires you to be S-Off otherwise. If you are S-On, then that is fine. First focus on getting yourself up to 4.2.2. Once that has been accomplished then use rumrunner universal for HTC to gain S-Off again.
Click to expand...
Click to collapse
Hello
Sorry I havent been online lately to give an update.
Thank you for your help. I am successfully now on 4.2.2 with sense 5 by following your instructions.
So now all I have to do is Root again. Can you tell me an quick and easy way to Root again?? I did it last over a year ago on this phone and I think the way it was rooted was the reason I was having such issues. But idk.... Im open for better options on rooting the phone. Towelroot doesnt work for this phone, not that I every used towelroot, i just seen that lots of others are saying it worked and it was fast and easy.
After I root it, I want to be able to increase my phone storage too and be able to move apps to sd card instead of it using all my phone storage. It is already saying cant download bc of insufficient storage.
And other than that, do you know of a good build.prop script for this phone that can increase network speed and maybe bypass the data cap?
Also, I still dont know how I can tell if Im S off or S on? When I hold the vol down and power button, it pops up like it used too but instead of saying its S off it just says LOCKED?