Hi all, I've been at this for a few hours now, trying to find a solution but I've come up with nothing.
Right now I am stuck in a boot loop after I've successfully gotten S-off on my device. I can enter bootloader and recovery (TWRP) just fine. I'd been running CM 10.0.0 prior to this and I've tried the whole shebang with reflashing my ROM and also flashing boot.img through fastboot. Nothing seems to be working and I can't seem to find the reason why. I just need to get my phone working again.
Thank you for your assistance.
Please provide more details. Post the first five lines of your bootloader screen. Also post which ROM you flashed.
Sent from my Evita
timmaaa said:
Please provide more details. Post the first five lines of your bootloader screen. Also post which ROM you flashed.
Sent from my Evita
Click to expand...
Click to collapse
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
I've attempted flashing CM 10.0.0 as well as 10.1.3 to no avail.
Where are you downloading the ROMs? And what recovery version are you on?
Sent from my Evita
download.cyanogenmod.org/?device=evita
And I am using TWRP v2.3.1.0
It seems like you're doing everything correctly. Now that you have s-off you don't need to flash the boot.img with fastboot anymore though. Maybe try without doing that, I don't think that's what the problem is though. Also try flashing a different ROM maybe.
Sent from my Evita
lyendsc 259
Right, I've tried with and without flashing boot.img multiple times, clearing caches/doing a factory reset before each time, I'm at a loss right now. I'll try another ROM, but if that doesn't work, what would you suggest I do?
Ruu reflash twrp reflashing rom. Check md5 of everything.
Sent from my HTC One XL using xda app-developers app
exad said:
Ruu reflash twrp reflashing rom. Check md5 of everything.
Click to expand...
Click to collapse
Will do these after I try flashing another ROM.
Your md5 matches on the downloads right?
Sent from my Evita
timmaaa said:
Your md5 matches on the downloads right?
Click to expand...
Click to collapse
I haven't been forcing an MD5 check, should I be?
Update, I've successfully flashed ViperXL 4.0.0 and I can now use my phone, thank you for the replies
You should ALWAYS do a manual md5 check using an md5 app/program on anything you intend to flash. The md5 for the file is listed on the download page, then you use the app to make sure it matches the md5 of the downloaded file. This ensures that the file isn't corrupted.
Sent from my Evita
Related
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Ayahuascaa said:
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Click to expand...
Click to collapse
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
watameron said:
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
Click to expand...
Click to collapse
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Ayahuascaa said:
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Click to expand...
Click to collapse
What HBOOT version do you have?
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
redpoint73 said:
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
Click to expand...
Click to collapse
ViperXL JB
and my hboot is 2.14
Ayahuascaa said:
ViperXL JB
and my hboot is 2.14
Click to expand...
Click to collapse
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
exad said:
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
Click to expand...
Click to collapse
Hmm.. I could have. I did it last night after two hours of frustration.
And I just did that to a new install of Nocturnal's rom, but with no luck. It still just hangs at the HTC dev warning screen. I'm going to try re downloading the ViperXL rom and hope I just had a bad copy..
heh. I did that without thinking last night and spent an hour trying to reverse the damage I did. Not only did I have s-on, but my cid was still "1111111".
./
Androidfilehost is only giving me ~50Kbps, so viper's rom has 3 hours left,
but Cleanrom is almost done.
Is there anyway to s-off the evita without booting into an os?
If not, can someone point me to a thread explaining how to manually s-off?
It seems that it's the cause for all this trouble I'm having and I've never had to do manually.
Thank you everyone for your help,
my phone still doesn't have a working os but I do feel like I'm getting somewhere.
Edit: How many of you have had problems installing roms with twrp 2.5.5.0? I'm thinking about trying 2.3.3.1. I thought this was what I flashed last night, but my touchscreen didn't work and according to exad's post I probably had the wrong one.
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
exad said:
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Ayahuascaa said:
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Edit: Can you point me to a link for twrp 2.3.3.1? The only thread on xda for that build doesn't have working download links
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
exad said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
CleanRom boots!
Thanks again to everyone who helped and exad for the 2.3.3.1 link,
I recently tried to flash CM10 onto my Rogers One X through TWRP 2.3.3.1 but it's been stuck on the bootloader so now I don't have a working OS. I've been trying to figure out how to either fix that or go back to stock through RUU I can't find the correct RUU for that.
**Relocked**
Evita PVT SHIP S-ON RL
Hboot -2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26
So far I've tried
Flashing TWRP 2.6 on, clearing cache/devlek/system then flashing CM10
Every phone is different. You should always read the stickies prior to doing anything even if you think you know what you're doing.
With 2.14 hboot and s-on you need to fastboot flash boot boot.img where the boot.IMG is extracted from the rom. This phone has a few quirks so I suggest reading more or you may find out the hard way.
Typically I ignore these questions but I was feeling nice today. Please also remember that the rules on xda are to search before asking so you are also in violation of xda rules.
Good luck.
Sent from my One X using xda app-developers app
I'll assume the attempted flash of TWRP 2.6 failed, since your bootloader is relocked.
redpoint73 said:
I'll assume the attempted flash of TWRP 2.6 failed, since your bootloader is relocked.
Click to expand...
Click to collapse
His last line shows that he flashed cm 10 in twrp 2.6 he relocked to try ruuing but there is no rogers ruu for that fw
Sent from my One X using xda app-developers app
Hi guys,
I was flashing sense 5 3.6+ota updates on my Rogers Evita, i had 3.5 before and it all went well surprisingly.
now i flash TWRP for evita 2.6 as recommended, i was able to get in, clean cache, flash ROM, flash the new boot.img as suggested, and got stuck on a bootloop.
Tried going back in TWRP, and now i see the Teamwin screen, then to htc screen than hangs.
I tried version 2.5 and 2.6 of TWRP get same results, same with clockwork. So My guess is that my problem doesnt come from the recovery file, but elsewhere ..
Current phone status:
S-On
Hboot 2.14
Radio 0.23a
Thanks!
xatomicx said:
Hi guys,
I was flashing sense 5 3.6+ota updates on my Rogers Evita, i had 3.5 before and it all went well surprisingly.
now i flash TWRP for evita 2.6 as recommended, i was able to get in, clean cache, flash ROM, flash the new boot.img as suggested, and got stuck on a bootloop.
Tried going back in TWRP, and now i see the Teamwin screen, then to htc screen than hangs.
I tried version 2.5 and 2.6 of TWRP get same results, same with clockwork. So My guess is that my problem doesnt come from the recovery file, but elsewhere ..
Current phone status:
S-On
Hboot 2.14
Radio 0.23a
Thanks!
Click to expand...
Click to collapse
Boot to fastboot and type
Fastboot erase cache. That will probably get you into twrp
Sent from my HTC One XL using xda premium
31ken31 said:
Boot to fastboot and type
Fastboot erase cache. That will probably get you into twrp
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
That worked for the bootloader, so far so good.
I'm back to bootlooping, probably need a different boot image. Flushed the whole SD started from scratch, and still bootlooping hehe
xatomicx said:
That worked for the bootloader, so far so good.
I'm back to bootlooping, probably need a different boot image. Flushed the whole SD started from scratch, and still bootlooping hehe
Click to expand...
Click to collapse
Rom includes boot image. Reflash the rom. Then fastboot flash the boot.img from the rom. You just installed, wipe cache, and dalvik. A factory reset after woukdnt hurt either
Sent from my HTC One XL using xda premium
31ken31 said:
Rom includes boot image. Reflash the rom. Then fastboot flash the boot.img from the rom. You just installed, wipe cache, and dalvik. A factory reset after woukdnt hurt either
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah i always flash the rom included in the zip file, thats why i'm surprised about bootlooping.
This may sound silly, but you're flashing 3.6 on top of r3 right?
Sent from my Evita
xatomicx said:
Yeah i always flash the rom included in the zip file, thats why i'm surprised about bootlooping.
Click to expand...
Click to collapse
Did you verify the md5 of the downloads? Could be a corrupted file
Sent from my HTC One XL using xda premium
timmaaa said:
This may sound silly, but you're flashing 3.6 on top of r3 right?
Sent from my Evita
Click to expand...
Click to collapse
Yes i am
I tried Cyanogen, just for fun of trying another room, i get the same boot freeze as with Sense 5
I don't know why it's looping, it shouldn't be if you're following the correct procedure. Are you doing a full wipe, then flashing the ROM, and then flashing the boot.img from that ROM in fastboot?
Sent from my Evita
What does it say in the bootloader screen? Just the top part don't post your imei.
Sent from my HTC One XL using xda premium
31ken31 said:
What does it say in the bootloader screen? Just the top part don't post your imei.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah, it doesnt bootloop anymore, it hangs now.
And i am closely following steps for rom installation, i wipe the whole shazam, cache and dalvik and such, it always worked well, until now.
Bootloader screen
Tampered
Unlocked
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
Radio-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
So you're wiping system/factory reset/cache/dalvik cache? Then flashing ROM, then rebooting to bootloader and flashing boot.img?
Sent from my Evita
xatomicx said:
Yeah, it doesnt bootloop anymore, it hangs now.
And i am closely following steps for rom installation, i wipe the whole shazam, cache and dalvik and such, it always worked well, until now.
Bootloader screen
Tampered
Unlocked
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
Radio-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
Did you flash boot.img from the rom after installing it? If not it will never boot being your s-on and on hboot 2.14
Fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
31ken31 said:
Did you flash boot.img from the rom after installing it? If not it will never boot being your s-on and on hboot 2.14
Fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah, i am always flashing the boot included in roms, but somehow my bootloader always show 2.14 after flashing ... that might be why i cant get it to work
Your bootloader will always show 2.14 unless you get a firmware update. Flashing ROMs does not change your hboot.
Sent from my Evita
timmaaa said:
Your bootloader will always show 2.14 unless you get a firmware update. Flashing ROMs does not change your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Well anyone knows what's the solution? flashing the embedded boot.img did not help.
It's really difficult to diagnose the problem without actually being there. Can you please provide a detailed step-by-step account of what you're doing when you flash the ROM and boot.img.
Sent from my Evita
timmaaa said:
It's really difficult to diagnose the problem without actually being there. Can you please provide a detailed step-by-step account of what you're doing when you flash the ROM and boot.img.
Sent from my Evita
Click to expand...
Click to collapse
Sure,
1 log in twrp
2 wipe cache / dalvik
3 flash rom + updates
4 wipe cache again
5 log on fastboot usb
6 pull off boot.img from rom .zip
7 fastboot flash boot boot.img
8 hit reboot in bootloader
9 system hangs
xatomicx said:
Sure,
1 log in twrp
2 wipe cache / dalvik
3 flash rom + updates
4 wipe cache again
5 log on fastboot usb
6 pull off boot.img from rom .zip
7 fastboot flash boot boot.img
8 hit reboot in bootloader
9 system hangs
Click to expand...
Click to collapse
What version of twrp you using?
Edit: I see 2.6
What version of cm did you try? See if you can get Scott's clean rom booted. That one has flashed and booted for a couple other people having issues. And make sure you verify md5 before you flash it
Sent from my HTC One XL using xda premium
31ken31 said:
What version of twrp you using?
Edit: I see 2.6
What version of cm did you try? See if you can get Scott's clean rom booted. That one has flashed and booted for a couple other people having issues. And make sure you verify md5 before you flash it
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
i tried nightly 10.1
And sense 5 3.6,
i am now on sense 5 3.6, flash the 3 first, then 3.6 and 3.6.1
ill see for your "scott's clean rom", never heard of it, will try.
AT&T HTC ONE X
*** 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
CID: 11111111
version-main: 2.20.502.7
Hello guys. I need some assistance.
In an attempt to install a custom ROM (Android_Revolution_HD-One_X_31.2)
1) Followed steps 1-6 the One_X_ATT_All-In-One_Kit_v3.0.1 to unlock the bootloader and installed TWRP recovery.
2) Then used Flash_boot_31.x_0.1 to get the boot.img loaded and upon installation of the ROM the phone just suddenly restarts at about 30% (tried it twice) and after restart is stuck on HTC incredible boot screen.
I can get to the boot loader and also to TWRP recovery. So I decided to use the backup I made before step 2 and the phone just restarts to the boot screen over and over.
Can I get any pointers on what to do?
I want in the end to get it out of loop mode, then S-OFF, and install a custom ROM so upgrade Hboot.
Thanks,
Ok, firstly there is no Android Revolution ROM for Evita, that's for the Endeavor so you're lucky you didn't brick your phone.
Secondly, you're s-on, so when you made the backup of your previous ROM did you backup the boot partition as well? Restoring a system backup will restore the system but if you're s-on you need to flash the boot.img by fastboot.
At this stage you probably need to flash another ROM and flash the boot.img as well.
Sent from my Evita
timmaaa said:
...there is no Android Revolution ROM for Evita.
Click to expand...
Click to collapse
Where's that disclaimer. It should be in the tittle or something. If it is I can't believe I missed it. Got lucky.
timmaaa said:
...did you backup the boot partition as well?
Click to expand...
Click to collapse
Yes, boot was backed up but still restarts.
timmaaa said:
...you're s-on you need to flash the boot.img by fastboot.
Click to expand...
Click to collapse
Could you please point out which boot.img I could try? I asume ICS as JB requires another hboot and I can't S-off yet.
Thanks.
tavuslokus said:
Where's that disclaimer. It should be in the tittle or something. If it is I can't believe I missed it. Got lucky.
Yes, boot was backed up but still restarts.
Could you please point out which boot.img I could try? I asume ICS as JB requires another hboot and I can't S-off yet.
Thanks.
Click to expand...
Click to collapse
There's no disclaimer, it isn't needed because that ROM isn't posted in our device forum, it's posted in the Endeavor forum, you have the Evita. As long as you only ever stay within the forum you're posting in now you'll be fine, but don't ever stray from here.
Have you tried flashing the boot.img that was backed up via fastboot after restoring the system backup? You can't just restore the boot backup.
The boot.img must be from the ROM you're trying to flash. I'm not sure what you mean when you say JB requires another hboot, that only applies on certain ROMs. Which ROM backup are you trying to restore exactly?
Sent from my Evita
timmaaa said:
don't ever stray from here.
Click to expand...
Click to collapse
Just now I noticed the difference in the forum sections. I need to pay more attention.
timmaaa said:
Have you tried flashing the boot.img that was backed up via fastboot after restoring the system backup? You can't just restore the boot backup
Click to expand...
Click to collapse
The TWRP backup files look like this "boot.emmc.win", renamed it to boot.img and flashed via flashboot and it restarted like nothing was wrong. :good:
Now to S-OFF and get a custom ROM. But tomorrow I guess, eyes need rest.
Thanks for the help timmaaa
I'm glad to see you got it working again :thumbup:
Sent from my Evita
Stay in the forum section in the future to avoid the same mistake again: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or use my Index, sticky at the top of General: http://forum.xda-developers.com/showthread.php?t=1671237
Hello all, here is my situation.
I recently purchased two used HTC One X phones. After a bit of research, I found out that they are actually the international version, the XL or Evita as they also go by. This is not a problem to me. I struggled getting them to take custom ROMs and I was finally able to get Cyanogenmod 10.0 installed. They are working great as is, however I would like to be able to update further, as there are a couple very minor bugs. Whenever I try to install an update through clockwordmod recovery, I always get a bootloader error. The number is spits out is 2.14, which I know is a never version of hboot. So, my question is, should I update my hboot (currently in 1.14.0002) to 2.14 in order to install newer versions of Cyanogenmod? If so, can you please provide detailed step by step instructions, or link me to a forum that does? Thank you.
Other potentially relevant information:
-EVITA PVT SHIP S-ON RL
bootloader unlocked via HTCdev
Ok, firstly it isn't the hboot you need to update, it's the firmware. It just happens that the firmware contains the hboot, and the hboot version is what's used by the ROM installer to tell whether you've updated or not. First thing you'll need to do is get s-off, that's required for flashing the firmware.
Facepalm S-off
Rumrunner S-off Thread
Once you've done that just head to the How-To Guide For Beginners thread in my signature and follow the directions there to update your firmware.
It might be a good idea to bookmark that thread, and also the Evita FAQ thread. The answer to your question is contained within the FAQ thread, which is actually stickied at the top of the section you've just posted in.
Sent from my Evita
timmaaa said:
Ok, firstly it isn't the hboot you need to update, it's the firmware. It just happens that the firmware contains the hboot, and the hboot version is what's used by the ROM installer to tell whether you've updated or not. First thing you'll need to do is get s-off, that's required for flashing the firmware.
Facepalm S-off
Rumrunner S-off Thread
Once you've done that just head to the How-To Guide For Beginners thread in my signature and follow the directions there to update your firmware.
It might be a good idea to bookmark that thread, and also the Evita FAQ thread. The answer to your question is contained within the FAQ thread, which is actually stickied at the top of the section you've just posted in.
Sent from my Evita
Click to expand...
Click to collapse
Okay, thanks. Yeah I'm aware you can't get boot without a firmware update. Will 2.14 allow me to update to cyanogenmod 11?
Yes it will but getting that firmware requires you to run an RUU, which also requires s-off, and is a lot harder than just flashing the firmware package.
Sent from my Evita
timmaaa said:
Yes it will but getting that firmware requires you to run an RUU, which also requires s-off, and is a lot harder than just flashing the firmware package.
Sent from my Evita
Click to expand...
Click to collapse
Major problems. I now have s-off but my phone refuses to boot. It was in a boot loop, tried flashing boot.img again and now it tries to start then fails, black screen until I how the volume and power button to get back into bootloader. Any suggestions on that?
asilaydyingdl said:
Major problems. I now have s-off but my phone refuses to boot. It was in a boot loop, tried flashing boot.img again and now it tries to start then fails, black screen until I how the volume and power button to get back into bootloader. Any suggestions on that?
Click to expand...
Click to collapse
Flash a ROM, not really a major problem.
Sent from my Evita
timmaaa said:
Flash a ROM, not really a major problem.
Sent from my Evita
Click to expand...
Click to collapse
Tried it, still fails. Installed the ROM, gapps, and flashboot flash boot boot.img
timmaaa said:
Flash a ROM, not really a major problem.
Sent from my Evita
Click to expand...
Click to collapse
Flashed the right boot.img (somehow had the wrong one) now back in boot loop again. Any ideas? I did have to change my CID because I did not turn on debugging for ADB. Would that have something to do with it?
What are your bootloader details now? What did you change your CID to? And what did that have to do with debugging? What ROM did you flash?
Sent from my Evita
timmaaa said:
What are your bootloader details now? What did you change your CID to? And what did that have to do with debugging? What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT 1.14.0002
Flashed Cyanogenmod 10.0.0. I was unable to use the last command successfully on facepalm's tutorial without allow ADB in android debugging.
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
timmaaa said:
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ummm... how do I transfer the new files to my phone if I can't get it to boot in the first place? I will need to transfer the files for the new ROM.
timmaaa said:
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
IM BACK IN!!! Updating the firmware did it! THANKS FOR YOUR HELP!!! KITKAT HERE I COME!