This thread is supposed to become a HowTo eventually. In fact I will write it like a HowTo, but with some remarks and questions in between, as I have not tried the procedure (still on unrooted stock rom atm). I just thought I post this here anyway, as it might be helpful for someone.
Until all the questions are answered and someone succeded to rebrand, consider this thread as a think tank, with some of the thinking already done
So what is this all about? There often is the question how to flash the correct stock rom for warranty purposes. This is an easy task if the correct RUU is available. Unfortunately the recent SLCD desires often lack a corresponding RUU. If you flash the 2.1 ruu that rebrands an amoled, you will end up with a black screen, making an ota update nearly impossible.
But now S-Off is in the wild, there might be a workaround for that. There are just some things that have to be considered first... Things that I am not sure of will be marked in red. I will explain some more details on the explicit steps when the principle is confirmed working. If you dont have a clue how to perform those steps right now, it might be better to wait for the more detailed version.
As always: Do this at your own risk.
[UPDATE]
Some advances have been made here thanks to Hummelchen, who volunteered to try this procedure on his desire. It was a T-Mobile germany branded Amoled device, but care was taken to ensure that this procedure also works on SLCD without going through a phase where the screen stays black. Nonetheless, a final test still has to be done.
I updated the HowTo, but better wait until Hummelchen has confirmed it, as he was the one who tried it.
Prereqs:
- A desire to rebrand with S-Off
- fastboot and a zip-sign tool ready to run
- A RUU that corresponds to your carrier (that would normally break your display)
- The froyo OTA package that updates from the software version included in the RUU
Rename the ota_update to 'update.zip' and copy it to the root of your sd on the phone (better not forget that)
Extract the rom.zip from the RUU (double check CID in android-info.txt, compare with http://forum.xda-developers.com/showthread.php?t=631519) by running the RUU (without phone connected) and fetching the file out of your temp folder
extract the zip and delete the hboot file and the recovery
Extract OTA, extract the firmware.zip within the OTA and copy the included recovery.img into the same directory where the rest of the RUU files are
(maybe not really needed: edit android-info.txt like here)
zip, sign
boot into fastboot
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <your_signed_zip>
Don't try to boot into the system now. As the kernel does not have SLCD drivers, all will be black
Instead boot into recovery and apply the OTA -> you will end up on a totally debranded/unrooted/s-on desire!
Thanks go to Hummelchen, who came up with lots of ideas and the guts to just try it on his own device. Also to ieftm for a little support on fastboot commands.
mblaster
For TMobile Germany/UK/CzechRep./Netherlands (according to the CID info in the OTA and base ROM) users, Hummelchen has prepared something nice:
Hummelchen said:
Okay, here is it: CustomRUU
# MD5
9ff8adf8c2471c3e2d085203d4923904 customRUU.zip
# SHA1
b5c3e174af3a797ed4f500d573794db74c595d35 customRUU.zip
I didn't found another way as fastboot. But if this RUU works, we could write a simple script to install it.
This customRUU comes without Hboot. So everyone could test it without risk.
This is the way:
1. Go to fastboot (the script could send: adb reboot-bootloader)
2. type: fastboot erase cache
3. type: fastboot oem rebootRUU
4. type: fastboot flash zip customRUU.zip
5. type: fastboot reboot
The phone will reboot to T-Mobile Stock rom.
-----------------------------------------------------
Now the way to do it on other roms (don't tested) with hboot.
1. Strip the rom.zip from your 2.1 RUU and extract it to your favorite folder.
2. delete recovery and hboot.
3. Open the OTA.zip, open the firmware.zip which is in it and extract the recovery.img to the first folder.
4. Open android-info.txt and delete hbootpreupdate:2. Save it!
5. Now zip the files in the first folder and use the commands above.
6. Now you have a S-Off Hboot and the new recovery. You should be able to flash the OTA.zip with your recovery. This OTA will overwrite your Hboot.
That's it
Click to expand...
Click to collapse
Has anyone tested?
Sent from my HTC Desire using XDA App
At least no one reported back. Seems like the interest in this topic is not too great.
I've found a RUU on T- Mobile AT to rebrand a SLCD Desire (froyo). It's the solution for my problem.
Sent from my HTC Desire using XDA App
A little question: I’ve i use the RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe the SLCD will brick (HBOOT 0.80). Could i use Fastboot to flash the Update.zip with Froyo without root (HBOOT 0.93)?
So i have to go to the bootloader and press „Power“, plug it to my notebook an send a „fastboot flash update.zip“ ? Could it work?
If this works, i will get a rebranded SLCD desire
Hummelchen said:
A little question: I’ve i use the RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe the SLCD will brick (HBOOT 0.80). Could i use Fastboot to flash the Update.zip with Froyo without root (HBOOT 0.93)?
So i have to go to the bootloader and press „Power“, plug it to my notebook an send a „fastboot flash update.zip“ ? Could it work?
If this works, i will get a rebranded SLCD desire
Click to expand...
Click to collapse
No, you will loose S-OFF since it will flash an unpatched HBOOT. Hence fastboot will be as good as useless.
Dragooon123 said:
No, you will loose S-OFF since it will flash an unpatched HBOOT. Hence fastboot will be as good as useless.
Click to expand...
Click to collapse
Also No . I think you can't even fastboot flash a .zip file. €: OK, just ReadTFM ... Fastboot flash update update.zip seems to work. But as stated, don't do it.
You will have to unpack the zip and flash the images manually (skipping hboot obviously).
@Hummelchen: Do you have a german TMo Desire? €: OK, just noticed the flag below your avatar...
mblaster said:
@Hummelchen: Do you have a german TMo Desire? €: OK, just noticed the flag below your avatar...
Click to expand...
Click to collapse
Yes. My Amoled Desire have a stucking pixel and TMo will send a SLCD. I hate the hard way
Sent from my HTC Desire using XDA App
Hummelchen said:
... the SLCD will brick (HBOOT 0.80) ...
Click to expand...
Click to collapse
Hummelchen said:
Yes. My Amoled Desire has a stucking pixel ...
Click to expand...
Click to collapse
Do you want to rebrand a SLCD or AMOLED Desire
Because with AMOLED you can just install the Eclair RUU and apply the OTA update...
My next desire will be an SLCD one. But I don't want to root as long as there's no easy way back.
Sent from my HTC Desire using XDA App
Hummelchen said:
My next desire will be an SLCD one. But I don't want to root as long as there's no easy way back.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
That's why I started this thread here. In theory my plan should work, but i am quite reluctant to test it myself just for the kicks. I am also on a german T-Mobile Desire.
€: I just had a nice idea, I just need to know if the current custom recoveries are able to apply a patched/resigned or even an unpatched OTA-update.zip.
This would allow the following:
1) Extract the rom.zip from the RUU (the one that would break slcd), unzip it, delete the hboot and recovery, zip again, fastboot flash update rom.zip -> everything but hboot and recovery are stock
2a) Boot into recovery and flash the ota.zip file and be stock/unrooted/s-on OR
2b) remove the firmware.zip from the ota.zip (also remove 'write_firmware_image("PACKAGE:firmware.zip", "zip");' from the updater script), zip, sign, flash from recovery. Manually fastboot flash boot/radio/rcdata from the omitted firmware.zip. This will bring you to a stock/unrooted system, but with s-off hboot and a custom recovery. This has the advantage, that you can make an actual nandroid of a stock system without root files sticking around. From there you can play around with your system as you like and always unroot in 2 simple steps by restoring the stock nandroid and fastboot flashing the firmware.zip (removing custom recovery and hboot from the phone).
I am just not sure if the custom recoveries handle the ota packages as intended (with all the file patching going on there), but i think there is no reason why it should not work.
Hmm... I could reroot my Amoled desire and test it
If hboot and recovery not affected i can flash the whole ruu on fail, right?
Edit: I've extracted the Rom.zip, deleted hboot and recovery and created a signed update.zip
Sent from my HTC Desire using XDA App
Would be interesting to see the result. I think as long as you can enter the bootloader (the one from alpharev) you cant really screw it up, as you can always install a recovery or system via fastboot. I think the RUU also only depends on a working hboot.
So if you are careful with that hboot (and remove it from the ota also), you should be fine (I hope...).
Might be that you need a goldcard for flashing the RUU to get back to stock afterwards, but I am not sure of that.
It would be great if you tried that, as it would make sure that there is a way back to stock for SLCD owners without a friendly RUU. Please report back if you have been brave enough to try.
ok, i've done it. I S-off'ed my Desire and try to flash the rom.zip of the T-mobile RUU without Hboot and recovery.
Flashing the system.img didn't work because it needs the original Hboot. Fastboot says: File is to large. Same on Recovery.
Flashing boot.img works, but without system... It seems the 0.80 Hboot has another patitionsize as 0.93. That's stupid.
Thats strange. The system image of the TMO RUU (I think i have downloaded the newer one of the 2 available) is only 222 MB. Standard size for Data is 258 MB, so it should fit in withut problems. I am quite sure that all the official hboots have the same partition size.
Did you by chance install an alpharev hboot with modded partition table, like the N1 table (149 MB) or the modded Sense Table (180 MB)?
Did you try to flash only the system.img via fastboot flash system instead of fastboot flash update zipfile.zip?
BTW: Thanks for trying.
Thats strange. The system image of the TMO RUU (I think i have downloaded the newer one of the 2 available) is only 222 MB. Standard size for Data is 258 MB, so it should fit in withut problems. I am quite sure that all the official hboots have the same partition size.
Click to expand...
Click to collapse
Hm.. Strange
Did you by chance install an alpharev hboot with modded partition table, like the N1 table (149 MB) or the modded Sense Table (180 MB)?
Click to expand...
Click to collapse
I had it originally. I start the Iso, S-Off and after that i try to flash the rom.zip.
Did you try to flash only the system.img via fastboot flash system instead of fastboot flash update zipfile.zip?
Click to expand...
Click to collapse
I try:
- Fastboot update rom.zip
- Fastboot flash system system.img
- Fastboot update system.zip (pack it with 7zip)
I also try to flash the rom.zip and the system.zip with clockworkmod recovery
Nothing works... :/
You could try a 'fastboot erase system -w' before flashing. This clears /system /data and /cache. Perhaps it helps.
€: Come to think about it this really makes sense. I guess the flashing routine checks how much space is free, as it perhaps does not necessarily delete the existing files on the partition. I don't know how the flashing process works, but maybe it is more similar to a file copy operation than a linux 'dd'.
mblaster said:
You could try a 'fastboot erase system -w' before flashing. This clears /system /data and /cache. Perhaps it helps.
Click to expand...
Click to collapse
It didn't work. Tested 2 mins ago
Seems like this problem is more or less known.
http://forum.xda-developers.com/showpost.php?p=8596521&postcount=38
Maybe we could ask ieftm for some help. €: Sent him a message.
Another thought: Did you use 'fastboot update filename.zip' or 'fastboot flash update filename.zip'? I've seen both syntaxes and they might do something different. Perhaps just try the one you didn't use.
Related
Hey ,
ok.. everything went fine Now my Desire S is S-off'ed and is rooted
(a big thanx to all who helped me here )
Now, I have a few questions before flashing the ENG HBOOT & installing the touch recovery (4EXT):
- Which zip file version of ENG HBOOT should I flash?
Got 2 zip files here: one of them is named "PG88IMG(ENG 0.98.2000)" and is having "engHBOOToverARX.img" named IMG file.
Other one is named "PG88IMG" and is having "hboot_0.98.0000_361a7ba6_0310.img" named IMG file.
I checked their size and MD5; size is same but their MD5 hashes are different.
Please suggest, which one to go for? Or should I flash a newer version of ENG HBOOT? the 2.00.xxx ? Which ones better? :|
- Flashing this ENG HBOOT is it equivalent to flashing a new radio?
-Will I need to format any partitions, cache,...anything? I am not going to install any custom ROM for now, so I need my applications and their data..everything intact (just being noob here )
--
UPDATE:
I have successfully installed 4EXT recovery but when I check my filesystem info it says that except the SD Card all of my partitions are already ext4! is that possible? i din't converted them. by default all phone partitions as EXT4? wow :O and my SD Card is shown as fat32 partition (its ok).
Anyways.. :|
--
- I am thinking to install the 4EXT touch recovery, found it comfortable instead of pressing volume/power keys again and again. (and offcourse donate to the dev; great job there..keep it coming! )
- Do I need to convert to EXT4 partition type? How can I check my existing partition type? well of which partition are we talking about here?..the internal memory or the SD card partition type? noob*
- Can somebody give me some short steps of how to install 4EXT without bricking my phone..as I am worried a bit now to move forward
Click to expand...
Click to collapse
S-off'ing and rooting was a walk in the park (thx devs for making it sooo..easy)
Regards,
sky770
sky770 said:
ok.. everything went fine Now my Desire S is S-off'ed and is rooted
Click to expand...
Click to collapse
Congrats SKy770! Welcome to the elite S-OFF club! (Just joking!)
sky770 said:
Which zip file version of ENG HBOOT should I flash?
Got 2 zip files here: one of them is named "PG88IMG(ENG 0.98.2000)" and is having "engHBOOToverARX.img" named IMG file.
Other one is named "PG88IMG" and is having "hboot_0.98.0000_361a7ba6_0310.img" named IMG file.
I checked their size and MD5; size is same but their MD5 hashes are different.
Please suggest, which one to go for? Or should I flash a newer version of ENG HBOOT? the 2.00.xxx ? Which ones better? :|
Click to expand...
Click to collapse
If you've used revolutionary, you're Hboot should now be RVL v6.98.1000?
The engHBOOToverARX is a modified v0.98 bootloader, which *pretends* to be v6.98.2000. This allows you to overflash the RVL hboot. The easiest method is to use fastboot.
To flash, extract the file on your computer to get the xxxxx.img. Boot into Fastboot mode (Vol- and power), click fastboot, plug in USB cable. and type the code:
Code:
fastboot flash hboot xxxxx.img
This should take like a second or less. Reboot into hboot to check.
Alternatively you can use the hboot update interface by placing the P88IMG.zip file on SD card, and when you boot into hboot it will ask you whether you want to update (click yes obviously). I personally don't like this method as people tend to forget to delete the .zip file and may be at risk of repeatedly flashing your hboot.
I don't know whether flashing v0.98 or v2.00 straight without going through v6.98.2000 would work? Try it?
the ENG v0.98 should work with most ROMs. I think v2.00 is only needed for some newer ROMs which require a /data/lib partition (better search round for which ROMs need it).
Tbh, never found any problems with v0.98, so I've stuck to it ever since I first rooted it. Don't think there is any real life benefits of one over the other (except obviously if your ROM doesn't work with v0.98).
sky770 said:
- Flashing this ENG HBOOT is it equivalent to flashing a new radio?
Click to expand...
Click to collapse
Yes and no. It's similar that radio updates can also be applied via fastboot or the hboot PG88IMG.zip interface...
But effectively you're flashing different things. BOTH GIVES YOU RISK OF BRICKING YOUR PHONE. So the tip is if it ain't broke, don't fix it!
sky770 said:
Will I need to format any partitions, cache,...anything? I am not going to install any custom ROM for now, so I need my applications and their data..everything intact (just being noob here )
Click to expand...
Click to collapse
Generally its a good idea to at least wipe the partition if you've messed with hboot. So its a good idea to backup before you mess around with your phone.
THis can be done through 4EXT easily. (the wipe/format settings)
sky770 said:
- I am thinking to install the 4EXT touch recovery, found it comfortable instead of pressing volume/power keys again and again. (and offcourse donate to the dev; great job there..keep it coming! )
- Do I need to convert to EXT4 partition type? How can I check my existing partition type? well of which partition are we talking about here?..the internal memory or the SD card partition type? noob*
Click to expand...
Click to collapse
Well, ext4 isn't strictly necessary... your phone will work on ext3, but if you've heard about the infamous Desire S eMMC problem, then ext4 gives you a little more protection.
(the problem I think is that on overloading the cache partition, say updating all market apps, the phone hangs... people intuitively do a battery pull which corrupts the /cache partition. There is a small risk of frying your memory if you quickly reinsert your battery back after you've battery pulled it, so its generally advised to wait 10 seconds after battery pull before putting battery back in.)
Ext4 supports write-back journaling so should be less susceptible to this...
to convert to ext4, use 4EXT convert tools (NOT wipe/format!)
sky770 said:
- Can somebody give me some short steps of how to install 4EXT without bricking my phone..as I am worried a bit now to move forward
Click to expand...
Click to collapse
Download the .apk file and install. You need to be rooted and S-OFF'd. It will then ask you to update, click yes. Then install the latest version (1.005 RC3?)
DOne.
anchemis said:
If you've used revolutionary, you're Hboot should now be RVL v6.98.1000?
The engHBOOToverARX is a modified v0.98 bootloader, which *pretends* to be v6.98.2000. This allows you to overflash the RVL hboot. The easiest method is to use fastboot.
Click to expand...
Click to collapse
Well, after using revolutionary I have HBOOT v.6.98.1002.
So should I use:
the Other one is named "PG88IMG" and is having "hboot_0.98.0000_361a7ba6_0310.img" named IMG file.
Click to expand...
Click to collapse
?
But as the name of the file suggests its 0.98.0000 and NOT 0.98.2xxx. *now am confused*
Well I extracted the "hboot_0.98.0000_361a7ba6_0310.img" file from the zip available here
and thx for clearing up my 4EXT doubt (so i am assuming that for 4EXT I don't have to re-format my partition(s)..simply install, convert partitions to ext4 and voila! )
the eMMC fried chip prob? yep..I saw that somewhere around here in forums :O *shrugs*
UPDATE:
I have successfully installed 4EXT recovery but when I check my filesystem info it says that except the SD Card my all my partitions are ext4 only! is that possible? :O and my SD Card is shown as fat32 partition (its ok).
Anways..
Hi guys,
I just tried flashing my HBOOT with the ENG HBOOT file available here
using the PG88IMG.zip method.
But the HBOOT said "bypassed".. now what is that? :O though I am able to boot into my stock ROM (thank god I din't bricked my phone phewff).
Now how can I work this one out to have 0.98.xxx ENG HBOOT?
Any help/suggestions would be appreciated.
Regards,
sky770
sky770 said:
Hi guys,
I just tried flashing my HBOOT with the ENG HBOOT file available here
using the PG88IMG.zip method.
But the HBOOT said "bypassed".. now what is that? :O though I am able to boot into my stock ROM (thank god I din't bricked my phone phewff).
Now how can I work this one out to have 0.98.xxx ENG HBOOT?
Any help/suggestions would be appreciated.
Regards,
sky770
Click to expand...
Click to collapse
Looks the RVL v6.98 hboot is bypassing (aka blocking) hboot flashes.
Did you try the fastboot method?
Try flashing the ENGHBOOToverARX.img first.
You should get hboot v0.98.2000? (just ignore it, as it is 0.98.xxxx in reality)
After you've done that. Flash ENG 0.98.xxxx
---------- Post added at 02:15 PM ---------- Previous post was at 02:07 PM ----------
sky770 said:
Well, after using revolutionary I have HBOOT v.6.98.1002.
Click to expand...
Click to collapse
Yes, sorry, my brain isn't functioning today...
The reason why you're 'bypassing' is that when you flash using the PG88IMG method, your hboot will detect / compare the version numbers.
As RVL 6.98.1002 (despite being 0.98 in disguise) is greater than 0.98.xxxx, it will not flash it.
the EngHBOOToverARX.img has version number 6.98.2000, which allows you to overflash the RVL 6.98.1002. This version I think also allows 'downgrade' flashing, so you can revert back to ENG 0.98.xxxx
anchemis said:
Looks the RVL v6.98 hboot is bypassing (aka blocking) hboot flashes.
Did you try the fastboot method?
Try flashing the ENGHBOOToverARX.img first.
You should get hboot v0.98.2000? (just ignore it, as it is 0.98.xxxx in reality)
After you've done that. Flash ENG 0.98.xxxx
---------- Post added at 02:15 PM ---------- Previous post was at 02:07 PM ----------
Yes, sorry, my brain isn't functioning today...
The reason why you're 'bypassing' is that when you flash using the PG88IMG method, your hboot will detect / compare the version numbers.
As RVL 6.98.1002 (despite being 0.98 in disguise) is greater than 0.98.xxxx, it will not flash it.
the EngHBOOToverARX.img has version number 6.98.2000, which allows you to overflash the RVL 6.98.1002. This version I think also allows 'downgrade' flashing, so you can revert back to ENG 0.98.xxxx
Click to expand...
Click to collapse
yeah.. we're on the same page now
I just tried flashing the 6.98.200 (engHBOOToverARX.img) but my HBOOT just ignored it after saying.. "parsing.." and nothing else.
So, right now my HBOOT is still sitting on 6.98.1002
Both times I'd tried I did it using the PG88IMG.zip method (i.e. just copied my file onto the root of SD Card and tried flashing it with HBOOT/Bootloader)
Regards,
sky770
sky770 said:
yeah.. we're on the same page now
I just tried flashing the 6.98.200 (engHBOOToverARX.img) but my HBOOT just ignored it after saying.. "parsing.." and nothing else.
So, right now my HBOOT is still sitting on 6.98.1002
Both times I'd tried I did it using the PG88IMG.zip method (i.e. just copied my file onto the root of SD Card and tried flashing it with HBOOT/Bootloader)
Regards,
sky770
Click to expand...
Click to collapse
Fastboot it?
0. Delete the PG88IMG.zip file to stop it causing you trouble.
1. Extract the .img file from the .zip file (so you get the engHBOOToverARX.img)
2. Plug phone to computer and get phone into FASTBOOT USB mode, get to hboot (vol- + power), then scroll to fastboot, it should say fastboot usb.
3. Get the android sdk tools.
4. Use the command line type:
Code:
fastboot flash hboot engHBOOToverARX.img
[\code]
whatever that .img file is called.
5. See the result? (if successful, you should get v6.98.2xxx)
6. Install ENG 0.98.xxxx the same way.
anchemis said:
Fastboot it?
0. Delete the PG88IMG.zip file to stop it causing you trouble.
1. Extract the .img file from the .zip file (so you get the engHBOOToverARX.img)
2. Plug phone to computer and get phone into FASTBOOT USB mode, get to hboot (vol- + power), then scroll to fastboot, it should say fastboot usb.
3. Get the android sdk tools.
4. Use the command line type:
Code:
fastboot flash hboot engHBOOToverARX.img
[\code]
whatever that .img file is called.
5. See the result? (if successful, you should get v6.98.2xxx)
6. Install ENG 0.98.xxxx the same way.[/QUOTE]
Well, I got the procedure described [URL="http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2"]here[/URL]. Confirmed. They are exactly the same as you have pointed out in the above post :)
Now, my HBOOT version is 6.98.2000 (PG8810000)
so..whats next? should I repeat the same steps for the 0.98.xxx ENG HBOOT; extracting and using the "hboot_0.98.0000_361a7ba6_0310.img" file?
:D
Regards,
sky770
Click to expand...
Click to collapse
and....Voila
My HBOOT says version 0.98.2000 (PG8810000) after second flash from 6.98.2000 (PG8810000). Also, Revolutionary's logo has also been removed from the top of Bootloader
I will be writing and attaching a small slightly modified batch file script using which noobs can easily change their HBOOT version.
I hope that small contribution could make XDA a better place for noobs (not to mention the enormous help I got here )
Regards,
sky770
sky770 said:
and....Voila
My HBOOT says version 0.98.2000 (PG8810000) after second flash from 6.98.2000 (PG8810000). Also, Revolutionary's logo has also been removed from the top of Bootloader
I will be writing and attaching a small slightly modified batch file script using which noobs can easily change their HBOOT version.
I hope that small contribution could make XDA a better place for noobs (not to mention the enormous help I got here )
Regards,
sky770
Click to expand...
Click to collapse
Congrats!
I bet you're fingers are now itching for a custom ROM...
Yeah, perhaps someone should write an article about how to flash S-OFF / hboots. The guides on the index are a bit old now.
anchemis said:
Congrats!
I bet you're fingers are now itching for a custom ROM...
Click to expand...
Click to collapse
Itching..? am frigging wanting to flash Fallout's latest RC *greedy me*
but will give it a break for now
anchemis said:
Yeah, perhaps someone should write an article about how to flash S-OFF / hboots. The guides on the index are a bit old now.
Click to expand...
Click to collapse
Already done..check this out
Regards,
sky770
hoping that my thread here is made a sticky :|
maybe somebody of you could help me out in spreading this thread
Thanks & Regards,
sky770
sky770 said:
Itching..? am frigging wanting to flash Fallout's latest RC *greedy me*
but will give it a break for now
Click to expand...
Click to collapse
I've been eyeing up the CM9 alpha progress... and it's been pretty stable so far!
Can't wait to get rid of sense!
anchemis said:
I've been eyeing up the CM9 alpha progress... and it's been pretty stable so far!
Can't wait to get rid of sense!
Click to expand...
Click to collapse
Yep..CM's always been one of my fav ROM to look forward to since I have been thinking to get a droid. Now it looks like I have something to build my turf on
Heres hoping that CM9 gets rock solid stability
Regards,
sky770
sky770 said:
Yep..CM's always been one of my fav ROM to look forward to since I have been thinking to get a droid. Now it looks like I have something to build my turf on
Heres hoping that CM9 gets rock solid stability
Regards,
sky770
Click to expand...
Click to collapse
It is so far despite being an alpha...
So long as you can put up with:
1. No FM radio
2. minor bugs
3. Camera only up to 4MPx
anchemis said:
It is so far despite being an alpha...
So long as you can put up with:
1. No FM radio
2. minor bugs
3. Camera only up to 4MPx
Click to expand...
Click to collapse
waiting for official ICS sources
fm radio? meeh..SKY.FM ftw!
anchemis said:
Fastboot it?
0. Delete the PG88IMG.zip file to stop it causing you trouble.
1. Extract the .img file from the .zip file (so you get the engHBOOToverARX.img)
2. Plug phone to computer and get phone into FASTBOOT USB mode, get to hboot (vol- + power), then scroll to fastboot, it should say fastboot usb.
3. Get the android sdk tools.
4. Use the command line type:
Code:
fastboot flash hboot engHBOOToverARX.img
[\code]
whatever that .img file is called.
5. See the result? (if successful, you should get v6.98.2xxx)
6. Install ENG 0.98.xxxx the same way.[/QUOTE]
excuse me :P
can i still do this if i already installed custom rom
[ROM][27 APR] [Reaper V3.0 | GB 2.3.7] [Reaper Kernel V1.2][FTL Launcher][UCS]]
?? thx for the answer
Click to expand...
Click to collapse
I received my phone with version 1.73 and immediately rooted and flashed cm10. Is there any benefits to updating to 2.20? If so what are they?
Between 1.73 and 2.20 there are a significant amount of bug fixes and performance enhancements. Best thing to do is download the 2.20 ruu, extract the rom.zip. in there you will have all the .img files, just flash them all individually in boot loader, making sure not to flash the hboot.nb0. That will update you to 2.20 and keep you on the older boot so you don't need to worry about flashing kernals seperatly from roms.
18th.abn said:
Between 1.73 and 2.20 there are a significant amount of bug fixes and performance enhancements. Best thing to do is download the 2.20 ruu, extract the rom.zip. in there you will have all the .img files, just flash them all individually in boot loader, making sure not to flash the hboot.nb0. That will update you to 2.20 and keep you on the older boot so you don't need to worry about flashing kernals seperatly from roms.
Click to expand...
Click to collapse
Downloading file - ok
Unzipping - ok
"Flashing individual img files" - Hrm.. How does one do that? I can't seem to find a guide for that..
Also, will that remove root access if one has already rooted, or will it still be there?
Will it prevent the phone from updating to the 2.20 OTA?
you will basically have the same thing as 2.20 ota minus the nasty new hboot.
Flash them in twrp?
Flash them in bootloader. Fastboot flash
I am sorry for being noobish when it comes to this. So I put all the image files in the same directory As adb except the h boot. So my phone should be in bootloader mode which is power and volume down when I flash the files. Thanks for all your help
Sent from my One X using xda app-developers app
18th.abn said:
Flash them in bootloader. Fastboot flash
Click to expand...
Click to collapse
Ok, I haven't been able to find a guide or howto on HOW to actually accomplish that (using only the phone and a linux PC)
What are the actual steps to this?
Does one have to have an "unlocked bootloader" to do this?
I'll keep looking, but if anyone can point me in the right direction that would be really cool.
disregard.... I think you would have too dd them individually in adb shell and I don't think there is any sort of tutorial on that method. But go to the stickies and eraste made a good thread on updating safely.
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
LSGio said:
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
Click to expand...
Click to collapse
1. No, if you have S-ON you can't create a NAND backup as you don't have a custom recovery.
2. ***TAMPERED*** means that an app or apps have gone into your /system/ partition, thereby triggering the tampered flag. You can remove this message by running a HTC RUU.
3. No, you first flash the zip file with the boot.img inside, then flash the boot.img in the bootloader. fastboot flash boot boot.img
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
Then yes you can make a backup and restore later. Just always full wipe, cache and dalvik cache wipe.
As far as flashing kernels/boot.img, if you are < hboot 1.13 then just flash via recovery. If your hboot is > or = to hboot 1.13tjen flash via fastboot or flash img GUI (available in the play store and in various threads).
And as of right now there is no s-off for the one s.
Sent from a baked One S
If I've helped hit the thanks button
LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
KACE321 said:
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
Click to expand...
Click to collapse
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
LSGio said:
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
Click to expand...
Click to collapse
fastboot oem writecid 11111111
usaff22 said:
fastboot oem writecid 11111111
i have 2 questions:
1.how many 1's do i have to write
2.can i get back to my cid and how?
Click to expand...
Click to collapse
Yes, you can make nand backups and restore them if you have a custom recovery. You don't need to have s-off for that but you do need to have your bootloader unlocked. Depending on your hboot version, restoring a nand backup will not restore your boot image. (1.09 and below will, 1.13 and up won't.) We do now have the means to downgrade hboot tho.
You get the *tampered* line if your recovery is unsigned. When you use a custom rom, you will most likely also get a red warning text over your boot splash. It's normal.
You have to extract the boot image from the rom zip and flash it in fastboot before you boot the new rom. This may even be before you flash the new rom. You can leave the rom zip unchanged and flash it in recovery.
-Jobo
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Sent from my HTC One S using xda app-developers app
LSGio said:
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Click to expand...
Click to collapse
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
LSGio said:
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Click to expand...
Click to collapse
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
touch of jobo said:
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
Click to expand...
Click to collapse
can you please tell me how can i download an ruu that matches my stock rom. cause when i get to the filefactory server it tells me that i need to buy premium because the file is larger than 500MB.
and the link to the ruu downloads is from this thread:
http://forum.xda-developers.com/showthread.php?t=1543588
if youll go to the first page and click the (ville S4) link you will see a list of ruu's but i can't download them because the size of them is larger han 500mb and i need premium.
Hello all. So a friend of mine handed me his One X today and from what I gathered he was unable to flash CM after unlocking the bootloader and flashing CWM recovery. I figured I would give it a shot since I am familiar with flashing roms etc but wow what a difference it is for HTC devices!
I've spent the past 2 or 3 hours browsing this subforum however I feel like I could be just misinforming myself. The phone is a Rogers HTC One X the firmware version it was running I am unsure of as its currently stuck in bootloop. I've attached a screenshot below of the current fastboot menu. As it seems the bootloader is indeed unlocked however it is still s-on and stock recovery. If someone would be kind enough as to point me in the right direction of how to gain root and flash a recovery I would be super grateful. Feel free to PM me as well.
Thanks for your time.
What is the full filename of the ROM you're trying to flash? Also, the phone is s-on so you would need to flash the boot.img via fastboot to get it to boot.
Sent from my Evita
timmaaa said:
What is the full filename of the ROM you're trying to flash? Also, the phone is s-on so you would need to flash the boot.img via fastboot to get it to boot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. From what I was told he flashed the latest CM nightlies for Evita through CWM. Although now it appears to have the stock recovery.
So as far as gaining root and flashing a recovery, since the bootloader is unlocked can I not simply flash a recovery through fastboot and then flash a rom with SU like CM?
Yeah you can, use TWRP recovery instead of CWM though. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP on the phone. Go into it, wipe cache/dalvik/factory reset/system, then install the ROM and gapps. Like I said though you'll need to flash the boot.img via fastboot afterwards. So once you've installed the ROM reboot to bootloader, grab the boot.img from the ROM zip and flash it using this command:
Code:
fastboot flash boot boot.img
Once that's completed you should be able to reboot into the ROM. Please note though that some of the latest CM ROMs have a few bugs, including booting problems.
Sent from my Evita
Hey thanks again timaaa for the fast reply! I've successfully booted into CM now after flashing the boot.img. Regarding the bootloader should I be concerned with s-on? Will I run into trouble down the road because I do not have s-off?
Cool, glad you got it booted. In my opinion getting s-off would be a good idea. The benefits include the following:
Not needing to flash the boot.img from a ROM/kernel through fastboot anymore.
Being able to flash radios (s-on restricts this on phones with a hboot equal to or greater than 1.14).
Being able to change hboot freely (or just remove the red warning text from the startup screen).
Being able to change CID if needed.
Being able to flash the required firmware package which is required to run current Sense 5 ROMs.
In order to get s-off you first need SuperCID though, the hex edit method will be the best to use. Here's a link:
http://forum.xda-developers.com/showthread.php?t=2212737
Once you have SuperCID you can go ahead and get s-off here:
http://forum.xda-developers.com/showthread.php?t=2155071
Both processes are pretty quick and simple, and the benefits are great.
Sent from my Evita
Hi everyone..
I am sitting on a One S which has an unlocked bootloader, is not S-off, Hboot 2.15.
Previously was rooted and had Viper Rom installed 3.1, experienced lot of random reboots, tried to go S-OFF with rumrunner and moonshine, without it working.
Tried to return to a nandroid backup (TrickDroid 9.0) but now system is not responding and results in a reboot after 1-2 minutes after rom is booted.
I would like to return to Stock Rom with a RUU, but I can't seem to find the right one and I really need some help..
Even if I found the right one I don't know how to install it because phone keeps rebooting and fastboot doesn't seem to work on Win 8.
HELP!!
Okay. I got fastboot to work on my girlfriends computer and windows 7..
I got the following from running "fastboot getvar all":
Code:
<bootloader> version: 0.5
<bootloader> version-bootloader: 2.15.0000
<bootloader> version-baseband: 1.15.50.05.29
<bootloader> version-spld: None
<bootloader> version-microp: None
<bootloader> version-main:
<bootloader> version-misc: PVT SHIP S-ON
<bootloader> serialno: H*************
<bootloader> imei: 35***********
<bootloader> product: vle
<bootloader> platform: HBOOT-8960
<bootloader> modelid: PJ4010000
<bootloader> cidnum: T-MOB101
<bootloader> battery-statis: good
<bootloader> battery-voltage: 3867mV
<bootloader> partition-layout: Generic
<bootloader> security: on
<bootloader> buildmode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> cimmitno-bootloader: dirty-64bedd38
<bootloader> hbootpreupdate: 11
<bootloader> gencheckpt: 0
Which RUU should I get my hands on?
And do I need to run any fastboot commands before I try installing the RUU?
same
i've ****d mine to lmao
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Hammerbak said:
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Click to expand...
Click to collapse
I have not seen a RUU that had a radio version that high. The highest version I have seen is 1.13. I think that's the problem.
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Hammerbak said:
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
Click to expand...
Click to collapse
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
Click to expand...
Click to collapse
Well, no I'm not in the US. I live in Denmark.
The phone however was bought in Germany 2 years ago, and was delivered from T-mobile I think.
I will give this a try.
However the reason I want to get back to STOCK is due to getting S-OFF.
If I can get the phone working as it is now with TrickDroid 9.0 ROM that would also suffice. At least for quite some time.
The problem I have with the ROM is that "system" stops responding on boot.
I am thinking that this problem could be due to kernel incompatibility because the phone had the Viper One ROM before, which I think flashed another kernel together with the ROM.
Could this be the problem and could it be solved with flashing a new kernel?
However is it possible to flash a kernel without the use of the recovery?
I can't mount the internal memory and the phone has no slot for a SD card
Again.. Thanks!
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
808phone said:
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
Click to expand...
Click to collapse
Already did post in there, with no responses so far..
Well I had TrickDroid 9.0 running fine before I updated to Viper One ROM, and this was when problems started happening.
Then I went back with a NAND restore from recovery..
I don't remember flashing the boot.img, as I thought that followed along when I flashed the TrickDroid ROM, but since I think that doing a NAND recovery, doesn't bring a long the kernel I guess that if I installed the kernel from TrickDroid I could get the phone working with this.. What do you think?
Which file contains the kernel..? Is that the boot.img?
Once again, thanks for putting an interest in this post and helping me out! You're a lifesaver so far!
If you are not s-off then you need to flash the boot.IMG.
If you didn't do this, then could be the problem. AFAIK the boot.IMG contains the kernel.
http://forum.cyanogenmod.com/topic/79408-fastboot-flash-boot-bootimg/
Here's another link that might help.
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom/
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Rapier said:
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
Click to expand...
Click to collapse
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD
Rapier said:
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Click to expand...
Click to collapse
Thanks.
There's definitively a lot I will have to work with.
As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you.
I would very much like to get back to TrickDroid first of all, since it's the ROM already installed on the device I think I only have to flash the kernel and then it should be working.
If it is so I can then put Viper One ROM on the phone and flash that using the procedure that you described above.
However I am unable to find the TrickDroid 9.0 ROM since the ROM seems to have gone out of development.. Or at least that is my guess. If I'm lucky I have it somewhere on my old laptop and can get the boot.img from there. And as well I know how fastboot and ADB works, I just need the commands that I will be using.
I will try to find the TrickDroid boot.img and flash that using fastboot and then I will get back to you.
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Hammerbak said:
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD...
Click to expand...
Click to collapse
HERE is a list with all RUUs, taken from dev section. Find what you may need
Hammerbak said:
...As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you...
Click to expand...
Click to collapse
No, you don't have a card slot but you should be able to mount the internal memory as an sdcard
Hammerbak said:
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Click to expand...
Click to collapse
Yes, you could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Sounds good. I would try and flash that boot.img. I had a similar problem but was able to find an RUU that worked.
Maybe you just missed this part (or not)
Reboot into bootloader
Go into fastboot mode
fastboot flash boot boot.img
fastboot erase cache
Reboot
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
I should point out that I did NOT have success with ViperOneS. It looks awesome and did lots of things well except hold onto calls! Every time I would make a call, it would hang up for no reason. This problem apparently doesn't happen to everyone, but it did to me.
BTW: I have CM11 running so smoothly on my HTC One S. Pretty much all of my major issues are fixed. Only the limitations of google remain.
Rapier said:
HERE is a list with all RUUs, taken from dev section. Find what you may need
Click to expand...
Click to collapse
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
Rapier said:
You could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Click to expand...
Click to collapse
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer..
Another thing I could do would be to go to the HTCDev page and try to unlock the bootloader again..
Which would you recommend?
Hammerbak said:
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer
Click to expand...
Click to collapse
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed). You could even flash an AOSP KK ROM if you like, the same way
Rapier said:
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed)
Click to expand...
Click to collapse
Okay. Just to put in aspect I have the following choices:
Try to gain S-OFF as phone is now with rumrunner or moonshine
Try to get TrickDroid to work by flashing a kernel that is supported
Try to flash Viper and it's kernel from fastboot
If I try to gain S-OFF using rumrunner, do I still need to unlock the bootloader through HTCDevs?
I will try the first mentioned choice first, since gaining S-OFF would ease stuff up quite a bit.
If I can't gain S-OFF using rumrunner I will try to use moonshine.
If that doesn't work either I will be happy with just getting TrickDroid 9.0 to work as a starter.. Step by step procedure to actually gaining a working device firstly.
Then I can start thinking of how to get Viper One working after that or going back to stock to try the S-OFF methods once again.
My list of intentions is to:
Get S-OFF - whether it works or not
Getting the device to be booted and actually perform phone calls and etc.
Research the method and possibilites of getting back to stock to try S-OFF again.
Plan further upgrades to either new ROMs and/or Kernels
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
808phone said:
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
Click to expand...
Click to collapse
Okay.
Is was just about to write what you put in your edit. Haha lazy me.. xD
Well I guess as a starter I can go and unlock the bootloader, flash a recovery and try rumrunner.
When I get the recovery working I can start to plan what to do next
EDIT:
Bootloader is unlocked now and for some reason recovery wasn't removed
so I have unlocked bootloader and have a working recovery now.
Will try rumrunner S-OFF now..