[Q] Weird Problem Flashing ROM's

[Q] Weird Problem Flashing ROM's - HTC Desire S

Hey guys,
I've been searching the net for a solution and couldn't find one so here I am...
My brother has a Desire S (SAGA) and for some reason I can't flash any JB ROM on it...And I've tried everything I know with no luck.
Some details, the phone use to have Android 4.0.4 with HBOOT 2.00.0002, I've used HTCDev to unlock the bootloader and then did root and CWM Recovery with no hassle. (so the phone was rooted with S-On).
I've tried to flash a new JB 4.2.2 ROM and got stuck on the white HTC logo screen.
Tried another 4.2.2 ROM, same thing...Did a little research and some people said I should flash the boot.img of the ROM I'm flashing as the phone is still S-On, so I did (I have the One X so I'm familiar with this) - No luck.
After that I thought the problem was my HBOOT being too new so I downgraded the phone back to HBOOT 98.xxx and then used the Revolutionary method to obtain S-Off and Root (the HTCDev way gave me errors) so now I'm S-Off with HBOOT 6.98.1002.
Tried again to flash a bunch of new 4.2.2 ROM's - No luck !
Now for the weird part (for me) - I CAN flash any ROM up to v4.0.4 (right now I managed to flash CM9) - anything newer and I get stuck on the white HTC screen (also tried v4.1).
Ohh, I also tried re-partitioning the SD card to FAT, FAT32, made EXT3 partition, EXT4 partition, Linux Swap - nothing worked.
Now I'm thinking of flashing the HBOOT to 7.00.1002 version but I'm not sure its the problem so I decided to post here hoping for an educated answer.
Anyone knows whats the deal here?? any suggestion will help.
Thanks in advance !

Change your hboot to 7.0.....

Your problem is that you have a Hitachi panel instead of a Sony.

I don't understand...Changing to HBOOT 7.00.1002 is going to help or are you sure its a problem with the panel?
How can I check who made the panel?

Rotem_46 said:
I don't understand...Changing to HBOOT 7.00.1002 is going to help or are you sure its a problem with the panel?
How can I check who made the panel?
Click to expand...
Click to collapse
Use the search engine?
Non-Sony Screen Panel Desire S Users Lounge + How-To
And use your common sense about a user's reputation as to which advice you take.

I already found that thread and as it turned out I do have the Hitachi panel....
Now I'm trying out ROM's with the fix provided on that thread hoping to find a good one for my brother's DS.
Considering my panel is Hitachi, should I Change the HBOOT to version 7.00.1002 ? I mean, will it change anything ?
Thanks!

Rotem_46 said:
I already found that thread and as it turned out I do have the Hitachi panel....
Now I'm trying out ROM's with the fix provided on that thread hoping to find a good one for my brother's DS.
Considering my panel is Hitachi, should I Change the HBOOT to version 7.00.1002 ? I mean, will it change anything ?
Thanks!
Click to expand...
Click to collapse
For the roms that don't need a /system/lib partition, going with the newer hboot doesn't change anything, apart from the fact that IIRC the /cache partition is smaller to make room for the extra /system/lib partition on the 2GB emmc. However, if you intend to flash a rom that requires a /system/lib partition, which is all MIUI roms and Desire XS IIRC, then you must flash the newer hboot. For other roms, like I said, it doesn't matter apart from that the space allocated to the /system/lib partition is wasted, which does not matter in any way.

I think that you must try changing your CWM and try to flash latest CWM in your HTC Desire S .. May Be It Will Solve Your Problem

Related

[Q] How to S-on after S-off with Revolutionary?

I've made S-off with Revolutionary method to upgrade my Radio, after I've made the upgrade I'm still having issues with my signal, so I'm thinking to send the phone in warranty, but I can't manage to do the S-off.
Do you have any solutions?

