[Q] AOSP Based Kitkat ROM for Lenovo ROW P780 8GB? [SOLVED] - Lenovo P780

Hi,
How to install a KitKat Based Light Weight ROM such as AOSP v 1.8 on the ROW Model of Lenovo P780 8GB RAM which is currently rooted, running SLXROM v25e with TWRP Recovery?
There are a bunch of ROMs which are now being developed only for the KIT (CN) Version (for example AOSP 1.8) and the information about converting an 8GB RAM ROW Version to KIT (CN) Version is scattered and it is not clear whether it is possible?
In addition, there seems to be a ROM based on Android L and that's also developed for the KIT (CN) base. - has anyone given it a try?
Most of the development is happening on Russian Forums and the procedure to adopted is not entirely clear even when translated to English
So, here are a few queries which I'm looking to clarify and consolidate through this Q&A thread:
1. Are there any AOSP based KITKAT (4.4) ROMs available for Lenovo P780 ROW 8GB Model?
2. If not, then to install these ROMs, we need to first convert the device from ROW to CN. I'm guessing that the conversion can only be done flashing the ROM using SP Tools. Is that correct?
3. I'm also guessing that a Chinese Stock ROM cannot be flashed on the 8GB RAM ROW device because the Chinese Stock ROMs were developed for 4GB RAM and doing this could cause bootloops and other issues in partitioning. Correct?
4. What is the best way to convert a ROW Version to KIT (CN) Version especially for P780 8GB RAM device, with root and TWRP Recovery?
Although the community for 8GB RAM P780 users may not be as large as the 4GB RAM Model, it's very much in existence and the number of users adopting the 8GB RAM device is expected to be higher recently.
Regards
GxxA

In FAQ section of custom roms based on KitKat 4.4.2 says that if you have 4gb, you need first to install XVibe v3, than throw TWRP install custom rom...About 8gbROW version says:
"Поставить любую официальную китайскую прошивку через флеш тул(Рекомендуется для аппаратов 8GB)- придется подкидывать рекавери из XVIBE0.3 перед прошивкой."
If I understand this right, you need to flash stock chinese rom for 8gb with changed stock recovery with recovery from XVibe rom (twrp), than flash custom rom (AOSP; Android L...)
You can always ask on Lenovo Russia forum using google translate and original english question, they will anwser...
P.S. I have 4GB ROW, so I'm not 100% sure about any of your question...

Dear All -
OK... Here's my first attempt.
1. Installed USB Drivers, SP Flash Tool Driver, Used the SP Flash Tool to Write P780_S308_130814 (Chinese Stock ROM) with "Firmware -> Upgrade" option -- Success
Am assuming now my phone is successfully converted from ROW to CN (KIT). I checked available storage, it reflected 8GB, so it's good.
2. Did Framaroot with SuperSU, Installed MobileTools, Updated Recovery to TWRP 2440 (p780-twrp-en-asia-recovery.img) -- Success
This was done to install the X-VIBE ROM.
3. Installed X-VIBE ROM (clean_x-vibe) as suggested by using the TWRP Restore feature -- Success
Was able to successfully boot into X-VIBE ROM as well.
4. After installing the X-VIBE ROM, went back into Recovery, Flashed with AOSP 4.4.2 v.1.8.zip, Applied Wipe Dalvik/Cache and Rebooted.
!! At this point, the device went into Bootoop at Start Screen !!
Just Reset the Phone and Reflashed a Stock ROM with SP Flash Tool once again and everything is back to normal as it was...
But still want to figure out why did the Bootloop occur and how to get pass through to install AOSP 4.4.2 v 1.8 on my 8GB P780 Device. Any suggestions?

