Related
EDIT: Problem is resolved. After I learn very much:
I made a video, cause there is no helpful video with Safestrap 4. Only with Version 3 and this way is wrong now!
I also write a blog about that helpful storry and links that will help other's.
Hello,
i started to root my Apollo 8.9/LTE with Tutorials from here and a translation in german. I live in germany.
http://www.android-hilfe.de/thema/r...r-kindle-hdx-8-9-apollo-fire-os-4-5-2.693547/
http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
Root Tool
Thats what i do
Rollback to OS 3.2.8 was great
Update to 4.5.2 was also ok
I rootet my Apollo, it works - i tested it
After that i renamed the DeviceSoftwareOTA.apk from Kindle in the priv-app
Now i copied all needed GAPPS files to the system Folder except the descripited
After that i restart my Apollo and now the Problems start
After restart
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Folder with Images
The Google Assistent start immediately after restart
I have to choise a Language but there was no german
Also i had no WIFI Connection, so the Assistent start the Option to connect with WIFI
This work, but at the wifi there is a X and in the Assistent i habe no Internet connection
I use my SIM Card to get a internet connection (This work) but the Assistent need a WIFI
Also i lost my root and get Denied when i try to copy/change with a older version befor April 15 or delete the GAPPS Files in the system Folders
I can start/install Apps with apk, at the apollo i only can use the settings. I have no menu or keys
Thats what i tried
I can use adb and install ES Datei Explorer or SuperSu
I used KingRoot, it dosn't work
I copied the mod Rollback to 3.2.8 bin File in the root folder, but Apollo dont use this file, maybe cause i renamed the OTA Systemfile
I made a reset of the Apollo, but the google Assistent is in the systemfiles and start even after a reset
My Apollo
Has Fire OS 4.5.2
The DeviceSoftwareOTA.apk is renamed
I only can Read NOT Write in the system folders
I can use adb and connect to the Apollo
I tried so much the last 2 days so i hope you got a hint for me.
Gatam77 said:
Hello,
i started to root my Apollo 8.9/LTE with Tutorials from here and a translation in german. I live in germany.
http://www.android-hilfe.de/thema/r...r-kindle-hdx-8-9-apollo-fire-os-4-5-2.693547/
http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
Root Tool
Thats what i do
Rollback to OS 3.2.8 was great
Update to 4.5.2 was also ok
I rootet my Apollo, it works - i tested it
After that i renamed the DeviceSoftwareOTA.apk from Kindle in the priv-app
Now i copied all needed GAPPS files to the system Folder except the descripited
After that i restart my Apollo and now the Problems start
After restart
Google Folder with Images
The Google Assistent start immediately after restart
I have to choise a Language but there was no german
Also i had no WIFI Connection, so the Assistent start the Option to connect with WIFI
This work, but at the wifi there is a X and in the Assistent i habe no Internet connection
I use my SIM Card to get a internet connection (This work) but the Assistent need a WIFI
Also i lost my root and get Denied when i try to copy/change with a older version befor April 15 or delete the GAPPS Files in the system Folders
I can start/install Apps with apk, at the apollo i only can use the settings. I have no menu or keys
Thats what i tried
I can use adb and install ES Datei Explorer or SuperSu
I used KingRoot, it dosn't work
I copied the mod Rollback to 3.2.8 bin File in the root folder, but Apollo dont use this file, maybe cause i renamed the OTA Systemfile
I made a reset of the Apollo, but the google Assistent is in the systemfiles and start even after a reset
My Apollo
Has Fire OS 4.5.2
The DeviceSoftwareOTA.apk is renamed
I only can Read NOT Write in the system folders
I can use adb and connect to the Apollo
I tried so much the last 2 days so i hope you got a hint for me.
Click to expand...
Click to collapse
Nice post; well documented.
You made some serious mistakes (come back to that later) and have a challenge ahead recovering your device. Based on others experiences there is some type of conflict between gapps and the stock launcher. That is probably why you are not seeing soft buttons, keyboard, etc. The only known solution is to temporarily use a different launcher to regain control of your device long enough to reroot. Problem is your device will revert back to the stock launcher on a number of different events including pressing the home key which frequently doubles as 'back' on FireOS. You then have to reinstall the non-stock launcher or find some way to make FireOS treat it as primary.
General overview:
- grab a copy of Nova or Apex (other launchers will probably work too)
- install via 'adb install' (research if unfamiliar)
- if all goes well you should regain temporary use of soft buttons and keyboard
- stay away from home key if possible as it will immediately restore the compromised stock launcher
- attempt to reroot your device with Kingroot. This should be safe given OTA is blocked. You many need to install Kingroot via adb. Once launched Kingroot needs an internet connection to do its magic; hopefully it will pick that up via your sim card
- you can also try rooting with CVE-2014-4322 exploit.
Once you are rooted there are several paths that can be pursued. Since you have a LTE device installing Safestrap and a different ROM probably isn't the best option. Nor is reinstalling gapps on FireOS as you will face an ongoing series of battles (conflicts) between Amazon and Google frameworks. You may need to roll back and upgrade again to fully resolve the launcher conflict.
Discussion for a different post. See if you can get rooted first.
Davey126 said:
You made some serious mistakes (come back to that later)
Click to expand...
Click to collapse
maybe you mean in a later post. Or do you mean, that i crash some Fire OS Framework with the GAPPS framework
Davey126 said:
Apex
Click to expand...
Click to collapse
I take Apex, i am familar with it.
Davey126 said:
You many need to install Kingroot via adb. Once launched Kingroot needs an internet connection to do its magic
Click to expand...
Click to collapse
i install kingroot 4.1 allready on the Apollo and also the software in my pc. Then i start the windows software but root didn't work. - Maybe because i dont have a internet connection on the Apollo??
Davey126 said:
you can also try rooting with CVE-2014-4322 exploit.
Click to expand...
Click to collapse
I used the cve20147911.apk from here (it work one time, bevor the GAPPS), but i try this one.
Davey126 said:
You may need to roll back and upgrade again to fully resolve the launcher conflict.
Click to expand...
Click to collapse
I couldn't rollback now. Is the reason that i dont have root?
Gatam77 said:
I couldn't rollback now. Is the reason that i dont have root?
Click to expand...
Click to collapse
You can't change FireOS versions because you previously blocked OTA by renaming DeviceSoftwareOTA.apk. This file is required to perform rollbacks/upgrades. You will need to obtain root permissions to restore the original filename.
Davey126 said:
You can't change FireOS versions because you previously blocked OTA by renaming DeviceSoftwareOTA.apk. This file is required to perform rollbacks/upgrades. You will need to obtain root permissions to restore the original filename.
Click to expand...
Click to collapse
OK. With this file the update Start. But befor the Update load from amazon Website this takes first a look on the SDCard. Wright?
Gatam77 said:
OK. With this file the update Start. But befor the Update load from amazon Website this takes first a look on the SDCard. Wright?
Click to expand...
Click to collapse
After enabling OTA put your device in airplane/flight mode to prevent updates from downloading. Make sure your device is stable (starts/functions normally) before attempting a rollback/update. I also advise allowing your device to upgrade to 4.5.5 (you will loose root) and then restart the rollback procedure from there.
Davey126 said:
Nice post; well documented.
You made some serious mistakes (come back to that later) and have a challenge ahead recovering your device. Based on others experiences there is some type of conflict between gapps and the stock launcher.
Click to expand...
Click to collapse
Thx for your words.
I installed a launcher and restart but also had no buttons. But a other way was it.
I GOT IT!!
I dont have permission on system folder with ES Datei Explorer, but now i use adb.
I found a post here how to change permission with adb
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Now i rename the file with mv MYNAMEOFOTA to DeviceSoftwareOTA.apk
After i used the gifroot Files But i got a message that it wouldnt work with this kernel.
So i dont know exactly which way was it.
But now to my serious mistakes. Can you tell me please what you mean? Cause I love this amazon hardware but I hate the amazon Fire OS and i love GMail, sheets, Maps, and other good apps from Google. So i need root.
All works bevor i push the GApps. So what is the better way. I know I have to read much more bevor i start again. Cause the Apollo is tricky.
I wait for a answer of you bevor i rollback to 3.2.8. I can wait.
Gatam77 said:
Thx for your words.
I GOT IT!!
I dont have permission on system folder with ES Datei Explorer, but now i use adb.
I found a post here how to change permission with adb
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Now i rename the file with mv MYNAMEOFOTA to DeviceSoftwareOTA.apk
After i used the gifroot Files But i got a message that it wouldnt work with this kernel.
So i dont know exactly which way was it.
But now to my serious mistakes. Can you tell me please what you mean? Cause I love this amazon hardware but I hate the amazon Fire OS and i love GMail, sheets, Maps, and other good apps from Google. So i need root.
All works bevor i push the GApps. So what is the better way. I know I have to read much more bevor i start again. Cause the Apollo is tricky.
I wait for a answer of you bevor i rollback to 3.2.8. I can wait.
Click to expand...
Click to collapse
Congratulations! Glad you were able to make some progress. Unfortunately, you are not out of trouble yet. Do not change permissions on any other files as FireOS is very sensitive and sometimes will not start if permissions are not as expected. Especially on 'system' files and folders.
Two concerns with the approach you took:
- using an outdated mod guide not published on XDA. Some of the techniques are old or no longer recommended
- attempting to install GApps on FireOS. Amazon and Google frameworks do not play nice together. While some have got it to work acceptably there are almost always problems, some quite serious.
A better approach is to use a twrp (recovery) emulator called Safestrap. Once installed you can install a limited selection of high quality ROMs that offer full access to the Google Play store. You may be familiar with the names: Nexus and CM11. They essentially turn your Kindle into a generic android tablet. You can even use native Amazon apps like Kindle reader.
The downside is LTE is not well supported by these roms. If you use your tablet off WiFi and need LTE then you have a tough decision to make:
1) Forgo LTE in favor of a rom with full Google Play access
2) Retain LTE and FireOS with limited access to Google services and apps
You don't have to make that decision now. First step is to rollback to 3.2.8, upgrade to 4.5.2, obtain root and block OTA. In a previous post I suggested upgrading to 4.5.5 first. I am stepping away from that suggestion to streamline the process. However, there is additional risk going from 4.5.2->3.2.8 because if anything goes wrong you could end up bricking your device. Going from 4.5.2->4.5.5 is less risky but adds another step.
There are many posts on XDA detailing the rollback/upgrade/root/blockOTA/Safestrap/rom process. Start here and spend some time reading. I did not pick this thread because it was the 'best'; just one I happen to remember contributing to in recent days. But it will lead you to other helpful posts that lead to even more posts ...
As always:
- ask questions if unsure; never assume or guess
- keep WiFi off (airplane/flight mode engaged) to prevent OTAs when upgrading or rolling back. Consequences are large: an OTA can (and likely will) permanently brick your device.
- make sure you fully understand the procedures, expected outcomes and recovery options if things go wrong
- only use files posted on XDA (links ok too)
- a fresh mind helps; take a break when tired. Your device will wait.
Good luck.
Davey126 said:
Two concerns with the approach you took:
- using an outdated mod guide not published on XDA. Some of the techniques are old or no longer recommended
- attempting to install GApps on FireOS. Amazon and Google frameworks do not play nice together.
The downside is LTE is not well supported by these roms. If you use your tablet off WiFi and need LTE then you have a tough decision to make:
1) Forgo LTE in favor of a rom with full Google Play access
2) Retain LTE and FireOS with limited access to Google services and apps
As always:
- ask questions if unsure; never assume or guess
- a fresh mind helps; take a break when tired. Your device will wait.
Good luck.
Click to expand...
Click to collapse
The again a lot.
I need my Mobile Internet. Not really LTE but at least 3G! But LTE get better here in Germany so it would be nice.
I like CM. I already flashed my Samsung S3, my wife S3 Mini, and my 2 Amazon's Tate.
That's why I bought the Apollo and hope after 1 year or so there will be a custom ROM with LTE working. So if someone interested I will flash a Custom Rom, life a time without Mobile Internet and help the developer with sending log files, or other needed things.
No I started reading! But I will post again here that other can read and learn from my mistakes.
Gatam77 said:
The again a lot.
I need my Mobile Internet. Not really LTE but at least 3G! But LTE get better here in Germany so it would be nice.
I like CM. I already flashed my Samsung S3, my wife S3 Mini, and my 2 Amazon's Tate.
That's why I bought the Apollo and hope after 1 year or so there will be a custom ROM with LTE working. So if someone interested I will flash a Custom Rom, life a time without Mobile Internet and help the developer with sending log files, or other needed things.
No I started reading! But I will post again here that other can read and learn from my mistakes.
Click to expand...
Click to collapse
FYI - you can find the Safestrap compatible CM11 rom thread here. As I recall some aspects of LTE/3G work ok. Skim through the posts for more detail. Might be a non-issue for your needs.
Davey126 said:
You don't have to make that decision now. First step is to rollback to 3.2.8, upgrade to 4.5.2, obtain root and block OTA. In a previous post I suggested upgrading to 4.5.5 first. I am stepping away from that suggestion to streamline the process. However, there is additional risk going from 4.5.2->3.2.8 because if anything goes wrong you could end up bricking your device. Going from 4.5.2->4.5.5 is less risky but adds another step.
Click to expand...
Click to collapse
After i was short befor to brick my Apollo, maybe I would first Going from 4.5.2 > 4.5.5 and then 3.2.8 > 4.5.2.
But i dont read a hint with a link to 4.5.5. Can I download ist from here Davey?
Also i take a look in my router and he block some IPs when I used Kingroot on my PC yesterday.
14.17.41.155
202.77.59.49
163.177.71.157
120.198.203.149
103.7.29.30
They come from Hongkong and Bejiing. Is it possible that that was the reason Kingroot couldn't root my Apollo?
Gatam77 said:
After i was short befor to brick my Apollo, maybe I would first Going from 4.5.2 > 4.5.5 and then 3.2.8 > 4.5.2.
But i dont read a hint with a link to 4.5.5. Can I download ist from here Davey?
Also i take a look in my router and he block some IPs when I used Kingroot on my PC yesterday.
14.17.41.155
202.77.59.49
163.177.71.157
120.198.203.149
103.7.29.30
They come from Hongkong and Bejiing. Is it possible that that was the reason Kingroot couldn't root my Apollo?
Click to expand...
Click to collapse
I can't speak to what IPs Kingroot uses. There have been various reports of it being slow or temporarily not working. Perhaps due to network congestion. Usually clears up after a few hours.
If you have restored DeviceSoftwareOTA.apk you can simply enable WiFi (disable airplane/flight mode) and allow the device to receive an OTA and self-update to 4.5.5. This is actually a good test OTA functionality is working which is also required for manual rollbacks/upgrades.
There is another option that does not involve rollbacks/upgrades: If you can obtain root you can then attempt to install Safestrap v4 followed by CM11 or Nexus v4 (you can also 'repair' FireOS using this method). Both Kingroot and Safestrap require interactive access. You don't need to type anything (so keyboard doesn't need to display), just tap an on-screen button or two. You would need to install apks via adb and then have enough control over your device to launch the app. Not easy or intuitive.
I will caution there is risk with either path (upgrading FireOS or installing Safestrap on a dysfunctional device). You have to weight the risks and take the course the feels most comfortable. There are no guarantees.
Reminder: do not do a 'factory reset' from the native recovery menu unless recommended by an experienced contributor, especially after rooting or installing Safestrap.
Now all is ok again. I am so joyful.
First Download Safestrap from here
Downloaded and Follow the instructions here
Now i can start with a new and clean Android on a good Amazon Hardware
Installed Safestrap on my damaged Fire OS 4.5.2
Than install a recovery in the Safestrap APP
After that i made a slot with 1200 System/1500 Data/1000 Cache
Active the slot
go into Wipe Menu and Swipe to perform a factory reset
Go in the Install Menue and install CM11, GAPPS and SuperSu
Now i started in CM11
Again thx to Davey126.
My stock ROM is still the damaged where I mixed amazaon and google framework. What can i do?
Active the Stock slot, start into my damaged Fire OS
Push with adb a Fire OS 4.5.5 to the sdcard
Or make a OTA over the WLAN from amazon?
Or (in the video says: NEVER touch the stock at Safestrap) Install a Fire OS bin in Safestrap to witch slot?
Gatam77 said:
Now all is ok again. I am so joyful.
First Download Safestrap from here
Downloaded and Follow the instructions here
Now i can start with a new and clean Android on a good Amazon Hardware
Installed Safestrap on my damaged Fire OS 4.5.2
Than install a recovery in the Safestrap APP
After that i made a slot with 1200 System/1500 Data/1000 Cache
Active the slot
go into Wipe Menu and Swipe to perform a factory reset
Go in the Install Menue and install CM11, GAPPS and SuperSu
Now i started in CM11
Again thx to Davey126.
My stock ROM is still the damaged where I mixed amazaon and google framework. What can i do?
Active the Stock slot, start into my damaged Fire OS
Push with adb a Fire OS 4.5.5 to the sdcard
Or make a OTA over the WLAN from amazon?
Or (in the video says: NEVER touch the stock at Safestrap) Install a Fire OS bin in Safestrap to witch slot?
Click to expand...
Click to collapse
Excellent - glad to hear the progress!! However, there are some important changes needed that will greatly improve your CM11 experience (battery life, performance, stability). Some of this contradicts information in the video and recommendations from other versions of Safestrap.
The use of secondary slots is not recommended in Safestrap v4:
WiFi only works with CM11; Nexus v4 and Stock FireOS will fail to make a connection
Only 2 of 4 CPU cores are utilized resulting in poor performance under load
CPU runs at maximum speed at all times (no throttling) resulting in high battery use when idle
GPU does not throttle
Device never enters 'deep sleep'; radios remain active at all times
Backups can not be migrated between slots; flashing a secondary slot backup to the stock slot will brick device
Slot storage must be allocated in advance and can not be adjusted (must delete/recreate/reflash rom)
Recommended path:
Delete secondary slot (this will destroy your CM11 installation)
Flash CM11, GApps, SuperSu in stocki slot; this will overwrite FireOS in stock slot
This means your device will be running CM11 with no access to FireOS. However, if needed you can replace CM11 with FireOS 4.5.2 from this thread. Note the images are customized for Safestrap; flashing a unmodified stock image will brick your device.
Miscellaneous:
NEVER perform a 'factory reset' from the native recovery menu; your device will brick
Make a backup of the stock slot from within Safestrap (it will be large); move to a host PC for safe keeping
Always keep a flashable copy of CM11 image on the device (in the root of sdcard) for emergency recovery. Safestrap v4 can not communicate via wifi, bluetooth or tether. If CM11 fails to boot your only option is to reflash an OS (CM11, Nexus or FireOS) from within Safestrap recovery. If a Safestrap compatible/flashable image is not already on the device you can not recover from this type of failure.
Safestrap may appear to be a full blown recovery but it is actually a TWRP emulator that runs within the system partition and has dependencies on other Amazon components (bootloader, native recovery, etc) that remain on your device from the previous FireOS 4.5.2 installation. Be careful with advanced tools that run at a low level. It is possible to 'damage' your device to an extent that it can not be recovered. Ask first if uncertain.
questioning asking
This is so interesting. So sorry for my allways following questions. You said I should ask, but maybe also other can have a answer for me. This also cost your time.
So if you can't answer its ok. Or if there are only some hint words that will be a help for me to find out more. Whatever.
I am more than thankfull for that help to find out more about Android.
Davey126 said:
However, there are some important changes needed that will greatly improve your CM11 experience (battery life, performance, stability). Some of this contradicts information in the video and recommendations from other versions of Safestrap.
Click to expand...
Click to collapse
Ok, a next thing that i can search for.
I see some of my Apps close very often. Special Play Store
Davey126 said:
Delete secondary slot (this will destroy your CM11 installation)
Flash CM11, GApps, SuperSu in stocki slot; this will overwrite FireOS in stock slot
Click to expand...
Click to collapse
With secondary slot you mean the ROM Slot 1, cause the Stock will be the first slot maybe?
I don't will go back to the Fire OS cause i have a Fire TV Stick and a Raspberry for that. If i still think so in some months i also can flash the Stock Rom with a CM Image? But its not necessary cause i have my CM11 or maybe in the future CM13 in the ROM Slot 1. Or are they more reasons for that step?
Davey126 said:
NEVER perform a 'factory reset' from the native recovery menu; your device will brick
Click to expand...
Click to collapse
Whats do you mean special with "native recovery"?
That i start with the StockRom into my FireOS and after that i make a factory reset?
Davey126 said:
[*] Always keep a flashable copy of CM11 image on the device (in the root of sdcard) for emergency recovery. Safestrap v4 can not communicate via wifi, bluetooth or tether. If CM11 fails to boot your only option is to reflash an OS (CM11, Nexus or FireOS) from within Safestrap recovery. If a Safestrap compatible/flashable image is not already on the device you can not recover from this type of failure.
[/LIST]
Click to expand...
Click to collapse
I will do this! But...
I dont know, at this time, so much from safestrap. But i take look in it, and i can use ADB Sideload, Mount a USB Storage. Maybe also to reboot into the Download.
Is a push from adb or a Backup on a USB not also a way to restore a damaged Custom ROM.
Like
Start into Safestrap
Wipe my Slot with the CM11 or delete ist and create it again
Push with adb a new file of CM11, GApps, SuperSu into my data permission
And after that flash it to the Data Partition
Davey126 said:
[*] Safestrap may appear to be a full blown recovery but it is actually a TWRP emulator that runs within the system partition and has dependencies on other Amazon components (bootloader, native recovery, etc) that remain on your device from the previous FireOS 4.5.2 installation. Be careful with advanced tools that run at a low level. It is possible to 'damage' your device to an extent that it can not be recovered. Ask first if uncertain.
[/LIST]
Click to expand...
Click to collapse
How i can find out what Low Level tools are?
I think a recovery like TWRP is one.
I also use Tasker or BusyBox. They can make also deep things on my system. Also Low Level?
When ends the Low Level and start the Deep System?
Gatam77 said:
With secondary slot you mean the ROM Slot 1, cause the Stock will be the first slot maybe?
Click to expand...
Click to collapse
Yes - delete all ROM slots (1-n) that you created. Bottom line: you only want to use the Stock slot.
Gatam77 said:
I don't will go back to the Fire OS cause i have a Fire TV Stick and a Raspberry for that. If i still think so in some months i also can flash the Stock Rom with a CM Image? But its not necessary cause i have my CM11 or maybe in the future CM13 in the ROM Slot 1.
Click to expand...
Click to collapse
You do not want to maintain multiple slots (ROM images) in Safestrap v4. When you switch ROMs you overwrite the existing ROM in the Stock slot. You can overwrite CMxx with FireOS. At present CM12 and CM13 are not compatible with Safestrap v4. Do not attempt to flash any ROM image other than those specifically listed as "Safestrap Compatible".
Gatam77 said:
Whats do you mean special with "native recovery"?
Click to expand...
Click to collapse
"Native recovery" is the one supplied by Amazon accessible via <power> + <vol-up> from a cold start. NEVER use the 'factory reset' function from this menu when Safestrap v4 is installed; your device will brick.
Gatam77 said:
I dont know, at this time, so much from safestrap. But i take look in it, and i can use ADB Sideload, Mount a USB Storage. Maybe also to reboot into the Download. Is a push from adb or a Backup on a USB not also a way to restore a damaged Custom ROM.
Click to expand...
Click to collapse
None of these features work with Safestrap. Think of Safestrap as a virtual machine with ROMs running inside (technically inaccurate but conceptually convenient). You can only make full use ADB after portions of the ROM are up and running. If the ROM is damaged/unbootable you must do all repairs from within Safestrap. At present Safestrap v4 can not communicate with the outside world; all repair tools/images must be 'on board' (preloaded).
Gatam77 said:
Start into Safestrap
Wipe my Slot with the CM11 or delete ist and create it again
Push with adb a new file of CM11, GApps, SuperSu into my data permission
And after that flash it to the Data Partition
Click to expand...
Click to collapse
Probably repetitive but you do not want to recreate ROM Slot 1. Delete it and then flash CM11 (or Nexus v4 or FireOS) to the Stock slot.
Gatam77 said:
How i can find out what Low Level tools are?
I think a recovery like TWRP is one.
I also use Tasker or BusyBox. They can make also deep things on my system. Also Low Level?
Click to expand...
Click to collapse
- You can not use 'native' TWRP on your system as the bootloader is locked and can not be unlocked. Safestrap emulates TWRP.
- Tasker and BusyBox are fine
- Be careful with Xposed modules or other 'tweaks' that might cause your device to become unbootable.
Bottom line: enjoy CM11 and the apps that can be installed from the Play Store. Resist the temptation to customize further. If your device freezes or becomes unbootable you may not be able to recover.
Davey126 said:
Yes - delete all ROM slots (1-n) that you created. Bottom line: you only want to use the Stock slot.
Click to expand...
Click to collapse
Short Post
Oh my god. Again I trust a old Video. More later
So i install again.
First i make a backup (over WLAN) from my Stock Rom. I didn't get connection over USB at my PC neither connect a USB Stick to the Micro USB Slot. That's may what you mean that Sfestrap works like a virtual mashine.
So i CHECK if all files are at my root folder in the stock
After that i Wipe the Stock Rom
After that Flash all needed files and install like the last time but this time into the Stock Rom
Gatam77 said:
Short Post
Oh my god. Again I trust a old Video. More later
So i install again.
First i make a backup (over WLAN) from my Stock Rom. I didn't get connection over USB at my PC neither connect a USB Stick to the Micro USB Slot. That's may what you mean that Sfestrap works like a virtual mashine.
So i CHECK if all files are at my root folder in the stock
After that i Wipe the Stock Rom
After that Flash all needed files and install like the last time but this time into the Stock Rom
Click to expand...
Click to collapse
Good! Please confirm that you are now running CM11 in the Stock slot.
Assuming 'yes' you can (and should) remove all other slots if still present. Benefits:
- recover 3-4 Gb of permanent storage on your device and return it to the stock slot
- avoid potential confusion while in Safestrap recovery which could possibly lead to a bricked device
Once everything is stable boot into CM11 and move the large backup files to a host via tether (fastest), WiFi or Bluetooth. You do not need to keep backups on your device for recovery purposes; only the smaller ROM image.
You can not attach a flash/thumb drive or any other USB device (including keyboards/mice) to the micro-USB port as HDX devices lack OTG support at the hardware level. An unfortunate design choice by Amazon and can not be fixed via software or special cables.
Keep in mind the HDX is a sensitive device. After flashing a ROM there rarely a need to return to the Safestrap recovery environment. Exceptions:
- flash a newer version of ROM (release release notes carefully)
- make periodic backups of your existing system and data partitions
Davey126 said:
Good! Please confirm that you are now running CM11 in the Stock slot.
Click to expand...
Click to collapse
I will do. At the moment it is still in Slot 1 and i recharge battery to 100%.
Maybe tomorrow . Because there is no video with this, i try to make a movie while making all this steps.
Assuming 'yes' you can (and should) remove all other slots if still present. Benefits:
- recover 3-4 Gb of permanent storage on your device and return it to the stock slot
Click to expand...
Click to collapse
So i Flash my CM11 to the Stock Rom. And AFTER That i remove the other Slots.
After that I can recover storage back to the Stock ROM?
You do not need to keep backups on your device for recovery purposes; only the smaller ROM image.
Click to expand...
Click to collapse
After all works with the Custom Rom on the Stock Rom, i leave the ZIP file on my device after the flash. All other like GAPPS i also can thether later, if i need this again.
Gatam77 said:
So i Flash my CM11 to the Stock Rom. And AFTER That i remove the other Slots.
After that I can recover storage back to the Stock ROM?
Click to expand...
Click to collapse
Correct. Although the goal is to delete all secondary (non-stock) slots there is no benefit to removing the slot that is currently hosting CM11 until you have confirmed the reflash of CM11 to the stock slot. This leaves you with a working ROM should something go wrong.
An 'idle' secondary slot does not present a problem just being there. However, it consumes considerable space and increases the possibility of making a fatal mistake while working in Safestrap recovery. Ultimately the decision is yours whether to keep or discard secondary slots. However, you want your primary slot to be stock. Hope this makes sense.
Gatam77 said:
After all works with the Custom Rom on the Stock Rom, i leave the ZIP file on my device after the flash. All other like GAPPS i also can thether later, if i need this again.
Click to expand...
Click to collapse
Correct.
Want to update to CM13? Read this first!
Welcome to my upgrade guide that will allow users to painlessly upgrade from an earlier version of android to CM13.
Background info:
Our Cyanogenmod maintainer, Lysergic Acid, started bring alpha builds of Cyanogenmod 13 since October of last year. Now, we have official nightlies on our device which just proves how strong of a device we have and how strong we are as a community on XDA. With all of the exciting new features Marshmallow brings to the table, people have been flashing CM13 without reading any precautions or information about the possible consequences of not doing a particular step or procedure. With this guide, you will learn how to successfully flash CM13 on a device, everytime!
This guide will assume you are on a rooted custom ROM with a working custom recovery. It will not guide users how to update from stock ROM to CM13. If you haven't rooted your phone yet or are on stock ROM, use a different guide to install a rooted custom ROM (KK or LP preferred) then follow this guide.
Another important tip is to read the issues post before flashing the latest build of CM13. There could be issues that you could encounter so make sure to read before flashing!
How to install:
CM13 is available to install for CM12.1 users via the OTA updater. However, updating to CM13 via OTA updater is buggy and will remove gapps and Isorec Recovery. If you receive notifications about the CM13 update, don't use the OTA updater! Use this guide below instead.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the upgrade process or you don't like CM13 in general. If you are using Cyanogen recovery from CM12.1, you should flash a isorec recovery from this thread. TWRP or CWM are both fine. Note: If you are using a build earlier than 20160119 nightly or not using one of Lanchon's isorec kernels, you will not be able to use a isorec recovery. This will not apply to people on older versions of android (for older versions of android, KK compatible recovery or higher is all you need).
If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section. It is required for users to re-partition their system partition to 1GB to prevent issues when flashing gapps. Please also note that when upgrading from an older ROM, you must flash a newer Gapps to keep Gapps on your phone.
Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
If you are in CWM, while on the main menu, choose factory reset. Then go into mounts and storage and select format system. If you are in TWRP, go into the wipe menu, select advanced wipe, check wipe system, data and cache, then swipe the bar to wipe.
Flash the CM13 zip.
(Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
(Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken.
I will repeat what I said earlier but with more explanation. Why don't I have a guide on how to update to CM13 via OTA? OTA update from CM12.1 to CM13 is broken! You will lose gapps and it will cause a lot of problems to user. Just follow the above guide to flash update manually and no issues will be encountered.
Gapps on Android Marshmallow:
Recommended Gapps: OpenGapps Pico
What to select on OpenGapps page: ARM>6.0>Pico
While flashing Gapps is an optional step during the upgrade process, many people require the Google Play store to install all of their apps. It is required for people who want to flash gapps to increase their system partition to 1GB (or more). Stock partition sizes have a system partition size of about 500MB which is not enough to hold even the smallest gapps packages available!
Re-partition guides
You can re-partition your device by following my guide (Requires PC): http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
If you have working recovery, use Lanchon's guide (second link). Otherwise, my guide (first link) will work for everyone else.
Please note that re-partitioning your device via ODIN (first link) will delete all of your data, including your internal storage which contains all of your personal files. You must backup all of your files to an external sd card or PC if you want to keep them! However Lanchon's guide (second link) keeps all of your personal data but requires a working custom recovery!
Please also note about the naming of the zip/pit files!
If you get error 70 while flashing Gapps, make sure you are using the re-partition guides properly, you may have missed a step or forgot to do something. If you didn't bother reading all of the information I've given and decide to post about your error, you will be told to read the information properly and nothing else. All help was given already If you get some other error, read the OpenGapps FAQ.
Stock Cyanogen Recovery:
CM13 Stock Cyanogen Recovery is a basic recovery that allows you to flash zips from your internal and external sd storages. It provides wipe options and ADB flashing support, but was only designed to provide the basic tools for flashing. Although it works fine in recent builds of CM13, it is highly recommended that you use an Isorec Recovery like TWRP.
Update: Cyanogen recovery has fixed mounting support for internal and external sd as of the 5th of October nightlies. The steps below now only apply to people who want to use older CM13 builds.
If you have build 20161005 or later, you can now easily switch to an Isorec recovery simply by flashing it via Cyanogen recovery. You can not do this in older builds!
Isorec install on builds older than 20161005
1. ADB Sideload Method (requires PC)
This is the easiest and quickest method to restore Isorec Recovery on your device. However it will require ADB/Fastboot tools to be installed on your computer. You also need to enable ADB debugging and enable root access for ADB in the development settings to use this method. If you don't have ADB/Fastboot tools installed, download it from this thread
Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
Reboot your phone into Cyanogen recovery
Select apply update from ADB sideload
In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
Select open command line menu here
Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
Cyanogen recovery should begin flashing TWRP recovery
Once completed, reboot your device
2. ODIN method (requires PC)
This method requires ODIN to be installed on your computer. You will be connecting your phone to the computer which may or may not be a problem for some users.
Put your phone into download mode (Power key, home button, Volume Down button)
Connect your phone to your PC
Open ODIN. Make sure that it detects your device. If it doesn't, check if you have the right drivers installed and if the usb cable/port is damaged
Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4 Don't worry if it isn't CM13 kernel, you will have to reflash CM13 anyway! If you don't know which one to choose, the TWRP CM12.1 kernel is fine.
Select the CM12.1 kernel as PDA (or AP)
Make sure you untick auto-reboot
Start the flash.
Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
Get into recovery mode (Volume Up, Power Key, Home button)
Repeat CM13 flashing guide above without any backup.
If you have linux, use JOdin instead of ODIN.
3. Terminal method (Doesn't require PC)
This method requires a terminal emulator. Either download one from the google play store or enable the in-built terminal emulator in development settings. Follow the guide carefully. You can use this method if your USB port is broken.
See Lanchon's post: http://forum.xda-developers.com/showpost.php?p=65164875&postcount=1002
As mentioned in Lanchon's post, IF YOU MAKE A MISTAKE IN ONE SINGLE CHARACTER YOU TYPE IN THE TERMINAL, YOU COULD BRICK YOUR PHONE FOREVER!!!
Root on Android Marshmallow
CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.
You may be familiar with the root tool, SuperSU, and it may have been installed in CM12.1 or earlier versions of android. Android Marshmallow has a different way of rooting the device. It is not compatible with older versions of root.
Currently, SuperSU doesn't work on CM13. Do not attempt to install it with system method and don't try to install it with systemless method.
How to update to a newer build of CM13
1. OTA Updater method
This method of updating Cyanogenmod is usually preferred by many users because it is ready-to-use and is quite simple to do.
Go into settings>about phone>system updates
If there is a new build available, press the download button. The OTA updater will now download the update to your phone
Once it finishes downloading, it will prompt you if you want to install the update. Confirm that you want to update and your phone should restart
Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
2. CyanDelta Update method (Popular method)
This method of updating Cyanogenmod is most beneficial to people who want to save bandwidth and/or want to download the update via their mobile data. This method typically saves around 200MB of data which makes it a quick way of updating, without sacrificing stability.
Download Cyandelta from the google play store
Download from CyanogenMod website the .zip file of the ROM you are using. Please note that if you haven't saved a copy of your current build onto your phone, the Cyanogenmod Downloads server usually deletes old nightlies. Update: The Cyanogenmod downloads page is gone, instead download from here.
Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
If you are stuck using the CyanDelta update method, check out their FAQ on their website.
3. Manual method (Recommended)
If you have issues using the other methods to update CM13, you can also install the update manually via recovery. This method usually has the greatest success rate.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the update process. If you don't have Isorec TWRP or CWM, use the guide above to reinstall CM13 with a working recovery!
Download newer CM13 build from the official cyanogenmod downloads page onto your phone. Note: Old cyanogenmod nightlies are usually deleted from the Cyanogenmod server if you haven't downloaded your current build onto your phone yet. Update: The Cyanogenmod downloads page is gone, instead download from here.
Flash the CM13 zip
Wipe cache
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken. If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
New users are encouraged to post questions about CM13 here and not in the CM13 Development thread, this will leave everyone happy and everyone gets what they want
Thanks to Lysergic_Acid for CM13, Cyanogenmod team, CyanDelta team, arnab for his TWRP isorec recovery, Lanchon for his Isorec kernels, repartition script, Isorec recovery and guides.
Updated on 02/02/17
Since the wiki for our device hasn't been updated yet, here are a list of some issues on CM13:
Issues marked with red are recent issues you will experience in any current build of CM13.
Ongoing issues:
MX Player can not use HW+ decoder. Instead, use HW or SW decoder. The developer of MX player is working on a fix.
Cyanogenmod OTA Updater sometimes can be buggy. MD5 errors, download errors, installation errors. Although it is working fine for most people, I still recommend just to flash manually via recovery!!!
Internal storage and external storage is not labelled correctly and has a random name. This is not a bug but a feature of one of the mounting ways of MM.
Screenrecorder works for some users, however it seems that you can not playback them on your phone. Workaround: Play the videos using your PC.
Some apps may have trouble detecting internal/external storage.
Some bluetooth devices may not behave properly or connect
Multiple issues with F2FS. Please note that this FS is still relatively new for our device so bugs are likely to be experience. Stay on ext4 for best stability!
Some people have reported that they have lost connection to their mobile network. This usually can be fixed by resetting APNs. If this doesn't help, you may need to downgrade back to stock 4.1.2 ROM.
MMS video file (.3pg format) will not play on the default video player. Workaround: Play the video through MX Player on SW renderer.
Hardware button is always on until screen is switched off. Workaround: After installing the BLN MOD and synapse, you can control the timeout values.
You may experience reboots when you receive phone calls
More to be added later
Fixed issues:
(from latest issue solved to earliest)
Cyanogen Recovery can not mount internal and external storage. You can not flash zips via internal or external storage. ADB sideload or other methods of flashing can be used instead. Fixed in nightly 20161005
Battery Percentage Incorrect and Causing Constant Low Battery Warnings. Fixed in nightly 20160818
As of the 20160722 nightly, decryption of /data partition is broken. Keyboard can't be switched to enter digits. Fixed in nightly 20160724
As of the 20160722 nightly, setup wizard is broken. When you press next, the notification bar drops down instead of the next screen showing. Fixed in nightly 20160724
Some people have reported that the youtube app (play store version) displays green lines during playback.
Front camera errors in recent builds
Phone dialer is currently broken Workaround: Use google dialer from Google Play Store
Live lockscreen has multiple issues being experienced in recent builds.
Nightly 20160326 is experiencing Google Play Launcher FCs. Please stay on a earlier build until this is fixed. Fixed in nightly 20160329
People who are using a non-english language may experience Clock app FCs. This problem is under investigation. Update: Fixed in nightly 20160325
Doze feature can not optimize any apps. This is not a bug, doze is disabled on our device! Please ignore this menu! Update: Fixed in nightly 20160325. Note: This is the app standby feature that is now working and not motion sensor doze!
Nightly 20160323 is experiencing CM file manager FCs Fixed in nightly 20160325
Nightly build 20160216 is currently affected by the no signal bug and dialer issues. Update: Calling issues have been fixed in nightly builds 20160218 or newer. If you are on build 20160216, you should update immediately to fix this issue.
FAQ
Q: What is cyanogenmod?
A: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device. CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Q: What version of android is CM13 based on?
A: Android Marshmallow 6.0.1
Q: What is Gapps?
A: Google Apps (Gapps) is an app package containing the Google Framework which is required for most apps from Google to function. This will include the Google Play Store and other Google apps and services depending on what setup you select (it varies on what Gapps package you select, I recommend OpenGapps).
Q: Is this ROM pre-rooted?
A: CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for adb too because this can help you recover from some problems that may occur in the future.
Q: I get error 70 when flashing gapps. What can I do to solve it?
A: Error 70 means that you have insufficient space available in the system partition. Your device does not have sufficient space available in the system partition to install the Open GApps package. As I have said in my guide, you will need to repartition your system partition using one of the links in the gapps installation section of my guide. Then only you will be able to install gapps on your phone.
Q: Help me! My phone says that sdcard0 is corrupted! What can I do to solve it?
A: If you've re-partitioned your device recently using the ODIN method, it is highly likely that you forgot to format your internal sd card. You can do this in the recovery by selecting sdcard0 or internal sd, format as vfat (fat) or default (CWM). Alternatively, you can use your computer to format it manually by mounting your phone's storage via recovery then using a formatting utility such as the built-in windows formatting tool.
Q: Does xyz app work with CM13?
A: I don't know. Check the app's website, check the google play store, check other users comments. Google is your best friend. If not, try it out for yourself! Some apps require selinux to be set to permissive, you can do this in apps like SELinuxModeChanger.
Q: Does SuperSU work on CM13?
A: While there are ways to get SuperSU working, this guide is only here to provide basic procedures. I do not recommend new users to install SuperSU on any Android 6.0 ROM.
Q: My apps that require root say that I need busybox to use the app. What should I do?
A: You do what it tells you to do. Download busybox installer from the app store, install busybox and your app will hopefully work as it should.
Q: What happened to busybox? It was available on older android versions but why do I have to install it myself on CM13?
A: Busybox was replaced with toybox in CM13. As a result, you can not run apps that require busybox so you need to install a busybox installer from the google play store.
Q: Does GPS work well on CM13?
A: Reports have shown that GPS is still not reliable like in CM12.1.
Q: Does CM13 have Isorec Recovery Support?
A: Yes, it does. However CM13 comes with CM recovery as the default recovery.
Q: Does xposed work on CM13?
A: Yes it does. Use the latest installer (xposed-v80-sdk23-arm or newer) and make sure selinux is set to permissive.
Q: Which is better, CM13 or CM12.1?
A: CM13 is still new for our device. Naturally, there will be bugs experienced by users. Over time, the ROM will mature and it will become stable for everyone to use. Try it out for yourself and see which one is best for you
Q: Can I install CM13 on {different S2 model}?
A: If it is just a carrier/region variant of the international s2 i9100, it should work without problems. If it is different physically (hardware), then it will not work!
Q: Battery life sucks on CM13! What happened to doze mode?
A: Our device lacks the (low power) sensors that take advantage of this feature, therefore making it useless so it was disabled. Don't forget our device (s2) is quite old now, it shouldn't be a surprise that we can't take advantage of new features like this.
Q: Battery life sucks on CM13! (General)
A: Download and install betterbatterystats onto your device. Check what app is the culprit to your poor battery life. If there are no apps that are behaving strangely, try reflashing your current ROM and making sure to factory reset and format system partition. A lot of battery problems are created by the user, maybe brightness is set too high, change the screen timeout delay, etc.
Q: Can I update to CM13 without a computer?
A: Yes you can. I have included guides/steps that are not computer dependent if you haven't noticed already. If you have a broken USB port, you need to get it fixed ASAP because if anything happens during the flashing process, your phone is useless!
Q: My device runs slow on CM13. Can I do anything to make it go faster?
A: Make sure to close all apps that are not needed. Change swappiness to a lower value or 0. Change CPU governor parameters: Up threshold, sampling rate. Make these values smaller to give more performance. Remove apps that may be hogging up your CPU/RAM. Reboot, it helps
Q: What does android security patch level mean?
A: Google regularly updates their newer android versions with security fixes. Cyanogenmod will apply those fixes to their ROM so you will stay protected as well.
Q: Why is xyz feature not available in CM13 when it was available in CM12.1?
A: It is a good possibility that Cyanogenmod are not ready to add the feature yet. It could still need more internal testing or other more important features have to be added first for adding it to the ROM.
Q: Why can't I install gapps?
A: Now before you post this, have you read the post given by the users on the CM13 thread? I have said in my guide that in order to flash gapps, you will need a larger system partition. Please re-read the guide and make sure to read carefully before posting questions.
Q: What is BLN?
A: BLN (Backlight Notification) is a feature which uses your phone's hardware button lights to notify you whenever you receive a notification such as SMS, email, etc.
Q: How do I use BLN?
A: BLN is disabled by default. You need to use Synapse to configure it. See this thread
Q: How do I change the behavior of BLN?
A: See this thread
Q: Will BLN drain my battery?
A: BLN (not BLN without wakelock) prevents your CPU from going to deep sleep mode (low power CPU mode to save battery) which will drain your battery quicker versus having it disabled. Lighting up your hardware buttons will also use a little more power, so please take these factors into account before posting about poor battery life.
Q: Why is my button backlight always on?
A: See this thread
Tuning guide
For performance
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Change CPU governor to PegasusQ
Change swappiness to 20
Change I/O scheduler from CFQ to Deadline
Decrease CPU governor sampling rate to 40000
Decrease CPU governor up threshold to 60
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Change entropy read threshold to 512 and write threshold to 256
Disable entropy for internal and external sd
Disable iostats for internal and external sd
For battery life
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Kernel Adiutor
Change CPU governor to PegasusQ
Change swappiness to 40
Change I/O scheduler from CFQ to SIO
Increase CPU governor up threshold to 90
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Decrease vfs cache pressure to 60
Change entropy read threshold to 512 and write threshold to 256.
Disable entropy for internal and external sd
Disable iostats for internal and external sd
Greenify
Enable aggressive doze (beware, you may lose notifications!)
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
rolves1899 said:
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
Click to expand...
Click to collapse
Repartition is highly recommended, otherwise you will have a hard time finding a gapps package that will work. Use lanchon's guide linked in the OP now that you have a working recovery.
gsstudios
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Draky50110 said:
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Click to expand...
Click to collapse
You have good luck then However, it still needs to be worked on.
Although it is not required to reflash isorec, I include it anyway in the steps to prevent issues that may occur anyway. That way, users are 100% sure that they don't end up with cyanogen recovery.
gsstudios
stylemessiah said:
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Click to expand...
Click to collapse
Thanks, will add this to the guide soon.
gsstudios
Thanks for your work and this nice guide.
In this guide in the repartition part where is instructed
to flash kernel with ODIN, i would instruct to set the option
for AUTOMATIC RESET after flash to OFF, and pull battery after flash.
Because the flash happens so quickly and its a little difficult to
do the 3-finger boot then.
Best regards.
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.
I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.
I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.
So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?
Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?
I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
OP updated with recommendations from other users. Thanks for the suggestions!
Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.
gsstudios
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
fireburner-de said:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
Click to expand...
Click to collapse
Already in the OP. It is the second link for the repartition section
gsstudios
AT LAST ! Now they will not spam the official thread of cm 13!
gsstudios said:
Already in the OP. It is the second link for the repartition section
gsstudios
Click to expand...
Click to collapse
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
UsualSuspectReaL said:
AT LAST ! Now they will not spam the official thread of cm 13!
Click to expand...
Click to collapse
I fear, they still will
fireburner-de said:
Well I know, that the link is there. Just 2 lines after the links you write in read that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
I fear, they still will
Click to expand...
Click to collapse
Yes, I forgot to change that. Updating now... I read your post wrong
gsstudios
Edit: Done. Thanks!
Joshndroid's UNOFFICIAL CM13.0 BUILDS
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
CyanogenMod
Rom Source
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65753816&postcount=4
Alternate Download - Basketbuild Download
https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu
Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.
Google Shares
Rules -
1. I WILL NOT be keeping your PM or your email address anywhere once you have been added to the share, i WILL be respecting privacy so I expect the same in return.
2. I WILL however, be creating a google doc (probably in each rom folder) to signify by XDA username only who is in the share. (This is for a couple reasons, 1 - because I can keep track of who I have added to the share, 2 - people can see if they have been added or not to the share to either remind, 3 - It keeps people accountable when their, somewhat, online identity is linked to something.)
3. Do NOT spam me with PM's if I dont get to add you within a day. I am very active on the forums due to mobile access, but to add to the share I will need to be at home. If you have not been added and see your username in the google doc after 2 days, politely PM me again.
4. If you do not use the below template (as it has all the information I will be requiring on my end to add you), You wont be added (so 2 days will pass, you wont see your name or a rom and then check the info u sent me).
5. First download for yourself is going to be rather big (about 4 roms worth). I want to keep atleast a couple roms in the share so that if something is wrong, I can pull a download or whatever at it will not affect anything to severely.
6. You will not have any access to modify or delete the files. I am the owner and you guys will only be able to download/view (which is all you need).
Okay so how can you let me know your in.
First PM me using this template:
XDA Username -
Email (google drive account) -
Rom -
Devices (some have more than one) -
I will add you to the share, I will add you to the local google doc, you will get a device folder and your files will start to sync locally to your PC.
Couple quick FAQ's
How do you know when a new rom is on the share?
You could check it manually, I also was toying with a solution that I could share within the drive that would conduct periodic checks, problem is is that it would rely on a generated file as well as direct links (something that is hard to come by on file sharing services to firstly predict and script & usually requires you to manually click a share button to get a link).
However, there is a google chrome based extention that will notify you by tracking a folder when something new has been added to a google drive folder - https://chrome.google.com/webstore/detail/folder-notifications-for/pamfobflonhoblkekglgpplpibfnckna
This will only track and send an email based on tracking 1 folder.
I am looking into the paid version myself ($2 - http://ez34.net/ezdrive/folder-notif) that will track 10 folders (which is a lot).
Can I get roms from the other locations?
Yes. I have done this setup to quicken my workflow to get roms out, the quicker you guys get them, the happier you's are. Now the primary issue I have it sync'ing to other file services to ensure I limit my bandwidth in uploading (to reduce wait times) and to keep things concurrent across. If i upload to google drive first and sync to other locations on my end, its quicker than me manually uploading to locations.
Remember the first few days I will be spammed with PM's to add everyone who wants to join, I may be a bit slow. But once that is out of the way it will be back to usual and we will then see the benefit of it. I am big on automation, the more I can automate, including checks and failsafes, the more we become something like can be provided by big rom providers.
so;
why did i make a new thread?
Well, i was tired of spamming the other thread that is of a nightly status with these unofficial builds. I pretty much run these builds each time i run a temasek build so they will be frequent enough.
Why havnt you just submitted to CM your the maintainer?
Well, everything is not fixed yet i have been looking at the camera and once that is fixed will probably submit it for nightly status for cm-13.0
what will happen then?
This will be the main thread for cm-13.0 as it continues on, through these unofficial builds and hopefully on to nightlies once the camera is done.
what about android N?
Waaaaaaaay to early to speculate about that yet.
Anything different to base cm-13.0?
Slightly, as the rom is built using UBERTC 4.9 for the rom, the kernel specifially is untouched (unlike temasek builds)
New build March 10 2016 is up on basketbuild and google shares... cheers
Further for some rom updates whatever/follow me on twitter (DW i don't spam) - @joshndroid
Thanks you for the ROM!
This is This is stable or beta or testing? Thanks
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
I prefer to use the temasek build, because of the temasek settings and the omniswitch support, but i think both releases are stable.
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Thanks bruh just makin sure....
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Sy Borg said:
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Click to expand...
Click to collapse
Temasek is his main project so it will get updated more often than dis one I think he started dis one to get it goin to nightly once da camera is fixed....
Gapps for temasek cm13 - difficulty
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
jaypea500 said:
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
Click to expand...
Click to collapse
Bro I have a perfectly fine gapps package linked in second post (opengapps.org)...
These packages work fine for 7 devices I use.
yeah, I fixed it. it wasn't the gapps package. I keep forgetting that when flashing a new rom you need to immediately flash gapps without rebooting in between. the older I get, the more drips out of my colander-brain...
New build 18032016 is up on basketbuild and Google shares
Preparing SD card causes black screen
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
XDAdeveloperHTC said:
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
Click to expand...
Click to collapse
Don't use that... Just use it as external storage.
drm problem
Hi,
i've installed the latest version and get a DRM Error. DRM Widevine is missing...
Thx for a reply
JMF
Hi All,
sharing the guide to install the multiple Rom's in our Axon 7 (as we don't have multi-boot in place).. as the development already kicked with Noughot.. and multiple roms are landing here...
this is for people who can't move out of Stock (due to Audio issues including me) and want to sneak peak the other LOS based roms.
Dual Boot Patcher is an app created by chenxiaolong for S4 initially and it broadly supports more than 150 devices now, whoever used in S4 would be familiar with it.. this app allows you to have multiple ROMs on a single device.
If you loved his work, go to his thread say Thank You
Axon 7 is official supported
I have tried with RR as Secondary and it's working.. so thought of sharing this.
For More details on this Dual Patcher official Thread:
https://forum.xda-developers.com/showthread.php?t=2447534
Working:
- patch ROM zip files
- patch GAPPS zip files
- patch SuperSu zip files
Instructions: More details
Keep the Stock Rom as always Primary.
Use the Data slot and create a name for the folder, as the System/Cache space will be small for LOS Rom
If you want to flash the LOS, RR roms remove the below script in the update-script (ROM\META-INF\com\google\android)
Code:
assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + "."););
assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.0/NRD90M/20170128.052618:user/release-keys");
Issues:
- Encryption and Boot UI are not supported
- trustzone verification in the Update-script will fail while flashing the TWRP, remove the above code before flashing the zip file.
- Pins, patterns or passwords are wrong in one of the ROMs . Then simply delete the file /data/system/locksettings.db (your saved fingerprints won't be lost) with TWRP.
Warning: for me setting the PIN in one rom works, if i enabled PIN in 2 roms it's not working, everytime you have to delete the locksettings.db and boot into other rom. Fingerprint works in 2 ROMS
- if In-app flashing doesn't work, you have to use TWRP to flash the patched zip files (use the latest TWRP)
- If flashing of a patched zip fails for any reason, you have to choose another install location ("Partition Configuration" in the app) when patching the same zip file again!Note: If flashing fails, first look up the error at /sdcard/MultiBoot.log and google it before reporting it...
Download
Download Dual Boot Patcher APP
Download Dual Boot Utilities
Credits to:
@chenxiaolong - for the great app and supporting till date.
@jimbo77 - for making Dual boot Axon 7 official support
@Glove007 - for additional details on workaround for Op3 - applies to Axon7
XDA Community
if i missed any plz let me know.
i can't find anyother thread related to this Dual Patacher, if it's available please merge the thread.
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Nik2424 said:
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Click to expand...
Click to collapse
No you won't lose any data when you flash this.. (But take a backup for safety)
Plz follow this steps.
Install the Dual patcher app and set the current Rom as primary
Make sure you patch the second Rom and Gapps (Super SU optional) in the Dual Patcher App before flashing in TWRP (or it will overwrite the Primary ROM)
in the patched rom remove the TrusstZone entries as mentioned in OP
then flash it via TWRP.
the Rom will be added to your Data or Cache based on the selection you made while patching the Zip file in the Dual Patcher (Preferable is data slot, and rom will be saved in Data>multiboot).
once logged in the Second rom, use the patcher to set the Rom as secondary.
when you want to switch rom, select the rom in the Dual Patcher app and reboot. (the app will move the correct boot.img to partion and selected rom will boot. )
if you want to Wipe Primary Rom or Second/Third Rom use the Dual Boot Utilities in the TWRP, this will wipe only the specified rom and you Second/third Rom won't get deleted. (if you wipe data/cache using TWRP menu, it will wiped your Second/third roms)
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Nik2424 said:
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Click to expand...
Click to collapse
those are added in the Rom to validate you're flashing in the right firmware.. like Noughot roms shouldn't be flashed in MM firmware.
Nothing wrong here in removing in those lines during flashing as secondary Roms..
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
I edit the update-script and remove the quoted lines
I install the dual boot patcher app
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs.
I boot to both ROMS and select stock as primary and LineageOS as secondary
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
Does this seem about right?
Thanks.
So glad this got brought to our phone
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
you should patch with Dual Patcher APK... -- Dual Boot utilities will be flashed in TWRP to install/wipe/update Primary Roms without impact to other Roms.
I edit the update-script and remove the quoted lines - yes
I install the dual boot patcher app - in primary Rom, yes
Open the App, give Root permission - it will prompt you for making the kernel as Primary, set it now - this is required so that App can switch between multiple Roms
1. basically the App will copy the boot.img of primary into storage>multiboot>primary
2. when you install the secondary rom and boot it up, install the app set the rom as secondary.
3. it will copy the secondary rom boot.img in to the same folder
4. whenever you switch rom, the app will copy the switched roms's boot.img to the Boot partiion so that corresponding rom will start on reboot
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
In-app flashing is failing for me, use TWRP to flash it.
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs. - yes
I boot to both ROMS and select stock as primary and LineageOS as secondary
Set the Primary when you installed the App in primary Rom itself.
and set the secondary when installed the app in secondary rom
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
I doubt App sharing is working correctly, please try and let me know
hope this helps
Does this seem about right?
Thanks.
Worked!
Great, this workd for me thanks!
thank you so much for this post
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Sebastian Fox said:
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Click to expand...
Click to collapse
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
`SBR` said:
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
Click to expand...
Click to collapse
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
mvortex3710 said:
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
Click to expand...
Click to collapse
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
`SBR` said:
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
Click to expand...
Click to collapse
Thanks very much for your fast reply.
When I checked the main thread it seems like this problem may be caused by not flashing a patched kernel as well, so I will try that presently and report back!
Edit: The patched kernel I'm using (AX7Kernel) is returning the error: "unable to find boot block location!", I've tried googling it but haven't found anything. Would you happen to know what might be causing this? Flashing in TWRP seems to have fixed this. Attempting boot now.
Edit 2: Boot didn't succeed, I was faced with 5 vibration then a restart to TWRP, where I used the Dual Boot utilities to change back to my Primary (stock) boot.
I'm going to try the other way round, with RR as primary and Stock as (secondary) data boot.
`SBR` said:
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
Click to expand...
Click to collapse
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Sebastian Fox said:
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Click to expand...
Click to collapse
thats not possible...
`SBR` said:
thats not possible...
Click to expand...
Click to collapse
Oh then it seems we reached a blocked road, is there anyway to convert the stock to f2fs??? Partitioning data???
I will try partitioning if possible but it's useless if the dualboot app/utility doesn't support it.
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Nik2424 said:
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Click to expand...
Click to collapse
for me i'm able to ptach RR and it's working in data slot..
did you try to install anything after patched RR and patched Gapps?
So, I've been wanting the Galaxy Tab S7+ for months. But I haven't had the money for it until now (yeah, you guesses it, stimulus payment). But I'm still on the fence about buying it. I know bootloader unlock, TWRP and Magisk root is available for this tab. But I don't want to be limited to just running stock-based ROM's. My plan is to flash a Project Treble-based firmware like Phh Treble, Resurrection Remix.
The questions I'd like to ask are:
1. This tab appears to be Treble compatible, it is listed on the Treble device compatibility page as working. But I would like to hear from an actual owner of this device that has successfully booted and ran a Treble/GSI ROM
2. The partition layout is ARM64 A/B and system-as-root?
3. Besides unlocking bootloader and flashing TWRP, are there any other special considerations I would need to know about?
Without this info, I won't buy, and Google doesn't always produce solid answers. I would like to become an active developer for this device as well, but I need compelling reasons to buy it, besides just great hardware, the latest Android 10/11, that kind of thing....the superficial stuff.
I could just buy now and test when I get it, Amazon has a 30 day return policy. But I don't think they will accept a tablet return if the warranty has been voided by the user. So this really isnt an option.
AnonVendetta said:
So, I've been wanting the Galaxy Tab S7+ for months. But I haven't had the money for it until now (yeah, you guesses it, stimulus payment). But I'm still on the fence about buying it. I know bootloader unlock, TWRP and Magisk root is available for this tab. But I don't want to be limited to just running stock-based ROM's. My plan is to flash a Project Treble-based firmware like Phh Treble, Resurrection Remix.
The questions I'd like to ask are:
1. This tab appears to be Treble compatible, it is listed on the Treble device compatibility page as working. But I would like to hear from an actual owner of this device that has successfully booted and ran a Treble/GSI ROM
2. The partition layout is ARM64 A/B and system-as-root?
3. Besides unlocking bootloader and flashing TWRP, are there any other special considerations I would need to know about?
Without this info, I won't buy, and Google doesn't always produce solid answers. I would like to become an active developer for this device as well, but I need compelling reasons to buy it, besides just great hardware, the latest Android 10/11, that kind of thing....the superficial stuff.
I could just buy now and test when I get it, Amazon has a 30 day return policy. But I don't think they will accept a tablet return if the warranty has been voided by the user. So this really isnt an option.
Click to expand...
Click to collapse
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
LSS4181 said:
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
Click to expand...
Click to collapse
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
5. Is it possible to moves apps to SD without enabling adoptable storage (on stock, I know custom AOSP firmwares will require AS, or a root app like Apps2SD and a 2nd partition on SD.
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And if I do buy, I am serious about becoming a developer.
LSS4181 said:
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
Click to expand...
Click to collapse
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And I am serious about developing for this device if I do buy. Mainly for AOSP firmwares or porting LineageOS, but maybe for stock too.
It looks like I can't delete the previous double posts, and editing causes it to be posted again. I hate the new XDA layout, the old was so much better.
AnonVendetta said:
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And I am serious about developing for this device if I do buy. Mainly for AOSP firmwares or porting LineageOS, but maybe for stock too.
Click to expand...
Click to collapse
I actually booted it myself and kept a backup of it so I can test it a bit further if needed. With TWRP and appropriate backups it's not difficult to switch back and forth.
Since Magisk can't work with Android 11 vendor at the moment, and that recent GSI builds are not certified for some reasons (which blocks Google login), my current use of GSI is still a bit limited, so I'm mostly still doing stuffs on stock.
As for other questions:
1. I'm rooted on stock ROM with Magisk (it works there). Magisk does not work on GSI with Android 11 vendor at the moment.
2. I haven't tried mounting system r/w from within Android, but TWRP certainly could mount it r/w, as Multi-Disabler needs to modify stuffs there. For GSI, you need to use vndklite variants in order to be able to mount system r/w.
Honestly, this is my first Samsung Android device and is also my first device with a super partition, so I still have a lot to learn...
EDIT: I'm using a Galaxy Tab S7+ 5G variant. I think for Wi-Fi variant most things should be similar... but I'm not really sure.
LSS4181 said:
I actually booted it myself and kept a backup of it so I can test it a bit further if needed. With TWRP and appropriate backups it's not difficult to switch back and forth.
Since Magisk can't work with Android 11 vendor at the moment, and that recent GSI builds are not certified for some reasons (which blocks Google login), my current use of GSI is still a bit limited, so I'm mostly still doing stuffs on stock.
As for other questions:
1. I'm rooted on stock ROM with Magisk (it works there). Magisk does not work on GSI with Android 11 vendor at the moment.
2. I haven't tried mounting system r/w from within Android, but TWRP certainly could mount it r/w, as Multi-Disabler needs to modify stuffs there. For GSI, you need to use vndklite variants in order to be able to mount system r/w.
Honestly, this is my first Samsung Android device and is also my first device with a super partition, so I still have a lot to learn...
EDIT: I'm using a Galaxy Tab S7+ 5G variant. I think for Wi-Fi variant most things should be similar... but I'm not really sure.
Click to expand...
Click to collapse
I am using the WIFI variant (SM-T870) on the latest stock release (T870XXU2BUC6) with root and Magisk 22.1 running just fine. Root was accomplished by flashing a Magisk modified boot image with Odin found here https://forum.xda-developers.com/t/...-updated-3-29-21.4159291/page-2#post-84843377 on this thread. I used Titanium Backup to debloat and have had no issues at all. The performance is great and the stability sound. I would suspect that a similar arrangement could accomplished on the other versions of the tablet but cannot speak from experience. Personally I have never had much luck flashing Project Treble GSIs on any of my devices. They tend to be very unstable and iffy at best and I always wind up returning to stock or another custom ROM choice.