Database Develop

[L3] [MOD] CWM recovery for e400 [CM/MIUI/SDMERGE]

Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
I also included the recovery for the SDMerge and also a linux script. Sorry, but the archive is too big to post it here on xda so i had to upload it on 4shared.
Requirements:
1) Rooted phone (obviously!!)
Instuctions Windows:
1) Download the package from 4shared
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
Instructions Ubuntu/Debian/Mint:
1) Download the package from 4shared
2) Extract it
3) Make sure you have the sdk properly installed with adb (if not check here: http://forum.xda-developers.com/showthread.php?t=2100673 )
4) Run the script by typing
Code:
./CWM-Installer.sh
5) Enjoy the new recovery
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /data/local/recovery.img
or if you want the recovery for the SDMerge just replace:
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
with this:
Code:
Files\adb push Files\SDmergerecovery.img /data/local/recovery.img
And then run the script again.
Feel free to post comments!!
Download here:
http://www.4shared.com/archive/8HmnogYQ/CWM-Installer-E400tar.html

wow, long time no see...
keep it up buddy

yayakuya said:
wow, long time no see...
keep it up buddy
Click to expand...
Click to collapse
Thanks yaya, I was busy with work and home and I haven't internet at home so I can't download the huge GBs of a repo.

Works like said great job keep it up buddy!

Cobmaster said:
Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
Requirements:
1) Rooted phone (obviously!!)
Instuctions:
1) Download the attachment
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
IT DOESN'T WORK WITH SDMerge MOD!!!
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /mnt/extra-sd/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /mnt/extra-sd/recovery.img
And then run the script again.
Feel free to post comments!!
Click to expand...
Click to collapse
i created a flashable zip for the recovery her it is please thank me.:good:

jeffreyvh said:
i created a flashable zip for the recovery her it is please thank me.:good:
Click to expand...
Click to collapse
I used the script written a long time ago for who has only the device rooted but hasn't the recovery installed... Btw good job!

@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)

andwie said:
@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)
Click to expand...
Click to collapse
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).

Cobmaster said:
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).
Click to expand...
Click to collapse
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort

andwie said:
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort
Click to expand...
Click to collapse
Here it is, to flash it use my script replacing the recovery.img with the one attached and report if it works or not.
Btw, are you sure that the "/data" partition is ext4? Because if it's wrong the recovery doesn't mount it.

