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!
Related
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.
my HH has an unique issue when i flashing another custom rom....
before i flashed i already done this :
wipe data/cache/dalvik 3x each of them.....
and after it finished to flash and reboot its stuck on HTC logo.
this issue encountered when i flash another custom rom except the synergy 3dvo from nightly....
please help me solve this problem....
thx b4
didit.here said:
my HH has an unique issue when i flashing another custom rom....
before i flashed i already done this :
wipe data/cache/dalvik 3x each of them.....
and after it finished to flash and reboot its stuck on HTC logo.
this issue encountered when i flash another custom rom except the synergy 3dvo from nightly....
please help me solve this problem....
thx b4
Click to expand...
Click to collapse
Sounds like your kernel is not getting flashed. If you used HTC's method to unlock you'll need to use fastboot to flash the boot.img
xHausx said:
Sounds like your kernel is not getting flashed. If you used HTC's method to unlock you'll need to use fastboot to flash the boot.img
Click to expand...
Click to collapse
yeah, im using unlock method... does it mean i have to run it in fastboot usb mode if i wanna flash??
my htc is in newest OTA and in hboot 1.500
didit.here said:
yeah, im using unlock method... does it mean i have to run it in fastboot usb mode if i wanna flash??
my htc is in newest OTA and in hboot 1.500
Click to expand...
Click to collapse
I've answered this type of question a few times in other posts. I've edited my answer from a few minutes ago to help answer your question. Feel free to post back if anything isn't clear!
http://forum.xda-developers.com/showpost.php?p=18807723&postcount=3
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any 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.
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.
Hope that helps!
Click to expand...
Click to collapse
joeykrim said:
I've answered this type of question a few times in other posts. I've edited my answer from a few minutes ago to help answer your question. Feel free to post back if anything isn't clear!
http://forum.xda-developers.com/showpost.php?p=18807723&postcount=3
Click to expand...
Click to collapse
whoaa it was really helping me, thx man for the suggestion.....
i think i have to try it
sorry, im to noob in flashing method
hey fam i was running virus rom Eternity 3.0 with stock kernel then i flashed the cm7 rom by joelz yesterday but had to change kerenls to get it to work. i used the apk to do that i think its gui i think, but anyway i tried to restore back from nadroid and my phone wont boot. im on 1.5 with s-on
thanks if any one can help.
evoguy404 said:
hey fam i was running virus rom Eternity 3.0 with stock kernel then i flashed the cm7 rom by joelz yesterday but had to change kerenls to get it to work. i used the apk to do that i think its gui i think, but anyway i tried to restore back from nadroid and my phone wont boot. im on 1.5 with s-on
thanks if any one can help.
Click to expand...
Click to collapse
I guess you have flashed a 2.3.3 kernel so you are experiencing issues.........so now just boot your phone in bootloader then select fastboot > connect your phone to pc (it should say fastboot usb on phone)> now open cmd > head to your fastboot folder in cmd> then type fastboot boot xxxxx.img (xxxx = your recovery img (cwm/twrp) ) > Now your phone will boot into recovery > then restore your Nandroid backup .......
Hope this helps
If the above didnt work try to flash boot.img from your nandroid backup using fastboot (not recovery) with command "fastboot flash boot boot.img"
press thanks if i helped you
is there a way i can do it without my computer im at work,so i don't have all my files on hand...thanks this has got me stomped......
I m sorry you cannot do it without a pc .....you know the limitations of htc unlock method...you can only flash kernels made for 2.3.4 from flash image gui......you can always download those fastboot/adb files from here or google for it.They are just a few kb's
evoguy404 said:
is there a way i can do it without my computer im at work,so i don't have all my files on hand...thanks this has got me stomped......
Click to expand...
Click to collapse
Yes, as long as all the nandroid backup files are on your sdcard. Steps below.
mnomaanw said:
I m sorry you cannot do it without a pc .....you know the limitations of htc unlock method...you can only flash kernels made for 2.3.4 from flash image gui......you can always download those fastboot/adb files from here or google for it.They are just a few kb's
Click to expand...
Click to collapse
This isn't true. Flash Image GUI will flash the kernel for any version, but if your system OS is not also updated at the same time, the device will not boot.
If you're looking to do a nandroid restore w/o using fastboot (or being attached to a computer), here are the steps I would suggest:
1) From Flash Image GUI, select the boot.img from inside of the custom recovery backup directory on the /sdcard. Flash this kernel.
2) Reboot directly into recovery mode. Run the nandroid restore for that SAME backup as the boot.img was pulled from and flashed via Flash Image GUI.
3) After nandroid restore finishes, reboot and the device should be back to the previous state found in the backup.
Remember, this is a work around for the HTC unlock and might not always be the best solution.
Keep us updated and let us know. Hope that helps!
joeykrim said:
Yes, as long as all the nandroid backup files are on your sdcard. Steps below.
This isn't true. Flash Image GUI will flash the kernel for any version, but if your system OS is not also updated at the same time, the device will not boot.
If you're looking to do a nandroid restore w/o using fastboot (or being attached to a computer), here are the steps I would suggest:
1) From Flash Image GUI, select the boot.img from inside of the custom recovery backup directory on the /sdcard. Flash this kernel.
2) Reboot directly into recovery mode. Run the nandroid restore for that SAME backup as the boot.img was pulled from and flashed via Flash Image GUI.
3) After nandroid restore finishes, reboot and the device should be back to the previous state found in the backup.
Remember, this is a work around for the HTC unlock and might not always be the best solution.
Keep us updated and let us know. Hope that helps!
Click to expand...
Click to collapse
hey joey i know we can use flash image gui to flash boot.img from a rom.zip but evoguy cannot boot his phone at all.So how will he be able to use Flash image GUI? I m only telling him what he can do now........
mnomaanw said:
hey joey i know we can use flash image gui to flash boot.img from a rom.zip but evoguy cannot boot his phone at all.So how will he be able to use Flash image GUI? I m only telling him what he can do now........
Click to expand...
Click to collapse
If the device won't boot past the splash screen, chances are the issue is kernel related. For kernel related issues, the ONLY method provided by HTC via their unlock is to use fastboot to boot the recovery. This is the only accessible mode HTC grants write access to the kernel partition.
This is the only way HTC provides write access to the kernel for a device that is not booting properly. The command using fastboot is as follows: fastboot boot c:\recovery.img .
This command will temporarily load the custom recovery with kernel write access allowing a proper recovery to take place.
One reason the device is not booting could be the android OS version mismatches with the kernel, therefore the kernel's ramdisk is looking for files which are not present and cause the device to either freeze or reboot.
There are other reasons too, probably too many worth detailing out as the easiest route to solving the issue is to restore back to a known good working nandroid or cleanly load another known working ROM/kernel combination.
Hope that helps clarify! Best of luck!
Thanks to all you guys. Got it back running XDA is the best.
sent from my Rooted & Boosted 3VO.
I tried booting various sense and aosp roms, but my phone won't boot past the flying 3d or any other boot animations. Can someone please help? I tried wiping everything. It worked at first but it doesn't now.
I think this belongs in the questions part of the thread.(Im sure a mod might move it) Other than that can you even do a Nandroid restore?
SilverSuperman said:
I think this belongs in the questions part of the thread.(Im sure a mod might move it) Other than that can you even do a Nandroid restore?
Click to expand...
Click to collapse
i tried that too. I think it has to do something with flashing a bad kernel
Ok in order for anyone to help you more could you please tell which hboot you have, also specify further about your problem. For example: does your phone just freeze at some point or does the bootscreen keep running and never gets past it or is it taking over the world or what?
---------- Post added at 12:08 AM ---------- Previous post was at 12:05 AM ----------
Im asking because there has been alot of views on this and ppl just pass it up because its in the wrong section. Dont take offense to this plz. Im sure u knew this due to you have been a member since Oct. 2009
SilverSuperman said:
Ok in order for anyone to help you more could you please tell which hboot you have, also specify further about your problem. For example: does your phone just freeze at some point or does the bootscreen keep running and never gets past it or is it taking over the world or what?
Click to expand...
Click to collapse
HB1.5
it keeps freezing at the flying 3d animatio.
I think you should re-post this in the questions and answers part of the thread and leave this one alone. Otherwise theres gonna be ppl that will "flame" you and say that we have a section for questions and answers. Technically of course it doesnt belong here anyways. Just re-post it over there too and for some reason ppl will be more willing to help you.
ok heres your fix
1-take the rom of your choice put in your sd card
2-then take boot.img out of your rom and recovery.img of your choice and place it in android-sdk/platform-tools
(rename recovery u have to recovery.img then place it in android-sdk/platform-tools)
3-if runing widows hold shift and right click then open with command prop
4-then reboot your phone into fastboot (make sure u have fastboot drivers installed)
5- then type this in command prop
fastboot flash boot boot.img
after its done type this
fastboot boot recovery.img
then it will take u into recovery then do all wipes and flash rom of your choice
and enjoy
hope this helps u
sac23 said:
ok heres your fix
1-take the rom of your choice put in your sd card
2-then take boot.img out of your rom and recovery.img of your choice and place it in android-sdk/platform-tools
(rename recovery u have to recovery.img then place it in android-sdk/platform-tools)
3-if runing widows hold shift and right click then open with command prop
4-then reboot your phone into fastboot (make sure u have fastboot drivers installed)
5- then type this in command prop
fastboot flash boot boot.img
after its done type this
fastboot boot recovery.img
then it will take u into recovery then do all wipes and flash rom of your choice
and enjoy
hope this helps u
Click to expand...
Click to collapse
You can take the boot.img piece out that is not needed. Once you power on phone holding power and volume down, choose fastboot, connect usb, and just do fastboot boot recovery.img this will give you full access and when you flash the rom, it will install kernel and all necessary files.
Sent from my PG86100 using XDA App
He provided the fix for the problem he's having right now. So his steps are correct. Now in the future he'd want to do the
Code:
fastboot boot recovery.img
To help with flashing in the future.
nolimit78 said:
He provided the fix for the problem he's having right now. So his steps are correct. Now in the future he'd want to do the
Code:
fastboot boot recovery.img
To help with flashing in the future.
Click to expand...
Click to collapse
I didn't think that was needed. What exactly does fastboot flash boot boot.img do?
Sent from my PG86100 using XDA App
There is a limitation with HTC's unlock, recovery does not have permission to write to the boot partition, this is where the kernel goes. What this means is that you can't flash a kernel through the normal recovery. Which also means that you can't flash a ROM that requires a custom kernel. There are two ways that I know of to work around this. One is to just flash the kernel(boot.img) from fastboot, the other, and easier way is to boot recovery from fastboot and just do everything from there.
Sent from my PG86100 using XDA App
is there a way around all of this besides fastboot? or anything i can do in recovery instead?
mariojp said:
is there a way around all of this besides fastboot? or anything i can do in recovery instead?
Click to expand...
Click to collapse
My 3D is not yet rooted, but you should be able to flash everything you need without a computer. You will need Flash Image GUI, which is found in the market, or can be downloaded via the XDA post. It's JoeyKrim's program.
Here's a stickied thread, over in the Android Dev forum
http://forum.xda-developers.com/showthread.php?t=1306248
I used the app to flash kernal now when I flash rom I am stuck in bootloader. I know its the fault of the app. I can't nandroid restore either. need help
charlesvw9 said:
I used the app to flash kernal now when I flash rom I am stuck in bootloader. I know its the fault of the app. I can't nandroid restore either. need help
Click to expand...
Click to collapse
First, I do want to thank you for posting this instead of filling up my PM on XDA.
Second, I disagree with part of your post as I don't think it is the fault of the application. Sounds as if the user has flashed an incompatible kernel. The application can only do so much to check, verify, prompt the user for confirmation, etc. but as the old saying goes, "garbage in, garbage out".
Can you provide a link to the kernel?
On to some possible solutions to remedy this situation!
In my Flash Image GUI thread OP, more than likely the location where you obtained a link for the actually application file, I have the following suggestions for troubleshooting, with the assumption you're on hboot 1.5:
Issue #1: If the device hangs or reboots while on the splash screen, the kernel (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
Click to expand...
Click to collapse
Have you tried using recovery from fastboot mode to properly restore a nandroid?
If you have no known working nandroid (very poor decision), you're next best step is to flash a ROM which includes a kernel from fastboot boot recovery mode, using the same command given in the quote of my OP. fastboot boot c:\downloads\cwm-recovery.img will load the custom recovery in a temporary fastboot mode granting it write access to the kernel partition via HTC's unlock.
Hope this helps and good luck! Keep is udpated.
I meant to say, I know it is not the fault of the app
I had this same thing happen to me and no it's the gui app, it's the kernel that was being flashed. If u have a nand back up then just do the fastboot method of flashing. I recommend even flashing the proper kernel first then the back up. @ joey thanks for the awesome app. I've used it so much I'm supprised I don't get a message asking me to give it a break!