#-------------------------Disclaimer----------------------------#
I am in no way responsible for dead NAND/EMMC chips, SD cards Lost basebands, nuclear war or anything else for that matter YOU the users are soley responsible for any and all actions you make the build is 100% tested & confirmed working on UBIFS R11 max chinaphone with board variant Q6_M144_GT-018_MB_1.0
#-----------------------Device info----------------------------#
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
Board Variant: HS_Q6_MB_V1.0
Storage Capacity=512Mb (4Gb ext through recovery)
Ram Capacity= 497Mb
Resolution= 480×854
#-----------------CyanogenmodOS--------------------------#
Version = 11
SDK-ver = 4.4.4
SDK-API = 20
B-TYPE = userdebug
Build id = XNG3C
Linux Kernel = 3.4.67
LCD- density = 240
LCD-Dpi = 320
• Deodexed
• IO_scheduler set to CFQ
• Performance adjustments
• Preloaded with Gapps
• Cyanogen account support
• CyanogenMod Logo
• Ram flag optimisations
• Default runtime set to art
• Voice unlock support
• Pre rooted with Cyanogenmod SU 1.34
• addon.d support
• init.d support
• BT NFC support
• addon.d & init.d slinked in cpio in bootimg
• Custom CM bootimg with storage fix.
• Ad and popup blockers
• CM ambient updater
• CM InCallUi
• google voice search
• CM Device management
• CM SetupWiz
• factory test mode [ *#*#0#*#* ]
• CM Live lockscreen
• CM MusicFX
• CM Trebuchet Launcher
• Chrome based browser
• CM Voice +
• Voice command support
• Camera interpolated and tweaked
• camera path changed to added cameraserver in vendor/bin/cameraserver instead of system/bin/mediaserver
• Added Clearmotion props to default & build.prop
• Added Clearmotion config to /etc
• Added Clearmotion support libs
• Added Clearmotion FW to /lib
#---------------------------NOTICE------------------------------#
I do this in my free time DO NOT ask for Eta's,
Includes storage modified CM boot.img which will be flashed with the rom please use the partiton sd card option in advanced options in recovery to make up to a 4096mb /data partition before transferring zip to sd and flashing.
#----------------------------BUGS------------------------------#
• update #003 is having a whinge with storage for downloaded apps from store so they wont install after download will be fixed in build #004,
• NFC is working properly but you must purchase NFC bluetooth module tags to support nfc transfer, i have compiled & added an nfc.ko module to use bluetooth instead of newer modules which use the wifi reciever as the antenna and due to there being no NFC compatibile HW on these extremely poor low end devices i do not wish to see comments about this as a bug.
#-------------------------LINKS------------------------------#
CM CTR recovery.
https://drive.google.com/file/d/1UErBsSe2DLFEtcgwXz-hZR_fQINxpn9H/view?usp=drivesdk
Stock touch recovery to replace original
https://drive.google.com/file/d/14Y-WQHDLfqlEdjmu-PTujNqGkkUpcpLn/view?usp=drivesdk
CyanogenmodOS #001-BETA 20190412
https://drive.google.com/file/d/1Xuf-gSHPHr5CGsZjFu3pgT44FdR5GFx5/view?usp=drivesdk
CyanogenmodOS update #002 20190414
https://drive.google.com/file/d/19Nt1pVo8ruvTCugsgejtMQvJDe2xZIb7/view?usp=drivesdk
CyanogenmodOS update #003 20190504
[ Has play store issue ]
https://drive.google.com/file/d/1D4sCf1oflvSTFJxFzH1WwMJL_1j8H5-G/view?usp=drivesdk
Welcome to CyanogenMod 11
BUILD #002 is up get it from the OP
CHANGELOG
Camera works now with slow motion & fast motion video recording, picture quality is still **** but is tons better than it was on stock rom.
Rebuilt the system layout and merged most /vendor files and folders to /system
Fixed gallery keeps stopping error even though it wasnt
Cleaned up the GUI scaling to produce cleaner icons etc etc changelog is in /etc for anyone that wants to look
Changed the Live lockscreen wallpaper to something much simpler & better looking.
Converted entire system to single sim & removed Gemini where i could & set props to disable what i couldnt find of it, repathed ril to run through mtk-ril.so also added init.volte.rc, volte_imsm.so/volte_stack.files to help ril call clarity as certain parts of the stack are interacting with ril even though its a GSM Radio
Added getenforce & setenforce to /bin and file_contexts to try and get my init.rc props for setenforce to run the kernel permissively for some extra init processes, BUT setenforce for some reason is receiving permission denied cannot symlink so i hope to have this completed & working in build #003
Added /product/build.prop dir to deal with zram for swap & ext4 /data partitiion under logical boot partitions.
Added new android apple crime screen power off logo
Added some misc ringtones, notification tones and ringtones other than the cyanogen tones.
Nice Work Matty1993!!
You have been a busy bee :highfive:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
bigrammy said:
You have been a busy bee :highfive:
Click to expand...
Click to collapse
Haha yeah one of my old projects ive been meaning to get finished for ages, finding out how to attach android to UBIFS on top of UBI was a pain in the ass lol got to experiment with ril on this one as it was dual sim and tried running gemini through it but as it was a source build dual sim compatibility dosent work so had to depract gemini and set single sim still been working on the tuba build tho taking my time with it as sony really like to mix things up, also finishing a lineage OS 14.1 build for Alcatel Pixi 3.5 that was from source also but dualsim works on this one even though this phones a single sim phone haha go figure lol
DJ Robby said:
Hello,
I am new to ROMs, Could you give me detailed instructions on how I would install this?
Thanks,
Robby
Click to expand...
Click to collapse
What model is your R11 max clone phone it must be HS_Q6_MB_V1.0 board revision or it wont boot on your device and i will need to build one for your revision if so as the kernel will be different,
You can find the board variant by taking the backing off the phone and looking at the sim slot see pic attached,
Check this out first or youll brick it 100% i gaurantee it, google how to take a firmware backup using SP flash tool before doing anything SP flash tool can be downloaded from here aswell as the MTK Vcom drivers for flash tool,
https://spflashtool.com
If your board is different i need the BOOTIMG.file from your SP Tool backup so please do this first before anything or i wont be able to build you anything as i need your stock kernel from boot.img to decompile and make changes for my rom aswell as the boot.img is highly modifed with CM source
Hello,
I can't find a number like that, I looked everywhere.
Here is a full backup of the phone: https://drive.google.com/file/d/15P9KutXb0FrxHRTj4qrQ-KW94XA6J2SI/view?usp=sharing
The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
DJ Robby said:
Hello,
I can't find a number like that, I looked everywhere.
I have the boot.img, I will edit this message with the boot.img when I have a chance. The kernel is the same though because if I go to settings it shows the same kernel number as the one in this post.
Thanks,
Robby
Click to expand...
Click to collapse
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Matty1993 said:
Hey mate the kernel number may be the same but the config of the kernel will be diff, if it dosent have a number in the sim slot it will deffo not be a HS_Q6_MB you may have the ZMA_12_MB or ZMA_9_MB board
So deffo dont flash any of this stuff if you get me the stock boot.img & recovery img from your R11 max i can build the recoveries and rom for your board revison just upload them here in a .zip file when you get the chance
Thanks
Click to expand...
Click to collapse
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Hey mate,
Sweet ill get onto it and post link here to a new thread ill make for your variant r11 max.
Ive got a new build just about ready also which is build #003 so ill start your variant from #003 which has vast improvements from build #002
# edit
Glad you didnt flash your R10 is eMMC ext4 fs and not ubifs just finished the boot.img off anyhow
DJ Robby said:
I added the link to a full backup of the phone through the SP flash tool on my above post which includes the boot.img and recovery.img, Also thanks so much for all the help!
Click to expand...
Click to collapse
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Matty1993 said:
Try these recoveries tell me if they boot uo and everything is ok with them
Oppo touch recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1ZUZ3jmNhVkWSTB-57ifPh9_Lmm_jjkCB/view?usp=drivesdk
CWM recovery for R10_zm19e_eMMC+ext4
https://drive.google.com/file/d/1WO44rtoWttfeeAvCdff_97JqbuXboeXB/view?usp=drivesdk
Open sp flash tool & load your scatter file,
Then click on the recovery path and load a recovery into the slot,
MAKE SURE that download only is selected and NOT format all + download this is very very important
Click download with phone switched off plug into pc & recovery will now flash,
Once flash is complete remove then re insert the cord wait for the charging screen to appear,
You can now boot to either recovery by holding the volume up button and power button until the first boot logo appears then release only the power button and keep holding power up to see if they will boot or not,
If they boot all sweet ill upload the rom as its just about finished being built
Click to expand...
Click to collapse
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
DJ Robby said:
I can try when I get home but I already got TWRP with the Easy Magic Installer except it is an older version: https://forum.xda-developers.com/showthread.php?t=2798257
Click to expand...
Click to collapse
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Matty1993 said:
More or less just to test for device compat is all glad you told me youve got TWRP tho as my rom dosent have mount asserts in the script as they were causing error 7 so ill have to rebuild the meta-inf again as ive got set for perm aswell whereas TWRP uses meta-data to set file permissions
Click to expand...
Click to collapse
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
DJ Robby said:
So when do you think the ROM will be ready?
Edit: Oppo Touch Recovery works, I'd rather not bother with CWM if that's ok? And if you could port a TWRP instead of Oppo Touch Recovery I would appreciate that since it is more advanced.
Click to expand...
Click to collapse
Rom will be ready soon it takes time to convert things to ext4 from ubifs patience is a must for these things unless you want a brick ? Lol plus ive got another 5 projects on the go so lots to do and not enough time to do it all, just finished lineage 14.1 android 7.1.2 for alactel pixi 4027A using a stock kernel on android 4.4.4
as for TWRP probably not due to the size of your recovery and the size of most twrp is about 3mb to short for your partition youll need to use cwm ive added mount points to the script for your data & system partitions so if it dont flash mount in CWM and then flash if it still dosent use the take a log option in my installer and forward it to me so i can see if it was the mounts or what,
Also i havent set meta-data for permissions ive set perm & perm_recursive which is specifically for CWM so please flash with that,
I make no gaurantee it will boot as i dont have one in front of me to work on & debug but everything should work ok though link will be up in roughly half hour max
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Matty1993 said:
Links up tell me if it installs and boots ok is based off my cyanogenmod 11 new unreleased build #003 for ubifs
CyanogenMod 11 R10
emmc + ext4
BETA TEST BUILD
https://drive.google.com/file/d/1CvP3TPjo5fxXi6tHKI388WFN5KnWTyZ4/view?usp=drivesdk
If it dosent flash remember to get the log from my modified installer
if it dosent boot past first logo tell me it will be fstab issue which ill need to adjust
If it gets stuck on infinite bootanimation tell me ill need to adjust the vold
If any errors just flash back your backup with SP flash tool using download only mode and youll be back up and running with it until i get it fixed if it does need fixing.
Click to expand...
Click to collapse
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
DJ Robby said:
So does that mean Oppo Touch Recovery is useless? So I should just put CWM in the recovery and then flash the CyanogenMod11 with CWM If I could get more detailed instructions that would be helpful as you know I am a noob...
Edit: So I flashed it with CWM and it failed, Here is the log: https://pastebin.com/i2F55g08
What I think happens is the first image that says welcome comes up, Then the boot animation comes up but it doesn't finish before returning to the welcome image that was at the start and it stays on that forever.
Edit 2: I also don't know how to restore the backup with SP Flash Tool but that is ok since this isn't my everyday phone so i'll just wait until you fix the ROM.
Click to expand...
Click to collapse
Hey mate i took a look at the log,
For some reason it didnt symlink any of the system files or set the perms for them
Modified boot.img didnt flash either for some reason so surprised it started playing animation so all my adjustments from ubifs to ext4 must be correct
In the script
Format was ok
Mounting was ok
Extract system files was ok
I think it may have something to do with CWM possibly as thats the only reason its not booting none of the files have correct perms everything else went ok though, so ill see what i can do today about another recovery for you,
The oppo touch recovery is just a stock recovery i added to get rid of the 3e recoveries these phones originally come with, much nicer is all,
To restore your backup using SP flash tool open flash tool, select the scatter box,
Navigate to your backuo folder & double click on the scatter_file.txt,
All of your partitions and files will automatically load up for flash,
Change the download mode to download only
Power off phone click start download
Connect phone & wait for flash
I will just wait for the new Recovery and ROM to work because like I said before this is a device that I didn't use at all but I will probably use it once I get the ROM. Again I just want to thank you for all your help since because of you I don't need to throw out this horrible phone.
Related
CyanogenMod
CyanogenMod is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android-based firmwares of vendors of these cell phones.
Not Working:
FM Radio
Sources
Device: - https://github.com/SaNek011/android_device_huawei_u8500
Installation
Install ClockworkMod recovery
Boot into recovery using the 3-button combo (Call+Volume Up+Power button)
Wipe (wipe data/factory reset + wipe cache partition)
Install the ROM from the SD card using ClockworkMod Recovery
DOWNLOAD ROM - UPDATE_10
DOWNLOAD CWM
CWM 5.0.2.8 by $aNek011 (Fastboot version)
CWM 5.0.2.8 by $aNek011 (Recovery version)
DOWNLOAD Google Apps
GoogleApps - http://goo-inside.me/gapps
Changes:
Update_10:
Updated CyanogenMod Sources
New Wpa_supplicant v.0.6(Allows you to connect to hidden networks wifi)
Updated Kernel (It has become even more productive)
Patched audio library, new audio filter (sound became clearer) - http://review.cyanogenmod.com/#/c/17091/
-----------------
Update_9:
Updated CyanogenMod Sources (19.06.2012)
------------------
Update_8:
Kernel([email protected] #4)
Added HTC driver vocpcm.c
ZRAM Removed
-----------------------
New boot-logo
Auto-start load_oemlogo
Recompiled opengl
Added RAMZSWAP
Update_7:
Repo sync(14.05.2012)
Added CIFS to kernel
Added TUN to kernel
Working RomManager
Updated RomManager
Updated keylayout
Updated RootExplorer
New Splash Logo Huawei + auto-script SplashLogo
Update_6:
ZRAM(Integrated to kernel)
New libaudio
New Audiofilter
Update_5:
Repo sync (19.04.2012)
Fixed Brightness
Update_4:
Repo sync (18.03.2012)
Enabled JIT
Interface usb modem rndis changed to
Replaced by a camera on the original from the android 2.3.7
Proximity Sensors tweaks
Update_3:
Repo sync(15.03.2012)
New kernel
Optimized apk files
Unlock lock screen by pressing the MENU key - Disabled
New gralloc,copybit,lights,sensors
Update_2:
Repo sync (11.04.2012)
New libaudio
New AudioFilter
Updated kernel
New keylayout and keychars
Thanks
aorth - for device tree
psyke83 - for device tree
tilal6991 - for device tree
BPaul - for helping with development
destruct0r - for assistance in the implementation of htc vocpcm driver
Good work!
Good work! Keep up!
Whats new is in the update7?
______________________________________
[Send by Tapatalk 2 from my u8500]
Posted ClockWorkMod Recovery 5.0.2.8
thanks
My father thanks you
Today should be posted Update 7 By $aNek011!
added UPDATE_7
$aNek011 said:
added UPDATE_7
Click to expand...
Click to collapse
i'll try IT!!
I hope with this update, sygic gps mobile now works....
$aNeK! have you any idea for more of free ram?
not swap
Hi $anek!!
Any idea to work WIFI, because in wifi, options advanced say:
Macadress: no avalaible....
have u activated wifi?
mine is working just fine
NAZUnlimited said:
have u activated wifi?
mine is working just fine
Click to expand...
Click to collapse
yes, but no work!!!
in advanced option say: Macadress no avalaible........
can you help me and teach me , how can you done it?
moche_bcn said:
yes, but no work!!!
in advanced option say: Macadress no avalaible........
can you help me and teach me , how can you done it?
Click to expand...
Click to collapse
The mac isnt available because wifi is disabled
I'll suppose that one of these options is the one u experience
A) u turn wifi on and after a few seconds it say error
B) u turn wifi on and it auto-disable itself even before showing wireless networks or giving any error
Either one, in most cases, result from a bad flashing or the wifi files have the wrong permission, since i dont want to make u go to a goose chase after the permissions, flash the rom again but before do a full wipe (the normal + format boot + system. They are the advanced option) and fix permissions before reboot
Sent from my U8500 using xda premium
Muito Obrigado!!!
I am spanish speaker..
I'll try it!!!
Hi !!
Now work the wifi...
One question?.....
can I change in the nvram.txt,(In the path system/etc/firmware) the
macaddr=00:90:4c:14:43:01 for my macadress of my phone??
Can I add too direct to the folder system/app the current apks from google(googlequicksearch.apk, voicesearch.apk, vending.apk,maps.apk,etc) ? before install...
doing so, Can the ROM works?.....
Funny thing, in the other rom someone asked about the mac address too
In theory, u can do that, i havent tryed that, mine reports the correct mac (some things in every rom are weird, different results for the same kind of phone)
about gapps, yes, u can flash those apps at the system folder but before doing that, check if u have enough free space in that folder. Use the root explorer, enter that folder and see how much free space is there ( it is written above the file listing) and compare with the size of those apps. The rom just needs 10mb of free space in system to boot without any problems. Download the gapps zip for gingerbread and paste them inside the app folder of that zip and flash it. This way, if u want the updated versions of those, u can place them in the zip and flash, the new ones will replace the old ones. Just remember to fix permissions before reboot.
And yes u can flash them after flashing the rom, it wont affect boot just the time it needs to start the 1st time. Will take a minute (give or take) more to boot (more apps mean more time to write the dalvik cache, but it will only do that the 1st boot)
Sent from my U8500 using xda premium
hi
respect to fastboot
What is it for? can you teach me more about ?... forgive my ignorance.....
I just know to install the ROM's and clockwordmod ...
by the way, I installed the CWM 5.5.0.4 of $anek011
Update
I have to install all updates or just the latest?
Just the lastest
______________________________________
[Send by Tapatalk 2 from my u8500]
Base On stock otaJB4.1.1 JRO03D for Nexus7
Didnt sign this zip,before flash,check Ur reovery sign Verify switch off
Cause I'm chinese,sorry about my English
chinese user may go gfan,same post in chinese
=============Features/log=============
What's works：
Google Now (Seems offline voicedata not support nexus s now) only work in N7&GalaxyNexus
Every thing works.
=======================================
*1 deodex/zipalign
*2 busybox
*3 rooted by superSU(Chainfire)
*4 bettery% ，mostly like this
*5 Advanced Power Management (1reboot 2reboot to recovery ，long press recovery to BLmode)
*6 Camera join，works fine，(MODACO)
*7 Volume button wake up
*8 USBdebugging works fine
including full google services,but books/video/etc...not support my location,just download them from google play,that's easy
If anyone wanna disable the Nvbar,go check my app fullscreen toggle
This app madefor galaxy nexus,also support Nexus7
==========Download JB4.1.1 JRO03D =============
N7-Stock-OTA-rooted-deodex-zipaling-JRO03D.zip - 233.80 MB
Thanks for this. I'll give it a flash and let you know how it goes. Also, I think you're English is pretty good!:good:
Can I flash this ROM?
I unlock bootloader, flash clockworkmod and made root in my nexus 7, can I make OTA update to 4.1.1 or is better flash this rom in recovery clockworkmod?
What is the boot.img file?
My state is in the fallowing:
* BOOTLOADER *
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - 015d24a424042006
SIGNING - not defined yet
LOCK STATE - UNLOCKED
* SYSTEM *
Modelo: Nexus 7
Versão do Android: 4.1
Versão do Kernel: 3.1.10-g55edff4
Número da compilação: JRN84D
if. ota ,you need unroot first
Sent from my GT-P1000 using xda premium
What is the boot.img file?
What is the boot.img file?
kernel
Sent from my GT-P1000 using xda premium
Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!
Angst said:
Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!
Click to expand...
Click to collapse
I can't tell if you're trolling or don't know but the boot.img is the kernel. u wanna check? go look in the zip of the Trinity kernel b4 u flash.its boot.img..same with the Franco kernel or any other kernels.
examples of this can be seen with grub or lilo (linux bootloaders).
Hope this has cleared this up.
RED OR BLUE YOU CHOOSE !!!
Boot.img contains the kernel, believe the OP was just using that ad a shorthand explanation.
But the boot.img does indeed contain more than that. When unpacked it has all of the init.rc files and other essential system operations. If you build your own kernel, you can pack the boot.img and replace the kernel with your own newly made zimage.
<del>
Angst said:
Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!
Click to expand...
Click to collapse
Put the zImage from boot.img in your pipe.
This ROM won't even boot for me, which is really weird. Anybody else have that issue?
test on cwm6.1.0
Sent from my Galaxy Nexus using xda premium
Hello !
Currently i'm working in Le 2 kernel and device tree. My purpose is to make meaningful changes and additions so other ROMs can implement them.
Confirmed working with LOS, Carbon, LegendROM (latest releases)
This thread is all about the kernel. Currently the kernel features
sdcardfs support
cpu-input boost
power efficient work-queues
improvements to touchscreen driver, preparing support for dt2w
adj tree
low memory killer improvements
powersuspend driver
nvidia patches for energy efficiency
memory bus improvements
Adreno memory pools
and other small improvements in battery management and scheduler
Download: https://drive.google.com/open?id=0B4AOvCehd4v3OXBEX3dMSkdxQ3c
Source: https://github.com/mthomos/android_kernel_leeco_msm8976
To enable sdcardfs support just add this line in build.prop
Code:
ro.sys.sdcardfs=true
To be clear from the beginning: I will not answer to any feature requests and i respond to bug reports without logs. I hope to understand this
Cheers !
XDA:DevDB Information
Diades Kernel, Kernel for the LeEco Le 2
Contributors
marios199546
Kernel Special Features:
Version Information
Status: Testing
Created 2017-09-05
Last Updated 2017-09-07
What's the decryption key?
Good luck :good::good:
For which ROM?
Nice one.
Gonna try and report!
Its asking for decryption key!
OP updated with new link
Work on rom based in eui or only aosp rom ?
Sent from my Le X522 using XDA-Developers Legacy app
fmehdi said:
Work on rom based in eui or only aosp rom ?
Click to expand...
Click to collapse
Doesnt work on eui base
Only custom roms
What does sdcardfs mean?
bonsai.14 said:
What does sdcardfs mean?
Click to expand...
Click to collapse
https://www.xda-developers.com/divi...les-fuse-replacement-will-reduce-io-overhead/
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
billybobjoe512 said:
I probably shouldn't be here this looks complicated but how do you flash the .img files? Are they even supposed to be flashed
Click to expand...
Click to collapse
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Njishi said:
Sounds like you're new to this. When you boot your device into recovery (TWRP to be specific). You will see a option"Install", click over there then it will open up the local directory. And on the bottom right, you still see a option to select imgs file. Select that option and boom now you will see all your downloaded imgs files showing up there.
Note:- Make sure to choose a proper partition. For recovery. Img select recovery and so on. Taking a backup before you try something new is always recommended.
Click to expand...
Click to collapse
So where would I flash these .img files? Or do I have to do something else before flashing
billybobjoe512 said:
So where would I flash these .img files? Or do I have to do something else before flashing
Click to expand...
Click to collapse
What else you can do? Like going for a walk is recommended!?
You just have to boot into recovery. And then flash them like the way i said.
Or else you can use this app.
https://youtu.be/6IMvOCUy2Wc
You can also flash .img via fastboot with this command : fastboot flash boot <file_name.img>
Also if you have magisk installed you have to flash again the magisk install every time you install a new kernel.
I am a bit of a noob so I'm probably doing a ton of things wrong here
So how long does it take to start up the device after flashing the kernel? I flashed to boot partition and I waited for about 10 minutes and I got impatient so I restarted and tried to take a logcat but it just said waiting for device so I just restored a backup that I had made
Did I mess up somewhere or do I need to have a logcat for this
Phone don't boot bro I waite d 20 min
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
marios199546 said:
Mine works perfectly, which rom do you use ? I have tested with LOS and Carbon and works flawlessly
Click to expand...
Click to collapse
Phone not booting. Stuck at Spash screen. Cant take logs (waiting for device).
------------------------DISCLAIMER------------------------
Flash this Firmware with SP flash tool at your own risk i am in no way responsible for any damage that can occurr flashing your MTK device with flash tools, such as
•Hardbricked devices
•Soft Bricked devices
•Lost imei or baseband issues
or anything else for that matter, you are solely responsible for the actions you make when flashing this firmware, however following instructions below you shouldnt have a problem with the device and you can enjoy your new updated R11 max Firmware,
There are 2 firmware builds at the bottom,
1st with google play store as an app store.
2nd with Aptiode store.
Choose which version you wish to select Google play version is labelled as GP & Aptiode store is labelled as AP.
______________________________________
This Samsung S7 themed Rom has been personally built by myslef with the base system of an R11 max chinaphone ive replaced almost everything.
DEVICE INFO
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
_____________________________________
REMOVED OR UPDATED
_____________________________________
• Cooee launcher ( spyware )
• Marshmallow game ( adware )
• Browser
• calander
• gallery
• camera
• music fx
• exchange2
• email
• Volume control
• framework.jar
• calculator
• music player
• File manager
• system/vendor apps/FBlite/Whatsapp
• Stock boot animation
• Stock shutdown animation
• Stock start tone
• Stock Shutdown tone
• Stock UI sounds
• Stock Notifications sounds
• Stock Ringtone Sounds
• Stock Boot Logo
• Libs from removed apps
• framework from removed apps
• -res from removed apps
• Build.prop (Edited)
• Test Keys (they should be release)
• Wallpapers
• Live wallpapers
• Network Restriction lock (network Lock )
• Modem (connectivity & imei issues )
Plus alot more crap removed that i cant remember right now....
___________________________________________
ADDED OR REPLACED
___________________________________________
• updated Launcher for G930F Ui resemblance.
• Lightning Browser (looks like chrome)
• gallery V1.1 with photolocker
• Modded Camera FV-5
• JRD Secure container
• JRD plugger
• Updated music FX
• JRD media container
• Samsung Boot animation
• Samsunf Shut Animation
• G930F boot logo
• G930F icons and theme
• Samsung G930F oreo Ringtone Sounds
• Samsung G930F oreo Notification Sounds
• Samsung G930F oreo UI sounds (where available)
• Build edited to display device as SM-G930F
• Fingerprint updated
• Updated to Release Keys (was test keys)
• updates -res
• root set to function without the need for Su manager app binaries can run themselves.
• UPDATED 3G modem to fix connectivity issues (pulled from HTC desire 310)
•Replaced some system apps and some other apps from and alcatel OT 5050 MT6575 for faster UI and system stability.
• SU Binary pre installed to system, no need for root manager
• BUSY BOX binary pre installed to system, no applet's are preinstalled though
Plus alot more stuff i cannot remember as i never made a changelog this is listed as release software as i deem it stable enough for daily use but as the system is customised it should be treated as Beta software, any bugs please report them to me so they can be fixed.
---------☆☆☆MODIFIED BOOT IMG☆☆☆---------
This Rom for now must use the modified boot.img & external SD card should you wish to use either of these roms due to a mounting error somewhere, no app will install despite there being 70mb + on both builds /data partitions so i need to fix, all works perfect with the modified boot.img,
Partition your SD card as follows using Mini partition tool with 2 partitions in this exact order EXT 4 Cannot be first or you will face data decryption error until rectified.
•PRIMARY partition
- FAT32 label it data
•PRIMARY partition
- EXT4 label it mmcblk0p2
To flash with modified boot.img open the scatter file, click on the BOOTIMG file path & select the modified boot.img,
Insert the newly partitioned SD card into the device and flash the firmware using the instructions on how to flash below.
__________________________________________
FLASHING THE FIRMWARE
__________________________________________
********This is a "UBIFS" filesystem*********
EMMC storage devices are NOT compatible
Unless you change the scatter to support your file system and even then it may require porting still.
•Open SP flash tool
•select the scatter.file
•insert the modified boot.img into BOOTIMG path
•change flash method to download only
•click start
•Wait for it to complete the flash
•Disconnect & Reconnect the usb cord
•Wait for device to start charging
•Turn on & enjoy
DO NOT USE "format all + download" in SP flash tool unless you have a backup of your firmware and security partition or you WILL lose your imei.
_________________________________________
LINKS
GP Build https://drive.google.com/file/d/1gpGH1Wj_JQHFFroV12r1PcHsxeE5zbTV/view?usp=drivesdk
AP Build https://drive.google.com/file/d/1VhZmpZyA-z-N6phAn9nfBifL-Lk0pdWL/view?usp=drivesdk
SP Flash Tool https://spflashtool.com
Modified boot is located within the .zip all credits to luca Roggero for his modified boot.img
can't get it to load with modified boot
i partitioned it as directed on a 32gb card flashed modified boot and it wont load also theres a weird glitch on this rom where once your battery hits about 20% it just instantly drops to 0 also cant install a custom recovery with easy magic (any of them) do u know the code to unlock the bootloader?
thinkotherwize said:
i partitioned it as directed on a 32gb card flashed modified boot and it wont load also theres a weird glitch on this rom where once your battery hits about 20% it just instantly drops to 0 also cant install a custom recovery with easy magic (any of them) do u know the code to unlock the bootloader?
Click to expand...
Click to collapse
Sorry for the late reply ive been busy busy busy making android 6.0.1 for the R11 max its almost finished,
Righto lets get started and get you up and running with the modified boot.img
Firstly how did you partition the Sd card, what partitions were they formatted to exactly and in which order,
They must be formatted in this exact order ill include the info aswell
Label: DATA
Format: FAT32
Type: PRIMARY
Label: MMCBLK0P2 (use lower case letters)
Format EXT4
Type: PRIMARY
i use mini partition magic and it works beautiful,
If the system boots on your device also it means that the boot.img is compatible with the device,
Which means that the modified boot.img is also compatible with your device as the original untouched works and all thats been done to it is the mount points were changed to the ext4 partition on the sd card,
This is everything that was done modifications to files were as follows
mount ubifs ubi @ userdata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mount yaffs2 mtd @ userdata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mount ext4 / emmc @ usrata / data -> mount ext4 / dev / block / mmcblk0p2 / data
mmcblk0p2 is the name of the 2nd EXT4 partition of the sd card, which must be second and not first
The sd card must have 2 partitions, the first FAT32, the second ext4, both primary
Try that and see if it works,
If it dosent boot past the power on logo message back here you may have another revision board as there are a few in which i have a boot.img for 2 of the R11 max boards so will get your phone working with whatever GB storage you set as your partition
Did you also make sure you have the NAND version of R11 MAX also as there is an R11 which is emmc and not nand ? There are 5 variations of the NAND R11 max and 3 or 4 variations of the R11
basic info on the R11 max 5 build versions
Storage type: NAND (typically hynix)
Flash Size: 512mb
DRam 478mb
Radio: 2G GSM
The only diffs for the ones above are the partition infos and the bull**** storage capacity,
Basic info on the R11, 4 build versions
Storage type: EMMC (unknown)
Flash size: 2.5GB
DRam: ( unknown )
Radio: 2G GSM & 3G UMTS
Let me know how you go and sorry for the late reply
Oh by the way what you think is a Glitch isnt actaully a glitch,
Theres nothing i can do about that unfortunately,
In the framework-res.apk battery stats are set in 15% increments to much work for me to fix on the status bar, go to settings then battery and turn your battery % on thats at least accurate
And in physical terms of the battery i hope you dont actually think there a 3000Mah battery,
They are actually cheap chinese lithium cells that produce only 1000Mah and dont last very long at all mine did the same thing around 20% if you know what your doing you can re cell the battery with a samsung cell or similar as long as you are very careful and dont put to much force on the pcb on top of the cell to much and desolder it properly you will have a working battery that actually lasts, i did it to mine but i run a phone repair shop, i dont advise you do it if you are inexperienced in that case find a replacement battery that is decent quality same same size and pin location and youll be sweet.
And about the custom recovery again nothing i can do about that ive built and not used any tools that dont work half the time with so many diff variations of custom recoveries ive made,
Ive packed them with twrp ramdisk and made all edits but they just refuse to boot and only flash white and reset,
The bootloader is pre unlocked as youll notice theres no OEM unlock,
However if you really wanna try yourself,
Connect to the phone via adb and use one if the commands below to get you into fastboot mode, thats as far as youll get though fastboot oem unlock hangs on waiting even though fastboot devices shows the device
Syntax:
adb reboot bootloader
adb reboot-bootloader
adb reboot fastboot
adb reboot-fastboot
Forget which one it is but you can try for yourself,
Ive been trying and trying to get a half decent recovery for the next 6.0 build its still stock but ive done alot of mods to recovery like enabling adb in recovery and redoing the default.prop within it also
guess i'll just hold out
well its working pretty good sans battery life, lol
are you compiling a real marshmallow build? because that will for sure solve the sdcard as internal issue and you can install gapps etc.... the playstore would work etc... it wasn't until marshmallow that google started letting you use your sd a internal, still an awesome job man i love this project, its a hobby of mine taking old bricked or soft bricked phones and trying to get them to optimal standards so far so good! keep me updated on the progress.
I definitely used minitool and followed your instructions to a tee i'm thinking 32gigs is too much for the boot.img i'm going to try and partition it smaller on the fat32 and see if it will boot then, how big do you reccomend i make the mmcblock0p2 partition? i made it 3 gigs could that be the issue? too big?
Hey mate sorry for late reply was finishing up another alcatel U5 custom recovery project,
Yeah battery life isnt the best, next build ive added scripts to optimise battery life, ram and a few other things,
With the build unfortunately i cant fit an entire 6.0 system on a 512mb flash nand it just cant be done unfortunately theres not enough space but im working on that for a later build so at the moment though next build will use SDK23 system components but it will also include mostly SDK20, SDK21 & SDK22 system components that ive managed to merge into it,
Either way the modified boot.img is neccessary regardless, Gapps and play store i can confirm does work perfectly fine on this next build and there will be roughly 50mb so a couple apps can be installed before getting the storage low warning,
Even it if were a proper dedicated 6.0 build though again it would still need the modified boot.img as even though the app has been placed on the sd card it still has to run through the main system at startup and a full memory at startup will not boot the phone so again modified boot.img is necessary,
Shouldnt matter what size you make the partitions either, these boards support up to 32GB TF cards so thats not a problem,
I have a 16GB i made 2 partitions as follows
Data 7.5GB FAT32 primary
mmcblk0p2 7.5GB EXT4 primary
In that exact order & spelt that exact way if it is still not working for you then it is purely a pilot error (being you) as i mentioned normal untouched boot.img packed in with the firmware works correct ?
That means the modified boot.img will work also they are identical apart from the fact that the internal storage has been mapped over to your SD cards mmcblk0p2 instead of your internal mmcblk0p2,
If it is still not working i want you to please take a backup of your firmware and then from that zip up the following into an archive upload it to google drive or whatever you use and post the link to it here so i can download it and have a look at it to see if there are any differences anywhere
RECOVERY
BOOTIMG
MT6572_Scatter_file.txt
I highly doubt there will be any difference as it already works on your PMT info if there were something wrong it wouldnt boot at all even with the untouched stock one,
The boot.img and recovery has been highly modified in the next build so if your facing any probs still ill need to sort it out and possibly make a second version to support it, hopefully not the case tho.
Attention all users of R11 max,
New build will be up in a week maximum, Google play is functional, i have also built a custom recovery for this model R11_Max however wont be released until the new rom is released.
Thread will be updated here with new links when its ready.
New rom is not far away now for the R11 MAX im just finishing up some minor touchups in the meantime i have built a number of custom recoveries for the phones due to 1 there not being any available at all for it & 2 all recovery porting tools do not work with this phone so manually built a number of different styles,versions etc theres TWRP, CTR, CWM, etc even an OPPO touch recovery even that i also managed to build enjoy,
https://forum.xda-developers.com/android/development/recovery-t3892041
Note all R11 max users,
A new rom will be released for this device by me in the near future when released it is advised to update to the latest build, modded with CM but stock 4.4.4 unfortunately that is all i am able to upgrade it to, 6.0 build i am scrapping for now i can get 6.0 apps to install but they just will not run most not at all,
Another note though ive managed to modify the boot.img some more to swap not only the data from
"ubifs" "UBI" "userdata" "/data" to
"Ext4 "EMMC" "/dev/block/platform/mtk-msdc.1/by-num/p2 (EXTERNAL SD)
but also system from
"ubifs" "UBI" "system" "/system" to
"ext4" EMMC" "/dev/block/mmcblk0p3" "/system" (SDCARD)
Not sure if i can get a rom functional to boot from it but TWRP recognises it aswell as mounts & formats it correctly, some useful info incase anyone else wants to give it a go also
All R11 users please be aware that a new build will be uploaded today or tomorrow latest which is a full AOSP CyanogenMod 11 flashable zip,
I will link the thread here was built for hs_q6_mb
But should work on all other variants as long as you use your stock boot.img
New thread will be linked here one completed and rom is uploaded
New rom is up link is here
https://forum.xda-developers.com/android/development/rom-cyanogenmod11r11maxmt6572ubifs-t3920315
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B]
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
A11 Testing:
https://build.twrp.me/test/coral/twrp-3.5.0-0-test1-coral.img
Please test and let me know if anything isn't working.
DOWNLOAD:
Please go to https://twrp.me to download the recovery image.
Old info:
Hello, this is a test build for coral users (will work on crosshatch/blueline later).
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
TWRP seems to be pretty stable now as of test 5. Missing features include adb sideload and repacking recovery which I will be working on in the upcoming months. Android 11 will be supported when stable APIs have been release and we have time to update to that release.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test4-coral.img
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test5-coral.img
- fix restoring of persist partition
- fix restoring of super partition
July FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test6-coral.img
- allow repacking of TWRP from boot.img
- magisk not working currently on repacked image
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test7-coral.img
August FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test8-coral.img
- fix repacking magisk with TWRP
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a base for Coral/Flame TWRP
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
These devices do not have a recovery partition. You will not be able to flash the img file directly to the phone. Make sure you use fastboot boot to temporarily boot TWRP and use adb to push it to the /sdcard folder for repacking.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_twrp_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Select your TWRP boot.img from /sdcard
5. Touch Install Image Recovery Ramdisk
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
Glad to see this!
Finally TWRPified! Thanks for bringing this to us!
bigbiff said:
[RECOVERY] TWRP 3.4.0-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
coral Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Hello, this is a test build for coral users (will work on crosshatch/blueline later). I was hoping adventurous people would try this fastbootable image out for testing.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up. Will check back later to see feedback. Don't try if you are unable to reset back to stock. Only try if you are curious to kick the tires.
June FW Date https://build.twrp.me/test/coral/twrp-3.4.0-0-test1-coral.img
http://twrp.me
Click to expand...
Click to collapse
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Daisymae said:
When trying to boot the image it gets stuck on the TWRP flash screen. I'm on a rooted custom rom. Sorry to sound stupid if I'm missing something obvious.
Click to expand...
Click to collapse
Same here ?
I'm stuck on splash screen as well, but I'm gonna try to push this thread in a more helpful direction with a detailed description and a logcat:
I'm on June radio/bootloader, running AOSiP, rooted with Magisk, build # QQ3A.200605.001
Here's the logcat of stuck @ splash
https://pastebin.com/sAMURQKw
If anything else you need tested or logged please don't be shy to tag me - I'm excited to see TWRP making its way here and I know it's been hard work. Hope the log helps and will gladly take more if it doesn't show the pertinent info you need.:good:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Surge1223 said:
I'll follow in Wrong Ways example.
Build: du_coral-userdebug 10 QQ3A.200605.002.A1 eng.surge.20200605.155815 release-keys
Probs wont do much more than this for now. But figured id upload to help the cause
Few things I thought I might add.
-manually adding libion.so to /system/lib64 allows you to get further but then it requests libandroidicu.so which is an apex/android runtime lib which isn't available since system isn't mounted
-toybox missing pigz always shows up
Click to expand...
Click to collapse
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
bigbiff said:
Thanks for the logs, I am working on getting our relink process working better so I hope to get that done soon to get all the built objects into the right space.
Apex files should be mounted and available before the decryption process happens. init is then configured to use these apex libraries for loading. It works locally but not on your pixels for some reason.
Can you post the results of mount -v?
Here is a new test image as well, I verified it on my own coral and it decrypted with pin: https://build.twrp.me/test/coral/twrp-3.4.0-0-test2-coral.img
Also this image is fastboot only. I need to work on installing into the ramdisk.
Click to expand...
Click to collapse
Sure, no problem. logs attached
Surge1223 said:
Sure, no problem. logs attached
Click to expand...
Click to collapse
Thanks, did you try test2?
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
bigbiff said:
Thanks, did you try test2?
Click to expand...
Click to collapse
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
Boggling my mind that it works on my coral with out linking issues.
Can you post the results of getprop please?
Surge1223 said:
yep
fastboot boot /Users/surge/Downloads/twrp-3.4.0-0-test2-coral.img
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
BTW, im stuck on splash whenever I try to do this, I thought decryption only took place when attempting to enter pin/pattern?
Click to expand...
Click to collapse
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
bigbiff said:
It might be something funky happening with qsecomd starting up. There is a whole orchestration of steps that might cause an issue unfortunately. Until we get things ironed out you might have to wipe via stock recovery a few times. I assume by splash you mean the white G screen?
Click to expand...
Click to collapse
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
Click to expand...
Click to collapse
Wait did you want getprop while in recovery or booted?
Surge1223 said:
I meant the twrp splash screen.
https://hastebin.com/ovamadoken.md
Could it have to do with the interface_start in relation to keymaster4?
---------- Post added at 02:23 AM ---------- Previous post was at 02:20 AM ----------
Wait did you want getprop while in recovery or booted?
Click to expand...
Click to collapse
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
bigbiff said:
Sorry, I would like it executed in recovery. I want to try and find out why it seems as when apex libraries are mounted, they do not seem to be added to the library search path in init.
Since some of the decryption programs don't find libion.so, they cannot start up.
Click to expand...
Click to collapse
heres getprop
https://hastebin.com/eluqagolub.md
heres list of files in /system/lib64
https://hastebin.com/uqoxuheqef.pl
Got some $$ coming your way Monday OP.
Thank you for this. It could not have been easy
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
dhacke said:
@bigbiff,
i tested the test2 img, too and i have the same result as wrongway213 and Surge1223. It hangs on the twrp Splash Screen.
I'm on AOSiP Official (no Gapps) from june (=> latest build) so my factory image is on june, too (i don't know which slot is active atm).
Just a theory: Can it have to do with the fact that on the other slot is still the old AOSiP build with may factory image installed? Mayby this makes a crash on the decryption. I'm not a dev so it's just a assumption.
If you need logs i'm glad to give them to you but i know only the logcat from adb. So for more i would need guides/help.
Click to expand...
Click to collapse
No, it seems to be related to trying to load libion.so from apex images. Can you post a URL to the exact build you are using? I can test it on flame locally.