[Q]Rogers One X Stuck in Bootloop - AT&T, Rogers HTC One X, Telstra One XL

Hello all. So a friend of mine handed me his One X today and from what I gathered he was unable to flash CM after unlocking the bootloader and flashing CWM recovery. I figured I would give it a shot since I am familiar with flashing roms etc but wow what a difference it is for HTC devices!
I've spent the past 2 or 3 hours browsing this subforum however I feel like I could be just misinforming myself. The phone is a Rogers HTC One X the firmware version it was running I am unsure of as its currently stuck in bootloop. I've attached a screenshot below of the current fastboot menu. As it seems the bootloader is indeed unlocked however it is still s-on and stock recovery. If someone would be kind enough as to point me in the right direction of how to gain root and flash a recovery I would be super grateful. Feel free to PM me as well.
Thanks for your time.

What is the full filename of the ROM you're trying to flash? Also, the phone is s-on so you would need to flash the boot.img via fastboot to get it to boot.
Sent from my Evita

timmaaa said:
What is the full filename of the ROM you're trying to flash? Also, the phone is s-on so you would need to flash the boot.img via fastboot to get it to boot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply. From what I was told he flashed the latest CM nightlies for Evita through CWM. Although now it appears to have the stock recovery.
So as far as gaining root and flashing a recovery, since the bootloader is unlocked can I not simply flash a recovery through fastboot and then flash a rom with SU like CM?

Yeah you can, use TWRP recovery instead of CWM though. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP on the phone. Go into it, wipe cache/dalvik/factory reset/system, then install the ROM and gapps. Like I said though you'll need to flash the boot.img via fastboot afterwards. So once you've installed the ROM reboot to bootloader, grab the boot.img from the ROM zip and flash it using this command:
Code:
fastboot flash boot boot.img
Once that's completed you should be able to reboot into the ROM. Please note though that some of the latest CM ROMs have a few bugs, including booting problems.
Sent from my Evita

Hey thanks again timaaa for the fast reply! I've successfully booted into CM now after flashing the boot.img. Regarding the bootloader should I be concerned with s-on? Will I run into trouble down the road because I do not have s-off?

Cool, glad you got it booted. In my opinion getting s-off would be a good idea. The benefits include the following:
Not needing to flash the boot.img from a ROM/kernel through fastboot anymore.
Being able to flash radios (s-on restricts this on phones with a hboot equal to or greater than 1.14).
Being able to change hboot freely (or just remove the red warning text from the startup screen).
Being able to change CID if needed.
Being able to flash the required firmware package which is required to run current Sense 5 ROMs.
In order to get s-off you first need SuperCID though, the hex edit method will be the best to use. Here's a link:
http://forum.xda-developers.com/showthread.php?t=2212737
Once you have SuperCID you can go ahead and get s-off here:
http://forum.xda-developers.com/showthread.php?t=2155071
Both processes are pretty quick and simple, and the benefits are great.
Sent from my Evita

Related

HELP: I cant install any ROM (noob here)

