Hi there.
As most of you already know, starting some time ago, CM team has decided to include a script check for firmware/hboot that will allow to flash a CM based ROM only on newer firmware/hboots (2.13.0000, 2.15.0000, 2.15.4444). This is valid for all 3.4 kernel based ROMs (CM 10.2, PACman, PA, Odyssey and so on). This check was introduced because some were reporting problems by flashing such ROMs on lower hboots and it was assumed that you MUST have the latest firmware in order to flash and run them.
This leaves few options for those having lower hboots: either upgrade to latest firmware OR not flashing the ROMs at all.
What if, someone has a lower hboot/firmware and IS able to run those ROMs without issues? The previous assumption that having lower hboot will make the ROM not working/booting is wrong...at least for me and I don't think I'm unique. I'm sure that there are more users having lower hboots that could run the latest ROMs without having to upgrade their firmwares. I'm on 1.06.0000 hboot S-On and I'm happy with it. I didn't had any single ROM flashed on my device that didn't run. I don't like the idea of being forced to upgrade (going through a procedure that for some proved to be difficult or bricked their phones) without needing to
Well there is still hope....
DISCLAIMER
PLEASE BE AWARE THAT I DO NOT RECOMMEND TO TRY THIS IF YOU DON'T KNOW WHAT YOU'RE DOING. EVEN IF FOR SOME USERS THE 3.4 KERNEL BASED ROMS WILL WORK ON LOWER HBOOT/FIRMWARE, CM DIDN'T PUT THAT CHECK THERE FOR NOTHING. I SHOULD NOT BE HELD RESPONSIBLE IF YOU FLASH SUCH ROM AND IT WON'T WORK. ALSO DO NOT REPORT ANY BUGS IN CASE YOU FLASH A ROM THIS WAY
Now, what people maybe thought already (but some don't know how to do it) is that you need to get rid of that script check in order to flash such ROM. Following the steps below anyone can get rid of the check and enjoy the newest ROMs without upgrading their firmware, presuming such a ROM will run on their firmware/device
Prerequisites:
In order to do this properly anyone will need two tools
- PPCGeeks Android Signer application (or similar) - DOWNLOAD
- Notepad ++ (or similar) - DOWNLOAD
Download and install both from links above then you're ready to go...
Steps to change the script & flash ROM:
1. Download the ROM of your choice and save it on your PC
2. Create a folder with a distinctive name (say CM 10.2) and extract the ROMs ZIP there
3. Look for the file "updater-script" located in \META-INF\com\google\android folder where you have previously extracted the ROM
4. Open the file using Notepad++
5. You will usually find the check for firmware at the beginning of the file and it'll look like something like below:
assert(getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000");
That means that, only the users having hboot 2.15.4444, 2.15.0000 and 2.13.0000 will be able to flash that ROM, anyone else will be receiving an error and ROM won't flash
6. Delete those lines with Notepad++ then save the file
7. ZIP the whole ROM again and give the ZIP a name
8. Sign the ZIP with Android Signer then copy the signed ZIP on your phone's sdcard
9. Flash the ROM
This should do it and you'll be able to flash such ROM.
There is an alternative method of extracting the file from the ZIP, deleting the lines then putting it back in the ZIP...this will skip the unzipping and signing steps but depending on how you'll do it it could also give you script errors when flashing (Status 7 or Status 6 errors). Steps to be followed for this "quick" method are:
1. Extract the updater-script from the ZIP and save it on your PC
2. Edit it with Notepad++ like I've described above
3. Open the ZIP with WinRAR and navigate to the place where updater-script is (\META-INF\com\google\android) and delete it from the ZIP
4. Using drag&drop, take the modified updater-script and drop it onto the opened WinRAR window in the location where it should be. There will be a popup windows to confirm adding the file to the ZIP, just press OK.
5. Close the ZIP and flash it
Well many of you might already know and do this one way or another but there might also be some users that don't know how to do it and either ask for help in various ROM Development threads or just quit flashing the ROM
So this is for all those that would like to try the new 3.4 kernel based ROMs and don't know how to do it. It won't guarantee that such ROM WILL WORK on their devices, it just allows flashing it even if they don't meet the firmware requirements. If after flashing, the ROM won't boot or it'll boot loop, there's almost sure need for a firmware upgrade in order to run it.
Thanks rapier. This helps me tons.
I guess the only annoying part about it is that we have to delete those lines each time there's an update/nightly that comes out. But for the time being this will suffice until I have the luxury to upgrade my firmware.
Sent from my HTC One S using xda app-developers app
I too am on Hboot 1.06 and S-on and have never had problems with other ROMs. Being away from the community for several months i'm a bit bewildered by all the risky processes I have to carry out to get my phone to accept the new 3.4 kernel.
So I will give your method a try right away!
Many thanks
RichardW1992 said:
I too am on Hboot 1.06 ...
So I will give your method a try right away!
Click to expand...
Click to collapse
Have you had any success? I am very curious.
Thanks
Patrick
This looks interesting and looks much less complicated than the whole upgrade process.
I'm on HBOOT 1.13 and S-ON; I tried to flash CM 10.2 just for fun but I got the error message (script related).
I read that those who had no problem running the latest Trickdroid and Viper can use this ROM without upgrading their firmware. TD and Viper are the 2 latest ROMS I've been using.
I'm gonna try this this weekend or next week lol - although I prefer the features of Sense ROMS.
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
---------- Post added at 09:54 PM ---------- Previous post was at 09:11 PM ----------
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
This is known about theme'd files, you cannot sign them even with command line. They must be opened with 7zip as not to break the signature and edited that way, then close and flash.
Click to expand...
Click to collapse
I did that, so I guess I dont need to re-sign the file
I'll flash another day, Im really tired
By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
Thanks
salutcemoi said:
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
...
Click to expand...
Click to collapse
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
salutcemoi said:
...
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
I did that, so I guess I dont need to re-sign the file
...
Click to expand...
Click to collapse
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
salutcemoi said:
...By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
...
Click to expand...
Click to collapse
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Rapier said:
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Click to expand...
Click to collapse
thank you !
Much appreciated :good:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
cougzzz said:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Shouldn't be affected by the script change. This change only allows you to flash the ROM, nothing else. You can try a WiFi fix or reflash kernel for this kind of issue. I had CM10.2 running well on my phone and didn't have any problems with WiFi. Same for Odyssey ROM which is also Android 4.3 with same kernel as I know
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
I also had exactly the same issue with CM...could not fix it even after flashing kernels....gave up and went to AOKP ..now Wi-Fi works, still no 4g..but that wasn't working with CM either
Sent from my HTC One S using xda app-developers app
okaiuz said:
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
Click to expand...
Click to collapse
Same here
I'm also hboot 1.13
Sent from my HTC One S using xda app-developers app
I've read it in the forum for either AOKP or CM that lower HBOOT like 1.13 is going to cause bootloops....I was hoping that using this method, in the OP thread, I'd be able to upgrade to newer ROM...but I wasn't able to (bootloops)
Sent from my HTC One S using xda app-developers app
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
el_smurfo said:
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
Click to expand...
Click to collapse
Yup
I rooted my phone and flashed custom roms before the official JB firmware update.
Sent from my HTC One S using xda app-developers app
Related
CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded
I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.
Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Any comments from people that have this applied (and working with full root)?
Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
That worked Thanx
Kernel's working just fine with Avalaunch's Froyo ROM.
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.
lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!
Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.
Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk
for what ever reason i fought with 1.2 bootloader for about 6 days straight with 0 luck loading any ics rom's. so i decided to try the 1.1 bootloader and it works just fine. i have loaded every ics rom i have downloaded and every single one booted with no problems. i followed the process from the frozen ice rom for each of them. i am currently running the g harmony 4.o.4 ics 120 rom and it has been very stable and everything works except the camera and mic which is already a known issue with the ics rom's for the gtab.
jamcar's frozen ice thread
http://forum.xda-developers.com/showthread.php?t=1707503
a little video i made of the bootloader rebooting into ics
http://www.youtube.com/watch?v=7L2KYaiu0OI&list=UUitE779SbBIZKk0EGlnHWVg&index=1&feature=plcp
i don't know if this will work for everyone but it did work very well for me.
Possible other solution.
I had the same experience. Installed ICS bootloader 1.2 just fine. Then couldn't download any apps from anywhere. Went back and researched some more, downloaded 3DGtab-GAppZ- 8.3.zip, installed it the same way as ICS and everything fixed itself. Been using ICS for several weeks. Never going back! :good:
I'm curious about the speed of ICS? I just installed Frozen Ice and it seems that it takes some apps up to 30 seconds to load and the wi-fi has just been horrendous (other users are reporting that as well). Wondering if its just the Frozen Ice build that is doing this or if all the ICS Roms have this problem..
JJewel is the harmony ROM you are running available here?
jjewell said:
for what ever reason i fought with 1.2 bootloader for about 6 days straight with 0 luck loading any ics rom's. so i decided to try the 1.1 bootloader and it works just fine. i have loaded every ics rom i have downloaded and every single one booted with no problems. i followed the process from the frozen ice rom for each of them. i am currently running the g harmony 4.o.4 ics 120 rom and it has been very stable and everything works except the camera and mic which is already a known issue with the ics rom's for the gtab.
jamcar's frozen ice thread
http://forum.xda-developers.com/showthread.php?t=1707503
a little video i made of the bootloader rebooting into ics
http://www.youtube.com/watch?v=7L2KYaiu0OI&list=UUitE779SbBIZKk0EGlnHWVg&index=1&feature=plcp
i don't know if this will work for everyone but it did work very well for me.
Click to expand...
Click to collapse
thats insane!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
for two reasons:
1.) wrong bootloader
2.) the CWM version you have wasnt supposed to be able to flash above froyo but let you have ICS
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
Dymondy2k said:
I'm curious about the speed of ICS? I just installed Frozen Ice and it seems that it takes some apps up to 30 seconds to load and the wi-fi has just been horrendous (other users are reporting that as well). Wondering if its just the Frozen Ice build that is doing this or if all the ICS Roms have this problem..
JJewel is the harmony ROM you are running available here?
Click to expand...
Click to collapse
yes it was the Fr0z3n 1c3 build. it was due to a bad upload so users had a bad download, but it has been fixed
Jamcar.. It seems to be running great for me now.. much faster speeds in both wi-fi and opening apps...
jamcar said:
thats insane!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
for two reasons:
1.) wrong bootloader
2.) the CWM version you have wasnt supposed to be able to flash above froyo but let you have ICS
Click to expand...
Click to collapse
There's something definitely puzzling here but those 2 are not the reason for puzzlement.
As for point #1: yes, the TeamDRH 2.6.39.x kernel works on both the 1.1 and 1.2 bootloaders--it definitely was a surprise. This is what nVidia/ViewSonic should've done with their older 2.6.32.x kernels also when they updated the bootloader.
Point #2 is not puzzling either: Recovery (we're discussing only CWM here) mode consists of 2 components both of which are build when you compile CWM:
a) the /sbin/recovery program proper which puts up the menus and performs the tasks chosen by the user, and,
b) (for installation only) a program called (for Froyo onwards) META-INF/com/google/android/update-binary in the installation zip file.
It is this update-binary program which is responsible for reading and executing a META-INF/com/google/android/updater-script file which is where the steps required to install a ROM are written. Ie. it is not the recovery program which does the installation. So, as long as you have an update-binary program which understands the updater-script in the installation zip file, all CWM versions > 2.5.x will be able to do the job.
The only puzzling thing is how the 1.1 bootloader was put back.
If it was using one of the 1.1 nvflash packages we have floating around on this board, then the "system" partition would have been shrunk back to 200 MB. This means that during the ICS ROM install, some apps/programs wouldn't have been written--/tmp/recovery.log should show a lot of file copy failures during installation due to "no space left on device" errors. That file will also show which files were not copied. And depending on which files were not copied, it could or, could not--in this case--adversely affect the final ROM install.
rajeevvp said:
There's something definitely puzzling here but those 2 are not the reason for puzzlement.
As for point #1: yes, the TeamDRH 2.6.39.x kernel works on both the 1.1 and 1.2 bootloaders--it definitely was a surprise. This is what nVidia/ViewSonic should've done with their older 2.6.32.x kernels also when they updated the bootloader.
Point #2 is not puzzling either: Recovery (we're discussing only CWM here) mode consists of 2 components both of which are build when you compile CWM:
a) the /sbin/recovery program proper which puts up the menus and performs the tasks chosen by the user, and,
b) (for installation only) a program called (for Froyo onwards) META-INF/com/google/android/update-binary in the installation zip file.
It is this update-binary program which is responsible for reading and executing a META-INF/com/google/android/updater-script file which is where the steps required to install a ROM are written. Ie. it is not the recovery program which does the installation. So, as long as you have an update-binary program which understands the updater-script in the installation zip file, all CWM versions > 2.5.x will be able to do the job.
The only puzzling thing is how the 1.1 bootloader was put back.
If it was using one of the 1.1 nvflash packages we have floating around on this board, then the "system" partition would have been shrunk back to 200 MB. This means that during the ICS ROM install, some apps/programs wouldn't have been written--/tmp/recovery.log should show a lot of file copy failures during installation due to "no space left on device" errors. That file will also show which files were not copied. And depending on which files were not copied, it could or, could not--in this case--adversely affect the final ROM install.
Click to expand...
Click to collapse
wait then why does cm9 require that you CWM 5.x.x.x ( the one koush made for ICS)?
jamcar said:
wait then why does cm9 require that you CWM 5.x.x.x ( the one koush made for ICS)?
Click to expand...
Click to collapse
Is it a "hard" requirement or a "soft" recommendation? Because CWM works as I've described for user-driven zip file installs.
I used gtab.nvflash.1.2.branch.20110508 with cwmv3028 To go to BL 1.2 and then flashed G_Harmony_ICSv1.5(120)(SuperCharged)
It went smooth, works great, and I am very happy with my GTAB
rajeevvp said:
Is it a "hard" requirement or a "soft" recommendation? Because CWM works as I've described for user-driven zip file installs.
Click to expand...
Click to collapse
For cm9 I'm honestly not 100% sure, but in cm7 you had to have CWM v3.x.x.x it was a hard requirement. It wouldn't install if you weren't on v3.x.x.x
Sent from my SPH-D710 using xda app-developers app
jamcar said:
... but in cm7 you had to have CWM v3.x.x.x it was a hard requirement. It wouldn't install if you weren't on v3.x.x.x
Click to expand...
Click to collapse
Check this again: Official CM7 installs just fine with 2.x for these 2 reasons:
1. All official CM7 releases (even the latest 7.2) come with a kernel built for a 1.1 bootloader. This means that they expect to run on a 1.1 bootloader, which, in turn, means that recovery image must also necessarily have a 1.1 kernel.
2. All the versions of CWM v3.x that I've seen on this board have a 1.2 kernel in the recovery image.
This means that if you were planning to install any of the official CM7 builds, then you would not be able to do it by using any of the CWM-v3.x versions built by roebeet--CWM-v3.x just wouldn't boot. You would need to be running one of the 2 CWM versions for a 1.1. bootloader: CWM-v2.5.1.x or CWM-4.0.1.5.
Note:
CWM >= 3.x officially dropped support for "Amend" scripting. CWM-2.5.x supports both the old "Amend" and the newer "Edify" scripting.
There are unofficial CM7 repacks and RCs which have a 1.2 kernel and so will run on the 1.2 bootloader.
You could also insert a 1.1 kernel into a 1.2-based recovery image and get more choices of CWM versions--I'm running CWM-5.5.0.4Beta15 on my 1.1 right now, for instance.
These last 2 are the exceptions rather than the rule-- but, really, there's no need for any ambiguity in any of this. The fact that ICS ROMs and CM7.x can be installed using any version of CWM >= 2.5.1.x can easily be checked.
That's interesting. Wish I knew that before I switched over to 1.2
Sent from my VS910 4G using xda premium
opening this up for anyone that may have problems installing the kernel etc.
first question, i've out all of the necessary files into the CNA.zip (Codename Android) that i want to flash, but whenever i boot into TWRP to flash it, it fails. i could've sworn i saw @FBis251 say that zips didn't need to be signed, maybe i'm misunderstanding his meaning. anyone with advice?
I only really provide support for AOKP as TWRP was compiled using the AOKP source code. There may be differences in the code from other roms' recoveries that make the zip installations fail. What I can recommend you try is to try flashing it via TWRP + AOKP to verify that it isn't a TWRP error.
If you continue having problems it's up to the rom devs to make other mods work with their roms. There are just too many roms for me to keep up with and I haven't had time to be doing that.
I'm on AOKP (pay no attention to my sig) with TWRP and it's not checking signing on the zips, so I guess I don't know what the issue is
Sent from my Unicorn powered SGS4G
I'm assuming other zips flash fine? It might be a problem with the way the rom dev created the zip. Normally using 7-zip with highest compression (lvl 9) works for me in case you want to try re-zipping it yourself, assuming there aren't any other problems with the zip file.
It's the same zip I flashed (your) AOKP from. I did rezip it, on my Mac, so I don't know if the issue might arise with how he program is rezipping the file
Sent from my Unicorn powered SGS4G
well you might have better luck with the command line zip utility that comes with your mac.
You can extract the rom zip, then try doing this
cd /path/to/extracted_files
zip -9 -r ~/destination.zip *
that'll zip all the rom files up into a high compression zip. Try flashing after that.
Still nothing. Hmmm, I wonder what is causing this
Sent from my Unicorn powered SGS4G
Juls: Try "Betterzip" for Mac - that's what I used to set up Slim with Thomas's LZ kernel. It allows you to modify the zip file without extracting/unzipping it.
I installed the LZ kernal into the latest miui v4 rom Erik released today and when i flashed it through TWRP if flash successfully but i lost root access, so i tried flashing it through cm9 recovery because that's how i fixed the root access on gummy mutt but it didn't give me the option to fix root. Any help ?
allstar1397 said:
I installed the LZ kernal into the latest miui v4 rom Erik released today and when i flashed it through TWRP if flash successfully but i lost root access, so i tried flashing it through cm9 recovery because that's how i fixed the root access on gummy mutt but it didn't give me the option to fix root. Any help ?
Click to expand...
Click to collapse
Flash the superuser binary zip with cwm? Just google superuser binary and it should link you to it
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
Are you tired of seeing all that free space in your system partition? Well let's make use of it by moving your dalvik-cache to the system partition saving you a lot more space for apps and downloads Its all done automatically at boot all you have to do is hit thanks and flash the zip provided in recovery and reboot.
Update: should work on every rom just flash in recovery. hboot version no longer matters
thanks! sounds nice!
two questions:
1. what partitions are used for actual CM-nightlies? I flashed the 4.4.2 OTA a while ago, does this mean I have the new partition-layout?
(maybe a quick tip for everyone how to check which layout is used)
2. do we have to flash this every time we flash a new nightly?
Yes but as far as the second question you'll have to modify updater script anyway since you have the newer firmware every time you flash a new nightly. So what I do is also delete the line that says "format" also. That way any system modifications you make won't be touched.
Sent from my One Mini
Also with this mod you can make youre own init.d scripts and just put em in the init.d directory and they will run at boot. So you don't need a scripter app. Just set the permissions of your scripts accordingly 755 should do the trick
Sent from my One Mini
theodorius123 said:
thanks! sounds nice!
two questions:
1. what partitions are used for actual CM-nightlies? I flashed the 4.4.2 OTA a while ago, does this mean I have the new partition-layout?
(maybe a quick tip for everyone how to check which layout is used)
2. do we have to flash this every time we flash a new nightly?
Click to expand...
Click to collapse
AFAIK CM still uses the "old" layout. That means you'll have to modify the CM nightly zips to flash them successfully to your device, if it has the new partition layout.
I made a new thread to share my insights and to describe how to check which layout a device has: http://forum.xda-developers.com/showthread.php?t=2713849
morschesholz said:
AFAIK CM still uses the "old" layout. That means you'll have to modify the CM nightly zips to flash them successfully to your device, if it has the new partition layout.
I made a new thread to share my insights and to describe how to check which layout a device has: http://forum.xda-developers.com/showthread.php?t=2713849
Click to expand...
Click to collapse
Its very very easy to do simply open updater script look for the number 33 change it to 35 then look for 31 and change it to 33 then flash the ROM and flash my mod from this post and you're good to go.
Sent from my One Mini using Tapatalk
I'm just wondering if it's necessary to modify the boot.img, too? It contains a fstab, doesn't it? However, it seems to work as well with the original boot.img from the cm zip.
There is a custom kernel in this mod with the adjustments made that's why theres two different versions.lol
Sent from my One Mini using Tapatalk
this actually sounds great, never understood why htc kept 5gb to themselves.
however im on hboot 2.19, s off and quite happy with my phone as it is...would love to free up an extra 1GB though
thanks
Yeah there is really zero advantage to upgrading hboot.lol
Sent from my One Mini using Tapatalk
Quality! so for users like myself that are on (hboot 2.19) pre hboot 2.22...just flash the 4.2/4.3 link.aye ??
Braddison said:
Quality! so for users like myself that are on (hboot 2.19) pre hboot 2.22...just flash the 4.2/4.3 link.aye ??
Click to expand...
Click to collapse
Yessir
Sent from my One Mini using Tapatalk
Brilliant! so re: the CM nightlies.."simply open updater script look for the number 33 change it to 35 then look for 31 and change it to 33 then flash the ROM and flash my this mod".
also i normally unzip,delete all the apps,libs that i dont need/use, add pure x performance mod, add google launcher.xposed etc ..i can just do that the same way huh?
sorry for all the questions bud and thanks again
Yup, though pure x is virtually a placebo. I wouldn't even use it.
Sent from my One Mini using Tapatalk
yeah , see i wasn't too sure about it. as you say a placebo. although it does reduce the animation scale down...which i feel makes a difference but i suppose that can be done in dev options
You can switch animation off in development settings.lol or adjust it.
Sent from my One Mini using Tapatalk
just a heads up!! flashed your zip but keeps rebooting into recovery. hboot 2.19, twrp 2.6.3. latest cm11 nightly
Did ya flash the right one
Sent from my One Mini using Tapatalk
yup! for firmware 4.2/4.3
I'll check it out right now
Sent from my One Mini using Tapatalk
[OBSOLETE] @yshalsager As of 8.8.16 flashable TWRP non ARB Firmware now available see thread.
[GUIDE] Updating Modem, Bluetooth and DSP! ~~~ Without triggering ARP on WHYRED!
For anyone on customs rom and need to updated the above partitions?
The commands to flash them in fastboot are: -
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
pause
I just created a bat file (windows) with the above content.
All I need do in future is download a firmware from here, extract the three files and place the bat file in the same folder, and run it.
^^^ Note I have adb/fastboot setup with a global path in windows.
Haven't tested in operation yet but in theory should work. I'm on 8.7.5 Beta firmware at present and see no need to update until the custom rom in use requires update files.
Above 3 files have been reported safe to flash here (Thanks @aank) , without effecting the bootloader, so not to trigger ARP.
First two files are self explained.
DSP (Digital Signal Processor)
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
Attached is a sample bat file, just remove the .txt from the end of the file name.
I posted this before in the Everything About Anti Roll-back [Whyred] by @AL_IRAQI , but would probably get lost there.
Edit: - Edited the batch file to include a "pause", in case you double click instead of running in CMD/POWERSHELL window.
Cool, hope it works if i ever need it. Thanks
thx tested it, it works, i am still on anti 3 after updating these 3
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
rizdar said:
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
Click to expand...
Click to collapse
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
@corkiejp Do you recommend flashing the firmware files from 9.5.19 or the ones from 8.7.26 when moving to a custom rom?
corkiejp said:
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
Click to expand...
Click to collapse
I'm on Arrow OS right now.
But after I do the steps above, it seems like nothings changed.
The signal is still the same.
It's happening on all custom ROMs, is it because my providers?
Edit: I was on 8.7.26 (Masik U 2.2)
@eyebiz
I would stick with whatever firmware your device has at present. It is probably more recent than firmware recommend by custom roms.
There is really no reason to update firmware, if your device is working well with what you have!
If the rom recommends a specific firmware, then you may need to upgrade, but don't downgrade firmware to match.
If I'm flashing firmware, I usually use the version from beta roms, as that is often the more recent firmware.
I only update roms, once a month when security patches included. And patch the firmware at the same time.
@rizdar Your network provider maybe the problem, check your APN settings with the recommend settings of your provider.
The three files mentioned in this thread, may not be alter from one firmware to the next. It is usually the bootloader (which we need to avoid for ARP) that regularly changes.
You could compare files and hashes from different firmware to see if there is changes.
Hi @corkiejp
I've created TWRP flashable .zip with latest stable modem, dsp and bluetooth here :
https://drive.google.com/file/d/1eYys31FFgdxz4GyMFgMiuvoTWwwgER1Y/view?usp=drivesdk
The ARB should be fine as well,
I've tried myself, flashed it on top of 9.6.3 fw less ROM.
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
corkiejp said:
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
Click to expand...
Click to collapse
Oh, no, am not on xiaomi.eu. Just happen to look around the fw less thread, and it seems there's a need for a TWRP flashable zip for radio only update,
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
I didnt delete too much files from firmware update folder, only one i think is really safe to delete.
Alright, i will modify the file name.
It contain 8.8.16 Global files.
otonieru said:
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
Click to expand...
Click to collapse
Have you a link to git, it would be easier to just download the three files for me, than extracting them from Firmware zips.
Apparently those firmware files are safe. I flashed them with a .zip file I put together. For anyone that wants to try you can download it from here.
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
lol. you spoiled the surprise, it was a test. I'll release it soon
corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
I edited the original one and signed the .zip, it seems to be working. Although the cell power consumption is still quite high so far.
deleted
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
ahsnali said:
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
Click to expand...
Click to collapse
It may or may not help your situation. If your worried about your anti version, there is non arb firmware zips available with just them files.
VoLTE is broken on most PIE roms (I believe based on discussions in TE) , check your rom thread and see if anyone else has it working. Or if there is Patch to enable it.