Alternate way to restore your phone to S-ON and stock
Hi,
I've spent the last few days digging through the internet, looking for ways to get my Desire S back to S-ON after AlphaReveX S-OFF. The reason? I need to send it in for repair due to a birth defect.
I thought I'd share the path which turned out to be successful. Remember that there's always a risk that your phone will end up bricked as a result of procedures like this. I take no resonsibility for bricked devices, this is just a statment saying what worked for me. Good luck.
My initial setup was AlphaReveX S-OFF with Clockworkmod Recovery and LBC Mod. As the ARX HBOOT can't be overwritten by the HTC update program, it has to be replaced by a HBOOT that can. Luckily I found this thread in which Igl0 provides a pretty much tailor made HBOOT for this purpose:
http://forum.xda-developers.com/showpost.php?p=15493125&postcount=1.
The only problem: It couldn't be flashed in the bootloader (it would just return the message "parsed .."). After this I tried flashing through ADB, but for some reason it didn't work either. My third attempt was more fruitful - I successfully flashed engHBOOToverARX.img through fastboot (HTC drivers required which you probably already have).
Just to keep things simple I've made a zip which contains the files needed (except HTC drivers) to perform this flash. This guide assumes that you have already tried other methods and are familiar with related terms.
1. Connect phone to PC and navigate to fastboot
2. Download and extract the compressed folder attached to this post
3. I've composed a simple .bat (called "Click This") that will open a cmd prompt
and execute the command: fastboot flash hboot engHBOOToverARX.img.
4. Restart and enter HBOOT.
Click to expand...
Click to collapse
If the file was transferred and flashed correctly, the header text in HBOOT should now read "ENG HBOOT ...".
Now you can go ahead and flash a HTC stock RUU. It will overwrite other customisations such as a custom recovery. The HTC Update failed on my first attempt (file: RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release), but luckily I found another RUU that worked (RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed). You can browse this great collection to find one that suits you: http://forum.xda-developers.com/showthread.php?t=1002506.
As my first RUU installation failed partially, I was left with only the stock HBOOT and a non working recovery. Though, I found out that I could perform the next HTC Update attempt while in fastboot, and it was successful this time.
Cheers
Maarten

Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!

More questions....I'm afraid
sebysebu said:
Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!
Click to expand...
Click to collapse
You need to provide more information and details like Settings->About Phone-> Software info Radio (Baseband),Build Number,Kernel etc
If you know what radio version you had on your phone when you got it and what you have now that would be useful.
As I believe what you're saying is that you still have the same ROM version (ORANGE) as your phone came with, but you've simply changed radio and S-OFF'd!?
Do you have a custom recovery installed ie CWM (clock work mod)?
Having a branded ROM shouldn't effect your signal reception...

sebysebu said:
Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!
Click to expand...
Click to collapse
Okay. I'm afraid I don't have the competence to answer that!

ben_pyett said:
You need to provide more information and details like Settings->About Phone-> Software info Radio (Baseband),Build Number,Kernel etc
If you know what radio version you had on your phone when you got it and what you have now that would be useful.
As I believe what you're saying is that you still have the same ROM version (ORANGE) as your phone came with, but you've simply changed radio and S-OFF'd!?
Do you have a custom recovery installed ie CWM (clock work mod)?
Having a branded ROM shouldn't effect your signal reception...
Click to expand...
Click to collapse
Now I have: Radio : 3805.06.02.03_M
Build number : 1.47.401.4
Kernel : 2.6.35.10
Before I don't know what radio I had.
Yes, I have the same ROM version (ORANGE) that camed with the phone, and I'd simply changed the radio after S-off by Revolutionary
I don't have any custom recovery installed.
Regards,
Thanks!!!

Rooted HTC Desire S bricked after stock ROM update.

