I really would like to get Tiamat Sense 1.1.0 on my Infected ROM Eternity, but the article "http://infectedrom.com/showthread.php/561-ROM-Eternity%99-2.3.4" doesn't really say anything about installing a custom kernel via fastboot. If I could have some help doing this, that would be great!
dopapifreak34 said:
I really would like to get Tiamat Sense 1.1.0 on my Infected ROM Eternity, but the article "http://infectedrom.com/showthread.php/561-ROM-Eternity%99-2.3.4" doesn't really say anything about installing a custom kernel via fastboot. If I could have some help doing this, that would be great!
Click to expand...
Click to collapse
i'm sure there are plenty of guides providing better directions than i can give, as i've never used the htc unlock method, but from the different posts and guides i've read, there seems to be threee approaches:
1) using my flash image gui app, you will be able to flash the kernel .zip file from android! i've confirmed it works after having used the revolutionary unlock method and many other users have confirmed it works after having used the htc unlock method.
2) fastboot boot c:\downloads\custom-recovery.img - once you've loaded the custom recovery using this method, it will work to flash a custom kernel. the custom recovery will only work during the current boot, as soon as you reboot, it won't have access to flash a kernel. everytime you need to flash a custom kernel, you'll have to fastboot boot recovery.img.
3) fastboot flash boot kernel-boot.img - downside is you also have to pull out the /system/lib/modules files from the kernel .zip file and manually copy those over to your system after you have booted the custom kernel. if you don't copy over the modules, wifi and wimax will not work but will throw errors. the previous two methods both take care of this step for the user.
if you have a chance to try any of these methods, please post back what works! hope that helps!
Yeah. Just download kernel and put into root of sdcard. Then on pc, fastboot into recovery or bootloader then recovery and install zip from sd card and that's all. That's only downside from rooting by HTC compare to S-OFF.
Sent from my PG86100 using xda premium
i can get it workk..!! thanks man!!
i can flash new kernel with S-ON!
hi can you help me doing either option 2 or option 3?
evo 3d x515m is not supported by the app so option 1 is not possible
_Intel_ said:
hi can you help me doing either option 2 or option 3?
evo 3d x515m is not supported by the app so option 1 is not possible
Click to expand...
Click to collapse
I haven't added official support because I haven't had a tester yet. If you'd be willing to test, I can easily toggle support for the device. Once I have a confirmed good test, I will have no problem distributing it with support for EVO 3D X515M.
If anybody is able to help run a test flash and confirm it worked properly, send me a PM and I'll send you a custom version to test with! Thanks!
In regards to methods 2 and 3, I outlined all the required commands above. I would suggest going with method 2 as it is more thorough and should be used whenever accessing the custom recovery. The HTC unlock method blocks write access to the kernel partition thus the traditional method of booting the custom recovery will not work.
Method two is how HTC designed their unlock to grant a custom recovery kernel write access. To repeat my post above, the command is: fastboot boot c:\cwm-recovery.img .
If you are having specific issues with any of the methods, please post up details or error messages. The more detail you provide, the better of an answer we can provide!
Hope that helps!
ok,
im trying to install this custom kernel:
http://forum.xda-developers.com/showthread.php?t=1202422
but based on your instruction, i need custom-recovery.img. where can i get that?
_Intel_ said:
ok,
im trying to install this custom kernel:
http://forum.xda-developers.com/showthread.php?t=1202422
but based on your instruction, i need custom-recovery.img. where can i get that?
Click to expand...
Click to collapse
Any custom recovery will work that is designed to support the EVO 3D GSM. I think your options are clockworkmod recovery and twrp recovery. I don't have an EVO 3D GSM so I'm not 100% positive what custom recoveries are available.
Once you have the correct custom recovery .img file, use the command I provided above and you're all set!
Hope that helps! Good luck!
joeykrim said:
Any custom recovery will work that is designed to support the EVO 3D GSM. I think your options are clockworkmod recovery and twrp recovery. I don't have an EVO 3D GSM so I'm not 100% positive what custom recoveries are available.
Once you have the correct custom recovery .img file, use the command I provided above and you're all set!
Hope that helps! Good luck!
Click to expand...
Click to collapse
will this work?
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-shooteru.img
i just wanted to be extremely sure..
_Intel_ said:
will this work?
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-shooteru.img
i just wanted to be extremely sure..
Click to expand...
Click to collapse
Based on the file name and the naming convention of the EVO 3D GSM being "shooteru", yes, this looks like the correct version of the custom recovery for your device.
_Intel_ said:
will this work?
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-shooteru.img
i just wanted to be extremely sure..
Click to expand...
Click to collapse
its still giving me problems.
here's what i did:
1) downloaded the recovery img from the link above.
2) in terminal, i did: ./fastboot boot recovery-clockwork-5.0.2.0-shooteru.img and it says waiting for device
3) shutdown evo3d and press down vol + power
4) from bootloader, i choose fastboot.
5) the terminal says:
recovery-clockwork-5.0.2.0-shooteru.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.900s]
booting...
OKAY [ 0.001s]
finished. total time: 0.902s
6) it booted CWM
7) tried to install the latest unity kernel. but still failed. same error
_Intel_ said:
its still giving me problems.
here's what i did:
1) downloaded the recovery img from the link above.
2) in terminal, i did: ./fastboot boot recovery-clockwork-5.0.2.0-shooteru.img and it says waiting for device
3) shutdown evo3d and press down vol + power
4) from bootloader, i choose fastboot.
5) the terminal says:
recovery-clockwork-5.0.2.0-shooteru.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.900s]
booting...
OKAY [ 0.001s]
finished. total time: 0.902s
6) it booted CWM
7) tried to install the latest unity kernel. but still failed. same error
Click to expand...
Click to collapse
Sounds like you've correctly loaded the custom recovery through the fastboot boot method, good. One less step to be concerned with while troubleshooting.
The next issue is the error message you're receiving in the recovery. This is almost always due to the .zip being coded incorrectly by the developer. I would check his thread for reports of the same issue.
The steps to troubleshooting a recovery .zip file flashing error is as follows:
Once you flash the .zip and the recovery throws the error message, the details for the error message are output into a recovery error log stored at - /tmp/recovery.log .
Via adb shell type, cat /tmp/recovery.log. Feel free to post the output up here and we can help troubleshoot the kernel developer's .zip file coding.
Hope that helps!
I can confirm that booting into that recovery image and flashing a kernal works. I was able to flash kamma v2 cwm zip with no issues, even wifi works
1.49.0011 S-ON.
@joeykrim if you haven't gotten any guinea pigs for your gsm version of your application yet, I'll be more than happy to be one.
hmm ok it seens a problem with the newly released kernel for evo 3d.. i will post the same in the devs thread. http://pastebin.com/raw.php?i=T250g1Cg
thanks a lot
i flash the new kernel in 5.0.2.0 recovery and i still get error(status 7)
why
ricky886 said:
i flash the new kernel in 5.0.2.0 recovery and i still get error(status 7)
why
Click to expand...
Click to collapse
try to flash it via fastboot.
ricky886 said:
i flash the new kernel in 5.0.2.0 recovery and i still get error(status 7)
why
Click to expand...
Click to collapse
_Intel_ said:
try to flash it via fastboot.
Click to expand...
Click to collapse
yea, some of the kernel developers need to clarify their methods.
if you're coming from a brand new completely stock kernel, the anykernel type kernel .zip files will not work, as the stock kernel has the first 256 bytes encrypted.
you can only flash a boot.img type custom kernel, which is included in some ROMs, over the the stock signed/encrypted kernel.
once you've flashed an unencryptd/unsigned boot.img kernel, you can flash anything after that!
not sure the best way to educate the developers other than trial/error and user feedback. please post your recovery error messages back in each developer's thread to help them be aware of the issue they're causing.
hope that helps!
_Intel_ said:
will this work?
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-shooteru.img
i just wanted to be extremely sure..
Click to expand...
Click to collapse
I will definitely NOT use this version, it has charging issues, reboot issues. I only had problems with it: had to connect my phone to the PC to start it using adb commands or pull out the battery so often!
I moved to 4.0.1.4, which is available in one of the sticky thread in GSM EVO 3D forum.
Related
Hello all
Please I have "error" when i turn on wifi
what is the problem?
I have 1.49.0012 Hboot S-ON
rom Virtuous 1.0.1
I have tried to :
-Unzip the ROM
-copy boot.img unzipped
-paste onto adb file folders
-turn your phone into fastboot, connect your phone with computer
-fastboot usb shown on display
-open CMD
-type: fastboot flash boot boot.img
-reboot
but not work
and replaced "bcm4329.ko"
but also not working
please help meee
alex62157 said:
Hello all
Please I have "error" when i turn on wifi
what is the problem?
I have 1.49.0012 Hboot S-ON
rom Virtuous 1.0.1
I have tried to :
-Unzip the ROM
-copy boot.img unzipped
-paste onto adb file folders
-turn your phone into fastboot, connect your phone with computer
-fastboot usb shown on display
-open CMD
-type: fastboot flash boot boot.img
-reboot
but not work
and replaced "bcm4329.ko"
but also not working
please help meee
Click to expand...
Click to collapse
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
WiFi whoes
Im having the same problems as alex...
Ive flashed many roms through recovery mode, but for some reason the kernel wont update.
When ever i go to check the kern version, it's displaying the same.
When i go to flash a kernel zip through cwm-4.0.1.4-shooteru recovery mode, it stops when 'Installing Kernel' for at least 2 minutes... says its complete, but does not update the kernel!
When i push the kernel using fastboot.. it says OK, but most kerns wont boot the phone, and i have to keep resorting back to Crypt0's_RUU_V_1.3 boot.img to revive the phone!!
JoeyKrim, when i launch your app, it says 'Sorry, current device: HTC EVO 3D X515m is not supported".... Have i missed something, do i not have a evo 3D..hahah!?!? Do you have any idea what is going on here?
This is driving me crazy, everything i do to try and restore my WiFi, nothing works.. I have purchased this phone in China, tried 3 different stock HTC RUU's (all asian versions available)(windows installers), and all report 'error 115 - Not supported' before entering the flashing process on the phone... I have no idea on how im going to re-flash back to stock, as this is what im willing to do to get my WiFi back...
My Evo 3d version is 1.49.0011 S-ON, now using SU 3.02 signed and have cwm-4.0.1.4-shooteru recovery...
Worst HTC experience ever!!! I now feeling I should have stuck with Samsung! As im used to the full support and quality methods supplied this great community for Samsung hardware!
radmanz said:
Im having the same problems as alex...
Ive flashed many roms through recovery mode, but for some reason the kernel wont update.
When ever i go to check the kern version, it's displaying the same.
When i go to flash a kernel zip through cwm-4.0.1.4-shooteru recovery mode, it stops when 'Installing Kernel' for at least 2 minutes... says its complete, but does not update the kernel!
When i push the kernel using fastboot.. it says OK, but most kerns wont boot the phone, and i have to keep resorting back to Crypt0's_RUU_V_1.3 boot.img to revive the phone!!
JoeyKrim, when i launch your app, it says 'Sorry, current device: HTC EVO 3D X515m is not supported".... Have i missed something, do i not have a evo 3D..hahah!?!? Do you have any idea what is going on here?
This is driving me crazy, everything i do to try and restore my WiFi, nothing works.. I have purchased this phone in China, tried 3 different stock HTC RUU's (all asian versions available)(windows installers), and all report 'error 115 - Not supported' before entering the flashing process on the phone... I have no idea on how im going to re-flash back to stock, as this is what im willing to do to get my WiFi back...
My Evo 3d version is 1.49.0011 S-ON, now using SU 3.02 signed and have cwm-4.0.1.4-shooteru recovery...
Worst HTC experience ever!!! I now feeling I should have stuck with Samsung! As im used to the full support and quality methods supplied this great community for Samsung hardware!
Click to expand...
Click to collapse
My app was designed and only tested on the CDMA version of the EVO 3D, as that is what I own. I never had a tester for the GSM version until today. I hope to release an update to my app in a few hours.
In the mean time, if you follow the 2nd method I listed above, it will work for you as long as you've completed the HTC unlock method.
The HTC unlock method does not unlock write protection for the kernel using the traditional custom recovery boot method.
If you want write access to the kernel with a custom recovery, HTC requires you to fastboot boot the custom recovery.
I posted the command above and will repeat it again as it is the key to properly loading the custom recovery in order for HTC to grant write access to the kernel. The command: fastboot boot c:\cwm-recovery.img
Technical details: When you fastboot boot the recovery image, you're technically not in *recovery* mode. You're technically in a temporary fastboot state. This is a unique feature of the HTC bootloaders not found on Samsung devices (outside of the Google phone, Nexus S). It is only designed to temporaroy boot a *kernel* and recovery is essentially a "dumbed" down kernel.
Appreciate the support and hope that helps!
joeykrim said:
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
Click to expand...
Click to collapse
Okay thanx, I'll try the methods..
joeykrim said:
Sounds like you're on the right path. Essentially the most common cause for the WiFi error is HTC unlocked users not being able to flash custom kernels through the traditional custom recovery route.
There are essentially two easily feasible alternatives:
1) Use my Flash Image GUI app while in the normal Android mode. My app will flash both the kernel's boot.img file and copy over the correct /system/lib/modules including bcm4329.ko from the kernel's .zip file. Using my app ensures both the kernel flashed to memory and the modules copied over are in sync and will prevent the common WiFi error from having a kernel and module out of sync.
2) Use fastboot to "boot" not "flash" the custom recovery. Command: fastboot boot C:\cwm-recovery.img . This will temporarily boot the custom recovery and grant it write permission to the boot/kernel partition. While temporarily booted into the recovery, flash the kernel .zip file and this will ensure the kernel image matches the modules being loaded.
If using either of the two methods above still results in the same WiFi error, I'd give them another try. If it still persists, there could be a deeper issuer, perhaps hardware related. The best approach, in my opinion, at that point would be to revert to a stock ROM. If you still have the issue on a stock ROM, that would indicate some type of hardware issue and the best resolution at that point would be to return/exchange the device. Again, all my opinion.
Hope that helps!
Click to expand...
Click to collapse
I've tried the 2nd method and now it's working right
thanx alot
alex62157 said:
I've tried the 2nd method and now it's working right
thanx alot
Click to expand...
Click to collapse
Hi alex,
Are you able to tell me what version of CWM recovery image you have used? or even post it online for me to use...
I've tried many different img versions, and it keeps locking up on the HTC boot screen... Also, what kernel have you chosen to get your wifi working again!?!?
RadmanzZZZzzZZZ
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
yankee minaj said:
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
if you have hboot 1.5 then you have to flash thru cmd prompts
yankee minaj said:
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
3vo kid said:
if you have hboot 1.5 then you have to flash thru cmd prompts
Click to expand...
Click to collapse
This is not 100% correct. If you use my application, Flash Image GUI, you're able to flash ROMs and kernels w/o ever using the command process.
Details are all below.
Although, as a word of cuation.
Using the command process to fastboot boot c:\recovery.img is the best way to fully nandroid backup and RESTORE the device.
This is important because many times there are bugs or issues in custom software users don't want bu don't know until they load it. If you want to easily be able to revert, always use proper backups.
If you have hboot 1.5, the main limitation is not being able to flash the kernel through standard recovery mode.
HTC unlocks write access to the kernel in two other modes: normal android mode and fastboot mode.
I've answered this question many times on this Q&A forum, so I'm pasting an excerpt from a previous answer. Please post back if you have questions or something isn't clear!
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes: normal Andriod mode and fastboot.
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any ROM.zip or kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
After loading the ROM .zip, Flash Image GUI will flash only the kernel and modules. Reboot into the custom recovery to flash there rest of the ROM.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery. This mode requires a computer.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues caused with Hboot 1.5 on the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
joeykrim said:
This is not 100% correct. If you use my application, Flash Image GUI, you're able to flash ROMs and kernels w/o ever using the command process.
Details are all below.
Although, as a word of cuation.
Using the command process to fastboot boot c:\recovery.img is the best way to fully nandroid backup and RESTORE the device.
This is important because many times there are bugs or issues in custom software users don't want bu don't know until they load it. If you want to easily be able to revert, always use proper backups.
If you have hboot 1.5, the main limitation is not being able to flash the kernel through standard recovery mode.
HTC unlocks write access to the kernel in two other modes: normal android mode and fastboot mode.
I've answered this question many times on this Q&A forum, so I'm pasting an excerpt from a previous answer. Please post back if you have questions or something isn't clear!
Click to expand...
Click to collapse
You know I also heard that if your Rom has no custom kernel you can flash it in a regular recovery with out computer is that correct?
And with the explanation and all that being said....Im good to go and flash themes and Rok with your app?
Sorry if I'm askin too much you know just making sure thanks
Sent from my PG86100 using XDA App
yankee minaj said:
You know I also heard that if your Rom has no custom kernel you can flash it in a regular recovery with out computer is that correct?
And with the explanation and all that being said....Im good to go and flash themes and Rok with your app?
Sorry if I'm askin too much you know just making sure thanks
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
The only time issues occur is when the .zip file contains a kernel. The HTC unlock method blocks all writing to the kernel partition from recovery mode. This is where my app, Flash Image GUI, helps out as it allows the kernel and modules to be properly loaded so the rest of the .zip file can be loaded from the recovery!
If the .zip file does not contain a kernel, you can flash directly from recovery w/o any issues.
Hope that helps clarify!
I have an EVO 3D GSM of Telstra with hboot 12. I unlocked an rooted. I can flash all cook rom. Howerver, I can' flash any custom kernel. It always notice a error status 7. I tried many different kernel, but it was not working. I also tried using the Image UI and I got error.
Someone help me please. I want to flash some kernel.
Thanks for helping.
Someone help me. I want to flash some karnel...
S-On dosen't allow flashing kernals, but to get past that u have to access Recovery from Fastboot. To know how to do this follow these steps.
Download this: http://www.mediafire.com/?g6ex57jvbobel07
Then Follow this:
1. Boot into Fastboot and connect your phone to the computer
2. In the Folder you downloaded Click Open cmd
3. Type fastboot boot recovery.img
4. When recovery boots, just flash the Kernal normaly
5. Enjoy!!!!
You can also use this method to install S-OFF roms,
Happy Flashing!!! XD
Cousie G said:
S-On dosen't allow flashing kernals, but to get past that u have to access Recovery from Fastboot. To know how to do this follow these steps.
Download this: http://www.mediafire.com/?g6ex57jvbobel07
Then Follow this:
1. Boot into Fastboot and connect your phone to the computer
2. In the Folder you downloaded Click Open cmd
3. Type fastboot boot recovery.img
4. When recovery boots, just flash the Kernal normaly
5. Enjoy!!!!
You can also use this method to install S-OFF roms,
Happy Flashing!!! XD
Click to expand...
Click to collapse
I knew this method before, and I did it but result is error status 7. SO SAD (
Is the kernel you're flashing compatible with that rom? I don't think you can flash just any 'ol kernel.
G.Newton said:
Is the kernel you're flashing compatible with that rom? I don't think you can flash just any 'ol kernel.
Click to expand...
Click to collapse
Can you show me how can I identify it?
HI EVERYBODY,
Today i wanna introuduce my first filekit for rooting htc amaze 4g,
It is easy and needs only clicks instead of writing commands and reading different sites and downloading files from different sites it's all in one,
so follow the guide carefully!
<<<<<<I AM NOT RESPONSIBLE FOR ANY KIND OF DAMAGE YOU MAKE OR FOR ANY BRIKED DEVICES!>>>>>>>
Click to expand...
Click to collapse
STEP BY STEP GUIDE!
GUIDE 1:: {unlocking the bootloader!}
This is htc amaze 4g unlocking,flashing recoveries and rooting filekit by playboydroid at xda developers.
first step enable usb debugging in settings>developer options>usb debugging tick it.or if you are at gingerbread so goto applications>devlopment>usb debugging.
STEP 2>> go into my filekit select data folder>install htc drivers.
STEP 3>> connect your pc to phone with usb cable then in data folder slect reboot into bootloader when you get into bootloader so use volume keys to navigate and
power key to select,you should be connected with usb cable between your phone and pc you will see written fastboot usb highlited with red if you cannot see
so select fastboot written in the bootloader menu so when you see fastboot usb in red colour, then select token id windows batch file present in data folder of my
FILEKIT so by selecting token id from pc will help you in getting the token so select the token as follows:
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
after marking the token copy it by right clicking on the command window opened so after right clicking a dailouge box will appear so select edit>mark then select the token written and right click to select the token then visit htcdev.com singup first then select unlock bootloader at the right of the site select your device
htc amaze (t-mobile)or(mobilcity)or other then begin unlocking bootloader skip all steps goto step 10 and deposit your identifier token there and you will recieve
unlock_code bin in your email download it and place it in my toolkit>data folder then run the file unlockbootloader in my toolkit>data so this will ask a question on your phone's screen so select yes if you want to unlock or select no if you don't want to unlock bootloader
Code:
(note that when you select yes your all data would be deleted)
so now you are done unlocking bootloader now you can flash recovery and you can proceed to root.
GUIDE 2 : flashing custom recoveries..
first step>>connect your phone with pc using usb cable.
second step>>use the file reboot into bootloader present in my filekit>data it will take you to bootloader (note;usb debugging should be enabled)
third step>>after getting into bootloader use the file flash cwm5026 recovery so the file will flash recovery in your phone!
fourth step>>select recovery in the bootloader menu while usb disconnected,to see that, is recovery working?
and you are done flashing recovery the second part of rooting.
GUIDE 3 : rooting/installing superuser binary..!!
step 1>> goto my filekit>data folder then select super su folder and send the supersu.zip file to your phone.
step 2>> now select reboot into recovery from my filekit>datafolder it will take you to recovery.
step 3>> select install zip from sd card and find the supersu.zip in your storage then select it and answer it yes and you are done!
step 4>> reboot your system now!
EXTRA GUIDE FOR S-ON USERS;FLASH 4EXT RECOVERY:
I WILL RECOMMEND TO FLASH 4EXT RECOVERY AFTER ROOTING AMAZE 4G WITH CWM RECOVERY BECAUSE IT
IS THE BEST RECOVERY AND WELL FEATURED!
TO FLASH 4EXT RECOVERY GO TO: AND FROM THERE DOWNLOAD 4EXT RECOVERY!
THEN YOU WILL GET 4EXT RECOVERY.ZIP SO SEND IT TO YOUR SD CARD THEN BOOT YOUR PHONE INTO BOOTLOADER USE THE
REBOOT INTO BOOTLOADER FILE FROM MY FILEKIT>DATA AFTER THAT NAVIGATE TO RECOVERY AND SELECT
4EXT RECOVERY.ZIP AFTER IT FLASHES SUCESSFULLY REBOOT YOUR SYSTEM OR REBOOT RECOVERY SO THEN
NEW RECOVERY WILL BE SEEN..
ALL GUIDES AND FILES ARE AVAILABILE IN THE ZIP..
EXCEPT 4EXT!
ALTHOUGH I HAD INCLUDED 4EXT RECOVERY IN THE FOLDER BUT IT IS NOT WORKING!
YOU CAN DOWNLOAD THE 4EXT RECOVERY UPDATER APP AND YOU CAN FLASH LATEST RECOVERY FROM THAT APP AFTER ROOTING!
4EXT Recovery App
so first download the zip from here
unzip it and use the guides above to proceed! use 7zip or similar
if you got any help from my post so please tap the thanks :good: button so i could post more!
I AM HERE TO HELP IF YOU GET CONFUSED IN UNDERSTANDING MY ENGLISH BECAUSE MY ENGLISH IS NOT WELL!!
SOON I WILL BE POSTING A VIDEO SO YOU CAN UNDERSTAND MORE CAREFULLY!
There is another way & it is now the only way by using Ubuntu 12.04 (and newer) 32bit
as you can see here
http://forum.xda-developers.com/showthread.php?t=2167596
http://unlimited.io/juopunutbear.htm
Team Unlimited
WE NO LONGER SUPPORT ANY VERSION OF WINDOWS!
thanks
Hi ..!
I like your post ..!
And I had tried this ..!
Very usefull post for unlocking bootloader
phone stuck at HTC logo
hey guys,
great guide, plain and simple
I have gotten to the point of rooting the phone, however when I install roms from sd card and reboot, the phone gets stuck at the htc logo with the white background. Am I missing something...After i install the super su and reboot, can I just install a rom, or do i need to update the kernel or install an update?
thanks in advance
reddo_xda said:
hey guys,
great guide, plain and simple
I have gotten to the point of rooting the phone, however when I install roms from sd card and reboot, the phone gets stuck at the htc logo with the white background. Am I missing something...After i install the super su and reboot, can I just install a rom, or do i need to update the kernel or install an update?
thanks in advance
Click to expand...
Click to collapse
Yes the problem is that you need to flash boot.img from bootloader or for easily flashing roms from recovery ,use 4ext recovery...
Just flash this recovery from an app at play store or xda named 4ext recovery control this will work only if phone is booting or if the phone is not booting so search 4ext recovery.img or .zip on xda and flash it in your current recovery and reboot your recovery...you would now be able to get in new recovery now before flashing roms you need to enable 4ext smart flash,which is available inside tools options in 4ext recovery once you had enabled smart flash start flashing roms and they would boot...but NOTE: when ever you are flashing roms always check that is 4ext smart flash enabled or not ,you need to enable it in order to boot new roms and always make an Nandroid backup...
Happy flashing and don't forget to hit thanks
Sent from my HTCSensation using xda app-developers app
oschamp said:
Hi ..!
I like your post ..!
And I had tried this ..!
Very usefull post for unlocking bootloader
Click to expand...
Click to collapse
Thanks dude...be happy..
Sent from my HTCSensation using xda app-developers app
reddo_xda said:
hey guys,
great guide, plain and simple
I have gotten to the point of rooting the phone, however when I install roms from sd card and reboot, the phone gets stuck at the htc logo with the white background. Am I missing something...After i install the super su and reboot, can I just install a rom, or do i need to update the kernel or install an update?
thanks in advance
Click to expand...
Click to collapse
And please tell me that you're currently on CWM recovery or anyother...
Well CWM recovery is included in the package so hoping you're on custom recovery..
The only solution for your problem is that your phone should be ICS 4.0.3 updated and you should have 4ext recovery with smart flash enabled...
Or other solution is perform S-OFF..which is very hard,because of the wire trick!
Sent from my HTCSensation using xda app-developers app
help me out little bit confused ....
playboydroid said:
And please tell me that you're currently on CWM recovery or anyother...
Well CWM recovery is included in the package so hoping you're on custom recovery..
The only solution for your problem is that your phone should be ICS 4.0.3 updated and you should have 4ext recovery with smart flash enabled...
Or other solution is perform S-OFF..which is very hard,because of the wire trick!
Sent from my HTCSensation using xda app-developers app
Click to expand...
Click to collapse
Ya the same problem with my htc amaze !
whenever I flashed rom it just stuck at HTC boot logo with white background ...!
but one rom finally works that is viper amaze but in this rom there are some bugs !
for example. Bluetooth is not working, the sound is not working !
These are some bugs which make this rom worst ...
I m soo confused what to do !
And performing s-off is very risky due to wire trick !
Because may be the device get damage ..!
Soo any other help or suggestions ???
oschamp said:
Ya the same problem with my htc amaze !
whenever I flashed rom it just stuck at HTC boot logo with white background ...!
but one rom finally works that is viper amaze but in this rom there are some bugs !
for example. Bluetooth is not working, the sound is not working !
These are some bugs which make this rom worst ...
I m soo confused what to do !
And performing s-off is very risky due to wire trick !
Because may be the device get damage ..!
Soo any other help or suggestions ???
Click to expand...
Click to collapse
I assume that you are on ginger bread with old bootloader,so try CM7 or older roms that might work on your device,for flashing ICS and JB newer roms you will need to be on latest bootloader which you can get after updating your phone to ICS(official)..
if you are having unbranded HTC Amaze Ruby then you need to S-OFF or if you are having Branded i.e T-Mobile or any other just flash the RUU from boot loader....:victory:
playboydroid said:
And please tell me that you're currently on CWM recovery or anyother...
Well CWM recovery is included in the package so hoping you're on custom recovery..
The only solution for your problem is that your phone should be ICS 4.0.3 updated and you should have 4ext recovery with smart flash enabled...
Or other solution is perform S-OFF..which is very hard,because of the wire trick!
Sent from my HTCSensation using xda app-developers app
Click to expand...
Click to collapse
ok, so im at a lost, i have used 4ext recovery and used a cyanogen mod and still no luck. I followed your instructions but it still sticks at the htc logo. what is this S-off you are talking about and exactly how risky is it?
reddo_xda said:
ok, so im at a lost, i have used 4ext recovery and used a cyanogen mod and still no luck. I followed your instructions but it still sticks at the htc logo. what is this S-off you are talking about and exactly how risky is it?
Click to expand...
Click to collapse
Did you enabled smart flash inside tools options in 4ext recovery.?
Just Google s-off,you might find details about it.
And another solution is to try hasoons2000 toolkit for htc amaze and learn how to flash boot.img on bootloader..
Sent from my HTCSensation using xda app-developers app
reddo_xda said:
ok, so im at a lost, i have used 4ext recovery and used a cyanogen mod and still no luck. I followed your instructions but it still sticks at the htc logo. what is this S-off you are talking about and exactly how risky is it?
Click to expand...
Click to collapse
did you tried enabling smart flash in recovery?
for s-off visit this.
and for booting a new rom you need to flash boot.img from bootloader.
use this once you enter boot loader and your phone should be connected to pc.see this for more information.
Code:
fastboot flash boot boot.img
I got through somewhat
playboydroid said:
did you tried enabling smart flash in recovery?
for s-off visit this.
and for booting a new rom you need to flash boot.img from bootloader.
use this once you enter boot loader and your phone should be connected to pc.see this for more information.
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Ok, so i extracted the img file and loaded it using the fastboot command, it booted in to Android OS (cm-10-20131006-NIGHTLY-ruby.zip) but it keeps cutting off, I had installed the same rom previously, When loading the boot.img, do i need to extract all the other contents to a folder so it can pull all the files?
reddo_xda said:
Ok, so i extracted the img file and loaded it using the fastboot command, it booted in to Android OS (cm-10-20131006-NIGHTLY-ruby.zip) but it keeps cutting off, I had installed the same rom previously, When loading the boot.img, do i need to extract all the other contents to a folder so it can pull all the files?
Click to expand...
Click to collapse
No need to extract all files except boot.img.
Sent from my HTCSensation using xda app-developers app
then what...
playboydroid said:
No need to extract all files except boot.img.
Sent from my HTCSensation using xda app-developers app
Click to expand...
Click to collapse
ok, so im just suppose to load the boot.img file and then what, will it boot up just like that or do i need to do something else
how to flash a rom??
reddo_xda said:
ok, so im just suppose to load the boot.img file and then what, will it boot up just like that or do i need to do something else
Click to expand...
Click to collapse
1-->Flash rom in recovery with wiping, usually
[wipe data/Factory Reset and Wipe Cache + Dalvik Cache]
Click to expand...
Click to collapse
2-->boot to Bootloader while connected to PC.[note that the fastboot screen would show fastboot USB written In Red,if not so click the Fastboot Button in bootloader by pressing power button..
3-->now extract the Boot.img of your specific Rom
(which you flashed previosly in recovery..)
Click to expand...
Click to collapse
4-->use ------>
Code:
fastboot flash boot boot.img
.....
[NOTE: you should open a command propt in the folder where FASTBOOT and BOOT.IMG is present,press SHIFT and then RIGHT CLICK so you would be able to see Open command window here,click it and type the previous command...]
Click to expand...
Click to collapse
5-->you are done flashing,now reboot your device....HAPPY FLASHING.....
thank you so much!!!!!
playboydroid said:
1-->Flash rom in recovery with wiping, usually
2-->boot to Bootloader while connected to PC.[note that the fastboot screen would show fastboot USB written In Red,if not so click the Fastboot Button in bootloader by pressing power button..
3-->now extract the Boot.img of your specific Rom
4-->use ------>
Code:
fastboot flash boot boot.img
.....
5-->you are done flashing,now reboot your device....HAPPY FLASHING.....
Click to expand...
Click to collapse
ok, so I did all the above, I also installed an update:
You MUST flash the ICS firmware update when coming from a GINGERBREAD ROM before flashing Viper Amaze
Place the PH85IMG.zip in the root of your
EXTERNAL SDCARD and boot into bootloader
This will update your radio
to 1.15.550L.08D _30.80.550L. 16D
and HBOOT to 1.93.2222
I did the above, installed the Viper Amaze 1.7.2.3 official, and it worked!!!!
thanks again for your help and patient, thank you
reddo_xda said:
ok, so I did all the above, I also installed an update:
You MUST flash the ICS firmware update when coming from a GINGERBREAD ROM before flashing Viper Amaze
Place the PH85IMG.zip in the root of your
EXTERNAL SDCARD and boot into bootloader
This will update your radio
to 1.15.550L.08D _30.80.550L. 16D
and HBOOT to 1.93.2222
I did the above, installed the Viper Amaze 1.7.2.3 official, and it worked!!!!
thanks again for your help and patient, thank you
Click to expand...
Click to collapse
your welcome....Be happy and play with new roms,but always read the instructions before flashing...:good:
As I was using CM 4.4.2, everything was going fine, I had 3 bars of LTE, and then I tried to make a call and it said mobile networks not available, I checked my signal in the status bar and it still said LTE and data still worked fine. I went to my phone settings and checked it and it said my mobile network was unknown, and my phone number was 000-000-0000. I wiped, and flashed CM10.2(4.3) and it did the exact same thing, only this time it said my phone number, but still, I couldn't make any calls or text, I've tried flashing two sense 5 roms and none of them display my phone number or let me call or text, but upon changing the subscription type from global to LTE/CDMA, it gives me LTE data, but that's it...Can anyone please help me?
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
rejectedjs said:
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
santod040 said:
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
rejectedjs said:
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
Click to expand...
Click to collapse
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
rejectedjs said:
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
Click to expand...
Click to collapse
No problem bud.
Glad that worked out for you.
Same process always fixes 3g/4g issues after flashing many roms for me, on all of my devices.
:good:
This exact thing happened to me a few weeks ago. Busted my ass trying to fix it, after a few days of no service i finally got it.
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
The way you fixed it seems a lot easier than what I did. I returned to s-on, 1.15 hboot and the oldest firmware. Now my phone's bootloader will always say tampered too, since i had to HTC dev unlock it to get root.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
:good: Can't thank you enough.
I have a second DNA that I have not been able to use.
Since Moonshine S-off I have not had any data connection. It has been very frustrating.
Followed your steps and now it's back up and running.
Awesome my friend, just awesome. Thank you.
quick question
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
LuckyPuppy said:
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
Click to expand...
Click to collapse
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
how to
sdamark said:
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
Click to expand...
Click to collapse
Awesome! Thank you so much!
Where is there a stock rom
thayl0 said:
Where is there a stock rom
Click to expand...
Click to collapse
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
sdamark said:
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
Click to expand...
Click to collapse
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
thayl0 said:
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
Click to expand...
Click to collapse
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
sdamark said:
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
Click to expand...
Click to collapse
why would i do a dirty install?
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
uNdea said:
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
Click to expand...
Click to collapse
You do know flashing 3.06 ruu makes it stock recovery. Not sure of you flashed a Rom or a ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app