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?
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Wildfire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. Can be installed with unrEVOked. Installs and works well according to users in this thread. Off-mode charging works according to t0mas_.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-buzz.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-buzz.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Flash like a normal ROM ?
Use it with unrevoked then custom recovery in the menu and use the image file in the zip
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Well my phone was installed and works well ...
t0mas_ said:
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Click to expand...
Click to collapse
No idea. It depends on the CM7 3.2.0.0 recovery source code. I didn't change anything, and I'm quite sure j_r0dd didn't touch this.
cse.10100 said:
Well my phone was installed and works well ...
Click to expand...
Click to collapse
Great! Updating the OP.
thanks, i'll try this out when i find time
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
aggourodolmas said:
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
Click to expand...
Click to collapse
Well, the recovery image itself doesn't touch superuser, but unrevoked will. I belive that you might be downgrading the superuser binary, but (at least for CM7) a reflash with the same zip without wiping anything should restore the superuser binary that was included in your ROM. It should work on other ROMs as well, as long as they're not wiping /data or /sd-ext while flashing for some reason. Make a nandroid backup before you consider flashing this recovery, that's my advice.
Can anyone confirm if this supports off mode charging?
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
Not sure where to look, but maybe one can search for this in some type of changelog for the official cwm repository.
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
works for me
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
rseke said:
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
Click to expand...
Click to collapse
You need to use unrevoked to flash the .img file.
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
rseke said:
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12548919&postcount=26
Unrevoked 3.14 can be found in the same thread on the first page.
Thanx for fast reply and for help.
I have one problem now,mu super user app not working how can i fix that,i cant enter to superuser app to update su binary,force close.
Hey there! It has been a while..
You may have noticed Team Win Recovery Project (short: TWRP) is available, but still not for our device,
and it seems I am the only one who spends time on making TWRP fully compatible
for our device which includes some bug fixes and modifications.
Both, TWRP and the kernel were compiled on my pc, using OS X Yosemite (10.10) as host system
from CM sources.
Use at your own risk.
I am not responsible for any damages on your device.
Click to expand...
Click to collapse
What is TWRP?
A fully touch driven custom recovery developed by TeamWin with a nice and easy to use user interface.
You can install your ROM's, backup it or restore it from/on your internal or external storage.
Backups can be compressed which saves alot of storage space and backups can have an individual,
user chosen name. Some unique features are an integrated filemanager, shell access,
rooting and the option to set a display timeout and display brightness.
TWRP includes alot of more features that I listed.. just explore yourself.
Download (also check the #Download page):
recovery263.img => TWRP 2.6.3.0 (STABLE)
recovery283_1.img => TWRP 2.8.3.0 (BETA)
For developers and for GPL reasons:
gkernel_x3_defconfig.zip => Used kernel defconfig (no kernel sourcecode changes have been made except mac os x specific kernel building fixes)
Sources (using cm10.2 sourcecode with cm p880 kernel):
p880_device: https://bitbucket.org/supergordon/device_lge_p880
p880_recovery_twrp: https://bitbucket.org/supergordon/twrp_lge_p880
p880_kernel: https://github.com/CyanogenMod/lge-kernel-p880
How do I install TWRP on my unlocked device?
Option 1: Fastboot
Code:
adb reboot oem-unlock
fastboot flash recovery recovery263.img
fastboot reboot
Option 2: ADB (put first the recovery image to the root directory of your internal storage)
Code:
adb shell
su
cat /sdcard/recovery263.img > /dev/block/mmcblk0p1
What device specific changes have been made?
Reboot options now properly working
Use CM's device specific fix to blank the display
Add missing external storage display name
Add missing screen brightness path
Modified display dimming delay
Fix rendering bugs that caused high battery consumption and device heat-ups
Add proper handling of the quadcore. Reduces backup time by about 10%.
UMS support (external storage only)
Since 2.6.3.0:
Using cm10.2 source
Using cm kernel
Exclude wiping sd-ext (bugfix for 2.6.1.0)
Since 2.8.3.0:
Now using twrp.fstab
Remove UMS support (TWRP has now MTP support. both internal and external storage are shown on the PC)
Add data/media[/0] button in Advanced page. Pressing the button toggles between /data/media and /data/media/0
Added missing option to (not) backup/restore recovery partition.
SD-Ext support (secondary partition of your microsd has to be ext4 formatted)
Using twrp sources from 30 december 2014
Click to expand...
Click to collapse
For changelogs on TWRP itself visit http://www.teamw.in/project/twrp2
My submitted patches on TeamWin's gerrit:
http://review.teamw.in/606
http://review.teamw.in/607
[July 1st] --> Both patches have been now reviewed and merged into the official TWRP sources.
Please report any bugs to help improving TWRP on our device.
Bug reports can be submitted here.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG Optimus 4X HD
Contributors
gordon0001
Version Information
Status: No Longer Updated
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-12
Current Beta Version: 2.8.3.0
Beta Release Date: 2014-12-31
Created 2013-09-17
Last Updated 2015-01-16
Reserved
Finally!!!...Thanks..Thanks..Thanks..
I follow you and your work and i hope that soon you release a gbootmenu 0.2 with twrp 2.5...
Or via terminale put the recovery.img in your sdcard and write:
1) su and agree superuser request
2) flash_image recovery /sdcard/recovery.img
Sent from my Wildfire S using xda app-developers app
gave thanks as appreciation =)
Sent from my LG-P880 using Tapatalk 4 Beta
Thanks awesome! i really like twrp much more than cwm.
Is it possible that Fix Permissions is not working? it takes about a second to finish, with cwm it was 5 to 10 minutes.
Thanks!
Fastboot mode :
cannot load 'recovery.img': No error
Why?
Thx
saenta said:
Thanks awesome! i really like twrp much more than cwm.
Is it possible that Fix Permissions is not working? it takes about a second to finish, with cwm it was 5 to 10 minutes.
Thanks!
Click to expand...
Click to collapse
no, thats fine. twrp uses its own way to fix permissions.
Gesendet von meinem LG-P880 mit Tapatalk 2
@tiflao
Recovery.img is not in your fastboot directory. I'm 100 percent sure
Sent from my LG-P880 using xda app-developers app
tiflao said:
Fastboot mode :
cannot load 'recovery.img': No error
Why?
Thx
Click to expand...
Click to collapse
be sure you change to the directory where you stored recovery.img at your terminal(linux, osx)/command prompt(windows) with the "cd" command.
Thx guys
@gordon0001:
How is the development of the next version of GBootmenu going on? I am really looking forward to see TWRP 2.5.0.0 and CWM 6.0.3.1 in just one menu.
Thanks for TWRP 2.5.0.0! Good work!
Thanks gordon0001. Will make flashing and everything else a lot easier. Installed using the All in one P880 kit.
Have a good weekend!
tool_king said:
@gordon0001:
How is the development of the next version of GBootmenu going on? I am really looking forward to see TWRP 2.5.0.0 and CWM 6.0.3.1 in just one menu.
Thanks for TWRP 2.5.0.0! Good work!
Click to expand...
Click to collapse
Hey!
Nice to see you like my work, but this thread is about TWRP and not GBootMenu. Post your questions about my other work in the correspondending release thread.
gordonbennet said:
Thanks gordon0001. Will make flashing and everything else a lot easier. Installed using the All in one P880 kit.
Have a good weekend!
Click to expand...
Click to collapse
Thank you!
The all in one kit installs an outdated, dangerous to use, version of TWRP.
Please install the new, updated version of TWRP or your hardware could be damaged.
Instructions can be found in the first post #1.
gordon0001 said:
Thank you!
The all in one kit installs an outdated, dangerous to use, version of TWRP.
Please install the new, updated version of TWRP or your hardware could be damaged.
Instructions can be found in the first post #1.
Click to expand...
Click to collapse
I forgot to add that I replaced the old one with your one in the toolkit's data files (just renamed the v2.5 to whatever the toolkit was using and deleted the old one).
Thanks for the concern though. Currently loving archived backups
TWRP is damn good! more functions, faster backup/restore etc., thanks!
Thanks for your work .. I love the recovery so much .. Thumbs up
Loving the touch,everything works as it should
updated to 2.6.0.0. see first post
the patches i submitted were reviewed, verified and merged into the official twrp sources. meaning with twrp 2.6.0.0 every device profit from it
http://review.teamw.in/606
http://review.teamw.in/607
Click to expand...
Click to collapse
gordon0001 said:
updated to 2.6.0.0. see first post
the patches i submitted were reviewed, verified and merged into the official twrp sources. meaning with twrp 2.6.0.0 every device profit from it
Click to expand...
Click to collapse
works perfect here
Sent from my LG-P880 using xda app-developers app
This is a guide of how to dualboot KitKat and Android Lollipop on a Nexus 5. This will allow you to test out Lollipop while keeping a stable ROM to run as a daily driver. I am running CM11, but you can do this with any KitKat ROM, even stock.
REQUIREMENTS
Nexus 5
Root
Unlocked bootloader
MultiROM
A brain
At least 1 GB of free space (I recommend 4 GB though)
1. Setting up.
I'm assuming you are already rooted if you are planning on doing this. If not, follow this guide to root and unlock the bootloader. http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-cf-auto-root-t2507211
1. After verifying you have root on your phone, download MultiROM Manager off Google Play: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=en
2. Install and open MultiROM Manager and install MultiROM, Recovery and the patched kernel.
Here is what the following is...
MultiROM: This boots before the system and gives you the option of what system you want to boot. When you select the system, it then hands it off to boot. This will not overwrite your current ROM, but make a backup to be safe
Recovery: This is a custom TWRP recovery with options to install a secondary system
Kernel: This will patch your kernel with kexec-hardboot patch which is requires to dualboot in general.
2. Installing Android Lollipop
1. After you install and verify that MultiROM is installed on your phone, download the Android 5.0 flashable zip from the downloads section at the bottom
2. Reboot into the recovery and go to Advanced> MultiROM> Add ROM
3. When you get there, set ROM type to Android and select "Dont share" for kernel sharing and then press next
4. select ZIP file and install "N5_L_PREV_LPX13D.zip" you downloaded earlier and flash it.
If you wish to not root L, you can go ahead and reboot your phone into Lollipop (The first boot will take several minutes). If you do want to root, go on to the next step. Your primary ROM won't be touched as your primary ROM and its root status won't be affected when using MultiROM.
3. Rooting Android Lollipop (optional)
Rooting is completely optional and is not required for it to run. You need to install root if you do plan on using root apps or busybox on Android 5.0.
As of the LPX13D build, there have been changes made in the bootloader that will prevent SuperSU or root from working. If you want to root on the LPX13D build, you will need to flash this bootloader: http://www.reddit.com/r/Nexus5/comments/2jkx7a/
1. Download the SuperSU zip in the downloads section and save it to your phone.
2. Boot into recovery and go to Advanced> MultiROM> List ROMs and select the L ROM you installed earlier (unless you renamed the zip file or the system name, it should show"N5_L_PREV_LPX13D")
3. Select flash zip and flash the SuperSU zip you downloaded.
4. Reboot and you should now be rooted.
Updating Android Lollipop
As of right now, there are issues if you try to do a dirty flash from DP1 to DP2 (These are issues with Android L and not MultiROM). These issues include home button not working, quick settings pulldown not working, no lockscreen when there is one and data issues (at least with Sprint). If you are coming from LPV79 and updating to LPV81C or LPX13D, it is recommended to do a clean install to avoid these issues. If you are doing a fresh install, you don't have to worry about this issue
Android Lollipop Bugs
These are issues with Android Lollipop and not MultiROM
-The issues stated above when certain things don't work after a dirty flash
-During the inatial setup, the phone may freeze and require reboot when trying to connect to wifi (seems like a new bug with LPV81C). The phone will say Connecting and show a white box before it freezes
-Some apps will crash or be buggy (this is to be expected though with the transition to ART)
-More bug reports can be found [Here]
-A list of apps that have issues with working with Android L can be found [Here]
Downloads
Android Lollipop flashable zip: http://forum.xda-developers.com/showpost.php?p=56112246&postcount=5498
L Root: http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Thanks
Chainfire for CF Autoroot and SuperSU
Tasssadar for MultiROM to make this dualboot possible
davy917 for posting a solution for people having internal storage issues with L
For more information and general use of how MultiROM works, go to its main thread [here]
Also if you do have the issue where your internal storage doesn't mount, follow this solution found [here]
Thanks! First time trying multiROM & working great
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
davy917 said:
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
Click to expand...
Click to collapse
Strange. I didn't have that problem but I will look in to it. I recommend going to advanced> MultiROM> list ROMs and perform a wipe of the cache and dalvik of your L system. I was able to download without problems and the internal storage worked fine. Also, how much space was there on your phone before doing this
Sent from my Nexus 5 using Tapatalk
I can't boot to L. Says I need a kexec-hardboot enabled kernel.
Sent from my Nexus 5
Elisha said:
I can't boot to L. Says I need a kexec-hardboot enabled kernel.
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, you need a kernel that has that patch included to be able to use MultiROM. There are a few of them if you look around.
---------- Post added at 01:53 AM ---------- Previous post was at 01:53 AM ----------
davy917 said:
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
Click to expand...
Click to collapse
L does sdcard differently
ThatGuy94 said:
Strange. I didn't have that problem but I will look in to it. I recommend going to advanced> MultiROM> list ROMs and perform a wipe of the cache and dalvik of your L system. I was able to download without problems and the internal storage worked fine. Also, how much space was there on your phone before doing this
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Lethargy said:
L does sdcard differently
Click to expand...
Click to collapse
Do you know how I can access the files in my sdcard?
davy917 said:
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Do you know how I can access the files in my sdcard?
Click to expand...
Click to collapse
You'll have /system/sdcard/0/ and /system/sdcard/
davy917 said:
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Do you know how I can access the files in my sdcard?
Click to expand...
Click to collapse
Just wondering, what is your baseband version. I'm just thinking if it may be a firmware issue for some reason. Also try ES File Explorer to see if your files show up in it because my files in sdcard appeared with it
Sent from my Nexus 5 using Tapatalk
Lethargy said:
You'll have /system/sdcard/0/ and /system/sdcard/
Click to expand...
Click to collapse
I don't see such directories.. No sdcard folder in system
---------- Post added at 01:50 PM ---------- Previous post was at 01:49 PM ----------
ThatGuy94 said:
Just wondering, what is your baseband version. I'm just thinking if it may be a firmware issue for some reason. Also try ES File Explorer to see if your files show up in it because my files in sdcard appeared with it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am using ES Explorer but no luck
My baseband is M8974A-2.0.50.1.13
When I tried to take a screen shot, I got an error saying cannot save screenshot, storage may be in use. Any idea what the deal is?
davy917 said:
I don't see such directories.. No sdcard folder in system
Click to expand...
Click to collapse
In KitKat, try to find /mnt/shell/emulated/0 or /sdcard in L
Sent from my Nexus 5 using Tapatalk
I can find both, but in L the folders in /sdcard are all empty
davy917 said:
I can find both, but in L the folders in /sdcard are all empty
Click to expand...
Click to collapse
Are they empty if you try to open them in KitKat? Also it looks like your baseband is out of date. I have the baseband M8974A-2.0.50.1.16. I recommend updating your baseband to see if it fixes it. Also what is your primary ROM
Sent from my Nexus 5 using Tapatalk
ThatGuy94 said:
Are they empty if you try to open them in KitKat? Also it looks like your baseband is out of date. I have the baseband M8974A-2.0.50.1.16. I recommend updating your baseband to see if it fixes it. Also what is your primary ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's not empty when I open in KK.. I'm running SlimKat
I'll try updating my baseband and see if it helps. Thanks for all the suggestions!
davy917 said:
It's not empty when I open in KK.. I'm running SlimKat
I'll try updating my baseband and see if it helps. Thanks for all the suggestions!
Click to expand...
Click to collapse
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
ThatGuy94 said:
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I think I'll just try starting over.. Nothing seems to work. I basically don't have any access to storage when on Android L as my secondary. I can't even take photos lol it takes a pic and can't save anywhere
davy917 said:
Yeah I think I'll just try starting over.. Nothing seems to work. I basically don't have any access to storage when on Android L as my secondary. I can't even take photos lol it takes a pic and can't save anywhere
Click to expand...
Click to collapse
There have read people in the Android L thread that have had this same issue. That's why I always thought dual booting with Android L wasn't a good idea.
Got some help from the multirom thread.. Followed the below and it worked fine. Had to reinstall Android L afterwards tho.
1. Install terminal from play store in Android L ROM.
2. In terminal: "su" *enter*
3. In terminal: "restorecon -FR /data/media/0" *enter*
4. Wait.*
5. Reboot.
*If it doesn't boot anymore, delete Android L as ROM, and flash it again trough multirom.
ThatGuy94 said:
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Slimkat is AOSP/stock kernels.... Not CM11/caf. ?
KJ said:
Slimkat is AOSP/stock kernels.... Not CM11/caf. ?
Click to expand...
Click to collapse
Thanks for the correction. I don't use slimkat so I thought it was using the cm11 kernel.
Sent from my Nexus 5 using Tapatalk
Hi, I am sharing my Nougat ROM for LG-P880 with the XDA community. As a tribute to the original @MoltenMotherBoard, it will continue to be named as such.
AFH download:
https://www.androidfilehost.com/?w=files&flid=109853
ChangeLog
20180122
- Android-7.1.2_r36 (N2G48H)
- kernel
* Optimized kswapd based on kernel-msm/3.10/Bullhead
- Tuned extra_free_kbytes to 4 screen buffers
- Reduced I/O read_ahead_kb from 2048 to 256 for better latency
- Set dalvik.vm.dex2oat-thread = 2
Complete changelog
https://www.androidfilehost.com/?w=files&flid=109853
SELinux for Nougat
SELinux in Nougat has been hardened to never allow text relocation for executables. This is the only rule that we had to relax to enable pre-KitKat blobs to run.
To enable SELinux Enforcing, do this from recovery
Code:
$ adb shell mount /data
$ adb shell touch /data/.selinux
$ adb shell umount /data
Known issues
- MHL not working
- Display freeze on Cast Screen disconnect
- Widevine DRM not working
Broken AOSP components
- Clock
- Browser2
- Music
- Webview
Installation
You need to have custom recovery that can flash multiple zip files without having the reboot. I personally use the official CWM 6.0.4.5 so the instructions will be based on that with no external SD.
>Coming from other ROMs
- wipe userdata/cache
- format /system
- apply ROM zip
- apply Gapps zip ...or more Gapps if using modular Gapps
- format /data and /data/media
- reboot
>Coming from the same ROM
- format /cache
- format /system
- apply ROM zip
- apply Gapps zip ...or more Gapps if using modular Gapps
- reboot
Recommended Gapps is OpenGapps stock. Default webview provider is Google WebView. Please make sure your Gapps include this. Attached you will see my Gapps config.
This is based on Grouper blobs, so as usual barcode/QR scanning will not work and will not consider this as bug. However, Grouper blobs works with Screen Cast, which for me, is more useful than barcode/QR code scanning.
Let the testing begin!!!:fingers-crossed::fingers-crossed::fingers-crossed:
Kernel
Kernel https://github.com/CyanogenMod/lge-kernel-p880/tree/cm-12.1
See attached for patches
Code:
commit 413b3fc527c086450f28acbe92893c71e73ad5b6
Author: demetris <[email protected]>
Date: Wed Nov 4 00:39:13 2015 +0200
Use "git am -3" for .patch files
Use "git apply" for .diff files.
Reserved another
Different installation hmmm Thanks for everything csk1jw
Use TWRP 3.0.2.0 and do the recommend wipes .Have the zip files on a EX sdcard.
By flashing get messages "unknow command log" in red letters
Try to install open gapps for 7.0 beta pico and get errorcode 20 .Witch gapps can i use ?
Flash without gapps and get also the messages in red letters,but
boot normally and it seems working good fast and smooth :good:
Try copy the zip files for gapps to intern sd.In recovery can flash gapps and webview,
clean dalvik/cache , reboot but cant not open playstore
Regards
Can anyone provide me touch recovery for flashing this ROM.
Also need gapps for this ROM, I am unable to access some sites in my country (Kingdom Of Saudi Arabia).
Please provide me touch recovery for this ROM and link for Gapps.
Edit: Attached CWM Touch Recovery v6.0.4.5
Anyone up for helping me????
Salman Al-Badgail said:
Anyone up for helping me????
Click to expand...
Click to collapse
Here is a link for gapps 7.0 stock:
https://www.dropbox.com/s/r4uxxnqkfcxvc6c/open_gapps-arm-7.0-stock-20160910.zip?dl=0
Here is the latest twrp recovery. Please confirm that this is a touch recovery, if it is. I'm sticking with CWM 6.0.4.5. and don't wanna flash TWRP now.
https://www.dropbox.com/s/rq4xiya446h0mgo/twrp-3.0.2-0-p880.img?dl=0
Phil_Smith said:
Here is a link for gapps 7.0 stock:
https://www.dropbox.com/s/r4uxxnqkfcxvc6c/open_gapps-arm-7.0-stock-20160910.zip?dl=0
Here is the latest twrp recovery. Please confirm that this is a touch recovery, if it is. I'm sticking with CWM 6.0.4.5. and don't wanna flash TWRP now.
https://www.dropbox.com/s/rq4xiya446h0mgo/twrp-3.0.2-0-p880.img?dl=0
Click to expand...
Click to collapse
@Phil _Smith
I use TWRP 3.0.2.0 .How get you the stock gapps to work? I can flash,but googleservices is not working !!
sourly64 said:
@Phil _Smith
I use TWRP 3.0.2.0 .How get you the stock gapps to work? I can flash,but googleservices is not working !!
Click to expand...
Click to collapse
I suggest you try CWM 6.0.4.5.
I remember that there always had been some problems with TWRP and AOSP-based ROMs.
---------- Post added at 07:27 PM ---------- Previous post was at 06:41 PM ----------
Is there any chance to get the xposed framework to work on this rom? Or is there simply no version available for android 7.0?
Phil_Smith said:
I suggest you try CWM 6.0.4.5.
I remember that there always had been some problems with TWRP and AOSP-based ROMs.
---------- Post added at 07:27 PM ---------- Previous post was at 06:41 PM ----------
Is there any chance to get the xposed framework to work on this rom? Or is there simply no version available for android 7.0?
Click to expand...
Click to collapse
Please do provide me CWM 6.0.4.5.
Thanks
Salman Al-Badgail said:
Please do provide me CWM 6.0.4.5.
Thanks
Click to expand...
Click to collapse
Here you are, sir! Hope you got adb working, as I only found this as an .img
(For myself I use Rom Manager).
https://www.dropbox.com/s/7kpdaoobfizmlum/cwm_6.0.4.5.img?dl=0
Edit: Ah, but I remember that flashing .img files is easy via twrp (a little bit ironic)
Phil_Smith said:
Here you are, sir! Hope you got adb working, as I only found this as an .img
(For myself I use Rom Manager).
https://www.dropbox.com/s/7kpdaoobfizmlum/cwm_6.0.4.5.img?dl=0
Click to expand...
Click to collapse
Thanks for providing me, many sites are blocked by govt here this is only the reason I am troubling you. Sorry.
Adb is working fine. Thanks again @Phil_Smith
---------- Post added at 11:16 PM ---------- Previous post was at 11:11 PM ----------
I found CWM Touch Recovery (6.0.4.5) HERE
I attached CWM Touch 6.0.4.5 (please do check)
Edit: Attachment Not working
Salman Al-Badgail said:
Thanks for providing me, many sites are blocked by govt here this is only the reason I am troubling you. Sorry.
Adb is working fine. Thanks again @Phil_Smith
---------- Post added at 11:16 PM ---------- Previous post was at 11:11 PM ----------
I found CWM Touch Recovery (6.0.4.5) HERE
Click to expand...
Click to collapse
No problem, I know - I read your previous post
Bluetooth does not work for me. The device is detected properly, but then there is no sound playing from my external audio speaker. Can anyone comfirm the Bluetooth issue?
Phil_Smith said:
Bluetooth does not work for me. The device is detected properly, but then there is no sound playing from my external audio speaker. Can anyone comfirm the Bluetooth issue?
Click to expand...
Click to collapse
Confirmed. Will investigate. Device paired and connected but no sound.
It is too slow on my device
fukuli053 said:
It is too slow on my device
Click to expand...
Click to collapse
Give it a couple of shots (that is reboots). At first nothing worked for me eighter, but it gets stable and really fast after like 4 restarts or so!
fukuli053 said:
It is too slow on my device
Click to expand...
Click to collapse
Well, it can't be. Nougat UX is faster than Marshmallow.
What's your Gapps installation?
All CM13 and RR releases we have so far are using pretty old China Dev MIUI v.6.6.30 as base not even listed on Xiaomi Downloads anymore. This as some of us know is the cause of all bugs we've had with these custom ROMs and were fixed by replacing vendor files from newer MIUI versions. On top of that some helium users cannot reboot to recovery from Android, phone doesn't power off... things like that... which most likely is due to using the wrong hydrogen kernel in this builds. Some users including me are experiencing no data going thru on good connection... Not gonna even mention VoLTE etc. So we still have bugs...
The vendor files and kernel that comes from MIUI as base are the main part that makes the hardware working flawlessly with the Android OS. These files are proprietary files with closed code, we can't change them so we have to rely on whatever Xiaomi do to optimize device performance. But we can choose which version to use and that is my goal here... Test and find the best set that works with custom ROMs.
Here we go... I have been testing the latest Global MIUI as base for two days now and so far haven't seen any issues at all. That doesn't mean no bugs... More time and testing is needed. But at least they are not any worst than what we are using now.
The common sense and logic is(fixed bugs proved that) vendor files and kernel from latest stable Global MIUI for the particular device should have more bug fixes and optimizations for the world out of China(I hope)... So using the best of my knowledge I compiled these two sets for:
HYDROGEN:
Based on latest Mi Max official Global MIUI v.8.0.1 (miui_MIMAXGlobal_V8.0.1.0.MBCMIDG_3657fef420_6.0.zip)
Download: vendor-base801MG_update-HYDROGEN.zip
HELIUM:
Based on latest Mi Max Prime official Global MIUI v.8.0.3 (miui_MIMAX652Global_V8.0.3.0.MBDMIDG_2da4c7e9db_6.0.zip)
Download: vendor-base803MG_update-HELIUM.zip
These packages are not recovery flashable zips!!! Keep reading for install instructions!
The install will get all vendor proprietary files I know of, firmware and kernel properly updated for the device code. Let's hope we get the better and latest from Xiaomi...
INSTALL INSTRUCTIONS:
MAKE TWRP BACKUP OF SYSTEM AND BOOT PARTITIONS BEFORE ANYTHING TO REVERS CHANGES IF YOU NEED TO!!!
The installation process is a little bit involving due to replacing the kernel in the actual installed boot.img in your device. I can't supply universal updated boot.img because they might be different from one release to another. I want to update what you already have. Did my best to make it user-friendly as I can without coding special app or something. Thanks to this guy whoever he is for the boot.img tools https://github.com/xiaolu/mkbootimg_tools.
Follow the steps and you should be fine:
1. Download the appropriate zip for your device code and unzip it to the root of your internal storage. You should end up with /sdcard/vendor_update folder;
2. Open your favorite terminal emulator app and execute the following commands one at a time pressing ENTER after each line:
Code:
su
hit ENTER
Code:
cp /sdcard/vendor_update/vendor-updater.sh /data/local/tmp/
hit ENTER
Code:
chmod 777 /data/local/tmp/vendor-updater.sh
hit ENTER
Code:
sh /data/local/tmp/vendor-updater.sh
hit ENTER
Alternatively you can USB connect your phone to computer and run the same commands from adb shell.
For HYDROGEN users:
That's all you have to do. The script will update your kernel and automatically will reboot phone to recovery and update vendor files so save your work before running the commands!
For HELIUM users:
Due to that can't reboot recovery bug you have to reboot manually by holding POWER and VOLUME+ buttons or fastboot method... The vendor zip will be flashed automatically and phone reboots back to system. If not, install /sdcard/vendor_update/vendor_update-HELIUM.zip manually and that's it.
Simple stuff if you decide to test these packages...
To verify update you should see kernel and baseband versions in About Phone changed like in the attached hydrogen screenshot. I can't test helium so they might be a little different. Check WiFi also... If you can turn it on and works all is good...
Helium users see if you can reboot to recovery from Advanced Power Menu, check if you can Power OFF your phone etc... the usual bugs.
Let see if these updates change anything for good or bad.
Happy testing!:good:
EDIT: Looks like 3G bug is still present in latest MIUI modem files. Flash CM_3G_fix.zip and keep the rest of the update if 3G bug is back.
Thanks a lot.
You are welcome!
Please guys lets not quote the whole OP... It takes so much screen...
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Maybe not... Give me a mnute...
That's what happens when you code unix script on windows and forget to convert it.
@JulianJenner
EDIT: FIXED(i think)...Try now and let me know it works or not!? Helium feedback appreciated...
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
JulianJenner said:
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
Click to expand...
Click to collapse
Did you redownload the fixed zip? Do you have the "/sdcard/vendor_update" folder with the files in it?
Make sure you copy text line by line hitting ENTER after each one!!! That's 4 lines... su... cp... chmod... sh...
Hydrogen works for me... Can't test helium unfortunately...
Terminal running successfully.
Phone reboot.
But my BB and Kernel version did not changed...
Yours Mon Aug 29
Mine Wed Jun 29
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No. I will download again. A.S.A.P.
---------- Post added at 11:18 PM ---------- Previous post was at 11:01 PM ----------
Working.
It was my fault.
"...line by line hitting ENTER after each one..."
Firstly I did not understand it.
I pressed Enter after at the end once...
Click to expand...
Click to collapse
Phew... I thought I screwed up again...
Run this in terminal emulator:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Upload /sdcard/boot.img somewhere... I will update kernel and you will flash it... Let see if version changes. Maybe Xiaomi haven't updated helium kernel yet!? But it is definitely different from the hydrogen latest one byte by byte...
Baseband was probably already updated if you are running ajsmsg78's RR.
I did.
Upload...
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
I did.
And now?
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Go to sdcard and you will find boot.img in there, upload it somewhere and give me the link...
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Just checked helium kernel with hex editor and the date is Fri Sep 2 23:22:31 CST...
Have no idea why it didn't update since script did not throw any error, right? Did the phone reboot to recovery and flashed the vendor zip?
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
Did the phone reboot to recovery and flashed the vendor zip?
Click to expand...
Click to collapse
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
Where is this vendor zip ( okay, I find it. vendor_update-HELIUM.zip)? Can I flash it from TWRP?
I have stock recovery, I used TWRP from Fastboot mode 'fastboot boot recovery.img' command...
Click to expand...
Click to collapse
Yes you can but first kernel has to get updated or wifi won't work.
And thats not the point... I want to see why script did not do the job but I will debug it with someone else...
Here is updated kernel link removed
Download it to /sdcard/boot_updated.img and run this in terminal:
Code:
su
hit enter
Code:
dd if=/sdcard/boot_updated.img of=/dev/block/bootdevice/by-name/boot
hit enter
After that reboot to recovery and flash that vendor_update-HELIUM.zip
Post versions, please...
OK. I think solved by myself.
Ran script again in adb shell.
And when phone tried to reboot recovery.
I stopped it with buttons.
Reboot in Fastboot mode with buttons.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
Click to expand...
Click to collapse
Aaah, I got it... that can't reboot recovery bug for helium ... I will change script to not boot automatically and let helium users boot to TWRP manually and it will flash vendor zip automatically. Didn't get that bug under consideration.
Thank you for opening my eyes Hate when I can't test things...
This is mine, helium, seems it has been success, I use the one you posted at the first.
@nijel8... your work is a hard work!
I am proud to be working with you.
laolang_cool said:
This is mine, helium, seems it has been success, I use the one you posted at the first.
Click to expand...
Click to collapse
Great...:good: Seems like you don't suffer from hydrogen kernel.