{
"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"
}
FINALLY THE GREAT GUYS HERE ARE SUCCESSFULL IN BRINGING CYANOGENMOD 7.2 FOR OUR BELOVED EXPLORER
cyanogenmod 7.2 is a free, community built, aftermarket firmware distribution of android 2.3.7 (gingerbread), which is designed to increase performance and reliability over stock android for your device.
Click to expand...
Click to collapse
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.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
desclaimer--
#you are flashing this rom (which i may add is awesome) on your own risk
#we are not responsible for any bricked devices or fried sd cards
FIRST OF ALL I HAVE NO HAND IN COMPILING THIS ROM I AM JUST BUILDING A NEW NOOB FRIENDLY THREAD (No offence to noobs as i am kinda one myself :silly: ) CREDITS BELOW
Working Features--
- WiFi
- Hardware acceleration
- RIL
- Gps
- Audio
- Usb Mass Storage
- Bluetooth
- USB Tethering
- Fm Radio
- Everything else except below
Not Working--
- Camera
- Phone sometimes reboots when playing videos
Click to expand...
Click to collapse
NOW INTRUCTIONS--[--Unlock bootloader and root your explorer (if you haven't already) follow this link http://forum.xda-developers.com/showthread.php?t=1415223 to root. Dont create a partition just yet.
--Download cm-7-20120807-UNOFFICIAL BUILD #4-pico.zip from mediafire link below and copy it anywhere on sdcard.
--Download gaaps from link below and copy it on sdcard
--Boot into recovery
-- (optional but recommended) go to backup and restore and select backup. This will backup your phone just as it is so that if u ever wanna revert back you can just restore from recovery. (Thanx Liverpool_fan for tip)
--Go into mounts and storage and format /system and /boot and come back and wipe data/factory reset (even if you have any custom rom installed)
--Select Install zip from sdcard-> choose zip from sdcard-> browse to where you have copied the zip file and select it
--Wait for the installation to complete and download latest kernel from link below and flash it in recovery. (format of kernal MDD so update to the latest one)
--flash gaaps to install basic google apps.
--Now select reboot and wait for your phone to boot up.
--If you want to move your dalvik cache to sdext first you will have to partition your sd card. 512mb partition is enough. Use minitoolwizard to partition your sdcard. Partition it in only ext2, ext3 or ext4 format because fat32 is not supported. You can also use recovery (advanced>partition sdcard) to partition but it will erase all data on your sdcard so back it up.
--Now dowload a2sd.zip (credit- Sakindia) and flash it through recovery. You can find a2sd.zip where the kernals are uploaded (check below)
--Reboot and go into Terminal emulator and type "a2sd cachesd" (without quotes)
--Wait for the working to finish and reboot. You have 148mb internal memory free now. :good:
--Alternatively people are saying that s2e is more stable. So download s2e from play store.
--check everything except application data. Reboot.
NOTE: Either flash a2sd or install s2e.
--Enjoy.!!
(OPTIONAL)--
--Download titanium backup and come to the app list now long press on any app and select move data to sd. It will ask you to create a directory, accept! Now select menu button while still in titanium backup and select batch. Come down to option "move app data to sd". Run it to get more internal memory but I recommend to use class 6 sdcard if you are moving app data.
LINK FOR KERNALS AND A2SD(CREDIT- sakindia)--
http://goo.im/devs/sakindia123
Click to expand...
Click to collapse
LINK FOR BUILD #1
http://www.mediafire.com/?2hash35eaw61ibn
Click to expand...
Click to collapse
LINK FOR BUILD #2
http://www.sendspace.com/file/h8s855
Click to expand...
Click to collapse
LINK FOR BUILD #3
http://www.sendspace.com/file/x14u9i
Click to expand...
Click to collapse
LINK FOR BUILD#4
http://www.sendspace.com/file/ci209s
http://www.mediafire.com/?oy3mrrf6ts9olim
Click to expand...
Click to collapse
Gapps
http://goo.im/gapps/gapps-gb-20110828-signed.zip
Click to expand...
Click to collapse
If you want to help in development or want the source code check out this link
http://forum.xda-developers.com/showthread.php?t=1793026
Click to expand...
Click to collapse
Now importantly THE CREDITS--
- lirokoa
- derefas
- LiVeRpOoL-FaN
- rom2maru
- sakindia
AGAIN I HAVE NO HAND IN DEVELOPMENT OF THIS PORT
I will be uploading screenshots and mediafire links soon! Please be patient!!
RESERVED for FAQs and troubleshooting!!
ReSeRvEd just like that :silly:
:cyclops:
Reserved for Changelogs ....too lazy to do it now
Fantastic work!
But I suggest you to change the thread name, and including the following "[TUTORIAL]", because poeple will think that is the main thread to this rom.
Regards!
a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............
You sir just made my day.
LiVeRpOoL-FaN said:
a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............
Click to expand...
Click to collapse
Not really. You'd only ever need to do a factory wipe/reset and then dalvic-cache wipe Cheers.
Txask said:
Fantastic work!
But I suggest you to change the thread name, and including the following "[TUTORIAL]", because poeple will think that is the main thread to this rom.
Regards!
Click to expand...
Click to collapse
Did it ..thanx for the heads up!!(sorry reached thanx limit of the day will surely do it tomorrow)
LiVeRpOoL-FaN said:
a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............
Click to expand...
Click to collapse
Did this too..thanxx for the tip!!
AIndoria said:
Not really. You'd only ever need to do a factory wipe/reset and then dalvic-cache wipe Cheers.
Click to expand...
Click to collapse
thats what i thought..and dalvik cache also gets cleared by factory wipe!! Anyway whats the harm in being extra cautious!!
ToinouAngel said:
You sir just made my day.
Click to expand...
Click to collapse
I aim to please :angel:
vshl2995 said:
I aim to please :angel:
Click to expand...
Click to collapse
Yeah well I can't unlock the bootloader, thanks to HTC Sync who doesn't recognize my phone. So I'm screwed.
ToinouAngel said:
Yeah well I can't unlock the bootloader, thanks to HTC Sync who doesn't recognize my phone. So I'm screwed.
Click to expand...
Click to collapse
Did you download the latest htc sync software? Here
http://www.htc.com/sea/software/htc-sync/
vshl2995 said:
Did you download the latest htc sync software? Here
http://www.htc.com/sea/software/htc-sync/
Click to expand...
Click to collapse
Yeah, but no luck. I'll try on another laptop when I have a chance.
EDIT: Windows 8 seems to be the problem, I can't update the drivers with the unrevoked f.ile. So yeah, I'll try with Windows 7.
ToinouAngel said:
Yeah, but no luck. I'll try on another laptop when I have a chance.
EDIT: Windows 8 seems to be the problem, I can't update the drivers with the unrevoked f.ile. So yeah, I'll try with Windows 7.
Click to expand...
Click to collapse
You shouldn't really use consumer preview as your primary OS..u should install it in a different partition!!
vshl2995 said:
You shouldn't really use consumer preview as your primary OS..u should install it in a different partition!!
Click to expand...
Click to collapse
I know, I installed the Consumer Preview in order to try it out, problem is I was doing multiple things at the same time and accidentally installed it over Vista.
I was too lazy to reinstall Vista back so I just decided to wait for the final version to be released as the preview works just fine for everything I do with my laptop... Well until now anyway, ha.
ToinouAngel said:
I know, I installed the Consumer Preview in order to try it out, problem is I was doing multiple things at the same time and accidentally installed it over Vista.
I was too lazy to reinstall Vista back so I just decided to wait for the final version to be released as the preview works just fine for everything I do with my laptop... Well until now anyway, ha.
Click to expand...
Click to collapse
Lol..
(I would use jaggy's tutorial to ask but since it hasn't been active for ten days I thought I'd be better to ask here instead of bumping the other thread, if I'm wrong I apologize)
So yeah, I'm still at the rooting process and it seems I'm definitely out of luck on this one.
So first off, I apparently managed to unlock the bootloader (and it IS unlocked, when I'm in bootloader mode I do have the "*** unlocked ***" on top of the screen) and at the same time keeping my apps, settings, etc...This was the first flag that something was wrong.
Adding the Recovery seems to have worked out fine, however when I tried to install the Superuser.zip I got the apparently not-so-uncommon "(Status 0) Installation aborted" message. I did some research and tried the method of removing the extra "updater-script~" from the archive but it did not work. Tried the method of doing a nandroid backup and then installing Superuser but no luck either.
I'm getting seriously hopeless, any idea on what I might have done wrong and how to get Superuser working?
Which recovery did you install, I was having some problems flashing anything with non-yannou's (I know i wrote it stupid but, you've got the idea )
Anyway, give a try to flash some rom, not sure if it will work without superuser installed, but nothing worse can happen (I think)
shortyoko said:
Which recovery did you install, I was having some problems flashing anything with non-yannou's (I know i wrote it stupid but, you've got the idea )
Anyway, give a try to flash some rom, not sure if it will work without superuser installed, but nothing worse can happen (I think)
Click to expand...
Click to collapse
I installed the Recovery given by jaggy's tutorial. But Recovery isn't the problem as far as I know, since I've the option to install .zip file when in Recovery mode. My only issue comes from the fact that the Superuser file won't install itself.
Related
CM10.1 "WEEKLIES"!
{
"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"
}
This ROM aims at bringing to the G2X community what it deserves : a fully working jellybean (this is NOT the hackfest) build based on CM10.1 (android 4.2.1). I wanted this powerful device to get the very best, and now it will get the most recent android system, updated whenever I will have some time to. Never again, we will wait for LG to update this device.
As most of you know, the radio doesn't work, which means no calls/SMS on CM10/10.1. That is why I adapted a dual boot system (based on bihariel's work) for this device.
WHY DUAL BOOT?
With dual booting, you can choose between two ROMS and change from one to another in less than 20 seconds!
You can change to CM10.1 to...
- Feel what it means to have a buttery smooth device
- Play games
- Make free WIFI calls (US and Canada) with GrooveIP lite
- Use the most recent android OS.
When you're on the go, change to a CM7/CM9/CM10 (hackfest) ROM...
- FAST!
- Without altering the CM10.1 files
- To make phone calls and receive SMS
DISCLAIMER
I AM NOT RESPONSIBLE of any damages to your device related to the use of this ROM or the dualboot toolkit. You do this at your own risk. Even though this has been tested and works well, using NVFLASH may brick your device if done incorrectly.
INSTALLATION INSTRUCTIONS
This ROM comes in two flavours: The dualboot toolkit or the Original flashable ROM
Dualboot ROM Instructions
WARNING! NVFLASH will format EVERYTHING, including internalSD. Make sure you backup your important files on your externalSD card
PART 1 - Resizing system partition
1) Unzip the dualboot toolkit and unzip NVFLASH_Resizer-G2X.zip.
2) Power off your phone and remove the battery. Keep vol. up and vol. down held and plug the phone via USB to a WINDOWS computer.
3) Windows should add an "APX driver". Go to control panel -> Device manager and right click on it -> Update driver -> search in system. Then, browse to the drivers folder inside the NVFLASH package and choose nvidiausb.inf. Approve any error messages (Windows 8 users read my FAQ). Install the Nvidia Fastboot driver.
4) Unplug your phone and hold down vol.up and vol.down. Replug it again and double click on flash.bat inside the NVFLASH folder. KEEP BOTH BUTTONS HELD DOWN DURING THE WHOLE PROCESS!.
5) When NVFLASH is done, unplug the phone and put back the battery. Reboot into recovery with power + vol. down. Plug it back and go to mounts and storage -> mount USB storage. If your PC asks to format the internal SD card, select yes.
PART 2 - Installing ROMS
1) Download the desired "call/SMS" ROM and extract boot.img from it's flashable zip. Rename it to boot1.img. Extract Step3_bootimg.zip from the dualboot toolkit and copy-paste boot1.img into system/boot, replacing the file that is already there. Repack Step3_bootimg.zip.
2) Copy-paste your desired ROM into the 0dualboot folder and send it to your device SDcard with everything it contains (your device should already be in the "mount USB storage" menu).
3) From the recovery, flash Step1_enabler.zip. When the screen goes black, hold power + vol. down to get back into recovery.
4) Flash your desired ROM, then Step2_ROM1.zip. Reboot to the OS.
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
And there you go! To switch from one OS to another, just open the systemchanger app and click on "switching"!
Credits to bihariel for the original method. See the original thread here.
Original flashable zip ROM instructions
1) Boot into recovery with power + vol. down
2) Wipe data/cache, then mounts and storage -> format system
3) Flash this ROM
4) Advanced -> Wipe dalvik cache and fix permissions
5) Reboot and enjoy!
Special trick : In settings, go to About phone and click 6 times on Build number. This will pop up the developer and performances options. In performances options, CPU settings, change the governor from INTERACTIVE to SMARTASSV2.
Download links
ROM with DUALBOOT Toolkit ***BETA***
DOWNLOAD HERE!
Original flashable ZIP (For single boot)
DOWNLOAD HERE!
Credits and thanks
See my original thread here for the full list!
Thanks to bihariel for the original method for the Optimus 2X which I adapted for the P999. Great job!
Special thanks to Core Memory for helping me start this project
CHANGELOG
***
V.2
Mazout360's kernel V.0122
Based on CM10.1 (Android 4.2.2)
Comes with Google Apps (20130301)
Patched Service.jar
LG Bootanimation
Stable and no hot reboots
GrooveIP for free US/Canada calls
Radio disabled (battery saving)
V.1 (original release)
Mazout360's kernel V.0104
Tweaked and fast!
Comes with Google Apps (20121212)
Patched Service.jar
LG Bootanimation
Fixed Facebook sync (untested yet)
Fixed SDcard detection by apps
Mass storage working
ADB working
Stable and no hot reboots
FAQ
I am using Windows 8 and I cannot install NVFLASH drivers!
In windows 8, you will need to go on Select Settings (right bar)/More PC Settings (at bottom). Then go General/Advanced Startup/Restart Now/Troubleshoot/Advanced Options/Windows Startup Settings/Restart. Disable driver signature enforcement (should be options 7 I think). If you don't get to the advanced startup menu, keep pressing F8 when rebooting.
I am getting Status 7 errors while flashing this ROM!
This is possible, and to fix this simply flash another CM10.1 ROM before (adampk's build 7) and dirty flash this ROM again. If it doesn't work, go to mounts and storage and manually mount /system.
I found a bug, can I submit a logcat ?
Yes, but make sure you are taking a logcat while the bug happens. Please post them in a userthread or send them to me via PM. Thanks!
I have a suggestion for your ROM...
...and I'm always open to them! Whether it's for integrating new apps, themes, tweaks, I'm always open for good ideas! PM me or post in the user thread.
I am experiencing FC and some base apps are missing!!
This is not normal. I've been running this build for two days in a row and didn't have a single issue. You should consider reinstalling using the Original flashable ZIP package. Simply boot to CM10.1, power off the phone, then get into recovery using power + vol. down and follow the instructions (if you are using the Dualboot Toolkit).
USERTHREAD HERE : http://forum.xda-developers.com/showthread.php?t=2127810 (Thanks to Yuvin for maintaining it!)
Re: [ROM][CM10.1] Mazout's CM10.1 weeklies with DUALBOOT Toolkit![V.beta1]
Appreciate this friend. You are quite generous.
Sent from my LG-P999 using xda app-developers app
Thanks a lot, I'll try it as soon as possible
Re: [ROM][CM10.1] Mazout's CM10.1 weeklies with DUALBOOT Toolkit![V.beta1]
This looks great. You are one of the best developers out there
Sent from my LG-P999 using xda app-developers app
Re: [ROM][CM10.1] Mazout's CM10.1 weeklies with DUALBOOT Toolkit![V.beta1]
Whoa. I think I'm going to try it out. Maybe a stable Gingerbread ROM like hellfire for calls to back up the CM10 goodness. Would switching ROMs often, like 3 or 4 times an hour, have much impact on battery?
Sent from my LG-P999 using xda app-developers app
plarmann said:
This looks great. You are one of the best developers out there
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Thanks! This was not my main project as this is only a port of cm10.1 (with some fixes and many tweaks to make it interesting of course ) because I had some issues with the other one but I'll try to make this one as useful as possible even without radio. I actually compiled this and realized that it was very efficient and functional.
Ravinxx said:
Whoa. I think I'm going to try it out. Maybe a stable Gingerbread ROM like hellfire for calls to back up the CM10 goodness. Would switching ROMs often, like 3 or 4 times an hour, have much impact on battery?
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Switching ROMS shouldn't have a very big impact on battery usage. Changing the CPU governor to SMARTASSV2 and keeping airplane mode on (in CM10.1) might help somewhat, but I already silenced the radio so it shouldn't use too much battery anyway.
If everything goes as planned, I should release another kernel build by tomorrow to add some interesting features and the upcoming "weekly" updates for this ROM will be available as "patches" for those who already have the dual boot set up to make it as simple as possible. Of course, new users will also have the full CWM flashable zip version.
I installed Original flashable ZIP (For single boot). It's the one that I am looking for a while.
• Jelly Bean 4.2.1
• 1080p Camera
• Fast / Classic / Common&Known / Simple / Stable
• Good&Concerned Developer
I don't know what's going on but after I unziped this dual boot file with 7zip and I went into the "0dualboot" folder then the "NVFlash_Resizer-G2x" and in there I find the "Drivers" folder like you said. However, in the drivers folder is the "amd64" and "i386" but both of those folders are empty. Nothing is inside them at all. Am I missing something? This is on Win7 so should find it just fine. Can anyone help me with this?
Edit: I just downloaded the file "DBToolkit_cm10.1_p999" for the 3rd time with the same problem. Also the file you specified, "flash.bat" isn't showing up either in the NVFlash folder.
Thank you so much. I hope people like you keep the G2X development alive.
Thanks again.
draky said:
I don't know what's going on but after I unziped this dual boot file with 7zip and I went into the "0dualboot" folder then the "NVFlash_Resizer-G2x" and in there I find the "Drivers" folder like you said. However, in the drivers folder is the "amd64" and "i386" but both of those folders are empty. Nothing is inside them at all. Am I missing something? This is on Win7 so should find it just fine. Can anyone help me with this?
Edit: I just downloaded the file "DBToolkit_cm10.1_p999" for the 3rd time with the same problem. Also the file you specified, "flash.bat" isn't showing up either in the NVFlash folder.
Click to expand...
Click to collapse
Oh woah my bad...I honestly don't understand why it's missing files in the NVFLASH package..Well it's being reuploaded at the moment so it should be ready in about 5-10 minutes.
Sorry for this.
I will download it myself and verify it to make sure everything is okay now...If something is wrong just reply back
EDIT: Okay it's back up and I verified everything so you should be good.
Re: [ROM][CM10.1] Mazout's CM10.1 weeklies with DUALBOOT Toolkit![V.beta1]
So do we have to use nvflash to flash these roms
faratl said:
So do we have to use nvflash to flash these roms
Click to expand...
Click to collapse
Use the single boot (Original flashable zip) if you do not want to use nvflash. For dual boot, you don't have the choice. If you backup everything with titanium backup on your externalSD or computer you shouldn't lose anything though.
Mazout360 said:
Oh woah my bad...I honestly don't understand why it's missing files in the NVFLASH package..Well it's being reuploaded at the moment so it should be ready in about 5-10 minutes.
Sorry for this.
I will download it myself and verify it to make sure everything is okay now...If something is wrong just reply back
EDIT: Okay it's back up and I verified everything so you should be good.
Click to expand...
Click to collapse
Just downloaded it and it has stuff in there. Thank you!
hey man thanks for your work, where you found time to tinker with our little dual boot problem, while working on the kernel and everything else, i wont ever know. dang dude. will be trying this out after i replace my wifes screen tonight. i would say the G2X community owes you one...or more. thanks again!
Ok, so I was installing this dual boot and ran across a problem, I, now, cannot mount the system or cache after the first step... So I cannot get a ROM on my phone to work at this time. Any ideas?
draky said:
Ok, so I was installing this dual boot and ran across a problem, I, now, cannot mount the system or cache after the first step... So I cannot get a ROM on my phone to work at this time. Any ideas?
Click to expand...
Click to collapse
Restart the NVFLASH process. Make sure you keep vol. up and vol. down held during the whole process. Plug the phone directly in a USB port from your motherboard (not in a splitter or a front port, for example). Also make sure you followed the instructions correctly and that the bootloader and recovery files are completely sent when running NVFLASH.
Oh also, verify that you have the correct drivers installed (Nvidia USB-boot driver or something like that) and extract everything for the NVFLASH archive.
Just to make sure the archive is okay now, can I have a confirmation of someone who tried it and it worked ?
Mazout360 said:
Restart the NVFLASH process. Make sure you keep vol. up and vol. down held during the whole process. Plug the phone directly in a USB port from your motherboard (not in a splitter or a front port, for example). Also make sure you followed the instructions correctly and that the bootloader and recovery files are completely sent when running NVFLASH.
Oh also, verify that you have the correct drivers installed (Nvidia USB-boot driver or something like that) and extract everything for the NVFLASH archive.
Just to make sure the archive is okay now, can I have a confirmation of someone who tried it and it worked ?
Click to expand...
Click to collapse
Thank you, I never thought to redo the NVFLASH.
Now, the NVFLASH opened a windows for a second or less when I told it to run. Is that normal?
And the APX drivers are installed correctly because I have been going from twrp to cwm and back without a problem.
I will try it again when I get home because my brother in law doesn't have a working pc. Will let you know and let me know about the NVFLASH please. Thank you
---------- Post added at 01:22 PM ---------- Previous post was at 01:01 PM ----------
Forgot to mention, the Window that opens on NVFLASH closes in less than a second so I cannot read it.
Awesome work Mazout! I'll try out this method after my exams are over, Also, do you want a new Userthread for this Dualboot system or will you use the older one?
{
"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"
}
KatKiss Marshmallow ROM
Asus TF300T Q&A Thread
Please note that this version is made for and tested on the TF300T model.
Thanks to keep this thread for the TF300T
Rom Thread: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3237867
-
Long time starting whilst whilst "optimizing App 1 of 1"
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks
DPR59 said:
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks
Click to expand...
Click to collapse
not sure,
I don't have that issue.
Try to format /cache and dalvik-cache to force a full optimize process.
Maybe something went wrong whent art tried to optimize one app.
Did it do that from the 1st install or after you restored some of your apps ?
Would help to find out which app it is exactly.
If it is still doing it after the cache and dalvik format,
reboot and Grab a logcat right after it is done optimizing the 1 of 1 app.
timduru said:
not sure,
I don't have that issue.
Try to format /cache and dalvik-cache to force a full optimize process.
Maybe something went wrong whent art tried to optimize one app.
Did it do that from the 1st install or after you restored some of your apps ?
Would help to find out which app it is exactly.
If it is still doing it after the cache and dalvik format,
reboot and Grab a logcat right after it is done optimizing the 1 of 1 app.
Click to expand...
Click to collapse
Tim, thanks for a prompt response. I have now done a clean install, including a factory reset and data format.
Problem still present on second boot, with only apps in your recommended GAPPS package installed.
Then installed ES File Explorer and Chainfire's LiveBoot to create the logcat.log file. However, I don’t have the knowledge to understand the output, even with the help of google.
I then wiped cash and dalvik and on restart the optimization process moves along at a reasonable pace, but spends a long time optimizing app 69 of 72. Not sure if this helps, and remember this is with ES File Explorer and Liveboot installed.
Any advice would be appreciated.
Regards
DPR59 said:
Then installed ES File Explorer and Chainfire's LiveBoot to create the logcat.log file. However, I don’t have the knowledge to understand the output, even with the help of google.
Click to expand...
Click to collapse
post the logcat file here.
timduru said:
post the logcat file here./
Tim, sorry but can not work out how to post the file.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DPR59 said:
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks
Click to expand...
Click to collapse
i have the same problem not a big issue just a bit annoying
[email protected] said:
i have the same problem not a big issue just a bit annoying
Click to expand...
Click to collapse
Seems to be google gms app taking too much time to optimize for users who left /data as ext4
I'll increase the timer in V008,
but if you change /data to f2fs that should be faster and work fine too.
It seems to be the difference between those who have the issue and those who don't: /data ext4 Vs f2fs
timduru said:
Seems to be google gms app taking too much time to optimize for users who left /data as ext4
I'll increase the timer in V008,
but if you change /data to f2fs that should be faster and work fine too.
It seems to be the difference between those who have the issue and those who don't: /data ext4 Vs f2fs
Click to expand...
Click to collapse
hey, sorry for the noob question but how do i change to f2fs and also the browser seems to block going on google sites that are advertised if i try go on bookings.com for example through a google search it says err connection refused
[email protected] said:
hey, sorry for the noob question but how do i change to f2fs
Click to expand...
Click to collapse
Wipe => Advanced wipe
check the box for data then click on Repair or change file system
then click F2FS
and also the browser seems to block going on google sites that are advertised if i try go on bookings.com for example through a google search it says err connection refused
Click to expand...
Click to collapse
That's the adblocker included.
What is the hostname in the url? I can remove that to let it go through.
timduru said:
Wipe => Advanced wipe
check the box for data then click on Repair or change file system
then click F2FS
Click to expand...
Click to collapse
it seems I'm very unlucky lol, I tried doing this but get an error that says file system could not be changed or something like that, I tried some other sollutions on google but none of them worked, I still get the same error
[email protected] said:
it seems I'm very unlucky lol, I tried doing this but get an error that says file system could not be changed or something like that, I tried some other sollutions on google but none of them worked, I still get the same error
Click to expand...
Click to collapse
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)
timduru said:
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)
Click to expand...
Click to collapse
thanks this solved everything, you really are a mastermind
DPR59 said:
timduru said:
post the logcat file here./
Tim, sorry but can not work out how to post the file.
Click to expand...
Click to collapse
Tim, update
have now changed /data to f2fs and installed version 008 of the ROM, not added any of my apps yet but so far no apps optimizing on a restart. Thanks for you help with this, donation on the way, and keep up the great work.
Paul
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Screen rotation cure?
I have found that with rotation control app installed, but NOT running, auto rotate appears to work for apps I am using, if rotate screen is enabled in display properties.
No need for manual rotation, indeed, the rotation app is not running, just installed then stopped in app properties.
So far works every time for me
Hey Tim just for curiosity sake would there be any benefit in having cache and system as f2fs aswell? If so can you make the next update compatible I tried doing it just to see if it would work but was just stuck on the meerkat screen so I put system and cache back to ext4
Fantastic work, Timduru. I installed the 08 without a problem and without changing partition to F2FS. Installation and App optimization took less than 10 min. I got frustrated though because of the autorotation issue and the lack of marshmallow support (card access) of some apps (i.e. Dropsync). With the 09 and the autorotation issue solved I will go back to MM. Thanks for your effort :good::good::good::good:
I actually hadn't touched my TF300t for the last year. But with your great roms - it is a pleasure to use it again.
MPSmart said:
Fantastic work, Timduru. I installed the 08 without a problem and without changing partition to F2FS. Installation and App optimization took less than 10 min. I got frustrated though because of the autorotation issue and the lack of marshmallow support (card access) of some apps (i.e. Dropsync). With the 09 and the autorotation issue solved I will go back to MM. Thanks for your effort :good::good::good::good:
I actually hadn't touched my TF300t for the last year. But with your great roms - it is a pleasure to use it again.
Click to expand...
Click to collapse
Is 7 --> 8 --> 9 dirty flashable?
Google Play Wont Download apps
I installed the ROM but for some reason none of the apps will install from Google Play. They start downloading and stay downloading forever - never actually downloading.
Any suggestions....
Thanks
Jay
timduru said:
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)
Click to expand...
Click to collapse
Thanks for all your work on this ROM.... A noob here, am using the KatKiss Lollipop v030 and it is the best. Have tried to install KatKiss Marshmallow v009, seems to be slow as i suspect am doing it wrong, here is the steps i did using TWRP 2871.
1. Full Wipe = success
2. Flash KatKiss Lollipop v009, flash super su, flash gapp (in that order) = success
3. Wipe cache/davlic = success
4. Tried to change data to f2fs with twrp 2871 = not allowed or error or failed
5. Reboot to system = tablet booted to marshmallow but very slow even though i let it optimize for an hour and a
half.
Questions:
1. When should i change the data from ext4 to f2fs? Is it before step 1 or after step 1, step 2?
2. I also see some post that i should unmount, how to do that and in which step should i do unmount?
3. Maybe TWRP 2871 is the culprit?
I update TWRP by flashing the latest TWRP(zip file). The problem now is the latest twrp(2872) is an img file.
Will that img file be flash to update my TWRP?
Have returned back to KatKiss Lollipop v030. Sorry for all this troubles, this tablet is my only computer and you made it very fast. Helps me with my studies. If someone can help me?
{
"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"
}
LineageOS 20.0
lineage-20.0-20230507-UNOFFICIAL-flo.zip
lineage-20.0-20230507-UNOFFICIAL-deb.zip
Known issues:
- We are still Permissive (SELinux)
- Encryption is not working .. Pls do NOT encrypt your /data partition!
- Camera is not fully working .. Only certain Camera apps are working well.
- And maybe more issues .. ?
Installation:
1.) Do factory reset in TWRP - keep internal storage this way.
2.) Format /system partition in TWRP
3.) Install ROM
4.) Install Gapps (optional)
5.) Install Magisk 26.1 (optional)
6.) Reboot into system and start to setup your device.
Gapps:
Mind the Gapps
LiteGapps
TWRP:
twrp-3.7.0_9-1-flo_followmsi.img
twrp-3.7.0_9-1-deb_followmsi.img
Magisk:
Tested with Magisk 26.1
MicroG:
The builds have been patched to support microG !
Android 11/12/13 File-system size:
Flo and Deb device -> 1275 MB -> both devices needs reparition !
Pls check below for more details.
System repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system partition .. either via TWRP package or manually via shell.
It's an one time task.
But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 880mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 880mb).
The free space we got thru repartitioning needs to be allocated again.
For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.
There are repartition solutions from @ipdev @Clamor @k23m .. and maybe more.
Made new sysrepart.zip based on the original from @k23m
https://forum.xda-developers.com/showpost.php?p=76278047&postcount=19
The original code is changing to 1140MB (system) and 260MB (cache).
These days /cache is not used anymore .. a few MB only.
For this reason I have changed the values to 1280 (system) and 120MB (cache) now.
https://forum.xda-developers.com/showpost.php?p=78703434&postcount=1971
In latest version we have changed to 1380MB (system) and 20MB (cache)
https://forum.xda-developers.com/t/...neageos-18-1-2021-11-05.3569067/post-85999781
sysrepart_1380_20.zip
All the credits to @k23m !!!
Pls check REPIT script from @ipdev .. to get 1480MB system partition .. to be able to install opengapps !
https://forum.xda-developers.com/t/tool-unofficial-port-repit-for-nexus-7-2013-deb-flo.4237183/
Sources:
https://github.com/followmsi/manifests/tree/flo-deb-lineage-19.1
https://github.com/followmsi/manifests/tree/flo-deb-lineage-18.1
https://github.com/followmsi/manifests/tree/flo-deb-lineage-17.1
https://github.com/followmsi/manifests/tree/flo-deb-aex-pie
https://github.com/followmsi/manifests/tree/flo-deb-lineage-16.0
https://github.com/followmsi/manifests/tree/flo-deb-pixel-pie
https://github.com/followmsi/manifests/tree/flo-deb-rros-lineage-16.0
https://github.com/followmsi/manifests/tree/flo-deb-aosp-p
https://github.com/followmsi/manifests/tree/flo-deb-aosp-o
https://github.com/followmsi/manifests/tree/flo-deb-aosp-nougat
Download:
https://drive.google.com/drive/fold...HZThGTnM?resourcekey=0-0BunAmDBWluYPghT0Fs6CA
All other ROM have been moved to androidfilehost.com ..
https://androidfilehost.com/?w=files&flid=289295
All the testing has been done by @ipdev - big thanks to him !
Thanks to @nbehary and @DevSwift1 and @flex1911 and @yattodettaman and @emmett.tsai !
Big Thanks to LineageOS Team !
Enjoy
Thanks will download when I get home
lollyjay said:
Thanks will download when I get home
Click to expand...
Click to collapse
Cool .. go for it
It seems there are some download issues using mobile devices.
Google Mobile version wants to redirected to some ...mobile... link, which is not working.
At least for me.
Also the import into Google Drive App seems not to work.
If you choose "request desktop version" in Chrome mobile settings it should work.
On normal desktop browsers there are no problems.
This issue occurs since a few days .. for "all" my Google Drive projects
Hi I downloaded in Windows 10 and all working atm. More after I test.
---------- Post added at 08:31 PM ---------- Previous post was at 08:01 PM ----------
ROM seems fully functional. Working well with data and dalvik formatted f2fs.
Your recovery is also functioning well, with the the exception that it takes over a minute to load. Not a problem for me though.
This is related to F2FS .. if you would have ext4 data it will load much more quickly.
followmsi said:
This is related to F2FS .. if you would have ext4 data it will load much more quickly.
Click to expand...
Click to collapse
After installation, does not go into the recovery (3.0.2)
On version 3.0.3-3, such a problem will not exist?
Which sections have the format f2fs ?, and whether it is possible to add a night mode?
boom1982 said:
After installation, does not go into the recovery (3.0.2)
On version 3.0.3-3, such a problem will not exist?
Which sections have the format f2fs ?, and whether it is possible to add a night mode?
Click to expand...
Click to collapse
/system/bin/install-recovery.sh
You loose recovery .. this is normal ... if not rooted ..(SuperSU.zip)
The easiest solution is to install SuperSU.zip via TWRP.
Maybe I can remove it for next build .. not sure.
F2FS .. via TWRP
Wipe - Repair/Change file-system ...
Jus install the ROM and test and play yourself
Cheers
Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
rajsris said:
Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
Click to expand...
Click to collapse
Micro gapps works! [emoji6]
I cannot install Gapps 7.1.1 (tried micro and aroma), message saying I am on Android 6.0.1 and need to use proper version. Deb.
finkbg said:
I cannot install Gapps 7.1.1 (tried micro and aroma), message saying I am on Android 6.0.1 and need to use proper version. Deb.
Click to expand...
Click to collapse
I installed open gapps arm 7.1 pico with no problem. Not enough system available space for micro
You can try to resize file system of system partition inside TWRP to get full partition size.
Or use the Update.zip_resizefs_flo.zip inside the download folder.
Works for deb too.
Cheers
Hmmm not sure what I'm doing wrong. Tried the process twice, both times after reboot step, TRWP tells me no OS installed. Suggestions?
Enough space is available for micro. I managed to install it after a few reboots (no clue how). However, having converted data to f2fs, I now cannot write to data from within the ROM (play store crashes on install of any app, webview cannot start a download and camera cannot save photos). Latest rom from yesterday, haven't installed any fstab patches (thought this rom being the next release would not need any patches, am I correct?). Any suggestions?
rajsris said:
Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
Click to expand...
Click to collapse
Keep in mind that all Open GApps installs can be customized so if you want FaceLock you would chose the lowest package with it and them use the config file to remove the rest of the differences.
Also Face Unlock DOES come with Nano BTW, only package without it is Pico.
(Disclaimer: I'm a former Open GApps team member.)
Yes, micro works. It worked with the original ROM by nbehary and it works with this one as well.
finkbg said:
Enough space is available for micro. I managed to install it after a few reboots (no clue how). However, having converted data to f2fs, I now cannot write to data from within the ROM (play store crashes on install of any app, webview cannot start a download and camera cannot save photos). Latest rom from yesterday, haven't installed any fstab patches (thought this rom being the next release would not need any patches, am I correct?). Any suggestions?
Click to expand...
Click to collapse
Did you fix your problems ?
The fstab has been changed ... you can verify yourself.
Open terminal app ..
Code:
su -
cat fstab.flo
To see the current partitons and there used/mounted filesystems ..
Code:
mount
Pls have a look here ..
https://forum.xda-developers.com/showpost.php?p=71296026&postcount=716
F2FS seems to work fine on data - I still use it on cache only.
If you face strange issues, pls start with a fresh TWRP factory reset first.
Cheers
bgiesing said:
Also Face Unlock DOES come with Nano BTW, only package without it is Pico.
Click to expand...
Click to collapse
Thanks for the info, I meant pico actually, as all other nougat roms for this device only have space for that package.
followmsi said:
F2FS seems to work fine on data - I still use it on cache only.
Click to expand...
Click to collapse
Working fine here.
I have the rom flashed and everything looks good with cache and data converted to F2FS. However I am experiencing an odd issue. When i first set up the tablet I sign in with my gmail account and everything looks good. I do a clean setup so nothing restores and download the official gmail from the play store. Once it installs and opens it does not seem to notice that my google account is configured. It asks me to add a mail account and if i put the same account in it says the account already exists. I've factory reset this 3 times trying something different each time thinking maybe I did something dumb. Flashed many roms before and never seen this, any ideas?
---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------
followmsi said:
You can try to resize file system of system partition inside TWRP to get full partition size.
Or use the Update.zip_resizefs_flo.zip inside the download folder.
Works for deb too.
Cheers
Click to expand...
Click to collapse
dumb question but what does the partition resize change it to? I was looking to find a stock partitioning sizes vs this script chart or explanation.
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
******************************************
Hi there,
This is the official build (beta) based on TWRP sources and xiaomi blobs ... fully working !
(Mi CC9 meitu Edition)
!!! IT'S NOT MY PROBLEM, IF YOU DON'T READ AND FOLLOW MY INSTRUCTION CAREFULLY, IF YOU DON'T HAVE TIME FOR THIS, OR IF YOU FLASH SOMETHING OR DO A MANIPULATION I DIDN'T MENTION HERE !!!
Installation Procedure (first time) :
- Unlock your bootloader D)
- Enable ADB from your Official MIUI Developer option
- Plug your USB cable to your Windows PC and type :
adb reboot bootloader
- type then :
fastboot flash recovery twrp-3.3.1-0-vela-final (auto-decrypt).img (rename your image just by twrp.img)
fastboot flash vbmeta vbmeta.img
fastboot reboot (keep Vol+ pressed until you see TWRP splash)
- Wait for decrypting ... (if already you set a lockscreen pattern or a fingerprint)
- Format Data (button on the right) + Type "yes" on the keyboard popup
- Reboot
- To boot TWRP from MIUI : reboot menu + keep Volume UP pressed.
- To boot from phone off : power button + Volume UP
TWRP can now auto-decrypt your crypted /data partition so you can make backup with no issue.
This is a big fix that prevent to loose your fingerprint and pattern ...
For MIUI users, you must flash the fstab.zip fix after flashing your MIUI rom !!!
Enjoy ! :good:
Update : 2019-11-05
-version : 3.3.1-0
-busybox update
-terminal fixed
-stable and optimized : setting lockscreen pattern and fingerprint on the first boot is no longer needed !
BE SURE WHEN YOU WIPE YOUR DATA, YOU KEEP THE "4 FOLDERS BELOW + .layout_version". THESE ARE YOU ENCRYPTION DATA. IF YOU DELETE THEM, YOU WILL NOT BE ABLE TO RESTORE YOUR DATA BACKUP UNTIL YOU FORMAT YOUR DATA AGAIN.
TRICK TO SAVE YOUR LIFE : ALWAYS KEEP YOUR BACKUPS ON THE EXTERNAL STORAGE !!!
!!! This recovery is only for flashing "vela" roms in the future. Don't use it to flash pyxis roms. For this, use pyxis recovery instead !!!
Download
link
XDA : DevDB Information
TWRP, Tool/Utility for the Mi CC9 meitu Edition (vela)
Contributors
gringo80
Source Code 1 : https://github.com/TeamWin
Source Code 2 : Prebuilt Recovery Kernel from MIUI
Version Information
Status : Stable
Release Date : 2019-11-05
Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.
yotamy said:
Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.
Click to expand...
Click to collapse
It's working now. Thanks
I think it works
gringo80 said:
It's working now. Thanks
Click to expand...
Click to collapse
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?
yotamy said:
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?
Click to expand...
Click to collapse
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !
thanks. Some QA
gringo80 said:
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !
Click to expand...
Click to collapse
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam
yotamy said:
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam
Click to expand...
Click to collapse
this is not a bug. you have to format data after installing twrp.
from twrp homescreen, go to :
Wipe > Format Data (on the right) > type yes from the keyboard
TWRP don't support backup/ restore from encrypted files/folders. You must decrypt by formatting data !
Reboot to system. Install and config your rom then go TWRP to make backup !
Always put your roms and zip on the External SD Card... or sideload them by adb cmd from your windows PC !
Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !
sorry. i dont understand
gringo80 said:
Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !
Click to expand...
Click to collapse
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?
yotamy said:
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?
Click to expand...
Click to collapse
lol
it's inside the zip. go to my mediafire link. you will find everything
yes you flash it on twrp
i cannot thank you enough
thanks again
New Update (TWRP auto-decrypt)
yotamy said:
i cannot thank you enough
thanks again
Click to expand...
Click to collapse
Please update you TWRP ! (Highly recommended). Read OP carefully !
Thanks
:good:
You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp
yotamy said:
You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp
Click to expand...
Click to collapse
Yes, the fingerprint and the lockscreen pattern.
Follow the instruction on the OP !
Are the font files related to this twrp?
There are 2 font files in the link
yotamy said:
There are 2 font files in the link
Click to expand...
Click to collapse
NO, for the roms !
Speaking of roms.....
yotamy said:
Click to expand...
Click to collapse
work in progress
now its working good
gringo80 said:
work in progress
Click to expand...
Click to collapse
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam
yotamy said:
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam
Click to expand...
Click to collapse
Don't delete TWRP folder on your internal storage, to keep your TWRP settings.
3 way reboot is framework related. Sorry i don't support MIUI for now because i'm busy with GSI. Try to download "Simple Reboot" from the playstore.
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.0 or newer for root (after first boot) - (Download from here)
First time installation:
You need Unlocked bootloader for install
step 1 Download crDroid from the link, if you want root then download Magisk also and copy it all to your Phone internel or external your choice.
step 2 Go to recovery when you didnt installed it already download it from the listed link, go in fastboot with all 3 keys pressed hold then select with volume keys Download mode and hit power button,
When youre on Windows download adb minimal and fastboot here in https://forum.xda-developers.com/showthread.php?t=2317790 install it , open the shortcut on your desktop if one was created when not just serch in Windows for minimal and you will find it.
step 3 Type in the opened command prompt in minimal adb and fastboot: adb devices to check if device was recognized, when not download here the drivers to make sure it works fine https://downloadmirror.co/1LnA/HTC_Driver_v4.17.0.001.zip?pt=SCTaNyN4GCn3NIchsd7q3hM7hBYxuFbGvjQe9voyZY4= run it let it install then type again fastboot devices make sure you see some numbers like FA53WYJ13710 then it works fine and can start flashing.
step 4 Go to your download folder and search for twrp-3.4.0-0-hima.img rename it to twrp.img to make it easier for you to flash. copy the renamed twrp.img to C:/Program Files (x86)/minmal adb and fastboot/
step 5 Type in your Minimal adb Fastboot prompt: flash recovery twrp.img after OK type fastboot reboot bootloader and select with volume keys recovery and hit power button, congrats youre in TWRP recovery
step 6 Now you can make A backup of all your stuff when you have enough Disk space on your Internal or External storage when not make space on your SDcard or Internal storage and copy all your stoff on your Computer to make Space for a backup of your Data =apps and settings System = current Android. when you have Done that part go to install and select the Download Rom install it and if you want root then also The Magisk.zip props go out to https://forum.xda-developers.com/member.php?u=4470081 thanks to him for for his Makgisk root solution :good: and after all installed hit Reboot
Update installation:
You can dirty flash it if youre on android 10 and youre lucky it will start without apps crashing.
If you dont want to get Dirty then you youre fomat Data and System in TWRP and flash the Rom also you can make a Backup current Rom if you want.
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/Claymore1297/android_kernel_htc_msm8994
Download:
ROM crdroid.net
ViperFX Profile for Speaker
Unzip_me_not_flashabel
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
ViperFX is included and fully suporrted,
just disabel AudioFX or turn on legacy mode.
I dont recommand both together couse (loud bugs)
For those peopel who download over phone i suggest to turn Desktop Mode ON in Browser settings to be abel to Download directly.
Known issues:
Only FM not working, if found something
share log and we will see
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Here some pics
Edit: The rom is newer then the pics, this are just Sampels i created a while ago
https://ibb.co/BjCbGCV
https://ibb.co/HXNCPTh
Thanks to:
- Claymore 1297 and his Team for the work on the M9, without him it wouldn't be possible!
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
ROM OS Version Android 11
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: Lineage
Version Information
Status: Stable
Created 2021-05-11
Last Updated 2021-11-18
Thank you for the great work!
The gapp link is for android 10. Is it good to go on android 11?
Oh, yeah i replaced them. 10 from opengapps not work doe SDK. Nikgapps should work but remember when flash new rom also to flash Nikgapps again , in recovery it will say it will backup and install again but in the end it can lead to bootloop so after a New Build flash Nikgapps again or it will not start. i just looked at Opengapps they dont have 11 there. Or when you want to ungoogel go to /data/app and find vendig or venedig apk and delete it from Recovery in Advanced settings. So it should start without need to flash of Nikgapps
Does not boot for me, even on a clean flash, just reboots with a "TSENS reset" error
Edit : After flashing it like 10 times for whatever reason it booted up just fine, will use it some time and then give you my thoughts
Edit1: After trying to install gapps, the phone crashed on boot with the same error, like 5 reinstalls later, still doesnt work, maybe it could be because my phone is hot, i think TSENS means Temperature SENSor, ill let it cool off a bit.
Edit2: After cooling down the phone shows a different error "KP: EDAC cache: UE instance:cpu7 block L2 'A57 L2 Uncorrectable Error'
This was a very cool rom for the 30 minutes that it worked, i wish i could use it, hopefully you fix these issues.
I wiped everything, installed ROM, but always reboot after logo screen.
firmware 4.16.709.3
twrp 3.4.0.0
Seems very interesting, i tryed before upload and it worked fine by me , but i will now clean flash it and try by my self. I already have the newest build, build and will check these dont forget to thx Claymore to make this possibel
In this rom i have disabled some cores and set some Voltages to enlarge battery and normal performance.
Also i replaced the Camera app to OpenCamera couse this is just a better app for photos and sharpines, also 4k is supported in OpenCamera.
Realy looking forward to the new build, thanks!!
ps: I also flashed twrp3.5.2.9.0, NikGapps, BiTGApps, opengapp test builds...but no luck.
tombbb said:
Realy looking forward to the new build, thanks!!
ps: I also flashed twrp3.5.2.9.0, NikGapps, BiTGApps, opengapp test builds...but no luck.
Click to expand...
Click to collapse
What youre mean with no luck ?
Was it booting before Gapps ?
@tombbb
platinumthis said:
What youre mean with no luck ?
Click to expand...
Click to collapse
I mean the phone doesn't boot into system, keeping reboot.
platinumthis said:
Was it booting before Gapps ?
@tombbb
Click to expand...
Click to collapse
no, I tried only flash Rom, same reboot loop.
tombbb said:
no, I tried only flash Rom, same reboot loop.
Click to expand...
Click to collapse
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
platinumthis said:
Was it booting before Gapps ?
@tombbb
Click to expand...
Click to collapse
yeah for me too, it did boot one time but after that it never booted again, with gapps or without.
pinckston said:
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
Click to expand...
Click to collapse
Just FYI, I tried flash lineage 18.1 along with opengapps at last, and it booted normally. But I really want to try crDroid.
tombbb said:
no, I tried only flash Rom, same reboot loop.
Click to expand...
Click to collapse
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
tombbb said:
Just FYI, I tried flash lineage 18.1 along with opengapps at last, and it booted normally. But I really want to try crDroid.
Click to expand...
Click to collapse
Crdroid worked first time here, no issues. I wipe cache, dalvik/art, data and system. Then line up the zips - rom, nikgapps core, magisk.zip and execute.
It booted first time, in less than 5 minutes. I then opened magisk and allowed it to complete and update. Then booted back to recovery and flashed my migrate-gpe zips and rebooted. No issues at all.
Are you wiping caches after install but before boot? If so, don't. Odexed roms (most are now, I believe) won't boot if caches are wiped, I think the rom needs the art cache to be precompiled and this is deleted with a cache wipe.
All I've got I'm afraid!
pinckston said:
I've literally just flashed with core nikgapps and using migrate-gpe to restore apps. Done in less than an hour, only error was migrate-gpe couldn't restore chrome. Everything else is flawless. I'd suggest starting over with a ruu firmware flash and start again from vanilla stock.
Crdroid worked first time here, no issues. I wipe cache, dalvik/art, data and system. Then line up the zips - rom, nikgapps core, magisk.zip and execute.
It booted first time, in less than 5 minutes. I then opened magisk and allowed it to complete and update. Then booted back to recovery and flashed my migrate-gpe zips and rebooted. No issues at all.
Are you wiping caches after install but before boot? If so, don't. Odexed roms (most are now, I believe) won't boot if caches are wiped, I think the rom needs the art cache to be precompiled and this is deleted with a cache wipe.
All I've got I'm afraid!
Click to expand...
Click to collapse
Also, if Lineage 18.1 boots, maybe try flashing CrDroid over Lineage (same base)? And, as a second-to-last resort (last resort is ruu flash) you could try format data in twrp. This is the bottom right button in the wipe menu - it WILL nuke your internal memory so make sure everything is backed up first. Using a pc you may then have to sideload the rom and gapps using adb, so I'd recommend an sd card. I've solved similar issues in this way.
pinckston said:
Also, if Lineage 18.1 boots, maybe try flashing CrDroid over Lineage (same base)? And, as a second-to-last resort (last resort is ruu flash) you could try format data in twrp. This is the bottom right button in the wipe menu - it WILL nuke your internal memory so make sure everything is backed up first. Using a pc you may then have to sideload the rom and gapps using adb, so I'd recommend an sd card. I've solved similar issues in this way.
Click to expand...
Click to collapse
Thanks for the useful suggestions ! I will first try flash crDroid on lineage and see if it works.
edit: flashed crDroid on lineage, then boot loop again.. I'll see what else I can do...
tombbb said:
Thanks for the useful suggestions ! I will first try flash crDroid on lineage and see if it works.
edit: flashed crDroid on lineage, then boot loop again.. I'll see what else I can do...
Click to expand...
Click to collapse
Did you tried to format /data and then install without gapps ? will this work ?
platinumthis said:
Did you tried to format /data and then install without gapps ? will this work ?
Click to expand...
Click to collapse
I always format data, wipe data,system,cache, install rom, gapp, magisk. But I will try again, maybe flash new build.
What I don't understand is why lineage ROM works?