I rooted my HTC Desire S after downgrading it's HBOOT from 2.00 to 1.47 something. I was not satisfied by using customised ROMs with lots of bugs so I flashed stock ROM HTC Saga Asia India and then updated it by mistake or you can say foolishly. Now my phone is not booting and it is stopped on logo screen. I tried to use recovery but it just wiped data and and reboots when I select Install Zip from sd card.
Any fix for this? I have to go to HTC care center or it can be sorted out at home? Thanks in advance.

hi,
i thing you have been flashed wrong RUU, or your procedure is wrong,
have you know your phone's cid
post here your phone's cid, anyone suggest you which ruu file you have to flash.

If you could explain properly and in proper readable font, what steps exactly did you perform to reach this phone state - people would help. As it is, my eyes hurt from looking at your post, I only see huge letters and can't read anything out of them.

it's same case with me..
and now i need some help too

padrik said:
it's same case with me..
and now i need some help too
Click to expand...
Click to collapse
I suggest you read this http://forum.xda-developers.com/sho...[GUIDE] How to be a New User (and not a noob)
I know you've been told to stop tagging your problems on the bottom of others, if I've noticed your posts then I'm sure a mod has.

[Q] un root & restoring the htc sensation

Hello
I have HTC SENSATION which i have rooted recently and installed " cm-10-20130307-bruce2728-pyramid.ion" the interface is amazing and i am in love with it...(Hats off to developers)
but now i am facing the continuous & repeated shutting down of phone .
as I Start it then with in a couple of seconds it shut down again... i have done the complete wipe also 2 times (using 4eXt Recovery control 2.4.6)...but the problem is same..i want to solve that issue..
insted of this some of the system apps is also not working. like torch and music player
configuration..of phone ..
htc sensation z710e
Firmware :- 3.33.720.6
H Boot No:- 1.27.0000
***Unlocked***
but S-On.
Now is that any way to back to UN ROOT the phone and get back to original Official OS of 4.0.3 ICS with sense 3.6....to get back the warrenty..
(sorry for bad English)

atulvijay007 said:
Hello
I have HTC SENSATION which i have rooted recently and installed " cm-10-20130307-bruce2728-pyramid.ion" the interface is amazing and i am in love with it...(Hats off to developers)
but now i am facing the continuous & repeated shutting down of phone .
as I Start it then with in a couple of seconds it shut down again... i have done the complete wipe also 2 times (using 4eXt Recovery control 2.4.6)...but the problem is same..i want to solve that issue..
insted of this some of the system apps is also not working. like torch and music player
configuration..of phone ..
htc sensation z710e
Firmware :- 3.33.720.6
H Boot No:- 1.27.0000
***Unlocked***
but S-On.
Now is that any way to back to UN ROOT the phone and get back to original Official OS of 4.0.3 ICS with sense 3.6....to get back the warrenty..
(sorry for bad English)
Click to expand...
Click to collapse
you can install a RUU. A RUU will make your phone stock again. look for your correct RUU by checking your CID
Code:
fastboot getvar cid
and look for the corresponding RUU. check anyting related to RUU's here. Read it all carefully so you don't make any mistakes. Make sure you know what you're doing before doing it

Not able to get Right RUU
onemanshow85 said:
you can install a RUU. A RUU will make your phone stock again. look for your correct RUU by checking your CID
Code:
fastboot getvar cid
and look for the corresponding RUU. check anyting related to RUU's here. Read it all carefully so you don't make any mistakes. Make sure you know what you're doing before doing it
Click to expand...
Click to collapse
Thanks for the Valuable information but a slight problem came...
as the device come with ginger bread and i updated it to ICS
Now
MY CID Come "HTC_038" which relates to HTC ASIA_India...
Software version is "3.33.720.6"
RADIO is "11.24A.3504.31_M"
Then related to this ia m not able to find the Right RUU in the links shown..please help me in that respect...
Thanks in advance...

