Related
Hi Guys,
Yesterday I tried to flash CM7 latest nightly build on my Incredible S, but got stuck on boot animation.
I was on NIK project X v4, I assume that that zip is missing something that's why I didn't boot.
Can anyone help me with the same??
mohitgalaxy3 said:
Hi Guys,
Yesterday I tried to flash CM7 latest nightly build on my Incredible S, but got stuck on boot animation.
I was on NIK project X v4, I assume that that zip is missing something that's why I didn't boot.
Can anyone help me with the same??
Click to expand...
Click to collapse
Have not had that issue
Nonverbose said:
Have not had that issue
Click to expand...
Click to collapse
I have flashed CM7 lastest nightly and I didn't boot it up and at the same time I have flashed the gbgapps zip as well.
Can that be a problem or not ??
Figured it out my self, flashing the google app without booting cause the boot loop.
Thread closed
Nonverbose said:
Have not had that issue
Click to expand...
Click to collapse
Ok one more thing, you are using CM7, so can you guide me to some MODS, themes some good stuff?
mohitgalaxy3 said:
Ok one more thing, you are using CM7, so can you guide me to some MODS, themes some good stuff?
Click to expand...
Click to collapse
I use ics theme https://play.google.com/store/apps/details?id=com.sonny.theme.ics
Also GO launcher
Nonverbose said:
I use ics theme https://play.google.com/store/apps/details?id=com.sonny.theme.ics
Also GO launcher
Click to expand...
Click to collapse
Wifi is not working for me, please help what should I do, should I replace wpa_supplicant file.
Go backup must have restored access points that could be a problem??
If yes can you please upload your wpa_supplicant file, you will find it in data\misc\wifi..
mohitgalaxy3 said:
Wifi is not working for me, please help what should I do, should I replace wpa_supplicant file.
Go backup must have restored access points that could be a problem??
If yes can you please upload your wpa_supplicant file, you will find it in data\misc\wifi..
Click to expand...
Click to collapse
Sounds like you're s-on and either didn't flash your boot.img in fastboot or, more likely didn't push your wifi module (/system/lib/modules/bcm4329.ko)
Nonverbose said:
Sounds like you're s-on and either didn't flash your boot.img in fastboot or, more likely didn't push your wifi module (/system/lib/modules/bcm4329.ko)
Click to expand...
Click to collapse
I have S-OFF, black rose.
No I haven't flash boot.img in fastboot.
Tell me what exactly i need to do make it working please.
Should I flash/push the wifi module from any other sense 4 rom, will that do the trick??
mohitgalaxy3 said:
I have S-OFF, black rose.
No I haven't flash boot.img in fastboot.
Tell me what exactly i need to do make it working please.
Should I flash/push the wifi module from any other sense 4 rom, will that do the trick??
Click to expand...
Click to collapse
If you're s-off you shouldn't be having that issue. Did you clear cache and dalvik when you flashed cm7?
Edit: what version radio are you on?
Nonverbose said:
If you're s-off you shouldn't be having that issue. Did you clear cache and dalvik when you flashed cm7?
Edit: what version radio are you on?
Click to expand...
Click to collapse
I have flashed the ARDH wipe script bfr flashing CM7 and I am on 11_M. the ics one radio.
mohitgalaxy3 said:
I have flashed the ARDH wipe script bfr flashing CM7 and I am on 11_M. the ics one radio.
Click to expand...
Click to collapse
Try rolling back to revolutionary hboot and a GB radio (the one in my sig is good) and see if that makes a difference. Remember to clear the cache after you have flashed them.
This might help getting back to revolutionary http://forum.xda-developers.com/showpost.php?p=26909973&postcount=13
Nonverbose said:
Try rolling back to revolutionary hboot and a GB radio (the one in my sig is good) and see if that makes a difference. Remember to clear the cache after you have flashed them.
This might help getting back to revolutionary http://forum.xda-developers.com/showpost.php?p=26909973&postcount=13
Click to expand...
Click to collapse
really for just wifi, I have to do that much???
mohitgalaxy3 said:
really for just wifi, I have to do that much???
Click to expand...
Click to collapse
2 things? No you don't have to do it, and as I don't have the issue I cant even say that it will work. There's always other options...
So I'm rooted with an unlocked boot loader and a custom ROM installed but when I downloaded some apps it said it can't access root so I checked root checker and it said
My phone isn't rooted even tho I have supersu and a custom ROM on it
Sent from my HTC One using xda app-developers app
Remove the super su and install superSU.zip from recovery.
Sent from my One V using xda app-developers app
Are you sure nothing will happen? Can I just get it from Google play?
Sent from my HTC One using xda app-developers app
Zakdroid said:
Are you sure nothing will happen? Can I just get it from Google play?
Click to expand...
Click to collapse
If you just moved up to 4.3, root implementation has changed, so you need to flash SU from recovery the first time.
iElvis said:
If you just moved up to 4.3, root implementation has changed, so you need to flash SU from recovery the first time.
Click to expand...
Click to collapse
I'm having similar issues with my HTC One, I unlocked and rooted and installed Maximus HD 13 rom - that's when I started getting problems with SuperSu - first the update issue, now it says no binaries.
I tried installing it from recovery, I even tried CWM, then reflashed TWRP. Still nothing, same error. No binaries. Driving me bloody crazy.
ieldra said:
I'm having similar issues with my HTC One, I unlocked and rooted and installed Maximus HD 13 rom - that's when I started getting problems with SuperSu - first the update issue, now it says no binaries.
I tried installing it from recovery, I even tried CWM, then reflashed TWRP. Still nothing, same error. No binaries. Driving me bloody crazy.
Click to expand...
Click to collapse
Do a full wipe and start over, flashing rom and then supersu together.
iElvis said:
Do a full wipe and start over, flashing rom and then supersu together.
Click to expand...
Click to collapse
Yeah it looks like that's what I'm gonna have to do, should I wipe boot as well ? Maximus HD installs the stock kernel as well, wondering if it also installs hboot. Afaik /boot is split into boot and kernel. Wouldn't wanna wipe the entire device, install the ROM, reboot and find myself with no hboot !
ieldra said:
Yeah it looks like that's what I'm gonna have to do, should I wipe boot as well ? Maximus HD installs the stock kernel as well, wondering if it also installs hboot. Afaik /boot is split into boot and kernel. Wouldn't wanna wipe the entire device, install the ROM, reboot and find myself with no hboot !
Click to expand...
Click to collapse
hboot and boot.img are two different things. No rom will touch hboot. Only way to change your hboot is via RUU or OTA, or to s-off and flash in RUU mode.
All roms include a kernel, usually the stock kernel. That will overwrite whatever you had there before but you should still wipe /data.
iElvis said:
hboot and boot.img are two different things. No rom will touch hboot. Only way to change your hboot is via RUU or OTA, or to s-off and flash in RUU mode.
All roms include a kernel, usually the stock kernel. That will overwrite whatever you had there before but you should still wipe /data.
Click to expand...
Click to collapse
Thanks for your replies man! Really helpful ! I installed Maximus HD again, formatted everything I possibly could... it comes preloaded with supersu. Still says no binaries... What the hell should I do
ieldra said:
Thanks for your replies man! Really helpful ! I installed Maximus HD again, formatted everything I possibly could... it comes preloaded with supersu. Still says no binaries... What the hell should I do
Click to expand...
Click to collapse
Did you flash the supersu zip separately in recovery? I've had to do that every time I installed a 4.3 rom.
iElvis said:
Did you flash the supersu zip separately in recovery? I've had to do that every time I installed a 4.3 rom.
Click to expand...
Click to collapse
Alright, basically what I did today is I wiped every single partition I had access to, so everything but boot and recovery. installed maximus HD 13, installed faux kernel, installed faux kernel camera fix. Maximus installs supersu by default, I opened it up and I got the stupid no binary error. So I went back to recovery and attempted SuperSu 1.65 from zip, still the same problem. Please note that I did all this BECAUSE of my issues with root, funny how after nuking the whole phone I still have the same problem. I've google extensively, and pretty much the only advice I've found involves either rooting from recovery or changing something in SuperSu settings, which I CAN'T ACCESS because the app closes right after the error prompt pops up.
I'm a few desperate attempts short of attempting an exorcism...
ieldra said:
Alright, basically what I did today is I wiped every single partition I had access to, so everything but boot and recovery. installed maximus HD 13, installed faux kernel, installed faux kernel camera fix. Maximus installs supersu by default, I opened it up and I got the stupid no binary error. So I went back to recovery and attempted SuperSu 1.65 from zip, still the same problem. Please note that I did all this BECAUSE of my issues with root, funny how after nuking the whole phone I still have the same problem. I've google extensively, and pretty much the only advice I've found involves either rooting from recovery or changing something in SuperSu settings, which I CAN'T ACCESS because the app closes right after the error prompt pops up.
I'm a few desperate attempts short of attempting an exorcism...
Click to expand...
Click to collapse
I have not used Maximus, so maybe you should move over to that thread. I had the same issues with ARHD, but flashing SuperSU in recovery after the rom flash took care of it. In all likelihood, you're not the only Maximus user to deal with this, so the answer may be over there.
iElvis said:
I have not used Maximus, so maybe you should move over to that thread. I had the same issues with ARHD, but flashing SuperSU in recovery after the rom flash took care of it. In all likelihood, you're not the only Maximus user to deal with this, so the answer may be over there.
Click to expand...
Click to collapse
I don't know what changed, but i changed TWRP for CWM, installed the rom, then immediately installed supersu and it worked. I love you. I want you to have my babies.
ieldra said:
I don't know what changed, but i changed TWRP for CWM, installed the rom, then immediately installed supersu and it worked. I love you. I want you to have my babies.
Click to expand...
Click to collapse
I'm lacking the uterus for that, but feel free to hit the Thanks button.
iElvis said:
I'm lacking the uterus for that, but feel free to hit the Thanks button.
Click to expand...
Click to collapse
Alright, so SuperSu WORKED. Until I flashed the faux123 kernel, at which point it stopped working again. Same issue, no binaries. So I reformatted the whole phone, installed Rom, then faux123 kernel, then SuperSu. Same issue. No binaries. I can only conclude that installing the kernel causes the issue. Hope this helps someone who has the same problem. Gonna stick to stock kernel for now
ieldra said:
Alright, so SuperSu WORKED. Until I flashed the faux123 kernel, at which point it stopped working again. Same issue, no binaries. So I reformatted the whole phone, installed Rom, then faux123 kernel, then SuperSu. Same issue. No binaries. I can only conclude that installing the kernel causes the issue. Hope this helps someone who has the same problem. Gonna stick to stock kernel for now
Click to expand...
Click to collapse
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
iElvis said:
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
Click to expand...
Click to collapse
Pretty sure I am, "m7-faux123-Sense43-007m.zip" and "faux123-jb43-sense-camera-fix.zip". Did you have to root again after installing ElemntalX ? Just finished reinstalling ROM for fourth time today, going to check SuperSu works, go back to recovery, make a nandroid backup and perhaps try ElementalX Is there a kernel control app for it ?
ieldra said:
Pretty sure I am, "m7-faux123-Sense43-007m.zip" and "faux123-jb43-sense-camera-fix.zip". Did you have to root again after installing ElemntalX ? Just finished reinstalling ROM for fourth time today, going to check SuperSu works, go back to recovery, make a nandroid backup and perhaps try ElementalX Is there a kernel control app for it ?
Click to expand...
Click to collapse
I only had to flash SuperSU once. I use TricksterMod.
I've experienced this problem on two different ROMs (different variations of the same problem, actually). In both cases, flashing the same SuperSU .zip fixed it. Link here.
iElvis said:
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
Click to expand...
Click to collapse
Dude,
Thank you so much for you post, been wondering is this problem bothering me since i saw you post so i tested it out, end up the rom was fine till i flash the faux123 kernal and camera fix, and binary not install issue come out again.
for people who having same problem, this might be the issue
Cheer
Hi guys.
I'm attempting to flash the ElementalX-m7-5.2 on my phone which is currently running ARHD 21.0 Sense 5. My base is 3.17.xxx therefore I think everything should be fine. I just wondering what my Kernel version should read after I finish flashing it. From what I can see, it kernel hasn't been successfully flashed. Are there any prerequisites that I have to fulfill before flashing a custom rom?
Cheers.
s3330987 said:
Hi guys.
I'm attempting to flash the ElementalX-m7-5.2 on my phone which is currently running ARHD 21.0 Sense 5. My base is 3.17.xxx therefore I think everything should be fine. I just wondering what my Kernel version should read after I finish flashing it. From what I can see, it kernel hasn't been successfully flashed. Are there any prerequisites that I have to fulfill before flashing a custom rom?
Cheers.
Click to expand...
Click to collapse
Why not?
What's the error? You get it in recovery when you flashed?
Or are you talking about what you can see into settings?
Guich said:
Why not?
What's the error? You get it in recovery when you flashed?
Or are you talking about what you can see into settings?
Click to expand...
Click to collapse
Well it's beyond me really. Well, I have to get into recovery to flash it, so yeah.
Flashing seems to work as there is no error. I restart it twice, just as it requires. I go into my system info to check my kernel version, but nothing seems to have changed. Note, I've attempted to flash this twice now. Maybe, I'll just have to keep trying.
s3330987 said:
Well it's beyond me really. Well, I have to get into recovery to flash it, so yeah.
Flashing seems to work as there is no error. I restart it twice, just as it requires. I go into my system info to check my kernel version, but nothing seems to have changed. Note, I've attempted to flash this twice now. Maybe, I'll just have to keep trying.
Click to expand...
Click to collapse
ElementalX is "[email protected]" under kernel. If it shows that, then you're good.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
ElementalX is "[email protected]" under kernel. If it shows that, then you're good.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Ahhhhh. Super! I guess it worked then. Brilliant. :good:
Hi everyone,
Recently I tried to follow a post from xda dev on putting a new kernel on my HTC Desire C.
Although I followed all the steps I am now unable to get past the boot screen wit the htc logo.
I have tried a number of solutions to make it work but nothing so far, backup recovery failed, changing to another kernel failed.
I think that at this point it might be bricked, and all that I can see is the logo and a disclaimer message.
Does anyone has any idea if I could fix it, and what do I need to do?
Kind regards,
Florin
Edit: thanks to aashay960 for telling me how to fix this.
The solution was to reinstall kernel and rom (since I made a mess of it initially)
Current config : CyanogenMod 10 + N.O.P.E Kernel 875Mhz
sir_florin90 said:
Hi everyone,
Recently I tried to follow a post from xda dev on putting a new kernel on my HTC Desire C.
Although I followed all the steps I am now unable to get past the boot screen wit the htc logo.
I have tried a number of solutions to make it work but nothing so far, backup recovery failed, changing to another kernel failed.
I think that at this point it might be bricked, and all that I can see is the logo and a disclaimer message.
Does anyone has any idea if I could fix it, and what do I need to do?
Kind regards,
Florin
Click to expand...
Click to collapse
Its not bricked. Tell me which kernel you are trying, with which rom? And try flashing a lower frequency kernel.
aashay960 said:
Its not bricked. Tell me which kernel you are trying, with which rom? And try flashing a lower frequency kernel.
Click to expand...
Click to collapse
I tried the Prometheus Kernel for sense linked in your signature with the stock. I got to the HTC logo screen and it got stuck there. It might be that the method I used was wrong.
Would it be possible to use the ones you do? Cyanogem mode and the N.O.P.E Kernel?
Can I install them only with recovery? And is there and "xda approved" method of installing kernels and custom roms?
Thanks,
Florin
Flash a lower frequency Prometheus Sense Kernel from fastboot.
You cannot use nope for sense roms. Nope is for Jellybean roms only.
As of now we have two ways to flash a kernel on this device. One is fastboot, which I personally use. Second is the auto Boot.img flasher that you will find if you search..
For now, tell me what frequency you tried. And try a lower one.
aashay960 said:
Flash a lower frequency Prometheus Sense Kernel from fastboot.
You cannot use nope for sense roms. Nope is for Jellybean roms only.
As of now we have two ways to flash a kernel on this device. One is fastboot, which I personally use. Second is the auto Boot.img flasher that you will find if you search..
For now, tell me what frequency you tried. And try a lower one.
Click to expand...
Click to collapse
Hi, I forgot to mention in the previous one that I initially used the 816 one, and then switched to the lower one 767.
Is it worth it to try a "clean install" as in a new configuration with a new kernel and rom?
No a wipe is not necessary.
Just make sure you do
Fastboot erase cache
Fastboot flash boot boot.img
Try an even lower one.
Now that your bootloader is unlocked. Why not try a custom rom?
aashay960 said:
No a wipe is not necessary.
Just make sure you do
Fastboot erase cache
Fastboot flash boot boot.img
Try an even lower one.
Now that your bootloader is unlocked. Why not try a custom rom?
Click to expand...
Click to collapse
What rom do you have in mind? I was thinking about cyanogen
sir_florin90 said:
What rom do you have in mind? I was thinking about cyanogen
Click to expand...
Click to collapse
Yeah that seems to be the most popular rom around. Been using it for a long time..
You can look at other options too. You can't really go wrong with any...
Just make sure to flash nope kernel with a jb rom.
aashay960 said:
Yeah that seems to be the most popular rom around. Been using it for a long time..
You can look at other options too. You can't really go wrong with any...
Just make sure to flash nope kernel with a jb rom.
Click to expand...
Click to collapse
I have noticed: CyanogenMod 10 + N.O.P.E Kernel 875Mhz.
Is this for you desire C?
Yes that is..
aashay960 said:
Yes that is..
Click to expand...
Click to collapse
Thanks man, the phone is back alive. I was feeling so bad when I realised it might be bricked. Thanks again :d
Pls delete.
wilberfish said:
Pls delete.
Click to expand...
Click to collapse
Why would you ask a thread to be deleted without the consent of the OP
Sorry. My bad, I was referring to my post.
I seem to be having connection problems with the xda app resulting in posts when I thank people and only getting notification of successful posts when I am reading another thread!
Sorry for the confusion I caused.
wilberfish said:
Sorry. My bad, I was referring to my post.
I seem to be having connection problems with the xda app resulting in posts when I thank people and only getting notification of successful posts when I am reading another thread!
Sorry for the confusion I caused.
Click to expand...
Click to collapse
Oh its ok, I didnt get what you said. Some tips if you want someone to disregard your post just put a "Deleted." or "[Deleted]" tag.
OK. Thanks.
Hello,
I rooted my phone and then i istalled a new ROM. The ROM had some problems so i removed it trough recovery mode ---> clean to istall a new ROM
After that i accidentally type on "factory reset" and now i can't use my phone (it only shows me the logo screen)
i tried to istall other ROM but they didn't work ( they caused non-stop rebooting in my device)
HTC desire 510
android version 4.4.3
Can someone help me please?
Have you tried to install the stock ROM on the device
hilton24 said:
Have you tried to install the stock ROM on the device
Click to expand...
Click to collapse
Thank you for answering,
Yes i tried but it doesn't work maybe i download a wrong zip file do you know where to download an other stock ROM file please?
NatashaJbl said:
Thank you for answering,
Yes i tried but it doesn't work maybe i download a wrong zip file do you know where to download an other stock ROM file please?
Click to expand...
Click to collapse
What carrier are you using? A lot of roms that are stock have to be a specific carrier... Why don't you try using CM11? Or is your phone 64 bit? Where are you from?
MrMike2182 said:
What carrier are you using? A lot of roms that are stock have to be a specific carrier... Why don't you try using CM11? Or is your phone 64 bit? Where are you from?
Click to expand...
Click to collapse
Im from Italy
Carrier: Vodafone
and my phone is 64 bit
NatashaJbl said:
Im from Italy
Carrier: Vodafone
and my phone is 64 bit
Click to expand...
Click to collapse
You should not be trying to put any of these roms on your phone since it's 64 bit and all of these roms on here are 32 bit... I think there is a stock rom somewhere on here that you can download to fix the phone but you need to make sure you have philz touch recovery installed first.
MrMike2182 said:
You should not be trying to put any of these roms on your phone since it's 64 bit and all of these roms on here are 32 bit... I think there is a stock rom somewhere on here that you can download to fix the phone but you need to make sure you have philz touch recovery installed first.
Click to expand...
Click to collapse
Ok thank u, yes i have the philz touch recovery n im looking for the stock ROM but i haven't found anything yet
NatashaJbl said:
Ok thank u, yes i have the philz touch recovery n im looking for the stock ROM but i haven't found anything yet
Click to expand...
Click to collapse
Here use this one Vodafone rom
Thanks for the file, It worked only for 1 hour then it crushed and reboot continuously. battery doesn't charge and the phone shows me a message telling me that i have a modified system so i can't update it
NatashaJbl said:
Thanks for the file, It worked only for 1 hour then it crushed and reboot continuously. battery doesn't charge and the phone shows me a message telling me that i have a modified system so i can't update it
Click to expand...
Click to collapse
All phones that have a rom or kernel that's not 100% stock is going to say modified... Go into recovery clear your caches which are the dalvic and cache and try to charge your phone while it's powered off... Don't try to do updates because you cannot ever get it to work since you installed philz touch recovery... That rom is the ONLY one available for your Vodafone there is no stock RUU to fix it I can't find one and neither could you so I would try your best make the rom I gave you work.
MrMike2182 said:
All phones that have a rom or kernel that's not 100% stock is going to say modified... Go into recovery clear your caches which are the dalvic and cache and try to charge your phone while it's powered off... Don't try to do updates because you cannot ever get it to work since you installed philz touch recovery... That rom is the ONLY one available for your Vodafone there is no stock RUU to fix it I can't find one and neither could you so I would try your best make the rom I gave you work.
Click to expand...
Click to collapse
I will do my best thank you very much
Is it working now?