Does anyone happen to have a Rogers RUU?
Nope, the Telus RUU works fine on Rogers though. They use the exact same modem firmware so the only difference would be the crap apps they bundle.
mrplowdan said:
Nope, the Telus RUU works fine on Rogers though. They use the exact same modem firmware so the only difference would be the crap apps they bundle.
Click to expand...
Click to collapse
I'm trying to fix my bricked HTC Desire 601 with Rogers, and I tried the Telus RUU 4.2.2 and it failed with "Model ID error".
The thing is I think I bought my phone with 4.4.2 update already on it and that might be causing the error.
So I wanted to try using RUU for 4.4.2, but it's not available. What should I do ?
I can lock/unlock bootloader, i'm S-ON so no ROM flashing....
Thanks for any help.
black-venomz said:
I'm trying to fix my bricked HTC Desire 601 with Rogers, and I tried the Telus RUU 4.2.2 and it failed with "Model ID error".
The thing is I think I bought my phone with 4.4.2 update already on it and that might be causing the error.
So I wanted to try using RUU for 4.4.2, but it's not available. What should I do ?
I can lock/unlock bootloader, i'm S-ON so no ROM flashing....
Thanks for any help.
Click to expand...
Click to collapse
Sorry dude, I'd flash twrp and try to flash insert coin. Good luck. I sold this crappy phone and bought a used nexus 5. No more BS.
mrplowdan said:
Sorry dude, I'd flash twrp and try to flash insert coin. Good luck. I sold this crappy phone and bought a used nexus 5. No more BS.
Click to expand...
Click to collapse
InsertCoin is the reason I'm in this s*h*i*t*hole in the first place. I'm S-ON so it's not possible.
Thanks anyway.
black-venomz said:
InsertCoin is the reason I'm in this s*h*i*t*hole in the first place. I'm S-ON so it's not possible.
Thanks anyway.
Click to expand...
Click to collapse
Even if your s-on you can still flash twrp and install roms. You bought your phone new and it already had 4.4.2? Go to the bootloader and check to see what your hboot version is. Although I sold the phone I'll step you through.
mrplowdan said:
Even if your s-on you can still flash twrp and install roms. You bought your phone new and it already had 4.4.2? Go to the bootloader and check to see what your hboot version is. Although I sold the phone I'll step you through.
Click to expand...
Click to collapse
I've tried flashing multiple ROMs (custom and roms apparently stock).
The flash went well but after reboot the bootloop was still there (it probably never installed in the first place).
My hboot version is : 2.20.0000
I already have TWRP installed.
What should I do ?
Thank you for the help.
black-venomz
black-venomz said:
My hboot version is : 2.20.0000
Click to expand...
Click to collapse
Theres your issue, thats the jb hboot. First off make sure your twrp is the correct version. Boot into recovery and mount data and system and use the file browser to make sure its mounting properly. You'll have to find a twrp backup or flashable zip of 4.2.2. Once your back up and running s-off that sucker. Then change your mid to telus' and run the ruu. Then just ota as normal.
mrplowdan said:
Theres your issue, thats the jb hboot. First off make sure your twrp is the correct version. Boot into recovery and mount data and system and use the file browser to make sure its mounting properly. You'll have to find a twrp backup or flashable zip of 4.2.2. Once your back up and running s-off that sucker. Then change your mid to telus' and run the ruu. Then just ota as normal.
Click to expand...
Click to collapse
Couldn't find any TWRP backup for Zara_UL. Only one for Zara_CL.
The flashable zip, is it the one from HTCDev website ? Because there is one for my device.
If not, could you point out where I could find such thing ?
You have to understand I have tried many many things already and I'm kind of tired of it so sorry for all the lame questions .
Here my thread if you want to check it out : http://forum.xda-developers.com/android/help/soft-bricked-htc-desire-601-zaraul-s-t2893035/post55799596#post55799596
black-venomz said:
Couldn't find any TWRP backup for Zara_UL. Only one for Zara_CL.
The flashable zip, is it the one from HTCDev website ? Because there is one for my device.
If not, could you point out where I could find such thing ?
You have to understand I have tried many many things already and I'm kind of tired of it so sorry for all the lame questions .
Here my thread if you want to check it out : http://forum.xda-developers.com/and...1-zaraul-s-t2893035/post55799596#post55799596
Click to expand...
Click to collapse
No not from HTC dev. Try this http://forum.xda-developers.com/des...lockworksenseless-4-2-2-4-4-2-coming-t2845247
Have you checked to ensure twrp is mounting your partitions correctly?
mrplowdan said:
No not from HTC dev. Try this http://forum.xda-developers.com/des...lockworksenseless-4-2-2-4-4-2-coming-t2845247
Have you checked to ensure twrp is mounting your partitions correctly?
Click to expand...
Click to collapse
Now that you mention it, I have often seen the errors :
Unable to mount /system
Unable to mount /data
I just tried mount with TWRP and I can't even select System and Date (you have to check the box, and it won't let me check it).
Tried mounting with CWM and can't mount.
I thought that was the point of S-ON ? That you can't access and write in the system partition ?
black-venomz
black-venomz said:
Now that you mention it, I have often seen the errors :
Unable to mount /system
Unable to mount /data
I just tried mount with TWRP and I can't even select System and Date (you have to check the box, and it won't let me check it).
Tried mounting with CWM and can't mount.
I thought that was the point of S-ON ? That you can't access and write in the system partition ?
black-venomz
Click to expand...
Click to collapse
Good, making progress... Your using the wrong twrp. You'll need to flash the proper one. Not sure which one of these will work but I know for sure one of the 2.7 versions will http://techerrata.com/browse/twrp2/zaracl
I know this is for zara cl but they work with zara ul as well. I'm not sure but i think the older ones are for jb and the newer for kk. Just try a few until you can mount properly while in recovery, then flash that rom I posted.
S-on just restricts some fastboot commands and /system protection while booted into android, doesn't affect recovery. Some kernels are patched so /system is writable in android even with s-on
mrplowdan said:
Good, making progress... Your using the wrong twrp. You'll need to flash the proper one. Not sure which one of these will work but I know for sure one of the 2.7 versions will http://techerrata.com/browse/twrp2/zaracl
I know this is for zara cl but they work with zara ul as well. I'm not sure but i think the older ones are for jb and the newer for kk. Just try a few until you can mount properly while in recovery, then flash that rom I posted.
S-on just restricts some fastboot commands and /system protection while booted into android, doesn't affect recovery. Some kernels are patched so /system is writable in android even with s-on
Click to expand...
Click to collapse
Hope we have a solution there ! Thank you for the walkthrough. I'll try it when I have time (exam 2morrow).
black-venomz
black-venomz said:
Hope we have a solution there ! Thank you for the walkthrough. I'll try it when I have time (exam 2morrow).
black-venomz
Click to expand...
Click to collapse
Tried every version in the link (and others I found).
They all failed to mount System, Cache, Data.
As I said before I'm not really surprised because I believe S-ON is there to prevent us from doing exactly that.
I think I should look into "fastboot boot" command (already tried and failed but it seemed promising).
Any ideas ?
Thanks again.
black-venomz
Flash the jb rom via twrp https://drive.google.com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&usp=sharing
black-venomz said:
Tried every version in the link (and others I found).
They all failed to mount System, Cache, Data.
As I said before I'm not really surprised because I believe S-ON is there to prevent us from doing exactly that.
I think I should look into "fastboot boot" command (already tried and failed but it seemed promising).
Any ideas ?
Thanks again.
black-venomz
Click to expand...
Click to collapse
I can assure you it's not related to being s-on. Can you get adb access from any of the recoveries? fastboot boot doesn't work for a number of newer HTC devices, unfortunately including that zara so that's a dead end
Child's Play said:
Flash the jb rom via twrp https://drive.google.com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&usp=sharing
Click to expand...
Click to collapse
He has to get recovery working properly first. Good call on the backup though.
mrplowdan said:
I can assure you it's not related to being s-on. Can you get adb access from any of the recoveries? fastboot boot doesn't work for a number of newer HTC devices, unfortunately including that zara so that's a dead end
He has to get recovery working properly first. Good call on the backup though.
Click to expand...
Click to collapse
Do u need to mount in order to flash the stock rom zip?
Child's Play said:
Do u need to mount in order to flash the stock rom zip?
Click to expand...
Click to collapse
I got adb sideload running a while.
Just to test it I transfered a rom via "adb sideload c:/rom.zip"
It actually failed after like 40% transfer with "file corrupt".
When starting adb sideload my log had several errors that could help :
"""
TWRP 2.8.0.1
Unable to recreate /data/media folder
Updating partition details...
Unable to mount /cache
Unable to mount /data
Unable to mount /system
Unable to mount internal storage
Unable to mount /data/media during GUI startup
Unable to mount /cache
Kernel does not hav support for reading SELinux contexts (Might be because I flashed KofilaKernel ?)
Running boot script...
Finished running boot script
Unable to mount /cache
Unable to mount /data/media/TWRP/.twrps when trying to read settings file
Unable to mount /data
MTP Enabled
Using RAM for sideload storage
Etc...
""""
I did, at some point, flashed KofilaKernel (found on in HTC Desire 601/Kernels). I can't find a stock kernel. Could it be messing with TWRP ?
Child's Play what file should I flash ? You can flash a ".img" via recovery ? (Though it was .zip only)
U flashed kofilakernel sense 6.0?
Child's Play said:
U flashed kofilakernel sense 6.0?
Click to expand...
Click to collapse
I flashed this : http://forum.xda-developers.com/desire-601/development/kernel-kofilakernel-t2857403
Edit : I flashed the 2.2 version, wich is probably Sense 6.0
Related
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?
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.
Got an old phone from a friend which I'm using since wife broke her phone and I'm trying to decide what to replace it with.
Anyhow, I have an Aria with hboot 1.03, I have unlocked it via the HTC site and managed to get Cyano 10 on it. It is still s-on and I've tried multiple times to redownload Cyano 11 and always get an error of "Error in <name>.zip (Status 0) Installation Aborted". I'm making an assumption based on research that it is due to a combination of s-on and hboot 1.03 so I need to kick it down to 1.02 and s-off it. However, I have been unable to find a valid link for the Official HTC Froyo link to downgrade so I can run Revolutionary to s-off and move ahead.
Thanks in advance.
Hmm, can't find a link either... I can reupload it for you
But before you do that, try updating your recovery to this: http://forum.xda-developers.com/showthread.php?t=2474662
HTCdev unlock shouldn't have any problems with CM11, so it's probably your recovery...
Anyway, here's the RUU
http://goo.gl/OBVJL7
md5sum: 66d703b8a92fc382c38ceec4992a379c
And the rom.zip extracted from it if you just want to run it directly from the phone:
http://goo.gl/WF3RhW
md5sum: 49e737569d1d99e11e652ddcfc15bf84
Edit: Here's a list of them instead of just the AT&T one: http://www.androidruu.com/?developer=Liberty
Thank you Win, that did it. I had to fastboot the CMW as it wouldn't upgrade through recovery, after that I just flashed CM11.
CollinsJ said:
Thank you Win, that did it. I had to fastboot the CMW as it wouldn't upgrade through recovery, after that I just flashed CM11.
Click to expand...
Click to collapse
Problem is that due to S-On it is not possible to write to recovery partition from recovery. You also can't write to boot partition, but you can install ROMs without problems if you flash boot image separately through fastboot.
dansou901 said:
Problem is that due to S-On it is not possible to write to recovery partition from recovery. You also can't write to boot partition, but you can install ROMs without problems if you flash boot image separately through fastboot.
Click to expand...
Click to collapse
Boot images can be flashed from recovery just fine with S-ON... maybe you're thinking of newer (but not newest) HTC devices? I've heard they did that
WinSuk said:
Boot images can be flashed from recovery just fine with S-ON... maybe you're thinking of newer (but not newest) HTC devices? I've heard they did that
Click to expand...
Click to collapse
Possible. I own one of them (points at signature) and it's been that way for me then. When I rooted my Gratia way back, I also directly did the S-OFF so I never checked the procedure with S-ON. Have been a newbie at that time.
So I'm in a similar boat. I have an old aria, and seeing a cm11, id like to try it (though a nexus is my dd). Anyway, i had cm7 on it, went through some old nandroids, and finally got back to 2.1 just after i used unrevoked on it. I've tried to flash the posted rom.zip (2.2.2, so i can then s-off and /or upgrade hboot [which i also tried to do via htcdev with no success]), it fails a sig check on my cwm 2.5.0.1, telling me bad, even though i verified the md5. Figured it could be the recovery, but i cannot flash the newer version on here via ./fastboot flash recovery recovery.img. i also tried ./fastboot boot recovery.img to no avail. I also couldnt flash the recovery through the old cwm. Im baffled a bit here... Any suggestions are welcomed.
Im thinking of trying to put my sim in it and see if the old att update would go through, any thoughts on that?
Hello. I am at a loss. I just received an HTC Evo 4G LTE today and tried to root it with WinDroid Unversal HTC Toolkit v1.1. I unlocked the Bootloader and installed TWRP version 2.7.0.0 and that is working and I can boot into that. I next tried to flash a ROM and any ROM I try I get "error executing updater binary in zip." I read somewhere that I had to wipe data, system, cache, Dalvik and .android_secure. So I used TWRP to do that. Now when I reboot, it says I don't have an OS installed and when I choose to reboot, it just stays on the HTC logo and that's it. I still get the same error when trying to flash a ROM in TWRP. I tried flashing a ROM with fastboot and the latest RUU on HTC's website but it tells me to obtain correct RUU and try again. I don't know what else I can try. I've also tried relocking the bootloader, but then I can't get into recovery and doesn't make a difference with RUU. I just rewiped everything again, but now it won't mount the internal memory. Just the micro sd. I wiped the internal memory and now it will mount, but I just tried to flash a ROM again and get the same "error executing updater binary in zip." I also tried to flash boot.img and that worked ok. Then tried flashing rom using fastboot and got "data length is too large". I even tried fastboot erase cache, fastboot oem rebootRUU then tried flashing again with same results. Now when I turn off the phone and turn it back on, it goes directly to hboot.. can't even get to htc logo now. I would very much like to just go back to stock with no root. Nothing is working, please help :crying:
What HBOOT version are you on? Have u tried the new run from this form or the Viper rom?
Update recovery.
Sent from my EVO LTE using Tapatalk
bryguy9021 said:
What HBOOT version are you on? Have u tried the new run from this form or the Viper rom?
Click to expand...
Click to collapse
I am running HBOOT 2.10.0000. Do you mean ROM from this forum? I have not tried either. Originally this all started trying to flash SuperSU.zip and that's when I started getting this error. I tried using: JEWEL_Sense5.5_Android4.3-V4.zip as that seemed the most current version. What ROM would you recommend?
TroNit said:
Update recovery.
Click to expand...
Click to collapse
I'm assuming you mean update TWRP. There is 2.7.1.0. I have 2.7.0.0. However, I don't think it was specifically for jewel as I had used the one that came with WinDroid before. This one I downloaded from TWRP's website for this phone. I just updated it.
I think I'll wait to try flashing a ROM again until I get a recommendation of a good one. Thanks for the replies, both of you.
RenoHal77 said:
I am running HBOOT 2.10.0000. Do you mean ROM from this forum? I have not tried either. Originally this all started trying to flash SuperSU.zip and that's when I started getting this error. I tried using: JEWEL_Sense5.5_Android4.3-V4.zip as that seemed the most current version. What ROM would you recommend?
I'm assuming you mean update TWRP. There is 2.7.1.0. I have 2.7.0.0. However, I don't think it was specifically for jewel as I had used the one that came with WinDroid before. This one I downloaded from TWRP's website for this phone. I just updated it.
I think I'll wait to try flashing a ROM again until I get a recommendation of a good one. Thanks for the replies, both of you.
Click to expand...
Click to collapse
Edited.
Sorry I didn't read it right !
Sent from my EVO LTE using Tapatalk
I updated TWRP to the version in the link you gave me. I thought I'd try the RUU again from HTC's site after relocking the bootloader, but it doesn't even show I have anything installed. Tried updating, but still getting "Obtain corrent RUU and try again". I want to try JEWEL_Sense5.5_Android4.3-V4.zip from this forum, but I have to go S-OFF. Do I have to be booted into android for this to work or can I do it from fastboot? Couldn't find anywhere where this was clear as I don't have any OS installed. I would like to find out first before I try. I'm about to give up and call it bricked if I can't get it up and running soon. Thanks for any help you can give me
RenoHal77 said:
I updated TWRP to the version in the link you gave me. I thought I'd try the RUU again from HTC's site after relocking the bootloader, but it doesn't even show I have anything installed. Tried updating, but still getting "Obtain corrent RUU and try again". I want to try JEWEL_Sense5.5_Android4.3-V4.zip from this forum, but I have to go S-OFF. Do I have to be booted into android for this to work or can I do it from fastboot? Couldn't find anywhere where this was clear as I don't have any OS installed. I would like to find out first before I try. I'm about to give up and call it bricked if I can't get it up and running soon. Thanks for any help you can give me
Click to expand...
Click to collapse
V4 doesn't require s-off also ate you using the modified twrp from captain throwback?
Sent from my EVO using XDA Premium 4 mobile app
http://www.androidfilehost.com/?fid=23501681358543160 newest twrp modified for 2.10 hboot
Did u run the ruu to get to hboot 2.10? Your not soff aleady? I dunno much about sense roms but i know the rest you have to use fastboot for the boot image.. I dont think your bricked
I updated TWRP to the one modified by captain throwback in the link you gave me. Wiped everything but Micro SDcard. My bootloader is unlocked and am S-ON (never turned S-OFF) and tried out JEWEL_Sense5.5_Android4.3-V4.zip from this forum. I have hboot 2.10. That's what the phone came with. I'm getting the error: Error excuting updater binary in zip. It gets to Setting up /data/app... , Setting up /system... , Setting up symlinks... then error message. For some reason, I have no /misc. Someone in IRC said that was weird. It seems that my partitions are messed up according to him. Any ideas? Thanks for the help, all of you!
Did you reboot recovery after wipe but before install?
Sent from my EVO using XDA Premium 4 mobile app
I did not.. but here I go :fingers-crossed:
You guys are awsome! It works. Ran into the enter password for encrypted data thingy, but I followed http://dietrichschroff.blogspot.com/2013/01/nexus-7-password-to-decrypt-storage.html and it worked. I thought this phone would never work again. Thank you all very much. YOU ROCK! :laugh::laugh::laugh::laugh:
Sweet
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.