atulvijay007 said:
Thanks for the Valuable information but a slight problem came...
as the device come with ginger bread and i updated it to ICS
Now
MY CID Come "HTC_038" which relates to HTC ASIA_India...
Software version is "3.33.720.6"
RADIO is "11.24A.3504.31_M"
Then related to this ia m not able to find the Right RUU in the links shown..please help me in that respect...
Thanks in advance...
Click to expand...
Click to collapse
1. you can always flash a ARHD custom ROM. It's appearance is identical to stock and you're much better of if you consider the effort. check the ARHD thread by mike1986 for details, downloads and how-to's
2. if you can't find a specific RUU for your device then find one that matches your FW and radio version. use the extracted ROM flash method from the RUU-link I posted to flash the ROM. this method is considerebly more effort and risk for failure. so when u choose to do this, read everything carefully and know what you're doing before doing it
I suggest going for opt 1

atulvijay007 said:
Thanks for the Valuable information but a slight problem came...
as the device come with ginger bread and i updated it to ICS
Now
MY CID Come "HTC_038" which relates to HTC ASIA_India...
Software version is "3.33.720.6"
RADIO is "11.24A.3504.31_M"
Then related to this ia m not able to find the Right RUU in the links shown..please help me in that respect...
Thanks in advance...
Click to expand...
Click to collapse
Get s off ,
Flash gingerbread version of ruu , do s on
Update to ics via HTC ota
Btw did u tried another roms , coz ion version of Bruce Rom has camera issue .. and that's y your camera and torch not works , this is known issue .
I suggest u to try another Rom , Arhd with stock kernel and c , if issue persists send it to HTC
Sent from my HTC Sensation XE with Beats Audio using xda app-developers app

onemanshow85 said:
1. you can always flash a ARHD custom ROM. It's appearance is identical to stock and you're much better of if you consider the effort. check the ARHD thread by mike1986 for details, downloads and how-to's
2. if you can't find a specific RUU for your device then find one that matches your FW and radio version. use the extracted ROM flash method from the RUU-link I posted to flash the ROM. this method is considerebly more effort and risk for failure. so when u choose to do this, read everything carefully and know what you're doing before doing it
I suggest going for opt 1
Click to expand...
Click to collapse
As per your suggestion i opted the ARHD ROM ant it installs fine...but after some time my phone refused to recognize the Micro SD card (Sandisk class 4--16 GB)
in which i made the one ext2 partition also..
now what to do...?

[Q] Need some help badly, I just messed up my phone

OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.

beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
Ok, first, you're all over the place. Why did you install a radio+RIL when it explicitly tells you not to? It's actions like this that get people like you into a lot of trouble and destroys phones.
Secondly, there is no Android Revolution HD for this device. I believe you have the HTC One XL / at&t One X (Evita) judging from your post, but like I said there's no ARHD ROM for the Evita, only for the HTC One X (Endeavoru). This leads me to believe that you're jumping between the two device forums, very bad idea, none of the stuff from the Endeavoru forum is compatible with our phone.
You're lucky the ROM install stopped otherwise you would have bricked your phone. Long story short, you have no OS because the ROM install didn't complete, you have a corrupt boot partition because you flashed the ARHD boot.img which isn't compatible. In future do not stray outside our device forum for any reason at all. Here's our forum main page, bookmark it:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Next. Performing a factory reset in TWRP recovery does not wipe user data (images/music etc). I'm not sure what you've done but the factory reset in recovery wasn't it. A factory reset performed in the bootloader does however corrupt the sd card, so never do a factory reset from the bootloader.
You might have a chance at saving some of your data using a data recovery tool in Windows. You'll need to mount usb storage in TWRP for Windows to access the sd. Do not under any circumstances do any writing to the sd card before you attempt to save your data.
In conclusion, you've made numerous mistakes with your device. You need to slow down a bit and educate yourself a bit better, a lack of knowledge when it comes to modifying devices is a very dangerous thing.
Please post the first five lines of your bootloader.
Sent from my Evita.

