I was trying to flash a AOSP rom for my evo3D, used GUI flash app to flash the kernel and then flashed the AOSP rom. it was hanging on HTC screen. I've read somewhere if it does this the kernel does not support that ROM. so I restored my backup and when i did I had no wifi (running viperROM sense). I know that was because of the AOSP kernel I flashed, I used the same program and flashed the sprint stock kernel and restored my back up once again. it just hangs on the Htc screen now. my back-up no longer works.
1. is there anyway to flash a kernel using fastboot (I have 1.50 unlocked)?
update:
flashed a new recovery hoping it will change my kernel back (restored backup). it does not hang on the HTC screen anymore. but now its just a black screen, I am getting the received text sounds. when i press on the power button the home, menu, back, and search lights go on but not the screen.
TheFlatulentFox said:
I was trying to flash a AOSP rom for my evo3D, used GUI flash app to flash the kernel and then flashed the AOSP rom. it was hanging on HTC screen. I've read somewhere if it does this the kernel does not support that ROM. so I restored my backup and when i did I had no wifi (running viperROM sense). I know that was because of the AOSP kernel I flashed, I used the same program and flashed the sprint stock kernel and restored my back up once again. it just hangs on the Htc screen now. my back-up no longer works.
1. is there anyway to flash a kernel using fastboot (I have 1.50 unlocked)?
update:
flashed a new recovery hoping it will change my kernel back (restored backup). it does not hang on the HTC screen anymore. but now its just a black screen, I am getting the received text sounds. when i press on the power button the home, menu, back, and search lights go on but not the screen.
Click to expand...
Click to collapse
I haven't used the flash image gui app, so I don't have experience with it to say what might have gone wrong with the flash. However, if I were you, I would try booting your phone into recovery using fastboot. It sounds like something didn't flash right, and by booting into recovery using fastboot, you'll ensure that your boot.img (the part that has the kernel) flashes properly. So have a fresh copy of the rom you want to flash. Connect your phone to computer, and adb reboot bootloader. Then you should be in fastboot, and it'll say fastboot usb on your phone. (make sure you're in the folder that has a copy of your recovery.img) and type fastboot boot recovery.img. That will boot you to recovery. From that point, just flash the rom like normal. No need to flash the kernel separately. After you flash the rom, just try booting before flashing anything else, and see if it works.
k2buckley said:
I haven't used the flash image gui app, so I don't have experience with it to say what might have gone wrong with the flash. However, if I were you, I would try booting your phone into recovery using fastboot. It sounds like something didn't flash right, and by booting into recovery using fastboot, you'll ensure that your boot.img (the part that has the kernel) flashes properly. So have a fresh copy of the rom you want to flash. Connect your phone to computer, and adb reboot bootloader. Then you should be in fastboot, and it'll say fastboot usb on your phone. (make sure you're in the folder that has a copy of your recovery.img) and type fastboot boot recovery.img. That will boot you to recovery. From that point, just flash the rom like normal. No need to flash the kernel separately. After you flash the rom, just try booting before flashing anything else, and see if it works.
Click to expand...
Click to collapse
I will try this.
update: I did what you told me and I restored my old backup. Thank you!
TheFlatulentFox said:
I was trying to flash a AOSP rom for my evo3D, used GUI flash app to flash the kernel and then flashed the AOSP rom. it was hanging on HTC screen. I've read somewhere if it does this the kernel does not support that ROM. so I restored my backup and when i did I had no wifi (running viperROM sense). I know that was because of the AOSP kernel I flashed, I used the same program and flashed the sprint stock kernel and restored my back up once again. it just hangs on the Htc screen now. my back-up no longer works.
1. is there anyway to flash a kernel using fastboot (I have 1.50 unlocked)?
update:
flashed a new recovery hoping it will change my kernel back (restored backup). it does not hang on the HTC screen anymore. but now its just a black screen, I am getting the received text sounds. when i press on the power button the home, menu, back, and search lights go on but not the screen.
Click to expand...
Click to collapse
k2buckley said:
I haven't used the flash image gui app, so I don't have experience with it to say what might have gone wrong with the flash. However, if I were you, I would try booting your phone into recovery using fastboot. It sounds like something didn't flash right, and by booting into recovery using fastboot, you'll ensure that your boot.img (the part that has the kernel) flashes properly. So have a fresh copy of the rom you want to flash. Connect your phone to computer, and adb reboot bootloader. Then you should be in fastboot, and it'll say fastboot usb on your phone. (make sure you're in the folder that has a copy of your recovery.img) and type fastboot boot recovery.img. That will boot you to recovery. From that point, just flash the rom like normal. No need to flash the kernel separately. After you flash the rom, just try booting before flashing anything else, and see if it works.
Click to expand...
Click to collapse
I not only wrote the tool in question, Flash Image GUI, but have used it many many times on quite a few different devices and can speak to the specific process/steps followed in the OP.
I'm going to try and take a different approach to answering this post than I normally do, let me know if this makes sense.
There are essentially three sets of files which need to be loaded on the device in order for the device to boot properly and everything operate properly. By loading these three sets of files, there will be no stuck on htc boot screen and no wifi doesnt work issues.
1) The kernel
2) The kernel modules
3) The system files for the Android OS, slang term, ROM.
If any of these three sets of files have any type of conflict, there will be problems. From the standard recovery boot mode, HTC unlock only allows 2 of the above three sets of files to be flashed. By blocking one of the three sets of files from being loaded, HTC allows the system to easily get out of sync resulting in random boot issues, WiFi issues, etc.
In addition to these issues, even if all three files are properly loaded, if any of them are incompatible with any one of the other, there will be issues.
The key to avoiding issues is making sure all three of these sets of files are one, loaded properly and two compatible.
Flash Image GUI, loads the kernel and the kernel modules, but due to Linux/Android system limitations, is not able to load the system files. The recovery mode with HTC unlock loads both the kernel modules and the system files but is not able to load the kernel.
When using Flash Image GUI first, the kernel and the kernel modules both get loaded. Booting directly into the recovery will allow the system files to be loaded and the kernel modules will get reloaded.
As long as the kernel, kernel modules and system files (ROM) are all compatible, there should be no issues with this process. If somebody wants to experiment grab a kernel and match with a ROM, then we return to the two key points, make sure they are loaded properly and that they are all compatible.
Regarding how to restore a backup, if you refer back to the OP in the Flash Image GUI thread, there are steps at the bottom of the OP under the Troubleshooting section which show the proper process. I've quoted them below and bolded the needed action, for your convenience:
joeykrim said:
Troubleshooting after Rebooting:
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
Hopefully this makes sense. Let me know if you still have questions. I'm writing this off the top of my head but trying to think through it from a different angle so things are clear and organized.
joeykrim said:
As long as the kernel, kernel modules and system files (ROM) are all compatible, there should be no issues with this process. If somebody wants to experiment grab a kernel and match with a ROM, then we return to the two key points, make sure they are loaded properly and that they are all compatible.
Click to expand...
Click to collapse
that must have been my mistake, the kernel modules and ROM were not compatible. thanks joeykrim and k2buckley
So i rooted my POCO X2 and installed orange fox recovery, used the same rom which came pre-installed. Now a persistent notification of "SERIAL CONSOLE ENABLED, performance maybe impacted check bootloader to disable" hovers in my notifications, my device is running on ANDROID 11. Please help!
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 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 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!
Hey guys
I've only just got into this stuff so please forgive my ignorance, but I need a hand understanding what might have gone wrong. I've got a GSM Evo 3D which I've unlocked through htcdev, phone is still S-ON, hboot 1.53.007. I flashed CWM recovery but have since switched to 4ext.
I downloaded Viper3D, ran a backup using 4ext recovery so I could go back to stock when I feel like it, then flashed the new ROM to test it out (mainly just testing the process). The phone booted fine - no problem. On that success, I went to restore the backup I made before flashing Viper3D. The restore completed successfully from 4ext recovery, but on trying to boot my phone it just hangs on the first HTC boot screen.
Tried rebooting a few times, tried restoring a second time, did wipe/factory reset first, tried clearing cache and dalvik cache, still just hangs on that HTC boot screen. I probably left it for about 20 minutes on that screen but it didn't go anywhere.
I flashed Viper3D again, and it worked again and my phone boots up fine. So the question is, what's going wrong when I try to restore my original backup? I haven't upgraded hboot or changed the kernel.
Would appreciate if someone could shed some light on this, cheers.
Ok so I think I've figured it out but could still do with a little clarification from someone.
I've read around and found that people have fixed the HTC screen hang by flashing the boot.img with fastboot from the PC, so I decided to give it a go. I copied the boot.img from my original backup to my PC, then booted the phone up into 4ext recovery and restored the backup. After restoring had completed, I rebooted into fastboot and hooked up to my PC, then flashed the boot.img from there. Once that was done, disconnected the phone from the PC and rebooted and the phone booted up fine into my stock ROM.
One thing I noticed when flashing Viper3D is that immediately after flashing, the phone would boot to the HTC screen, then reboot a second time by itself. I now understand this is where 4ext is flashing the boot.img with Smartflash, and it didn't reboot this second time when I was trying to restore my backup so I'm guessing that's where the problem lies.
So it looks to me like 4ext/Smartflash is not doing the whole process for some reason, perhaps a bug? Smartflash is enabled permanently on my phone, so I can't think of another reason why it didn't work except that it's bugged.
Can anyone confirm this issue or have any other comments? Cheers.
zaphodalive said:
So it looks to me like 4ext/Smartflash is not doing the whole process for some reason, perhaps a bug? Smartflash is enabled permanently on my phone, so I can't think of another reason why it didn't work except that it's bugged.
Can anyone confirm this issue or have any other comments? Cheers.
Click to expand...
Click to collapse
Read the requirements for the SmartFlash feature to work on the OP of the 4EXT Recovery thread, and in particular the limitations section. My guess is that you didn't have a bootable kernel when trying to use the SmartFlash option.
An easier way to re-flash the ROM in that situation is to start recovery with this fastboot command:
fastboot boot recovery.img (where recovery.img is the name of your 4EXT recovery file)
Click to expand...
Click to collapse
That command will boot any custom recovery in a mode that will let it flash the entire ROM from recovery, but for 4EXT you have to make sure that the SmartFlash/S-ON option is disabled in the tools menu and then flash the ROM zip file.
ramjet73
Ok thanks, just to clarify - by doing fastboot boot recovery.img, that would reboot the phone into 4ext recovery and allow it to flash both boot.img and recovery.img when flashing the ZIP? What exactly is the fastboot command doing that allows this?
Cheers
zaphodalive said:
Ok thanks, just to clarify - by doing fastboot boot recovery.img, that would reboot the phone into 4ext recovery and allow it to flash both boot.img and recovery.img when flashing the ZIP? What exactly is the fastboot command doing that allows this?
Cheers
Click to expand...
Click to collapse
The "fastboot boot" command starts the recovery as an OS image and just like Android it has the ability to flash the boot partition (kernel) when loaded that way. When started in the "recovery" mode it is not able to flash the boot partition when the phone is S-ON.
SmartFlash uses the same principle to flash the boot partition after the existing kernel is booted, but if the current kernel is not bootable SmartFlash doesn't work.
ramjet73
Ok, I kinda understand (without quite understanding)... can the same command be used for flashing ROMs in a ZIP? e.g. fastboot boot yourromhere.zip
Thanks
zaphodalive said:
Ok, I kinda understand (without quite understanding)... can the same command be used for flashing ROMs in a ZIP? e.g. fastboot boot yourromhere.zip
Thanks
Click to expand...
Click to collapse
No. The "fastboot boot" command only works with bootable images and not zip files.
ramjet73
Thanks very much for your help. A couple of final questions...
How can you flash a custom ROM in a ZIP with fastboot? e.g. the Viper3D ZIP didn't have a recovery.img, only a boot.img
Also, I'm downloading Cool ICS and CoolZ kernel, and this is my first time flashing a kernel. Checked the CoolZ ZIP file and there's no boot.img which I was expecting, so I'm hoping that 4ext won't have any problems flashing it..? Also not sure whether to flash CoolZ or Cool ICS first.
Cheers
The fastboot commands are part of the bootloader (hboot) and custom ROM's are flashed by recovery.
There are guides in the general forum that cover ROM flashing procedures including this one by mpgrimm2.
ramjet73
Thanks, getting stuck installing the CoolZ kernel. I rebooted into 4ext with fastboot boot recovery.img, disabled Smartflash, tried flashing the ZIP, and after extracting files I got the error message:
assert failed: write_raw_image(" /tmp/newboot.img", "boot")
I assume this means it failed writing to the boot partition... any thoughts why?
zaphodalive said:
assert failed: write_raw_image(" /tmp/newboot.img", "boot")
I assume this means it failed writing to the boot partition... any thoughts why?
Click to expand...
Click to collapse
If the assert fails that usually means you are trying to flash something that's not intended for your device. Make sure you are flashing the correct version since there are CoolZ kernels for both the CDMA and GSM Evo 3D models.
Edit: I just checked and it looks like the CoolZ v4.5 kernel has one installation file for both Evo 3D models.
Make sure you can boot into the ROM you flashed before you try to flash the kernel.
ramjet73
Ok, a little weird...
I tried installing the CoolZ kernel, that failed (as mentioned before), then I installed the v14 ROM and v14b update. Booted up the phone, had no WIFI (just said error). So I flashed the boot.img from the v14b ZIP after that to see if I'd get WIFI back, got a couple of bootloops on the splash screen, and it then booted up with WIFI working and the CoolZ kernel installed.
I originally downloaded the CoolZ kernel separately from the Cool ICS ROM, but it appears that the kernel is part of the ROM package so I didn't need to do that.
Anywho, seems to be working now so I'll have a fiddle around. Thanks very much for your help.
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.