Related
Hello, to connect on my business account I turned ON encryptation.
To flash my ROM from ICS to JB, I perform a superwipe, and I install JB 4.1.2 revolution HD 17.1
To reconenct on my business account (google apps), I try to encrypt again my device (I know, I'm crazy ) but it's an endless process, I let my device more than 12 hours and process don't finish.
When I intall a new ROM, the free space in internal memory is less than 11Go (I have SGS3 16Go)
My questions :
1 - Is it normal to have less than 11Go after fresh rom installation ?
2 - My encrypted data are really wiped from my device or just hidden somewhere ?
3 - If my data arn't completely wiped, how can I full wipe my device ? (encrypted data include)
4 - Why I can't encrypt my device ?
11 gb is quite a lot...you'll need to use root explorer and look into every nook n corner of your sdcard
Sent from my iPad using Tapatalk HD
Hi guys,
That's a lot of text to read but when you guys advice me about that whole situation it can serve other people to plan and make their phone flashed without bricking it.
I need your opinion and advice on my move from Jelly Bean to KitKat. I have Lenovo P780 (China version) bought before 03.2014. My ROM is VIBEROM_V1.0_1347_3_ST_P780.
In general i'm happy with this rom, but after so long time of using it I would like to change it to more faster KitKat. And I would like to stick with VIBEUI because as i've said i'm happy with it. So I chose the newest: VIBEUI_V2.0_1512_7.149.1_ST_P780. I know it has only english and this other language but I don't use my native language even now when i have that option. Is it worth to flash it? Some people said about earlier version of kitkat it was buggy, and that JB is more stable than KK, but now after so much time of development it should be ready to smooth usage, right?
What I've done already:
I have istalled driver for preloader, lenovo usb drivers and adb drivers and then rooted with Kingoroot (of course on developer state and enabled usb debugging).
Then I made my copy of ROM through mtk droid tools, so I have istalled supersu but only for binaries (because mtk droid demanded them), then istalled busybox (from google play and hit install inside an app). And then I made copy of rom in mtk droid tools. But first hit „root” and then made backup, which was done without any error and is also prepared for SP Flash Tool. (I had trouble with backup because it ended with error but it was due to my default write disk in lenovo which was set on external storage, so mtk droid was writing image of ROM on built-in storage, which is, as you all know, very small, so i've changed default write disk and i was good to go).
I have done also backup of imei and nvram through mtk droid tools and backup of imei through mobile uncle tools.
THAT'S ALL I HAVE DONE. I didn't do anything besides this.
So first question: Is this enough? I mean root, drivers, backup of rom and imei.
Second question: What about „locked bootloader”? I've read a lot but in case of Lenovo P780 i've never read anything on locked bootloader besides one site but i can't insert url on my post because i'm new
So do I need to do sth with bootloader or it is unnecessary?
Next flashing: For downloading rom I used rather the most popular site with roms: needrom. I downloaded VIBEUI_V2.0_1512_7.149.1_ST_P780_OLK_W_3D22.zip. In this site is also scheme how to flash it. They say this stock rom should be flashed through CWM (I downloaded this recovery from their site):
Step 1: Download the custom ROM copied to an external SD card root directory
Step 2: the shutdown state. While holding down:
– Power button + volume button up, to enter the recovery mode.
– Wipe Data / Factory Reset -> delete all user data
– Wipe Cache Partition -> Wipe cache
– Advanced -> Wipe Dalvik Cache
Step 3: Return to recovery main interface Install zip from sdcard -> choose zip from sdcard -> Select your ROM
Step 4: Brush complete, restart the phone Patience required – first boot takes a while
Is this complete scheme? Because in xda i've found other way:
Install Vibe ROM, same as step 4 and then:
Step 5. Install Gapps
Step 6. Install SuperSU
Step 7. Wipe data/cache (Factory Reset) and reboot. Done
Sorry for carefullness but i don't want to brick my lenovo and it's better to ask with stupid questions than don't ask and flash. Also my brother had lenovo s650 but after conneting charger with electric socket it burned → then send on warranty to china --> then nothing... So... yeah i'm cautious.
I'm planning to flash cwm from needrom (same page as for stock rom) through mobile uncle tools (of course i will backup my contacts and other stuff). Or maybe it's better to create cwm recovery through mtk droid tools?
Then flash new vibe ui. Should I done this way or is it better other way? Like using stock revovery (but phone is rooted, i know i can remove root but i don't know if this rom is modded in any way so xda users didn't recommend to flash with stock recovery) or doing factory reset and then flashing with stock recovery ( i suppose doing factory reset can be done no matter if rooted, modded, etc., am i right? Then i should be available to make update through system settings?)? Asking because some guys said thay haven't managed to flash stock rom through cwm.
Now let's skip to Kitkat. Supposing i have done flashing properly through cwm i will have Kitkat vibe in stock version. So what then? I suppose i will need to:
1. root it (with kingoroot or iroot or sth like that because there are some problems with root on kitkat, right?)
2. get rid of ****ty china apps through root (suppose there will be around 10 apps to delete, so i will just run ie. kinguser and delete this system apps?)
3. install compatible recovery through mobile uncle tools (cwm or twrp, but in xda rather reign twrp) to flash gapps and maybe supersu if it's possible? Because i've read there are problems with framaroot on vibe but this regards only to framaroot or supersu too?
4. maybe restore imei, if it's lost
5. flash new modem (suppose this one i have now: V52?)
That's rather all, right?
Thanks in advance for your patience in reading and your opinions !
fictionch said:
Hi guys,
.............................................................................................
Now let's skip to Kitkat. Supposing i have done flashing properly through cwm i will have Kitkat vibe in stock version. So what then? I suppose i will need to:
1. root it (with kingoroot or iroot or sth like that because there are some problems with root on kitkat, right?)
2. get rid of ****ty china apps through root (suppose there will be around 10 apps to delete, so i will just run ie. kinguser and delete this system apps?)
3. install compatible recovery through mobile uncle tools (cwm or twrp, but in xda rather reign twrp) to flash gapps and maybe supersu if it's possible? Because i've read there are problems with framaroot on vibe but this regards only to framaroot or supersu too?
4. maybe restore imei, if it's lost
5. flash new modem (suppose this one i have now: V52?)
That's rather all, right?
Thanks in advance for your patience in reading and your opinions !
Click to expand...
Click to collapse
Hi. Alot of writing here! My eyes are like snail eyes now after all this reading!
1. KingoRoot will do fine! Framaroot is not working in KitKat.
2. Before eliminate china apps try to do a full backup of your firmware.
3. Install TWRP, you will find here some.
4. IMEI is lost only if you flash firmware with FlashTool! Not your case.
5. Flash modem... look for my post and you have there alot of KitKat modem software!
6. Yes in general this is all!
7. More tweaks are made, by every user. Depends on every user choices!
8. Good Luck.
I'm after upgrading to kitkat and.... all i can say is:
1. upgraded to kitkat VIBEUI_V2.0_1512_7.149.1_ST_P780_OLK_W_3D22 through cwm (carliv for p780 cn, you can found them on www|ambrand|net/Android) and a nightmare came...
2. i was able to install Kingoroot but i wasn't able to flash any gapps (i had in system apps google play services but only this and after manual install of google store it: "unfortunately stopped" every time) and superuser... and when rebooted into recovery throug mobileuncle tools my binaries for kingoroot where lost so every time I needed to root again...
3. kingoroot helped only with uninstalling user apps not system apps... titanium backup kept saying it works only with supersu...
4. tried flashing gapps with different cwm and twrp --> no success...
5. generally vibe ui is very beautiful, and works slightly better than vibe JB
6. after like 8 hours of trying to get my kitkat to usable state, I gave up...
7. through searching the internet i found VIBEUI_V2.0_1512_7.149.1_ST_P780mix_pansy_1_pl_ 28_03_15, so installed and now it seems to be good, it is mostly for polish users but there is also english inside and it has:
-root
-gaaps
-Xperia keyboard
-Titanium Backup
-Root Explorer
-Sony (Walkman)
-Lenowo launcher 6.8.289
-Lenovo dialer 3.8
-browser Dolphin
-Android browser
-SYNCit 1.1.14
-it has a lot of apps deleted, as you can see it has walkman from sony, so lenovo music app is gone, but performance of whole system is good, so if nothing wrong will happen i will stick with it
8. also it has kinguser (not from kingoroot) installed, but i think from zip named: Android_4.4_x_root, i haven't flashed this zip so now i slightly regreted because it might work then, but maybe some day i will do a backup and waste another day to challenge with stock rom especially with finding working gapps...
fictionch said:
I'm after upgrading to kitkat and.... all i can say is:
1. upgraded to kitkat VIBEUI_V2.0_1512_7.149.1_ST_P780_OLK_W_3D22 through cwm (carliv for p780 cn, you can found them on www|ambrand|net/Android) and a nightmare came...
2. i was able to install Kingoroot but i wasn't able to flash any gapps (i had in system apps google play services but only this and after manual install of google store it: "unfortunately stopped" every time) and superuser... and when rebooted into recovery throug mobileuncle tools my binaries for kingoroot where lost so every time I needed to root again...
3. kingoroot helped only with uninstalling user apps not system apps... titanium backup kept saying it works only with supersu...
4. tried flashing gapps with different cwm and twrp --> no success...
5. generally vibe ui is very beautiful, and works slightly better than vibe JB
6. after like 8 hours of trying to get my kitkat to usable state, I gave up...
7. through searching the internet i found VIBEUI_V2.0_1512_7.149.1_ST_P780mix_pansy_1_pl_ 28_03_15, so installed and now it seems to be good, it is mostly for polish users but there is also english inside and it has:
-root
-gaaps
-Xperia keyboard
-Titanium Backup
-Root Explorer
-Sony (Walkman)
-Lenowo launcher 6.8.289
-Lenovo dialer 3.8
-browser Dolphin
-Android browser
-SYNCit 1.1.14
-it has a lot of apps deleted, as you can see it has walkman from sony, so lenovo music app is gone, but performance of whole system is good, so if nothing wrong will happen i will stick with it
8. also it has kinguser (not from kingoroot) installed, but i think from zip named: Android_4.4_x_root, i haven't flashed this zip so now i slightly regreted because it might work then, but maybe some day i will do a backup and waste another day to challenge with stock rom especially with finding working gapps...
Click to expand...
Click to collapse
I understand what you deed! But here in development area, are alot of firmware! Clean firmware, rooted firmware, etc,
My posts are in Development section.
Hi guys,
just sharing my latest adventure with kitkat...
VIBEUI_V2.0_1512_7.149.1_ST_P780mix_pansy_1_pl_ 28_03_15 was not working on 100% because for example I wasn't able to receive incoming calls...
so flashed again*VIBEUI_V2.0_1512_7.149.1_ST_P780_OLK_W_3D22 <-- stock version, and managed to make it work 100%
so in cwm (used "recovery_cwm_kk_mod_P780":
1. Wipe data/ factory reset
2. Wipe cache
3. Wipe dalvik cache
4. install zip from sdcard "VIBEUI_V2.0_1512_7.149.1_ST_P780_OLK_W_3D22"
5. install zip from sdcard "Android_4.4_x_root" <-- that is 100% working root, not like kingoroot...
6. after installation of root phone rebooted automatically
7. back to cwm and install zip from sdcard "YourZgappsXS-4.4-2014.06.18" <-- that also 100% working gapps
8. deleting china apps if you haven't done after first reboot ;p
9. make backup !! ;p
Those mentioned zips you can download easily with the help of uncle Google
Thank you guys for advices, especially stympy
Hi All,
sharing the guide to install the multiple Rom's in our Axon 7 (as we don't have multi-boot in place).. as the development already kicked with Noughot.. and multiple roms are landing here...
this is for people who can't move out of Stock (due to Audio issues including me) and want to sneak peak the other LOS based roms.
Dual Boot Patcher is an app created by chenxiaolong for S4 initially and it broadly supports more than 150 devices now, whoever used in S4 would be familiar with it.. this app allows you to have multiple ROMs on a single device.
If you loved his work, go to his thread say Thank You
Axon 7 is official supported
I have tried with RR as Secondary and it's working.. so thought of sharing this.
For More details on this Dual Patcher official Thread:
https://forum.xda-developers.com/showthread.php?t=2447534
Working:
- patch ROM zip files
- patch GAPPS zip files
- patch SuperSu zip files
Instructions: More details
Keep the Stock Rom as always Primary.
Use the Data slot and create a name for the folder, as the System/Cache space will be small for LOS Rom
If you want to flash the LOS, RR roms remove the below script in the update-script (ROM\META-INF\com\google\android)
Code:
assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + "."););
assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.0/NRD90M/20170128.052618:user/release-keys");
Issues:
- Encryption and Boot UI are not supported
- trustzone verification in the Update-script will fail while flashing the TWRP, remove the above code before flashing the zip file.
- Pins, patterns or passwords are wrong in one of the ROMs . Then simply delete the file /data/system/locksettings.db (your saved fingerprints won't be lost) with TWRP.
Warning: for me setting the PIN in one rom works, if i enabled PIN in 2 roms it's not working, everytime you have to delete the locksettings.db and boot into other rom. Fingerprint works in 2 ROMS
- if In-app flashing doesn't work, you have to use TWRP to flash the patched zip files (use the latest TWRP)
- If flashing of a patched zip fails for any reason, you have to choose another install location ("Partition Configuration" in the app) when patching the same zip file again!Note: If flashing fails, first look up the error at /sdcard/MultiBoot.log and google it before reporting it...
Download
Download Dual Boot Patcher APP
Download Dual Boot Utilities
Credits to:
@chenxiaolong - for the great app and supporting till date.
@jimbo77 - for making Dual boot Axon 7 official support
@Glove007 - for additional details on workaround for Op3 - applies to Axon7
XDA Community
if i missed any plz let me know.
i can't find anyother thread related to this Dual Patacher, if it's available please merge the thread.
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Nik2424 said:
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Click to expand...
Click to collapse
No you won't lose any data when you flash this.. (But take a backup for safety)
Plz follow this steps.
Install the Dual patcher app and set the current Rom as primary
Make sure you patch the second Rom and Gapps (Super SU optional) in the Dual Patcher App before flashing in TWRP (or it will overwrite the Primary ROM)
in the patched rom remove the TrusstZone entries as mentioned in OP
then flash it via TWRP.
the Rom will be added to your Data or Cache based on the selection you made while patching the Zip file in the Dual Patcher (Preferable is data slot, and rom will be saved in Data>multiboot).
once logged in the Second rom, use the patcher to set the Rom as secondary.
when you want to switch rom, select the rom in the Dual Patcher app and reboot. (the app will move the correct boot.img to partion and selected rom will boot. )
if you want to Wipe Primary Rom or Second/Third Rom use the Dual Boot Utilities in the TWRP, this will wipe only the specified rom and you Second/third Rom won't get deleted. (if you wipe data/cache using TWRP menu, it will wiped your Second/third roms)
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Nik2424 said:
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Click to expand...
Click to collapse
those are added in the Rom to validate you're flashing in the right firmware.. like Noughot roms shouldn't be flashed in MM firmware.
Nothing wrong here in removing in those lines during flashing as secondary Roms..
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
I edit the update-script and remove the quoted lines
I install the dual boot patcher app
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs.
I boot to both ROMS and select stock as primary and LineageOS as secondary
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
Does this seem about right?
Thanks.
So glad this got brought to our phone
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
you should patch with Dual Patcher APK... -- Dual Boot utilities will be flashed in TWRP to install/wipe/update Primary Roms without impact to other Roms.
I edit the update-script and remove the quoted lines - yes
I install the dual boot patcher app - in primary Rom, yes
Open the App, give Root permission - it will prompt you for making the kernel as Primary, set it now - this is required so that App can switch between multiple Roms
1. basically the App will copy the boot.img of primary into storage>multiboot>primary
2. when you install the secondary rom and boot it up, install the app set the rom as secondary.
3. it will copy the secondary rom boot.img in to the same folder
4. whenever you switch rom, the app will copy the switched roms's boot.img to the Boot partiion so that corresponding rom will start on reboot
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
In-app flashing is failing for me, use TWRP to flash it.
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs. - yes
I boot to both ROMS and select stock as primary and LineageOS as secondary
Set the Primary when you installed the App in primary Rom itself.
and set the secondary when installed the app in secondary rom
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
I doubt App sharing is working correctly, please try and let me know
hope this helps
Does this seem about right?
Thanks.
Worked!
Great, this workd for me thanks!
thank you so much for this post
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Sebastian Fox said:
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Click to expand...
Click to collapse
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
`SBR` said:
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
Click to expand...
Click to collapse
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
mvortex3710 said:
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
Click to expand...
Click to collapse
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
`SBR` said:
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
Click to expand...
Click to collapse
Thanks very much for your fast reply.
When I checked the main thread it seems like this problem may be caused by not flashing a patched kernel as well, so I will try that presently and report back!
Edit: The patched kernel I'm using (AX7Kernel) is returning the error: "unable to find boot block location!", I've tried googling it but haven't found anything. Would you happen to know what might be causing this? Flashing in TWRP seems to have fixed this. Attempting boot now.
Edit 2: Boot didn't succeed, I was faced with 5 vibration then a restart to TWRP, where I used the Dual Boot utilities to change back to my Primary (stock) boot.
I'm going to try the other way round, with RR as primary and Stock as (secondary) data boot.
`SBR` said:
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
Click to expand...
Click to collapse
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Sebastian Fox said:
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Click to expand...
Click to collapse
thats not possible...
`SBR` said:
thats not possible...
Click to expand...
Click to collapse
Oh then it seems we reached a blocked road, is there anyway to convert the stock to f2fs??? Partitioning data???
I will try partitioning if possible but it's useless if the dualboot app/utility doesn't support it.
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Nik2424 said:
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Click to expand...
Click to collapse
for me i'm able to ptach RR and it's working in data slot..
did you try to install anything after patched RR and patched Gapps?
Hi there,
currently I am still using MIUI 8 Global (7.4.20) in Beta version with weakly updates on my RM Note 2 Prime and I am quite fine with it (above all the really impressive fast charging time).
But I also want to keep in touch with newer versions of Android as far as possible without giving up the overall usability of my phone and its components (Battery Live, Charging Time, GPS, Camera, Audio...).
So I try to keep myself informed about newer ROM versions for RM Note 2 which seems unfortunately not be supported by Xiaomi regarding newer Android Releases.
That lead my to RR and Lineage OS with RR seeming to be the better choice.
Now I am wondering what would be an efficient way to flash one of these ROMs with newer Android over my current MIUI ROM while keeping or restoring all my data, pictures, chats, navigation routes etc.?
Does Xiaomi PC suite also work with RR or Lineage OS?
All experiences, hints and tips are welcome!
Did someone else switch from MIUI to a newer Android ROM and what is your proposed procedure?
Thank you in advance!
Bye
Best way to get a custom ROM is to flash twrp!
When install with twrp you have to choose if you want to clear data, cache, dalvik, system, internal, external and otg, and so if you want to leave your data, the best option is to install Titanium backup (better with pro version) here you can safe all your apps (with all its data of course) and leave the backup in your internal.
Afterwards you can download any ROM you want (LP recommended!!) And better place it external if available.
Also to download gapps (Google apps) recommended
Than backup all your data with Titanium backup and you can boot after backup in twrp which is needed for custom ROMs!
Here you have to clear system (otherwise you will get error, because of cm based and miui based ROMs) and data+dalvik/cache.
Now you can choose with the install method your ROM and gapps and install.
Now you have to boot up system and after setup go into settings, build number 5times clicking, go to developer options and grant root access to all apps!
Now you have to install Titanium backup app again (pro recommended again) and choose the restore option
Now it will reinstall all apps with all its data and you can go on!
Hope I could help a bit
@Noobsi:
Thank you! Helps quite a lot. But what do you mean by "LP recommended"? Which ROM do you refer to here?
Regarding changing ROM (in my case this would be from MIUI to some kind of MM) I read that restoring Apps with their data is not recomended due to possible filesystem changes and things like that.
He means Lollipop (android 5) recommended, because marshmallow isn't stable enough.
IshtaNoob said:
He means Lollipop (android 5) recommended, because marshmallow isn't stable enough.
Click to expand...
Click to collapse
Thanks - this will leave me with MIUI further (since they [Xiaomi] will never bring it to newer Android versions it seems).
Try Dual Boot Patcher: https://forum.xda-developers.com/showthread.php?t=2447534
I use it to have MIUI 8 and Lineage OS 13, and when reboot, shows a menu to choose where want to boot.
Wow, did not even know such kind of things exists for Android mobiles too!
Thanks a lot! Are you happy with LOS13? Why did you choose it (instead of RR or something else)?
What are the diffs between MIUI8 and LOS13 you are experiencing? And which OS are you using more often?
And regarding Dual Boot Patcher: I also discovered other multi boot managers in Play Store for example, could I use them too or are all of them restricted/proposed to/for certain devices?
Hi there, I "ported" Cyanogenmod 12.1 rom from Lenovo Tab 2 a7-20 (from this link: https://drive.google.com/drive/folders/0Bxd-XcN0S63qWjJoTVlkRXlrams which I found on this russian website: http://4pda.ru/forum/index.php?showtopic=711492&st=1100#entry63268934) to our Lenovo Tab 3 710f with Cygwin and kitchen, succesfully installed it on the device with no flashing errors through Tzul's TWRP (see: https://androidfilehost.com/?fid=673368273298949373) and then flashed the patch for the rom which I previously ported as well, then proceeded to install Gapps 5.1 pico, succesfully too.
Now the problem begins..., whenever I try to boot into the rom, it loads a little while on Lenovo splash screen just to go back to TWRP recovery menu, and it always does that. I referred to Android's Kitchen FAQ (see: https://forum.xda-developers.com/showthread.php?t=633246) but I have no good knowledge nor adequate time to setup Android SDK and debug the issue with logcat, or in any other way that I know of, so I ask for somebody to help me sort out this problem and hopefully fix it so the rom may be bootable and usable, then the community may have the FIRST EVER ACTUAL CUSTOM ROM for this device, furthermore, making it stable. YOU WILL GET ALL THE CREDIT. (well, 99.9 of it)
Here are the PORTED files.
https://drive.google.com/drive/folders/14MJTWPRnp0xeFa0O2TKNID5SGj7JW688
HI.
Im also a 710F owner. Did you get anywhere with this. Did you get your rom to boot. I'm greatly in need of a custom rom for the 710f.
Kind Regards
Any update on this? What exactly happens in the TWRP?
Custom ROM at last
UpdatedHello there, I successfully found the work of a developer who tried to do what I did, but with success, just flash the latest july rom after formatting system, dalvik, data, (not internal storage) etc..., After it installs I advice you to immediately install gapps nano, and then reboot.
Here:
https://drive.google.com/drive/u/0/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJ
Greetings,
David.
Updated link:
https://drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
ChinmayDalal said:
The link returns 404, can you please reupload the file?
Click to expand...
Click to collapse
Here:
https://drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
Just follow my instructions and install the July 2 rom.
Hey man, thanks for finding this. However, when I try and flash the ROM I get Error: 7 although I have the 710F version.
Error 7 means wrong ROM.
David uploaded 2 roms, for the Tab2A710F and the TB3-710F.
I flashed the TB3-710F and it works.
Works very nicely.
MicroG works too, no need for Google Apps.
...
Sorry. There are Two Little Bugs. YouTube only has up to 360p. When the screen is locked, it rotates.
DavidRGX said:
Here:
https://drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
Just follow my instructions and install the July 2 rom.
Click to expand...
Click to collapse
Thankyou for finding this rom
Getting Error 7 with both the firmwares.
Edited the updater-script and then got "incompatible data, can't flash" in TWRP.
Edit: Managed to flash the ROM by formatting the cache to ext4, but now I'm facing the storage bug, it's showing 5GB instead of 8GB.
DavidRGX said:
UpdatedHello there, I successfully found the work of a developer who tried to do what I did, but with success, just flash the latest july rom after formatting system, dalvik, data, (not internal storage) etc..., After it installs I advice you to immediately install gapps nano, and then reboot.
Here:
https://drive.google.com/drive/u/0/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJ
Greetings,
David.
Updated link:
https://drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
Click to expand...
Click to collapse
Finally after a long time ... We atleast have a working rom .. i totally appreciate it .. the rom is good but the only problem is system is taking 500+ ram ... Is there any way to make this rom lite ?
how to activate hd in cyanogen 12.1 tb3-710f
Patche v1.0
DavidRGX said:
UpdatedHello there, I successfully found the work of a developer who tried to do what I did, but with success, just flash the latest july rom after formatting system, dalvik, data, (not internal storage) etc..., After it installs I advice you to immediately install gapps nano, and then reboot.
Here:
drive.google.com/drive/u/0/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJ
Greetings,
David.
Updated link:
drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
Click to expand...
Click to collapse
Hello!. Here is my contribution for this Rom.
Optimization Patch:
Programmers: For those who want to continue helping.
-It includes.
.Build.prop.
. Bootanimation. (Unmodified)
.Apps:
Es-Explorer Pro
Kernel Adiutor.
BuildProp Editor.
Root Booster.
RAR.
Terminal.
User: For Normal Users.
-It includes.
.Build.prop.
.Apps:
CPU-Z.
Root Booster.
Fix Lollipop Memory Leak. (Xposed)
-Install TWRP to flash.
-Clean Cache and Dalvik / ART Cache.
Any contribution is written to me by INBOX, or by DavidRGX.
Downloads:
drive.google.com/open?id=19V9mr9xMh1JUI4URxRYTYwtXxSyEFP7G
PDT: I speak Spanish.
Hola, necesitaria que pusieras un tutorial de como instalar paso a paso Cyanogenmod 12.1 en mi tabletlenovo tab 3 710f, ya que no encuentro la manera de hacerlo.
Gracias!!!
Hey thanks for it. I just wanna know how can I remove some apps before flashing it like File Manager, Email, Browser??
One bug I am encountering related to MAC address of the device, The MAC is changing on every on/off of WIFI radio?? How to fix it as my router can only connect limited number of devices??
...
Thank you!
Thanx a lot man!
You really saved my day, that others did mess up!
I rooted my device + wanted use custom roms.
It was an another website that had information and it was to "Tab 3 710F, but that fxxxxxg website only had roms to "tab3 710I".
I really messed up my pad.
Anyway I have some questions, the partition in my pad is only 5GB, do you know why?
Is the original Stock rom spooking around in some partition of 3GB?....as the internal memory in the pad is 8GB total...
Since this Cyanogen is based on Android 5 it dont support Adoptect storage on the fly.
I wanted originally to install Android 6 to this pad, Lenovo dont want to give it to me and thats the main reason why I rooted.
Is it possible to move whole applications to SD card and run from there?
Since the internal memory is so bad in this pad I really would like to use this feature!!!
Anyway I like this rom since unnesserary bloatware are gone and its good there is no playstore or gmail, since this pad is to one of my children and they dont really need these
DavidRGX said:
UpdatedHello there, I successfully found the work of a developer who tried to do what I did, but with success, just flash the latest july rom after formatting system, dalvik, data, (not internal storage) etc..., After it installs I advice you to immediately install gapps nano, and then reboot.
Here:
Greetings,
David.
Updated link:
Click to expand...
Click to collapse
freaking awesome man! Three bugs
1 - YouTube is only at 360p
2 - Camera is just at 1.5 (or something like that pixels)
3 - Doesn't recognize the device when I plug on the PC
Just to thank all of you for saving my kids tablet back to life!!!
It's sad that youtube is limited at 360p, but they will live with that.
Thanks!
You only hear the sound on live YouTube programs.
Is there any solution?