i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
ok guys thanks so much so far i will pick up again after work today.
bootloader says:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.19as.32.09.11_2
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012,21:08:24
I'm 99.9% i was s-off before this all...

There isn't and never has been an Android Revolution ROM in this forum. It's kinda easy to make the mistake, the forums are named similarly.
I'm 99.9% sure you weren't s-off before all this. A phone can't change the security status without you doing it manually. It just can't happen. Did you actually go through either the Facepalm or Rumrunner s-off processes?
Well, you definitely have the Evita (HTC One XL / at&t One X) so make sure you stay within the forum I linked to earlier.
Good luck with attempting to recover your data, I hope you get at least some of it back.
Sent from my Evita.

Ok so as far as mounting my sd card in twrp, there's something up with my screen touch input I think... I am not able to click that particular box in the 'mount' menu. It seems like that part of the screen was not clickable when installing roms and such but once I get into android everything works perfectly.
Is there a way to rotate the screen in twrp?
Also by looking at my bootloader info once I get my sd card mounted and recovered best as I can, what is my best plan of action? Re-lock and flash a stock att ruu and begin from scratch or what? Or just try and load a correct radio and rom? I'm not a complete newbie I know I made a foolish mistake but I have done this quite a few times playing on the inspire, cha-cha, my kids nabi 2 tablets and on this att one x. This is the first time I have gotten really stuck in probably 35 flashes. Just this time I might be over my head...

To be honest I've never tried rotating the screen while in recovery, so I'm not sure about that. Exactly which recovery type (CWM/TWRP) and version number are you using?
I think your best plan of action would be to run an RUU, this will bring everything back to the way it should be. You're lucky in the sense that you're still on quite an early firmware version, so you should have a couple of RUU options. One thing to be careful of though, absolutely do not run a jb RUU if you have SuperCID, it will brick your device. SuperCID + s-on + jb RUU = brick. We should check your CID just in case, connect your phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita.

beppomarx said:
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
Click to expand...
Click to collapse
There is absolutely no ARHD ROM for EVITA. You've made a grave error, and as timmaaa mentioned, you are lucky your phone isn't a paperweight now.
EVDEAVORU is partitioned completely differently from EVITA, so all bets are pretty much off on whether your data is still intact or not. The ROM itself may have overwritten your data. Also, if you happened to do a factory reset in hboot instead of TWRP (as you mentioned) this will corrupt the SD card on modded EVITAs (known issue, and somewhat common error).
Your best bet is to get the phone back up and running using timmaaa instructions. Then see if the files are still on the SD. If the data files aren't easily visible, you can also try data recovery programs to see if they can be salvaged (sometimes corrupted files get dumped to a temp folder, or otherwise recoverable).
But I wouldn't hold my breath on recovering the files. This is what always puzzles me (why folks never back their data, then freak out when its gone of damaged). If your data is important to you, its important enough to back up. And there are so many easy methods to do so (with built-in cloud backup apps and whatnot) yet so many folks neglect to do that. And all you are left with is regret when things do south. Its pretty much a no-brainer to backup anything important to you when modding the phone. I'm puzzling why so many folks never do it.

So since I have the 1.09.000 hboot i am going to download and install this:
1.85.502.3
File Timestamp: 25/05/12
Publically Seen: 06/06/12
Android: 4.0.3
Kernel: 3.0.8-01155-gca24d1e
hboot: 1.09.0000
radio: 0.17.32.09.12_10.86.32.08
adsp: 28.1.0.32.0504
wcnss: 1031120A
tp_syn3202: 3.0_PR1100755
tz: 001.031.511
sbl1: 001.031.503
sbl2: 001.031.501
sbl3: 001.031.502
OTA: OTA_Evita_UL_Cingular_US_1.85.502.3_R2_NEW_NFCPHON ESTORAGE-1.73.502.1_release_263287jkmeqj8u75z409z9.zip
RUU: RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe (Download)
Source: evita-ics-crc-3.0.8-271616b.zip
is this my best bet? I am going to try and check my CID status right now just need to download the android SDK and get that going...
**EDIT**
my CID is 11111111. is that superCID?
**EDIT**
looking for a way to remove superCID. If i just go S-off am i OK to run a RUU or should I keep looking to change my CID back?
**EDIT**
just downloaded WinDrid HTC One XL Toolkit and seems to be up and running fine. my plan so far is to S-off and run the RUU I posted above but I will wait for someone to chime in before I do anything else.. I feel like I am on the edge here and don't want to brick it... I can't find any way so far to return my CID but from what I read if I am S-off it should keep me safe.

