I got my htc one back in January and immediately rooted it with s-off and installed twrp, since then I have been using this rom and it has worked just fine. But recently I got quite sick of sense and when I tried in stall this rom the phone would not work, I tried cm11 after but it would not flash at all giving me an error every time. I read that I need to update my firmware but Im not really sure what that means, or how to tell what firmware I am on(I thought firmware was the same thing as a rom?)
sorry if this is a stupid question, Im not really that good with technology :L
thewaffleninja said:
I got my htc one back in January and immediately rooted it with s-off and installed twrp, since then I have been using this rom and it has worked just fine. But recently I got quite sick of sense and when I tried in stall this rom the phone would not work, I tried cm11 after but it would not flash at all giving me an error every time. I read that I need to update my firmware but Im not really sure what that means, or how to tell what firmware I am on(I thought firmware was the same thing as a rom?)
sorry if this is a stupid question, Im not really that good with technology :L
Click to expand...
Click to collapse
There were some recent changes to CM11 that require a new recovery. Have you tried the latest version of TWRP?
Where you using the CM11 nightlies or M releases?
durgis said:
There were some recent changes to CM11 that require a new recovery. Have you tried the latest version of TWRP?
Where you using the CM11 nightlies or M releases?
Click to expand...
Click to collapse
I used the most recent nightly at the time, this was on Wednesday. Im on twrp 2.6.3.3, could you or someone link me how to update twrp? goomanager does not work for some reason and those are the only tutorials i can find.
thewaffleninja said:
I used the most recent nightly at the time, this was on Wednesday. Im on twrp 2.6.3.3, could you or someone link me how to update twrp? goomanager does not work for some reason and those are the only tutorials i can find.
Click to expand...
Click to collapse
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
durgis said:
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
Click to expand...
Click to collapse
thank you
durgis said:
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
Click to expand...
Click to collapse
I just updated and it still didn't work :C
thewaffleninja said:
I just updated and it still didn't work :C
Click to expand...
Click to collapse
Where there any errors while installing the rom in TWRP? You might try one of the CyanogenMod snapshots instead of a nightly, they're a bit more stable and well tested. Also, make sure that you backup and wipe when switching between different roms.
http://download.cyanogenmod.com/?device=m7vzw&type=snapshot
Related
Here is my dilemma, I recently unlocked and rooted my HTC One M7 for Verizon. I may not have performed a backup but I am oblivious to what the problem may be. I am a newb to rooting and unlocking so please spare me any negative feedback. S-off was successful using firewater. Phone is unlocked in bootloader. Phone was rooted through TWRP v2.7.0.0 and SU. After root was successful I did a factory reset then flashed CM11 with TWRP. CM11 installation was successful except for one problem. My mobile network is not available and a message appears on the screen(You need to refer to the SIM card instruction that came with your phone.) The CM11 file that I installed is: cm-11-20140407-NIGHTLY-m7.zip and after reading that the "Nightly" roms are not the most stable, I then flashed this one: cm-11-20140405-SNAPSHOT-M5-m7.zip. Here is what the Installation looked like in Recovery:
Updating partition details...
Full SELinux support is present.
Formatting Cache using make_ext4fs function.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing ' /sdcard/Download/cm-11-20140405-SN
APSHOT-M5-m7.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details..
Successful.
Following the successful flash, I then installed gapps-kk-20131208. Please be detailed in how I can fix this issue. Thanks so much in advance.
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
KK firmware
cmlusco said:
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
Click to expand...
Click to collapse
I don't understand. What is KK firmware? This may seem like a stupid question but I really don't know.
kk
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Zacb01 said:
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Click to expand...
Click to collapse
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Mobile service
Crawshayi said:
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Click to expand...
Click to collapse
I installed this successfully but I still can't make or receive calls. I am wondering if the version of cyanogenmod that I flashed might not be compatible but I did not get a status 7 error when installing. I am also wondering why I got the sim card message when first installing cm11. The version that I installed is stated above on my first post but cyanogenmod has m7 and m7vzw, I can install m7, which I believe is for GSM but I have a Verizon HTC One. When I try to flash the m7vzw version I get the status 7 error code. I tried to do a fix for it but I may have done this incorrectly since I got a status 6 error code. Plz help. I need this phone for work.
You want the m7vzw, the regular m7 is gsm. Status 7 refers to an error in the update script or an incompatible update binary. Does it give a specific error with that status 7? You should also update your twrp to version 2.7.0.4b-santod. http://www.androidfilehost.com/?fid=23329332407584851
Last i heard cm11 is only in preview and data and calls do not work. That may have changed though.
Error
I updated the twrp to v2.7.0.4b-santod, did a factory reset and tried to flash cm11 for m7vzw and was given this mssg...E:Error executing updater binary in zip ' /sdcard/Download/cm-11-20140124-NIGHTLY-M7VZW.ZIP' Setting performance mode OFF. Error flashing zip....etc.....
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Compatible
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Recommendation
cmlusco said:
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Click to expand...
Click to collapse
I decided to go with cm 10.2.1. Thanks for everything!
Zacb01 said:
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Click to expand...
Click to collapse
Hmm thats strange, mabey cm11 just dosent like twrp or something. Glad you got something figured out.
Upgrading to lollipop
Someone should please help on how to upgrade to lollipop 5.0 on HTC m7 complaining of md5 file not found
Here is my story:
My Boss at work drunk one night ordered the P6 from China and it was delivered. To his surprise Google Play did not work.
Being a proud owner of 3 rooted devices with custom ROMS I offered my services to install a custom ROM on his P6 that would here in the UK.
However when using adb to boot into fasboot mode in order to flash a custom recovery nothing happened, I was left with a stuck logo screen.
The phones details are as follows:
kernel: 3.0.8-00796-g97d2208 [email protected] # 1
build: B113SP02
This particular build came with SuperSU already installed. I say already installed as I done a factory reset and it was still there.
I have copied over the beta kit kat zip in the hope that installing this from the stock recovery will help things, I need to wait for an sdcard though.
Am I going done the right path and if not could I be steered in the right path?
Any help will be greatly appreciated.
mediaman123 said:
Here is my story:
My Boss at work drunk one night ordered the P6 from China and it was delivered. To his surprise Google Play did not work.
Being a proud owner of 3 rooted devices with custom ROMS I offered my services to install a custom ROM on his P6 that would here in the UK.
However when using adb to boot into fasboot mode in order to flash a custom recovery nothing happened, I was left with a stuck logo screen.
The phones details are as follows:
kernel: 3.0.8-00796-g97d2208 [email protected] # 1
build: B113SP02
This particular build came with SuperSU already installed. I say already installed as I done a factory reset and it was still there.
I have copied over the beta kit kat zip in the hope that installing this from the stock recovery will help things, I need to wait for an sdcard though.
Am I going done the right path and if not could I be steered in the right path?
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Never touch the phone of your boss.
XDAvatar said:
Never touch the phone of your boss.
Click to expand...
Click to collapse
You may be right LOL, any advice though...........?
mediaman123 said:
You may be right LOL, any advice though...........?
Click to expand...
Click to collapse
Push the recovery of a official chinese firmware on it and try updating from there.
XDAvatar said:
Push the recovery of a official chinese firmware on it and try updating from there.
Click to expand...
Click to collapse
So your saying that trying to update my current build through the stock recovery to the latest kit kat build is the way to go?
I cant actually push any recovery images to the device as fastboot mode fails to initialize, hence why I am hoping an official update through stock recovery and sd card may solve that problem.
My aim is to get the latest kit kat TWRP installed, back up the stock build, then install a custom ROM.
mediaman123 said:
So your saying that trying to update my current build through the stock recovery to the latest kit kat build is the way to go?
I cant actually push any recovery images to the device as fastboot mode fails to initialize, hence why I am hoping an official update through stock recovery and sd card may solve that problem.
My aim is to get the latest kit kat TWRP installed, back up the stock build, then install a custom ROM.
Click to expand...
Click to collapse
Yes, sdcard is the solution.
XDAvatar said:
Yes, sdcard is the solution.
Click to expand...
Click to collapse
Ive been looking at various posts regarding the kit kat update and it makes reference to the B132 build and how its essential your on this first before updating to the B510 Kkit kat build.
Should I update to the B132 first?
mediaman123 said:
Ive been looking at various posts regarding the kit kat update and it makes reference to the B132 build and how its essential your on this first before updating to the B510 Kkit kat build.
Should I update to the B132 first?
Click to expand...
Click to collapse
Yes if you want the KK released by HUAWEI Romania. If you use the other BETA you must be on B125.
XDAvatar said:
Yes if you want the KK released by HUAWEI Romania. If you use the other BETA you must be on B125.
Click to expand...
Click to collapse
what other kit kat build is available?
what would you recommend?
I realize i will be putting a cutom ROM anyway, but jut so a stable nandroid backup can be made of an official build.
Thanks so far, you have been really hlepful........
Through more investigation it seems that the B510 kit kat update includes Google Play so it may be wise to install that and therefore the B132 first....
couldnt get the b132 build on or the b520, there were errors........
decided to flash twrp for JB and then install a custom rom....
will i ever be able to update to a KK rom now
XDAvatar said:
Yes.
Click to expand...
Click to collapse
Does it require updating to a stock build through stock recovery....
mediaman123 said:
Does it require updating to a stock build through stock recovery....
Click to expand...
Click to collapse
Yes. Of course.
XDAvatar said:
Yes. Of course.
Click to expand...
Click to collapse
That is a pain.........it will do for now I suppose......
I haven't heard of anyone else on here mentioning the B113 build, only B132 and so on...
Do you think this is an issue? Should I be updating to another build before trying B132?
Does the stock recovery need to match up with the OS build?
hi Have you done anything with your mobile?, I got the same Chinese B113SP06 with TWRP Recovery. I'm just looking for to update to official KitKat as on rooted device cannot run some apps.
mediaman123 said:
That is a pain.........it will do for now I suppose......
I haven't heard of anyone else on here mentioning the B113 build, only B132 and so on...
Do you think this is an issue? Should I be updating to another build before trying B132?
Does the stock recovery need to match up with the OS build?
Click to expand...
Click to collapse
If you still need a help look here http://forum.xda-developers.com/ascend-p6/general/huawei-p6-u06-chinese-rom-help-t2864228
I have same chinese mobile but it's back to international now.
I recently decided to get back in the trying customized software after taking almost a year and half break from regularly doing it back on my Nexus S. Everything was going smoothly at first and I choose the latest version of liquidsmooth as first at bat and it worked like a charm until the cellular radio would not turn on. I tried everything I could find and even tried flashing the latest radio while on the rom, but no dice. I had to flash the stock image and it worked again, but when I tried flashing again same problem. I even tried slim rom after my second attempt with liquid and the radio just would not work. Wifi worked like a charm but no cellular at all. Can anyone help me with this. I really liked what I got to play around with on liquidsmooth, but I need my phone to actually function as phone. For now I am back to stock until I can find a solution.
Which stock image did you flash? I recommend
http://forum.xda-developers.com/showthread.php?p=53353625
Lemme guess...you were using twrp to flash 4.4 ROMs
jrebo said:
Which stock image did you flash? I recommend
http://forum.xda-developers.com/showthread.php?p=53353625
Click to expand...
Click to collapse
I did flash that one. It's what I'm running now until I can figure out how to get my custom flashes working.
Skripka said:
Lemme guess...you were using twrp to flash 4.4 ROMs
Click to expand...
Click to collapse
Yes. I read that as long as I used version 2.6.3.3 or higher, it would be fine.
Protoroll said:
Yes. I read that as long as I used version 2.6.3.3 or higher, it would be fine.
Click to expand...
Click to collapse
"would be fine" in the sense that it has been common knowledge since 4.4 CyanogenMod builds started in November 2013...that TWRP does not work on L900 for AOSP-base 4.4, and it never has. And by the looks of things never will, as there's been no progress on L900 TWRP working in months,
Use PhilZ to flash and odds are your radios will magically work.
Skripka said:
"would be fine" in the sense that it has been common knowledge since 4.4 CyanogenMod builds started in November 2013...that TWRP does not work on L900 for AOSP-base 4.4, and it never has. And by the looks of things never will, as there's been no progress on L900 TWRP working in months,
Use PhilZ to flash and odds are your radios will magically work.
Click to expand...
Click to collapse
Alright, thank you for the help. I will try PhilZ and see how it goes.
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
Hello, I find now we have 2 latest TWRP recoveries, one is built by dianlujitao, the other one is the official build.
Which one do you choose? Why?
microwaveoven said:
Hello, I find now we have 2 latest TWRP recoveries, one is built by dianlujitao, the other one is the official build.
Which one do you choose? Why?
Click to expand...
Click to collapse
Use the official. If you have issue with it, the use blu_spar v14 twrp.
And read FAQ #9 in this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Use the official one.
abhibnl said:
Use the official one.
Click to expand...
Click to collapse
I flashed the official one, but the phone auto rebooted each time after the splash screen of the recovery appeared......
microwaveoven said:
I flashed the official one, but the phone auto rebooted each time after the splash screen of the recovery appeared......
Click to expand...
Click to collapse
I was using the official 3.0.3 and now I am on 3.0.4-0 by jcadduono. For me both work without issues.
Try the 3.0.4
I love the one blu_spark provides. Never had serious problems with it, but I disliked the fact that TWRP provided an outdated build all the time which loved to make serious problems.
microwaveoven said:
I flashed the official one, but the phone auto rebooted each time after the splash screen of the recovery appeared......
Click to expand...
Click to collapse
I am using the 3.0.4 version for official TWRP thread and it's working wonderfully for me. Maybe your flashing procedure is wrong or something is messing with your recovery.
abhibnl said:
I am using the 3.0.4 version for official TWRP thread and it's working wonderfully for me. Maybe your flashing procedure is wrong or something is messing with your recovery.
Click to expand...
Click to collapse
Since the flashing procedure is really simple and easy, only a "fastboot flash recovery xxx.img", I think there may be something messing with my recovery, but I flashed it after fully decrypted (wiped) the device. Anyway, I always encounter weird problems, I don't mind these problems now.
tnsmani said:
I was using the official 3.0.3 and now I am on 3.0.4-0 by jcadduono. For me both work without issues.
Try the 3.0.4
Click to expand...
Click to collapse
So many versions of TWRP...
Thank you, I'll try.
emuandco said:
I love the one blu_spark provides. Never had serious problems with it, but I disliked the fact that TWRP provided an outdated build all the time which loved to make serious problems.
Click to expand...
Click to collapse
Yes! I also think so! :good: