Related
There are many steps to returning to stock if i don't decide to use PD15IMG, i really just want some security and clarity on this.
Can someone help me understand how to do the following things-
1.Turn S-ON
2.replace clockwork with stock recovery
I used the visionary method, so unrooting is as simple as clicking unroot in the app.
I'm just confused about how to do the listed things.
The reason i don't want to use pd15img is because i'd rather not go through installing all of my apps and whatnot.
Also important- I want to know if there is a certain order in which to do these things to minimize risk? an example would be (Not coming from any prior knowledge about this, just something that sounds like it could be realistic) booting a rooted rom on hboot with S-ON - would it be incompatible for some reason?
I hope i make sense here, I just want to know that if i ever have the urge to revert to stock, i can without erasing all of the stuff on my phone.
I suppose you could also tell me these things about pd15img-
1. will it turn s-on?
2. will recovery be stock?
3. will i still be rooted?
4. will i be restored to hboot 0.86?
5. are there any dangers involved if i use it properly through hboot?
I'm sort of asking for a lot of information here I suppose, but answering as much as you can of it would be incredibly helpful. thanks in advance.
Ok, I do not think you can go back to s=on and such w/out it basically doing a factory reset. What is your current ROM? Is it Gingerbread or Froyo? If you have google backup then your apps should be fine, it will just take some time to restore them once you are back up and running again.
Also, check out this thread http://forum.xda-developers.com/showthread.php?t=863899
Look in the development section... there are multiple threads explaining what you want to do with step by step instructions.
Sent from my HTC Glacier using XDA App
I used HTC's official unlock and my phone is unlocked, but has S-On. Is there a benefit to S-Off now that mine is unlocked? What is the difference between how the unlocks are? Sorry if i'm not making much sense, I'm new to this place and Android in general... I just got my sensation last week.
Welcome to Sensation
Don't worry, everyone's a noob at some point, I'm pretty much still a noob myself but as far as I understand it:
To this point you have unlocked your bootloader which simply allows the phone to boot with third-party software installed. In your phone there is a form of security check and the level of security is determined by whether you are S-ON or S-OFF. It's a flag at the radio level of your phone that checks images before they are allowed to be written to the system memory. So when you gain S-OFF, you gain unrestricted access to the NAND flash memory on your device, also known as root. With S-ON you can get temporary root but it's not guaranteed, with S-OFF you can get permanent root no matter what you flash.
Essentially gaining S-OFF permits superuser access to the phone, giving you control over all aspects of software and hardware.
If you like your phone the way it comes to you, all filled up with bloatware and stuck using only the latest version of Android that your carrier releases OTA, with a boring/crappy splash screen and boot animation (and so on and so forth ) then you have no real reason to get S-OFF.
If however you have seen some of the shiny ROMs put together by the devs here at XDA, or have a sweet custom splash screen you'd love to see every time you boot up the phone, or just like the idea of having complete control over YOUR phone and flashing what-the-hell-ever ROM/firmware/radio/other stuff you damn well please, then you should definitely consider rooting.
The disclaimer to all this is that if you aren't careful and don't thoroughly research what you're doing BEFORE you do it, you could brick your phone and give yourself some serious grief. The fact you're even asking this now is a point in your favour, there are far too many 'help me' posts on here from people who did something without bothering to try and understand it first. Knowledge is power and there's buckets of knowledge on this forum and others.
I'd suggest reading here and here at the very least.
Hope that helps
s-off means you may do anything with your phone,
you will lose warrenty at s-off gain it at s-on
as the other guy said if u want a nice toutch to your rom s-off it and install, if u want it still legal dont
Thanks for the info. I've been considering using an ICS OTA file on my HTC Sensation 4G, but the guides i've seen only mention S-OFF and nothing about the unlocked S-ON. I just can't wait for the official release!
On the other hand though, I also want to remove bloatware from this phone and found a script for such... but i can't seem to get any temp root method working. I'm not ready to jump off the deep end yet, but i'm tired of the unnecessary stuff.
I also couldn't wait for the official ICS release so I s-off, rooted, super CID, and flashed an ICS firmware and went to android revolution. Honestly, it's one of the best decisions Ive ever made. If you think your stock phone is running good right now, you'll be amazed when you flash it, it will run absolutely faster I tell you.
Though there are alot of risks doing all of that, it might brick your phone completely. So be very careful, read and understand everything if you're going to do all of those stuff.
Sent from revolutionized HTC Sensation ICS
HTC sensation stuck at boot
Hey Guys Noob here,
I need help big time. I gone and mess with something I shouldn't have. I'm a first time android/touch screen user so bear with me.
I was trying to S-off my phone (alrady rooted- after several tries) but I downloaded the juopunutbear zip file on my phone. I mistakenly loaded it via the CWM recovery and now the screen is stuck on that juopunutbear image.
I have tried to flash my rom because I thought it was just a boot loop, but nothing happened. I NEED some advice please don't tell me I bricked it. :crying:
man+droid said:
Hey Guys Noob here,
I need help big time. I gone and mess with something I shouldn't have. I'm a first time android/touch screen user so bear with me.
I was trying to S-off my phone (alrady rooted- after several tries) but I downloaded the juopunutbear zip file on my phone. I mistakenly loaded it via the CWM recovery and now the screen is stuck on that juopunutbear image.
I have tried to flash my rom because I thought it was just a boot loop, but nothing happened. I NEED some advice please don't tell me I bricked it. :crying:
Click to expand...
Click to collapse
if you can boot into bootloader then you are not bricked
secondly what do you mean by juopunutbear.zip and from where?
edit:you said that you are already rooted
which means that you have unlocked bootloader from htcdev site am i right?
Yes it was already unlock from HTC dev, but I was trying to get S- off using the wire trick method. In reading the Jounutbear guide thread it directed u to a link which has the zip file which I should have run on my pc but I had mistakenly installed it from my sd card and now it isn't going furthuer than that screen. I now can't using the Jbear exe bcuz it not recogining it.
I don't really want to keep adding my nonsense to the thread how can I PM someone for help.
man+droid said:
Yes it was already unlock from HTC dev, but I was trying to get S- off using the wire trick method. In reading the Jounutbear guide thread it directed u to a link which has the zip file which I should have run on my pc but I had mistakenly installed it from my sd card and now it isn't going furthuer than that screen. I now can't using the Jbear exe bcuz it not recogining it.
I don't really want to keep adding my nonsense to the thread how can I PM someone for help.
Click to expand...
Click to collapse
do this
install 4ext recovery
enable smartflash from it
flash the rom
http://forum.xda-developers.com/showthread.php?t=1631861
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
man+droid said:
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
Click to expand...
Click to collapse
that's weird
did you perform a full wipe(from recovery) before flashing the rom?
also as long as you are on S-ON use 4ext recovery to flash the rom
and before flashing the rom enable smartflash from 4ext
if you have done all the above then use a ruu.exe to return to stock condition
http://forum.xda-developers.com/showthread.php?t=1672425
Well that thread seems to be a mouth full remember I'm a noob. But I will try and read that again to get what it really says. It seems though that it was a complex instruction how to get back to the stock rom? Isn't there a file for that I can download. I get to doing that RUU thing to see if it works tho
man+droid said:
Well that thread seems to be a mouth full remember I'm a noob. But I will try and read that again to get what it really says. It seems though that it was a complex instruction how to get back to the stock rom? Isn't there a file for that I can download. I get to doing that RUU thing to see if it works tho
Click to expand...
Click to collapse
i saw your post in the other thread
you managed to install 4ext
now try to flash a custom rom
before flashing the rom enable smartflash from 4ext
Hey guys good news
I finally got the phone to power on. I saw this thread that highlead my pro http://forum.xda-developers.com/showthread.php?t=2284273 but I was really got the details from another forum. I don't know if I'm allowed to post it so I won't, but I'll sum it up.
All I need to do was flash the boot image on my current rom (get this from the zip file) and also flash the recovery image from a backup I had and presto.
But I'll go and follow you guys instruction about enabling the 4ext smart flash from now on. What I want to know though is for some custom roms (eg cyanogenmod 10.1) do I needs to be S-off to install it?
If so I'm still gonna try and S-off this here thingy. Givethanks y'all
man+droid said:
Hey guys good news
I finally got the phone to power on. I saw this thread that highlead my pro http://forum.xda-developers.com/showthread.php?t=2284273 but I was really got the details from another forum. I don't know if I'm allowed to post it so I won't, but I'll sum it up.
All I need to do was flash the boot image on my current rom (get this from the zip file) and also flash the recovery image from a backup I had and presto.
But I'll go and follow you guys instruction about enabling the 4ext smart flash from now on. What I want to know though is for some custom roms (eg cyanogenmod 10.1) do I needs to be S-off to install it?
If so I'm still gonna try and S-off this here thingy. Givethanks y'all
Click to expand...
Click to collapse
any ICS/JB rom you can install via enabling smartflash in 4EXT before flashing the ROM
ganeshp said:
any ICS/JB rom you can install via enabling smartflash in 4EXT before flashing the ROM
Click to expand...
Click to collapse
Hey thanx for the heads up. So I'm finally s-off using the J-bear method but where unlocked use to be I'm now seeing the juopunutbear there so I got back into android but it was the old CWM that was on it how do I get back the 4ext and would that be a prob if that J name remains there tho?
man+droid said:
Hey thanx for the heads up. So I'm finally s-off using the J-bear method but where unlocked use to be I'm now seeing the juopunutbear there so I got back into android but it was the old CWM that was on it how do I get back the 4ext and would that be a prob if that J name remains there tho?
Click to expand...
Click to collapse
no you are fine now
there is no problem with juopunutbear because now you have patched hboot which is unlocked
you are fine also with cwm recovery
but if you still want 4ext do only step 2 from here
http://forum.xda-developers.com/showthread.php?t=1631861
man+droid said:
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
Click to expand...
Click to collapse
might be a bad dl. Download it again and reflash or try a different rom.
Hello Guys.... M really new to XDA as well as HTC devices.... had a Sony and a Samsung before... Seems HTC is entirely different!
i just needed some expertise on following questions i had in my mind:
1) i have bought an HTC one xl (snapdragon version) that is unlocked.. will a "FACTORY DATA RESET" or flashing of a custom rom lock it again??
(does this phone need to have an unlocked bootloader)
2) what is the best and most secure way to root it? (link to any guides will be much appreciated)
3) things that can possibly brick the phone and i should AVOID?
4) the best custom rom in terms of speed?
5) any necessary mods for stock rom?
PLEASE i neeed some help!
You need to find the correct root method for your current hboot. If your phone is the at&t model, click the link in my signature, then find the right root method for you. If it's not, just go to htcdev.com and unlock your bootloader, then you can flash TWRP recovery, and flash a custom ROM.
Sent from my Evita
1)Factory data reset in bootloader just clears the /data partition but does not function correctly at all if you unlock the bootloader for this device.
The only way to relock the bootloader is to do fastboot oem lock
2)As timmaaa said, follow the index. You want to unlock bootloader, flash ROM with root, get supercid, s-off.
The catches are:
AT&T devices need to gain temp root to get supercid before they can unlock bootloader.
Newer HTC updates eg new 3.17 and 5.xx updates may prevent you from getting supercid even with root, you may need to investigate downgrading things to get supercid.
With an unlocked bootloader, you are well on your way. You should check if you have supercid and if you are s-off.
3)Do not attempt to install HTC updates after you modify the phone. OTA is particular can be dangerous but even RUU's can be dangerous under some circumstances. OTA have many rules which are easy to follow once you have an idea of what they do, best bet is to just ignore them, RUU is fine if you have both s-off and supercid.
4)You can not ask that question and we can not answer it. It is unfair for someone to rate ROM's over other ROMs as the devs put a lot of effort in to these things. Each ROM is special in its own way, you need to check them out yourself.
A typical vibe is HTC stock ROMs will typically give the most reliable experience, eg less crashes, less bugs, etc, but tend to also lack features.
Unlocking your phone and modding it requires you to read and understand what you are getting yourself in to. It is not a perfect smooth ride, it is not for the average "non technical" user.
5)Not really
twistedddx said:
1)Factory data reset in bootloader just clears the /data partition but does not function correctly at all if you unlock the bootloader for this device.
The only way to relock the bootloader is to do fastboot oem lock
2)As timmaaa said, follow the index. You want to unlock bootloader, flash ROM with root, get supercid, s-off.
The catches are:
AT&T devices need to gain temp root to get supercid before they can unlock bootloader.
Newer HTC updates eg new 3.17 and 5.xx updates may prevent you from getting supercid even with root, you may need to investigate downgrading things to get supercid.
With an unlocked bootloader, you are well on your way. You should check if you have supercid and if you are s-off.
3)Do not attempt to install HTC updates after you modify the phone. OTA is particular can be dangerous but even RUU's can be dangerous under some circumstances. OTA have many rules which are easy to follow once you have an idea of what they do, best bet is to just ignore them, RUU is fine if you have both s-off and supercid.
4)You can not ask that question and we can not answer it. It is unfair for someone to rate ROM's over other ROMs as the devs put a lot of effort in to these things. Each ROM is special in its own way, you need to check them out yourself.
A typical vibe is HTC stock ROMs will typically give the most reliable experience, eg less crashes, less bugs, etc, but tend to also lack features.
Unlocking your phone and modding it requires you to read and understand what you are getting yourself in to. It is not a perfect smooth ride, it is not for the average "non technical" user.
5)Not really
Click to expand...
Click to collapse
thanks a lot man....
i appreciate since u elaborated on every aspect...!! =)
btw m sorry if i am wrong but what i meant in my first question was does rooting or a reset or flashing affect the "sim unlock" (or the factory unlock or jailbreak)? [the vendor says its unlocked to work on all networks]
besides you are right i was wrong with the approach.. every developer puts in a lot of efforts in ROM development and its not fair to rate it!
the only reason i would possibly root is to remove bloatware.
and rvhaval
timmaaa said:
You need to find the correct root method for your current hboot. If your phone is the at&t model, click the link in my signature, then find the right root method for you. If it's not, just go to htcdev.com and unlock your bootloader, then you can flash TWRP recovery, and flash a custom ROM.
Sent from my Evita
Click to expand...
Click to collapse
thanks i will surely go through that!
the thing that actually haunts me is this phone doesn't have a removable battery so if anything goes wrong and i have some boot loops i would be in a very hopeless situation.. So I need to go through everything!
Sonone said:
thanks i will surely go through that!
the thing that actually haunts me is this phone doesn't have a removable battery so if anything goes wrong and i have some boot loops i would be in a very hopeless situation.. So I need to go through everything!
Click to expand...
Click to collapse
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Sim unlock is unrelated to bootloader unlock, ROM flashing, etc etc.
The sim unlock should survive most everything you will do. Although I have not tested as my device was never locked.
thanks!! i hope it survives!
timmaaa said:
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
that sounds good!!
the people on this device forum seem very helpful:good::angel::highfive:
timmaaa said:
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
that sounds good!!
the people on this device forum seem very helpful:good::angel::highfive:
so Timaaaa i have done the following...
please i would like to give you a brief update of the following things..
1)Unlocked Bootloader
2)i have s-off
3)supercid is 11111111
4) installed twrp version 6.xx.xxx
5)my radio is 1.30a.32.45.18
6)hboot is 2.15.0000
7)device is now rooted
so m i good to flash custom roms like Cm,PAC,SLIM?
That all looks fine apart from two things.
The TWRP version you mentioned doesn't look right, the latest TWRP is 2.6.3, could you double check that?
Also, your hboot is 2.15 which will be ok for flashing cm, but I think PAC still has a restriction to hboot 2.14 and I'm not sure about Slim. Hboot 2.15 is perfect for running the latest Sense 5 ROMs though.
Sent from my Evita
timmaaa said:
That all looks fine apart from two things.
The TWRP version you mentioned doesn't look right, the latest TWRP is 2.6.3, could you double check that?
Also, your hboot is 2.15 which will be ok for flashing cm, but I think PAC still has a restriction to hboot 2.14 and I'm not sure about Slim. Hboot 2.15 is perfect for running the latest Sense 5 ROMs though.
Sent from my Evita
Click to expand...
Click to collapse
As u said i checked again its 2.5.0.0 how to update twrp?
it actually works well......
btw is it possible to change hboot version?
and thanks as always!
TWRP 2.5 is full of bugs, you should update to at least 2.6, here's how:
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'll have a much better version of TWRP.
You can upgrade and downgrade your hboot, there's a thread on our forum somewhere but I can't remember where, just search downgrade hboot within our forum and it should appear.
Sent from my Evita
did that... btw when i installed it... and tried to clear the cache partition and dalvik cache it said it "failed"...!!
Btw also i wanted to know..
since i had a Samsung before flashing a rom just meant copying the zip file and installing it through cwm followed by a resets (if needed)
is this the same way for HTC ONE xl. or like Sony do i have to first unzip the downloaded rom.. and flash the "boot.img" separately??
So even after putting TWRP 2.6 on your phone you get a failed message when trying to wipe?
With this phone all you need to do is copy the ROM zip onto the phone and install it, you are s-off so you don't need to worry about flashing the boot.img via fastboot.
Sent from my Evita
i tried it again mate and it works absolutely fine!
yay!!!! :laugh: flashing roms will be great!:good:
wish if we had a dual boot interface like we have on our computers installing every single app again becomes so inconvenient!:fingers-crossed:
btw m really sorry to bombard you with all the quetions:silly: i just needed to ask one thing that do we have a list of bloatware apps which are safe to remove..
i did google it but then it was very specific to carrier bloatware. as i have got an unlocked version there are no carrier bloatware apps but i do have some apps which seem useless at the moment.. i did freeze a few... but it would have helped if there would have been a list!
I'd love a dual boot setup too. In terms of bloatware, you can remove a fair bit but be careful while doing it. Removing anything that is integral to the running of the ROM will cause problems. Things like Stocks, Picasa, Talkback can be removed if you don't use them. Obviously don't remove anything like Phone or Messages lol.
Sent from my Evita
timmaaa said:
I'd love a dual boot setup too. In terms of bloatware, you can remove a fair bit but be careful while doing it. Removing anything that is integral to the running of the ROM will cause problems. Things like Stocks, Picasa, Talkback can be removed if you don't use them. Obviously don't remove anything like Phone or Messages lol.
Sent from my Evita
Click to expand...
Click to collapse
ya i wont ripp off phone or system ui etc :laugh:
m thinking of flashing clean rom 7.0.1 but den it seems it has an at&t bootscreen or something like that during start up which m not very inclined to have....
so i will stick to the rules not asking for any advice on which rom is preffered as every one of dem i great and i will check them out one by one.
I haven't tried the new Cleamrom, it's a very stock kind of ROM which isn't really my flavour but it's a very popular ROM.
Sent from my Evita
I have a one SV on cricket (US)
K2_PLC_CL (s-on) still
Ok so it was all stock from store. Tan I did this in order:
1.) Unlocked bootloader from HTC dev...
2.) (flashed) Installed CMW v6.0.2.8 via ADB
3.) MADE BACKUP with CWM
4.) Rooted by flashing a zip via CMW (worked great)
5.) tried moonshine.io for s-off tried twice. Failed
-program (distiller) closed after saying "moonshining 1...2...3...to 10)
-now on boot it gets to "Htc
I booted into CMW and retored that backup i had before any rooting or s-off etc... but it still hangs :silly:
Should I try the hboot option to restore? (I thought CMW backup was like a complete nand backup. Which should be bullet proof right?)
Thanks for looking guys! I have no communication as of now I just want to make calls at least
This is my first android device and I always like getting to know my devices from the inside, the iphone BS was too much haha. I gues i dont really need s off or super cid if it means no phone. but why not if it works.
Did you have ICS or JB, when you have tried S-off?
Please remember, as long as you are S-on you must flash the boot.img with fastboot commands (also, if you are restoring a backup and you did a full wipe)! If you have a cwm backup, boot.img should be inside of your backup folder.
Did you wipe everything before your restore? Maybe fragments of moonshine still there.
Did you try TWRP recovery?
[HTC oneSV boot hang, FIXED] THANKS!!
LOL I had no idea the boot.img had to to be manually flashed, thank you very much it work s great now!
This time I cleared/wiped data AND cache. it still hanged and wont boot. Than I re tried using CWM again to restore (still hangs). than I flashed boot.img THAT DID THE TRICK after "fastboot reboot".
BTW major fail on my part; I was rooting and moonshining for JB it turns out I have ICS (i forgot to update) now that you mentioned it hehehe
I had 4.0.4 sense 4.1. I think that is why everything went to hell...
Alright Ill try moonshine after the update to JB 4.1.2 if that fails than Ill try the facepalm.
One last question; if i do update to JB 4.1.2 and achieve s-off could I use that CMW backup to always go back to ICS 4.0.4? (just incase I ever wanted to get SUPER CID and get JB 4.2.2) I wonder if super cid works with k2-PLC-cl.... Ill try it when I get find the funds a better phone to risk a brick
-Thank you sir!
Ok, lets bring a bit light into these darkness:
- Facepalm S-Off only works, as long as you did not achieve the JB update!
- You can restore a ics cwm backup, also when you are on JB and S-Off, but
- Restoring ics from a backup is not the same, as you where on ics before the update.
Thats because of the updated hboot (ics-> hboot 1.0; jb-> hboot 2.0). In hboot 2.0 the Supercid/Facepalm exploit is fixed. You can still get Supercid under hboot 2.0, but you must do moonshine S-Off before.
So, at all you must think about, what you want and whats the best way to get, before updating to jb.
If this was to difficult to understand, ask again and i will try my best to explain it for you to understand.
Ok
Hum they creators of these phones really enjoy making puzzles for us don't they...
Alright so my options are:
1.) [stay on ICS]
-get super cid
-facepalm for s-off
(can I still update to JB after this and still have super cid and s-off? But that would install hbot2 wouldnt it? so....)
I think I want method 2↓
2.) [update to JB]
-use moonshine to get s-off
-some how get super cid? (I dont really need super cid but it would be nice to know I have it just in case)
-profit
//edit//(ohh yes, once on JB hboot v2, if i have s off and on hboot2 could I go back to hboot1 along with ICS should i need to)
Any ways thank you again
1. Right, you can update and both will stay.
2. Right, after S-Off you should be able to change SuperCid. But it should be said, that its a very risky operation and phone can be bricked very easily if you are doing something wrong.
And for your edit: You can restore a ics backup, but without a RUU it is difficult to bring back hboot 1. Only a backup of it will solve this. Recoveries usually don't backup hboot.
SV ICS super cid
I know this thread : http://forum.xda-developers.com/showthread.php?t=2264322
says to do super cid on original stock, but could I just go ahead and HEX my cid with my ICS that is unlocked/rooted/custom-recovery?
Do I have to un-do all of that to change the CID? or is that just good technique? [im also on cricket ics 4.0.4 if it matters, k2_plc_cl]
Thank you very much! I wish to change my cid right now but ill wait and see what you say if it saves me from a brick
than I'm off to s-off for all the goodies that follow haha.
I don't think, that this will be important, because SuperCid is located in a partition which has nothing to do with root or recovery.
alrighty than
haha wrong link in previous post I meant this one: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
WHEN HTCDEV UNLOCKS YOUR DEVICE YOU MUST START FROM SCRATCH!!!
Click to expand...
Click to collapse
I was reading his link and somehow posted your link, Ill use your link actually now that I read it... I thought it wouldn't matter, better safe than sorry. Ill try it out and see how it goes.
Thanks for helping
Questions about hexing CID
old.splatterhand said:
I don't think, that this will be important, because SuperCid is located in a partition which has nothing to do with root or recovery.
Click to expand...
Click to collapse
Alright its late and I'm not going to flash it yet ill wait to see what you make of this:
I have used hxd many times for xbox/psp/etc so i know how it works... it found 3 instances of my CID
(some info omitted as the 'x' char)
Code:
maincid=CRICK001xx.xx.cidlist=CRICK001.xx.xx.rid=105.xx.xx.modelid=PL8xxxxxx.xx.xx.report=com.xx.xx.skulist=1xxx.xx.xx.taskid=30xxxx.xx.xx.mainsku=1xxx.xx.onecid=1.xx.cwkey=CRICK001.ro.com.google.clientidbase=android-htc //more stuff after........
Im assuming only the first instance "maincid=CRICK001" needs to be 11111111
(or should all 3 instances of "CRICK001" be changed to 11111111)
Ill give it a go after work tomorrow when Im confident that my modifications wont render my phone as a door stop.
I need to buy you a beer, but the donation is in german, ill have to translate it when I get done
Gain_Medium said:
Alright its late and I'm not going to flash it yet ill wait to see what you make of this:
I have used hxd many times for xbox/psp/etc so i know how it works... it found 3 instances of my CID
(some info omitted as the 'x' char)
Code:
maincid=CRICK001xx.xx.cidlist=CRICK001.xx.xx.rid=105.xx.xx.modelid=PL8xxxxxx.xx.xx.report=com.xx.xx.skulist=1xxx.xx.xx.taskid=30xxxx.xx.xx.mainsku=1xxx.xx.onecid=1.xx.cwkey=CRICK001.ro.com.google.clientidbase=android-htc //more stuff after........
Im assuming only the first instance "maincid=CRICK001" needs to be 11111111
(or should all 3 instances of "CRICK001" be changed to 11111111)
Ill give it a go after work tomorrow when Im confident that my modifications wont render my phone as a door stop.
I need to buy you a beer, but the donation is in german, ill have to translate it when I get done
Click to expand...
Click to collapse
At this point i only can tell you about my guide and the picture inside. To be honest, i only noticed only one cid, together with imei. So maybe this helps you.
Edit:
Please, really be careful if your file/block is different than in my guide!
I'm on mobile and can't look at your code completely.
My guide for sure works for k2u & k2ul cause i did it myself at two different phones but i don't know, if cricket has changed more and i don't want your phone bricked.
Edit2:
I really not sure, if changing CID will work. Maybe you'll try the S-Off step by Moonshine after update to JB, would be better than a bricked phone!
You must also think, what do i profit from SuperCID?
K2u & k2ul can be unbranded this way, maybe they also profit from earlier updates.
But you can't use k2u/l Software on US phones, different network, so this point is useless for you. And i don't think, cricket will release their updates earlier for phones with SuperCID.
Just my two cents, now its on you to make your decision...
What i also want to say, i had help the first time i did.
It was @jmz who helped me, maybe he reads that and know more about cricket cid.
I think ill give it a go
I actually tried to contact him and others, but since im so new I can't send PMs (they send but nothing is in my sent box. link it never happened) so I guess unless JMZ stumbles upon this thread thats it.
As for me I don't think it would brick my phone (like a real brick) if all else I could just boot into recovery and flash back my backup stuff right?
Or if i screw up would it not even allow recovery / shell? Although a brick would permit me to buy a better popular phone
If i try it all post more details on it for other cricket users.
This is modifying the bootloader. If you do something wrong, the phone wont boot. Not in recovery, not in OS, bricked.
PS. @Gain_Medium
If you write a xda username with an @ before, the one will be notified, the he is mentioned somewhere
Side note: I don't believe that there is any reason for super cid on a cricket us carrier, unless you plan on traveling to Europe, Asia, or anywhere out of the continent.
Yes, it's cool to have accomplished superCID. But there is really no benefit here in the US, if you plan on maybe using a different service plan provider, you'll still need to unlock your SIM, even if you do achieve superCID without bricking.
Good luck with your decision. I hope to read your updates on what you have chosen. And how everything goes for you.
THESE ARE ONLY MY THOUGHTS AND OPINIONS. NOT TRYING TO SWAY YOU AWAY FROM ATTEMPTING ANYTHING.
but please research superCID for cricket mobile and see what you find.
Pros vs Cons
Hello,
I am trying to update my phone without losing all of my data and of coarse, root as well. Below is what I am working with:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Recovery TWRP v2.6.3.0
Android Version 4.0.4
Sense 4.0
software # 2.20.502.7.710RD
API Level 4.23
HTC extension 403_1_GA_20
Kernel 3.0.8-01558-g7f75e5b
baseband 0.19as
build 2.20.502.7
That's probably way more than you needed to know, but I like to be through. (c;
anyhow, I want to update everything to the latest version... firmware, hboot (if applicable), OS, radio, etc. without losing my data, recovery or root.
I have downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from HTC
and OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip from my phone.
I tried upgrading using adb sideload (renaming zip from carrier to update.zip) and it failed
I tried upgrading using install feature of TWRP using update.zip and it failed
I then thought I will just extract the .img files and flash using adb, but quickly discovered I don't know what .img file is which. If some one has a better way of accomplishing my goal i am all ears, however if someone can assist in identifying which .img files i should flash and how to best approach it I would be very appreciative.
the files extracted are attached (didn't want to flood the post)
It's better to provide too much information than not enough, which is what most people do lol.
I think you're a bit misguided on the whole process so I'll break it down for you. You've downloaded the right RUU but you don't need the OTA. You're also approaching it with the wrong methodology, you're not meant to extract the RUU and flash any image files manually. All you need to do is connect your phone to your PC in fastboot mode and run the RUU exe program in Windows then follow the prompts. You must get s-off first though, very important, do not skip this step!
You will lose your custom recovery and root, there's no way around that. But getting them back is as easy as flashing the custom recovery again and installing root or a rooted ROM. The RUU shouldn't wipe anything from your sd card but it's a good idea to make a backup just in case. You'll lose text messages, call logs, things like that but you can back those up using backup apps before the process.
So head over to the Rumrunner site and get s-off first and you'll be good to go.
Sent from my Evita
timmaaa said:
It's better to provide too much information than not enough, which is what most people do lol.
I think you're a bit misguided on the whole process so I'll break it down for you. You've downloaded the right RUU but you don't need the OTA. You're also approaching it with the wrong methodology, you're not meant to extract the RUU and flash any image files manually. All you need to do is connect your phone to your PC in fastboot mode and run the RUU exe program in Windows then follow the prompts. You must get s-off first though, very important, do not skip this step!
You will lose your custom recovery and root, there's no way around that. But getting them back is as easy as flashing the custom recovery again and installing root or a rooted ROM. The RUU shouldn't wipe anything from your sd card but it's a good idea to make a backup just in case. You'll lose text messages, call logs, things like that but you can back those up using backup apps before the process.
So head over to the Rumrunner site and get s-off first and you'll be good to go.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the response!
I figured I didn't need both the ruu and the ota, but I didn't know if one had newer componets than the other. Also, I didn't know that s-off had been accomplished, last I checked it was still unavailable.
The reason I was thinking of flashing the images manually was because it was so simple for the nexus 7 upgrade, and prevented data loss. The ruu says data loss will happen on it, so I was skeptical to run it as is. So now I am off to check out that link and get this party started! Thanks again!
Spy_64 said:
Hello,
I am trying to update my phone without losing all of my data and of coarse, root as well. Below is what I am working with:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Recovery TWRP v2.6.3.0
Android Version 4.0.4
Sense 4.0
software # 2.20.502.7.710RD
API Level 4.23
HTC extension 403_1_GA_20
Kernel 3.0.8-01558-g7f75e5b
baseband 0.19as
build 2.20.502.7
That's probably way more than you needed to know, but I like to be through. (c;
anyhow, I want to update everything to the latest version... firmware, hboot (if applicable), OS, radio, etc. without losing my data, recovery or root.
I have downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from HTC
and OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip from my phone.
I tried upgrading using adb sideload (renaming zip from carrier to update.zip) and it failed
I tried upgrading using install feature of TWRP using update.zip and it failed
I then thought I will just extract the .img files and flash using adb, but quickly discovered I don't know what .img file is which. If some one has a better way of accomplishing my goal i am all ears, however if someone can assist in identifying which .img files i should flash and how to best approach it I would be very appreciative.
the files extracted are attached (didn't want to flood the post)
Click to expand...
Click to collapse
If you get stuck or need more info, I threw together a guide with info from the forums that may help:
http://forum.xda-developers.com/showthread.php?t=2593037
By the way, tell me about your footer "HTC Evita Gummy 4.4.2 | Torched KK Kernel S-off | 2.14 | Modified TWRP 2.6.3"..... Cooked rom? How do you like it? How does it compare to stock?
Madcat8686 said:
If you get stuck or need more info, I threw together a guide with info from the forums that may help:
http://forum.xda-developers.com/showthread.php?t=2593037
Click to expand...
Click to collapse
Thanks!
Spy_64 said:
By the way, tell me about your footer "HTC Evita Gummy 4.4.2 | Torched KK Kernel S-off | 2.14 | Modified TWRP 2.6.3"..... Cooked rom? How do you like it? How does it compare to stock?
Click to expand...
Click to collapse
It's a really good Rom. Extremely stable with excellent battery life. It's my current "go to" Nandroid back up I use during the day now. I flash new Roms almost daily when I don't need the phone for work. It's based off AOSP and that's what I like most about it. It has tweaks but not too many. For someone making a jump to 4.4+ Roms, I would highly recommend this one as a starter. We are very fortunate to have many like this and I'm getting around too try all of them (we are very lucky to have some talented individuals working Roms in our Forum.)
As for stock, I have to be honest, I can hardly remember what stock is like. I tried most of the stock Roms a few months ago and I have Nandroid backups of them. I remember a few were very stable but as I said, I'm a sucker for pure AOSP.
AHHH shoot, I suppose I just fielded a question meant for Timmaa, my bad!
Madcat8686 said:
It's a really good Rom. Extremely stable with excellent battery life. It's my current "go to" Nandroid back up I use during the day now. I flash new Roms almost daily when I don't need the phone for work. It's based off AOSP and that's what I like most about it. It has tweaks but not too many. For someone making a jump to 4.4+ Roms, I would highly recommend this one as a starter. We are very fortunate to have many like this and I'm getting around too try all of them (we are very lucky to have some talented individuals working Roms in our Forum.)
As for stock, I have to be honest, I can hardly remember what stock is like. I tried most of the stock Roms a few months ago and I have Nandroid backups of them. I remember a few were very stable but as I said, I'm a sucker for pure AOSP.
AHHH shoot, I suppose I just fielded a question meant for Timmaa, my bad!
Click to expand...
Click to collapse
Thanks for the insight. (c; Know of any place i can see screenshots or more info? better battery life is very important to me. I have been steering clear of aftermarket rom's because it always seems that there is always one thing or another that doesn't work... and it always seems to be either or a combination of, tethering, GPS, MMS, or wifi, all are rather important to me. (c;
Spy_64 said:
Thanks for the insight. (c; Know of any place i can see screenshots or more info? better battery life is very important to me. I have been steering clear of aftermarket rom's because it always seems that there is always one thing or another that doesn't work... and it always seems to be either or a combination of, tethering, GPS, MMS, or wifi, all are rather important to me. (c;
Click to expand...
Click to collapse
The Roms are in the development and original development threads. I don't want to steer you down the wrong path and tell you that one Rom is better than another because that's not the XDA way. It implies that one dev's work is better or inferior in some way (plus it's against the rules.)
I can recommend Gummy Rom as a starter if you are ready to try out a custom Rom. I like it and I consider it a daily driver but a couple of the others are just as good. You just have to flash and find out. Many of the 4.4+ Roms on our Forum are stable and work really well.
well I have tried two different PC's running different OS's, and two different USB cables and I cannot get past
....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (11/120)
Waiting
Test 2: Booting device
Waiting for ADB (49/120)
Device detected.....................
[TTTT********************************************** **********]
Press ENTER to exit
Click to expand...
Click to collapse
when running rumrunner. I cannot seem to find anything out there that fixes it either )c;
Any thoughts?
Sometimes Rumrunner says it's failed but it has actually worked, does it still at s-on in your bootloader?
Sent from my Evita
timmaaa said:
Sometimes Rumrunner says it's failed but it has actually worked, does it still at s-on in your bootloader?
Sent from my Evita
Click to expand...
Click to collapse
Yah bootloader still says s-on. )c;
It's possible that it's the ROM/kernel that's the problem. You might consider flashing the latest MagioRom, I've had confirmed reports of success with that ROM.
Sent from my Evita
timmaaa said:
It's possible that it's the ROM/kernel that's the problem. You might consider flashing the latest MagioRom, I've had confirmed reports of success with that ROM.
Sent from my Evita
Click to expand...
Click to collapse
Wont I lose all my data doing so?
What do you mean by data? If you mean your images, music and such on your sd card, no you won't lose it. You never lose that when changing ROMs, I've flash multiple ROMs every week for the last few years and I've never once lost that data in all this hundreds of flashes.
You will lose your text messages, call logs, apps, stuff like that, but you can use several apps to back those up before you flash and then restore it afterwards. Do you use Titanium Backup? If not I suggest you look into it, it allows you to backup pretty much everything.
Sent from my Evita
timmaaa said:
What do you mean by data? If you mean your images, music and such on your sd card, no you won't lose it. You never lose that when changing ROMs, I've flash multiple ROMs every week for the last few years and I've never once lost that data in all this hundreds of flashes.
You will lose your text messages, call logs, apps, stuff like that, but you can use several apps to back those up before you flash and then restore it afterwards. Do you use Titanium Backup? If not I suggest you look into it, it allows you to backup pretty much everything.
Sent from my Evita
Click to expand...
Click to collapse
Mainly just, well data and apps...stored on sd or internal storage. That's great news though!
No problems. The rule of thumb is this: if it's worth worrying about it's worth backing up, just in case.
Sent from my Evita
I was going to backup using twrp to USB and an OTG cable but apparently that is not implemented in this kernel... so now its onwards to titanium backup... i haven't tried it for a few years now.
another question.... the romrunner page has modified hboots for htc one....does that include onex? could I use it once i get this all sorted out?
No. You don't want to use a modified hboot. Also, in TWRP recovery you can use the mount usb storage feature so your internal storage shows up on your PC and you can backup that way.
Sent from my Evita