{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod for Moto Z. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the ZIP file from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround" (if it's not working check out troubleshooting in next Post)
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/nkk71/multirom
Modified TWRP - https://github.com/nkk71/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/motoTurboZ/android_device_motorola_griffin---MR
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
XDA:DevDB Information
MultiRom for Moto Z, Tool/Utility for the Moto Z
Contributors
erfanoabdi
Source Code: https://github.com/motoTurboZ/android_device_motorola_griffin---MR
Version Information
Status: Testing
Current Beta Version: 33
Beta Release Date: 2016-12-06
Created 2016-12-06
Last Updated 2017-03-30
Video :
Downloads :
IT WILL NOT WORK WHEN ENCRYPTED
https://www.androidfilehost.com/?w=files&flid=140728
Old Versions :
TWRP : https://mega.nz/#!mQpzyRJL!rfWAhx9ZFKgL_WQ2I0dcZ6aSWtqJE98YYByXAaIK5ZU
Multirom : https://mega.nz/#!zFRjjA7I!v_EehAAX0REmVX7DC_y2M7Dl0B-q91K50VxTNT0Ut8E
Multirom Uninstaller : https://mega.nz/#!OEZAEbRK!p8qVatt_YcctZ4cbRR7CK9Mou6oaPT1YN-5NKCc1lh8
How to install :
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Changelog :
26 March :
- Nougat Support
- TouchScreen Fixed
30 December :
- SD Card and OTG Fixed
- Updated Multirom and TWRP
- modded Multirom Manager app
09 December :
- initial build
Bugs/issues :
*Let me know, i'll add them here and consider it my todo list on this
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to nkk71
[url]http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4[/URL]
Troubleshooting :
no-kexec workaround is enabled on TWRP but not working in Multirom :
go to "/data/media/0/multirom/multirom.ini" and set "no_kexec=1" (from 0 to 1)
Multirom manager app doesn't recognize your device :
make sure you're using my modded app and add this line
ro.product.device=griffin
into your build.prop at the root of system partition
Moto mods not working :
copy "init.gbmods.sh" from root in somewhere at your data partition like "/data/local/"
Than use init.d of kernel adiutor app to call it like :
Code:
chmod 0755 /data/local/init.gbmods.sh
chmod +x /data/local/init.gbmods.sh
./data/local/init.gbmods.sh
Hi thanks for the Multirom support...
Twrp works just fine but while flashing Multirom zip it give some update error 7
Here is the recovery log :
erfanoabdi said:
info : http://forum.xda-developers.com/oneplus-3/development/multirom-v33b-op3-t3415654
XDA:DevDB Information
MultiRom for Moto Z, Tool/Utility for the Moto Z
Contributors
erfanoabdi
Source Code: https://github.com/motoTurboZ/android_device_moto_griffin
Version Information
Status: Testing
Current Beta Version: 33
Beta Release Date: 2016-12-06
Created 2016-12-06
Last Updated 2016-12-06
Click to expand...
Click to collapse
Does it work with forced encryption enabled?
gomisensei said:
Does it work with forced encryption enabled?
Click to expand...
Click to collapse
No it's not working on encrypted phones
I'm a little bit busy on cm14 I'll add encryption support as soon as possible
@erfanoabdi I've been considering this phone for my next upgrade. I was starting to lean towards not buying, but you just made my decision for me. It will be my first multiROM experience when I get it :laugh:
erfanoabdi said:
No it's not working on encrypted phones
I'm a little bit busy on cm14 I'll add encryption support as soon as possible
Click to expand...
Click to collapse
CM14!! Super excited!
immadeofpixels27 said:
@erfanoabdi I've been considering this phone for my next upgrade. I was starting to lean towards not buying, but you just made my decision for me. It will be my first multiROM experience when I get it :laugh:
Click to expand...
Click to collapse
thanks man
but you need to know there's no kernel with kexec support for this device and on my kernel i need some one to help me to fix it (https://github.com/motoTurboZ/kernel-msm/tree/kexec) if no one add kexec support we can't use secondary roms on multirom
and "nkk71 no kexec" is not working with motorola stock rom and having 2 CM in multirom is just funny
so we have to wait for a good developer, someone smarter than me to fix kexec for multirom :good:
by buying moto z you won't lose anything this is first high-end phone with multirom support (except oneplus 3(T)) and no one had success to add kexec to msm8996 (it's possible on msm8994)
i'm trying by best to develop my kernel and other stuffs for you and other moto z lovers
when i done my device tree for moto z, porting other roms for moto z will be too easier and hopefully we can see more roms for this amazing hardware in near future :fingers-crossed:
erfanoabdi said:
thanks man
but you need to know there's no kernel with kexec support for this device and on my kernel i need some one to help me to fix it (https://github.com/motoTurboZ/kernel-msm/tree/kexec) if no one add kexec support we can't use secondary roms on multirom
and "nkk71 no kexec" is not working with motorola stock rom and having 2 CM in multirom is just funny
so we have to wait for a good developer, someone smarter than me to fix kexec for multirom :good:
by buying moto z you won't lose anything this is first high-end phone with multirom support (except oneplus 3(T)) and no one had success to add kexec to msm8996 (it's possible on msm8994)
i'm trying by best to develop my kernel and other stuffs for you and other moto z lovers
when i done my device tree for moto z, porting other roms for moto z will be too easier and hopefully we can see more roms for this amazing hardware in near future :fingers-crossed:
Click to expand...
Click to collapse
Well,i wasn't planning on getting it immediately anyway. Keep up the awesome work :good:
erfanoabdi said:
thanks man
but you need to know there's no kernel with kexec support for this device and on my kernel i need some one to help me to fix it (https://github.com/motoTurboZ/kernel-msm/tree/kexec) if no one add kexec support we can't use secondary roms on multirom
and "nkk71 no kexec" is not working with motorola stock rom and having 2 CM in multirom is just funny
so we have to wait for a good developer, someone smarter than me to fix kexec for multirom :good:
by buying moto z you won't lose anything this is first high-end phone with multirom support (except oneplus 3(T)) and no one had success to add kexec to msm8996 (it's possible on msm8994)
i'm trying by best to develop my kernel and other stuffs for you and other moto z lovers
when i done my device tree for moto z, porting other roms for moto z will be too easier and hopefully we can see more roms for this amazing hardware in near future :fingers-crossed:
Click to expand...
Click to collapse
Wait, doesn't only the main rom have to have kexec support? that's how multirom on my HTCm8 worked...
gomisensei said:
Wait, doesn't only the main rom have to have kexec support? that's how multirom on my HTCm8 worked...
Click to expand...
Click to collapse
Yes only primary kernel should have kexec hardboot support
erfanoabdi said:
Yes only primary kernel should have kexec hardboot support
Click to expand...
Click to collapse
so you could have cm as primary, and stock motorola as secondary (after making a nandroid backup of course)
gomisensei said:
so you could have cm as primary, and stock motorola as secondary (after making a nandroid backup of course)
Click to expand...
Click to collapse
I tried this but I got bootloop
I didn't play with this so much but next week I'll
Test more and tell about it
Good Newsss and Updates
my new year gift for you guys is new version of multirom
30 December Update :
OTG fixed
SD Card fixed
Updated Multirom and TWRP sources
and the Big one :
Now you can Multirom Stock and CM together
How to install CM and Stock Rom together ?
first if you're on stock make full backup (system, data, boot) with TWRP
if you're on CM and don't have stock backup, please uninstall it and go back to stock to get backup
now
install multirom TWRP
install CM14 (or other custom rom)
install multirom zip
reboot and setup your CM (maybe you need to change multirom.ini for nkk71-no-kexec boot [see troubleshooting])
go back to recovery
and use multirom setting to install your stock rom backup as secondary rom
reboot
ENJOY
i've only tested this with MM and turboZ kernel but this should work with N too
i've not tested stock as primary and CM as Secondary rom and not sure it's working
root (and xposed) is working well on primary and Secondary roms
you can also install 3 or 4 roms together with this method
:fingers-crossed: :fingers-crossed: :fingers-crossed:
erfanoabdi said:
Good Newsss and Updates
my new year gift for you guys is new version of multirom
30 December Update :
OTG fixed
SD Card fixed
Updated Multirom and TWRP sources
and the Big one :
Now you can Multirom Stock and CM together
How to install CM and Stock Rom together ?
first if you're on stock make full backup (system, data, boot) with TWRP
if you're on CM and don't have stock backup, please uninstall it and go back to stock to get backup
now
install multirom TWRP
install CM14 (or other custom rom)
install multirom zip
reboot and setup your CM (maybe you need to change multirom.ini for nkk71-no-kexec boot [see troubleshooting])
go back to recovery
and use multirom setting to install your stock rom backup as secondary rom
reboot
ENJOY
i've only tested this with MM and turboZ kernel but this should work with N too
i've not tested stock as primary and CM as Secondary rom and not sure it's working
root (and xposed) is working well on primary and Secondary roms
you can also install 3 or 4 roms together with this method
:fingers-crossed: :fingers-crossed: :fingers-crossed:
Click to expand...
Click to collapse
After flashing latest multirom.zip all the mods stopped working.
Sent from my Pixel using XDA-Developers mobile app
silvercat said:
After flashing latest multirom.zip all the mods stopped working.
Click to expand...
Click to collapse
Yes if you want to make them working you need to copy init.gbmods.sh from root in somewhere at your data partition
Than use init.d of kernel adiutor to call it like :
Code:
chmod 0755 /data/local/init.gbmods.sh
chmod +x /data/local/init.gbmods.sh
./data/local/init.gbmods.sh
This is happening because multirom change some permissions accidentally
This method is tested on stock Motorola rom as secondary
Tried dual booting with lineage and it's not working. Used lineage as my primary and stuff but still no luck. Lineage boots up fine as it's the internal (primary) ROM but when you select stock it'll just reboot back into multirom and not boot at all
I'm on the n bootloader.
ethanscooter said:
Tried dual booting with lineage and it's not working. Used lineage as my primary and stuff but still no luck. Lineage boots up fine as it's the internal (primary) ROM but when you select stock it'll just reboot back into multirom and not boot at all
I'm on the n bootloader.
Click to expand...
Click to collapse
Yes I just exactly right now tried that and same as you
Let me check for problem
This may related to stock nougat system, always want to boot from verified partition, if that's it I can't do anything
Thanks for sharing your experience
Update : Fixed
erfanoabdi said:
Yes if you want to make them working you need to copy init.gbmods.sh from root in somewhere at your data partition
Than use init.d of kernel adiutor to call it like :
Code:
chmod 0755 /data/local/init.gbmods.sh
chmod +x /data/local/init.gbmods.sh
./data/local/init.gbmods.sh
This is happening because multirom change some permissions accidentally
This method is tested on stock Motorola rom as secondary
Click to expand...
Click to collapse
I have a stock based rom as secondary and a camera mod. The camera mod works when the rom is in primary but once in secondary it doesn't. Applying this only makes it work partially. The power button responds by opening and closing the camera app, but the lens never opens up and extends. The zoom controls do nothing either.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.x
for Lenovo Tab2 A7-10F
(MT8127 only)
Disclaimer
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this
* recovery before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Always backup your device before flashing any rom/recovery/whatever
*/
Introduction
TWRP 3 built from Omnirom 5.1 sources
+ Omnirom 6.0 sources (TWRP 3.0.2)
+ Omnirom 7.1 (TWRP 3.0.3 and 3.1.x)
+ Omnirom 8.0 (TWRP 3.2.1)
+ Omnirom 8.1 (TWRP 3.2.3)
+ Omnirom 9.0 (TWRP 3.3.1)
+ Teamwin 9.0 (TWRP 3.4.0+)
Prebuilt stock 3.10.54 kernel
Features
TWRP functions (flash zip, flash img, backup, restore...)
USB OTG, Internal and external SD cards
NTFS support
Crypto enabled (don't know if it works though)
Extra languages
Changelog
3.6.2 (2022/07/22) :
Updated TWRP sources from Teamwin 9.0 branch (2022/07/22)
Older versions
3.6.1 (2022/03/16) :
Updated TWRP sources from Teamwin 9.0 branch (2022/03/13)
3.6.0 (2021/12/05) :
Updated TWRP sources from Teamwin 9.0 branch (2021/12/05)
3.5.2 (2021/04/24) :
Updated TWRP sources from Teamwin 9.0 branch (2021/04/20)
Allows flashing Magisk apk
3.4.0 (2020/08/11) : updated TWRP sources from Teamwin 9.0 branch (2020/07/30)
Allows flashing Magisk zip
3.3.1 (2019/07/07) : updated TWRP sources from Omnirom 9.0 branch (2019/07/07)
3.2.3 (2018/08/12) : updated TWRP sources from Omnirom 8.1 branch (2018/08/09)
v0.96 : updated TWRP 3.2.1 sources from Omnirom 8.0 branch (2017/12/08)
v0.64 : updated TWRP 3.1.1 sources from Omnirom 7.1 branch (2017/05/12)
Wipes should be faster
v0.41 : updated TWRP 3.1.0 sources from Omnirom 7.1 branch (2017/03/18)
v0.24 : updated TWRP 3.0.3 sources from Omnirom 7.1 branch (2017/02/13)
v0.18 : updated TWRP 3.0.3 sources from Omnirom 7.1 branch (2017/01/03)
v0.13 : mount USB Storage working, updated source (2016/07/03)
v0.12 : (removed) initial xda release, updated sources (2016/06/19)
Downloads
latest file from androidfilehost
If you use an unmodified stock KK or LP rom, stock recovery will be self installing again unless you flash KK_LP_no_stock_recovery.zip patch.
In TWRP, you need to be sure that "Mount system partition read-only" is unchecked in "Mount" menu before flashing this patch
Installation instructions
3 ways to install this recovery
Using SP Flash Tool
Prerequisites
Install MTK USB Drivers (windows xp/vista/7 - Windows 8/8.1/10 - other windows 10)
SP Flash Tool (howto)
In SP Flash Tool, always use "Download Only" mode when not explicitly asked to do otherwise (you could lose your IMEI/WIFI/BT) or if you don't know what you are doing.
Please do NOT ask about any problem with USB drivers or SP Flash Tool here in this thread, this is not the right place for it as these problems are not related to THIS particular recovery but to YOUR computer setup. There are other threads and/or sites about such problems.
Installation
power off the tablet
launch SP Flash Tool, click on "Download" tab
click "scatter-loading" button and choose the downloaded scatter file (MT8127_Android_scatter-recovery_only.txt is based on LP stock rom)
on the "RECOVERY" line, click the empty "Location", and choose the downloaded recovery img file
click "Download"
plug your tablet on USB
Using previous already installed TWRP
reboot to recovery
"Install"
"Install Image"
choose the recovery img to flash
choose "Recovery" partition
"swipe to confirm Flash"
Using an application (root needed)
such as Rashr
Boot to recovery
Turn your tablet off
Push Power button + Volume- + Volume+ buttons
Keep the buttons pushed untils boot logo appears
Thanks to/Credits
TeamWin
Omnirom
How to compile TWRP touch recovery (Dees_Troy)
TWRP Flags for BoardConfig.mk (MSF Jarvis)
Contributors
pix106
Source Code: https://github.com/LenovoTab2A7[/hide]
Reserved
Now time for new rom , i think you should try out building any cm based rom , omni is 75% Aosp so there might be some issues.
Sent from my A311 using XDA-Developers mobile app
[email protected] said:
Now time for new rom , i think you should try out building any cm based rom , omni is 75% Aosp so there might be some issues.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
How can AOSP be an issue ? I always choose opensource when possible.
pix106 said:
How can AOSP be an issue ? I always choose opensource when possible.
Click to expand...
Click to collapse
For mediatek open sources are not totally compatible with aosp's . every mtk chipset has same issue. So you can try out other others.
Sent from my A311 using XDA-Developers mobile app
[email protected] said:
For mediatek open sources are not totally compatible with aosp's . every mtk chipset has same issue. So you can try out other others.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, i may try some other rom though.
Thanks for your advice.
Do you have any info/link to mediatek sources ?
[email protected] said:
For mediatek open sources are not totally compatible with aosp's . every mtk chipset has same issue. So you can try out other others.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yep,agreed.With the years cyanogenmod went on its own and its not really based on aosp right now,while omni is more aosp based rom.
pix106 said:
Ok, i may try some other rom though.
Thanks for your advice.
Do you have any info/link to mediatek sources ?
Click to expand...
Click to collapse
You can try out official sources with stock kernel , i have only links for mt6582 and mt6592 sources for now.
Sent from my A311 using XDA-Developers mobile app
---------- Post added at 03:31 AM ---------- Previous post was at 02:52 AM ----------
[email protected] said:
You can try out official sources with stock kernel , i have only links for mt6582 and mt6592 sources for now.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
Can you link me any device/vendor tree . I'll try to compile cm12.1.
Sent from my A311 using XDA-Developers mobile app
[email protected] said:
You can try out official sources with stock kernel , i have only links for mt6582 and mt6592 sources for now.
Sent from my A311 using XDA-Developers mobile app
---------- Post added at 03:31 AM ---------- Previous post was at 02:52 AM ----------
Can you link me any device/vendor tree . I'll try to compile cm12.1.
Sent from my A311 using XDA-Developers mobile app
Click to expand...
Click to collapse
A few month ago, with a friend we did this for omnirom, we got boot (prebuilt kernel), graphics, but no wifi etc... : https://github.com/PixNDom/android_device_lenovo_Tab2A710F https://github.com/PixNDom/android_vendor_lenovo_Tab2A710F (other repos https://github.com/PixNDom).
We stopped as we did not know how to go on.
Yesterday after your advice i started a cm12.1 branch on my github (https://github.com/pix106/android_device_lenovo_Tab2A710F/blob/cm12.1), and got TWRP running using cm12.1 sources (with wrong device id, but it does not matter now).
I tried building the kernel again using lenovo sources (https://github.com/pix106/android_kernel_lenovo_Tab2A710F/tree/lenovo_osc_201511), with cm12, i got the same result than i got with omnirom : no graphics, "GTP Reset", i2C errors...
Thanks for your help
Let's go on these custom rom discussion there : http://forum.xda-developers.com/and...ustom-rom-lenovo-tab2a7-t3407069#post67513305
v0.13 : mount USB Storage working, sources updated on 2016/07/03
how to boot into recovery ?
volume up + power ?
No.. Volume up + volume down + power
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
while trying to perform wipe using this recovery, my tab's system and data partition got corrupted. And now only boot splash screen showing. plz help me. What should i do now??
mayank22 said:
while trying to perform wipe using this recovery, my tab's system and data partition got corrupted. And now only boot splash screen showing. plz help me. What should i do now??
Click to expand...
Click to collapse
I don't see how it could be only related to this recovery, i have wiped partitions at least a hundred times with it without any problem.
I don't know what corrupted your partitions, I suppose you'll have to restore your latest backup, or flash a rom if you don't have a backup.
pix106 said:
I don't see how it could be only related to this recovery, i have wiped partitions at least a hundred times with it without any problem.
I don't know what corrupted your partitions, I suppose you'll have to restore your latest backup, or flash a rom if you don't have a backup.
Click to expand...
Click to collapse
Yeah i have the backup but it too can't be restored. It gets stuck at wiping system partition....
I tried flashing stock firmware, bt sp flash tool is giving error, " error passing bootrom. May be device power on too soon" while i can see vcom device attached and functional in windows device manager. Now what should i try??
mayank22 said:
Yeah i have the backup but it too can't be restored. It gets stuck at wiping system partition....
I tried flashing stock firmware, bt sp flash tool is giving error, " error passing bootrom. May be device power on too soon" while i can see vcom device attached and functional in windows device manager. Now what should i try??
Click to expand...
Click to collapse
You can try "use rm -rf instead of formatting" in twrp options.
Or search for a partition corruption thread, as it's not a problem of this recovery.
pix106 said:
You can try "use rm -rf instead of formatting" in twrp options.
Or search for a partition corruption thread, as it's not a problem of this recovery.
Click to expand...
Click to collapse
got it working bro by flashing stock rom back from your package. TYSM
@pix106 bro, i tried to install your recovery again but sp flash tools didn't have success. But through rashr flash tool, it got installed. But again on wiping cache, i got stuck and the partition got corrupted. I just restored stock firmware. I think i will just have to use the older version of twrp
Why is my custom recovery showing in Chinese language
Team Win Recovery Project 3.2.2-0
This is for the Lenovo P2a42 only! Do not flash on the Lenovo P2c72!
WARNING: Rooting The Lenovo P2 with SuperSu currently works only in System-Mode, which prevents you from installing OTA Updates!
INFO: Follow the full rooting steps below, in order, to allow system modifications!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the Official Download here (Version: 3.2.2-0): recommended!
https://goo.gl/UbHbkr
You can find the Pre-Official Download here:Currently no Pre-Official!
See Post #3
This is the download link, for instructions on how to flash it, see below.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/ install adb & fastboot to your computer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download TWRP for Lenovo P2 (P2a42).
In your ROM, go to Settings -> About device. Tap 8 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Once you tap the unlock the bootloader it will ask you to formally submit the request, when you accepted the void warranty thing you will have to wait 14 days.
After 14 days . Reboot your device into fastboot mode. To do this, (adb reboot-bootloader) or select reboot from the power menu and hold the [Volume Down] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run this command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run these commands in order:
fastboot flash recovery twrp.img
fastboot boot twrp.img
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger system modifications for TWRP and TWRP will be installed permanently!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted see Post #2:
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.3-0 (beta) - Initial public beta v1 release.
v3.0.3-0 (beta) - public beta v2 release.
- Enable double-tap to wake in recovery
- Fixed MTP Issues
v3.0.3-0 (Official) - public release.
- fix device name for update.zip's
3.1.1-0 (Official) - Official release.
- Completely rebased on Nougat
- Included OTA support.
3.1.1-1 (Official) - Official release.
- Fix "Format Data" when using default (f2fs)
- Enabled OTA support.
3.2.1-0 (Official) - Official release.
- TWRP base Android 8.1
3.2.2-0 (Official) - Official release.
- TWRP 3.2.2-0 build
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
ADB root
Full SELinux support
Built in android 8.1 tree
KNOWN ISSUES
SuperSU will only work by default in System-Mode because the data partition is F2FS! (by default from Lenovo)
SuperSu's Systemless Mode will work when the data partition is changed to EXT4!
DECRYPTION NOT WORKING?
If your device isn't decrypting in TWRP, chances are you set a boot up password.
You can solve this by disabling your boot up password in your device OS's settings.
By disabling your password your OS will rewrite your crypto key to be compatible with TWRP and TWRP will decrypt with the default password.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
CONTACT & SUPPORT
You can find TeamWin on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/Celoxocis/android_device_lenovo_kuntao_row (android-7.1)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the Lenovo P2, Tool/Utility for the Lenovo P2
Contributors
celoxocis, Maintainer & Developer
Gilotto, Closed Beta Tester
HaJeeEs, Closed Beta Tester
Version Information
Status: Official
Current Official Version: 3.2.2-0
Official Release Date: 2018-07-07
Created 2016-01-07
Last Updated 2018-07-07
Download Counter:
Initial Beta Release v1: 57
Initial Beta Release v2: 20
Official Version: It's Over 5000!
So you are generation Y? too much to read or you don't real at all? Prefer a video? Head over to Youtube!
Video Tutorials on Youtube for Systemless Mode ROOT METHOD
How to ROOT LENOVO P2 | Install TWRP Recovery | Works on Marshmallow Only
How to ROOT Lenovo P2 with Android Nougat | Lenovo P2 Root Tutorial
Thanks to TechXplicit
You don't like command lines? Prefer to click your way through life? Take a look at the Lenovo P2 Root Tool! Head over to Youtube!
Lenovo P2 Root Tool!
Thanks to Varun Sai
----- General Information -----
All donations which are send to me (TWRP appreciation donations)
Will be put forward to support the Official LineageOS development.
Donation Link, please see my signature!
Official TWRP vs LineageOS TWRP
I am on Lenovo's STOCK ROM! All i want is root with STOCK ROM! I don't care about treble! Is this version for me?
YES!!!
I hate the Lenovo STOCK ROM! I want LineageOS Official and root! I want treble and Magisk! Is this TWRP version for me?!
NO!!! Why? Please read this!
Confirmed and working ROOT methods!
Up-to-date: For root with Nougat please use phh's supersu
Use version 2.59 from here
Install phh's SuperUser in the Play Store
to manage root access of apps.
Simply flash it and enjoy.
--------------------------------
If you prefer Magisk:
Prio to installing Magisk you will have to change the data partition from F2FS to EXT4 because the Lenovo Kernel is missing an F2F2 feature.
How to format data to EXT4:
Make sure while the first time you boot TWRP.
You "KEEP SYSTEM in READ ONLY MODE" by clicking "Keep Read Only"
then Go to:
Wipe>Advanced Wipe>Select "Data">Repair or Change File System>Change File System>EXT4
Install Magisk
and once you booted up the system install Magisk manager.
Proof that Magisk works see attachment!
too much to read? Prefer a video? Head over to Youtube!
Video Tutorials on Youtube for Systemless Mode ROOT METHOD
How to ROOT LENOVO P2 | Install TWRP Recovery | Works on Marshmallow Only
How to ROOT Lenovo P2 with Android Nougat | Lenovo P2 Root Tutorial | Works on Nougat!
Thanks to TechXplicit
You don't like command lines? Prefer to click your way through life? Take a look at the Lenovo P2 Root Tool! Head over to Youtube![/SIZE]
Lenovo P2 Root Tool!
Thanks to Varun Sai
--------------------------------
Outdated Root Method for Marshmallow ONLY:
Here is for confirmed and working ROOT METHODS !!! Marshmallow ONLY !!!
(FOR SYSTEM MODE ROOT ONLY!)
download this pack https://goo.gl/KFtyzl
and extract its content into the adb&minimal fasboot folder
enter TWRP
do
Code:
adb push dot.supersu /data/.supersu
Select "ADB Sideload" in TWRP menu, (Advanced>ADB Sideload) make sure to select "Wipe Cache" and
Swipe to to Start Sideload and use following command to push SuperSu files.
Code:
adb sideload SuperSU.zip
Reboot into System. Done!
--------------------------------
FOR SYSTEMLESS MODE ROOT ONLY: (preferred method!) !!! Marshmallow ONLY !!!
As i stated in the Opening Thread. SuperSu can not be installed in Systemless-Mode by default because by default the /data partition is formated in F2FS.
More detailed explanation here: here
The current workaround is to disable the encryption (fully optional) and wipe the /data partition and format the /data partition to EXT4, which is also supported by the boot.img (thank you Lenovo!) and install SuperSu in Systemless-Mode. EXT4 formatting can be done through the "advanced wipe" of TWRP.
It has been tested and confirmed working. The main advantage is working OTA due to systemless SuperSu. As the OTA doesn't care if /data is actually F2FS or EXT4. Lenovo was so kind to provide both options in the stock boot.img.
Factory Images for P2a42 Marshmallow/Nougat & TWRP Test Image & Kernel Sources
Q: I messed up help me?! :crying:
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
(FACTORY IMAGES FOR Marshmallow ONLY!)
Warning! Following images are all confirmed working for the P2a42!
Do NOT attempt to use it on the P2c72 it will brick your device!
If you need an P2c72 factory flasher version! Let me know i will provide you with one!
Download the Factory State Images for Marshmallow. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock recovery. Simply run:
Code:
fastboot flash recovery recovery.img
You can also replace all partitions if required.
There is an flashall.bat file in the SW directory. Run it in case you want to restore all partitions.
But i highly recommend to replace just the partition you messed up. In most cases it will be boot,recovery or system.
One exception would be if you want to upgrade from an Old Firmware and you simply do not receive any OTA update files.
In that case you want to run a complete upgrade by running the flashall.bat file.
(FACTORY IMAGES FOR Nougat ONLY!)
Warning! Following images are all confirmed working for the P2a42!
Do NOT attempt to use it on the P2c72 it will brick your device!
If you need an P2c72 factory flasher version! Let me know i will provide you with one!
Download the Factory State Images for Nougat. Which are all flashable with fastboot: https://goo.gl/b7Dx37
too much to read? again?! do you ever read?
don't worry TechXplicit got you covered!
Head over to Youtube!
Lenovo P2 STOCK Firmware | Restore Bootlooped Lenovo P2 | How to get back to OTA updates
Thanks to TechXplicit
--------------------------------
Pre-Official TWRP Images:
TWRP 3.2.2-0 (latest version)
Currently no Pre-Official.
Q: Why Pre-Official?
A: It's is an "canary build" meaning, in test phase before it gets pushed Official but it is fully tested on Marshmallow and Nougat. Even confirmed working for the P2c72.
--------------------------------
Lenovo P2a42 Kernel Sources for Marshmallow/Nougat:
Official Lenovo Download Link
Great work,
Now only an seperate forum :laugh:
Shall i request it?
wimmetje said:
Great work,
Now only an seperate forum :laugh:
Shall i request it?
Click to expand...
Click to collapse
No need to I will request one once I upload all sources and pushed TWRP Official.
As a reminder! Always create a backup of the boot and system partition (as image!) before installing anything to stay save!
celoxocis said:
Small Update: DO NOT Flash the latest System-Mode SuperSU. It was reported to cause a bootloop on the Lenovo P2. Stick with Version 2.76!
As a reminder! Always create a backup of the boot and system partition (as image!) before installing anything to stay save!
Click to expand...
Click to collapse
I was to fast! I installed version 2.79. I reinstalled version 2.76, but it wont boot Any idea how I can fix it? Of course I'm an idiot who didn't make a back up.
BDM101 said:
I was to fast! I installed version 2.79. I reinstalled version 2.76, but it wont boot Any idea how I can fix it? Of course I'm an idiot who didn't make a back up.
Click to expand...
Click to collapse
Look for "Unsu" script here in the forum. It will take you out from the bootloop.
celoxocis said:
Look for "Unsu" script here in the forum. It will take you out from the bootloop.
Click to expand...
Click to collapse
Thx!!!! That worked
Updated Post #2 here https://forum.xda-developers.com/showpost.php?p=70435635&postcount=2
for confirmed and working Root Method!
Fantastic! Is possible to have a separate forum for the p2?
celoxocis said:
Updated Post #2 here https://forum.xda-developers.com/showpost.php?p=70435635&postcount=2
for confirmed and working Root Method!
Click to expand...
Click to collapse
If I want to sideload the zip file, I got the error "error: no devices/emulators found". But for everything else ADB works.
Dagnelino said:
Fantastic! Is possible to have a separate forum for the p2?
Click to expand...
Click to collapse
It will be requested by the topic starter when twrp will be officiall
BDM101 said:
If I want to sideload the zip file, I got the error "error: no devices/emulators found". But for everything else ADB works.
Click to expand...
Click to collapse
It think you need the latest adb version for it to work. Closed Beta Testers confirmed adb sideload as working.
celoxocis said:
It think you need the latest adb version for it to work. Closed Beta Testers confirmed adb sideload as working.
Click to expand...
Click to collapse
I tried the default adb version in Fedora 25 and the latest one from https://forum.xda-developers.com/showthread.php?t=2317790 in a vm, but non of them work.
I guess I'm gonna be root-less for a while
BDM101 said:
I tried the default adb version in Fedora 25 and the latest one from https://forum.xda-developers.com/showthread.php?t=2317790 in a vm, but non of them work.
I guess I'm gonna be root-less for a while
Click to expand...
Click to collapse
I don't know about the Linux based adb. Testers used Windows as hosts.
celoxocis said:
I don't know about the Linux based adb. Testers used Windows as hosts.
Click to expand...
Click to collapse
I also tried it on windows (a windows 10 virtual machine) with "Minimal ADB and Fastboot" version 1.4.2 and still wont work.
BDM101 said:
I also tried it on windows (a windows 10 virtual machine) with "Minimal ADB and Fastboot" version 1.4.2 and still wont work.
Click to expand...
Click to collapse
I don't think it works on a virtual machine because of the USB passthrough. I know that ADB sideload works as it was confirmed by the Testers.
Instead of using sideload. Try by placing the SuperSu.zip onto the internal storage /data. And select the zip for install.
celoxocis said:
I don't think it works on a virtual machine because of the USB passthrough. I know that ADB sideload works as it was confirmed by the Testers.
Instead of using sideload. Try by placing the SuperSu.zip onto the internal storage /data. And select the zip for install.
Click to expand...
Click to collapse
Still in a bootloop. Maybe the "UnSu" script isn't deleting everything? (it boots when I run the script)
BDM101 said:
Still in a bootloop. Maybe the "UnSu" script is't deleting everything? (it boots when I run the script)
Click to expand...
Click to collapse
It depends on how often you tried to install SuperSU. It will revert all changes when you run SuperSu once. If you tried it more than once then the backup folder will overwrite the data with already patched data.
Grab the stock images packages from post #3 and extract it's content.
No need to restore all the partitions.
Just open up the *.Bat file and look for the command that says "fastboot flash boot boot.img" and the parts that say "fastboot flash system systemchunk*" and run those in fastboot shell.
You will be back to stock without losing any of your data.
Then try again with the confirmed method in post #2. Just make sure you create a backup of boot and system (as image!) In case you need to restore. Let's say for applying an OTA.
Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Reserved
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app
rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?
Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.
Everything went smooth! Thank you so much!
rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.
No problems at all... Everything went perfect!
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.
need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921
ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei P10.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 3 ROMs in total as of now - LineageOS (Unofficial), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei P10
Contributors
OldDroid, XePeleato, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-27
do you know anyway in which i could unlock my bootloader?
JohnnyMwanza said:
do you know anyway in which i could unlock my bootloader?
Click to expand...
Click to collapse
DC Unlocker is the only way to go as Huawei stopped releasing bootloader unlock codes since July 22, 2018.
I installed the Resurrection Remix and Lineage rom on my P10+ (VKY L29) device and both got me the same problem:
When i boot (the boot is successful), Google starts the first configuration. It asks me the language and the visual properties and then i press "next". The screen remains on "Just a second..." for about forever.
I tried format data before and after, tried to install several Treble roms... Everything took me to the same problem.
I tried also to re-install Gapps, but this took me to another problem: the Google First Configuration is totally black.
What should i do?
McEyes said:
I installed the Resurrection Remix and Lineage rom on my P10+ (VKY L29) device and both got me the same problem:
When i boot (the boot is successful), Google starts the first configuration. It asks me the language and the visual properties and then i press "next". The screen remains on "Just a second..." for about forever.
I tried format data before and after, tried to install several Treble roms... Everything took me to the same problem.
I tried also to re-install Gapps, but this took me to another problem: the Google First Configuration is totally black.
What should i do?
Click to expand...
Click to collapse
Its a know glitch, just reboot and try again.
netmaniack said:
Its a know glitch, just reboot and try again.
Click to expand...
Click to collapse
I tried rebooting about 10 times and he always did the same.
Fortunately I figured out how to resolve this hell:
The Google first configuration setup checks the integrity of the ramdisk Partition. I had a custom recovery so obviously the check was not satisfied.
The solution is to flash the stock recovery ramdisk partition (in my case i download The Official update of Huawei p10 Plus and extracted only the ramdisk image).
When i finished the configuration I completed every setup and then I reinstalled the custom recovery again.
McEyes said:
Fortunately I figured out how to resolve this hell:
The Google first configuration setup checks the integrity of the ramdisk Partition. I had a custom recovery so obviously the check was not satisfied.
The solution is to flash the stock recovery ramdisk partition (in my case i download The Official update of Huawei p10 Plus and extracted only the ramdisk image).
When i finished the configuration I completed every setup and then I reinstalled the custom recovery again.
Click to expand...
Click to collapse
If you have properly read the instructions in OpenKirin website, it was clearly stated there that all these ROMs must be installed wirh stock recovery to avoid other issues.
ej8989 said:
If you have properly read the instructions in OpenKirin website, it was clearly stated there that all these ROMs must be installed wirh stock recovery to avoid other issues.
Click to expand...
Click to collapse
True, I've read the disclaimer, but if someone, like me, used to install ROMs with the same warning without any problem (like an AOSP rom on my previous phone, which I installed having the TWRP), maybe he/she would think that there is not so much to worry about.
However, I noticed that there isn't a real "guide" on internet about a workaround of the "Just a sec" problem, so I wrote that message also for who needs a help and does not know about the partition check.
I found a bug on the "display" menu.
When i select a theme (light, dark, or the black switch), the system theme doesn't change at all. Tried to reboot, clear cache and data of SystemUI, nothing changed.
I bypassed this theme issue with Substratum. Didn't get any bug/problem with Substratum.
Device: P10 plus VKY-L29
Rom: Resurrection Remix 6.1.0 - Oreo - 2018.08.18
McEyes said:
I found a bug on the "display" menu.
When i select a theme (light, dark, or the black switch), the system theme doesn't change at all. Tried to reboot, clear cache and data of SystemUI, nothing changed.
I bypassed this theme issue with Substratum. Didn't get any bug/problem with Substratum.
Device: P10 plus VKY-L29
Rom: Resurrection Remix 6.1.0 - Oreo - 2018.08.18
Click to expand...
Click to collapse
for me working normal
how to root ? can i flash normal magisk or need special for huawei device?
doktor29 said:
for me working normal
how to root ? can i flash normal magisk or need special for huawei device?
Click to expand...
Click to collapse
If you use a normal Huawei EMUI system, there is a special treatment which use a special SuperSu zip file.
Also, you can use a Magisk version, always optimized for Huawei. I found the zip variant in a thread in the P10+ section.
If you have the Treble ROM, which is the main topic of the thread, I did this:
Ensured that there were no setups to do;
Re-flashed TWRP;
Installed the normal Magisk zip from TWRP.
Because is not a EMUI system anymore, you can easily install every mod or patch you wish.
Personal note: I tried install SuperSu with the zip, but the app said "binary occupied". Since it did like that before, with the EMUI system, I gave up and I installed Magisk.
Now it works like a charm.
McEyes said:
If you use a normal Huawei EMUI system, there is a special treatment which use a special SuperSu zip file.
Also, you can use a Magisk version, always optimized for Huawei. I found the zip variant in a thread in the P10+ section.
If you have the Treble ROM, which is the main topic of the thread, I did this:
Ensured that there were no setups to do;
Re-flashed TWRP;
Installed the normal Magisk zip from TWRP.
Because is not a EMUI system anymore, you can easily install every mod or patch you wish.
Personal note: I tried install SuperSu with the zip, but the app said "binary occupied". Since it did like that before, with the EMUI system, I gave up and I installed Magisk.
Now it works like a charm.
Click to expand...
Click to collapse
can you link magisk version?
i try many official but i get info "unable to detect boot image"
doktor29 said:
can you link magisk version?
i try many official but i get info "unable to detect boot image"
Click to expand...
Click to collapse
This is the thread:
https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
It says is good even for P10.
you must flash it with TWRP
McEyes said:
This is the thread:
https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
It says is good even for P10.
you must flash it with TWRP
Click to expand...
Click to collapse
what version of recovery You use ? because still wont work, i have 3.1.1 for oreo
you have dencrypted or encrypted data ? i try to decrypt but still in recovery i dont see anything in data partition
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
any chance to get rid of this annoying notification of SDCARD after reboot ?
rom ressurection remix
---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------
antiratar said:
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
Click to expand...
Click to collapse
so how i can flash magisk without twrp ?
for me it works only data partition is not vivible due to encryption
can someone test fingerprint after reboot ?
i have strange issue, after reboot my fingerprint is not recognized anymore :/
if i add new one is ok till next reboot, then again my FP is not recognizing.
and no i dont mean it wont work berofre i put PIN/Passoword after reboot it wont work at all after reboot till i add next one :/
it happen in RR and Carbon, other roms i dont test
doktor29 said:
can someone test fingerprint after reboot ?
i have strange issue, after reboot my fingerprint is not recognized anymore :/
if i add new one is ok till next reboot, then again my FP is not recognizing.
and no i dont mean it wont work berofre i put PIN/Passoword after reboot it wont work at all after reboot till i add next one :/
it happen in RR and Carbon, other roms i dont test
Click to expand...
Click to collapse
Are you on stock kernel? Does this happen ALL the time or just random?
doktor29 said:
so how i can flash magisk without twrp ?
Click to expand...
Click to collapse
Instructions here: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
You only need to use fastboot.
ej8989 said:
Are you on stock kernel? Does this happen ALL the time or just random?
Instructions here: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
You only need to use fastboot.
Click to expand...
Click to collapse
it happen to me every reboot :/
i have only magisk with stock recovery, from instruction above
doktor29 said:
what version of recovery You use ? because still wont work, i have 3.1.1 for oreo
you have dencrypted or encrypted data ? i try to decrypt but still in recovery i dont see anything in data partition
Click to expand...
Click to collapse
I use the FromFutureRom version that is in the thread I linked before. I think is made especially for Huawei P10/P10+
My data partition is still encrypted.
In order to decrypt data you should format the so called "user data", which is the combination of /data and /sdcard. Don't have to say that you will lose everything on your internal archive, so be sure to backup everything. The external SD card will NOT be affected.
In the TWRP you can to this on the menu "format" -> "format data" -> write "yes" and format everything.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
antiratar said:
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
Click to expand...
Click to collapse
You are absolutely right, but I said that you can install TWRP or any custom rom AFTER the Treble Rom installation. I am now on Resurrection Remix Treble rom, with a TWRP recovery installed after the rom flash and everything is fine since the first boot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Evolution X 7.1 for the Xiaomi Mi Note 10 Lite [toco]
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
- Have the latest Global stable MIUI v13.0.2.0 installed
- Make sure you're running TWRP or OrangeFox for Android 13
- Boot into recovery
- Copy Rom
- Flash Rom
- Format data
- Reboot to system & #KeepEvolving
Update / Dirty Flash
- Boot into recovery
- Flash Rom
- Wipe Dalvik Cache & Cache
- Reboot to system & #KeepEvolving
Download
Donate me! / Official Chat / Device Support
Android version: 13.0.0_r6
Evolution version: 7.1
Security patch level: September 2022
Build Author: AndroidHQ254
ROM Source: [URL]https://github.com/Evolution-X[/URL]
Kernel Source:: VantomKernel
ROM Developer: Joeyhuab
XDA:DevDB Information
Evolution X, ROM for the Xiaomi Mi Note 10 Lite
Contributors
AndroidHQ254, @NeoArian
Source Code: https://github.com/Evolution-X
ROM OS Version: Android 13
ROM Kernel: Linux 4.14.292
ROM Firmware Required: Latest Stable MiUI v13.0.2.0 (Android 12)
Based On: AOSP
Version Information
Status: Stable
Created 2020-09-22
Last Updated 2022-09-22
Dirty flash is available/possible when I'm update from A.12.1 of evoX?
kavillock said:
Dirty flash is available/possible when I'm update from A.12.1 of evoX?
Click to expand...
Click to collapse
NO. This requires a clean flash
i wanted to ask befor i upgrade from omega is it stable and dose it have ay removed features , especially the spoofing for free google photos , i wish to daily this rom and thats why i want to know about the experience
I have evox Snow, but I do not remember the latest installed miui. Is there a way to check it?
i flashed it and it boots but i get a black screen the os is on i belive cause holding the pwoer button makes my phone slightly vibrate so idk whats hapening
Alenett said:
I have evox Snow, but I do not remember the latest installed miui. Is there a way to check it?
Click to expand...
Click to collapse
You need Global MIUI 13.0.2.0 and this is specified in the post
Fox_it3 said:
i wanted to ask befor i upgrade from omega is it stable and dose it have ay removed features , especially the spoofing for free google photos , i wish to daily this rom and thats why i want to know about the experience
Click to expand...
Click to collapse
It would not be shared here if it were not stable
Fox_it3 said:
i flashed it and it boots but i get a black screen the os is on i belive cause holding the pwoer button makes my phone slightly vibrate so idk whats hapening
Click to expand...
Click to collapse
Ensure you perform a proper clean flash on the right base and make sure you are formatting data using the specified TWRP or OrangeFox for Android 13
AndroidHQ254 said:
Ensure you perform a proper clean flash on the right base and make sure you are formatting data using the specified TWRP or OrangeFox for Android 13
Click to expand...
Click to collapse
I've installed the orange fox for Android 13 roms and had a bug that caused the data partition not being able to mount and it wouldn't flash any rom so i had to downgrade , but ill try it again in the near future, so i need to update my orange fox then clean install the android 13 rom
Fox_it3 said:
I've installed the orange fox for Android 13 roms and had a bug that caused the data partition not being able to mount and it wouldn't flash any rom so i had to downgrade , but ill try it again in the near future, so i need to update my orange fox then clean install the android 13 rom
Click to expand...
Click to collapse
If you are on Android 13, you should not have any mounting issues unless you have something messed up. Keep in mind that the recoveries are tested extensively before posting
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
AndroidHQ254 said:
You need Global MIUI 13.0.2.0 and this is specified in the post
Click to expand...
Click to collapse
I know that, but it is not the question i did. Simply i can avoid to reflash the original MIUI if i know the version i have already installed previously. Anyway i reflashed the original firmware before installing evox 7.1 to be sure.
Fox_it3 said:
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
Click to expand...
Click to collapse
There is a separate recovery for each Android version. So I don't understand why you are using an OrangeFox for Android 13 on Android 12. Stick to the specifications and follow instructions
Alenett said:
I know that, but it is not the question i did. Simply i can avoid to reflash the original MIUI if i know the version i have already installed previously. Anyway i reflashed the original firmware before installing evox 7.1 to be sure.
Click to expand...
Click to collapse
Just flash the latest firmware if you are not sure what you have. You don't need to flash the entire MIUI 13.0.2.0 stock rom
AndroidHQ254 said:
Just flash the latest firmware if you are not sure what you have. You don't need to flash the entire MIUI 13.0.2.0 stock rom
Click to expand...
Click to collapse
It is what i did.
Alenett said:
It is what i did.
Click to expand...
Click to collapse
All working great I hope
Fox_it3 said:
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
Click to expand...
Click to collapse
- Install latest TWRP you can find in the other thread (using fastboot).
- Flash the lastest MIUI via adb sideload and perform a format data (backup your data before this).
- Reboot to system and let the MIUI to run.
- When the MIUI is ready (on the welcome page), reboot the phone in fastboot.
Then:
- Flash the TWRP again via fastboot (the MIUI restore the standard boot).
- Reboot in recovery mode (TWRP).
- Flash the new evox via adb sideload
- Format data
Reboot to system.
There is nothing else to do or explain. It must works.
Evox 7.1 works a lot better then 6.5. I have a good improvement in performance and battery life.
If you want to root when you have configured the phone and it is ready to be used:
- install root explorer from google play store
- download and install magisk app downloading the apk from github and installing it by root explorer (i recommend to not allow the browser to install apks).
- on the pc, extract the boot.img from the evox zip.
- attach the phone to the pc and transfer the boot.img to the phone.
- run magisk and patch the boot.img
- transfer the patched image to the pc
- reboot the phone in fastboot
- flash the patched boot.img via fastboot
- reboot to system
Enjoy!
Alenett said:
- Install latest TWRP you can find in the other thread (using fastboot).
- Flash the lastest MIUI via adb sideload and perform a format data (backup your data before this).
- Reboot to system and let the MIUI to run.
- When the MIUI is ready (on the welcome page), reboot the phone in fastboot.
Then:
- Flash the TWRP again via fastboot (the MIUI restore the standard boot).
- Reboot in recovery mode (TWRP).
- Flash the new evox via adb sideload
- Format data
Reboot to system.
There is nothing else to do or explain. It must works.
Evox 7.1 works a lot better then 6.5. I have a good improvement in performance and battery life.
If you want to root when you have configured the phone and it is ready to be used:
- install root explorer from google play store
- download and install magisk app downloading the apk from github and installing it by root explorer (i recommend to not allow the browser to install apks).
- on the pc, extract the boot.img from the evox zip.
- attach the phone to the pc and transfer the boot.img to the phone.
- run magisk and patch the boot.img
- transfer the patched image to the pc
- reboot the phone in fastboot
- flash the patched boot.img via fastboot
- reboot to system
Enjoy!
Click to expand...
Click to collapse
Thanks i must have missed this for sure , im pretty basic at this custom rom stuff thanks a lot
Double tap to wake does not work after ~5 seconds after screen off (after the always on display dims down)
* Might be related to a broken screen replacement.
* I DID verify that the problem is a software problem - flashed xiaomi.eu rom and it DOES work there.
* I'm NOT at all sure it worked even with original screen (screen was fully functional, just a few cracks in the glass)
Update:
Tried derpfest and project elixir, same problem.
also found this on pixel-experience github issue tracker...
exactly the same issue - AOD becomes too dim and tap to wake stops working.
seems it's a known problem.