S-off won't work unless you're able to boot into a ROM. I'd forget about using a toolkit for now, it completely bypasses some much needed learning, and doesn't always work anyway. I believe all you need to do is relock your bootloader and then run the RUU.
Sent from my Evita.

Ok I will look into how to re-lock that after work today. Can anyone else confirm this? Not that I don't trust you but wording it like 'I believe this will work' makes me ask again...

I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Sent from my Evita.

timmaaa said:
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Click to expand...
Click to collapse
ICS RUUs are free of the S-on and SuperCID bug. Plenty of folks have flashed that RUU (such as 2.20) with SuperCID with no issue.

so I am going to relock the bootloader, it's as simple as 'fastboot oem lock'? that's it? before doing so should i bother s-off first? here's my plan of action:
s-off
relock bootloader
run 2.20.502.7 ruu
unlock bootloader again
install twrp
load custom rom
that should work correct?

If you s-off first, I believe you do not need to relock the bootloader to run the RUU. Just s-off, then run the RUU.

As I've previously mentioned, you won't be able to get s-off unless your phone will boot a ROM. The above process looks right.
Sent from my Evita.

got back to stock just fine, now to work my way back to modded. You guys are the best thank you a million.

Please hit the thanks button on any post that you've found helpful on XDA.
Sent from my Evita.

Remember also to either s-off or change cid back to normal, it will assist in the future if you get in a jam like this.
Although s-off and flashing a rom for a different phone(like you did) may have ended up much worse as some of the checks that likely saved you will be disabled.
At very least do not OTA/RUU update to Jellybean while you are s-on and supercid!

S-OFF - Good idea? Please read before you decide....

All, please be aware that S-OFF is not a trivial thing to do - once you are S-OFF, you will NOT be able to go S-ON again, try and you'll have a nice mini paperweight!
You'll find that S-OFF can cause more problems than it can "solve" - a quick search will show that you may (actually, most likely will) have to keep your bootloader LOCKED to boot your ROM - a locked bootloader = no fastboot = no flashing new boot or recovery images. UNLOCKED = boot loop city, with you as the mayor!
The only way to use fastboot would be to run revone via adb shell or the TWRP built-in terminal, boot to hboot, do your fastboot stuff, then revone again to relock the bootloader so you can actually boot your ROM.
The reason that S-OFF became a popular was to remove HTC's system protection - system protection basically removes any changes made to the system and reverts to the original system image every time you reboot. REALLY annoying. S-OFF allows system mods, which is a good thing, BUT: It's NOT necessary, as the proper solution is a custom kernel which removes the system protection without you risking a bricked phone.
Bottom line is, AVOID S-OFF if you can.
S-OFF does have benefits and is very handy in certain situations, but felt that people should also be aware of the risks, and think before doing it, "Do I REALLY need to do this, or can I wait a short time after an Android version upgrade for a modded kernel, or ROM with kernel mods?"
I've now helped 16 members out of soft bricks, it's a long and laborious process - everybody wants the latest and greatest (I know I do!), but a little forethought and patience may save you £500 buying a new phone to get the latest and greatest. There is no claiming on warranty or asking for a refund for your brick.