Hi there.
2 things before i explain the problem: 1) Yes, I'm a noob and 2) sorru for bad english.
So, today I was trying to install a different custom rom because the previous one (official ICS) was too slow, etc..
My desire S was a branded one, unlocked, etc.
Now I have:
UNLOCKED
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
jul 31 2012,15:41:32
After trying to install the custom rom (fallout 5.0) etered the recovery and do a full wipe and a format. After that I copied on the sd card the ROM .zip and flashed from recovery. Always seem to be good, but when the phone rebooted, it was stucked on the white htc one screen.
I've tryied lot of guides and tool s here, but nothing helps me (5 hours on the forum).
A very big help will be very appreciated.
Thanks guys!
you need to flash boot.img after installing the rom
ContactFront said:
you need to flash boot.img after installing the rom
Click to expand...
Click to collapse
Something appening now. I'm trying to reinstall the RUU ICS. Previously I cannot because I needed to relock it.
Now I need to know how to install the fallout without problems.
Do I simply flash it from recovery than flash the boot.img?
Thank you very much
Burpo said:
Something appening now. I'm trying to reinstall the RUU ICS. Previously I cannot because I needed to relock it.
Now I need to know how to install the fallout without problems.
Do I simply flash it from recovery than flash the boot.img?
Thank you very much
Click to expand...
Click to collapse
yes.
flash your rom ->reboot into bootloader ->flash boot.img using fastboot command ->reboot your phone
every time you install a new custom rom, you need to flash the boot.img
ContactFront said:
yes.
flash your rom ->reboot into bootloader ->flash boot.img using fastboot command ->reboot your phone
every time you install a new custom rom, you need to flash the boot.img
Click to expand...
Click to collapse
Do i have to re-unlok it before re-flash the rom?
I've done everything (flash fallout 5.0 and after that flash boot.img). Still stuck on htc one white screen
EDIT: still stuck also with an other custom rom
Can you list all the things you did?
Tapatalked from Desire S running Andromadus
suku_patel_22 said:
Can you list all the things you did?
Tapatalked from Desire S running Andromadus
Click to expand...
Click to collapse
I think that I cannot flash any custom rom because (I think) I have to downgrade the 2.02 hboot.
By the way here the list of things I did with
RUU ICS, UNLOCKED, SAGA PVT SHIP S-ON RL, HBOOT-2.02.0002:
- recovery (cyanogenmod) > full wipe, etc
- install from zip file > fallout 5.0
- flash boot.img
After that everything seems good but when the phone reboot, it will stuck into htc one white screen (or black whit an other rom).
Thanks for help
EDIT: the only thing I want is to flash and test every roms I want, without having always some king of problem.
What command did you use to flash boot.img. Try to be precise rather than just say i flashed the boot.Img.
“He is a wise man who does not grieve for the things which he has not, but rejoices for those which he has.”* ~Epictetus
AW: HELP: I cant install any ROM (noob here)
To me it looks like you used the command "fastboot boot boot.img" instead of "fastboot flash boot boot.img", could that be the case?
teadrinker said:
To me it looks like you used the command "fastboot boot boot.img" instead of "fastboot flash boot boot.img", could that be the case?
Click to expand...
Click to collapse
That was my thought
“He is a wise man who does not grieve for the things which he has not, but rejoices for those which he has.”* ~Epictetus
Op seems to do first then read. The 2nd post should have solve his issue already.
FromA100
teadrinker said:
To me it looks like you used the command "fastboot boot boot.img" instead of "fastboot flash boot boot.img", could that be the case?
Click to expand...
Click to collapse
Yep, maybe this is the reason of my fail. I think I lost one "flash"
I'll try later and let you know if everything is ok
So, I'm trying to flash the rom. I've wipe everything, than flashed the rom. Now I entered the command "fastboot flash boot boot.img". The prompt still show "waiting for device". What the hell?
"fastboot devices" didn't give me an answer same as "adb devices"
Uhm... Maybe I need to reinstall htc sync drivers? :angel:
Ok, nevermind, I needed to reinstall correct win7 64bit drivers.
So. I success with fastboot flash boot boot.img. The phone is still stuck on the HTC one white screen. FUUUUU!
EDIT: SUCCESS!
Just need to wait 5 mins!
Thank you all!

[Q] Stuck on boot screen after try to change ROMs

As the title says my phone is stuck on the "initiating swagger" bootscreen from my last ROM. So initially I was trying to try out a new 4.3 based rom, but eventually figured out it wasn't working because my HBOOT is too old (1.14.002). From what I gather in order to upgrade my HBOOT safely, I need S-OFF. I had unlocked bootloader and SUPERCID but never got S-OFF. So I tried to restore to the backup I mad in TWRP, but that wouldn't make it past the bootloader, so I downloaded another 4.1.2 ROM instead, which got me to the previously mentioned bootscreen and thats as far as I go. What can I do from here? I gone through countless times, wiping cache,data, factory reset then installing rom, the loading boot.img, but I'm stuck. Any help would be appreciated.
At&T htc one x
hboot 1.14.002
If you're s-on you need to flash the boot.img from the ROM zip via fastboot.
And yes you must have s-off to safely run the 3.18 RUU to meet the requirements for the 4.2.2 ROMs.
Sent from my Evita
timmaaa said:
If you're s-on you need to flash the boot.img from the ROM zip via fastboot.
And yes you must have s-off to safely run the 3.18 RUU to meet the requirements for the 4.2.2 ROMs.
Sent from my Evita
Click to expand...
Click to collapse
I have been flashing the boot.img through the bootloader via fastboot. No luck.
Which version of TWRP are you using?
Sent from my Evita
timmaaa said:
Which version of TWRP are you using?
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.5
That's good problem, 2.5 is full of bugs. You need to upgrade to at least the 2.6 version. 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 can enter recovery on your phone and try again.
Sent from my Evita
Awesome, that worked. Now in order to flash a 4.3 mod I need to get S-off and then upgrade the hboot, right? How to I upgrade the hboot?
Thanks a lot.
Actually nevermind, I put hboot 2.14 on there and am now running PACman rom. Thanks again.

[Q] How to downgrade from 4.2.2.?

