I'm running CM11 M9 and am trying to update to M10.
I am getting the following error.
Installing zip file '/sdcard//cmupdater//cm-11-20140916-SNAPSHOT-M10-fireball.zip'
Installing '/sdcard//cmupdater//cm-11-20140916-SNAPSHOT-M10-fireball.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Entering TWRP battery check thread loop with delay timer set to 2 sec
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: assert failed: getprop("ro.baseband") == "1.53.06.1009"
assert failed: getprop("ro.baseband") == "1.53.06.1009"
E:Error executing updater binary in zip '/sdcard//cmupdater//cm-11-20140916-SNAPSHOT-M10-fireball.zip'
E:Error installing zip file '/sdcard//cmupdater//cm-11-20140916-SNAPSHOT-M10-fireball.zip'
Done processing script file
Click to expand...
Click to collapse
I currently have baseband 1.53.51.0108
I'm hesitant to change the baseband if I dont have to.
Hi, enricong.
I had similar problem when updated from M8 to M9.
I updated baseband and everything was fine.
Now, I'm not having this problem, but when updated to M10, I received a lot of popups about process crashing.
I'll probably lose one more night to solve it.
Did you just updated via CMW? Or did you do any wipe?
Tks!!
enricong said:
I'm running CM11 M9 and am trying to update to M10.
I am getting the following error.
I currently have baseband 1.53.51.0108
I'm hesitant to change the baseband if I dont have to.
Click to expand...
Click to collapse
CM 11 was changed to work with the newer radio like 6 months ago. I would flash it.
Both firmware and recoveries currently have minimum requirements.
See ---> http://wiki.cyanogenmod.org/w/Fireball_Info
enricong said:
I'm running CM11 M9 and am trying to update to M10.
I am getting the following error.
I currently have baseband 1.53.51.0108
I'm hesitant to change the baseband if I dont have to.
Click to expand...
Click to collapse
Yeah, my radio is newer.
But you need to have the exact radio (not newer).
So i just flashed it.
enricong said:
Yeah, my radio is newer.
But you need to have the exact radio (not newer).
So i just flashed it.
Click to expand...
Click to collapse
not exactly ... your previous radio: 1.53.51.0108 ... is an OLDER Z321e / Valente radio from March 4th 2013!! there is also the valente-tw radio 1.53.51.0528 from June 6th 2013 (the newest known for the valente-series and that's a JB4.1 radio btw) ... and on a note again, YES the valente-jp & valente-tw radios ARE compatible with our Droid Incredible 4G LTE
the actual most _recent_ version is that proposed DInc4G radio 1.53.06.1009 ... which has an actual date of _November 15th 2013_ and got released as/with the smaller January 2014 OTA for our DInc4G.
Related
I have the ICS leak running fine (no root yet). I just want to flash the radio image only.... do i need root or will the stock bootloader give me a option to flash a radio upgrade without flasing the entire new rom?
linnon said:
I have the ICS leak running fine (no root yet). I just want to flash the radio image only.... do i need root or will the stock bootloader give me a option to flash a radio upgrade without flasing the entire new rom?
Click to expand...
Click to collapse
I believe the radio is exactly the same as the "old" leak.
I read that it is different. It has a different build number too.. I just wanted to push the new radio instead of the entire ROM
linnon said:
I read that it is different. It has a different build number too.. I just wanted to push the new radio instead of the entire ROM
Click to expand...
Click to collapse
Someone compared the old radio to the new radio and they are exactly the same. Same Md5 sum and everything.
You sir just saved me a lot of time! Thanks
xxquicksh0txx said:
Someone compared the old radio to the new radio and they are exactly the same. Same Md5 sum and everything.
Click to expand...
Click to collapse
then how are their improvements? lol im confused
edit: nvm read the post
So I'm on my 3rd M8. They all from day one (literally as I walked out of the AT&T store) would reboot randomly, usually in the afternoon, all stock running the latest OS. On my 3rd I've installed Cyanogenmod and have been running the M builds (currently on M11), but now besides still freezing and randomly rebooting my wi-fi passwords get forgotten at random.
I have no answer for why this is happening, all i can think of is that its bugs in the radio version. Since I'm on my 3rd phone I can't imagine it's hardware and I'm not alone on this...
Has any other device that connects to your router also dropping signal and passwords too,or just your device. The latest AT&T radio is 1.19. I'm pretty confident boot loader will tell you that..Try other ROMs,maybe its a bug with the latest milestone release
Ill try the new radio. Last i checked it was 1.16. Since it happens in both cyanogenmod (and just today) as well as stock...im pointing at the radio too.
Seems to not reboot/crash when Wi-Fi is off.
trajik78 said:
Ill try the new radio. Last i checked it was 1.16. Since it happens in both cyanogenmod (and just today) as well as stock...im pointing at the radio too.
Click to expand...
Click to collapse
Did you try to update the entire firmware package, or just the radio? Just thinking of this, since WiFi is one of the updated firmware modules. It still doesn't explain why we haven't seen this issue impact others. But worth a try anyway.
redpoint73 said:
Did you try to update the entire firmware package, or just the radio? Just thinking of this, since WiFi is one of the updated firmware modules. It still doesn't explain why we haven't seen this issue impact others. But worth a try anyway.
Click to expand...
Click to collapse
I updated the radio to 1.19 hoping it would help. However it was still doing it. It's really strange that I would have this issue on 3 of the phones. Not sure about FIRMWARE package...?
trajik78 said:
Not sure about FIRMWARE package...?
Click to expand...
Click to collapse
Firmware package includes hboot, radio, WiFi, Bluetooth and other modules like media; as well as kernel and recovery. It get updated separately from the ROM, and also requires S-off to flash manually.
Wonders_Never_Cease has all the recent AT&T firmware packages and instructions to flash posted here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Again, it doesn't explain why you have this issue on the stock ROM or an AOSP ROM. But its worth trying, for lack of any better ideas.
What am I looking for? Since I'm running Cyanogenmod 11, am I installing
Download:
2.22.1540.4 firmware only unmodified
http://goo.gl/FJ7Hhv
???
trajik78 said:
What am I looking for? Since I'm running Cyanogenmod 11, am I installing
Download:
2.22.1540.4 firmware only unmodified
http://goo.gl/FJ7Hhv
???
Click to expand...
Click to collapse
2.23.502.3 is the latest firmware released for AT&T. So I'd try that.
redpoint73 said:
2.23.502.3 is the latest firmware released for AT&T. So I'd try that.
Click to expand...
Click to collapse
just flash it from TWRP?
this:???
Modded Hboot(Thanks santod040):
M8 - 2.23.502.3
No Red Text: http://goo.gl/ins3or
thanks Totoro.
HBOOT says my HBOOT version is 3.16.0.0000
OS-1.58.502.1
trajik78 said:
just flash it from TWRP?
Click to expand...
Click to collapse
No!!! Instructions on flashing the firmware are given on the webpage I linked. You flash with fastboot, and s-off is required.
trajik78 said:
this:???
Modded Hboot(Thanks santod040):
M8 - 2.23.502.3
No Red Text: http://goo.gl/ins3or
Click to expand...
Click to collapse
Actually, you will want this one: https://www.androidfilehost.com/?fid=23681161096069444
It includes WNC's debloated stock ROM. So the download is huge. But it has the whole firmware package.
The file you linked is hboot only.
trajik78 said:
thanks Totoro.
Click to expand...
Click to collapse
lol, you're welcome.
how can i tell what firmware im currently running?
do i need to install a whole other ROM (ISIS?) to get the firmware?
trajik78 said:
how can i tell what firmware im currently running?
Click to expand...
Click to collapse
Hboot number and radio number.
Hboot 3.16 indicates original (1.54/1.58) firmware. I believe the corresponding radio is 1.14xxx.
trajik78 said:
do i need to install a whole other ROM (ISIS?) to get the firmware?
Click to expand...
Click to collapse
Nope. You can just flash the firmware by itself.
I only get rebos still with wi-fi on. I didn't try flashing one of those ROMs above...was slightly confused. However I did install the GPE 4.4.4 RUU. Hoping that radio/software combo will solve my woes.
I've flashed the GPE 4.4.4 RUU here, and changed the CID to GOOGL001.
No random reboots after 2 days! wi-fi seemed the be the big issue and it seems to be solved!
I hope this helps others who have had the same random reboots, seemingly caused by wi-fi problems.
Info:
GPE RUU 4.4.4 from above thread.
Kept my phone unlocked. and with S-off. (SU installed)
CID-GOOGL001
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OPENDSP-V32.2.2-00542-M8974.0213
OS-2.12.1700.1
EMMC-BOOT 2048MB
JUN 16 2014,18:47:55.0
So I had a working Evo 4G LTE with CM11 on it, it was retired when I got a new One M8. I needed to pull Jewel out of retirement for another number, and it wouldn't activate. I understood that CM11 does not have the activation modules on it and I need to go back to stock or rooted stock, or a rom that has the activation software on it. So I chose an Android 4.3 stock rooted rom deodexed. I managed to get the recovery updated to close to the latest one, the errors i was getting with the earlier version seemed to focus on not being able to mount sd card. Updating the TWRP seems to have fixed that particular error, but now I'm getting the error executing updater binary. I also managed to wipe out the rom that was at least running even tho I couldn't make phone calls. I've rooted a couple of times and I am marginally able to follow rooting directions, if anyone cares to help me get back on track here. From the looks of that error, I've got to do something with that hboot perhaps? I'm attaching a few screenshots that show the error and some versions of the stuff it's running. No booting to a rom, I only have the recovery and wasn't able to connect adb when in fastboot- I'll have to cover that whole adb thing again if it turns out I need to, it doesn't seem to work on my computer. Any pointers would be appreciated-
Are you using official twrp or captain throwbacks custom twrp?
gstanke said:
Are you using official twrp or captain throwbacks custom twrp?
Click to expand...
Click to collapse
Looks like it could be Captain Throwbacks- This was the file name..
PJ75IMG_TWRP-Recovery-2.8.0.2-Jewel_CPTB.zip
And you have already updated to the 4.3 partition layout?
gstanke said:
And you have already updated to the 4.3 partition layout?
Click to expand...
Click to collapse
I believe I did, since I had CM11 working (mostly) on the phone in Feb or March of this year. It was my understanding I had to have the new layout to run cm11, which I believe was based on KK4.3. I do recall having a lot of problems getting the camera and some apps to work because of the new and "better " partition scheme.
Hardstarburst said:
I believe I did, since I had CM11 working (mostly) on the phone in Feb or March of this year. It was my understanding I had to have the new layout to run cm11, which I believe was based on KK4.3. I do recall having a lot of problems getting the camera and some apps to work because of the new and "better " partition scheme.
Click to expand...
Click to collapse
As far as I know cm11 didn't need the new layout. If you aren't positive you have updated to the new JB4.3 layout I'd recommend running the ruu, reflash Captains twrp and try the rom again.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
What version is your bootloader?
gstanke said:
As far as I know cm11 didn't need the new layout. If you aren't positive you have updated to the new JB4.3 layout I'd recommend running the ruu, reflash Captains twrp and try the rom again.
---------- Post added at 11:42 AM ---------- Previous post was at 11:41 AM ----------
What version is your bootloader?
Click to expand...
Click to collapse
Looks like 1.19.2222 see attachment
Hardstarburst said:
Looks like 1.19.2222 see attachment
Click to expand...
Click to collapse
There's your problem. You need to flash CM11 for the old partition layout (or upgrade to the new layout and flash the version of CM11 that you were originally trying to flash).
Hello,
I'm looking for some guidance on trying to install CM12 on HTC One (M8) with HBOOT 3.16.0.0000. Currently, when I try to flash the firmware in TWRP, I get a message that says HBOOT 3.18 or 3.19 is required. I do have S-OFF. Other information: CID-CWS__001. I'm not sure of the next steps to take.
Thanks!
When you say flash firmware are you talking about the cm12 ROM zip?
You flash firmwares in hboot/bootlooader.You will want to have Supercid for it to flash.
jball said:
When you say flash firmware are you talking about the cm12 ROM zip?
You flash firmwares in hboot/bootlooader.You will want to have Supercid for it to flash.
Click to expand...
Click to collapse
Yes, my mistake. I want to flash the CM12 ROM and I can't seem to do that because I (apparently) need a newer version of HBOOT.
My question is what is the next step? If I get supercid, will the CM12 ROM install or is there another intermediate step (upgrading HBOOT? How do I do that?).
Thanks!
poguemahone1976 said:
Yes, my mistake. I want to flash the CM12 ROM and I can't seem to do that because I (apparently) need a newer version of HBOOT.
My question is what is the next step? If I get supercid, will the CM12 ROM install or is there another intermediate step (upgrading HBOOT? How do I do that?).
Thanks!
Click to expand...
Click to collapse
Yes another step is needed,
Because your S-OFF,Supercid you can flash other firmwares to your device that will allow anything based on 5.0.0-5.0.1 and still run smoothly.
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
I even recommend converting to Dev edition fully and once fully converted it will OTA to the latest firmware for you .once your up to date you just use twrp/philz recovery and flash away
jball said:
Yes another step is needed,
Because your S-OFF,Supercid you can flash other firmwares to your device that will allow anything based on 5.0.0-5.0.1 and still run smoothly.
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
I even recommend converting to Dev edition fully and once fully converted it will OTA to the latest firmware for you .once your up to date you just use twrp/philz recovery and flash away
Click to expand...
Click to collapse
Thanks jball. I ended up doing something very similar (http://intoandroid.com/turn-gsm-htc-m8-google-play-edition/). Worked flawlessly and now I'm running Lollipop.
poguemahone1976 said:
Thanks jball. I ended up doing something very similar (http://intoandroid.com/turn-gsm-htc-m8-google-play-edition/). Worked flawlessly and now I'm running Lollipop.
Click to expand...
Click to collapse
Your welcome
I came from that very conversion but what I don't like about the full conversion is the system is full to the max .
Now by converting to Dev edition and flashing the ROM instead I have all this system left cause of the Sense partition table
I'm still on GPE conversion...I had thought about switching to Dev edition though...which firmwares have y'all used ? I was thinking 3.28.1540.5...
Well I was going to screenshot boot loader,but I forgot the key combo for boot loader screenshots. Here's what I with
Hboot: 3.19
Cid : 11111111
Mid: OP6B17000
FW : 3.11.1700.5
Im using graffixnyc's android l firmware
jxcorex28 said:
I'm still on GPE conversion...I had thought about switching to Dev edition though...which firmwares have y'all used ? I was thinking 3.28.1540.5...
Well I was going to screenshot boot loader,but I forgot the key combo for boot loader screenshots. Here's what I with
Hboot: 3.19
Cid : 11111111
Mid: OP6B17000
FW : 3.11.1700.5
Im using graffixnyc's android l firmware
Click to expand...
Click to collapse
You would want to use the 3.28.1540.***** cause if you did the earlier ruu you won't be able to OTA unless you change your CID
jball said:
You would want to use the 3.28.1540.***** cause if you did the earlier ruu you won't be able to OTA unless you change your CID
Click to expand...
Click to collapse
Here's what I have:
Hboot: 3.19
Cid : 11111111
Mid: 0P6B12000
FW : 3.11.1700.5
You think it makes sense to upgrade FW to 3.28.1540? Are the OTA updates the main benefit to upgrading?
poguemahone1976 said:
Here's what I have:
Hboot: 3.19
Cid : 11111111
Mid: 0P6B12000
FW : 3.11.1700.5
You think it makes sense to upgrade FW to 3.28.1540? Are the OTA updates the main benefit to upgrading?
Click to expand...
Click to collapse
No not the only benefit,
Stability when flashing the most recent Roms is another reason.
When flashing lollipop Roms it helps to be as up to date as you can in my opinion.
I found that when I flashed a lollipop firmware and then flashed a lollipop ROM it basically converted me to full GPE and left me with the system being about 200kb chey of having no space left (just like taking the OTA to GPE lollipop does)
jball said:
I came from that very conversion but what I don't like about the full conversion is the system is full to the max .
Now by converting to Dev edition and flashing the ROM instead I have all this system left cause of the Sense partition table
Click to expand...
Click to collapse
Why would this matter? It allows you to go back to Sense ROMs. But aside from that, I don't think that having system storage available yields any benefit. Or am I missing something?
redpoint73 said:
Why would this matter? It allows you to go back to Sense ROMs. But aside from that, I don't think that having system storage available yields any benefit. Or am I missing something?
Click to expand...
Click to collapse
It mattered when I tried to move an 815kb file to "system/bin" when there was only 225kb of system left.
It's a known issue ,
So I went back to Sense and flashed the stock GPE 5.0.1 ROM and have over 1.5g of extra space (not that I could soak up that much space)
jball said:
It mattered when I tried to move an 815kb file to "system/bin" when there was only 225kb of system left.
Click to expand...
Click to collapse
Ah, I see. So obviously if you try to add something to the system partition, and its maxed out, then that is a problem. Figured I was missing something.
OK, so I got the unofficial of the android development thread thing for the ATT HTC One m8 and just found out that Cyanogen just released a official nightly. So I go to install it, have zip and gapps. I wiped all cache, system, and data. Flashed zip but says error, I'm like wtf. It says I need to update a bininary or something. My android tech skills are at like 5/10 so I'm stuck here. With the unofficial I'm on android version 5.0.1 and I think the nightly I have is 5.0.3 (CM12 I have 2015-01-12 15:25:50). So any thoughts or recommendations on my dilemma please let me know. Thanks
What recovery and version?
I'm not a CM user. But you might check if CM12 requires a specific (such as updated) version of recovery, or updated hboot. Also, I believe the latest version of TWRP has some flashing issues with older hboots.
So hboot is 3.16.0.0000 and twrp is 2.7.0.2 I'm just going to try a different nightly and see ifnit works. If not I'll just wait for a new release.
I just read on xda that I may need to update hboot by going back to stock and getting rid of custom recovery and root, then update hboot somehow. A little confused here. Any suggestions?
iTzz_KAMIKAZE said:
I just read on xda that I may need to update hboot by going back to stock and getting rid of custom recovery and root, then update hboot somehow. A little confused here. Any suggestions?
Click to expand...
Click to collapse
Do you know what hboot is required?
If its 3.19, you can't update the AT&T version to that hboot by the method you described. There is no "stock" AT&T hboot 3.19 yet.
Are you s-on or s-off?