Hello everybody,
I would like to share my problem on my htc desire 601 zara_ul.
I just did the unlock bootloader / recovery / and root steps but i'm facing another issues.
I tried to install the InsertCoin from this post :
http://forum.xda-developers.com/des...om-insertcoin-3-0-6-zaraul-m7-port-5-t2819869
And sometimes the Aroma installer goes until the end successfully, and sometimes my phone just reboots half the installation.
And when it ends successfully , when i reboot, i just can't boot , i'm still stuck on the green htc logo on the white background.
Does anybody have an idea of what i'm doing wrong and how i could have a functional phone asap ? ( can't find/undersand how to restore a ruu for this phone ...)
I have no access to my sd card because i have no devices to read it.
Just tell me if you need more informations , and sorry for the form of the text, french is my native language.
Thx for the replies.
You need to flash boot.img from insertcoin rom *.zip.
Also you can mount you SD card as USB-Storage from your Recovery (if its CWM - Mount and Storage > Mount usb storage, if TWRP - Mount>Mount USB storage).
Thanks for your answer,
I tried to extract the boot.img from zip.
Then did a fastboot flash boot boot.img successfully
But when i did fastboot reboot it got stuck.
I got the same results.
I got this recovery : http://forum.xda-developers.com/des...recovery-twrp-2-7-1-0-touch-recovery-t2804520
Zara UL hboot 2.20 radio 1.21
Thanks for replies.
ryuaner said:
Zara UL hboot 2.20 radio 1.21
Thanks for replies.
Click to expand...
Click to collapse
Omg..You must flash firmware.zip from the Kit Kat OTA. InsertCoin worked ONLY on kit Kat firmware - hboot 2.22.0000
Sent from my HTC Desire 601
ryuaner said:
Zara UL hboot 2.20 radio 1.21
Thanks for replies.
Click to expand...
Click to collapse
Or use this modified updater-script for 2.20 hboot
https://drive.google.com/file/d/0B6bGr-ir8saMd1lkMEFnTUZjWlU/edit?usp=sharing
Overwrite file in insertcoin_6thsense_zara_ul-3.0.6.zip
Path: META-INF/com/google/android
Here is modified rom
https://drive.google.com/file/d/0B6bGr-ir8saMR1JvUW5qS3ZlNzg/edit?usp=sharing
Use recovery for Jelly Bean
Tried to do that with the updater script but with no luck.
TWRP says md5 check fail.
And philz touch says Finding update, opening update, installing update , then installation aborted.
Thx for your help by the way.
Any suggestion on what i'm doing wrong ?
Related
Hi, I am useing flyHoney 0.2 for a while...
Now I want to try some of the GB ROMs - because of the better phone support- but with no success:
every other ROM hangs in a boot loop.
(I downloaded the ROMs and installed them via flasing into the recovery (cwm) ant then i choose install - from sd card...)
32gb flyer europe wifi version...
you need to flash the boot image from fastboot or use:
Code:
fastboot boot <recovery image>
You cannot flash the boot image from within recovery with a HTC unlocked bootloader.
I installed the Zip from recovery, flashed the extracted LeeDroids Zip, flashed the boot.img as you told - but after reboot it´s stuck - HTC Logo on white backgound.
What am i doing wrong?
robeppef said:
I extracted LeeDroids Zip, flashed the boot.img as you told - after reboot it´s stuck - HTC Logo on white backgound.
What am i doing wrong?
Click to expand...
Click to collapse
try with this Link
step1: Goldcard creating
http://forum.xda-developers.com/showthread.php?t=1307759
is it even possible to fast-switch between hc and gb roms, respectively my rom-backups at the moment?
robeppef said:
is it even possible to fast-switch between hc and gb roms, respectively my rom-backups at the moment?
Click to expand...
Click to collapse
Not if you have a US wifi flyer.
robeppef said:
is it even possible to fast-switch between hc and gb roms, respectively my rom-backups at the moment?
Click to expand...
Click to collapse
No, it's not. You have to RUU downgrade to get back to a system that will work with GB. Among other things the boot image, hboot an radio are incompatible.
Puh, finally i got LeeDroids ROM to run... had to create a goldcard and all that stuff ;-)
Now I´m more happy with GB...
Thanks for your help here !
I'm writing this as these questions commonly get asked in the development threads, taking them off topic.
S-ON users commonly run into these problems, which are quite simple to solve with the right information.
When your device is S-ON and unlocked via the HTC Method, the boot partition is mounted read-only in recovery mode, which causes these problems flashing custom kernels or custom roms.
a) Flashing a custom kernel through recovery mode breaks wifi:
Android uses the linux kernel, and the wifi drivers are compiled as kernel modules. The kernel modules are located in /system/lib/modules, and the linux kernel is located on the boot partition. When you flash the kernel zip file through recovery, the updated kernel modules get successfully written to the system partition however the linux kernel cannot get written to the boot partition. The result of this is that the kernel now cannot load the wifi kernel modules. This is what causes the WIFI error.
Solution: Download FlashImgGui from the market, and use that to install the kernel. This program can successfully write the new kernel to the boot partition eliminating the mismatch between the kernel and wifi modules.
b) Flashing a custom rom through recovery breaks wifi.
This problem is basically the same as a). The boot partition cannot be written so the kernel that came with the rom isn't written to it. This causes a mismatch between the kernel modules in the custom rom and the kernel.
Solution: You can either flash a custom kernel with FlashImgGui, or extract the boot.img file from the custom rom's zip file and copy to your computer. Then use the fastboot binary to flash the boot.img to the boot partition. This will copy the kernel that is packaged with the rom to your phone, which will fix the mismatch between the kernel and wifi modules.
C) Flashing a custom rom through recovery causes boot loops or the phone hanging at the HTC screen.
Some custom roms need a different initrd.gz file to the standard one. The initrd.gz file is located on the boot partition. When you flash the custom rom through recovery, the boot partition cannot get written and so the new initrd.gz isn't written to it. This is what causes the problems booting.
Solution: Same as above. Extract the boot.img from the zip file and flash with fastboot. This will copy the correct initrd.gz file to your phone and allow the rom to function correctly.
MODS: If you feel this is in the wrong section please move it. I'm only posting here as these questions always pop up in the development threads.
exactly what i have discovered
i can provide the testimony that the above are correct !
THANKS FOR CONFIRMING IT
actually it can be solved by
1. booting into bootloader (or via cmd :adb reboot bootloader)
2. flash boot "cwm.img" <<<name of the cwm file
3. flash via cwm
4. wifi will back on
ilovemeow said:
actually it can be solved by
1. booting into bootloader (or via cmd :adb reboot bootloader)
2. flash boot "cwm.img" <<<name of the cwm file
3. flash via cwm
4. wifi will back on
Click to expand...
Click to collapse
That method is useful for avoiding the problems in the first place, but its easier to flash the boot.img than flash recovery and reinstall the ROM for users who already have the problem.
doesnt it has any thing to do with the RADIO ???
because my phone came with another radio than the widely used one
and hboot 1.18
and I had tons of problems with wifi with every single rom
so I downgraded it to hboot 1.07 by flashing the EU 1.20 rom which came with the radio used here and achieved s-off using revolutionary
and all wifi problems were gone for good
s_superman said:
doesnt it has any thing to do with the RADIO ???
because my phone came with another radio than the widely used one
and hboot 1.18
and I had tons of problems with wifi with every single rom
so I downgraded it to hboot 1.07 by flashing the EU 1.20 rom which came with the radio used here and achieved s-off using revolutionary
and all wifi problems were gone for good
Click to expand...
Click to collapse
Absolutely nothing to do with the radio. Your wifi problems were solved once you got S-OFF . S-OFF means the boot partitions is mounted read-write in recovery mode so you do not have any of the problems I listed in the OP.
Where exactly do you flash the boot.img to when you need the custom rom's initrd? I.e. for 'fastboot flash xyz "boot.img"', what's the xyz?
Sent from my HTC EVO 3D X515m using XDA App
waltibaba said:
Where exactly do you flash the boot.img to when you need the custom rom's initrd? I.e. for 'fastboot flash xyz "boot.img"', what's the xyz?
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
"fastboot flash boot boot.img"
I guessed as much, but wasnt gonna risk my phone without asking. Thank you!
Sent from my HTC EVO 3D X515m using XDA App
hi i have no access to market and i dont find the link to download out of market plz any one can upload the apk or zip and put the link ????
sahandv1989 said:
hi i have no access to market and i dont find the link to download out of market plz any one can upload the apk or zip and put the link ????
Click to expand...
Click to collapse
Here's a link to the thread:
http://forum.xda-developers.com/showthread.php?t=1192527&highlight=flash+image+gui
Please try the search button next time, it is usually the best place to start here
Two days working and the solution was under my nose!
THANK YOU!
Thanks for the information, but I don't think it's entirely accurate. Those with older phones (that haven't taken updates from HTC) will possibly have the old radio firmware. And if you are S-ON and HBOOT1.5, there's no way to 'get' the new firmware on the phone if you are unlocked.
So you must get the updated radio firmware (1216), put in in the root, relock the phone, and do a bootloader boot to flash the radio firmware. Unlock again, and then you are good to go. I had the 8xx version radio firmware and couldn't run any newer ROMS with working wifi until I got the updated firmware.
Be advised that lock/unlocking wipes your phone.
I followed the instructions but it doesn't work
What I did is:
1) Installed the custom ROM
2) installed the boot.img from fastboot
3) rebooted -> but stuck at htc logo
My friend's EVO 3D GSM has:
HBOOT 1.49.0018
S-ON
Unlocked
Can someone help me??
thanks in advance
a friend gave me his legend so i can update it to a better rom
i'm planing on CM7.2 KANG build
the phone is stock, from local operator...
S-ON
HBOOT: 0.43.0003
RADIO: 7.08.35.21
FW: 2.1-update1
baseband: 47.39.35.09U_7.08.35.21
build: 2.05.461.52 CL218650
i know that i can SOFF it via a tool HTC has released but i also know that i don't really need it and i can use CM even with C-ON (am i right?)
most root guides i see are for 1.01 and not 0.43 so i prefer asking then killing the phone
You don't want to unlock the bootloader with HTC's tool! You can flash the Alpharev bootloader! That one allows everything, even downgrading.
REMEMBER: ROOTING WILL VOID WARRANTY AND YOU ACCEPT FULL RESPONSEBILITY!!
To root if you have S-OFF:
- First download any rooted rom (eg the 7.2 KANG rom) and CWM recovery (You want the S-OFF .img file): http://forum.xda-developers.com/showthread.php?t=1290841 Put the rooted ROM on your SD card. You'l need the recovery later.
- Download fastboot (I uploaded it for you to make it easier: http://dl.dropbox.com/u/33521967/fastboot.exe) Then put fastboot in a folder. Also put the CWM recovery image in the same folder as fastboot.exe. Then do Shift + Right click on the folder and chose "open command prompt here" then do
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
Now turn of your phone then press volume down + power at the same time. Navigate to recovery using the volume buttons. Then press the power button. Now the phone should boot in Clockworkmod recovery.
Now you can use the trackball of your phone to scroll down to install zip from SD card en click on the trackball to choose that option. Now select choose zip from SD card. Now you'll see the contents of your SD card. Scroll down the .zip file of the rooted ROM you downloaded and click on the trackball again. Now choose Yes - Install ............. (WARNING THIS WILL DELETE EVERYTHING ON THE PHONE!) after a succesfull install of the ROM you have a rooted device!
i tried Alpharev made problems
i used this guide to downgrade to 1.13 and root
http://theunlockr.com/2010/06/07/how-to-load-a-custom-rom-on-the-htc-legend/
in the CWM S-on option
do i rename the zip file to update.zip?
If you don't want S-OFF you can use that guide the unlocker. And if you use the S-ON CWM then you use FakeFlash, You have to rename the CWM zip package to update.zip, boot up in recovery, then select update.zip, you'll get CWM recovery.
But if you want S-OFF, what problems do you have with Alpharev? With S-OFF it's way easier, you don't need to downgrade ur ROM, you can just flash anything, like I said in my previous post.
ITS ALIVE!!!
thx for all the help... got it to run with normal nightly CM7
mine is s-on
how to make it s-off
hboot is 0.43
i need help hboot and rom
I recently deleted everything in my htc one x device and now i want to start a fresh, i find difficulties in getting my phone to work which rom to nsta;ll or what todo
hetch said:
I recently deleted everything in my htc one x device ...
Click to expand...
Click to collapse
But here is the HTC Legend Forum ...
hetch said:
I recently deleted everything in my htc one x device and now i want to start a fresh, i find difficulties in getting my phone to work which rom to nsta;ll or what todo
Click to expand...
Click to collapse
A really great rom is the one for YOUR phone and not one for HTC legend. hahaha you need to pay attention and look at what your doing or you'll end up bricking your phone
Sent from my GT-I9505 using xda app-developers app
Hi,
if Desire X EMMC is bricked and phone stuck on htc boot logo screen.
so via CWM can we partition our external SD as EMMC and boot the phone.
Regards
Bluffmaster
You need to provide more details. What ROM? What recovery version? What kernel? What do you mean emmc is 'bricked'? Do you have logs? etc.
Sent from my Nexus 10 using XDA Premium HD app
vogonpoetlaureate said:
You need to provide more details. What ROM? What recovery version? What kernel? What do you mean emmc is 'bricked'? Do you have logs? etc.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
I think maybe is a guide not an help thread from his post..
xpirt
Hi,
I am a mobile phone technician, i received desire x in dead condition from my customer.
He told me that he used a third party rom due to which phone bricked.
So i resurrect via RIFF J TAG to power up phone, during resurrection when i checked repair kernal + flash recovery + repair htc partition i got below ERROR:
Resurrection is not Completed due to Error: 0x3901 when i click generic customization its completed. check below thread.
http://forum.gsmhosting.com/vbb/f63...ick-repair-htc-partition-1632881/#post9293094
I made generic resurrection then phone boot but stuck logo then i flash with RUU. RUU flashing complete but same condition.
then i unlock bootloader and install flash CWM recovery then i install boot IMG of myONEdx ROM then wipe cache factory data and install myONEdx RC4.0 FX+ rom
when rom complete phone still stuck on boot and can not go further.
then i install boot img of Fulmix ROM v1.0/xpirt rom and again wipe data cahce and install Fulmix ROM v1.0 ROM the my phone boot but restarting so i go to CWM recovery and make external SD partition , When Complete my phone boot sucessfully and running android.
some of times it hang and restart but phone working .
i am confused where is the actually problem.
Regards
Bluffmaster
bluffmaster said:
Hi,
I am a mobile phone technician, i received desire x in dead condition from my customer.
He told me that he used a third party rom due to which phone bricked.
So i resurrect via RIFF J TAG to power up phone, during resurrection when i checked repair kernal + flash recovery + repair htc partition i got below ERROR:
Resurrection is not Completed due to Error: 0x3901 when i click generic customization its completed. check below thread.
http://forum.gsmhosting.com/vbb/f63...ick-repair-htc-partition-1632881/#post9293094
I made generic resurrection then phone boot but stuck logo then i flash with RUU. RUU flashing complete but same condition.
then i unlock bootloader and install flash CWM recovery then i install boot IMG of myONEdx ROM then wipe cache factory data and install myONEdx RC4.0 FX+ rom
when rom complete phone still stuck on boot and can not go further.
then i install boot img of Fulmix ROM v1.0/xpirt rom and again wipe data cahce and install Fulmix ROM v1.0 ROM the my phone boot but restarting so i go to CWM recovery and make external SD partition , When Complete my phone boot sucessfully and running android.
some of times it hang and restart but phone working .
i am confused where is the actually problem.
Regards
Bluffmaster
Click to expand...
Click to collapse
Find the decrypted rom.zip somewhere and extract the boot.img. Flash that. Then flash Desire X 1.18 stock rooted rom to give them root and deodex. Tell your customer they're rooted and that everything should work fine...
Dear Stero 8,
Can i use below mention version for root and deodexes?
Desire_X_1_18_SUBB_deodexed
bluffmaster said:
Dear Stero 8,
Can i use below mention version for root and deodexes?
Desire_X_1_18_SUBB_deodexed
Click to expand...
Click to collapse
Yes!
Dear Stereo 8,
I Just Follow all you instruction , but i got black screen after htc sound ?
any suggestion
Weird... I'm clueless...
Flowed from my HTC branded muffin...
Hi,
Riff box release new DLL, so after resurrection with new dll i flash with stock ruu but phone stuck at boot screen and also not go to recovery.
from old dll it stuck on boot screen but can go to recovery so i can flash CWM but after new dll no recovery ?
What can i do .. confused
Fastboot flash recovery if you can go to fastboot.
Flowed from my HTC branded muffin...
i can boot to fast boot and i install CWM Recovery via fastboot.
but when i go to recovery its stuck at htc logo then restart it
Well, it's probably dead if you can't boot it whatever you flash....
Flowed from my HTC branded muffin...
You are wrong, Riff box restores the EMMC to stock plus if you get successful Resurrection with Riff it should be fine this means the problem is NOT EMMC which leads me to believe the device has a hardware fault but then you say if you install rom to Sd-ext the phone boots although unstable it atleast boots up. Which now leads me to think the device may have a unstable EMMC which means it needs the chip replacing. what you need to do is go to fastboot mode and open up a new CMD window and cd into your fastboot dir and type fastboot oem lock. Then run the Stock RUU and let it reboot into android. if that still dont help then PM me and send me your logs of resurrection from riff box and ill take a look at them see what the errors are thanks
Hi guys. can someone give me a download link for the stock recovery file and the boot.img file? I need to install the RUU for my enrc2b. since i have installed many custom roms and current is android revolution HD i cant install RUU by any procedure. the RUU always gives me some errors. I also tried to get the ROM.zip file extracted from the RUU file but it does not work anymore since HTC blocked it or something. pleaseeee help.
Just up the thread.
frrobin said:
Hi guys. can someone give me a download link for the stock recovery file and the boot.img file? I need to install the RUU for my enrc2b. since i have installed many custom roms and current is android revolution HD i cant install RUU by any procedure. the RUU always gives me some errors. I also tried to get the ROM.zip file extracted from the RUU file but it does not work anymore since HTC blocked it or something. pleaseeee help.
Click to expand...
Click to collapse
I'm also in need of the files just like the other person mentioned.
Currenly my HTC One X+ is runnning CM11 nightly build and wanted to flash back to stock.
What version of HBOOT and RADIO do you see in the FASTBOOT menu?
This is the stock recovery with 2.18.401.3:
https://yadi.sk/d/pgAzfBwhT562e
This is the stock 2.18.401.2 rom with inside the stock kernel (boot.img) to flash via fastboot:
https://docs.google.com/file/d/0B7yPonjCRjRrdnNUeDRNXzZyLXM/edit?pli=1
I think that the bootloader must be re-locked for the RUU
I hope it works! I stay tuned for any feedback