Please help.
I was trying to root the phone and keep the stock rom.
I used Hansoon's AIO kit for the HOX+ . I successfully unlocked the bootloader and I flashed the CWM (INTL model) firmware.
I successfully booted into the ROM where I had to set it up.
I rebooted afterwards and now it is stuck at the HTC boot screen.
I CAN get into CWM recovery.
I am just wondering how I should proceed from here.
Should I have flashed a custom kernel? I didn't htink so because I am keeping stock.
SHould I have flashed the ATT TWRP?
Thanks.
mfpreach said:
Please help.
I was trying to root the phone and keep the stock rom.
I used Hansoon's AIO kit for the HOX+ . I successfully unlocked the bootloader and I flashed the CWM (INTL model) firmware.
I successfully booted into the ROM where I had to set it up.
I rebooted afterwards and now it is stuck at the HTC boot screen.
I CAN get into CWM recovery.
I am just wondering how I should proceed from here.
Should I have flashed a custom kernel? I didn't htink so because I am keeping stock.
SHould I have flashed the ATT TWRP?
Thanks.
Click to expand...
Click to collapse
Find the RUU for your phone and run that. And yes you need to flash the ATT TWRP for the Telus model and also use a ATT - Telus ROM. After you run the RUU you can try again.
trannygranny said:
Find the RUU for your phone and run that. And yes you need to flash the ATT TWRP for the Telus model and also use a ATT - Telus ROM. After you run the RUU you can try again.
Click to expand...
Click to collapse
Ok, that's what I thought now.
Do you know where I can find the TElus RUU? I can't seem to find it.
THanks.
Figured out I need to sideload...
After it installed via sideload it was still stuck, I eventually just went into TWRP and reflashed the sideload.zip and it works now.
mfpreach said:
Figured out I need to sideload...
After it installed via sideload it was still stuck, I eventually just went into TWRP and reflashed the sideload.zip and it works now.
Click to expand...
Click to collapse
I'm stuck at the "HTC quietly brilliant" boot screen - can you outline what you did to get around this?
I grabbed the teamwin AT&T openrecovery image and fastbooted/flashed it, but what do you do after that?
Crankycoder said:
I'm stuck at the "HTC quietly brilliant" boot screen - can you outline what you did to get around this?
I grabbed the teamwin AT&T openrecovery image and fastbooted/flashed it, but what do you do after that?
Click to expand...
Click to collapse
I screwed up at one point, I actually didn't want to flash a custom rom, but only wanted to root stock. I ended up having to flash a custom rom since there is not Telus RUU available.
ANYWAYS,
Assuming that you have unlocked your bootloader,
Download a Rom and flash the kernel via fastboot.
The next problem is how to get the rom onto the phone in order to flash it because i spent 3 hours trying to figure out how to mount the phone and found out that you can't.
SO in order to flash a rom you need to use adb sideload.
In TWRP there is that option, then you just adb sideload romname.zip
At this point it installed the rom, ran aroma etc.. For some reason mine was still frozen. If this happens to you, just go into TWRP and install the sideload.zip , this will install the rom again.
Goodluck.
I wrote what I did to solve the same problem when I had the same issue. Check under my stats for my posts somewhere here on the forums...
Hope it helps.
Sent from my HTC One X+ using xda premium
gamepr said:
I wrote what I did to solve the same problem when I had the same issue. Check under my stats for my posts somewhere here on the forums...
Hope it helps.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
For some reason my adb push wasn't working, I for sure tried that first.
Sideload did though.
gamepr said:
I wrote what I did to solve the same problem when I had the same issue. Check under my stats for my posts somewhere here on the forums...
Hope it helps.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Just wanted to make sure - this post?
http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
Crankycoder said:
Just wanted to make sure - this post?
http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
Click to expand...
Click to collapse
Just use sideload in twrp it will install it for you also right after you push it.
Crankycoder said:
Just wanted to make sure - this post?
http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
Click to expand...
Click to collapse
I grabbed the stock ROM from this msg - http://forum.xda-developers.com/showpost.php?p=34428702&postcount=1
1. Extracted the boot.img
2. flashed the boot.img with:
$ fastboot flash boot boot.img
sending 'boot' (8191 KB)...
OKAY [ 1.232s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.464s]
finished. total time: 1.695s
3. Then used TW recovery to try to side load the zip file, but I get a failure to install.
I assume I'm doing something really stupid here. If someone can just point out what - that'd be awesome.
In the meantime, I'm going to try with the QX Senseless 2.0 rom as per the instructions in: http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
thanks!
vic
Crankycoder said:
I grabbed the stock ROM from this msg - http://forum.xda-developers.com/showpost.php?p=34428702&postcount=1
1. Extracted the boot.img
2. flashed the boot.img with:
$ fastboot flash boot boot.img
sending 'boot' (8191 KB)...
OKAY [ 1.232s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.464s]
finished. total time: 1.695s
3. Then used TW recovery to try to side load the zip file, but I get a failure to install.
I assume I'm doing something really stupid here. If someone can just point out what - that'd be awesome.
In the meantime, I'm going to try with the QX Senseless 2.0 rom as per the instructions in: http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
thanks!
vic
Click to expand...
Click to collapse
Yeah I dunno then.
I used Elegancia and the kernel from that rom.
Out of interest, did you flash the ATT twrp or the int'l one? I am on telus and originally flashed int'l (Because Canada isn't part of the US even though many may think it is) , and that was wrong. If you are on Telus you must flash the ATT twrp.
Turns out that the stock rom I linked earlier must be corrupt. I'm using qx senseless 2.1 with no problems after flashing with TWRP.
We should probably have a list of rims that have been verified to work.
So, were my instructions good for you to recover? Sounds like it.....but i just want to make sure
Crankycoder said:
Turns out that the stock rom I linked earlier must be corrupt. I'm using qx senseless 2.1 with no problems after flashing with TWRP.
We should probably have a list of rims that have been verified to work.
Click to expand...
Click to collapse
Yes!
I used the qx senseless 2.0 rom and everything worked just fine.
Thanks a bunch!
Vic
Sent from my HTC One X+ using xda app-developers app
Related
Help! My DNA isn't working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldn't mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Edit: Phone is now fixed, I went to IRC and a guy named Beaups took remote control and fixed it. Im not sure if thats his XDA username or not but if you guys see him make sure to give him a thanks Night everyone
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Its ok its very fixable, at this point. Just be very careful and very patient.
The worst thing you can do with something like this is get in a hurry or try to fix it while you're still very stressed out.
I'm passing on this advice because I almost screwed up yesterday because I made a boo boo and was in a huge hurry.
I'm going to wait for someone who knows more about this particular issue to chime in, but you have my word, I will help you resolve it after I do some more research while I wait for someone with more information or experience to post some info.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
In the original unlock downloader thread, there is a link to an irc chatroom, I would suggest you go there as well as look for help here, and be patient waiting for some one to respond ...
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Click to expand...
Click to collapse
Thats pretty much what I did but I keep getting that error:178 image file problem when its trying to finish (I am using the RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe RUU) Also my phone is recognized as 2.04 when I haven't flashed anything
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Re-Unlock your bootloader with your Unlock token (Unlock_code.bin) then do a fastboot flash recovery recovery.img and use the CWM recovery that is 6.0.2.8 (i believe is the most recent version) and you should be able to sideload your rom ... or if sideloading doesnt work just do an adb push rom.zip /sdcard/rom.zip and that will put the rom that you want to use on the root of the sdcard and then you can flash that there...
This should hopefully get you working again...
beasleyj62 said:
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Click to expand...
Click to collapse
I keep getting this when I flash the hboot
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.205s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.274s
and when I flash the Radio I get
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
error: cannot load 'PL83IMG.zip': Unknown error
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
beasleyj62 said:
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
Click to expand...
Click to collapse
I can unlock it at anytime....
see if you can flash after you unlock again
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
All I needed to run the RUU was the ENG Hboot. Flash it then you should be able to install the RUU provided you have the correct drivers installed.
Sent from my HTC6435LVW using xda app-developers app
He is still s-on.
Sent from my HTC Droid DNA
Andro X said:
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
How would I go about doing that?
beasleyj62 said:
see if you can flash after you unlock again
Click to expand...
Click to collapse
I didnt work. This is my 2nd DNA so I have done this before and it worked successfully(The first one had a screen problem)
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Halcyon7 said:
How would I go about doing that?
Click to expand...
Click to collapse
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
beasleyj62 said:
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I only found 1 link on my computer doctors forum but that link wasn't it
.torrented said:
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
Click to expand...
Click to collapse
No I haven't. I used the s-off facepalm method and I did everything as it said and now when I went into recovery nothing will mount and my device when trying to use the RUU says its a 2.04. So I didnt take the ota but thats what it is recognized as
I've been trying to root my EVO 4G LTE using various guides from this board, and I'm not having a lot of luck. I have HBOOT 2.09 and it's S-ON. It seems like the easiest way to root the device is to go S-OFF, but then it appears that the device needs to be rooted to get S-OFF. So I'm a little confused at this point. I've unlocked the bootloader and installed TWRP, but when I try to install the SuperSU root utility it gives me an error about mounting partitions and fails. My bootloader screen also displays "TAMPERED" which seems to be a problem but I'm not having a lot of luck finding a way to resolve it.
So... can anyone tell me what my next step is?
Thanks in advance.
Are you using Facepalm, Moonshine, or DirtyRacun? You haven't really provided enough details to help, at this point. What's your software version? I assume you're running the stock ROM?
I was running the stock ROM, I think it was 3.16. I tried using Facepalm but again it seems like it needs root to work which I haven't been able to achieve just yet. I tried installing the ROM from this thread through TWRP but it just hangs on the HTC screen so I'm not sure what's on there now. I can still get into the bootloader and recovery though.
You can't use Facepalm on 3.16 software. Use Moonshine.
Try flashing this stock rooted to get back to a working state: http://d-h.st/users/Captain_Throwback/?fld_id=10308#files
You may need to fastboot flash the boot.img to make sure it fully boots.
OK, I downloaded that ROM and extracted the boot.img. I booted the phone into the bootloader and ran "fastboot flash boot boot.img". It seems to have completed correctly, no errors at least, but now the phone just sits at the HTC screen with the red text at the bottom. Clearly I'm doing something wrong...
Did you flash the ROM too? Or did it reboot on you when you tried?
I just did the boot.img. Should I also do "fastboot flash zip 3.16.651.3_stock_rooted_odex_CPTB.zip"?
davel23 said:
I just did the boot.img. Should I also do "fastboot flash zip 3.16.651.3_stock_rooted_odex_CPTB.zip"?
Click to expand...
Click to collapse
You have to flash the ROM in recovery.
Ok, so I went into recovery which is still TWRP, adb pushed that ROM to the phone then tried to install it. It gives a bunch of error messages about being unable to mount various items, says it's unable to find path for partition [name of the zip] and fails.
Thanks for your help and patience so far...
You do not extract the file, leave it as a zip and do not open it. Move it to your SD card while in fastboot (mount sd) and from there use twrp and select the correct zip to flash. But above all... DO NOT EXTRACT THE FILR
Sent from my EVO using xda app-developers app
roscoepcoltra said:
You do not extract the file, leave it as a zip and do not open it. Move it to your SD card while in fastboot (mount sd) and from there use twrp and select the correct zip to flash. But above all... DO NOT EXTRACT THE FILR
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
He's S-on. He can't flash kernels from recovery with Hboot 2.09.
davel23 said:
Ok, so I went into recovery which is still TWRP, adb pushed that ROM to the phone then tried to install it. It gives a bunch of error messages about being unable to mount various items, says it's unable to find path for partition [name of the zip] and fails.
Thanks for your help and patience so far...
Click to expand...
Click to collapse
I don't understand what you're doing here. Boot to recovery, mount storage, copy the ROM zip over, and then flash it.
Ok, so I mounted storage from recovery, or least I tried to, my PC said it needed to be formatted. So I did so, copied the file over and flashed it which completed successfully this time. My phone now boots properly, I'll give Moonshine a try now. Hopefully I won't need to bug you again, thanks for all the help.
Captain_Throwback said:
You can't use Facepalm on 3.16 software. Use Moonshine.
Try flashing this stock rooted to get back to a working state: http://d-h.st/users/Captain_Throwback/?fld_id=10308#files
You may need to fastboot flash the boot.img to make sure it fully boots.
Click to expand...
Click to collapse
my friend wants to buy im rooted unlocked evo. it is on viper now can I flash this an it will be stock rooted ?
Tigerstown said:
my friend wants to buy im rooted unlocked evo. it is on viper now can I flash this an it will be stock rooted ?
Click to expand...
Click to collapse
Yes.
Captain_Throwback said:
Yes.
Click to expand...
Click to collapse
S-on Ok? Or do I need to moonshine first?
Tigerstown said:
S-on Ok? Or do I need to moonshine first?
Click to expand...
Click to collapse
You need to use Flash Image GUI or fastboot flash the kernel.
FinZ28 said:
You need to use Flash Image GUI or fastboot flash the kernel.
Click to expand...
Click to collapse
Ok I got that app I use that. An for my other one I'm selling is s-off so I can just flash this on that one..it's been fun on the Evo with the helpful fellow xda's on the jewel. But the wife's work now cover half your bill if you have verizon so we had no choice
Captain_Throwback said:
Yes.
Click to expand...
Click to collapse
Omg I just moonshine(easy thing I ever did) this phone my wife didn't want s-off before. So now I'm s-off I will just flash thanks once again throwback. Hope there is someone in vzw htc one thread that breaks down firmware like you.
Sent from my EVO using XDA Premium 4 mobile app
I'm having a little trouble with Moonshine. It reboots the phone a couple of times, gets to step 3 then just keeps printing periods in the program window. I've been reading through the Moonshine thread and it seems other people have had the same problem, but I haven't seen a solid fix yet. Anyone know what I need to do or should I stick with the Moonshine thread?
I Have an Htc one X+ of coarse, and recently rooted it for the first time. After finding my way through that process fairly easily, I decided to try to flash a custom rom (Android Revolution HD 8.0). However I didn't put the necessary zip file in the internal storage before putting the phone in fastboot and flashing the new boot image. After that my phone entered bootloop or atleast i think its a bootloop. It basically just shows the htc quietly brilliant splash screen and sits there till i try to turn it off and then it goes off and then turns itself back on and repeats. However I can get it to fastboot and in to trwp recovery. So I have no back up of my original boot.img soo i just googled factory JB boot.img 4.1.1 and flashed that and cleared both caches and rebooted through twrp. Still bootlooped, so while reading on these froums i read that i should do a wipe of everything i did that so now i have no os at the moment. But after reading a post about a similar problem had by a galaxy user they flashed there there new custom rom boot.img and used adb to push the .zip file to internal storage however when i tryed to use the same command text they used it simply said device not found. so I'm at a loss for what to try next. I'm very Sorry for the long post but, any help at all would be appreciated.
P.S: Sorry for not being smart enough to find the answer on my on, thanks for your help in advance.
The boot.img you googled? Was it even for the HOX+ or just any JB boot.img?? You should be careful flashing any old boot.img could lead to corruption of the boot partition...
Anyway just for info sake, this isnt a bootloop, your device just isnt booting. There are two things you can do in this situation....
1) look in the android dev section for a stockish 4.1.1 rom. You just need one from a rom that isn't heavily modded like insertcoin or viper. You could also grab one of the custom sense kernels from the original android dev section..
2) You could flash the kernel you did originally, then boot into recovery and sideload the right rom to your device.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
The boot.img you googled? Was it even for the HOX+ or just any JB boot.img?? You should be careful flashing any old boot.img could lead to corruption of the boot partition...
Anyway just for info sake, this isnt a bootloop, your device just isnt booting. There are two things you can do in this situation....
1) look in the android dev section for a stockish 4.1.1 rom. You just need one from a rom that isn't heavily modded like insertcoin or viper. You could also grab one of the custom sense kernels from the original android dev section..
2) You could flash the kernel you did originally, then boot into recovery and sideload the right rom to your device.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Thanks very much for the info and help I hope i didn't corrupt it. and I've never flashed a kernel before but Im sure i can find a tutorial. as long as I dont have to put any thing on internal memory sounds good to me. I guess sense I didn't have a kernal (atleast that i know of) the first time i guess i'll try 1. srry 4 being a noob btw.
EDIT: can i flash a rom from the computer without it being in internal storage?
joebee_2004 said:
Thanks very much for the info and help I hope i didn't corrupt it. and I've never flashed a kernel before but Im sure i can find a tutorial. as long as I dont have to put any thing on internal memory sounds good to me. I guess sense I didn't have a kernal (atleast that i know of) the first time i guess i'll try 1. srry 4 being a noob btw.
EDIT: can i flash a rom from the computer without it being in internal storage?
Click to expand...
Click to collapse
Try booting the boot.img file manually from the ROM you downloaded (find it inside the zip)
you can do that by the fastboot method using your PC
Do this when you enter the bootloader menu.
"fastboot flash boot boot.img"
joebee_2004 said:
Thanks very much for the info and help I hope i didn't corrupt it. and I've never flashed a kernel before but Im sure i can find a tutorial. as long as I dont have to put any thing on internal memory sounds good to me. I guess sense I didn't have a kernal (atleast that i know of) the first time i guess i'll try 1. srry 4 being a noob btw.
EDIT: can i flash a rom from the computer without it being in internal storage?
Click to expand...
Click to collapse
Sorry just to clarify. A kernel and a boot.img are the same thing. Depending on your hboot version and CID. There may be an RUU you can run from your PC to install stock firmware.
You can get your hboot version on your bootloader screen, and get your CID by using the fastboot command "fastboot getvar cid".
If we knew those maybe we could help finding the correct RUU (if there is one).
Sent from my HTC One X+ using Tapatalk 2
If you are trying to flash a custom ROM, then you could just sideload. TWRP (and some other recoveries) supports a process called sideload for when you forget to copy your ROM zip onto the internal storage - since phones like the HOX+ dont have a micro-SD slot for removable storage. Just google for sideload - plenty of tutorials.
The custom ROM zip will also contain the appropriate boot.img, so after flashing the ROM, all you then need to do is flash the boot.img. Hopefully all should be well then.
AndroHero said:
Sorry just to clarify. A kernel and a boot.img are the same thing. Depending on your hboot version and CID. There may be an RUU you can run from your PC to install stock firmware.
You can get your hboot version on your bootloader screen, and get your CID by using the fastboot command "fastboot getvar cid".
If we knew those maybe we could help finding the correct RUU (if there is one).
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
cid: CWS_001
HBOOT: 1.32.0000
Also I'd like to mention I've tired to push a file to my storage using fastboot and adb, but adb didnt recognize my device was there, although i haven't tired running trwp and the sideloading method yet so i guess I'll try that next.
EDIT: ok I managed to sideload the custom Android Revolution HD custom rom and it flashed it as soon as it was loaded to the phone however after flashing it. it just continued to say I had no os. does this mean like you mentioned be4 that my boot thing is corrupted?
joebee_2004 said:
cid: CWS_001
HBOOT: 1.32.0000
Also I'd like to mention I've tired to push a file to my storage using fastboot and adb, but adb didnt recognize my device was there, although i haven't tired running trwp and the sideloading method yet so i guess I'll try that next.
EDIT: ok I managed to sideload the custom Android Revolution HD custom rom and it flashed it as soon as it was loaded to the phone however after flashing it. it just continued to say I had no os. does this mean like you mentioned be4 that my boot thing is corrupted?
Click to expand...
Click to collapse
Did you extract the boot.img from the android revolution .zip and flash it through fastboot?
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Did you extract the boot.img from the android revolution .zip and flash it through fastboot?
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
The boot image and zip folder were separate I loaded the boot image manually be4 flashing the rom through side loading. and also I reloaded the boot.img after it regestered no os after flashing but it still registers as no OS so If the boot.img is loaded i should have an os according to twrp right?
also I took the SIM card out and put it in a backup phone for now that wouldn't be a problem correct? thanks again for all the advice.
joebee_2004 said:
The boot image and zip folder were separate I loaded the boot image manually be4 flashing the rom through side loading. and also I reloaded the boot.img after it regestered no os after flashing but it still registers as no OS so If the boot.img is loaded i should have an os according to twrp right?
also I took the SIM card out and put it in a backup phone for now that wouldn't be a problem correct? thanks again for all the advice.
Click to expand...
Click to collapse
Are you definitely not trying to flash international roms? Because the CWS CID is AT&T right? Maybe you should just flash an RUU. I don't know if there are any for the AT&T version. Maybe one of the American members can help..
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Are you definitely not trying to flash international roms? Because the CWS CID is AT&T right? Maybe you should just flash an RUU. I don't know if there are any for the AT&T version. Maybe one of the American members can help..
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
yes it is an AT&T phone, well Thank you for trying to help me anyway, I will look up an ruu tutorial next.
Did you factory wipe before doing the sideload? and I am not clear on what you mean by
....it still registers as no OS
Click to expand...
Click to collapse
Where doesnt it register as an OS?
surfatwork said:
Did you factory wipe before doing the sideload? and I am not clear on what you mean by
Where doesnt it register as an OS?
Click to expand...
Click to collapse
In Twrp it says there is no OS installed. right before reboot. even tho I loaded a boot.img and sideloaded a zip and flashed it. after flashing and every thing it still says no OS installed. but i went ahead and rebooted it anyway but it just sits at the HTC quietly brillant screen.
Thanks for the advice about the factory restore i didnt do it right be4 installing maybe i'll try that.
1. I notice that you say you flashed Android Revolution. afaik, that ROM is for the International version, not for AT&T. Have you checked you are using an appropriate ROM?
2. I am assuming you did the sideload procedure correctly? Did the ROM installation start after it finished copying over the ROM to the phone?
surfatwork said:
1. I notice that you say you flashed Android Revolution. afaik, that ROM is for the International version, not for AT&T. Have you checked you are using an appropriate ROM?
2. I am assuming you did the sideload procedure correctly? Did the ROM installation start after it finished copying over the ROM to the phone?
Click to expand...
Click to collapse
yes it did installed apps and things then when it was finished i was still in twrp in sideboot and it said reboot. but it still didn't register an OS. hmm maybe I should look specifically for an at&t custom rom. thank s for the advice.
To cut the story short, my EVO was working fine, it was S-off, Rooted, Unlocked with a custom rom. Two nights ago i decide to upgrade my HBOOT to 2.10 using RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4 and everything went downhill from there.
This is my current situation and wondering if it's still fixable:
Phone is RELOCKED,Unrooted but S-off. Stuck in a bootloop where it stays on the Splash screen no matter what rom you install. FastBoot commands give me FAILED (remote : not allowed), tried re-using RUU but I keep getting Error 120: BATTERY under 30% while my phone battery is at 84%, I'm stuck and don't know what to do anymore.
and yes, I can still use recovery TWRP.
Any suggestions? Please and thanks for the help.
TheRedFlash said:
To cut the story short, my EVO was working fine, it was S-off, Rooted, Unlocked with a custom rom. Two nights ago i decide to upgrade my HBOOT to 2.10 using RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4 and everything went downhill from there.
This is my current situation and wondering if it's still fixable:
Phone is RELOCKED,Unrooted but S-off. Stuck in a bootloop where it stays on the Splash screen no matter what rom you install. FastBoot commands give me FAILED (remote : not allowed), tried re-using RUU but I keep getting Error 120: BATTERY under 30% while my phone battery is at 84%, I'm stuck and don't know what to do anymore.
and yes, I can still use recovery TWRP.
Any suggestions? Please and thanks for the help.
Click to expand...
Click to collapse
Are you installing roms for the new layout
Sent from my EVO using XDA Free mobile app
Also, did you unlock the bootloader again? Do this before you do anything else. Also, as stated above, make sure you're flashing ROM's based on the new format. ROM's based on the old partition format (software version 3.17 or older) will not work. Additionally, what version of TWRP are you using? You have to use TWRP that's for the new format, also.
Sent from my HTC device
gstanke said:
Are you installing roms for the new layout
Click to expand...
Click to collapse
Yea and I updated the HBOOT because people usually say that updating is for the better for call qualities and signal retrieval.
Magnum_Enforcer said:
Also, did you unlock the bootloader again? Do this before you do anything else. Also, as stated above, make sure you're flashing ROM's based on the new format. ROM's based on the old partition format (software version 3.17 or older) will not work. Additionally, what version of TWRP are you using? You have to use TWRP that's for the new format, also.
Click to expand...
Click to collapse
No, I haven't attempted to unlock it again, but will do so now. Also, these are the two roms that i have tried and both didn't work Viper4G 4.0.0 and the Sense 5 (4.3) Y18 Version. They are both made for the new partition. Well i started with TWRP 2.7.0.0b but then downgraded it to 2.6.0.0 since i thought maybe the TWRP is failing to install my ROM's correctly.
TheRedFlash said:
No, I haven't attempted to unlock it again, but will do so now. Also, these are the two roms that i have tried and both didn't work Viper4G 4.0.0 and the Sense 5 (4.3) Y18 Version. They are both made for the new partition. Well i started with TWRP 2.7.0.0b but then downgraded it to 2.6.0.0 since i thought maybe the TWRP is failing to install my ROM's correctly.
Click to expand...
Click to collapse
Use TWRP from the 3rd post in the thread below:
http://forum.xda-developers.com/showthread.php?t=2751873
Sent from my HTC device
Magnum_Enforcer said:
Use TWRP from the 3rd post in the thread below:
http://forum.xda-developers.com/showthread.php?t=2751873
Click to expand...
Click to collapse
So far so good, I was able to unlock bootloader again and flashed the recovery you gave me. Should I flash a ROM now to see if it worked?
*Tip for those who can't get bootloader to re-unlock again through Fastboot. Put the Unlock_code.bin in the same directory as Fastboot and just use the command fastboot flash unlocktoken unlock_code.bin*
UPDATE:
Tried flashing a ROM, everything goes well but at the end of installation or wipe I get E: unable to mount /system and I cannot mount manually neither through recovery. I am also noticing that when the phone restarts it stays on the splash screen still but my HTCSyn Manager seems to be detecting it because it pops up mentioning that it couldn't connect to my phone.
TheRedFlash said:
So far so good, I was able to unlock bootloader again and flashed the recovery you gave me. Should I flash a ROM now to see if it worked?
*Tip for those who can't get bootloader to re-unlock again through Fastboot. Put the Unlock_code.bin in the same directory as Fastboot and just use the command fastboot flash unlocktoken unlock_code.bin*
UPDATE:
Tried flashing a ROM, everything goes well but at the end of installation or wipe I get E: unable to mount /system and I cannot mount manually neither through recovery. I am also noticing that when the phone restarts it stays on the splash screen still but my HTCSyn Manager seems to be detecting it because it pops up mentioning that it couldn't connect to my phone.
Click to expand...
Click to collapse
I got that error too, it sounds like you are not using the correct version of TWRP for the new partition layout.
http://forum.xda-developers.com/showthread.php?t=2639180
TWRP Recovery 2.7.0.8b or 4.13.651.4 Firmware + TWRP Recovery
Should work.
RChris173 said:
I got that error too, it sounds like you are not using the correct version of TWRP for the new partition layout.
http://forum.xda-developers.com/showthread.php?t=2639180
TWRP Recovery 2.7.0.8b or 4.13.651.4 Firmware + TWRP Recovery
Should work.
Click to expand...
Click to collapse
Chris, I got it working this morning, by coincidence/luck. I put my phone in RUU mode using fastboot oem rebootRUU and then ran the actually RUU utility and from there on it took off. Either way, thanks for you reply man, it'll probably help someone when they encounter this situation.
Im having a difficult time getting back to stock
downloaded the stock files from this thread: http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966
but the following happened :
ive had a botched attempt at updating the firmware and installing venomone.
i tried installing these via the all in one kit but it didnt work, it had me try relocking my bootloader and still didnt work.
so now im stuck with a relocked bootloader, and cant figure out how to get back to stock =/
edit: i managed to get the phone back to stock using this ruu
http://forum.xda-developers.com/showthread.php?t=2757462
so now, how can i unlcok my bootloader again?
whei try using htc devs methood
"fastboot flash unlocktoken Unlock_code.bin"
i get the message
"target reported max download size of 1830580224 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.128s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.149s
"
also from here which verision of twrp is the propper one? (att m8), and which firmware shoudl i upgrade to for venom rom to be compatible (also do i need to super cid again?)
Did you tried to get a new token From HTC ? Or you using the old one?
JEANRIVERA said:
Did you tried to get a new token From HTC ? Or you using the old one?
Click to expand...
Click to collapse
tried using the old one
edit:woohoo new token worked, not with the one click tool, but it worked when i used
"fastboot flash unlocktoken Unlock_code.bin"
I'm glad I was able to help!!!
JEANRIVERA said:
I'm glad I was able to help!!!
Click to expand...
Click to collapse
appreciate it, never would have thought of that
(i always assumed youd get the same token if you re-ran the process with the same phone)
The_Zodiac said:
ive had a botched attempt at updating the firmware and installing venomone.
Click to expand...
Click to collapse
Ditch the toolkit, brother. It has been a point of failure in itself for at least a few folks, so better to just remove it from the equation and flash things manually by adb/fastboot.
redpoint73 said:
Ditch the toolkit, brother. It has been a point of failure in itself for at least a few folks, so better to just remove it from the equation and flash things manually by adb/fastboot.
Click to expand...
Click to collapse
yeah very likely a good idea. i ended up manually flashing it and it seemed to have actually worked.
i finally managed to get venomone to work
for some reason every time i wipe (either in twrp and or in aroma ) it wont work correctly,
but i dirty flashed it over the failed attempt (with wipe) and it works for some reason weird
The_Zodiac said:
for some reason every time i wipe (either in twrp and or in aroma ) it wont work correctly,
but i dirty flashed it over the failed attempt (with wipe) and it works for some reason weird
Click to expand...
Click to collapse
I never wipe in AROMA. Might just be an old habit from One X (EVITA) days (where AROMA wipes caused some major problems) and those bugs might not exist on this phone. But wipes in TWRP have never caused issues for me.
Make sure you are on the latest TWRP. Maybe wipe cache in fastboot and re-install TWRP to see if its just not a faulty TWRP install.
redpoint73 said:
I never wipe in AROMA. Might just be an old habit from One X (EVITA) days (where AROMA wipes caused some major problems) and those bugs might not exist on this phone. But wipes in TWRP have never caused issues for me.
Make sure you are on the latest TWRP. Maybe wipe cache in fastboot and re-install TWRP to see if its just not a faulty TWRP install.
Click to expand...
Click to collapse
I ended up figuring out what the problem was, one of the apps I was removing was causing the problem.
After I didn't select the "remove apps" option it booted no problem