Hey,
I have an HTC Desire 601 I just recently rooted. I had TWRP but I removed it in hopes of getting the OTA update to install. I installed the originally recovery image but it made no difference. When installing the OTA update I just get a red triangle and exclamation point.
I've tried relocking the device and following this small guide - http://forum.xda-developers.com/showpost.php?p=53903841&postcount=2
The only thing that I know is still modded on the device is the kernel.
What's preventing the device from updating?
U said ur kernel is modified thats y its preventing ur device from updating. Make sure everything is stock with no modifying
Child's Play said:
U said ur kernel is modified thats y its preventing ur device from updating. Make sure everything is stock with no modifying
Click to expand...
Click to collapse
I haven't been able to find the stock kernel for it. Would you happen to know where it is?
http://forum.xda-developers.com/showthread.php?t=2804427
Child's Play said:
http://forum.xda-developers.com/showthread.php?t=2804427
Click to expand...
Click to collapse
So, I installed the Stock_JellyBean_Boot.img kernel, in doing so, the wifi no longer turns on and I still get the red exclamination point and triangle when updating.
Do I need to rename it before flashing?
No. Is ur phone s-on or s-off?
Child's Play said:
No. Is ur phone s-on or s-off?
Click to expand...
Click to collapse
The phone is S-On.
Im not sure y it doesnt work. Try to flash the kk ota zip
Child's Play said:
Im not sure y it doesnt work. Try to flash the kk ota zip
Click to expand...
Click to collapse
This?
Sense 5.5 OTA - KitKat_Sense55_OTA
OTA_ZARA_CL_K44_SENSE55_MR_Sprint_WWE_VM_2.15.652.3-1.10.652.9_R3_release_378339.zip
I think so
Child's Play said:
I think so
Click to expand...
Click to collapse
The firmware.zip is only 36MB. Should the main OTA zip file be installed instead with ADB or Fastboot?
http://forum.xda-developers.com/showthread.php?p=54086279
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
Flash it via fastboot
Child's Play said:
http://forum.xda-developers.com/showthread.php?p=54086279
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
Flash it via fastboot
Click to expand...
Click to collapse
I think I'm getting close. I've followed that guide as closely as I can but I'm getting hung up on installing the OTA update with TWRP. Making up a backup fails with the message of "unable to mount /data"
My Hboot is 2-20.0000, I think that needs to be updated to 2-22.0000.
I've tried the kitkat firmware and recovery imgs posted on this forum - http://forum.xda-developers.com/des...x-roms-mods-recoveries-backups-tools-t2804427 but they haven't worked for getting hboot updated.
One of them gave the error when flashing of -
Code:
C:\Users\SEEKING\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (2047 KB)...
OKAY [ 0.334s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.380s
Can you post a link to the image of hboot that should be used?
Thanks for all of the support! I appreciate it.
No u just need to update the kk via phone or flash it manually
Child's Play said:
http://forum.xda-developers.com/showthread.php?p=54086279
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
Flash it via fastboot
Click to expand...
Click to collapse
When trying to install the KitKat OTA with TWRP I get this error message -
Code:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error executing updater binary in zip '/sdcard/Download/OTA_ZARA_CL_K44....
Error flashing zip '/sdcard/Download/OTA_ZARA_CL_K44.....zip
I was able to get the hboot updated to hboot 2.22
Running the OTA over the air still isn't working as TWRP is installed. Does the phone need to be locked for the OTA update to work?
U can try it
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
U tried to flash it via twrp?
Child's Play said:
U can try it
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
U tried to flash it via twrp?
Click to expand...
Click to collapse
I've tried flashing it via TWRP but I had no luck. A bigger issue has cropped up, I can no longer use wifi. It's stuck at turning on. I think that started happening after I flashed another kernel. I've tried flashing back to the stock kernel numerous times, but it still wont turn on. I've also tried removing the SD card but it didn't help.
Have you seen that before?
U r supposed to flash it via fastboot. I dont know what happened
Child's Play said:
U r supposed to flash it via fastboot. I dont know what happened
Click to expand...
Click to collapse
The firmware ZIP or the entire OTA zip file?
Firmware zip
Related
i rooted my phone using the zedomax method basically the one click root method which put super su on my phone, nothing to harsh but after i did the update lost root of course and now i want to get super su off my phone and remove the tamped sign on the boot screen....
any suggestion or is this one of those things i have to wait for the stock ruu to come out it, would be nice to use my google wallet again
any suggestions would help or even better a way to fix it
aperezlol101 said:
i rooted my phone using the zedomax method basically the one click root method which put super su on my phone, nothing to harsh but after i did the update lost root of course and now i want to get super su off my phone and remove the tamped sign on the boot screen....
any suggestion or is this one of those things i have to wait for the stock ruu to come out
any suggestions would help or even better a way to fix it
Click to expand...
Click to collapse
The stock ruu is already out...
Download it and run it I don't know if it will cure the tampered message.
Sent from my EVO using xda premium
it was my understanding that the best you can currently do is have it report "Relocked"
I'm not sure how to tell if its been relocked or not it lost root and shows tampered sighn if that helps
Sent from my EVO using xda app-developers app
brandonmaze said:
The stock ruu is already out...
Download it and run it I don't know if it will cure the tampered message.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
any links on how to do it or the stock ruu download i really just want my google wallet to work again
You have to soff to remove the tampered messages, I couldn't use lazy panda so I don't know the process but you need boot 1.12...sorry that
---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------
If all you want is Google wallet you can flash a zip for the modified wallet, head over to themes and apps and download the zip installer and flash on recovery
Did you ever install a twrp recovery?
om4 said:
You have to soff to remove the tampered messages, I couldn't use lazy panda so I don't know the process but you need boot 1.12...sorry that
---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------
If all you want is Google wallet you can flash a zip for the modified wallet, head over to themes and apps and download the zip installer and flash on recovery
Click to expand...
Click to collapse
of course i would need root to flash over the zip files correct ?
OK, what is the current state of your phone
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Never mind I just reread, you can't remove any of the tampered signs without soff
om4 said:
You have to soff to remove the tampered messages, I couldn't use lazy panda so I don't know the process but you need boot 1.12...sorry that
---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------
If all you want is Google wallet you can flash a zip for the modified wallet, head over to themes and apps and download the zip installer and flash on recovery
Did you ever install a twrp recovery?
Click to expand...
Click to collapse
i used this method
http://forum.xda-developers.com/showthread.php?t=1671577
What error is wallet giving you?
the oh so famous "unsupported device" triangle due to me being rooted accepted the update and lost root but left my phone with a tampered sign and google wallet less device
You can still use wallet unless you never made an account and backed the data with titanium
om4 said:
You can still use wallet unless you never made an account and backed the data with titanium
Click to expand...
Click to collapse
i never used taitanium back up even on my old evo and nexus
so even though the triangle of lost hope pops up on my google wallet i could still use it ? ill probably give it a try tommrow and see if it works
Yep, if not you can unlock boot loader I mean you can't get rid of tampered anyway and flash twrp recovery, then use the wallet zip I mentioned earlier
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
Well maybe if you get ruu for 1.22, maybe? It was the way your root method originally got rid of it.
Sorry what was I thinking titanium won't work for your problem sorry
I wouldn't worry about the tampered message really
I need help my EVO 3D is stuck on the second screen that comes up as it boots. It has been unlocked (HTC dev) flashed (4ext) and has a custom rom (Shooter Sense 3.6) on it. I can get it into the bootloader, and into the recovery, but cleverly i forgot to make a stock backup and can't revert from where im at.
Hboot- 1.49.0012
Radio- 10.13.9020.20_M
eMMC-boot.
Thats pretty much all the information i have, other than its a Telstra phone.
you have to manually flash the boot.img using fastboot
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
http://forum.xda-developers.com/showthread.php?t=1752270
EM|NEM said:
the reason its not booting is probably because you didnt flash the boot.img using fastboot. that is required to get roms to boot when you are s-on.
first install the rom from recovery.
then extract the boot.img from the rom zip file(probably in the kernel/shooteru folder) then place it in the folder where you have adb,fastboot and AdbWinApi.dll which you used to unlock.
then open cmd. change directory to the folder containing adb/fastboot.
Connect your phone in bootloader mode and make your it says "fastboot usb"
then type in cmd "fastboot flash boot boot.img"
it should do a process and show that it completed.
then reboot and it should boot up.
all the info you need is here:
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
EM|NEM said:
you have to manually flash the boot.img using fastboot
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
Just gave it a go still on the boot screen for now. heres to hoping.
AndrewMoulakas said:
Just gave it a go still on the boot screen for now. heres to hoping.
Click to expand...
Click to collapse
No luck.
Maybe try a different rom.
And if all else fails you can always use RUU
http://forum.xda-developers.com/showthread.php?t=1208485
---------- Post added at 02:43 PM ---------- Previous post was at 02:41 PM ----------
go to recovery. do factory reset in 4ext and wipe cache+delvik
then install rom.
then flash boot.img in bootloader mode
Its still not working. stuck on the boot screen still. after manually booting with fast boot.
you could make your life so much easier by doing s-off. the rom you are trying to flash requires a newer firmware(which requires s-off).
I think you can update your firmware using an ICS RUU. or you could take the OTA update if its available
EM|NEM said:
you could make your life so much easier by doing s-off. the rom you are trying to flash requires a newer firmware(which requires s-off).
I think you can update your firmware using an ICS RUU. or you could take the OTA update if its available
Click to expand...
Click to collapse
I have S-OFF and i've tried the RUU, and my carrier does not support the ICS OTA update at the moment.
Im giving it a go again now following your instructions to the T.
If you have s-off then just flash the latest firmware in bootloader
http://d-h.st/Mf1
then install the rom. no need for manual flashing of boot.img
should have stated you were s-off :banghead:
IT WORKED!!!!! thanks man. I would have never figured that out on my own or even stumbled upon that other thread. Thank you so much.
glad i could help
flash nils' 3.6 sense based ics rom. do the fully wipe and check the md5 before flashing. everything looks good.
after flash the kernel and reboot, now phone is stuck at the welcome screen with a green loading bar.
does any one know what is happening? how long did you wait for first boot after flashing this rom?
thank you.
leotnnz said:
flash nils' 3.6 sense based ics rom. do the fully wipe and check the md5 before flashing. everything looks good.
after flash the kernel and reboot, now phone is stuck at the welcome screen with a green loading bar.
does any one know what is happening? how long did you wait for first boot after flashing this rom?
thank you.
Click to expand...
Click to collapse
as long as the loading bar is still progressing your good. nils first flash usually takes a while (5-7min) if not do a full wide and flash the kernel again ph98img file i presume.. if your still having issues you can flash it in fastboot via your computer..
famouscollin said:
as long as the loading bar is still progressing your good. nils first flash usually takes a while (5-7min) if not do a full wide and flash the kernel again ph98img file i presume.. if your still having issues you can flash it in fastboot via your computer..
Click to expand...
Click to collapse
stuck for an hour now:crying:
leotnnz said:
stuck for an hour now:crying:
Click to expand...
Click to collapse
ok. whats all your info. what does your hboot read everything.. are you s-on? latest firmware or GB? if you have gtalk hit me up on that its faster and easier to help ya
famouscollin said:
ok. whats all your info. what does your hboot read everything.. are you s-on? latest firmware or GB?
Click to expand...
Click to collapse
latest ruu. s on
leotnnz said:
stuck for an hour now:crying:
Click to expand...
Click to collapse
check to make sure you have a good md5 for the rom.. nils uses aroma installer righ? did it identify you as s-on and extract a ph98img to your sd? it should have and then you should have booted to hboot to flash it there, did all this happen
---------- Post added at 03:47 PM ---------- Previous post was at 03:18 PM ----------
heres the ph98img file extracted from nil 6.3 click file<download: https://docs.google.com/file/d/0B0ZJtM40GdJ0RTJJSGE0cTFWUTA/edit you can try putting this on your sd and booting to hboot. ive had problems with aroma not extracting the file properly name it to just (PH98IMG) before you put it on your sd card
famouscollin said:
check to make sure you have a good md5 for the rom.. nils uses aroma installer righ? did it identify you as s-on and extract a ph98img to your sd? it should have and then you should have booted to hboot to flash it there, did all this happen
---------- Post added at 03:47 PM ---------- Previous post was at 03:18 PM ----------
heres the ph98img file extracted from nil 6.3 click file<download: https://docs.google.com/file/d/0B0ZJtM40GdJ0RTJJSGE0cTFWUTA/edit you can try putting this on your sd and booting to hboot. ive had problems with aroma not extracting the file properly name it to just (PH98IMG) before you put it on your sd card
Click to expand...
Click to collapse
thx. prob solved.
leotnnz said:
thx. prob solved.
Click to expand...
Click to collapse
no prob bud just hit thee button.lol what fixed it bud?
Yes, brick my phone, my htc evo 3D with Hboot 1.58, Unlocked Bootloader.. I tried to flash the CyanogenMod Gangnam Style, with 4ext recovery, and stuck on Boot Animation.. I accidentally format system in te recovery, there is a solution? Thanks!
If you are s off you need to do downgrade your boot loader. If you are s on you needed to do the write trick then downgrade your boot loader.
To get your phone in order now, Download a sense 3.6 rom and format everything but sd card in recovery and flash it, Make sure you read up on the requirements to flash next time, All roms have certain hboot's you have to be on.
---------- Post added at 04:33 AM ---------- Previous post was at 04:32 AM ----------
Your the same person I was working to unlock the bootloader this morning with, You've already messed up again
Can't_Live_Without_My_Evo said:
To get your phone in order now, Download a sense 3.6 rom and format everything but sd card in recovery and flash it, Make sure you read up on the requirements to flash next time, All roms have certain hboot's you have to be on.
---------- Post added at 04:33 AM ---------- Previous post was at 04:32 AM ----------
Your the same person I was working to unlock the bootloader this morning with, You've already messed up again
Click to expand...
Click to collapse
I was thinking more about getting cm to work and forgot the part about just getting the phone to work at all. Probably a better route :beer:
isaacsosa said:
Yes, brick my phone, my htc evo 3D with Hboot 1.58, Unlocked Bootloader.. I tried to flash the CyanogenMod Gangnam Style, with 4ext recovery, and stuck on Boot Animation.. I accidentally format system in te recovery, there is a solution? Thanks!
Click to expand...
Click to collapse
You can not install Cm 10 or 9 with Hboot 1.58..... you need to S-off and downgrade it to hboot 1.49 ....do the wire trick to downgrade it.....ATM you still can get to bootloader right?? so it is sofbrick and very easy to fix....download the correct RUU and flash it...With hboot 1.58 you can install rom with sense only...
Can't_Live_Without_My_Evo said:
To get your phone in order now, Download a sense 3.6 rom and format everything but sd card in recovery and flash it, Make sure you read up on the requirements to flash next time, All roms have certain hboot's you have to be on.
---------- Post added at 04:33 AM ---------- Previous post was at 04:32 AM ----------
Your the same person I was working to unlock the bootloader this morning with, You've already messed up again
Click to expand...
Click to collapse
You are my god, look i need the rom, im looking for the rom all the day but nothing :/ where i can get it? And, how i can flash back?
Thanks For all dude
isaacsosa said:
You are my god, look i need the rom, im looking for the rom all the day but nothing :/ where i can get it? And, how i can flash back?
Thanks For all dude
Click to expand...
Click to collapse
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1 .09.00.0706_signed.exe
Search for that on google, Add the word download, Shouldn't be too hard.
Can't_Live_Without_My_Evo said:
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1 .09.00.0706_signed.exe
Search for that on google, Add the word download, Shouldn't be too hard.
Click to expand...
Click to collapse
problem solved! i lock the bootloader and run the RUU, my phone is working now! Thanks! regards
isaacsosa said:
problem solved! i lock the bootloader and run the RUU, my phone is working now! Thanks! regards
Click to expand...
Click to collapse
Alright, You're allowed 8 thanks a day, I expect to see some of them lol.
Ok i am running a stock tmobile rom 1.27.531.11 with s-off , rooted and custom recovery.
I flash the stock recovery and try to install the update it says
finding update package
opening update package
virifying update
installing update
waring: no file_contextsVerifying current system
assert failed: apply_patch_check(/system/bin/app_process",
after the , is to long numbers looks like a checksum mismatch to me but im unsure. I would like to know how to i fix this?
xile6 said:
Ok i am running a stock tmobile rom 1.27.531.11 with s-off , rooted and custom recovery.
I flash the stock recovery and try to install the update it says
finding update package
opening update package
virifying update
installing update
waring: no file_contextsVerifying current system
assert failed: apply_patch_check(/system/bin/app_process",
after the , is to long numbers looks like a checksum mismatch to me but im unsure. I would like to know how to i fix this?
Click to expand...
Click to collapse
I was running a custom ROM with custom recovery, s-off, rooted and my cid was 11111111(? how many 1's is that) . anyways what i did i just flashed a stock RUU and it went through fine then from there i just did a normal update through the phone settings.
---------- Post added at 07:58 PM ---------- Previous post was at 07:55 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
compta5 said:
I was running a custom ROM with custom recovery, s-off, rooted and my cid was 11111111(? how many 1's is that) . anyways what i did i just flashed a stock RUU and it went through fine then from there i just did a normal update through the phone settings.
---------- Post added at 07:58 PM ---------- Previous post was at 07:55 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
i might wanna add that after the update i'm still s-off with super cid but it did update my hboot to 1.55.
Click to expand...
Click to collapse
thanx for the help.
It probably dont mater anymore now tho. I ended up soft brciking the phone, (son was jumpping around and i eneded up hiting factory reset)
I think im going to im going to end up losing all me stuff :crying:
but im doing the ruu now and i will see what happens. Hopefully i can recover some of my pictures and stuff.
And i did do a nano backup but like a dumba.. i didnt transfer it to the laptop. Also forgot that the data/system is one and no sd card
I give from now on ill do weekly data backups.
I have same problem.
Flashed stock recovery , but still same...
I have unlocked bootloader and s-off (with t-mob cid, ect)
What to do? S-on? Don't really think it causes problem
tried S-on , but still same
"warning no file_contexts verifying current system" ...
jkjambo said:
I have same problem.
Flashed stock recovery , but still same...
I have unlocked bootloader and s-off (with t-mob cid, ect)
What to do? S-on? Don't really think it causes problem
Click to expand...
Click to collapse
Dont flash stock recovery. You have to flash the 1.27 RUU which will flash stock hboot, recovery, and ROM.
blackangst said:
Dont flash stock recovery. You have to flash the 1.27 RUU which will flash stock hboot, recovery, and ROM.
Click to expand...
Click to collapse
i have stock recovery and stock rom , so i'll flash now just hboot . if this will not help me , then i'll try whole Ruu (i'm too lazy to download and install that )
don't know why , but i couldn't install htboot , so donwloading 1.27.531.8 (Downgreader) ...