Hey guys, my friend flashed elementalx kernel onto his stock 4.1.2
he says that after he did that, his internal memory would not show and sd card could not be mounted in CWM.
after 3 reboots the problem still persisted.
after he did a factory wipe in CWM, he says his phone refuses to boot into anything other than bootloader.
i have not owned a htc one and i have no idea what to do.
what i understand is that he needs to get an ruu?
however i cannot find an RUU for CID HTC_039 Australian unbranded....
help would be much appreciated, thanks guys!
EDIT: would it be possible for him to use supercid when his phone is in the current state?
spazzy1912 said:
Hey guys, my friend flashed elementalx kernel onto his stock 4.1.2
he says that after he did that, his internal memory would not show and sd card could not be mounted in CWM.
after 3 reboots the problem still persisted.
after he did a factory wipe in CWM, he says his phone refuses to boot into anything other than bootloader.
i have not owned a htc one and i have no idea what to do.
what i understand is that he needs to get an ruu?
however i cannot find an RUU for CID HTC_039 Australian unbranded....
help would be much appreciated, thanks guys!
EDIT: would it be possible for him to use supercid when his phone is in the current state?
Click to expand...
Click to collapse
Which version of Elemental did your friend flash?
If it was v2 or higher - that only works with 4.2.2 so that would explain why it wasn't booting.
First thing I'd be doing is flashing a kernel I know is 4.1.2 compatible via fastboot seeing they can't get the SD card to mount and just see if it boots up and then go from there.
Here's a link to a stock 4.1.2 kernel > https://www.dropbox.com/s/tcryfrq6cpp00bd/boot.img
Good luck
thejosh86 said:
Which version of Elemental did your friend flash?
If it was v2 or higher - that only works with 4.2.2 so that would explain why it wasn't booting.
First thing I'd be doing is flashing a kernel I know is 4.1.2 compatible via fastboot seeing they can't get the SD card to mount and just see if it boots up and then go from there.
Here's a link to a stock 4.1.2 kernel > https://www.dropbox.com/s/tcryfrq6cpp00bd/boot.img
Good luck[/QUOTE
hello, can you reupload this file in your dropbox?
Click to expand...
Click to collapse
rilxous said:
thejosh86 said:
Which version of Elemental did your friend flash?
If it was v2 or higher - that only works with 4.2.2 so that would explain why it wasn't booting.
First thing I'd be doing is flashing a kernel I know is 4.1.2 compatible via fastboot seeing they can't get the SD card to mount and just see if it boots up and then go from there.
Here's a link to a stock 4.1.2 kernel > https://www.dropbox.com/s/tcryfrq6cpp00bd/boot.img
Good luck[/QUOTE
hello, can you reupload this file in your dropbox?
Click to expand...
Click to collapse
I've re-upped it link here: http://db.tt/FJ5Hi6Lo
Click to expand...
Click to collapse
spazzy1912 said:
Hey guys, my friend flashed elementalx kernel onto his stock 4.1.2
he says that after he did that, his internal memory would not show and sd card could not be mounted in CWM.
after 3 reboots the problem still persisted.
after he did a factory wipe in CWM, he says his phone refuses to boot into anything other than bootloader.
i have not owned a htc one and i have no idea what to do.
what i understand is that he needs to get an ruu?
however i cannot find an RUU for CID HTC_039 Australian unbranded....
help would be much appreciated, thanks guys!
EDIT: would it be possible for him to use supercid when his phone is in the current state?
Click to expand...
Click to collapse
uhh from the looks of it he flash a kernel that was not meant for his rom and didnt boot. he then proceeded to freak out and you said he factory wipe'd in CWM. Now correct me if i'm wrong but factory wipe basically obliterates the OS from the phone all together. so i can see why he'd be having problems. Also even if the factory wipe doesnt kill everything just resets everything back to normal, it would do anything for his kernel since theres nothing to revert back to. i would pump either a stock rom or a custom like viper or ARHD and it should boot just fine.
syaoran68 said:
uhh from the looks of it he flash a kernel that was not meant for his rom and didnt boot. he then proceeded to freak out and you said he factory wipe'd in CWM. Now correct me if i'm wrong but factory wipe basically obliterates the OS from the phone all together. so i can see why he'd be having problems. Also even if the factory wipe doesnt kill everything just resets everything back to normal, it would do anything for his kernel since theres nothing to revert back to. i would pump either a stock rom or a custom like viper or ARHD and it should boot just fine.
Click to expand...
Click to collapse
except he can't get his internal sd to mount lol.
he's already sent it back and paid 80 dollars to fix it.
i advised him to take more caution next time haha
Related
Hi im from australia and i accidently wiped my phone and data but before that i had rooted the phone and well accidently deleted the OS cause my phone kept freezing on HTC anyway i need the RUU for my Htc but i keep getting error 140 and my phone is on RELOCKED so could anyone link a RUU for my phone Thank you
I believe that error means you are trying to run an old RUU.
You can download a new one from htcdev website I think.
Why don't you unlock your bootloader and just flash a custom rom?
oglocswagger said:
Hi im from australia and i accidently wiped my phone and data but before that i had rooted the phone and well accidently deleted the OS cause my phone kept freezing on HTC anyway i need the RUU for my Htc but i keep getting error 140 and my phone is on RELOCKED so could anyone link a RUU for my phone Thank you
Click to expand...
Click to collapse
eRadicant said:
I believe that error means you are trying to run an old RUU.
You can download a new one from htcdev website I think.
Why don't you unlock your bootloader and just flash a custom rom?
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What he said!!!!!!
oglocswagger said:
Hi im from australia and i accidently wiped my phone and data but before that i had rooted the phone and well accidently deleted the OS cause my phone kept freezing on HTC anyway i need the RUU for my Htc but i keep getting error 140 and my phone is on RELOCKED so could anyone link a RUU for my phone Thank you
Click to expand...
Click to collapse
Yep. I had the same issue. I wasn't able to install the original RUU.
Try Nik rom. It is very good, faster and fiable, better than the HTC RUU. You just need to unlock your phone through HTCdev, falsh the recovery and flash bootload, and then install the rom.
Take a look in this link (Nik rom): http://forum.xda-developers.com/showthread.php?t=2153205
rodrijob said:
Yep. I had the same issue. I wasn't able to install the original RUU.
Try Nik rom. It is very good, faster and fiable, better than the HTC RUU. You just need to unlock your phone through HTCdev, falsh the recovery and flash bootload, and then install the rom.
Take a look in this link (Nik rom): http://forum.xda-developers.com/showthread.php?t=2153205
Click to expand...
Click to collapse
i installed it then i rebooted it and it goes back to recoverymod any suggestions ? thnaks
oglocswagger said:
i installed it then i rebooted it and it goes back to recoverymod any suggestions ? thnaks
Click to expand...
Click to collapse
Err... can you provide us with more info, like what recovery u were using? Did the ROM SUCCESSFULLY flash or did it give some error???
072665995 said:
Err... can you provide us with more info, like what recovery u were using? Did the ROM SUCCESSFULLY flash or did it give some error???
Click to expand...
Click to collapse
im using recovery-clockwork-5.0.2.0-vivo And heres a photo of the phone being installed [/ATTACH][/ATTACH]
oglocswagger said:
i installed it then i rebooted it and it goes back to recoverymod any suggestions ? thnaks
Click to expand...
Click to collapse
Hi did you flash the boot image? You need to flash it. The boot.img file is inside the ZIP file. Do you know how to flash it? If you want I can post you a step by step to do it.
Regards,
Rodrijob.
rodrijob said:
Hi did you flash the boot image? You need to flash it. The boot.img file is inside the ZIP file. Do you know how to flash it? If you want I can post you a step by step to do it.
Regards,
Rodrijob.
Click to expand...
Click to collapse
Umm nope lol could you please? Thank you!
Thank you all it worked
flash rom
oglocswagger said:
Thank you all it worked
Click to expand...
Click to collapse
You' re welcome. Did you flash the rom Nik 3.0 (that one I put in dropbox?) Or the Nik 3.6?
I notice yesterday that the version 3.6 is draining power quickly.
The 3.0 version is better and works pretty good.
rodrijob said:
You' re welcome. Did you flash the rom Nik 3.0 (that one I put in dropbox?) Or the Nik 3.6?
I notice yesterday that the version 3.6 is draining power quickly.
The 3.0 version is better and works pretty good.
Click to expand...
Click to collapse
omg yes the battery died in like 30 mintues of using it thanks ! i'll download the dropbox one
Rom Nik 3.0
oglocswagger said:
omg yes the battery died in like 30 mintues of using it thanks ! i'll download the dropbox one
Click to expand...
Click to collapse
Ok, just download it and place it in the root of your sdcard device. Then with Rom manager (or in recovery mode with clockworkmod) choose option "Install Rom from SDcard", than chose the rom you placed in the SDcard and follow the instructions. I recomend a full wipe.
Finally flash the boot image with the boot.img file of this rom (I am attaching the file) and it's done. This rom works very well.
Well... I was using this http://forum.xda-developers.com/showthread.php?t=1818502 and it works.
Then used http://forum.xda-developers.com/showthread.php?t=1826378
to install the latest CM10.1 nightly file, then failed(some problem with the zip file?), the usb mounting wont work. Then when I reboot recovery I gone back into normal recovery. And I cant install anything nor mount my USB to the default recovery.
Now I'm stuck. Some help please?
KiD3991 said:
Well... I was using this http://forum.xda-developers.com/showthread.php?t=1818502 and it works.
Then used http://forum.xda-developers.com/showthread.php?t=1826378
to install the latest CM10.1 nightly file, then failed(some problem with the zip file?), the usb mounting wont work. Then when I reboot recovery I gone back into normal recovery. And I cant install anything nor mount my USB to the default recovery.
Now I'm stuck. Some help please?
Click to expand...
Click to collapse
You really haven't given much informaton to go on. Basics with any help request;-
What are you trying to achieve?
What version are you running?
What ROM were you on before?
Rooted?
Bootloader locked or unlocked?
What recovery have you installed?
EXACT error message - this is the single most important detail!!
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
SimonTS said:
You really haven't given much informaton to go on. Basics with any help request;-
What are you trying to achieve?
What version are you running?
What ROM were you on before?
Rooted?
Bootloader locked or unlocked?
What recovery have you installed?
EXACT error message - this is the single most important detail!!
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
Click to expand...
Click to collapse
My bad.
I want to install Cm10.1
running on stock rooted v10e
Rooted yes.
My device is SEA, not sure if I unlocked bootloader...(might be the problem)
The recovery i stated on my question.
I now can only hope lg support tool can help me out.
Because I might forgot bootloader and my device is already wiped out clean(so i cant even return to stock because the whole device is empty).
edit:
Figured out how to enter download mode... haha
Will keep Continue my effort!
I've gone through hell Unlocking Sensation XE, 4X wont beat me!
SimonTS said:
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
Click to expand...
Click to collapse
KiD3991 said:
My bad.
I want to install Cm10.1
running on stock rooted v10e
Rooted yes.
My device is SEA, not sure if I unlocked bootloader...(might be the problem)
The recovery i stated on my question.
I now can only hope lg support tool can help me out.
Because I might forgot bootloader and my device is already wiped out clean(so i cant even return to stock because the whole device is empty).
Click to expand...
Click to collapse
Highlighted in red for a very good reason. You'll need to reflash your stock v10e first, yet again there are guides on how to do this. Once you have the phone back up and running on v10e then read carefully and make sure you understand all the steps before trying again
SimonTS said:
Highlighted in red for a very good reason. You'll need to reflash your stock v10e first, yet again there are guides on how to do this. Once you have the phone back up and running on v10e then read carefully and make sure you understand all the steps before trying again
Click to expand...
Click to collapse
Via LG mobile supporter I'm installing 20a or something. Then I will redo it. Thanks for your effort in helping. Hahaha. :good:
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
So as Im sure everyone here knows, new firmware updates have rolled out...
For some odd reason, though, I cannot enjoy them. I came from iHackers 4.1 ROM and attempted to update to the Criskelo .118 ROM. All went okay, except the wifi kept saying "turning on."
Then, amongst other problems, I tried to go to just a stock .108 by downgrading... Still, "turning on wifi."
I'm not sure if there is any relevance, but I had Phil/TWRP dual recovery installed. The Criskelo ROM instructions said I had to have CWM if on a locked bootloader, but I am unlocked. Perhaps I misunderstood and it has to be CWM for both? I did notice that despite many efforts to get my dual recovery back, I was stuck with CWM (I did get dual back though eventually).
So could the problem have been with the conflicting recoveries? And perhaps it didn't install the kernel or ROM properly?
Thanks in advance for any replies.
ShadowTech13 said:
So as Im sure everyone here knows, new firmware updates have rolled out...
For some odd reason, though, I cannot enjoy them. I came from iHackers 4.1 ROM and attempted to update to the Criskelo .118 ROM. All went okay, except the wifi kept saying "turning on."
Then, amongst other problems, I tried to go to just a stock .108 by downgrading... Still, "turning on wifi."
I'm not sure if there is any relevance, but I had Phil/TWRP dual recovery installed. The Criskelo ROM instructions said I had to have CWM if on a locked bootloader, but I am unlocked. Perhaps I misunderstood and it has to be CWM for both? I did notice that despite many efforts to get my dual recovery back, I was stuck with CWM (I did get dual back though eventually).
So could the problem have been with the conflicting recoveries? And perhaps it didn't install the kernel or ROM properly?
Thanks in advance for any replies.
Click to expand...
Click to collapse
The recovery has nothing to do with the functionality of wifi or anything in the ROM for that matter. Did you do a full wipe before installing the Criskelo ROM?
Other than that, make sure you're using the right baseband for .118. (if it even has changed)
If that all fails, make a backup of everything on your phone (also your internal 'sdcard') and do a full re-install of the official .118 ROM using flashtool.
B1nny said:
The recovery has nothing to do with the functionality of wifi or anything in the ROM for that matter. Did you do a full wipe before installing the Criskelo ROM?
Other than that, make sure you're using the right baseband for .118. (if it even has changed)
If that all fails, make a backup of everything on your phone (also your internal 'sdcard') and do a full re-install of the official .118 ROM using flashtool.
Click to expand...
Click to collapse
Yup, I made sure to do a full wipe before I installed it. I did do a backup of my internal and external SD cards just in case something managed to go wrong somehow... Im pretty sure I used the correct baseband, but I will double-check and also try your suggested method using flashtool. I'll let you know how it goes, and thanks for the response!
ShadowTech13 said:
Yup, I made sure to do a full wipe before I installed it. I did do a backup of my internal and external SD cards just in case something managed to go wrong somehow... Im pretty sure I used the correct baseband, but I will double-check and also try your suggested method using flashtool. I'll let you know how it goes, and thanks for the response!
Click to expand...
Click to collapse
Still nothing... I did more wipes/factory resets with this phone than I have ever done. lol
ShadowTech13 said:
Still nothing... I did more wipes/factory resets with this phone than I have ever done. lol
Click to expand...
Click to collapse
You had better bring your phone to the service if you don't want WiFi module dies.
Forgive me for asking, but what would be wrong with the module? Wouldn't it not work at all of that were the case? It's working right now...
Sent from my C6903 using xda premium
ShadowTech13 said:
Forgive me for asking, but what would be wrong with the module? Wouldn't it not work at all of that were the case? It's working right now...
Sent from my C6903 using xda premium
Click to expand...
Click to collapse
Alright so it's definitely not the module. I just flashed PAC's 4.4.4 Beta ROM. The wifi successfully turns on and I am able to view networks, as well as connect to them. So why then, can I not seem to get wifi working on stock based 4.4.4 or .108/.118 ROMs? Any ideas?
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?