Is this true, you can't turn s-on again without bricking the phone?
Also I'm currently s-off with an unlocked boot loader and don't suffer any boot loops. Using Magio R3 JB4.22 and JMZ kernel. Maybe you would suffer boot loops with a different setup, I don't know..
Also the kernel I'm using I'm sure has system protection disabled. Does this make s-off pointless for me? Does this do the same as s-off?
cheers.
Sent from my HTC One using Xparent Green Tapatalk 2

You my friend, are a smart man. You've stuck with a stable ROM which has a lot of solid development work which had been tested and verified. JMZ knows exactly what he is doing, and produced a kernel which, as you correctly pointed out, negated the need to s-off. ALL of the issues reported for 4.3 are down to people buggering about with something they don't really understand.
Stay stable.

Just in case I did at some point want to update my rom at a later date to 4.3 or maybe 4.4 when it's released, will I have issues being s-off? And is it possible to undo s-off? Or could I leave it as is without issues? I just want to be clear on this. Cheers.
Sent from my HTC One using Xparent Green Tapatalk 2

RuffBuster said:
Just in case I did at some point want to update my rom at a later date to 4.3 or maybe 4.4 when it's released, will I have issues being s-off? And is it possible to undo s-off? Or could I leave it as is without issues? I just want to be clear on this. Cheers.
Sent from my HTC One using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
There are roms for 4.3 (stock deodexed by tr1gg3r) which have a modded kernel which removes system protection, so no need for s-off - there is a new 4.3 magio rom coming very soon, I've been beta testing for a week.... It's sweeeeeeet! It's going to be about 60% smaller than the usual mini ROM due to getting rid of the massive amount of bloat.... Fast, trim, and battery life is a good 40% better!
When kitkat arrives (in February apparently!), it will be system protected, so I don't doubt the whole "stock/s-off" thing will kick off again - my advice to everyone is to have patience, a modded kernel included in a rom will be available a few days after the OTA....
Going s-off then attempting s-on is very risky.....
Hope this helps!

nelvinchi said:
There are roms for 4.3 (stock deodexed by tr1gg3r) which have a modded kernel which removes system protection, so no need for s-off - there is a new 4.3 magio rom coming very soon, I've been beta testing for a week.... It's sweeeeeeet! It's going to be about 60% smaller than the usual mini ROM due to getting rid of the massive amount of bloat.... Fast, trim, and battery life is a good 40% better!
When kitkat arrives (in February apparently!), it will be system protected, so I don't doubt the whole "stock/s-off" thing will kick off again - my advice to everyone is to have patience, a modded kernel included in a rom will be available a few days after the OTA....
Going s-off then attempting s-on is very risky.....
Hope this helps!
Click to expand...
Click to collapse
so once u s-off, is better to stay s-off right? Unless u have to exchange for warranty or something then u would have to take the risk to s-on. And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?

@abzboi "And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?"
it is the 4.3 rom that you have been discussing with tr1gg3r84 on his magiorom thread !!

abzboi said:
so once u s-off, is better to stay s-off right? Unless u have to exchange for warranty or something then u would have to take the risk to s-on. And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?
Click to expand...
Click to collapse
Warranty - If you touch the bootloader in ANY way, s-off/s-on, whatever, the device is MARKED and no tool or method to re-stock can hide this - if it goes back to HTC and is checked, they WILL know you have messed about with it. Fact.
For whatever reason someone has gone s-off, it's best not to mess about with it, the more modding the messier it gets. Google "back to s-on" and you'll see so many horror stories, and so many "HOW to return to 100% STOCK - 100% working!". Yeah, right.
S-OFF is unnecessary UNLESS you are an actual DEVELOPER, and have a full understanding of android and HTC system. 4.3 came out, people posted OTA's, then everyone found that they couldn't flash it as they were rooted/custom rom/custom recovery - ooooh, if i go back to "stock" i'll be able to install it. Errrr, I think you'll find that the majority of people who attempted to "re-stock" found that, "re-stock" = soft brick.
Stock rom IS sense rom
Braddison said:
@abzboi "And btw what is that 4.3 Rom? Is it like a stock Rom or sense Rom?"
it is the 4.3 rom that you have been discussing with tr1gg3r84 on his magiorom thread !!
Click to expand...
Click to collapse
Indeed it is. I've been beta testing versions for the past couple of weeks, and can confirm it's fast, slim, and de-bloated. Battery life is around 40% better....

