Related
So here's the situation. I've been running NoSensi 1.0.4 ROM w/o problems for the past month but all of a sudden tonight my phone started to freeze up. I would take the battery out and turn it back on but after a few minutes the phone would freeze up again. So I decided to try to flash the new version on NoSensi (1.0.8) and the first step was to flash the NoSensi_EXT4_Wipe and it was almost complete in CWM when it froze up and wouldn't respond. Waited a few more minutes to be sure it wasn't just taking a while so I took the battery out and went back into recovery. In CWM, I see the menu options but when I try to select install from SD, the CWM menu would reset every few seconds and leave me at the main screen.
So now I'm stuck with a phone that won't boot cause I don't have a proper ROM on and can't install a new ROM cause CWM is messed up.
Any ideas on how I can reinstall CWM or something?
First off, can you boot to hboot? And next do you have adb set up on your PC or Mac?
I'm gonna be honest with you, I can't really help you all the way but can give you the things you need to get started. And if anyone reads this and knows more about this please help thanks
Sent from my CM7 Nightly HTC Desire HD
Yes, I believe I can get into HBOOT, I get the white screen where the option of going into recovery of HBOOT. I do have adb on my PC, but don't know how to use it unless I have instructions.
Okay I remember going through the threads and saw something on using the PD98 img that has the recovery img inside instead of the system img. Ill look around but probably in the morning since its almost 2 for me. Or if someone knows what I'm talking that'd be great
Sent from my CM7 Nightly HTC Desire HD
bluizzo said:
Okay I remember going through the threads and saw something on using the PD98 img that has the recovery img inside instead of the system img. Ill look around but probably in the morning since its almost 2 for me. Or if someone knows what I'm talking that'd be great
Sent from my CM7 Nightly HTC Desire HD
Click to expand...
Click to collapse
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
Got CWM back with this, thanks so much! I tried doing the same method that was mentioned in this thread http://forum.xda-developers.com/showthread.php?t=1019868 but kept having issues with CWM resetting every 2 seconds which didn't allow me to use it at all. Your file worked and am flashing a ROM on now. Hopefully the random freezing was just random so I'm just going to do a fresh install of a ROM
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
Yay that's what I was looking for, thanks soo much
Sent from my CM7 Nightly HTC Desire HD
so it seems it may be a hardware issue after all... sigh. Going to look to see if I can pick up another one for cheap on craigslist or something now cause mine was also used of CL about 5 months ago.
dtothesquare said:
so it seems it may be a hardware issue after all... sigh. Going to look to see if I can pick up another one for cheap on craigslist or something now cause mine was also used of CL about 5 months ago.
Click to expand...
Click to collapse
HTC warranties the device for a year. I don't think any Inspire is a year old yet so you might want to call them first. Even if not covered by warranty, HTC is pretty reasonable on repairs.
Gene Poole said:
HTC warranties the device for a year. I don't think any Inspire is a year old yet so you might want to call them first. Even if not covered by warranty, HTC is pretty reasonable on repairs.
Click to expand...
Click to collapse
Cool, thanks for the tip, i'll try to get stock by on then call them up
So I'm trying to run the PD98IMG image in HBoot, but its not auto-running anymore. Any ideas on how to manually have it run?
- EDIT: Nvm, it was due to bad sdcard
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
So I tried reverting back to stock via the PD98IMG method with both the gingerbread and complete stock in the post you mentioned. Both them it updates fine but on the reboot it just hangs on the white htc screen. Any recommendations? Would HTC warranty if it's stuck like that?
It sounds like a hardware problem to me. The first and most obvious sign that a phone has been rooted is the S-OFF in the HBOOT screen. They probably won't warranty it if this is still set. Unfortunately, you need a functioning phone to get to the point that you can re-apply S-ON. I'm really not sure what advice I can give you at this point.
Gene Poole said:
It sounds like a hardware problem to me. The first and most obvious sign that a phone has been rooted is the S-OFF in the HBOOT screen. They probably won't warranty it if this is still set. Unfortunately, you need a functioning phone to get to the point that you can re-apply S-ON. I'm really not sure what advice I can give you at this point.
Click to expand...
Click to collapse
I figured as much. Oh well, going to miss the Inspire, really did like it except for that stupid battery door. Picked up a used captivate for cheap to hold me over until my next phone. Thanks for your help!
Missing CWM / No Recovery
Through a long string of mistakes, I'm stuck with an Inspire that will not load Recovery (just get black screen with phone icon and red exclamation point).
This thread was the best match I could find. I used the method above (renamed Gene Pool's file to PD98IMG.zip, placed on SD root), but HBOOT does not seem to find it during the startup scan.
Here is what I've got:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
I've tried 2 different SD cards - I got into this mess because radio updates were not being found in PD98IMG.zip files either, so feel like its an HBOOT problem.
Any ideas?
ctownj30 said:
Through a long string of mistakes, I'm stuck with an Inspire that will not load Recovery (just get black screen with phone icon and red exclamation point).
This thread was the best match I could find. I used the method above (renamed Gene Pool's file to PD98IMG.zip, placed on SD root), but HBOOT does not seem to find it during the startup scan.
Here is what I've got:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
I've tried 2 different SD cards - I got into this mess because radio updates were not being found in PD98IMG.zip files either, so feel like its an HBOOT problem.
Any ideas?
Click to expand...
Click to collapse
If you are sure you renamed it correctly (Windows didn't mangle the name with its stupid "hide extensions" feature) and you are S-OFF, then the only other thing it could be is a bad or weak SD Card. Do you have a spare to try?
I solved this. Figured it was not reading my SD cards so I reformatted one (FAT32), redid everything, and was able to re-flash CWM. Bizarre, since the same card has been used successfully several times on this phone.
I'm pretty sure I bricked my rogers HTC one X.
Where can I find a Rogers RUU?
I can see a lot of AT&T ones, but not a Rogers one.
Is there one around I can snag?
There's a link posted online. I restored mine last weekend.
Sent from my HTC One X using xda premium
I downloaded the Rogers RUU but it's just full of all the image files it's not an exe...? I'm confused
I can't post the link yet google rogers one x ruu
AT&T and Rogers HTC One X LTE Stock RUU (Evita ROM Update ...
androidromupdate.com/.../att-and-rogers-htc-one-x-... - United Kingdom
4 days ago – This is the original Stock RUU (Rom Update Utility) for HTC One X LTE branded versions released in AT&T USA, Rogers Canada and all other ...
You've visited this page 2 times. Last visit: 16/05/12
That's what it looks like on google
wouldn't let me hyper link
how do you make it an .exe? or do i have the wrong one
http://rapidlibrary.com/files/pj83img-evita-ul-rogers-wwe-1-73-631-1-radio-0-16a-32-09-06-10-81-32-14l-release-254934-signed-zip_ulc8eyefx8i89on.html
Here is the link to the Rogers shipped RUU. I am unsure of how to flash it too.
SiqMawsh said:
http://rapidlibrary.com/files/pj83img-evita-ul-rogers-wwe-1-73-631-1-radio-0-16a-32-09-06-10-81-32-14l-release-254934-signed-zip_ulc8eyefx8i89on.html
Here is the link to the Rogers shipped RUU. I am unsure of how to flash it too.
Click to expand...
Click to collapse
Ya that's exactly the one I have yours Isn't an exe either??
they are more than one way of doing it..but the easiest way I recommend to people who are new.
go through this post.
http://forum.xda-developers.com/showthread.php?t=1656516
download the tool I provided.(made by htc)
follow the steps i method in that post.
you should be able to flash it.
I keep getting error 102 for battery being lower than 30% although it's at 80?
adtoes said:
I keep getting error 102 for battery being lower than 30% although it's at 80?
Click to expand...
Click to collapse
are you using vm?
Not sure why you mean by vm but I did get it working put the phone in fastboot after a wall charge. I didn't think you needed to be in fastboot to use ARU
Thanks for all the help now bootloader says "relocked" lol
Completely back to stock ruu
I was unable to find an EXE, but did find the Rogers ZIP file.
Thanks to PeteHTC I used the file that you guys downloaded and followed this process, worked like a charm...
http://forum.xda-developers.com/showpost.php?p=25732586&postcount=4
Hi everyone,
I'm very new to the unlocking world and I couldn't have a worse start. In fact I have done something really stupid, I have installed a AT&T firmware, the latest, 1.85 on my Rogers HTC One X and even though the phone is working relatively well, I don't have my data plan, I guess because of the firmware.
I have tried to install a RUU, shown in this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says it can't update this ROM, saying this ROM isn't for this phone. It probably because my AT&T firmware.
Is there a way I could install a Rogers Firware back on my HTC One X?
Thanks a lot for your precious help, very appreciated.
Fr33man76 said:
Hi everyone,
I'm very new to the unlocking world and I couldn't have a worse start. In fact I have done something really stupid, I have installed a AT&T firmware, the latest, 1.85 on my Rogers HTC One X and even though the phone is working relatively well, I don't have my data plan, I guess because of the firmware.
I have tried to install a RUU, shown in this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says it can't update this ROM, saying this ROM isn't for this phone. It probably because my AT&T firmware.
Is there a way I could install a Rogers Firware back on my HTC One X?
Thanks a lot for your precious help, very appreciated.
Click to expand...
Click to collapse
I've never been able to get the rogers ruu to work either. my advice... If your unlocked... fastboot flash a custom recovery (twrp) and flash king cobra 1.2 rom found in our dev section.
your data issue is 99.9% of the time a missing apn.
Sent from my HTC One XL using xda premium
Hi ptesmoke,
What do you mean by "Unlocked" are you talking about the bootloader? If yes then I'm not but it won't be aproblem I have unlocked the bootloader a couple of times but for this Rogers RUU it says I need to have the bootloader Locked.
As I said, I'm very new to this world when you tell to fastboot a cutom recovery (twrp) are you talking about something like ClockworkMod Recovery? Is (TWRP) a recovery tool too? I have installed ClockworkMod Recovery into my phone.
Could you please post the link for the king cobra 1.2 file, is there a thread that explain how to flash the ROM?
Thank you very much ptesmoke, very appreciated you help
[deleted]
Before I start, all credit goes to JSLEnterprises. This is his method.:good:
I have a always working method, but requires the following:
1. Either having a Rogers Device, or have Supercid (no area limitations)
2. Locked bootloader (relocked is fine)
3. Drivers that can run fastboot USB (if you can unlock your bootloader, this is not a problem)
The way I got Rogers RUU to work is as follows:
1. open the AT&T RUU .exe
2. after the first window pops out (takes a while cause it need to decompress things), don't continue. Look for C:\Users\(your user name)\AppData (often hidden, change your "folder and search settings" in Organization)\local\Temp. In the Temp folder, search for rom.zip (you don't want to go over every f**king sub-folder, right?)
3. Rename the Rogers RUU zip into rom.zip and replace the rom.zip in Temp folder
4. start your One X into fastboot, connect it to the PC, and it should show "fastboot USB"
5. continue your steps in the AT&T RUU program.
Since you have replaced the AT&T ruu rom with rogers, rogers will be flashed.
Again, all credit goes to JSLEnterprises.
---------- Post added at 09:54 PM ---------- Previous post was at 09:48 PM ----------
Fr33man76 said:
Hi everyone,
I'm very new to the unlocking world and I couldn't have a worse start. In fact I have done something really stupid, I have installed a AT&T firmware, the latest, 1.85 on my Rogers HTC One X and even though the phone is working relatively well, I don't have my data plan, I guess because of the firmware.
I have tried to install a RUU, shown in this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says it can't update this ROM, saying this ROM isn't for this phone. It probably because my AT&T firmware.
Is there a way I could install a Rogers Firware back on my HTC One X?
Thanks a lot for your precious help, very appreciated.
Click to expand...
Click to collapse
You know what? this might be caused by two things.
1. At&t firmware
2. RUU don't usually downgrade stuff....you can only downgrade firmware with RUU when you are in fastboot usb
Get Supercid (I believe there's a one click tool for it...not sure if it works on every firmware though...use the search tool), flash through fastboot usb, and you will be fine.
By the way, instead of using the tool in the link you have (which I think is a stripped down version of RUU.exe), run the original AT&T RUU, and replace the rom.zip in temp (look above)...this works better for me than the stripped down version.
Hi xhao1108,
Thank you very much for your reply.
Actually I haven't flashed an AT&T with a Rogers ROM, it was the opposite. I have a Rogers phone that I have flashed with an AT&T (1.85) ROM and even though the phone works, I can receive and make calls, I don't have access to the data.
The Supercid is to root the phone? I've tried prior to flash my phone and I was able to root it, however with the new firmware I can't find a solution that works.
As for the method you propose, I've tried it but I can't find the rom.zip on my Temp folder, I have changed the folder and search options but no luck.
The problem is that I can't find a RUU from rogers, I have tried with this one on this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says the rom isn't for this device.
I'm quite stuck right now because I can't find a RUU from Rogers, I cant find a proper way to root and I can't even reboot on Recovery. I have installed recovery-clockwork-touch-5.8.3.1-evita-modaco and the process goes well, no error message, so I can't even boot on recovery and flash with the zip file.
Once again, thank you for your time and thank you everyone for the precious help.
Fr33man76 said:
Hi xhao1108,
Thank you very much for your reply.
Actually I haven't flashed an AT&T with a Rogers ROM, it was the opposite. I have a Rogers phone that I have flashed with an AT&T (1.85) ROM and even though the phone works, I can receive and make calls, I don't have access to the data.
The Supercid is to root the phone? I've tried prior to flash my phone and I was able to root it, however with the new firmware I can't find a solution that works.
As for the method you propose, I've tried it but I can't find the rom.zip on my Temp folder, I have changed the folder and search options but no luck.
The problem is that I can't find a RUU from rogers, I have tried with this one on this thread: http://forum.xda-developers.com/showthread.php?t=1658929 but half way it says the rom isn't for this device.
I'm quite stuck right now because I can't find a RUU from Rogers, I cant find a proper way to root and I can't even reboot on Recovery. I have installed recovery-clockwork-touch-5.8.3.1-evita-modaco and the process goes well, no error message, so I can't even boot on recovery and flash with the zip file.
Once again, thank you for your time and thank you everyone for the precious help.
Click to expand...
Click to collapse
ppl are telling you to do too many different things.
If you've unlocked before... and yes bootloader, unlock it again.
boot into bootloader once unlocked and fastboot flash TWRP recovery, you can find the thread in the dev section.
Once that's flashed reboot into recovery by completely turning off the phone and powering up with vol down and power. select recovery.
find the menu to mount usb storage device. hook up to pc.
download king cobra 1.2 or any other custom rom you'd like to try, and follow Instructions in the roms thread (usually factory reset, wipe cache and dalvik cache then flash rom)
once that's done reboot system.
WINNING
alternatively you could just add the rogers apn info in the rom you have on there now... then your data would work. But I'd recommend kingcobra, works stellar on rogers.
If your stuck pm me..and ill give u my gtalk info so we can txt.
edit; I'd link you to everything but it's 11pm here and I'm mobile...
Sent from my HTC One XL using xda premium
ptesmoke, you are definitely the man you are my hero and my saver
It worked perfectly, I had installed ClockworkMod recovery and I don't know for which reason I wasn't being able to go on recovery, with TWRP recovery it worked like a charm and I now have my data back.
Once again, a thousand thanks for your precious help. If I can do anything for you don't hesitate, if I can help I'm here.
OK,
I did something really stupid. I was able to flash King Cobra 1.2 and my phone was working just fine but then after I wanted to install Sick Sense but it asked to do a reset factory and wipe system in recovery mode which I did. However, after I've wiped the system I don't have the rom on my sdcard anymore, actually it seems I have only the folder structure but no files in it.
I thought the wipe system would erase my rom on my SDCARD, how I don't know how to put the rom back to be able to flash the rom, when I plug the USB cable it asks me to Format, which I don't do of course but I can't see my phone on the explorer.
Is there a way to push the rom file into the phone other than via the windows explorer?
Thanks for your help.
Fr33man76 said:
ptesmoke, you are definitely the man you are my hero and my saver
It worked perfectly, I had installed ClockworkMod recovery and I don't know for which reason I wasn't being able to go on recovery, with TWRP recovery it worked like a charm and I now have my data back.
Once again, a thousand thanks for your precious help. If I can do anything for you don't hesitate, if I can help I'm here.
Click to expand...
Click to collapse
just hit my thanks button that's all
Fr33man76 said:
OK,
I did something really stupid. I was able to flash King Cobra 1.2 and my phone was working just fine but then after I wanted to install Sick Sense but it asked to do a reset factory and wipe system in recovery mode which I did. However, after I've wiped the system I don't have the rom on my sdcard anymore, actually it seems I have only the folder structure but no files in it.
I thought the wipe system would erase my rom on my SDCARD, how I don't know how to put the rom back to be able to flash the rom, when I plug the USB cable it asks me to Format, which I don't do of course but I can't see my phone on the explorer.
Is there a way to push the rom file into the phone other than via the windows explorer?
Thanks for your help.
Click to expand...
Click to collapse
flash addict already? lol
you should be able to go into twrp recovery, mounts, mount usb storage.
plug into pc, copy rom onto phone.
unmount usb, go back, wipe, flash, profit?
if when mounting your pc says it needs to format the sdcard... don't do it. do it from recovery. ive never tried formatting my sdcard "essentially its just a folder" yet with recovery but it shouldn't break anything.. you'll just lose everything on it.. sounds like you already have though.
Sent from my HTC One XL using xda premium
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
If I were you I would stay away from toolkits altogether. Not because they are bad, only because you learn absolutely nothing from using them and usually come bomb the threads when **** hits the fan.
The wire trick is a fun little task to handle though so everything should be okay that way.
Sent from my Nexus 4 using Tapatalk 2
Toolkit
ArachnydZ28 said:
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
Click to expand...
Click to collapse
His toolkit is still there, just browse around a bit... or go here... http://d-h.st/users/hasoon2000/?fld_id=2818#files
acwest said:
His toolkit is still there, just browse around a bit... or go here...
Click to expand...
Click to collapse
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
demkantor said:
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
unlocked
Doubleshot PVT Ship S-On RL
Hboot- 1.45.0013
Microp-0353
eMMC-Boot
Nov 21 2011, 20:20:47
I do have recovery and hboot. Stock backup won't load though even though the file is there in recovery.
Thanks!
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I was able to reflash a version of CM10 I was using for a while and that works, but I can't find a stock one that will work. I've tried multiple, and they all give me "bad" error and don't finish the install.
I was going to try a different version of CM10, 10.1, or go to a stable release of 9. If none of those worked, I'd be happier with stock. None of the ones I've tried will work, but I'm assuming thats because I'm S-On, but since I can't find hasoon2000s S-Off tool everyone was raving about, and the wire trick requires stock ROM based on what the directions say, I find myself in a pickle.
The CM10 version I have can't do some basic things I need for work- like sync with my bluetooth in the car or not randomly freeze up during the day without me knowing it sending all my calls to voicemail. I tried versions of the others that other people are using (like silverL's 10.1 and the CM-listed stable CM9) and neither would load.
Do I have a different issue? AKA are other people with S-On able to load those Roms? I can try miktouch too.
---
Also trying to load via fastboot and I'm getting this error:
"Whoops: didn't find expected signature
read_central_directory_entry_failed
error: failed to access zipdata in [Whole bunch of non-english characters taking up a few lines]"
----
Update: Just to clarify, when I try to install a stock rom it gives me "Can't open [filename] (bad)
However, when I try to install the CM's, it installs fine and says "Install from sdcard complete" they just won't load when I restart my phone, except for the original version of CM10. (for example, in all the 10.1s I've tried I get "Unfortunately, the process com.android.phone has stopped" but the intro page will load. I figured that came down to an S-On issue when I tried to troubleshoot.
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
ArachnydZ28 said:
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
Click to expand...
Click to collapse
negative.
miktouch would go through the install process, and end at the Tmobile mytouch 4g slide screen forever. I know on one install it took a long time to "load" the first time so I left it on this screen for about 15 minutes to no avail. Let me know if there is any chance of it taking longer than that. Reinstalls were the same story.
I got CM9.1 to install by installing it twice on top of itself (not sure why that fixes it) but it was a tiny bit buggy.
Is there any chance this could be bootloader related or recovery related? I can try to reload those too. grrr...
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
demkantor said:
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
ArachnydZ28 said:
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
Click to expand...
Click to collapse
You should try CWM 5.0.2.7. Also, since you are S-On you should extract the boot.img from Miktouch and flash it from fastboot, separately from the ROM. Since you have been on an ICS/Jellybean rom, I have to believe your original boot.img was replaced at some point. This is the only way to get back the Gingerbread boot.img. I am not savvy enough to know if this file is the bootloader or the kernel, but this process should get you back to stock-enough to do the wire trick.
Sent from my SGH-T699 using xda app-developers app
It's the kernel.....the boot.img file, I mean. The bootloader is that mostly white screen you see with "Hboot" at the top that will have "S-On" or "S-Off" after the word Radio. Good response.:good:
ArachnydZ28 said:
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Click to expand...
Click to collapse
Load the pd15img.zip on your sd card and boot to your bootloader. It should detect the file on your card and ask if you want to flash it. Just follow the directiins it gives you
Edit: actually should be pd59img not 15
Sent from my SGH-T889 using Tapatalk 2
I really screwed up, I was installing a new OP and was wiping Cache, Dalvik ect... when I accidently wiped my external storage. Well I mounted my SD card and put an OP back on the sd card, installed through TWRP and I'm just stuck in a boot loop. Have tried several differnt OP's and all I get is the boot loop. Can someone please help me correct what I screwed up. Everything is gone, when I look under Android secure there is nothing.
I'm not sure what you mean by OP? Maybe you mean ROM? Anyway you need to give more information, what are your bootloader details?
Sent from my Evita
timmaaa said:
I'm not sure what you mean by OP? Maybe you mean ROM? Anyway you need to give more information, what are your bootloader details?
Sent from my Evita
Click to expand...
Click to collapse
Your correct, I was half asleep when I posted my question. I do mean ROM. What kind of information from the bootloader would you like?
S-off
CID-111111111
HBOOT-1.09.0000
OpenDSP-v34.1.0.45.1219
Well you're s-off, so the boot.img isn't the problem. Which ROMs in particular have you tried installing? What version of TWRP are you using?
Sent from my Evita
timmaaa said:
Well you're s-off, so the boot.img isn't the problem. Which ROMs in particular have you tried installing? What version of TWRP are you using?
Sent from my Evita
Click to expand...
Click to collapse
VenomXL 4.0.0 Sense 5, VenomXL 3.2.7, HatkaXL-evita-v4.7.1. These are all ROM's that I have previously run on my phone. TWRP is v2.3.3.1.
Thank you for your help.
You might need to try running an RUU.
Sent from my Evita
timmaaa said:
You might need to try running an RUU.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaaa are you going for the record of "how many people can you help!" on the Evita forums :silly:
scrappy1959 listen to this guy as he knows what he is talking about! :laugh:
radavs said:
Hey timmaaa are you going for the record of "how many people can you help!" on the Evita forums :silly:
scrappy1959 listen to this guy as he knows what he is talking about! :laugh:
Click to expand...
Click to collapse
Lol I have a lot of spare time on my hands recently, I can't work right now due to health problems so I spend a lot of time on here. I've taken a lot from the XDA community over the years so I feel it's the right thing to do to try to give back and help people where my knowledge permits. I love learning, especially when it comes to Android and I think this is the best place to do it. I think the next step is to actually try to learn how to develop a ROM, but that'll have to wait until I get a new PC.
Sent from my Evita
---------- Post added at 02:37 PM ---------- Previous post was at 02:25 PM ----------
By the way, radavs, it's great to see you throw another Telstra ROM on here for the Aussies :thumbup:
Sent from my Evita
timmaaa said:
You might need to try running an RUU.
Sent from my Evita
Click to expand...
Click to collapse
What would be a good RUU and how would you flash it? I don't want to lose root. Went through to much to achive it.
Root isn't the thing you should be worried about, the unlocked bootloader and custom recovery are what you actually need to flash custom ROMs. All root does is give you administrative access to the root directories on your phone.
You are s-off so it doesn't matter which RUU you use, click the link in my signature and you'll find RUU links in there. Your bootloader will remain unlocked and you will retain your s-off status through the RUU process. You don't "flash" an RUU, it's an exe file so you run it like you would run any other exe program on a pc. An RUU returns your phone to being completely stock, including recovery, so you'll need to flash TWRP again afterwards.
Sent from my Evita
timmaaa said:
I have a lot of spare time on my hands recently, I can't work right now due to health problems so I spend a lot of time on here. I've taken a lot from the XDA community over the years so I feel it's the right thing to do to try to give back and help people where my knowledge permits.
Click to expand...
Click to collapse
I love this attitude, as this is what XDA is all about. Contribute however you can, whenever you can!
timmaaa said:
Root isn't the thing you should be worried about, the unlocked bootloader and custom recovery are what you actually need to flash custom ROMs. All root does is give you administrative access to the root directories on your phone.
You are s-off so it doesn't matter which RUU you use, click the link in my signature and you'll find RUU links in there. Your bootloader will remain unlocked and you will retain your s-off status through the RUU process. You don't "flash" an RUU, it's an exe file so you run it like you would run any other exe program on a pc. An RUU returns your phone to being completely stock, including recovery, so you'll need to flash TWRP again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Would you be willing to explain the steps of installing the RUU. I think I know, just don't want to screw that up also. Once I get that far I should be fine flashing TWRP.
No worries, it's an exe file so it's pretty easy. Put your phone into fastboot mode and connect it to your pc, then run the RUU exe program, it's as simple as that. Just follow the prompts on the pc, you just need to say ok a couple of times.
Just make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off.
Just make sure you don't disconnect your phone while the RUU is running, sometimes it might look like the process is freezing (it sat on 27% for a while when I did it) but just let it continue, it should be fine.
Sent from my Evita
timmaaa said:
No worries, it's an exe file so it's pretty easy. Put your phone into fastboot mode and connect it to your pc, then run the RUU exe program, it's as simple as that. Just follow the prompts on the pc, you just need to say ok a couple of times.
Just make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off.
Just make sure you don't disconnect your phone while the RUU is running, sometimes it might look like the process is freezing (it sat on 27% for a while when I did it) but just let it continue, it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Just tried running the RUU and it was not able to connect with my OneXL, it had been so long since I have done any of this I forgot when I was flashing TWRP almost a year ago, both my laptop and desktop were not able to connect to the phone, something to do with the USB ports (Windows 8). However, I have an old laptop with XP that will connect to the phone. I am leaving for work at this point and will not be able to run the RUU until late tonight. I will let you know how it works out. Thanks
scrappy1959 said:
Just tried running the RUU and it was not able to connect with my OneXL, it had been so long since I have done any of this I forgot when I was flashing TWRP almost a year ago, both my laptop and desktop were not able to connect to the phone, something to do with the USB ports (Windows 8). However, I have an old laptop with XP that will connect to the phone. I am leaving for work at this point and will not be able to run the RUU until late tonight. I will let you know how it works out. Thanks
Click to expand...
Click to collapse
Thanks so much timmaaa, got out my old windows xp laptop and the RUU is loading on the phone right now (@29%). For some reason my newer laptop and desktop will not put my phone into Fastboot USB. I think it has something to do with the newer technolgy of the high speed USB. But, soon as I hook up my old XP laptop it picks it up right away and switches into Fastboot USB. It's done, now all I have to do is put TWRP back on the phone and I should be back in business. Thanks
Okay, I ran the new RUU 1.85. I can't seem to get TWRP installed. I downloaded super user# and it says I do not have root. However when I boot into bootloader it says
***UNLOCKED***
EVITA PUT SHIP S-OFF RL
CID-111111111
HBOOT-2.14.0000
S
Didn't think I would need help getting TWRP reinstalled but I do. If you could give me a little more help getting TWRP back on my phone. Thank you
scrappy1959 said:
Okay, I ran the new RUU 1.85. I can't seem to get TWRP installed. I downloaded super user# and it says I do not have root. However when I boot into bootloader it says
***UNLOCKED***
EVITA PUT SHIP S-OFF RL
CID-111111111
HBOOT-2.14.0000
S
Didn't think I would need help getting TWRP reinstalled but I do. If you could give me a little more help getting TWRP back on my phone. Thank you
Click to expand...
Click to collapse
I forgot, the phone is just unlocked. I need to re-ROOT. Thanks for your help.
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita
timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita
roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita
Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?
Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.
timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?
For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.