Very sorry for the very late reply, I just had the time to test your new recovery (I had to create flashable zip for it since the script didn't work) and it work perfectly.
Now we have alternative to increase data partition without having to edit apps like gellmar's StockMergE400, means it will be compatible with all stock-based rom :victory:
Thanks again @Cobmaster :good:

Don't worry about it. It's very pleasing to see that it works.

hi!
 @Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good

dricoarmani said:
hi!
@Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good
Click to expand...
Click to collapse
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo

Cobmaster said:
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo
Click to expand...
Click to collapse
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off

Axims said:
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off
Click to expand...
Click to collapse
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium

Cobmaster said:
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium
Click to expand...
Click to collapse
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?

lomax84 said:
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?
Click to expand...
Click to collapse
only use gellmar recovery, because it is fixed for sdmerge

kien_vip said:
only use gellmar recovery, because it is fixed for sdmerge
Click to expand...
Click to collapse
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2

lomax84 said:
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2
Click to expand...
Click to collapse
it contain in step 2 or you can see it on some sdmerge rom

[DEV][RECOVERY] TWRP Recovery 2.7.0.0

TWRP Recovery
For Galaxy Mini
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
BUGS:
If you have found a bug, please consider posting it here.
LIVE SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
chraso: For his precious help.
Me: For compiling it for Galaxy Mini.

CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.

DOWNLOAD:
http://www.upload.ee/files/3992673/recovery.img.html
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!

What to test in latest build?:
-NOTHING. IT IS STABLE NOW.

Reserved

Will test it the moment I get home. Which is about 4 hours from now...
Tapatalk-kal küldve az én GT-S5570-el

doesnt boots.hangs on teamwin boot screen. luckily i had pc.currently flashing recovery by odin

+1

arpitkh96 said:
doesnt boots.hangs on teamwin boot screen. luckily i had pc.currently flashing recovery by odin
Click to expand...
Click to collapse
Thanks for feedback.
Now, can you help me find the problem?
How?
-Install recovery.
-Though it's stuck at Teamwin's screen, use adb in pc and give the following command:
Code:
adb pull /tmp/recovery.log
-Now, you will have a recovery.log file at the location where your adb files are there.
Attach that file in your post or use pastebin.com.
AND
Can you try that (terminal emulator) method once?
If you don't know what I'm talking about, see PhilZ recovery FAQs > Alternative way to flash this recovery.

Bhargav97 said:
Thanks for feedback.
Now, can you help me find the problem?
How?
-Install recovery.
-Though it's stuck at Teamwin's screen, use adb in pc and give the following command:
Code:
adb pull /tmp/recovery.log
-Now, you will have a recovery.log file at the location where your adb files are there.
Attach that file in your post or use pastebin.com.
AND
Can you try that (terminal emulator) method once?
If you don't know what I'm talking about, see PhilZ recovery FAQs > Alternative way to flash this recovery.
Click to expand...
Click to collapse
terminal method doesnt works either.here is the log

arpitkh96 said:
terminal method doesnt works either.here is the log
Click to expand...
Click to collapse
Thanks for logs. They helped me.
I forgot to add some things in recovery.
I didn't recompile but repacked with those things added.
If you get a black screen, don't give me logs. (It maybe a repack problem)
But, if you get teamwin logo, I need logs again.
New recovery.img for test:
http://www15.zippyshare.com/v/37395986/file.html
Use terminal emulator method.

Bhargav97 said:
Thanks for logs. They helped me.
I forgot to add some things in recovery.
I didn't recompile but repacked with those things added.
If you get a black screen, don't give me logs. (It maybe a repack problem)
But, if you get teamwin logo, I need logs again.
New recovery.img for test:
http://www15.zippyshare.com/v/37395986/file.html
Use terminal emulator method.
Click to expand...
Click to collapse
loops between black screen and Samsung logo. Cant give log ,adB doesnt recognises
Sent from my GT-S5570 using XDA Premium 4 mobile app

arpitkh96 said:
loops between black screen and Samsung logo. Cant give log ,adB doesnt recognises
Sent from my GT-S5570 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will be back after a re-compile.(15-20 min)

Sorry to be late.
Here's new test:
http://www.upload.ee/files/3989901/recovery.img.html

Bhargav97 said:
Sorry to be late.
Here's new test:
http://www.upload.ee/files/3989901/recovery.img.html
Click to expand...
Click to collapse
Booted! Report time!
It can't flash sd-ext scripts.
Trying to mount or unmount partitions doesn't do anything and can get the vibration engine stuck on working.

hard bricked
cell bricked. time 4 ssc .hahaha.
only teamwin logo appearing.

sushil888 said:
cell bricked. time 4 ssc .hahaha.
only teamwin logo appearing.
Click to expand...
Click to collapse
Use test img files. Do all these only if you know how to recover. You'll have flash an older recovery using odin.
ast00 said:
Booted! Report time!
It can't flash sd-ext scripts.
Trying to mount or unmount partitions doesn't do anything and can get the vibration engine stuck on working.
Click to expand...
Click to collapse
Good...
Atleast it booted now...
You will have to help me.
-Boot into TWRP.
-Go to Mounts
-And select/un-select partitions and then install an sd-ext script and let it fail.
-Now, without doing anything else, give me the recovery log. (method in page #1)
And...you mean vibrator gets stuck in between?

Bhargav97 said:
Use test img files. Do all these only if you know how to recover. You'll have flash an older recovery using odin.
Good...
Atleast it booted now...
You will have to help me.
-Boot into TWRP.
-Go to Mounts
-And select/un-select partitions and then install an sd-ext script and let it fail.
-Now, without doing anything else, give me the recovery log. (method in page #1)
And...you mean vibrator gets stuck in between?
Click to expand...
Click to collapse
It's vibrating non stop and it only stops if I reboot.
http://pastebin.com/Bg5GJ8rF
This logs is weird... It looks like it does mount the stuff, it just doesn't update the ui.

ast00 said:
It's vibrating non stop and it only stops if I reboot.
Tapatalk-kal küldve az én GT-S5570-el
Click to expand...
Click to collapse
For me its not vibrating continuously but duration of vibration on a click or touch is really large.
One bug I noticed is that progress bars are not resized.
While backing up a ROM the indeterminate progress bar is fine but the blue one showing exact progress is not resized.
Its width is larger (it goes out of screen on rhs) and height is smaller than that of indeterminate progress bar so it doesn't actually appears as an overlay.I don't have camera now to show you a pic.I will show you pic after 2hrs
Sent from my GT-S5570 using XDA Premium 4 mobile app

ast00 said:
It's vibrating non stop and it only stops if I reboot.
http://pastebin.com/Bg5GJ8rF
This logs is weird... It looks like it does mount the stuff, it just doesn't update the ui.
Click to expand...
Click to collapse
Logs look fine.
@arpitkh96 says it's not vibrating non-stop but duration of vibration is long. I think, that can be managed somehow.
About the other report you gave of error when installing zip:
Your zip file's update-binary is old. You will need to update it. Replace /META-INF/com/google/android/update-binary file from cm11 or omni4.4 zip. You will need to do it in ANY zip that doesn't install. This is the way it works. KitKat has changed many a things, this is one of them.
Please try this and give result.
And, cm11 or omni or any other ROMs are installing or not?
Also, what do you mean by "mounting-unmounting partitions doesn't do anything." If the partitions are not mounted, your log would have errors but there are no errors.
@arpitkh96,
I know about that progress bar bug. Its theme related. I would fix it after fixing major recovery problems.
You can use any 240x320 twrp theme uptil then. It would work just fine.
For more info on Themes for TWRP, visit here:
http://forum.xda-developers.com/nexus-4/themes-apps/twrp-theme-collection-thread-t2035234

[DISCONTINUED][WiFi & LTE] CM12 UNOFFICIAL Builds

Official nightlies are up for our device's:
Scorpion (LTE): http://download.cyanogenmod.org/?device=scorpion
Scorpion (Wifi): http://download.cyanogenmod.org/?device=scorpion_windy
TWRP Installation:
You can install TWRP through ADB or Terminal Emulator app. Thanks to ejdan for finding this!
ADB:
Before you begin:
- Download TWRP:
Code:
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/WiFi%20-%20SGP61x/twrp.img"]WiFi - SGP61x[/URL]
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/LTE%20-%20SGP62x//twrp.img"]LTE - SGP62x[/URL] (Credits to [B]der_bert[/B] for making this)
- set Root access to "Apps and ADB" in Developer options.
- set USB Debugging Mode to "ON" in Developer options.
Instructions:
1. Put twrp.img in the root of your Z3TC.
2. Open command prompt and go to the location where ADB.exe is.
3. Start an ADB shell:
Code:
adb shell
4. Gain root access:
Code:
su
5. Flash TWRP on FOTAKernel partition
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
6. Reboot to recovery and you would see TWRP.
Terminal Emulator:
Before you begin:
- Download TWRP:
Code:
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/WiFi%20-%20SGP61x/twrp.img"]WiFi - SGP61x[/URL]
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/LTE%20-%20SGP62x//twrp.img"]LTE - SGP62x[/URL] (Credits to [B]der_bert[/B] for making this)
- set Root access to "Apps" in Developer options.
- set Local terminal to "ON" in Developer options. (If you don't have this option download then Terminal Emulator from the Play Store)
Instructions:
1. Put twrp.img in the root of your Z3TC.
2. Open the app Terminal or Terminal Emulator
3. Gain root access:
Code:
su
4. Flash TWRP on FOTAKernel partition
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
5. Reboot to recovery and you would see TWRP.
Version Information:
Status: Discontinued
Created 2014-12-24
Last Updated 2015-03-25

Nice? any plans for LTE model?

Lte model is merged into cm sources so it should work
Will try to get up an simple kernel with intelliplug and so on

moritz31 said:
Lte model is merged into cm sources so it should work
Will try to get up an simple kernel with intelliplug and so on
Click to expand...
Click to collapse
I'd be interested and thanks!

chaostimmy said:
Nice? any plans for LTE model?
Click to expand...
Click to collapse
I'm building right now for LTE but I can't test this builds.
EDIT: LTE Build is up!

I have tried the Wifi version and it seems to work fine.
First I had a few restarts when locking the screen but it seems to have fixed itself now. Maybe because I disabled double tap to sleep/wake?
SD card is not mounted. Is there a way to fix it? The card is listed in /proc/partitions so it should be possible to fix with a proper fstab.

ejdan said:
SD card is not mounted. Is there a way to fix it? The card is listed in /proc/partitions so it should be possible to fix with a proper fstab.
Click to expand...
Click to collapse
I compared fstab.qcom in CM12 with the stock kernel and found a difference. The stock kernel has /devices/msm_sdcc.3/mmc_host for sdcard1 but CM12 has /devices/msm_sdcc.2/mmc_host
I changed '2' to '3' in the ramdisk and now SD card works. I have attached my modified kernel image. Unpack the zip file and flash cm12-sdcard1-fix.img using fastboot. This kernel is taken from cm-12-20141225-0800-UNOFFICIAL-scorpion_windy.zip

Qzerno said:
I'm building right now for LTE but I can't test this builds.
EDIT: LTE Build is up!
Click to expand...
Click to collapse
Great, thank you but I could not install it. In TWRP it says:
"This package is for device: SGP621, SGP641, SGP651, scorpio; this device is scorpion_windy."
It's not. I have the LTE version, SGP621 aka Scorpion.

Thanks for the builds! What has everyone flashed?

Home Launcher
Is Trebuchet included in these builds? Ive flashed todays (26th) build and am I'm just getting the options for Google Now and Nova Launcher.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Any chance of making the kernel flashable?

BUG REPORT: double tap to wake is not working

ejdan said:
I compared fstab.qcom in CM12 with the stock kernel and found a difference. The stock kernel has /devices/msm_sdcc.3/mmc_host for sdcard1 but CM12 has /devices/msm_sdcc.2/mmc_host
I changed '2' to '3' in the ramdisk and now SD card works. I have attached my modified kernel image. Unpack the zip file and flash cm12-sdcard1-fix.img using fastboot. This kernel is taken from cm-12-20141225-0800-UNOFFICIAL-scorpion_windy.zip
Click to expand...
Click to collapse
Nice, thanks for fixing this. Do you maybe know which file in the source need to edit to get this works? then I can commit it to CyanogenMod.
Noe_S said:
Great, thank you but I could not install it. In TWRP it says:
"This package is for device: SGP621, SGP641, SGP651, scorpio; this device is scorpion_windy."
It's not. I have the LTE version, SGP621 aka Scorpion.
Click to expand...
Click to collapse
The recovery (TWRP) need to get a build separately for the scorpion (SGP621), then it should work.
I will search for a alternative installation method for the scorpion.
xan_asmodi said:
Is Trebuchet included in these builds? Ive flashed todays (26th) build and am I'm just getting the options for Google Now and Nova Launcher.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Any chance of making the kernel flashable?
Click to expand...
Click to collapse
Yes, Trebuchet is included in these build, PA Gapps remove Trebuchet I can upload Trebuchet separately if you want.
I want to make the kernel flashable but that has not yet succeeded.
xan_asmodi said:
BUG REPORT: double tap to wake is not working
Click to expand...
Click to collapse
Thanks for the bug report. I also noticed this. I will add this in the OP.

Qzerno said:
Nice, thanks for fixing this. Do you maybe know which file in the source need to edit to get this works? then I can commit it to CyanogenMod.
Click to expand...
Click to collapse
I made a pull request on Github. Not sure if it is the correct way to do it
https://github.com/CyanogenMod/android_device_sony_scorpion_windy/pull/1
The file fstab.qcom is in rootdir. Because of the overlay (scorpion is based on shinano common) I had to add a new file. I have not built from source so I have not checked that it is working but manually updating the ramdisk did work.

ejdan said:
I made a pull request on Github. Not sure if it is the correct way to do it
https://github.com/CyanogenMod/android_device_sony_scorpion_windy/pull/1
The file fstab.qcom is in rootdir. Because of the overlay (scorpion is based on shinano common) I had to add a new file. I have not built from source so I have not checked that it is working but manually updating the ramdisk did work.
Click to expand...
Click to collapse
Ahh that's why I can't find that file. I have add the file local and building right now.
EDIT: Yeah I have 10 posts!

Qzerno said:
Ahh that's why I can't find that file. I have add the file local and building right now.
Click to expand...
Click to collapse
You may have to add the file to a makefile somewhere but lets see how it goes.

Qzerno said:
Thanks for the bug report. I also noticed this. I will add this in the OP.
Click to expand...
Click to collapse
Your welcome Should I post stuff as I find them or PM you so you can update the OP?
Could you post trebuchet separately? That'd be a great help. I think the PA guys need to incorporate Aroma installer, because I don't think Google Now Launcher is as good as Trebuchet.
Keep up the good work, hopefully we'll get the camera drivers soon. I'll look to see if the camera module is the same as the Z2 tab, if so we may not need to wait, just take them from the other repository.

Oh, one more thing...
Xposed doesn't install through a combination of crap cyanogenmod recovery and other stuff which I can't profess to understand
Edit: I now understand that this is because of the shift from Dalvik runtime to ART. Getting CM12 to run Xposed will either require reverting to Dalvik (is this possible?) or waiting for the Xposed devs to rewrite Xposed.

When updating to a new nightly, you can flash over the previous build. When you do you need to reflash the ram disk/kernel update.
BUG REPORT: Rebooting into recovery from power menu doesn't work. Requires manual intervention at 'Sony screen'/purple LED.

Intalled it and works fine as far as i can tell. Can´t move Apps to he sd card thogh (not enough space error) but that might be because of that known sd issue. I have general access to the sd though.
Cheers and thanks
Chris

MasterTRL said:
Intalled it and works fine as far as i can tell. Can´t move Apps to he sd card thogh (not enough space error) but that might be because of that known sd issue. I have general access to the sd though.
Cheers and thanks
Chris
Click to expand...
Click to collapse
What nightly are you using and did you flash the sd card fix?

MHA-L29C636B172 perfect boot image

Hi guys
if anyone is interested in testing out this boot image i created for my c636b172
removes all encrypt, perfect mounting options for all partitions (this took a while to figure since some caused bootloops)
also reduced voltages for wifi module (may be unstable, if anyone has problems let me know i can try and adjust, otherwise if im not getting problems ill just keep decreasing it)
how to install
1. make sure twp is installed
2. in data/dalvik-cache delete arm and arm64 folders.
3. boot into twrp > wipe cache and dalvik
4. flash the boot image in twrp (flash image select image flash to boot)
5. if you had su installed, flash the zip again
6. go to wipe cache and dalvik again (just in case)
7. reboot and enjoy, theoretically should be slightly faster, and less overhead.
Download
https://www.dropbox.com/s/msda9a3smy9lqb4/modBootv2.img?dl=0
if anyone has a request for their specific boot image let me know and ill add the same values.

Thank you for your work. Is this only for C636 devices or would this work on any device.
Could your reassemble it to add features like DT2W (doubletap to wake)?

audioralf said:
Thank you for your work. Is this only for C636 devices or would this work on any device.
Could your reassemble it to add features like DT2W (doubletap to wake)?
Click to expand...
Click to collapse
i think DT2W is disabled, no flags of it in the boot image, you can try this guide.
https://forum.xda-developers.com/mate-9/how-to/enable-double-tap-to-wake-mate-9-t3580764
the boot image is for the c636, im not sure if you can flash it on another base you can try just have a stock boot.img handy
or to be safe you can send me your boot.img and ill edit it the same.

Thank you for your friendly offer!
I am back on C432B156 with supersu modified boot. The original boot img linked here
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Mine is https://mega.nz/#!EABCVJwb!wopFOGqJzbpIX6edxM5Y9IVeZAIJ_CAJYUn3q4cc074
I recognized that I have no adb access in TWRP 3.02.2
I can not mount my pc connection. Would this be fixed?
Gesendet von meinem MHA-L29 mit Tapatalk

audioralf said:
Thank you for your friendly offer!
I am back on C432B156 with supersu modified boot. The original boot img linked here
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Mine is https://mega.nz/#!EABCVJwb!wopFOGqJzbpIX6edxM5Y9IVeZAIJ_CAJYUn3q4cc074
I recognized that I have no adb access in TWRP 3.02.2
I can not mount my pc connection. Would this be fixed?
Gesendet von meinem MHA-L29 mit Tapatalk
Click to expand...
Click to collapse
no, twrp 3022 doesnt have MTP access right now.

Thank you for the info.
Which advantage is on daily usage. I guess I would have to install supersu again, for it modifies the boot.
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)

Mount does work in 3.1.0. Though you have to tap on "Mount USB Storage", then unmount before it actually mounts..

ante0 said:
Mount does work in 3.1.0. Though you have to tap on "Mount USB Storage", then unmount before it actually mounts..
Click to expand...
Click to collapse
ill try this
always thought it didnt work since it worked fine in 303

Hi Virtyx,
I very appreciate your work, good hope to use,
but i have some not understand the installation in STEP 2 (in data/dalvik-cache delete arm and arm64 folders) what to do?
Hope you can help explain more STEP 2 detail.
I have L29-C636b172 and unlocked Bootloader.
A lot of Thanks.

xjeepnsk said:
Hi Virtyx,
I very appreciate your work, good hope to use,
but i have some not understand the installation in STEP 2 (in data/dalvik-cache delete arm and arm64 folders) what to do?
Hope you can help explain more STEP 2 detail.
I have L29-C636b172 and unlocked Bootloader.
A lot of Thanks.
Click to expand...
Click to collapse
Using a file Explorer with root support, navigate to /data/dalvik-cache and remove those 2 folders. Alternatively use a terminal app and 'rm -rf /data/dalvik-cache/arm*'.
I guess you could use the file manager or terminal in twrp.

ante0 said:
Using a file Explorer with root support, navigate to /data/dalvik-cache and remove those 2 folders. Alternatively use a terminal app and 'rm -rf /data/dalvik-cache/arm*'.
I guess you could use the file manager or terminal in twrp.
Click to expand...
Click to collapse
Hi ante0,
I succeeded, Thank you so much

Hello sir,
My mate 9 stuck in boot loop....
And I can't access to recovery too
Can u make scatter file for mate 9 to fix boot loop

[Recovery][Stock OOS]Oxygen OS Stock recovery with ADB enabled

While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled.
Prerequisites:
Oneplus 8 Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <filename>
(with <filename> being the name of the recovery in the format of "recovery.img" you wish to flash)
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Step-by-step this would be:
Code:
cd /data/adb/modules
to change to the Magisk modules directory
Code:
ls
to list the content of this directory, each module has its own directory, usually with a well-recognizable name
Code:
rm -r <directory>
to delete the directory in question. Tip: in console TAB-autocomplete works
Downloads:
10.5.4 BA Recovery
Modified 10.5.4 BA recovery from GDrive
Original 10.5.4 BA recovery from Gdrive
10.5.5 BA Recovery
Modified 10.5.5 BA recovery from GDrive
Original 10.5.5 BA recovery from Gdrive
10.5.6 BA Recovery
Modified 10.5.6 BA recovery from GDrive
Original 10.5.6 BA recovery from Gdrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.

Description of method to modify recovery by yourself:
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash

Thanks for this...
On fastboot we have to flash the modified recovery img?
EDIT : Nevermind haven't read the whole OP

I have a noob question: this won't affect data or magisk right?

To remove a module , command should not be :
( rm -rf < directory> ) ?...

cultofluna said:
To remove a module , command should not be :
( rm -rf < directory> ) ?...
Click to expand...
Click to collapse
Thanks for your comment, but technically no
The - f flag is used to omit prompts before each removal, which may or may not be helpful - depending in how sure the user is on what he does
I chose the safer variety in my example, confident that users with more knowledge can always look at the "rm" man page to decide what command they want to use...
But again thanks, I do appreciate your help!

HottieLinus said:
I have a noob question: this won't affect data or magisk right?
Click to expand...
Click to collapse
Correct, the recovery resides in a separate partition and flashing it doesn't do anything anywhere else.
In fact the recovery looks and behaves the same when booting into it, the change only becomes apparent by being able to use adb in recovery.

@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...

cultofluna said:
@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...
Click to expand...
Click to collapse
It should be possible as the recovery gives you full access to your file system and so, given you know what to remove/change, it should also be possible to recover from issues as you mentioned.
My problem: I have no idea where themes or substratum additions are installed directory-location wise, will need to research a bit. Or maybe someone else can chime in on this, then I could update OP with info on that as well...

Ok one more question..
Can we flash zips through the recovery?...
Via ADB sideload?.. maybe..

cultofluna said:
..Can we flash zips through the recovery?...Via ADB sideload?..
Click to expand...
Click to collapse
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:

s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Ok...
Because on pixel4 XL you can reboot to stock recovery and choose the the option ADB sideload...
And from there you can flash a custom ROM...etc..

Updated OP with 10.5.5 recovery..

s3axel said:
Updated OP with 10.5.5 recovery..
Click to expand...
Click to collapse
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.

Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.
Click to expand...
Click to collapse
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...

cultofluna said:
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...
Click to expand...
Click to collapse
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?

Burt Squirtz said:
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?
Click to expand...
Click to collapse
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents

pyry666 said:
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents
Click to expand...
Click to collapse
What an incredibly helpful response. Sorry but if there's something that'll decrypt and allow me to backup and recover, of course I'm going to try and find it. And I suspect most other people here would too.

Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
Click to expand...
Click to collapse
I don't know presently, usually I compare recoveries or I (or other users) add recoveries for other regions which they made by themselves. When recoveries are the same of course they can be used
RIght now I cannot download the 10.5.5 AA firmware (download aborts after some time), I'll add the recovery once this is working... EDIT: seems OP pulled the downloads, so no luck at the moment...

If there is a working twrp in China then perhaps it's worth making contact with them to see if either:
A) they can let you have it
B) they can help you fix this one?
It's presume the former would make the most sense, with permission I see no problem in obtaining it or linking it, certainly not taking about it. Makes no sense to just avoid an obvious assist whilst we all struggle without twrp.