Related
ok i need help,i install PA over stock rom on 2.2 firmare,before flashing i maked a nandroid backup,i wanted to sell the phone and wanted to back to stock rom,BUT im stuck at boot loop htc screen because while i flash Pa i flash a PA boot img so i cant boot now stock rom,what is to best advice to back to any rom,can i flash somehow flash boot image of stock rom and where can find that boot img,or something else i can do,when i get into twrp recovery i cant do factory reset its failed and i dont have gapps and PA rom on my sd card that files are no more on my sd card i dont know why,so i cant flash PA anymore,need any help asap
if you are selling it reboot into bootloader and run "fastboot oem lock" then run the 2.20 ruu
DvineLord said:
if you are selling it reboot into bootloader and run "fastboot oem lock" then run the 2.20 ruu
Click to expand...
Click to collapse
i will try thanks
vigorito said:
i will try thanks
Click to expand...
Click to collapse
i dont have in bootloader oem lock?
vigorito said:
i dont have in bootloader oem lock?
Click to expand...
Click to collapse
i run the ruu 2.2 (i didnt find the fastboot oem lock) and the ruu start updating the rom and sending about 5 mins and i get error 155 unknown error the rom update utillity cannot cupdate your anddorid phone please get the correct rom update utillity and try again,can i just go to recovery again and do a restore again of stock rom ( nandroid stock) and then just flash boot image from stock rom but i dont know where can find boot image from stock rom?
vigorito said:
i run the ruu 2.2 (i didnt find the fastboot oem lock) and the ruu start updating the rom and sending about 5 mins and i get error 155 unknown error the rom update utillity cannot cupdate your anddorid phone please get the correct rom update utillity and try again,can i just go to recovery again and do a restore again of stock rom ( nandroid stock) and then just flash boot image from stock rom but i dont know where can find boot image from stock rom?
Click to expand...
Click to collapse
Fastboot oem lock
Type into the fastboot cmd prompt while phone is in fastboot. Then run the ruu
Sent from my One X using xda app-developers app
Myrder said:
Fastboot oem lock
Type into the fastboot cmd prompt while phone is in fastboot. Then run the ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
i did it in command promt i get bootloader lock succesfully
then bootloader tz htc svc disable ret and some numbers
and then failed (status read failed) too many links and in bootloader i see its relocked and some security warning
im running ruu now will se whats gonna happen
bro...i hit thanks!
I was actually wondering about the issue of having to flash the boot.img if restoring a TWRP backup. I assumed that it would have to be flashed via fastboot, since boot.img is obviously needed but can't be accessed by recovery on the 1.14 hboot. But haven't seen that discussed or confirmed here. Doesn't actually apply to my One X, since I'm on the old hboot. More just wondering academically.
Seems like the OP has taken the route of running the RUU. But if you ever need the boot.img for a stock ROM, many of the stock ROMs are posted in Development. So you can download the right one, and pull boot.img from it.
Yes you need to flash boot.img when restoring a backup on hboot 1.14.
Sent from my HTC One XL using xda app-developers app
Thanks for the tips guys, I also used this just now to unroot my phone and return it to bone-stock. I used the All-in-one tool to relock the bootloader and got the same error message that OP got, but after rebooting into the bootloader it said Re-Locked. Then downloaded HTC Sync and the 2.20 RUU and ran it. Took 15 minutes total and my phone looks stock, unless of course some busybody at AT&T decides to check the bootloader.
I am returning my One X and buying a One X + tomorrow morning.
EDIT: Oh and in case anyone is confused, you DO NOT need to flash boot.img in order to flash the 2.20 RUU.
i heard people say that they flashed the twrp boot backup in fastboot and it worked the same as flashing the boot from rom.zip in the ruu. i prefer the ruu method for going back to stock, just seems more official imo.
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.
This is for International hTC One XL/Evita - Hboot 2.14 & firmware 3.17 (Orange UK)
If you own AT&T One X please look elsewhere, this guide is not for your phone
There is an abundance of information scattered in these forums and not all root methods/exploits work universally due to variation in firmware builds and Hboots.
I had to read a lot of threads to figure out how to S-off my Orange UK One XL with Hboot 2.14 and firmware build 3.17.
I was only interested in attaining S-off but had to start with HTCDev bootloader unlocking which I didn't really want to do but none of the known root exploits worked on my firmware.
I am sharing this hoping it would help others avoid taking pills for headaches when pursuing this noble quest
AIM:
Provide a short guide to others with similar device and configuration on where to start and simple clear steps to follow with needed links.
PREREQUISITES:
1. latest htc drivers for your Windows PC/laptop if you have one of those. Check here.
2. a working adb environment preferably from latest Android SDK, if you don't have this already set up please check here.
3. "USB debugging" must be checked under Phone settings>Developer options
4. an original htc USB cable is strongly recommended.
5. phone charged at above 50%
6. basic knowledge of using command prompt (cmd) in Windows and adb commands.
STEPS:
So in my case the steps were:
[1] Unlock bootloader through htcdev.com
[2] Flash/install TWRP recovery
This is done manually. All-In-One Toolkit didn't work for me BTW.
1. download latest TWRP recovery for One XL/Evita from here
2. you can rename file for easier command prompt typing later, like TWRP5.img
3. place file recovery file in your adb/fastboot folder
4. connect phone in fastboot mode to PC, make sure it displays fastboot USB on phone before you proceed.
5. start command prompt from within fastboot folder by right clicking inside folder and choosing "open prompt here", type following command:
Code:
C:\yourFastbootFolder> fastboot flash recovery TWRP5.img
Not a bad idea to test your recovery by making a nandroid backup before proceeding to next step.
[3] Flash a custom rom (root)
All custom roms are rooted by definition. If you chose e.g. ViperXL like I did remember to flash boot.img extracted form same rom zip afterwards, otherwise bootloop!
You can of course flash a SuperSU zip instead to gain root but I don't see the point.
[4] SuperCID
This is the simplest way that I found accidentally during my endless searches, all credit goes to @beaups for this one and @Austempest for sharing :good:
1. connect phone to PC in Android mode (mode where you can use phone)
2. Run the following command from command prompt (CMD):
Code:
C:\>adb shell
To enter adb shell, then enter following commands after each other:
Code:
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
3. Reboot to bootloader and hopefully you'll see 11111111 as your CID ...... yes
[5] S-Off
Now that your are rooted with SuperCID you can just follow @beaups simple steps for S-Off found here Facepalm S-Off
That is it.... you broke your shackles :laugh:
I am not a dev and for sure not taking credit for other people's work, merely giving back and hoping this assists clarify stuff and save some time.
Cheers!
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a not in your guide that this guide wont work for at&t phones.
exad said:
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a note in your guide that this guide wont work for at&t phones.
Click to expand...
Click to collapse
Thanks for this important reminder, note added in red on top!
You mentioned one click is only for AT&T phones, I guess you mean All-In-One Toolkit by hason2000, you see even in the tool's thread it's not stated explicitly that tool works only for AT&T, while the respective threads for these exploit state that it's for AT&T One X not negating other international versions!
Most guides/tools are for North America and some Australia but very few for Europe which BTW only recently came on board with 4G/LTE.
So figuring out, especially for noobs, what is what with all these international variations for one device and huge amount of information, while searching doesn't always provide an answer is a tedious task and can end up miserably :crying:
I hope it's in order to add some info for European Evitas
guys kindly don't quote whole post(s), thanks
Only AT&T Phones are different in the case of unlocking/rooting because they can't use HTCDEV. Every other onexl is the same for unlocking/rooting.
Great guide, thanks you! it worked !
Now i'm stuck at the next step. ha :crying:
i cant get root, because my touchscreen not functional after flashed a custom rom. i had success until step 3, i cant proceed to step 4 as i cant use my touches when the rom loaded. i didnt have any back up. i already searched around to dgrade my touchscreen firmware, but it needs root. im stuck here, i can flash custom cwm recovery, install custom rom but cant touch screen. the default cm10.1 dont have android debugging enabled by default, i cant enable it cos i cant touch the screen. if i restore to stock ruu, i can touch screen n all works, but i had a problem sync google contacts.
The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.flashing stock JB RUU is ok. my target now is to s-off n superCID.
i can :
flash RUU 3.17, running a stock RUU 3.17.
unlock bootloader
flash custom recovery(twrp mess with my internal storage)
i cant :
root my device on stock rom
touchscreen wont work on custom rom
any help will b greatly appreciated.
Do not make multiple posts about the same thing. It is strictly against XDA rules.
sorry, may i know how to delete it? i click on edit/delete but cant see any options to delete my post.
You cannot
Sent from my One X using xda app-developers app
sir how to back or normal cid help me
sir how to back or normal cid help me i have a one x its allredy super cid how get back normal cid
Fastboot oem writecid whateveryourcidwas
This will only work once with s-on after supercid but will work as many times as you want if s-off.
Sent from my One X using xda app-developers app
ignore this post. found a relevant thread
How to upgrade bootloader to 2.14
So what if you are not on HBoot 2.14?
EDIT:
Warning: It is not a good idea to upgrade only the bootloader if you intend to flash the latest CM10 builds! Avoiding RUU and unlocking again out of laziness will probably get you in trouble afterwards. RUU is definitely the safer way. You'll find a good collection of ROMs here
http://forum.xda-developers.com/showthread.php?t=2119610
and the tutorial for upgrading RUU on a previously modded phone here
http://forum.xda-developers.com/showthread.php?p=26260005
I found these threads which helped me SuperCID, S-Off and finally upgrade the HBoot of my already rooted evita.
First you need the superCID from this post:
http://forum.xda-developers.com/showthread.php?p=42351491
Next Step S-Off:
http://forum.xda-developers.com/showthread.php?t=2155069
Then RegawMOD the appropriate bootloader from this thread and flash:
http://forum.xda-developers.com/showthread.php?t=1786498
The procedure was easy once I had found the appropriate threads on XDA
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Sent from my HTC One XL using xda app-developers app
New CM10 and derivates require HBoot 2.14
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Click to expand...
Click to collapse
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
ernstlustig said:
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
That's exactly why you should not do it that way. You may get issues along the way as a result of the software not properly utilizing your hardware. This is why you're supposed to update hboot. What you did is more like tricking it into thinking you updated the firmware.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
ernstlustig said:
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
As exad said, CM 10 didnt want you to update just the hboot it wanted you to flash 3.18 RUU or equal to get updated firmware.
The requirement to install 3.18 RUU is listed as a requirement for CM. The hboot is what is checked but things like radio, adsp and wcnss are what actually needed to be updated, which you have not updated.
All you have successfully done is beaten the basic check for if you flashed the 3.18 RUU without actually doing what you were told to do.
How did you get s-off? i have a rogers version
salt204 said:
How did you get s-off? i have a rogers version
Click to expand...
Click to collapse
Links to XDA threads updated. (Sorry.) Please look again.
Has anyone tried successfully to write SuperCID into hboot 2.15 S-On devices?
as the instructions is for hboot 2.14, and I would like to S-Off the device with hboot 2.15 and it is S-On.
I have tried the hex with adb method, but it doesn't work.
Hi everyone, I've yet to successfully load a custom ROM on my ville but I have got s-off and supercid. I'm currently on relocked bootloader running the total stock android 4.1. I'd just like to check through the steps I need to take to try a new 4.4.2 ROM. I was thinking of trying twistedkat.
1. Unlock bootloader (I already have the unlock file from htcdev)
2. Load custom recovery (I have TWRP 2.6.3.0 ready to go)
3. Flash SuperSU
4. Flash Rom file (do I need to unzip or flash the zip file in the recovery?)
5. Flash 4.4 Gapps
Any other steps I've missed? I'm on hboot 2.15, kernel 3.14 from the stock updater.
Thanks very much
fatboyslimerr said:
Hi everyone, I've yet to successfully load a custom ROM on my ville but I have got s-off and supercid. I'm currently on relocked bootloader running the total stock android 4.1. I'd just like to check through the steps I need to take to try a new 4.4.2 ROM. I was thinking of trying twistedkat.
1. Unlock bootloader (I already have the unlock file from htcdev)
2. Load custom recovery (I have TWRP 2.6.3.0 ready to go)
3. Flash SuperSU
4. Flash Rom file (do I need to unzip or flash the zip file in the recovery?)
5. Flash 4.4 Gapps
Any other steps I've missed? I'm on hboot 2.15, kernel 3.14 from the stock updater.
Thanks very much
Click to expand...
Click to collapse
1- if you didn't unlock your bootloader, you have to
2- i don't know which twrp you have but you shuld use the one from twistedkat thread (it's different from official one)
3- it's unrelated with custom rom flashing
4- DON'T unzip the rom, just flash the zip from recovery
5- you have to flash g-apps if want to use google's apps (gmail, playstore, etc.)
you don't need anything else AFAIK
have fun
Sent from my One S using xda app-developers app
By the way i recommend you to change your cid back to original, because supercid has no advantage over original cid. But one day you may want to turn back to stock and if you forget that your device has supercid it will brick the device
Sent from my One S using xda app-developers app
Do not forget to flash boot.img in fastboot! To do it, you need to extract boot.img from ROM zip file to same directory with fastboot on your computer and and reboot your device to fastboot mode. Then run this in terminal/cmd: fastboot flash boot boot.img . If you don't do this, your device won't boot to OS. Flashing SuperSU with a custom ROM is unnecessary since root usually is included in custom ROM.
EDIT: You don't need to flash boot.img, because you have S-OFF. Didn't notice it first.
ka_55 said:
By the way i recommend you to change your cid back to original, because supercid has no advantage over original cid. But one day you may want to turn back to stock and if you forget that your device has supercid it will brick the device
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Oh no! I've already ran a RUU with supercid to get back to total stock and that didn't cause any problems. Problem is I don't actually know what the original cid was!
fatboyslimerr said:
Oh no! I've already ran a RUU with supercid to get back to total stock and that didn't cause any problems. Problem is I don't actually know what the original cid was!
Click to expand...
Click to collapse
I checked again, ruu doesn't seem cause a brick but ota updates may cause such thing. So i think you shouldn't install ota updates till you remember your original cid
Sent from my One S using xda app-developers app
Thanks for the replies guys. One last question. If I load Twistedkat, which is based on CM11, I'll lose Sense?
Can I have sense as well? Is there a flashable sense zip file or something?
Thanks!
You will absolutely lose sense, and there is no way to install sense with kitkat roms right now for our one s
Sent from my HTC One S
See attached screenshot. Now successfully on 4.4.2.
I did need to get SuperSU. Thanks for all the help
Help im new!
Soo i recently got my htc one x on android jelly bean 4.2.2 from at&t and is there a method or easy root method for this version? 4.2.2, with 5.18? I really want to try and root my phone but i know nothing about messing with all these types of files, and i dont want to risk destroying my phone.
Im not sure if there is already a post or something about this and if it is im sorry, these forums are a bit overwhelming and i am new.
I would very much appeircate any help or info on being able to easily root my htc one x 4.2.2, 5.18 at&t white.
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
timmaaa said:
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
Click to expand...
Click to collapse
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
There is a perfectly easy way to unlock your bootloader on the 3.18 software, it isn't a stupid phone, nor is the exploit hard to achieve, hundreds if not thousands of people have done it. It's as simple as entering a few adb/fastboot commands.
You can't root on 5.18 because the update patched the weakness that was exploited in the 3.18 software/firmware. It takes time for devs to crack these things and the update has only just been released. It's not even sure whether the devs will want to spend any time finding a crack for a phone that's relatively old now. This is why you never take an update without first unlocking/rooting, unless you're comfortable with the fact that you won't be able to (it is a well established fact that updates patch exploits).
Sent from my Evita
5.18!to 3.18 ruu
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
brenntard said:
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
Click to expand...
Click to collapse
Bootloader details please.
Sent from my Evita
timmaaa said:
Bootloader details please.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Relocked
Evita put ship s-on rl
Hboot-2.18.0000
Radio-1.35a.32.45.27
Opendsp-v33.1.0.45.1128
Emmc-boot
It's weird, I tried using the all in one toolkit and was able to unlock the boot loader, get twrp recovery working and flash supersu. The only problem I ran into was when I opened supersu it said the binaries need to update. The first time I updated them and it was fine then the phone shut off and supersu would always need updated when opened...I downloaded titanium backup and was able to get root access before my phone restarted and I had to update supersu again... It is now relocked, obviously, but easy enough to unlock again using the toolkit
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Yes it says me CID is 11111111. Why would supersu be acting so funny and constantly telling me to update the binaries...supersu seems relatively useless at this point. do i need supersu to flash a custom ROM?
Forever95 said:
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
Click to expand...
Click to collapse
Lack of research. A working root method exists for 3.18, both a "manual" method and two "Toolkits" for those that can't handle the manual method.
Also, you should never never never install an OTA update unless you know what has been patched, changed, etc. Updates frequently will patch existing root exploits, and therefore leaving you in the spot you find yourself in.
Other devices (such as the One) can be rooted with later firmware, simply because that device has more developer interest. It requires the right talented developer(s) putting in the time and effort to find the exploit method. Its still possible on this device with 5.18. All it takes is the right guy and the proper amount of motivation. But as the device is getting older, and devs are moving to other phones, those chances do get more unlikely.
UPDATE!
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for the help. i know officially have an s-off device that is unlocked and rooted ready to run custom ROMS.
My next question would be how do i flash a kernel and why would i flash a kernel?
cant flash ROM
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
brenntard said:
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
Click to expand...
Click to collapse
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
timmaaa said:
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
Click to expand...
Click to collapse
That sounds easy enough.. I was able to gain s-off through the face palm method earlier today so now i just need to flash the 2.15 firmware. in the thread it says to "make sure you flash your current ROM's boot.img after" is this necessary if i am using the stock 4.2.2 sense 5 ROM already, does the download include the radio? do i need a different radio?
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
timmaaa said:
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
Click to expand...
Click to collapse
awesome! im gonna try that tonight.
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
timmaaa said:
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for your help! i succesfully flashed the firmware and amnow running CM10.2.1. If i want to flash a 4.4 ROM do i need a different recovery? im currently using 2.5.0.0
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) 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
Sent from my Evita
timmaaa said:
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) 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
Sent from my Evita
Click to expand...
Click to collapse
I guess the all in one toolkit hasn't had an update in a while...
thanks again for all the help, really appreciated
i have been working to get a custom rom on my device for roughly a month now and today was the day it finally happened
glad to say i learned a lot thanks to help from people like you in this great forum