@nelvinchi brilliant ! i've came from an galaxy s3 running slim rom and been looking for a superslim rom since gettin a one mini (as we are restricted with storage space).i hope tr1gg3r84 uploads the rom this weekend.
Re: S-off... i have no issues with s-off at the moment(no boot loops etc).will find out if i run in to difficulty when i flash the new MagioRom .
cheers

Braddison said:
@nelvinchi brilliant ! i've came from an galaxy s3 running slim rom and been looking for a superslim rom since gettin a one mini (as we are restricted with storage space).i hope tr1gg3r84 uploads the rom this weekend.
Re: S-off... i have no issues with s-off at the moment(no boot loops etc).will find out if i run in to difficulty when i flash the new MagioRom .
cheers
Click to expand...
Click to collapse
You are s-off - you'll be fine with this as it doesn't require a fastboot flash of the boot.img, so no bootloader unlocking/relocking necessary....
Can I ask (just out of curiosity):
If you are LOCKED/UNLOCKED
hboot version
SuperCID
Current ROM and recovery
Thanks!

cool.
S-off unlocked (used ramrunner not revone)
hboot- 2.19.00
supercid- no
rom- stock sense 5.5 4.3 deodex by tr1gg3r84
recovery- twrp not cwm
i did run into a few issues throughout the whole process to be honest though...After running superwipe it deleted everything,even the rom i was going to flash on sd.
i had to push rom to phone but it failed to flash. i then had to push rom and supersu to /data/local, then rom flashed from there but
couldnt find the md5 but it has worked without any issue since (you had helped me out by this point,thanks again)
cheers

I've just discovered that if you have hboot version 2.21 you will NOT need to re-lock your bootloader to prevent boot loops after going S-Off. However, in order to update your hboot to 2.21, you have to go S-off first, LOL. Just know that you won't be able to boot to anything other than recovery or fastboot until you update your hboot to 2.21. Hope this helps someone some day

Hum...
If i'm :
HBOOT 2.19
S-OFF
SUPERCID
Bootloader unlocked with htcdev
Root
On the stock 4.2.2 rom after purchase
I can't flash the stock rom of tr1gg3r84 or i may brick or have boot loops ?

@PuffDaddy_d Hey im currently S-off, unlocked bootloader ,hboot- 2.19.00 . never had any issues with bootloops no matter what rom I've tried. never had to flash the boot.img via fastboot either!
i take it that you mean we have to update our hboot for tr1gg3r84s new stock 4.4.2 rom or we will face bootloops ??
cheers

Braddison said:
@PuffDaddy_d Hey im currently S-off, unlocked bootloader ,hboot- 2.19.00 . never had any issues with bootloops no matter what rom I've tried. never had to flash the boot.img via fastboot either!
i take it that you mean we have to update our hboot for tr1gg3r84s new stock 4.4.2 rom or we will face bootloops ??
cheers
Click to expand...
Click to collapse
You might be right - I didn't go S-Off until I tried the new 4.4.2 Rom, so it very well could've worked with previous versions.

For the "boot loop city" you refer to while being s-off and unlocked. remove the file /system/bin/hcheck. It will fix that problem. No need to relock and unlock all the time
And why can you NOT go back S-ON?
And the write protection is in kernel and has nothing to do with S-OFF. Well, actually, kernel checks status of S-OFF/S-ON. If its on then don't allow system edits. If it is OFF then allow system edits. You can be s-on with a modified kernel and make changes to system

Database Info

welcome