Related
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
Hello,
I'm fairly inexperienced with this since this is my first Android device I've rooted manually (I have a Nexus 7 2012 I rooted via Nexus Root Toolkit). I have TWRP recovery v2.8.5.0 installed as well as SU and Busybox. Now I'm trying to install some Custom ROMS.
I've tried installing crDroid and Cyanogenmod 12.1, both of which have something along the lines of this error: (I copied and pasted part of the log, if you need the full log, just let me know) (this was when I tried installing crdroid, but Cyanogenmod had the exact same error minus the fact that the zip filename was different)
script aborted: This package is for device: xt1505,xt1506,otus_umts,otus_umtsds,otus,otus_ds; this device is surnia.
This package is for device: xt1505,xt1506,otus_umts,otus_umtsds,otus,otus_ds; this device is surnia.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/crdroid-5.1.1-20150912-otus.zip'
Error flashing zip '/external_sd/crdroid-5.1.1-20150912-otus.zip'
So far many google searches have brought nothing. My phone's model number is XT1526 and the code name is "otus", yet it appears that it is being identified as "surnia". Am I doing anything wrong? I'm wiping Data, System, Cache, and Dalvik Cache, and I've already created an update.zip in Titanium Backup as well as a Nandroid backup in TWRP recovery. As far as I know, this is the latest TWRP I can find, as the manager wants me to downgrade to 2.7.x.x, which I tried, only to have to reflash 2.8.5.0. And I'm getting the CM ROM download from CM's official website and I got the crDroid download from this website's Moto E 2015 ROMS forum. Can I?
A. Change the ID of my device to match the ID the ROM wants?
B. If the ROMS are the issue (I'm aware crDroid is based off of Cyanogenmod, so if CM doesnt work, maybe crDroid acts the same way), could I be pointed towards a few other ROMS that are close to Cyanogenmod or are just very useful to use?
C. Replace TWRP with CWM and try installing it that way?
Thank you so much in advance, I've tried every Google search possible and it seems hopeless. Hopefully these forums can help!
Fallonite said:
Hello,
I'm fairly inexperienced with this since this is my first Android device I've rooted manually (I have a Nexus 7 2012 I rooted via Nexus Root Toolkit). I have TWRP recovery v2.8.5.0 installed as well as SU and Busybox. Now I'm trying to install some Custom ROMS.
I've tried installing crDroid and Cyanogenmod 12.1, both of which have something along the lines of this error: (I copied and pasted part of the log, if you need the full log, just let me know) (this was when I tried installing crdroid, but Cyanogenmod had the exact same error minus the fact that the zip filename was different)
script aborted: This package is for device: xt1505,xt1506,otus_umts,otus_umtsds,otus,otus_ds; this device is surnia.
This package is for device: xt1505,xt1506,otus_umts,otus_umtsds,otus,otus_ds; this device is surnia.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/crdroid-5.1.1-20150912-otus.zip'
Error flashing zip '/external_sd/crdroid-5.1.1-20150912-otus.zip'
So far many google searches have brought nothing. My phone's model number is XT1526 and the code name is "otus", yet it appears that it is being identified as "surnia". Am I doing anything wrong? I'm wiping Data, System, Cache, and Dalvik Cache, and I've already created an update.zip in Titanium Backup as well as a Nandroid backup in TWRP recovery. As far as I know, this is the latest TWRP I can find, as the manager wants me to downgrade to 2.7.x.x, which I tried, only to have to reflash 2.8.5.0. And I'm getting the CM ROM download from CM's official website and I got the crDroid download from this website's Moto E 2015 ROMS forum. Can I?
A. Change the ID of my device to match the ID the ROM wants?
B. If the ROMS are the issue (I'm aware crDroid is based off of Cyanogenmod, so if CM doesnt work, maybe crDroid acts the same way), could I be pointed towards a few other ROMS that are close to Cyanogenmod or are just very useful to use?
C. Replace TWRP with CWM and try installing it that way?
Thank you so much in advance, I've tried every Google search possible and it seems hopeless. Hopefully these forums can help!
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
You need to be very careful with the variants because there are some variants of the new Moto E and maybe you downloaded the ROMs for a different variant of Moto E. For example this ROM instead is for real for your specified device
Regards
nilac said:
Hi and thank you for using XDA Assist
You need to be very careful with the variants because there are some variants of the new Moto E and maybe you downloaded the ROMs for a different variant of Moto E. For example this ROM instead is for real for your specified device
Regards
Click to expand...
Click to collapse
Hi nilac,
I downloaded the exact rom from the link you gave me, and I had the same error appear. Do you need the whole log? Or is there another solution?
Fallonite said:
Hi nilac,
I downloaded the exact rom from the link you gave me, and I had the same error appear. Do you need the whole log? Or is there another solution?
Click to expand...
Click to collapse
Hi again, well if it's still not working i suggest you then to write it over the Q&A forum of your device, right here:
E 2015 Q&A, Help & Troubleshooting
Good luck!
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
hicksd8 said:
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
Click to expand...
Click to collapse
You need the recovery from here to flash sagaopt roms IIRC.
jc1993 said:
You need the recovery from here to flash sagaopt roms IIRC.
Click to expand...
Click to collapse
Yes, that is the instructions I have been using and experiencing trouble with. I'll try it again.
Please give information how you solved difficulties. I'll probably try similar things soon. Thank you in advance
tag68 said:
Please give information how you solved difficulties. I'll probably try similar things soon. Thank you in advance
Click to expand...
Click to collapse
Well I tried it again with no success.
Can someone confirm for me that the ONLY difference between Saga and Sagaopt ROMs is the prerequisite partitioning and filesystem types required? ie, convert filesystems and SDcard filesystem to EXT4.
Trying to install CM13 Sagaopt complains something like "unable to execute the binary updater in the zip file". Trying to install CM12.1 Sagaopt gives exactly the same error so I guess the prerequisites are not right.
My phones are standard HTC Desire S and I assume that's okay?
I downloaded the ROMs from the Open Desire site after selecting device Desire S.
So still scratching my head on this one.
here my desire s runs now cm12.1
hicksd8 said:
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
Click to expand...
Click to collapse
the sagaopt rom uses the complete internal memory for the system (for a stable rom use latest CM12.1 nightly CM13 has ram and bluetooth issues)
Preparing and updating
(Optional but useful) http://forum.xda-developers.com/showthread.php?t=1679338 for new S-OFF HBOOT
(Optional but useful) http://forum.xda-developers.com/showthread.php?t=1858508 for new RADIO and Firmware (only B the rest is for a better stock 4.0.4 android)
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
@Layer_DE...........thank you for that. Certainly upgrading to TWRP v2.8.7.1 is key.
I flashed recovery file "TWRP-recovery-sagaopt-2.8.7.1.img" and the "error executing binary updater in zip" is gone.
Yes, I'm having some issues with CM13 so will try your suggestion of CM12.1
Many thanks. I'll post back with any further issues.
@Layer_DE.......I've flashed CM12.1 and it boots. Can you tell me which gapps file you flashed please? I'm finding that whatever gapps file I flash I seem to lose the virtual keyboard function. Using just CM12.1 the virtual keyboard works fine. I'd like to get the Play Store functioning correctly and its icon on my home screen. Thanks.
opengapps.org
ARM 5.1 pico
it works fine BUT for the first app you download you need more than a hour and every appinstallation takes very long
I'll give that a go. Thanks.
sent from my HTC smartphone
Hi All,
Just thought I'd give an update on this one........
I flashed TWRP 2.8.7.1 recovery and used it to set all filesystems to type ext4.
Then installed CM12.1 no problem.
Then installed opengapps 5.1 pico as suggested. No problem.
All working fine with that. In fact extremely good. No problem installing/uninstalling apps at all.
Still can't get CM13 (Marshmallow) to work. It will install but on reboot doesn't behave.
- You had me at 'Hello'...
Hi all -
Stumbled across this Thread, only to discover the AMAZING things still being done to these ol’ HTC Battle-Axes.
My interest stems from one of these devices recently being discovered as ’tucked away’ in a draw somewhere for a rainy day, and long forgotten by my Mother.
I don’t have any prior exposure to any form of Android - ( primarily due to my hate of any/everything Google. )
However, I’m now looking to break this arrogance of mine, with this otherwise un-used and forgotten lil’ HTC.
I am particularly impressed that you guys have managed to get this beast to dance - apparently without any major issues on Lollipop/Android v5.1 - via the installation of CyanogenMod 12.1.
Looking at your list of ingredients;
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
...all seems pretty straightforward.
( Well, straightforward enough - for me to be able to hunt around for explanations regarding what each step actually means! )
Being the ultraN00b I am, I’m curious as to how this set of instructions compares to say what the ‘official’ CyanogenMod position is;
wiki.cyanogenmod.org/w/Saga_Info
wiki.cyanogenmod.org/w/Known_Issues_page_for_saga
- Can any of you compare the ‘official’ CyanogenMod position, ( and specifically why they stop short at Gingerbread/Android v2.3.7 - via the installation of CyanogenMod 7.2 ), with what is suggested here?
- Are there any shortcomings that any of you have experienced running Lollipop/Android v5.1 , on this platform?
- How has the installation of Lollipop pulled up regarding stability? Any ‘glitches’ or ‘gremlins’ yet?
Nevertheless, I’m beyond impressed, and now pretty keen and excited to embark on my very first Android-expedition.
Thanks in advance for your responses -
Nunya-Biz
(c;=
Nunya-Biz said:
Hi all -
Stumbled across this Thread, only to discover the AMAZING things still being done to these ol’ HTC Battle-Axes.
My interest stems from one of these devices recently being discovered as ’tucked away’ in a draw somewhere for a rainy day, and long forgotten by my Mother.
I don’t have any prior exposure to any form of Android - ( primarily due to my hate of any/everything Google. )
However, I’m now looking to break this arrogance of mine, with this otherwise un-used and forgotten lil’ HTC.
I am particularly impressed that you guys have managed to get this beast to dance - apparently without any major issues on Lollipop/Android v5.1 - via the installation of CyanogenMod 12.1.
Looking at your list of ingredients;
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
...all seems pretty straightforward.
( Well, straightforward enough - for me to be able to hunt around for explanations regarding what each step actually means! )
Being the ultraN00b I am, I’m curious as to how this set of instructions compares to say what the ‘official’ CyanogenMod position is;
wiki.cyanogenmod.org/w/Saga_Info
wiki.cyanogenmod.org/w/Known_Issues_page_for_saga
- Can any of you compare the ‘official’ CyanogenMod position, ( and specifically why they stop short at Gingerbread/Android v2.3.7 - via the installation of CyanogenMod 7.2 ), with what is suggested here?
- Are there any shortcomings that any of you have experienced running Lollipop/Android v5.1 , on this platform?
- How has the installation of Lollipop pulled up regarding stability? Any ‘glitches’ or ‘gremlins’ yet?
Nevertheless, I’m beyond impressed, and now pretty keen and excited to embark on my very first Android-expedition.
Thanks in advance for your responses -
Nunya-Biz
(c;=
Click to expand...
Click to collapse
the CM12.1 is very stable and only has typical android bugs (found no device specific things) and the official cm people hasn't used the kernel 3.0 source of the desire from android 4.0
for istallation:
1. download adb from http://forum.xda-developers.com/showthread.php?t=2317790
1.1 download and install adb driver
1.2 if you use windows 8 or higher use the fastbootfix form https://opendesireproject.org
2.install adb to "C:\Windows" (pro: no path needed)
3.check android version in system settings if it is lower or lower2.3.X (if its not it could be ****ty) than check bootloader version
3.1 turn off fastboot in battery settings
3.2 power don phone
3.3 boot phone with vol down clicked and if its -REVOLUTIONARY- or if its 0.98.x s-off or 2.0X s-off go to 6
if its 0.98 s-on you go to 5
if its 2.02 ask anyone else on my desires with 2.02 s-off newer worked for me but you can try it (go to 4) or only unlock it
http://www.htcdev.com/bootloader select HTC Desire HD and dont upgrade anything (start at step 1 skip preparation) after that go to 8
4.download the oldest rom with you branding from http://androidruu.com/?developer=Saga
4.1 http://forum.xda-developers.com/showpost.php?p=18746686 downlad misc_version
4.2 http://forum.xda-developers.com/showthread.php?t=1312859 download DooMLoRD_v4_ROOT-zergRush-busybox-su.zip and extract zergRush
4.3 go to folder with misc_version and zergRush and open cmd there and type
adb push misc_version /data/local/tmp/
adb push zergRush /data/local/tmp/
adb shell
cd /data/local/tmp/
chmod 777 zergRush
chmod 777 misc_version
./zergRush
./misc_version -s 1.27.405.6
exit
exit
exit
4.4 execute the firmware form step 4
5 download and follow http://rev.alpharev.nl
6 follow http://forum.xda-developers.com/showthread.php?t=1679338 (optional)
7 follow B in http://forum.xda-developers.com/showthread.php?t=1858508 (optional)
8 follow my first tuturial (if you need help post it to the tread)
Hi there,
I managed to succesfully install CM13 on my girlfriends old HTC Desire S, but it's slow as hell and she keeps complaining (after refusing a more modern phone because of the bigger screens and her small hands...).
Now I'm looking for the old CM10.1 which ran fine on my old original Desire, but all the links I find are way outdated and down. Does anyone still have it?
Regards,
Markus
ElFidel said:
Hi there,
I managed to succesfully install CM13 on my girlfriends old HTC Desire S, but it's slow as hell and she keeps complaining (after refusing a more modern phone because of the bigger screens and her small hands...).
Now I'm looking for the old CM10.1 which ran fine on my old original Desire, but all the links I find are way outdated and down. Does anyone still have it?
Regards,
Markus
Click to expand...
Click to collapse
Try CM11 it runns very smooth and is fine (older than 4.4 isnt 100% supported by app developers)
I installed CM13 as well on my Desire S - at first it was really slow. Until I bought a faster SD card as I saw that the internal memory was emulated on the SD card. Therefore I tried it with a U3 speed SD card - now it is workable - I am happy to have cm13 installed
@schneert
What's the size of your SD Card? What do you mean by 'workable'?
@zurpher: I bought a 32Gb SD Card., therefore I have 32GB stated as internal memory. It is workable in that sense that it is fast enough to use it without very much slow issues. It is still not fast but I guess that is because of the RAM of the device.
During the last few months I have been testing several Nougat rom/kernel/modem/su combinations for the hlte N9005 international.
I created this thread to share my setup, hoping it will help others to save the many hours of research, trial, error and frustration I had before reaching the jackpot.
I have 3 hlte phones at my disposal, two myself and one my wife. All three are running trouble free.
By using my setup you will get:
Absolutely no freezes, reboots or FCs
Stable root and Safetynet checks ok
GPS fast and stable fix - average 5 seconds worst 20 seconds
Low battery drain (of course actual drain depends heavily on your apps and usage)
Everything works (AFAIK - you tell me what does not)
Keep in mind my main goal is to provide a stable setup. I will do my best to update this thread regularly, but it is very unlikely I will be using the very latest builds available, mainly because before I adopt a new build it must be thoroughly tested.
If you're interested head to the guide in Post #2
Why Resurrection Remix?
RR has, IMHO, the best combination of features and stability. The RR team has been around for a long time without the ups and downs of other roms. For the Note 3 we are in a very fortunate time, with an official build and many unofficial builds to choose from.
Since RR is based on LineageOS, it is available for most devices. It is very likely when we finally retire our Note 3 and move to another flagship, RR will be there for it.
Why Not Oreo?
Well, thread title says it all.
Credits and Thanks:
@vidwhal for the current RR build
@gj86 for Synergy kernel
@Jairus980 for Xenial kernel
@Hereiwas and @jcadduono for modems and bootloaders
@topjohnwu for Magisk
@stangri and @kantjer for Magisk unofficial daily beta builds
@Deic for the Safetynet fix Magisk module and @NovelliJack for finding the module
@MastahF and all other contributors that made the Open GApps project possible
Special thanks to @tarkzim for the RRN build used in initial setups.
and everyone else I forgot to mention.
>>>>>>> I know - screenshots below are from a previous setup. I will update then sometime in the future.
Rock Stable Setup
Using Resurrection Remix
Revision 11 - 11-Mar-2018
Phase 1 - Prepare for install
Here I am assuming you have a Windows PC. If not you will need to use google search to adapt my instructions to your available OS/hardware. The PC is only required for this phase.
1 - Samsung USB Driver:
Make sure you have the Samsung USB driver installed in your Windows PC.
If not download and install the latest driver:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.65.0.exe
2 - Odin:
If you do not have Odin, get it here, unpack to any folder and create a shortcut pointing to Odin3 v3.09.exe.
There are newer versions of Odin, but they may have issues with our Note 3. Odin v3.09 is the one to use.
3 - TWRP
New to TWRP? Read this guide: TWRP: the complete guide to using Recovery on Android.
If you do not already have it, install TWRP 3.2.1-0. Download it from https://dl.twrp.me/hlte. More info here.
If you no not have TWRP installed download the .tar file and flash with Odin.
If you have an older version download the .img file and use your current TWRP to flash the image into recovery partition.
4 - Update Bootloader and Modem:
You have to install latest Nordic Countries Bootloader and Modem. I have prepared a "tar.md5" with both.
And yes, modem is not country or region dependent. Rest assured Nordic will work no matter where you are.
Get it from here: N9005_Nordic_XXUGPQB1-Modem_XXSGBQD1-Bootloader.tar.md5
Updating bootloader and modem is a must!
If you don't you may get the "SIM Card not detected" error and GPS fix will be slow or not work at all.
There are many sure ways to flash modem and bootloader so that they "stick". What always works for me is:
- Restart into Recovery (TWRP)
- Select Reboot->Power off
- Turn on directly into download mode by holding Down Arrow+Home+Power at the same time
- Connect phone to PC
- Flash with Odin using the AP slot
Now you should check if update was successful. The best way is to install the app Phone INFO, run it and select the Firmware tab. The correct Bootloader and Baseband (modem) above should be displayed. There is a screenshot in first post.
If the update did not work repeat the steps carefully until it does. You may, as a last resort, after powering off remove the battery, wait for about 30 seconds, reinsert the battery and then turn on directly into download mode.
Thanks to @Hereiwas for the files I have used in previous setups. Check out in his thread Bootloader and Baseband for SM-N9005.
If you need more info on flashing modems and bootloaders also take a look at @jcadduono thread [Direct Download] Latest Bootloaders & Modems.
PHASE 2 - Download the necessary installation files
1 - Resurrection Remix Nougat rom - thanks @vidwhal:
Download from here: RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip.
Please note that I am not the rom builder or developer. All credits go to @vidwhal and the RR Team.
This is the rom thread: [ROM][HLTE][UNOFFICIAL][OMS]Resurrection Remix N.
Please note this build may not be the latest available. The goal here is to have a stable rom that you will be able to use as a daily driver with no issues for a long time. Only after a lot of testing a new build makes into my setup.
I modified the zip to remove Magisk. This will make it easier to use newer or beta Magisk builds if necessary in the future. Remember Safetynet is a cat and mouse game and changes happen fast.
Special thanks to @tarkzim, who produced the RR builds used in earlier setups. He did a fantastic job of producing a very stable build without a Note 3 device for tests. His builds led me to create this thread.
2 - Magisk v16.0 Official - thanks @topjohnwu):
Magisk Installer: Magisk-v16.0.zip
Magisk Manager: MagiskManager-v5.6.1.apk (optional - you might need it in the future)
Magisk Uninstaller: Magisk-uninstaller-20180222.zip (optional - you might need it in the future)
if you decide to use newer builds do it at your own risk. I strongly recommend to keep these.
3 - Gapps:
Open Gapps Pico: open_gapps-arm-7.1-pico-20180311.zip
Not much to say here. Open GApps FTW.
Again the above build is the one I tested. Use this for a failproof installation, but feel free to use a newer build. Usually it will not be a problem.
I prefer Pico Gapps so I have the bare minimum as system apps. And I live by the KISS Principle. All other gapps I need are installed as user apps so I am allowed to use Titanium Backup to backup/restore them with data.
If you would rather use another Gapps package just pick the one you want. All packages should work but the Aroma. Aroma does not work in TWRP 3.
4 - Xenial Kernel - thanks @Jairus980:
Xenial Kernel: [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
Kernel thread: [Kernel][Xenial][Hlte].
With Xenial you have some fixes like the correct charging current in lock screen and working Gravity, Linear acceleration and Orientation sensors. Of course there is a lot more under the hood. If you plan to do some kernel tweaking Xenial offers more options.
If you do flash Xenial kernel do not report any bugs in RR thread. To report a bug you must first go back to stock kernel by dirty flashing RR and Magisk. If you are still able to reproduce the bug then you may post it in RR thread.
Even if there is a newer kernel release, you should keep using the build I posted here to have my tested stable setup.
Special thanks to @gj86 for his Synergy Kernel, used in my previous setup. It is also a great option.
5 - GPS Fix:
In this setup there is no need for a GPS fix. GPS is fast and rock stable as it should always have been.
But you really must update your modem to my recommend Nordic QB1 or GPS will be slow or not work at all.
Do not worry about your current location. The modem will work not matter where you are.
Latest RR builds somehow made GPS fix slower. I checked the gps.conf file and it is exactly the same as in previous builds.
I have my own optimized gps.conf, prepared originally for Marshmallow CM13, with a few more adjustments for Nougat.
After installing my gps.conf in latest RR build, gps fix is back to normal, taking only a few seconds.
I prepared a flashable zip to install my gps.conf. It saves existing gps.conf and put mine in its place.
Download it from here: Fix-GPS-for-hlte-la14.1-based-roms-v1.zip.
PHASE 3 - Backup!!
Now it is time to make backups of your current setup.
Use TWRP to make a nandroid backup. You will need it if something goes wrong. If you are paranoid like me make two and save them on your PC hard drive.
If you use Titanium make also a Titanium full backup. Remember that you should never restore system apps or settings. Use Titanium only to restore user apps and xml backups of wifi passwords, call log and sms messages.
The steps to install the new ROM will not erase your internal storage, but why not make a backup of everything to your PC or an OTG USB Drive.
PHASE 4: Install
- Make sure you have updated TWRP and your bootloader and modem as instructed in phase 1
- Make sure you have all files downloaded from phase 2 in your phone - preferably in external sdcard
- Make sure you have backups!!
- Reboot into Recovery (TWRP)
- Use advanced wipe to wipe System, Data and Cache
- Flash RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip
- DO NOT WIPE ANYTHING
- Reboot System (be patient - it will take a while, around 3-4 minutes)
- Pick your preferred launcher
- Check Settings->Date & Time and make sure it is ok
- Reboot into Recovery (TWRP)
- Flash [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
- Flash Magisk-v16.0.zip
- Flash open_gapps-arm-7.1-pico-20180311.zip (or the one you prefer)
- DO NOT WIPE ANYTHING
- Reboot System (this time it will be faster)
- Go to Settings->Accounts and add your google account
- Customize your other settings
- Run Magisk Manager and check if SafetyNet passes
- If not disable/reenable "Magisk Hide" option in Magisk Manager Settings and try again
- Restore/install apps/data
- PROFIT!
[Reserved]
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
tarkzim said:
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
Click to expand...
Click to collapse
Sorry, you are absolutely right.
Thanks for being cool with it.
The main point in changing the rom zip is removing the magisk manager system app. It is a little tricky for noobs to remove the system app to be able to install the v5 beta Magisk Manager.
And thanks again for making your fantastic RR build available.
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
sperug said:
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
Click to expand...
Click to collapse
This does not happen in my phones.
In my work phone I have 600+ apps installed. It takes a while to open but no crashes.
If you post a logcat I may be able to help.
I reinstalled everything, and before made a full wipe, also of the internal storage. And the problem was no more present! Wow! And thank you again...
I checked AFH and have 30+ downloads of installation files.
Any more success or failure cases? Please let me know.
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
BobbyKa said:
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
Click to expand...
Click to collapse
AFAIK it should work for you no matter where you are.
I live in Rio de Janeiro, Brasil and use it.
If it does not work for you just flash another one.
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
BobbyKa said:
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
Click to expand...
Click to collapse
To use Sammy Spen apps/features you need a Touchwiz based stock rom.
There are some apps with similar features for AOSP roms.
Many users say the best is SPenCommand developed by @emandt. It is paid but users say that the app is well worth the price.
Check the SPenCommand Google+ Comunity.
Great post. I don't see google assistant working, any clue?
Sent from my Pixel using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:10 PM ----------
Please ignore, I installed nano gapps and it worked
Sent from my Pixel using Tapatalk
what about battery life ?
has anyone tried this on Sprint Note 3 sm-n900p ?
svbarbosa said:
Check the SPenCommand Google+ Comunity[/URL].
Click to expand...
Click to collapse
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
BobbyKa said:
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
Click to expand...
Click to collapse
I have never used SPenCommand myself. Just read good things about it many times in other threads. Try to search and get help from people who are using it.
You may also check these apps: Note Buddy (S Pen Helper) and CM S Pen Add-on(ROOT).
And this guide on them: The Ultimate S Pen Customization Tool for Your Galaxy Note 3.
But be advised that I have no experience using these apps. Just found them using google.
opexblue said:
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
svbarbosa said:
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
Click to expand...
Click to collapse
Thank you for fast response. I will try other kernel.
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.- Don't worry about taking the battery out when the tutorial says to.- If you have issues with the driver provided in the download, try these. (Run dpinst.exe) - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Kernel Source: here
Just yesterday I've dusted off this tablet, and so I was browsing the forums to see what rom I can put inside, and lickily, about the same time this thread was created! Installing it right now, gonna post a follow-up once I'm finished tinkering with it.
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
LukaHM said:
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
Click to expand...
Click to collapse
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
SaberShip said:
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
Click to expand...
Click to collapse
Haha, I've turned the damn thing over, looked at the sensor, and you're right. Havent actually used this device previously to know about it, so glad we have that one sorted out!
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
Click to expand...
Click to collapse
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
Click to expand...
Click to collapse
What app are you using? I have not seen any issues with downloading yet. If you see 10.43Gb it sounds like your internal storage is formatted correctly. I haven't seen any download issues with Firefox and ES-File Explorer.
Unable to flash firmware - because unable to install Android USB driver on Windows 10
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Main post updated with signed drivers. Please try it now.
Thank you @SaberShip!
The installation of Resurrection Remix 5.8.5 was successful after installing the signed Android USB driver!. System is stable and fast. Thank you again.
App issues:
1. Netflix app (not available on playstore, but at netflix web site) works online, but does not allow video downloads.
Netflix diagnostic error for download is OF.NA.4 -which probably means device does not meet security requirements. ? any workarounds?
// Amazon Prime video works, with offline video downloads as well. Google chrome works. Tried other apps as well.
Documentation issues (minor):
1. "- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)" --> Google Apps Super package did not install since the device ran out of space (error 70). Google Apps "Nano" worked.
System issues:
1. Wifi still does not auto-reconnect after Wireless Access Point is rebooted, but given that this has happened with different ROMs I am concluding it is due to a hardware issue with this device (and not ROM specific).
// Skype camera issue fixed. Camera image is NO longer upside down.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Netflix app not working on ROM due to Widevine DRM
Great job on the ROM!! - it is fast and stable.
I have been investigating why the <latest> Netflix app with offline download capability does not work with Resurrection Remix 5.85 ROM.
I found that some other ROM has similar problem, and it was caused because Widevine DRM was not supported. Netfix (latest app and offline download) started working after Widevine DRM support was added to that ROM.
Is it possible to support Widevine DRM in this ROM?
Here is the quote from another ROM:
"Quote:
Originally Posted by Federek
I recently found out the reason why after opening the Netflix app it shows the error "this app is not compatible with your device". The only workaround right now is to download an old APK directly from Netflix website (it doesn't support the feature of downloading movies). After some digging, I'm pretty sure the error is due to the fact that on, I think any Oreo rom available for bacon, Widevine Drm is not supported (as u can see in the screenshot below). I think it's connected to the files in the screenshot below, but I didn't manage to find a solution. I believe it must be implemented by someone directly in the rom code (I'm absolutely not an expert). I'm also sure it's not connected with root or anything else (the Netflix app is available in the play store for me).
(sorry is my first post)
[/IMG]"
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe) - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected] I'd be grateful for any pointers you might have.
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
jfaheyfan said:
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected]. I'd be grateful for any pointers you might have.
Click to expand...
Click to collapse
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
Catfish78 said:
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
Click to expand...
Click to collapse
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
SaberShip said:
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
Click to expand...
Click to collapse
Thanks for your answer. If only i could do something like that of my own... i have so much interests, i don't know if i could learn that in a usefull time!
By the way, why did you call it "old"? i'm using the Galaxy S2 build 2011, with LineageOS 16. I think this is an old device , like my Galaxy Tab 1 and 2.
But anyway, thanks for your work. After some time i'll write again about issues i found, if it will be helpful.
Regards
Thank you, SaberShip. It's been on my list to get a DD-WRT enabled router, so maybe now's the time.
I've had no problems with WiFi.
If you build an updated Oreo ROM, I volunteer to test it. I'm fond of my A7600-F.
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe)
- Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time
- Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
Does usb otg work?
thierry_w said:
Does usb otg work?
Click to expand...
Click to collapse
Just tested, It works perfectly with my USB wireless Keyboard and mouse combo.
When I tried a USB flash drive it did not mount automatically, however "SDA" does appear in the /dev/block/ directory so you can likely mount the flash storage manually with some terminal commands. YMMV
USB OTG works with both my wired and wireless trackballs (Logitech).
I mount/unmount flash drives with StickMount and explore them with Total Commander.
excellent. Works very well