Hi,
I'd like to ask for your help. After an update to Android 4.2.2 and Sense 5.0 on my HTC ONE SV I'd really like to go back to the previous version, I know a lot of people are happy about the update, but I'd really like to go back to the older menus, look etc. I don't mind losing the data.
I'm new over here ... so please bare with me
What info should I provide?
Nina
I can't help you at the moment because I have to get ready for work but for starters you will need to unlock your device, acquire the proper ruu (4.1.2), or if its available on here then a nandroid backup (4.1.2) specific to your device. Then at this point the procedures to take would be based on whether you are S-On or S-off.
Hopefully someone else may chime in on this while I am at work.
Sent from my C525c using XDA Premium 4 mobile app
We need to know, what version of one sv you have (k2u, k2ul, or other).
And if you are S-off, which hboot...
To unlock your device or in simple terms the bootloader you will need to head over to HTCDEV.com and follow their instructions. If you wish to be S-Off you will need to get rumrunner for your phone and follow its instructions - otherwise you may remain S-On.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 07:38 AM ---------- Previous post was at 07:36 AM ----------
old.splatterhand said:
We need to know, what version of one sv you have (k2u, k2ul, or other).
And if you are S-off, which hboot...
Click to expand...
Click to collapse
Sounds like she is legit stock on everything lol. So this may in a sense be easy assuming instructions can be followed
Sent from my C525c using XDA Premium 4 mobile app
Thanks to both of you.
My version is:
K2_UL PVT SHIP S-on RL
HBOOT-2.00.0000
ninamalina said:
Thanks to both of you.
My version is:
K2_UL PVT SHIP S-on RL
HBOOT-2.00.0000
Click to expand...
Click to collapse
Then its quiet easy:
unlock your device at htcdev.com (follow the instruction on that side.
Then you need to flash a custom recovery (i recommend TWRP 2.6.3) with fastboot, and next you flash a 4.1.2 rom with recovery. Now you need to flash the boot.img that was inside your rom zip with fastboot and you are ready to go
All links you need, you will find in my index thread (look at my signature for it).
To flash a custom recovery with fastboot you will need to insure your custom recovery image file is located in the same folder as your fastboot file to keep this next part simple.
Go into your HBoot then select fastboot. Connect device to your pc and in the command window type:
Code:
fastboot devices
This should show that your device is connected. If you see nothing then you will need to resolve that before proceeding. Next , once connection is established type:
Code:
fastboot boot customrecovery.img
You are booting instead of flashing the custom recovery so your stock recovery will be persevered. Each time you reboot your device you will need to follow those steps again to access the custom recovery vice your stock recovery.
If you wish to flash it then:
Code:
fastboot flash recovery customrecovery.img
I don't recommend you flashing it yet unless you get a copy of your stock recovery first.
Sent from my C525c using XDA Premium 4 mobile app
old.splatterhand said:
Then its quiet easy:
unlock your device at htcdev.com (follow the instruction on that side.
Then you need to flash a custom recovery (i recommend TWRP 2.6.3) with fastboot, and next you flash a 4.1.2 rom with recovery. Now you need to flash the boot.img that was inside your rom zip with fastboot and you are ready to go
All links you need, you will find in my index thread (look at my signature for it).
Click to expand...
Click to collapse
Great, thanks!
I'll do everything when i come home
Modding.MyMind said:
To flash a custom recovery with fastboot you will need to insure your custom recovery image file is located in the same folder as your fastboot file to keep this next part simple.
Go into your HBoot then select fastboot. Connect device to your pc and in the command window type:
Code:
fastboot devices
This should show that your device is connected. If you see nothing then you will need to resolve that before proceeding. Next , once connection is established type:
Code:
fastboot boot customrecovery.img
You are booting instead of flashing the custom recovery so your stock recovery will be persevered. Each time you reboot your device you will need to follow those steps again to access the custom recovery vice your stock recovery.
If you wish to flash it then:
Code:
fastboot flash recovery customrecovery.img
I don't recommend you flashing it yet unless you get a copy of your stock recovery first.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will follow your advice!
Although instructions are clear, I still have problems
I've tried using different computer, turned my av off, but still get this when i try to run the downloaded file from HTCdev.com:
This aplication has failed to start because AdbWinApi.dll was not found.
You are missing files.
You can get them from here: http://rom.android-host.de/DESIRE_C/tools/Android.zip

[Q] Please help phone has no OS

Okay so here is what happened i unlocked my bootloader and rooted my phone using the all in one toolkit, i tried to flash a custom ROM using the GooManager app. This is where things went wrong. After flashing the ROM my phone shut off and would only turn on to the HTC Quietly Brilliant page at the beginning of the boot cycle, i made a backup but dont know how to find it. I somehow managed to wipe the entire phone and now i have no operating system. I had TWRP installed but cannot access it because i relocked the phone. Is there anyway to get this thing working again? any help would be much appreciated
here is what my fastboot screen reads:
***TAMPERED***
***RELOCKED***
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
brenntard said:
Okay so here is what happened i unlocked my bootloader and rooted my phone using the all in one toolkit, i tried to flash a custom ROM using the GooManager app. This is where things went wrong. After flashing the ROM my phone shut off and would only turn on to the HTC Quietly Brilliant page at the beginning of the boot cycle, i made a backup but dont know how to find it. I somehow managed to wipe the entire phone and now i have no operating system. I had TWRP installed but cannot access it because i relocked the phone. Is there anyway to get this thing working again? any help would be much appreciated
here is what my fastboot screen reads:
***TAMPERED***
***RELOCKED***
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
FASTBOOT
to previous item
to next item
to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
Since you are s-on, you need to fastboot flash boot boot.IMG from the ROM you want to use. While you're at it you may as well just s-off your device. It will make things simpler in the end. You're going to have to unlock the boot loader again to flash the boot image though. You will also want to flash recovery again via fastboot.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Since you are s-on, you need to fastboot flash boot boot.IMG from the ROM you want to use. While you're at it you may as well just s-off your device. It will make things simpler in the end. You're going to have to unlock the boot loader again to flash the boot image though. You will also want to flash recovery again via fastboot.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so much for the response...i have a couple questions. I am fairly new to android and these are the first real problems i have run into that i havent been able to solve on my own. how do i "fastboot flash boot boot.IMG"? i just want to use the stock ROM or CM10 which ever will get my phone running again. I have unlocked to bootloader again and now have access to TWRP
brenntard said:
Thank you so much for the response...i have a couple questions. I am fairly new to android and these are the first real problems i have run into that i havent been able to solve on my own. how do i "fastboot flash boot boot.IMG"? i just want to use the stock ROM or CM10 which ever will get my phone running again. I have unlocked to bootloader again and now have access to TWRP
Click to expand...
Click to collapse
Take a look at this thread
http://forum.xda-developers.com/showthread.php?t=2136172
It will answer many of the questions that you have and provides links to appropriate tools.
You should definitely s-off your device now. Just look for the question in the thread I linked for more detail. Bookmark it as well, or add it to your favorites, as it will provide a great reference point for future use.
Once you have s-off, you will just have to flash any ROM you want from recovery. It will make your life way easier.
If someone helps you, just hit the thanks button, or thumbs up from the xda app.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Take a look at this thread
http://forum.xda-developers.com/showthread.php?t=2136172
It will answer many of the questions that you have and provides links to appropriate tools.
You should definitely s-off your device now. Just look for the question in the thread I linked for more detail. Bookmark it as well, or add it to your favorites, as it will provide a great reference point for future use.
Once you have s-off, you will just have to flash any ROM you want from recovery. It will make your life way easier.
If someone helps you, just hit the thanks button, or thumbs up from the xda app.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In the rumrunner instructions to s-off my device it says i need to have fast boot unchecked in settings. I am pretty sure i have it checked but there is no way for me to tell for sure...since i dont have an OS installed is this an issue?
brenntard said:
In the rumrunner instructions to s-off my device it says i need to have fast boot unchecked in settings. I am pretty sure i have it checked but there is no way for me to tell for sure...since i dont have an OS installed is this an issue?
Click to expand...
Click to collapse
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
timmaaa said:
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
Click to expand...
Click to collapse
Okay I was able to flash the boot.img but can't figure out how to flash the rom.. Should I do it through recovery? Or through a fast boot command prompt like the one used to flash the boot.img
timmaaa said:
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
Click to expand...
Click to collapse
This may go with out saying but when I'm in recovery and hit the reboot button and try to select "system" it comes up with a message telling me I have no OS installed and asks if I want to continue anyway..
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
timmaaa said:
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
Click to expand...
Click to collapse
How do i get the ROM onto my phone? that might be a stupid question but i am stumped
brenntard said:
How do i get the ROM onto my phone? that might be a stupid question but i am stumped
Click to expand...
Click to collapse
Mount your sdcard through TWRP. You should then be able to drag and drop the file from your computer to your sdcard. It should go without saying that your phone needs to be connected to your computer.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Mount your sdcard through TWRP. You should then be able to drag and drop the file from your computer to your sdcard. It should go without saying that your phone needs to be connected to your computer.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i cant mount my sd card, i can put a little x by cache data and system but not sd card...
timmaaa said:
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
Click to expand...
Click to collapse
i was unable to do a wipe of my phone. in twrp i went to wipe and "swipe to factory reset" it ran through and came back as failed..
Try to format your sd then (from recovery)
Gesendet von meinem Xperia Neo V mit Tapatalk 2
What ROM did you flash with Goo Manager?
You mount the sd card by going into the mount menu, then using the mount usb storage option.
Sent from my Evita.

At&t Htc One X 4.2.2 Root

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

Categories

Resources