I'm writing this as these questions commonly get asked in the development threads, taking them off topic.
S-ON users commonly run into these problems, which are quite simple to solve with the right information.
When your device is S-ON and unlocked via the HTC Method, the boot partition is mounted read-only in recovery mode, which causes these problems flashing custom kernels or custom roms.
a) Flashing a custom kernel through recovery mode breaks wifi:
Android uses the linux kernel, and the wifi drivers are compiled as kernel modules. The kernel modules are located in /system/lib/modules, and the linux kernel is located on the boot partition. When you flash the kernel zip file through recovery, the updated kernel modules get successfully written to the system partition however the linux kernel cannot get written to the boot partition. The result of this is that the kernel now cannot load the wifi kernel modules. This is what causes the WIFI error.
Solution: Download FlashImgGui from the market, and use that to install the kernel. This program can successfully write the new kernel to the boot partition eliminating the mismatch between the kernel and wifi modules.
b) Flashing a custom rom through recovery breaks wifi.
This problem is basically the same as a). The boot partition cannot be written so the kernel that came with the rom isn't written to it. This causes a mismatch between the kernel modules in the custom rom and the kernel.
Solution: You can either flash a custom kernel with FlashImgGui, or extract the boot.img file from the custom rom's zip file and copy to your computer. Then use the fastboot binary to flash the boot.img to the boot partition. This will copy the kernel that is packaged with the rom to your phone, which will fix the mismatch between the kernel and wifi modules.
C) Flashing a custom rom through recovery causes boot loops or the phone hanging at the HTC screen.
Some custom roms need a different initrd.gz file to the standard one. The initrd.gz file is located on the boot partition. When you flash the custom rom through recovery, the boot partition cannot get written and so the new initrd.gz isn't written to it. This is what causes the problems booting.
Solution: Same as above. Extract the boot.img from the zip file and flash with fastboot. This will copy the correct initrd.gz file to your phone and allow the rom to function correctly.
MODS: If you feel this is in the wrong section please move it. I'm only posting here as these questions always pop up in the development threads.
exactly what i have discovered
i can provide the testimony that the above are correct !
THANKS FOR CONFIRMING IT
actually it can be solved by
1. booting into bootloader (or via cmd :adb reboot bootloader)
2. flash boot "cwm.img" <<<name of the cwm file
3. flash via cwm
4. wifi will back on
ilovemeow said:
actually it can be solved by
1. booting into bootloader (or via cmd :adb reboot bootloader)
2. flash boot "cwm.img" <<<name of the cwm file
3. flash via cwm
4. wifi will back on
Click to expand...
Click to collapse
That method is useful for avoiding the problems in the first place, but its easier to flash the boot.img than flash recovery and reinstall the ROM for users who already have the problem.
doesnt it has any thing to do with the RADIO ???
because my phone came with another radio than the widely used one
and hboot 1.18
and I had tons of problems with wifi with every single rom
so I downgraded it to hboot 1.07 by flashing the EU 1.20 rom which came with the radio used here and achieved s-off using revolutionary
and all wifi problems were gone for good
s_superman said:
doesnt it has any thing to do with the RADIO ???
because my phone came with another radio than the widely used one
and hboot 1.18
and I had tons of problems with wifi with every single rom
so I downgraded it to hboot 1.07 by flashing the EU 1.20 rom which came with the radio used here and achieved s-off using revolutionary
and all wifi problems were gone for good
Click to expand...
Click to collapse
Absolutely nothing to do with the radio. Your wifi problems were solved once you got S-OFF . S-OFF means the boot partitions is mounted read-write in recovery mode so you do not have any of the problems I listed in the OP.
Where exactly do you flash the boot.img to when you need the custom rom's initrd? I.e. for 'fastboot flash xyz "boot.img"', what's the xyz?
Sent from my HTC EVO 3D X515m using XDA App
waltibaba said:
Where exactly do you flash the boot.img to when you need the custom rom's initrd? I.e. for 'fastboot flash xyz "boot.img"', what's the xyz?
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
"fastboot flash boot boot.img"
I guessed as much, but wasnt gonna risk my phone without asking. Thank you!
Sent from my HTC EVO 3D X515m using XDA App
hi i have no access to market and i dont find the link to download out of market plz any one can upload the apk or zip and put the link ????
sahandv1989 said:
hi i have no access to market and i dont find the link to download out of market plz any one can upload the apk or zip and put the link ????
Click to expand...
Click to collapse
Here's a link to the thread:
http://forum.xda-developers.com/showthread.php?t=1192527&highlight=flash+image+gui
Please try the search button next time, it is usually the best place to start here
Two days working and the solution was under my nose!
THANK YOU!
Thanks for the information, but I don't think it's entirely accurate. Those with older phones (that haven't taken updates from HTC) will possibly have the old radio firmware. And if you are S-ON and HBOOT1.5, there's no way to 'get' the new firmware on the phone if you are unlocked.
So you must get the updated radio firmware (1216), put in in the root, relock the phone, and do a bootloader boot to flash the radio firmware. Unlock again, and then you are good to go. I had the 8xx version radio firmware and couldn't run any newer ROMS with working wifi until I got the updated firmware.
Be advised that lock/unlocking wipes your phone.
I followed the instructions but it doesn't work
What I did is:
1) Installed the custom ROM
2) installed the boot.img from fastboot
3) rebooted -> but stuck at htc logo
My friend's EVO 3D GSM has:
HBOOT 1.49.0018
S-ON
Unlocked
Can someone help me??
thanks in advance
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
xlxcrossing said:
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
Click to expand...
Click to collapse
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
JayDaKissEP said:
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I did not use that method to flash, no. I'm assuming you mean from my PC execute the command. I did follow the instructions to install TWRP which is a custom recovery and I flashed a ZIP from TWRP for Superuser and checked it to be working which it was. (I tested Root Explorer and Terminal Emulator for root)
I was operating off the assumption that custom roms with a STOCK kernel could be flashed by booting into recovery. I went to bootloader then recovery then flashed the rom. Obviously I did something wrong since both roms wouldn't load. I will use your method of PC commands from fastboot into recovery and see where that gets me....pease let me know if this is correct or anything else I need to do....thanks a bunch.
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
xlxcrossing said:
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
Click to expand...
Click to collapse
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
ifly4vamerica said:
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
Click to expand...
Click to collapse
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
xlxcrossing said:
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
Click to expand...
Click to collapse
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Twolazyg said:
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Click to expand...
Click to collapse
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
JayDaKissEP said:
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
ifly4vamerica said:
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
Click to expand...
Click to collapse
Yeah I read all about it I'm still stuck on why if I had a stock kernel installed with a stock rom and I do a custom rom flash and as stated it doesn't touch the kernel why the rom wouldn't simply run off the stock kernel - that's what confuses me. I understand the issue of the kernel not being flashed which is obviously what happened with me. I just don't really know where I stand with what kernel to ALWAYS have loaded since if that's the thing with the issue I would want to for purposes of not doing tons of work stay away from flashing kernels and stick to flashing roms when I want to change it up. But if the STOCK kernel won't load with a custom rom which technically it should I guess I'll just have to flash a universal custom kernel and assume any rom I flash will simply use that kernel. Kind of a nightmare compared to my 4G....welcome to the world of the 3D I guess.
I guess going into recovery from hboot with the volume and power buttons wouldn't count - I have to stick with PC commands?
Okay, so I was having a hell of a time trying to install Roms after unlocking. All the usual ways didn't work. Flat out.
What I found out:
I have to use Clockwork Mod 4.0.1.4 (TWR can't restore the nand it creates and Flash_Utility GUI doesn't work)
I have to flash a kernal within Clockwork after flashing the Rom (flashing a boot.img in fastboot doesn't work even though it says it was successful)
I have NO clue why my phone doesn't play nice with boot image like other phones. Luckily Tiamat writes good kernels
Mes3 said:
Okay, so I was having a hell of a time trying to install Roms after unlocking. All the usual ways didn't work. Flat out.
What I found out:
I have to use Clockwork Mod 4.0.1.4 (TWR can't restore the nand it creates and Flash_Utility GUI doesn't work)
I have to flash a kernal within Clockwork after flashing the Rom (flashing a boot.img in fastboot doesn't work even though it says it was successful)
I have NO clue why my phone doesn't play nice with boot image like other phones. Luckily Tiamat writes good kernels
Click to expand...
Click to collapse
You have to add superuser to the ROM and give necessary permissions to Flash image GUI to flash kernels with it.
Which ROM are you trying to flash? Do you GSM or CDMA Evo 3D?
Flashing boot.img in fastboot should work.It does say not successful as you stated.
Make sure you bootloader says unlocked and flash kernels/ROMs based on 2.3.4 if your phone came with 2.3.4.
@Mes3 ,
Does this sound similar to your problem?
[help]HTC Unlocked ROM/Recovery install Problems (fastboot/FlashimageGui/RomMgr)
http://forum.xda-developers.com/showthread.php?t=1450466
I been searching around all over the place and I am just hitting my head against the wall. Any help would be appreciated.
This is my setup: hboot 1.5 S-ON, I have unlocked using the HTC method. I have Revolutionary CWM recovery installed.
I am looking to update the Kernel and Radio/PRI of the phone to the latest versions. (I haven't done it in a very long time.)
By what I read, since I have hboot 1.5 updating the kernel seems close to impossible. I did read that I may have to go to a Stock Rom and update via sprint OTA to get the latest updates then unlock again? That doesnt sound right to me.
I am all types of confused. Part of this was started because I wanted to try the MeanROM (link:http://forum.xda-developers.com/showthread.php?t=1466362) and also update my phone. Everything I try to do fails or I cant do because of the 1.5 or the S-ON.
Hopefully i am making some sense. I dont know what I have to do to get the latest kernel or if it even is possible.
If you are rooted already the only thing you need to do is install flash GUI app (you can get it in the market) and flash the kernel (boot.img) file before you flash the ROM and you should be OK
There is a myth that if your on 1.5 s-on your doomed, that's not true. It does mean that you'll need an extra step to do things but you'll be able to get things done without issues.
Sent from my Xoom using Tapatalk
megabiteg said:
If you are rooted already the only thing you need to do is install flash GUI app (you can get it in the market) and flash the kernel (boot.img) file before you flash the ROM and you should be OK
There is a myth that if your on 1.5 s-on your doomed, that's not true. It does mean that you'll need an extra step to do things but you'll be able to get things done without issues.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
spiderz13 said:
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
Click to expand...
Click to collapse
If your firmware is compatible with the Rom and kernel yes. If not, you will brick your phone or features will not work as they have to do. After you install flash GUI go to browse button and you will be advertised that file is too large for a kernel or recovery image, then asks if it is a valid Rom zip file. Tap yes and it will search the kernel inside the Rom. After it finishes tap flash and after reboot in recovery(you have to have recovery.img in root of your SD card), next wipe dalvik and cache, install zip and wait until the phone finishes. It is also recommended to you to make a nandroid backup before install anything.
spiderz13 said:
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
Click to expand...
Click to collapse
For the EVO 3D, much like the EVO 4G, the custom ROMs generally do not contain the radio or pri images.
There are some different reasons for this, but one of the common reasons being some users claim to experience different radio performance based on their geographic loation in relation to different versions of the radio and pri images.
luis4ever said:
If your firmware is compatible with the Rom and kernel yes. If not, you will brick your phone or features will not work as they have to do. After you install flash GUI go to browse button and you will be advertised that file is too large for a kernel or recovery image, then asks if it is a valid Rom zip file. Tap yes and it will search the kernel inside the Rom. After it finishes tap flash and after reboot in recovery(you have to have recovery.img in root of your SD card), next wipe dalvik and cache, install zip and wait until the phone finishes. It is also recommended to you to make a nandroid backup before install anything.
Click to expand...
Click to collapse
The only clarification to this post would be having recovery.img in the root of your SD card is not required for rebooting into recovery mode. In order for a custom recovery to load, when rebooting into recovery mode, the recovery.img has to have been flashed previously. Flash Image GUI can also flash the recovery.img to the recovery partition so when you reboot into recovery, the proper custom recovery loads. Most users flash custom recoveries infrequently when compared to how often they flash ROMs so the process for flashing the recovery process isn't covered as often.
In general, regarding the OP's original question of flashing the "MeanROM", the Flash Image GUI thread provides a great beginner step by step guide I wrote to help walk thru the general overview and process. I've quoted it below for easy reference.
Appreciate all the support of Flash Image GUI! I'll echo the optimism for hboot 1.5 s-on unlocked users, most everything is still possible. HTC just requires an extra few steps which can be frustrating, but once they are learned, the process is fairly smooth.
Hope the clarification helps iron out any confusion on the details!
HTC Unlock - Hboot 1.5 Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using HTC method for Hboot 1.5 users
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
Click to expand...
Click to collapse
Help!!! I am willing to pay someone $50 via Paypal to help me resolve my issues.
Here is my story. I have a DNA bought a month ago. Have not installed the latest OTA updates. I wanted to root it because I had my Thunderbolt rooted and was using the Wifi Tether app which was great.
So last night I followed exact directions and rooted the phone. I first did all the unlocking the boot loader then installed TWRP recovery, etc then rooted it. I am sorta a newbie when it comes to rooting but I have done about 5 Thunderbolts for friends and families without any issues.
So after the root things seems to be OK. I went ahead and installed the Wifi Tether app (the yellow one) but it did not work. I then checked SuperSU and it kept saying the binaries needed to be updated but everytime I told it to do that the phone would reboot and if I go back into SuperSU then it would say binaries needed to be updated again. I researched then installed Superuser and chose to use that instead. At this point the Wifi stopped working. It would say "turning on" but never does.
So I tried different ROMs including the HTC sense rooted, Viper, CM Mod, whatever.
With different ROMs either I still experience the same Wifi not turning on or get message "unfortunately, the process com.android.phone has stopped" and it would be like that every 2 seconds.
At this point I am so disgusted as it wasted so much of my time. All I wanted was to get wifi hotspot which I assumed I had to root.
This is a nightmare and at this point I still would like to root it but more importantly I need a working phone like it was before I rooted this.
If anyone willing to invest some time and help me straighten this out I can pay you $50 by Paypal. It maybe an easy fix but I gave up.
Vince
did you flash a kernel with system write enabled?
with each rom usually comes a boot.img in a zip file (or the rom dev will have a separate download) and what you need to do is copy the boot.img file to where you have adb.exe, then issue the following:
Code:
adb reboot bootloader
Flash boot.img in Bootloader by doing this (make sure on the phone screen when you are in bootloader it says "fastboot usb") :
Code:
fastboot flash boot boot.img
Then once you flashed your boot.img file reboot to recovery and then flash the rom and modules (usually the modules.zip is in with the boot.img) take the modules.zip place them on your sdcard where ever you like and after you flash the rom then flash the modules.zip in recovery and that should fix your wifi issues and by flashing the correct kernel(boot.img) that will fix the su binaries and they will update
oh and if you are on a shared data plan the wifi tethering is free...
hondaguy28 said:
Help!!! I am willing to pay someone $50 via Paypal to help me resolve my issues.
Here is my story. I have a DNA bought a month ago. Have not installed the latest OTA updates. I wanted to root it because I had my Thunderbolt rooted and was using the Wifi Tether app which was great.
So last night I followed exact directions and rooted the phone. I first did all the unlocking the boot loader then installed TWRP recovery, etc then rooted it. I am sorta a newbie when it comes to rooting but I have done about 5 Thunderbolts for friends and families without any issues.
So after the root things seems to be OK. I went ahead and installed the Wifi Tether app (the yellow one) but it did not work. I then checked SuperSU and it kept saying the binaries needed to be updated but everytime I told it to do that the phone would reboot and if I go back into SuperSU then it would say binaries needed to be updated again. I researched then installed Superuser and chose to use that instead. At this point the Wifi stopped working. It would say "turning on" but never does.
So I tried different ROMs including the HTC sense rooted, Viper, CM Mod, whatever.
With different ROMs either I still experience the same Wifi not turning on or get message "unfortunately, the process com.android.phone has stopped" and it would be like that every 2 seconds.
At this point I am so disgusted as it wasted so much of my time. All I wanted was to get wifi hotspot which I assumed I had to root.
This is a nightmare and at this point I still would like to root it but more importantly I need a working phone like it was before I rooted this.
If anyone willing to invest some time and help me straighten this out I can pay you $50 by Paypal. It maybe an easy fix but I gave up.
Vince
Click to expand...
Click to collapse
Find a kernel you like and flash both parts of it.
Flash the modules in recovery and flash the boot.img wither in fastboot using "fastboot flash boot boot.img" or using the flash img gui app.
Sent from my HTC6435LVW using xda app-developers app
ninja'd by Bigandrewgold
You need to flash a kernel with system write enabled. Since you are not S-off you have to flash the kernel via fastboot and then reboot to recovery and flash the kernel modules zip that comes with your kernel of choice. Without system write enabled you cannot update busy box. If you do not have adb or fastboot enabled to flash the kernel via fastboot there is a tool suite that will help. Most wifi issues are because of not having flashed the modules.zip in recovery after flashing the kernel. Once you get that fixed there is a thread in the Questions section where I posted my Wifi Tether settings that work with the DNA.
Thanks for the fast responses. I like the Viper DNA ROM. I will try to follow your directions. I will be home in a couple of hours and will try it and plan on spending all night if I need to get this thing working.
Vince
Man I'm counting my cash already look out suckers.. J/K I really don't know anything..
.torrented said:
did you flash a kernel with system write enabled?
with each rom usually comes a boot.img in a zip file (or the rom dev will have a separate download) and what you need to do is copy the boot.img file to where you have adb.exe, then issue the following:
Code:
adb reboot bootloader
Flash boot.img in Bootloader by doing this (make sure on the phone screen when you are in bootloader it says "fastboot usb") :
Code:
fastboot flash boot boot.img
Then once you flashed your boot.img file reboot to recovery and then flash the rom and modules (usually the modules.zip is in with the boot.img) take the modules.zip place them on your sdcard where ever you like and after you flash the rom then flash the modules.zip in recovery and that should fix your wifi issues and by flashing the correct kernel(boot.img) that will fix the su binaries and they will update
oh and if you are on a shared data plan the wifi tethering is free...
Click to expand...
Click to collapse
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
hondaguy28 said:
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
Click to expand...
Click to collapse
Download this its the ROM and put it on your /sdcard in your phone: http://www.androidfilehost.com/?fid=9390288116658473299
Then
Go here and download this .zip its what ViperDNA Recommends (but later if you want to you can download any kernel you wish)
http://forum.xda-developers.com/showthread.php?t=2064066
Now this is what you do with this second download, open the .zip and there will be a boot.img and a Modules.zip
place the modules.zip where you placed the ViperDNA .zip, then take the boot.img and place it where you have your adb.exe file
then boot into the bootloader where it says "fastboot usb"
now after you get into fastboot issue the
Code:
fastboot flash boot boot.img
then it will flash the boot.img file after it completes on the phone boot into recovery
then do all of the wipes (FR, cache, dalvik) then flash the viperdna rom and after that finishes flash the modules.zip then you can boot into the rom and everything should be working
then once you get all of those done you should get some kind of notification from ViperDNA to flash some kind of OTA (their versions there should be three) to update to the latest ViperDNA
here is the viperdna thread http://forum.xda-developers.com/showthread.php?t=2105745 for w/e you need it for
if you need anymore help just send me a PM ill be more than happy to help
hondaguy28 said:
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
Click to expand...
Click to collapse
Go to the Rom thread. There will be a link for the Rom for you to install and there will be another download for the boot.img for you to flash.
Sent from my HTC6435LVW using xda app-developers app
.torrented said:
Download this its the ROM and put it on your /sdcard in your phone: http://www.androidfilehost.com/?fid=9390288116658473299
Then
Go here and download this .zip its what ViperDNA Recommends (but later if you want to you can download any kernel you wish)
http://forum.xda-developers.com/showthread.php?t=2064066
Now this is what you do with this second download, open the .zip and there will be a boot.img and a Modules.zip
place the modules.zip where you placed the ViperDNA .zip, then take the boot.img and place it where you have your adb.exe file
then boot into the bootloader where it says "fastboot usb"
now after you get into fastboot issue the
Code:
fastboot flash boot boot.img
then it will flash the boot.img file after it completes on the phone boot into recovery
then do all of the wipes (FR, cache, dalvik) then flash the viperdna rom and after that finishes flash the modules.zip then you can boot into the rom and everything should be working
then once you get all of those done you should get some kind of notification from ViperDNA to flash some kind of OTA (their versions there should be three) to update to the latest ViperDNA
here is the viperdna thread http://forum.xda-developers.com/showthread.php?t=2105745 for w/e you need it for
if you need anymore help just send me a PM ill be more than happy to help
Click to expand...
Click to collapse
Hi, I sent you PM but not sure if it went out. If it did not please send me one and I will reply.
Thanks.
You could follow the steps in my guide which can be found in my signature. Skip any steps you don't need.
Everything you need to know is there