Well, had a breakthrough today and was successful in Flashing the AOSP 4.4.2 ROM on Lenovo P780 8GB RAM ROW Version.
1. Installed USB Drivers, SP Flash Tool Driver, Used the SP Flash Tool to Write P780_S308_130814 (Chinese Stock ROM) with "Firmware -> Upgrade" option -- Success
2. Did Framaroot with SuperSU, Installed MobileTools, Updated Recovery to TWRP 2440 (p780-twrp-en-asia-recovery.img) -- Success
3. Installed X-VIBE ROM (clean_x-vibe) as suggested by using the TWRP "Restore" feature (Do Not USE Install!) -- Success
Here comes the tricky part, earlier, I tried flashing AOSP 4.4.2 ROM directly over the X-VIBE ROM without cleaning it up. That's where the problem was. Instead,
4. Logon to TWRP Recovery, Choose Wipe and Execute ALL Wipe Commands (Dalvik, Cache, Factory Reset, Internal, Secure, etc.). -- Success
(Note: Do Not Wipe the External Memory as it's your SD Card.)
5. Now, Go Back and Flash the AOSP 4.4.2 ROM, Apply Wipe Dalvik/Cache and Reboot -- Success
Your Lenovo P780 system should now be running 4.4.2. I used AOSP 1.7 Version as it seemed much more stable compared to AOSP 1.8 (AOSP 1.8 has some bugs - Front Camera causes exception, issues with Google Apps in Communicating with Google Servers, etc.). AOSP ROM is light weight and has a buttery User Experience compared to the Sticky UI in Stock Kitkat ROMs.
Few Suggestions:
Replace the Modem that comes with AOSP 1.8 with the Stock Modem of your choice. I installed the Modem that came with S220 ROW (modem_P780_V104_S220). This worked better for me!
I intuitively turned OFF "Wi-Fi optimization" as I felt it causes battery to drain faster for some reason! I've been using this ROM for over 10 hours with Wifi turned ON and the battery has hardly reduced by 5 - 6%.
Another suggestion that I adopted was to install Xposed Installer and install Gravity Box for KK - this provides a lot more customization to help your productivity.
If you ever felt you wanted to revert to the ROW version, just flash the Stock ROW Version ROM (P780_8G_ROW_S124_140403) through SP Flash Tool.
Regards
GxxA.

GxxA said:
Well, had a breakthrough today and was successful in Flashing the AOSP 4.4.2 ROM on Lenovo P780 8GB RAM ROW Version.
1. Installed USB Drivers, SP Flash Tool Driver, Used the SP Flash Tool to Write P780_S308_130814 (Chinese Stock ROM) with "Firmware -> Upgrade" option -- Success
2. Did Framaroot with SuperSU, Installed MobileTools, Updated Recovery to TWRP 2440 (p780-twrp-en-asia-recovery.img) -- Success
3. Installed X-VIBE ROM (clean_x-vibe) as suggested by using the TWRP "Restore" feature (Do Not USE Install!) -- Success
Here comes the tricky part, earlier, I tried flashing AOSP 4.4.2 ROM directly over the X-VIBE ROM without cleaning it up. That's where the problem was. Instead,
4. Logon to TWRP Recovery, Choose Wipe and Execute ALL Wipe Commands (Dalvik, Cache, Factory Reset, Internal, Secure, etc.). -- Success
(Note: Do Not Wipe the External Memory as it's your SD Card.)
5. Now, Go Back and Flash the AOSP 4.4.2 ROM, Apply Wipe Dalvik/Cache and Reboot -- Success
Your Lenovo P780 system should now be running 4.4.2. I used AOSP 1.7 Version as it seemed much more stable compared to AOSP 1.8 (AOSP 1.8 has some bugs - Front Camera causes exception, issues with Google Apps in Communicating with Google Servers, etc.). AOSP ROM is light weight and has a buttery User Experience compared to the Sticky UI in Stock Kitkat ROMs.
Few Suggestions:
Replace the Modem that comes with AOSP 1.8 with the Stock Modem of your choice. I installed the Modem that came with S220 ROW (modem_P780_V104_S220). This worked better for me!
I intuitively turned OFF "Wi-Fi optimization" as I felt it causes battery to drain faster for some reason! I've been using this ROM for over 10 hours with Wifi turned ON and the battery has hardly reduced by 5 - 6%.
Another suggestion that I adopted was to install Xposed Installer and install Gravity Box for KK - this provides a lot more customization to help your productivity.
If you ever felt you wanted to revert to the ROW version, just flash the Stock ROW Version ROM (P780_8G_ROW_S124_140403) through SP Flash Tool.
Regards
GxxA.
Click to expand...
Click to collapse
Hi can you please share a link to download AOSP 1.7 please. I am not able to locate this older version.

GxxA said:
Well, had a breakthrough today and was successful in Flashing the AOSP 4.4.2 ROM on Lenovo P780 8GB RAM ROW Version.
1. Installed USB Drivers, SP Flash Tool Driver, Used the SP Flash Tool to Write P780_S308_130814 (Chinese Stock ROM) with "Firmware -> Upgrade" option -- Success
2. Did Framaroot with SuperSU, Installed MobileTools, Updated Recovery to TWRP 2440 (p780-twrp-en-asia-recovery.img) -- Success
3. Installed X-VIBE ROM (clean_x-vibe) as suggested by using the TWRP "Restore" feature (Do Not USE Install!) -- Success
Here comes the tricky part, earlier, I tried flashing AOSP 4.4.2 ROM directly over the X-VIBE ROM without cleaning it up. That's where the problem was. Instead,
4. Logon to TWRP Recovery, Choose Wipe and Execute ALL Wipe Commands (Dalvik, Cache, Factory Reset, Internal, Secure, etc.). -- Success
(Note: Do Not Wipe the External Memory as it's your SD Card.)
5. Now, Go Back and Flash the AOSP 4.4.2 ROM, Apply Wipe Dalvik/Cache and Reboot -- Success
Your Lenovo P780 system should now be running 4.4.2. I used AOSP 1.7 Version as it seemed much more stable compared to AOSP 1.8 (AOSP 1.8 has some bugs - Front Camera causes exception, issues with Google Apps in Communicating with Google Servers, etc.). AOSP ROM is light weight and has a buttery User Experience compared to the Sticky UI in Stock Kitkat ROMs.
Few Suggestions:
Replace the Modem that comes with AOSP 1.8 with the Stock Modem of your choice. I installed the Modem that came with S220 ROW (modem_P780_V104_S220). This worked better for me!
I intuitively turned OFF "Wi-Fi optimization" as I felt it causes battery to drain faster for some reason! I've been using this ROM for over 10 hours with Wifi turned ON and the battery has hardly reduced by 5 - 6%.
Another suggestion that I adopted was to install Xposed Installer and install Gravity Box for KK - this provides a lot more customization to help your productivity.
If you ever felt you wanted to revert to the ROW version, just flash the Stock ROW Version ROM (P780_8G_ROW_S124_140403) through SP Flash Tool.
Regards
GxxA.
Click to expand...
Click to collapse
AOSP 1.7 is row or kit?

unable to flash alice rom cn on my 8gb rom
please help me....

Related

[Q] MIUI V5 4.8.27: Stuck at boot

I recently flashed my Lenovo P780 which was running 4.4.2 to MIUI V5 4.8.27 ROM using the guideline mentioned in this thread http://forum.xda-developers.com/len...iui-v5-4-6-2-jb-4-2-lenovo-p780-dual-t2795361
I also used the recovery image mentioned this thread http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605 using mobileuncle.
I followed every step mentioned in the thread and flashed the rom. Now my device is booting but is stuck at boot. All I can see is MI.com logo. It is stuck like this for more than 30 mins.
I am unable to go back to recovery mode also. I don't know what to do. Please someone help!!
Ok. I solved the issue. Since I flashed the ROM when my Lenovo was running stock kitkat 4.4.2, the MIUI was stuck in bootloop.
What I did was I reflashed my P780 with LIFE ROM V7 using Flashtool. Then I flashed MIUI using TWRP. Now it works fine.
eashwar83 said:
Ok. I solved the issue. Since I flashed the ROM when my Lenovo was running stock kitkat 4.4.2, the MIUI was stuck in bootloop.
What I did was I reflashed my P780 with LIFE ROM V7 using Flashtool. Then I flashed MIUI using TWRP. Now it works fine.
Click to expand...
Click to collapse
Yes, I also did the same thing. Life ROM is Savior with TWRP recovery built in. Whenever, I had a wrong flash and my mobile is dead, I returned to this by flashing with SP Tools, boot straight into TWRP and then restored my previous working ROM or tried flashing another ROM.
Welcome to MIUI world. I am sure you will enjoy this ROM. Go for OTA update to 4.8.30 which worked like breeze for me. Try the Android V5 Dark theme. You will love it.
ganapathyraman_s said:
Yes, I also did the same thing. Life ROM is Savior with TWRP recovery built in. Whenever, I had a wrong flash and my mobile is dead, I returned to this by flashing with SP Tools, boot straight into TWRP and then restored my previous working ROM or tried flashing another ROM.
Welcome to MIUI world. I am sure you will enjoy this ROM. Go for OTA update to 4.8.30 which worked like breeze for me. Try the Android V5 Dark theme. You will love it.
Click to expand...
Click to collapse
Oh! I was going to ask whether OTA update to 4.8.30 was safe. Thanks for letting me know.
My lenovo softbricked after I tried to OTA update MIUI 4.8.27. Then, as you guys said, I installed Life Rom V7 and when I tried installing either MIUI 4.6 and 4.8.27 through TWRP, Roms got installed without any boot issue but I couldn't open any of the apps, even system apps like Dialer and File Explorer. Any suggestions? I would really love to go back to MIUI. May be there is a way to repack it and install through Flashtool?
Sent from my Lenovo P780 using XDA Free mobile app
eashwar83 said:
I recently flashed my Lenovo P780 which was running 4.4.2 to MIUI V5 4.8.27 ROM using the guideline mentioned in this thread http://forum.xda-developers.com/len...iui-v5-4-6-2-jb-4-2-lenovo-p780-dual-t2795361
I also used the recovery image mentioned this thread http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605 using mobileuncle.
I followed every step mentioned in the thread and flashed the rom. Now my device is booting but is stuck at boot. All I can see is MI.com logo. It is stuck like this for more than 30 mins.
I am unable to go back to recovery mode also. I don't know what to do. Please someone help!!
Click to expand...
Click to collapse
I am still stuck with this problem. flashed using TWRP on 4.2 JB version for P780. Not sure what the problem is ?
maverickvarun said:
I am still stuck with this problem. flashed using TWRP on 4.2 JB version for P780. Not sure what the problem is ?
Click to expand...
Click to collapse
Soooo... MIUI is for Jelly Bean not for KITKAT.
DO NOT FLASH OVER KITKAT.
IF YOU FLASH OVER KITKAT YOU WILL HAVE ALOT OF PROBLEMS LIKE: YOUR SD CARD WILL NOT WORK(THIS IS THE SMALLEST PROBLEM), BOOTLOOP,BOOTLOADER CORUPTED, ETC ETC.
SO BE WARNED...
If you want to test MIUI do this:
1. Flash stock s124 ROM;
2. Download Framaroot and root your phone;
3. Install Mobileuncle Tools;
4. Get TWRP 2.6.3.0 no other;
5. Flash TWRP with Mobileuncle Tools;
6. Download MIUI and put it in your phone SD Card;
7. Install from market Reboot Manager, give root right and reboot to recovery;
8. From SD Card flash MIUI wipe cache dalvik etc etc;
9. reboot and voila MIUI.
10 Good Luck.

Galaxy S6 Edge: No Deep Sleep with Android 5.1.1 and diff. kernels and ROMs (COI9)

Hi all,
I own a brand new Galaxy S6 Edge, SM-G925F, bought just 3 days ago in European Union/
Germany.
It has installed the latest Samsung Stock:
Android version: 5.1.1
Base band version: G925FXXU3COI9
Build number: LMY47X.G925FXXU3COI9
Security Software: MDF v2.0 Release 3 und VPN v1.4 Release 5.2
Latest Stock: G925FXXU3COI9_G925FDBT3COI6_DBT.zip
After updating OTA to the latest stock I tried to root the phone.
First of all I have flashed TWRP 2.8.7.1 via Odin 3.10.6. Then I have installed
Hacker Kernel V5 and XPosed v75.8 by WANAM (20151030) (using TWRP).
After finishing configuring the phone I have seen the next day that my akku has
been eaten and found out that the phone *never* enters deep sleep mode.
As soon as I go back to Stock ROM, Stock Kernel, Stock Recovery
(G925FXXU3COI9_G925FDBT3COI6_DBT.zip), deep sleep mode is working instantly
(controlled with CPU Spy).
What I have done without success to solve the problem:
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. trying the solutions from zidroid (fix-battery-drain-and-deep-sleep-issue-on-galaxy-s6-and-s6-edge)
Method 1 (zip file flasing and Method 2 (terminal).
Both in several combinations with different kernels, alternative ROM, stock ROM,
root only (flashing kernel using Odin without TWRP)
3. trying differenz kernels:
- Hacker Kernel v4, v5
- UniKernel v8
- AELMultiVariant_v2_9_311015
4. trying the kernels without custom recovery, i.e. first flashing stock ROM, then
flashing the kernels directly using Odin.
5. trying the next solution that I have found in the forum:
first stock firmware again, then TWRP, then kernel (for root). Afterwards extracting stock
recovery image from G925FXXU3COI9_G925FDBT3COI6_DBT.zip, flashing this one only.
Running stock recovery, erasing cache, reboot (repeated several times).
Again no deep sleep.
6. first stock firmware again, then flashing TWRP and CarHDRom_V.14_3COJH.
All these tries without XPosed framework, starting from a fresh installed stock system
(i.e. resetting the whole phone to default, then erasing/formatting everything (without
EFS) from TWRP, then flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
Even tried everything without a SIM card.
As soon as I flash something (kernel only, TWRP only, combinations or complete ROM) the
phone never enters deep sleep mode. In "best" case it is working with 200 Mhz only.
Can this be a problem with Samsung's latest boot loader?
Thanks for your assistance!
Problem solved, reason unknown
In the end I have found a working solution.
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
3. flashing TWRP
4. flashing hacker kernel (enabling root)
5. flashing XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S.zip
Deep Sleep is working now, even in combination with XPosed framework and XPrivacy.
As XtreStoLite_ROM_v2.4_Deo-Mod-Edition is based on XXU3COI9 , I assume there could
be a problem with the lasted boot loader from the stock firmware XXU3COI9 that I had installed
previously.
yoda947 said:
In the end I have found a working solution.
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
3. flashing TWRP
4. flashing hacker kernel (enabling root)
5. flashing XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S.zip
Deep Sleep is working now, even in combination with XPosed framework and XPrivacy.
As XtreStoLite_ROM_v2.4_Deo-Mod-Edition is based on XXU3COI9 , I assume there could
be a problem with the lasted boot loader from the stock firmware XXU3COI9 that I had installed
previously.
Click to expand...
Click to collapse
fixed!

how to update unlocked MT2-L03 to latest lollipop B322

my mate 2 is still in the original Android version 4.3. I never updated it. Now I am thinking to update the phone to latest Lollipop B322, May I know how I can do it? Will this update reset my phone to the factory mode? How can I still recover my phone to the current state after updated to new Lollipop? Sorry for my naive questions. Thanks in advance for your help!
If your on 148, I think you need to hit an intermediate update first. It will reset your phone to stock, but you can install TWRP backups. Not sure if you can restore old system images. I know the partition sizes get larger on android 5 builds
Sent from my Ascend Mate 2 using Tapatalk
Do clean installs only. So backup everything first. A backup of all apps can be useful as it was for me but some apps from jelly bean didn't work on lollipop and I had to find and alternative. Some apps just had errors and I just had to re downoad them from the play store. So backup first. Also the custom recovery you have on 4.3 will need to be updated for newer ROM on this phone. Use your old twrp first to back up your stock 4.3 first.
Then go like this:
Build 148 ->
Build 309 (lollipop)
Factory reset (repartitions internal storage) ->
Build 322 (gives you new bootloader) ->
Factory reset (so all is ready) ->
All set to install custom ROM. Update your custom recovery to the one the ROM you want requires.
Remember to do clean installs and wipe cache and davlik. If you use xposed flash the ROM, Gapps and xposed then so you don't have to wait on Android to rebuild the davlik cache later when you've restored your 100+ apps (takes a while).
@superbass311 made a bunch of YouTube videos to get you updated. They're in the how to guide thread
http://forum.xda-developers.com/showpost.php?p=61682557&postcount=7
how can I root official b322 ?
thanks
notoriouspk said:
how can I root official b322 ?
thanks
Click to expand...
Click to collapse
If I remember right you can install a custom recovery TWRP and then boot into TWRP and it will ask if you want to root. There are other options to root the phone as well. I just flashed from B322 -> custom rom which was already rooted. If you're staying on stock b322 though I think TWRP will do it for you.
arcadesdude said:
Do clean installs only. So backup everything first. A backup of all apps can be useful as it was for me but some apps from jelly bean didn't work on lollipop and I had to find and alternative. Some apps just had errors and I just had to re downoad them from the play store. So backup first. Also the custom recovery you have on 4.3 will need to be updated for newer ROM on this phone. Use your old twrp first to back up your stock 4.3 first.
Then go like this:
Build 148 ->
Build 309 (lollipop)
Factory reset (repartitions internal storage) ->
Build 322 (gives you new bootloader) ->
Factory reset (so all is ready) ->
All set to install custom ROM. Update your custom recovery to the one the ROM you want requires.
Remember to do clean installs and wipe cache and davlik. If you use xposed flash the ROM, Gapps and xposed then so you don't have to wait on Android to rebuild the davlik cache later when you've restored your 100+ apps (takes a while).
@superbass311 made a bunch of YouTube videos to get you updated. They're in the how to guide thread
http://forum.xda-developers.com/showpost.php?p=61682557&postcount=7
Click to expand...
Click to collapse
arcadesdude said:
If I remember right you can install a custom recovery TWRP and then boot into TWRP and it will ask if you want to root. There are other options to root the phone as well. I just flashed from B322 -> custom rom which was already rooted. If you're staying on stock b322 though I think TWRP will do it for you.
Click to expand...
Click to collapse
thanks for ur response Twrp asked if I want to root it ..it booted fine but no SU ...checked root it wasn't there ....at the moment I am running cm 13.0 rooted which works fine ...can u give me a link for stock rooted B322 ? thanks
btw which is better cm 13 or B322 rooted ?
notoriouspk said:
thanks for ur response Twrp asked if I want to root it ..it booted fine but no SU ...checked root it wasn't there ....at the moment I am running cm 13.0 rooted which works fine ...can u give me a link for stock rooted B322 ? thanks
btw which is better cm 13 or B322 rooted ?
Click to expand...
Click to collapse
If TWRP root didn't work you can flash SuperSU.zip file using TWRP.
http://forum.xda-developers.com/ascend-mate2/help/how-one-root-upgraded-to-5-1-t3148167
http://androiding.how/how-to-flash-supersu-using-twrp-recovery-and-root-any-android-device/
A limitation of B322 over a custom rom like CM is that Xposed doesn't work on B322. So if you want lots of features and customization go with a custom rom like CM13 (which I will eventually be upgrading to it is just a lot of work to migrate 200+ apps & settings lol). A positive of B322 is EMUI (Huawei's stock rom aka B322) is extra battery life. I hear that CM13 is just as good in that regard but I haven't tried it yet. So I'd say a custom rom would be better than stock B322 (even if it is rooted) just because of the ability to use Xposed.
Thank you so much for your reply! I am still having two questions:
1. Before upgrade, i should backup data. Can I just use the backup function in handset which i found from Settings/About phone/System Update/Local Update/? I don't know about TWRP.
2. to upgrade from B148 to B322, can I just follow this instruction: http://consumer.huawei.com/us/support/manuals/detail/index.htm?id=52025&key4=mate 2
4.1 Force upgrade
---Step 1. A MICRO SD card of 4G or more should be available. The MICRO SD card
made by Sandisk, Kingstone, or Kingmax is recommended.
---Step 2. Format the MICRO SD card (This operation is optional).
If your phone’s system is B3XX, you should skip Step 3 and Step 4.
---Step 3. Copy the Software: recovery package file UPDATE.APP and main package file
UPDATE_VENDOR.APP to a directory named dload.
---Step 4. Copy the entire dload folder (with UPDATE.APP and
UPDATE_VENDOR.APP in it) to the root directory of the MICRO SD card.
If your phone’s system is B126 or B148, you should skip Step 5.
---Step 5. Copy the upgrade package UPDATE_VENDOR.APP to a directory named
dload and copy the dload folder to the root directory of the MICRO SD card.
---Step 6. Make sure your handset is power off. Insert the MICRO SD card into the
handset. Press the VOLUME UP and VOLUME DOWN keys and POWER key to
power on the phone(picture4.1.1) , when the HUAWEI logo is showed , release
the POWER key and keep pressing the VOLUME UP and VOLUME DOWN
keys(picture 4.1.2) until your phone is entered the Software Upgrade
Software Upgrade Guideline
2015-9-3 Page 5, Total8
Mode(picture 4.1.3).
4.1.1 4.1.2
4.1.3
---Step 7. When the progress bar stops, your handset will reboot and enter the new
system.
Thanks!!
arcadesdude said:
Do clean installs only. So backup everything first. A backup of all apps can be useful as it was for me but some apps from jelly bean didn't work on lollipop and I had to find and alternative. Some apps just had errors and I just had to re downoad them from the play store. So backup first. Also the custom recovery you have on 4.3 will need to be updated for newer ROM on this phone. Use your old twrp first to back up your stock 4.3 first.
Then go like this:
Build 148 ->
Build 309 (lollipop)
Factory reset (repartitions internal storage) ->
Build 322 (gives you new bootloader) ->
Factory reset (so all is ready) ->
All set to install custom ROM. Update your custom recovery to the one the ROM you want requires.
Remember to do clean installs and wipe cache and davlik. If you use xposed flash the ROM, Gapps and xposed then so you don't have to wait on Android to rebuild the davlik cache later when you've restored your 100+ apps (takes a while).
@superbass311 made a bunch of YouTube videos to get you updated. They're in the how to guide thread
http://forum.xda-developers.com/showpost.php?p=61682557&postcount=7
Click to expand...
Click to collapse
Best to have a full system backup using TWRP. Also having a full backup from Titanium Backup will allow you to restore apps which can be faster than installing them over. If you don't have too many apps it isn't a big deal. It does let you save app settings.
Also use an app to back up phone log and sms if you want that history.
I don't know about the built in backup. Haven't used it.
piapiaworld said:
Thank you so much for your reply! I am still having two questions:
1. Before upgrade, i should backup data. Can I just use the backup function in handset which i found from Settings/About phone/System Update/Local Update/? I don't know about TWRP.
2. to upgrade from B148 to B322, can I just follow this instruction: http://consumer.huawei.com/us/support/manuals/detail/index.htm?id=52025&key4=mate 2
...
Click to expand...
Click to collapse
You can do that. I think that will work. You might have to flash it twice if there are issues after the first time. Then once it is B322 do a factory reset/restore just in case as well. All data is lost in the process of upgrading.
arcadesdude said:
If TWRP root didn't work you can flash SuperSU.zip file using TWRP.
http://forum.xda-developers.com/ascend-mate2/help/how-one-root-upgraded-to-5-1-t3148167
http://androiding.how/how-to-flash-supersu-using-twrp-recovery-and-root-any-android-device/
A limitation of B322 over a custom rom like CM is that Xposed doesn't work on B322. So if you want lots of features and customization go with a custom rom like CM13 (which I will eventually be upgrading to it is just a lot of work to migrate 200+ apps & settings lol). A positive of B322 is EMUI (Huawei's stock rom aka B322) is extra battery life. I hear that CM13 is just as good in that regard but I haven't tried it yet. So I'd say a custom rom would be better than stock B322 (even if it is rooted) just because of the ability to use Xposed.
Click to expand...
Click to collapse
Thanks for those important pointers and the OP for this topic.
I also like my 2 year old HAM2 so much i just picked up another one as a fallback device perhaps if not daily handset.
I will leave that one JellyBean but i do plan to upgrade the next one to Lollipop 322 i hope.
On the old Mate 2 i flashed through TWRP the very latest SuperSU zip 2.76 i think.
I assume it's best to always use the latest version of it? Is that ok?
Mirror-Mirror said:
Thanks for those important pointers and the OP for this topic.
I also like my 2 year old HAM2 so much i just picked up another one as a fallback device perhaps if not daily handset.
I will leave that one JellyBean but i do plan to upgrade the next one to Lollipop 322 i hope.
On the old Mate 2 i flashed through TWRP the very latest SuperSU zip 2.76 i think.
I assume it's best to always use the latest version of it? Is that ok?
Click to expand...
Click to collapse
I also have a backup HAM2...very useful phone and must props to the devs for working on all the custom recoveries, roms and apps which help make our phones really customizable and usable.
Yes. Update SuperSU using the zip in TWRP 'install.' I just upgraded my own phone to CM13.0 (snapshot) and it fixed some issues (with other issues remaining...always a tradeoff lol!). SuperSu latest version works great! It's a good idea to use the newest version but remember if it isn't broke why take the chance to upgrade it and make it broken?
arcadesdude said:
I also have a backup HAM2...very useful phone and must props to the devs for working on all the custom recoveries, roms and apps which help make our phones really customizable and usable.
Yes. Update SuperSU using the zip in TWRP 'install.' I just upgraded my own phone to CM13.0 (snapshot) and it fixed some issues (with other issues remaining...always a tradeoff lol!). SuperSu latest version works great! It's a good idea to use the newest version but remember if it isn't broke why take the chance to upgrade it and make it broken?
Click to expand...
Click to collapse
It's been a long time since I bothered with ROM's, rooting etc. but another MT2-L03 in the stable demanded to get those hands dirty again.
As usual I errored some things a little, lost root, and even managed to muff TWRP backups with Error 255 or whatever. But Mate 2 is ever so forgiving. It was just a matter of reflashing the Stock Recovery and then firmware, Factory Reset, and install anew the UPDATE.APP+VENDOR (aka:Lollipop!) redo which cleaned everything out so that TWRP 3.02 installed and backed up as expected as well as ROOTED!! :good:
It took getting onboard the L24-LIW Honor 5X to make me appreciate the Mate 2 even more.

S. O. S Accidently deleted OS, no backup available

Hello guys, I know It may sound funny but I was tweaking around the TWRP 3.1.1-0 and when I tried to reboot it said: no os installed are you sure you wish to reboot?
Ive made no backups and i know nothing about flashing, roms, installing android and all those stuff I've seen when I Googled it. Can anyone give me some light? Step by step kinda thing?
Ps: I have not rebooted or whatsoever the phone so far after deleting this stuff XD idk if that would help
Just flash any custom rom and gapps using twrp...and the phone will boot..
Laranja mecânica said:
Hello guys, I know It may sound funny but I was tweaking around the TWRP 3.1.1-0 and when I tried to reboot it said: no os installed are you sure you wish to reboot?
Ive made no backups and i know nothing about flashing, roms, installing android and all those stuff I've seen when I Googled it. Can anyone give me some light? Step by step kinda thing?
Ps: I have not rebooted or whatsoever the phone so far after deleting this stuff XD idk if that would help
Click to expand...
Click to collapse
At this point you have to install a rom. You can choose to revert back to miui or install any nougat based from. If you want to install miui head over to en.miui.com and under device find "Redmi Note 4x", there would be global and developer builds available, download the build pertaining to Redmi Note 4x International version.
But if you want any custom ROM then download any ROM from the forums, but make sure it is ONLY nougat (7.1.2) version, because twrp 3.1 .1 doesn't support Oreo Roms.
If you choose to install miui make sure you have the lazy flasher zip with you. Now carefully follow the steps-
1. Copy the files to your pc or to an SD card .
2. From twrp - format data
3. Wipe - system, data, cache, dalvik
4. Copy the files to internal storage of device using a USB cable if the files are on pc. (ROM file , and lazy flasher if rom is miui)
5. Now install the ROM zip .
6. Flash lazy flasher if the ROM you installed was miui.
7. Now reboot (if you installed miui it will say no os installed, but just reboot)
MyNameIsRage said:
At this point you have to install a rom. You can choose to revert back to miui or install any nougat based from. If you want to install miui head over to en.miui.com and under device find "Redmi Note 4x", there would be global and developer builds available, download the build pertaining to Redmi Note 4x International version.
But if you want any custom ROM then download any ROM from the forums, but make sure it is ONLY nougat (7.1.2) version, because twrp 3.1 .1 doesn't support Oreo Roms.
If you choose to install miui make sure you have the lazy flasher zip with you. Now carefully follow the steps-
1. Copy the files to your pc or to an SD card .
2. From twrp - format data
3. Wipe - system, data, cache, dalvik
4. Copy the files to internal storage of device using a USB cable if the files are on pc. (ROM file , and lazy flasher if rom is miui)
5. Now install the ROM zip .
6. Flash lazy flasher if the ROM you installed was miui.
7. Now reboot (if you installed miui it will say no os installed, but just reboot)
Click to expand...
Click to collapse
Thanks so much sweet, I'll try this out tomorrow when I have my laptop with me, hopefully I'll be able to resurrect my phone

Latest Custom ROM für Galaxy Wifi 5.0 (YP-G70)?

Hello.
What is the last and best custom ROM for the Galaxy Wifi 5.0, and where can I find the files?
Thanks.
Meticulus.co.vu to download the latest but listen to me you need to start with cwm, then flash meticulous 4.4.4 to update the cwm, then flash twrp to get 5.1.1 installed, here. I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.
chris1892006 said:
Meticulus.co.vu to download the latest but listen to me you need to start with cwm, then flash meticulous 4.4.4 to update the cwm, then flash twrp to get 5.1.1 installed, here. I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.
Click to expand...
Click to collapse
I have tried but something went wrong.
Now when I boot I have a black screen with "NUTELLA" and a logo with "M".
If I use recovery mode a menu with yellow items is shown but every installation from ZIP file fails with the error:
E: failed to map file
Installation aborted.
Any suggestion ?
Thanks !
erlofp said:
I have tried but something went wrong.
Now when I boot I have a black screen with "NUTELLA" and a logo with "M".
If I use recovery mode a menu with yellow items is shown but every installation from ZIP file fails with the error:
E: failed to map file
Installation aborted.
Any suggestion ?
Thanks !
Click to expand...
Click to collapse
www.meticulus.co.vu/p/yp-g70.html
1st download this - https://androidfilehost.com/?fid=24591023225177417 + update 1 & 2 here =
https://androidfilehost.com/?fid=24665542585483890
https://androidfilehost.com/?fid=24686680535466961
2nd make sure you have cwm 5.0.2.7 because that Meticulus KK Carbon 4.4.4 rom will update to the version of cwm required to install twrp 2.8.0.0
3rd install the twrp 2.8.0.0 after you updated your cwm via the rom above, it auto-updates the cwm to the version required to have to flash twrp 2.8.0.0
twrp here - https://androidfilehost.com/?fid=24686680535466961
then install Meticulus 4.4.4 KK Carbon 4.4.4 make sure to put them in folders to know the KK is 4.4.4 and LP is 5.1.1
it fixes the partitions so it can take the 5.1.1 meticulous rom make sure to install the updates
ps - 4.4.4 is faster than 5.1.1
test 4.4.4 KK kit kat first then try 5.1.1 …. I'm using 5.1.1 because its newer but its really slow.
rom 5.1.1 - https://www.androidfilehost.com/?fid=24572369242688755
update 1 - https://www.androidfilehost.com/?fid=24665542585483911
update 2 - https://www.androidfilehost.com/?fid=24686680535466111
Finally I has been able to restore my device and install KK.
Now I will try it for some days and then will decide if upgrade to CM12
Some problems because .meticulus site is down today ( deleted ???? ) and because Odin with Win10 doesn't recognise my device. fortunately I still have a WinXP machine that works like a charms !
erlofp said:
Finally I has been able to restore my device and install KK.
Now I will try it for some days and then will decide if upgrade to CM12
Some problems because .meticulus site is down today ( deleted ???? ) and because Odin with Win10 doesn't recognise my device. fortunately I still have a WinXP machine that works like a charms !
Click to expand...
Click to collapse
KK works but seems slower than 2.3.6.
Is CM12 even slower than KK ?
erlofp said:
KK works but seems slower than 2.3.6.
Is CM12 even slower than KK ?
Click to expand...
Click to collapse
Yeah I'm using Slim Rom 4.3.1 right now but the camera is broken the pictures are blurry and the result is a corrupt file capture. So now I have to find another rom that'll work better.
Meticilius roms are laggy as all get out so idk what to do. I'm going to re-read my post on how to do these tricks anyway its been a while since i messed with it.
*UPDATE* I find Meticulus 4.4.4 works best for now at least the camera isnt broken but no overclock stability sadly but its fine. If only this device had 2gb ram it would be way more fun to play around with.
sadly the link posted for TWRP for the YPG70 was just the same link all over again.
does anyone happen to have the most recent TWRP?
what I want to do is repurpose my Galaxy Wifi Player to view the remote status of my car, so all it needs is a working screen, web browser and wifi.
speculatrix said:
sadly the link posted for TWRP for the YPG70 was just the same link all over again.
does anyone happen to have the most recent TWRP?
what I want to do is repurpose my Galaxy Wifi Player to view the remote status of my car, so all it needs is a working screen, web browser and wifi.
Click to expand...
Click to collapse
https://www.mediafire.com/file/uyhoyrubtjtzzm9/TWRP-2.8.0.0-venturi-flashable.zip/file
thanks @chris1892006 that's very kind of you.
chris1892006 said:
Meticulus.co.vu to download the latest but listen to me you need to start with cwm, then flash meticulous 4.4.4 to update the cwm, then flash twrp to get 5.1.1 installed, here. I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.
Click to expand...
Click to collapse
Is there any video to follow steps? Please help me. Thank you.
I'm sorry but I forgot how to do it from the gingerbread is what it comes with by stock right? Reading my posts on here I tell exactly how to do it around these threads somewhere around here on xda. Sorry bro. Keep in touch. BTW - the device is best left stock because its useless for anything for anything other than for musicolet music player or music folder player & mx player. I'd be pleased with stock because all I use mine for is Music only.

Categories

Resources