Hello, I have a dna rooted, I tried to install as described, two types of kernel, but do not make me turn on wifi ...
and when I had the stock kernel everything was fine, what determines this?
Did you flash the modules?? If you did try to re-fastboot the kernel again. I had the same problem and fastbooted the boot.img again fixed it
Sounds like you are not flashing the modules.
Open up the zip for a Rom, inside there should be 2 things. A boot.img to flash in fastboot or with flash img gui. And another zip to flash in recovery.
Sent from my HTC6435LVW using xda app-developers app
in the zip for the kernels, you will find a boot.img and a modules.zip. flash the modules AFTER flash the kernel using the flash image gui or fastboot.
in simpler words,
1. flash boot.img using the flash image gui app in the play store (search it) OR use fastboot/adb. either works.
2. in your RECOVERY flash the modules.zip. problem solved
many thanks ,
first time i've don't flash with image.boot
after flash whit image.boot , it's all ok
some kernel not require this flash mode ..
Stryker1297 said:
in the zip for the kernels, you will find a boot.img and a modules.zip. flash the modules AFTER flash the kernel using the flash image gui or fastboot.
in simpler words,
1. flash boot.img using the flash image gui app in the play store (search it) OR use fastboot/adb. either works.
2. in your RECOVERY flash the modules.zip. problem solved
Click to expand...
Click to collapse
I'm have an issue with the wifi not turning on (it stays grey saying turning on but never does) all other radios work, just not wifi. I have flashed the boot.img several times to make sure. in regards to the modules.zip, I see a folder but it is not a .zip are we supposed to zip this then flash it? I cant get wifi to run on any rom except for stock. I am s-off if that helps solve anything.
ApexPredation said:
I'm have an issue with the wifi not turning on (it stays grey saying turning on but never does) all other radios work, just not wifi. I have flashed the boot.img several times to make sure. in regards to the modules.zip, I see a folder but it is not a .zip are we supposed to zip this then flash it? I cant get wifi to run on any rom except for stock. I am s-off if that helps solve anything.
Click to expand...
Click to collapse
Do NOT hijack an old thread, PLEASE start a new thread!!!!
RLGL said:
Do NOT hijack an old thread, PLEASE start a new thread!!!!
Click to expand...
Click to collapse
Just figured since I'm having the same problem there was no need to make duplicate posts. Thanks for your help.
Related
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?
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
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
Hi, first of all, my English is bad and i'm a noob at installing custom roms
My HOX+ is rooted and i have the TWRP Recovery installed.
So, i downloaded the newest CM11 Nightly for my device (enrc2b) from the Cyanogenmod site.
When i try to flash it with TWRP it says:
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E:Error executing updater binary in zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
I also downloaded a Snapshot version of CM11
It says:
Skipping MD5 check: no MD5 file found
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
So finally i downloaded the CM10.2.1 Version
I wiped all cache and data and did a factory reset.
After flashing the .zip and rebooting the phone, but i got stuck in a boot loop (i think) because i waited like 20 minutes but the boot animation didn't change (blue guy with the arrow). Did i do something wrong
I just restored my phone to the backup i made (stock rom)
If you need any information about my phone or something just say it.
I also heard about using CWM instead of TWRP but i don't know how to change it.
PLZ HELP :crying:
CWM recovery
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
[email protected] said:
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
Click to expand...
Click to collapse
Thx, I will try it
Sent from my HTC One X+ using XDA Free mobile app
I'm working with a Mac so it might take a while before i understand everything but i'll let you know if it worked.
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Anthony26 said:
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
did you flash the boot.img in fastboot before installing the rom?
reaper90 said:
did you flash the boot.img in fastboot before installing the rom?
Click to expand...
Click to collapse
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Anthony26 said:
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Click to expand...
Click to collapse
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Thx,
I forgot to unzip the file :silly:
I'll try it and let you know of it worked
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Stock boot image
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Anthony26 said:
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Click to expand...
Click to collapse
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
[email protected] said:
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Click to expand...
Click to collapse
reaper90 said:
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
Click to expand...
Click to collapse
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Anthony26 said:
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Click to expand...
Click to collapse
no, oxp_kk is just for 4.4 (kitkat) AOSP like roms. there's another non- kk version which works with 4.2.2/sense5 roms, but i don't know about stock roms. There's also a fallback kernel version which should work with all stock and custom 4.2.2/Sense 5 roms.
https://www.dropbox.com/s/1c582fybb1phvlv/recovery.tar.md5.zip?dl=0
DISCLAIMER: FOLLOW INFO OR YOU WILL 86(RUIN) YOUR PHONE.
Download the file
Extract the file and flash via ODIN in BL Section
This should fix any bootloop issue.
Until they figure out a fix, this will take care of that force boot into TWRP
so you kinda have to flash between the two so you can boot it or to flash proper files.
DEVS!!!! Please request MODs to sticky this until this issue is fixed.
I tried this and it didnt change the boot loop in my phone. I have tried flashing everything and no luck.
It helped me only bc after updating... phone kept going back to recovery...
SykkNyzz said:
https://www.dropbox.com/s/1c582fybb1phvlv/recovery.tar.md5.zip?dl=0
DISCLAIMER: FOLLOW INFO OR YOU WILL 86(RUIN) YOUR PHONE.
Download the file
Extract the file and flash via ODIN in BL Section
This should fix any bootloop issue.
Until they figure out a fix, this will take care of that force boot into TWRP
so you kinda have to flash between the two so you can boot it or to flash proper files.
DEVS!!!! Please request MODs to sticky this until this issue is fixed.
Click to expand...
Click to collapse
My Phone model is SM-J700H/DS.
the phone is not booting after flash SuperSU.
i do get in TWRP and Downloading Mode.
will this solution will fix it ?
thanks.
Update:
Problem Solved,
i had falshed the wront SuperSU version.
falshed again v2.68 and that solve the problem.
i took it from here:
http://rootmygalaxy.net/flash-supers...ndroid-device/
SykkNyzz said:
https://www.dropbox.com/s/1c582fybb1phvlv/recovery.tar.md5.zip?dl=0
DISCLAIMER: FOLLOW INFO OR YOU WILL 86(RUIN) YOUR PHONE.
Download the file
Extract the file and flash via ODIN in BL Section
This should fix any bootloop issue.
Until they figure out a fix, this will take care of that force boot into TWRP
so you kinda have to flash between the two so you can boot it or to flash proper files.
DEVS!!!! Please request MODs to sticky this until this issue is fixed.
Click to expand...
Click to collapse
An alternative method is to make sure you have an installed rom an with supersu in twrp flash a stock boot.img to the recovery partition and youll boot up no problems
Sent from my SM-J700P using Tapatalk
I found the issue is also from when people use that *reboot to recovery* function.
SykkNyzz said:
I found the issue is also from when people use that *reboot to recovery* function.
Click to expand...
Click to collapse
Thats what i used through adb
Sent from my SM-J700P using Tapatalk