[GUIDE/TUTORIAL/HOWTO] Sony Xperia Tablet Z LTE or Wifi Any version to Android 9 Pie
[GUIDE/TUTORIAL/HOWTO] Sony Xperia Tablet Z SGP321 LTE/4G (pollux) or Wifi (pollux-windy) Any version to Android 9 Pie / LineageOS 16
This detailed step-by-step guide helps you transform your Sony Xperia Tablet Z to a powerful one with Android 9 Pie.
To make sure you are with a Xperia Tablet Z 4G / Pollux / SGP321 (SGP351 for USA, SO-03E for Japan) :
On the tablet, go to Menu -> Settings -> About tablet. Check that the "model number" is correct : SGP321 (Europe).
Same for the Wifi/Pollux_windy version.
### You must be logged as a Microsoft Windows administrator to run console commands below.
### When you lose control of your Xperia tablet Z, hold Power + Volume+ until tab restarts.
CHANGELOG
v14. If you want Magisk, use v25.2+
v13. Drop Magisk (if you want it, use v24.1), update pack
v12. Permanent TWRP recovery, overclock with Smartpack kernel manager
v11. Move to Android 9, replace addonsu with Magisk root, revert to 2016 adb + fastboot (fastboot flash fails with latest versions), fix glitches in tutorial
v10. Updated pack for TWRP 3.4.0-0 + LOS download links
v9. Updated pack for TWRP 3.3.1-0
v8. Moved to Official LineageOS 15.1 available to bring you Android 8.1 Oreo
v7.2. Refresh OpenGapps download link
v7.1. Refresh pack v2 (TWRP 3.2.3-0) and tutorial
v7. recovery TWRP 3.2.2-0 and new FOTAKernel installation
v6. Google Play certification, recovery TWRP 3.2.1-0, new pack for easier install
v5.5. Overclock
v5. Updated tutorial to latest ROMs and utils
v4. Upgraded tutorial
v3. Moved to Android 7.1
v2. Tutorial updated for permanent recovery, Black kernel, pack has no more missing fastboot files, drivers included, F2FS optimizations
v1. Initial release
1) DOWNLOAD FILES
- djibe Xperia Tablet Z pack (~ 48 MB) : http://bit.ly/djibe-xperia-tabletz-v2
(contains Xperia USB drivers + adb + fastboot + recovery TWRP 3.4.0-0 for both LTE/4G/Pollux version and Wifi/Pollux_windy + Smartpack Kernel Manager)
+ ROM Unofficial LineageOS 16: https://forum.xda-developers.com/xperia-tablet-z/orig-development/rom-lineageos-16-0-t3924942
Download latest build for Tablet Z LTE/Pollux: https://anonfiles.com/h7n8z0Rdx3/lineage-16.0-20220131-UNOFFICIAL-pollux_zip
Download latest build for Tablet Z Wifi-only/Windy: https://anonfiles.com/Ddncz2Rfx2/lineage-16.0-20220131-UNOFFICIAL-pollux_windy_zip
WARNING. Download correct version, Pollux for your 4G/LTE model, Pollux_windy for your Wifi-only model
ROM backups: https://androidfilehost.com/?w=files&flid=140468&sort_by=date&sort_dir=DESC
+ BitGApps ARM 9: https://github.com/BiTGApps/BiTGApps-Release/releases
or OpenGApps ARM 9 Nano: https://opengapps.org/?arch=arm&api=9.0&variant=nano
+ a microSD card. Copy ROM, OpenGApps, +/- Magisk +/- SmartpackKernel.apk on microSD card and insert it in tablet.
+ Charge tablet to 100%.
NB. Use a USB2 port to connect tablet to PC.
2) INSTALL DRIVERS
Commands below are for Windows 10 installation of unsigned drivers.
### For other Windows versions, Google "windows X install unsigned driver".
On the keyboard of PC, use "Windows key + R" combo.
In the command prompt that opens, type:
Code:
shutdown -r -t 0 -o
This opens a Windows menu:
Go to Troubleshooting > Advanced Options > Settings > Restart
Upon restart, press on keyboard : key 7 - Disables drivers signature verification
After boot,
Start Flashtool Xperia Driver Pack 1.8,
check the Fastboot drivers, ADB and Xperia Z tablet drivers, start the installation and confirm the
forcing the driver installation. It ends by saying that everything was installed.
Restart Windows.
2bis, optionnal, FOR WARRANTY PURPOSE) Backup bootloader
Cannot help you precisely, didn't know about it at the time.
- Root. Follow Bin4ry root : http://forum.xda-developers.com/showthread.php?t=1886460
Download : http://forum.xda-developers.com/showthread.php?t=1886460
- Then Backup TA. https://github.com/DevShaft/Backup-TA
Unzip it in C:\
Make sure partition is saved.
3) IMEI NUMBER
On tablet, go to Menu > Settings > About tablet > Status > Information on the IMEI code
Note the IMEI. Store it.
4) GENERATE BOOTLOADER UNLOCK CODE
From your PC, go to : https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
At the bottom of the page, in Select your device : Select Xperia Tablet Z (or Tablet Z Wifi).
Enter your IMEI and check both checkboxes.
Copy the unlock code on next page.
5) CONNECT TAB IN FASTBOOT MODE
Tablet powered off, hold "Volume up" while you plug the tablet in USB.
The blue light appears next to microSD cable, the drivers install in Windows.
6) UNLOCK BOOTLOADER
In Windows, copy the path to the "flash" folder you unziped earlier.
Open a Windows command prompt : Start menu > Command prompt > Start as administrator
Then type
Code:
cd /d thePathToFlashFolder
(ex: E:\root\Sony Xperia Tablet Z SGP321 Pollux\djibe Xperia pollux Pack\flash)
Type:
Code:
fastboot -i 0x0fce getvar Version
If a line is returned, drivers are correctly installed.
### Use fastboot and adb from my pack
Paste the following line (written at the end of the page issued by Sony) :
Code:
fastboot oem unlock 0xYOURUNLOCKKEY
confirm with Enter. After 2 seconds, it is displayed OKAY.
Bootloader is unlocked !
7) FLASH TWRP RECOVERY 3.4
Still in fastboot, type in console :
Code:
fastboot flash boot twrp-3.4.0-0-pollux.img
(or twrp-3.4.0-0-pollux_windy for Wifi model). Confirm with Enter.
Wait, then once the confirmed success,
type :
Code:
fastboot reboot
(confirm with Enter).
AND while it restarts, repeatedly click Volume+ AND Volume- buttons to access the recovery (can take a while).
8) BACKUP CURRENT ROM
You are now in TWRP recovery, swype to unlock changes.
Go to Backup, select all partitions.
In Storage, select microSD Card then OK.
Then swype to start backup (Well, hums, it failed on my tablet ;-) ).
Click the TWRP icon to return to home.
Go Wipe > Wipe Advanced > Select Dalvik, System, Cache, Data and swipe to confirm flash.
### If errors are displayed in red "failed to mount data (invalid argument)" appear (as I had),
### go to Wipe > Data Format, type yes and click OK.
9) FORMAT TO F2FS
INFO. F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and EXT4 is still faster.
Still in Advanced Wipe menu,
select the /Cache partition and tap Repair or Change File System > Change File System and select F2FS.
Confirm with a Swipe to Change.
Do it again for the /Data partition.
### Any partition problem ? Bootloop ? Format every partition back to EXT4, wipe all partitions and reflash Zips.
Go to Reboot > Recovery.
10) INSTALL ROM, GAPPS +/- ADDONSU ROOT
Back to TWRP home menu.
Go to Install > select lineage*.zip.
### If no file is visible, click Storage > select microSD Card.
### If you get an error and flash fails, go to Reboot > Recovery and wait for TWRP to reboot.
Add more zip > OpenGapps*.zip file,
(Optional) Add more zip > addonsu*.zip file.
Swype to confirm flash.
Wait while Install Zips are flashed.
At the end, select Wipe Dalvik and cache and then Reboot system.
Tab will reboot soon after first reboot.
Wait during both boots.
11) ROOT
Go to Settings > About tablet > Tap 7 times on Build number item.
Go to Settings > System > Advanced > Developer options.
Root > Applications and ADB.
12) PERMANENT TWRP RECOVERY AND TWEAKS
To keep TWRP recovery permanently, you need to flash it to a smart location: the FOTAkernel partition.
Now Settings > System > Advanced > Developer options.
Advanced restart switched ON (Hold power > Restart > Restart to recovery to access TWRP easily later)
Root access > ADB only
Android debugging switched ON
Windows animation scale yo Animation scale .5x
Same for Transition animation scale and Animator duration scale to improve reactivity
Connect tablet to PC.
Re-open a Windows command on my /flash folder.
Enter commands in order:
Code:
adb devices
On tab, grant ADB access
Code:
adb root
Code:
adb wait-for-device
Code:
adb push twrp-3.4.0-0-pollux.img /tmp/twrp.img
Command returns: 2600 KB/s (12103680 bytes in 4.544s)
and finally
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
It will output
> 23640+0 records in
> 23640+0 records out
> 12103680 bytes transferred in 2.864 secs (4226145 bytes/sec)
You are done with flashing ! Congratulations.
13) OVERCLOCK (optional)
Open built-in Files app.
Open microSD folder.
Install Smartpack Kernel Manager app from my pack.
Launch app and grant root access.
Go to CPU menu > Apply on boot, CPU Maximum Frequency 1728 MHz
CPU min: 192MHz
Governor: ondemandplus
GPU: 487MHz
14) Others
For faster GPS fix, use GPS Status and Toolbox and download A-GPS data.
Your tablet is a rocket, enjoy ;-)
Thanks: LineageOS team, TWRP team, OpenGApps team, Flashtool Xperia Driver pack team, @CaHbKaUp, @CyberWalkMaN, @AdrianDC, Chippa_a, @Rootk1t
You forgot to mention about Backuping TA before bootloader unlock.
Also operation under numbers 4,5,7,8 can be done via Flashtool practically in one click, so it's much faster.
Also with frequent messages "can't post outside links" instruction is "half-done".
Your message
Rootk1t said:
You forgot to mention about Backuping TA before bootloader unlock.
Also operation under numbers 4,5,7,8 can be done via Flashtool practically in one click, so it's much faster.
Also with frequent messages "can't post outside links" instruction is "half-done".
Click to expand...
Click to collapse
XDA blocks my external links. What can i do about that ?
About flashtool, it is always more instructive to understand all the process rather than a tool you don't know the limits.
I'll look at TA partition backup, thx for your advice.
But this guide is made to help noobs like me. Everyone isn't good as you. Title is clearly written for noobs.
Direct links are finally available
Hi
Which version of stock are you using? Thanks!
Latest OTA from Sony. Looks like a 4.x.x with Sony Touch Interface
juanchinho said:
Hi
Which version of stock are you using? Thanks!
Click to expand...
Click to collapse
Latest OTA from Sony. Looks like a 4.x.x with Sony Touch Interface
Thanks a lot for this guide!
After installing CM13 on my Xperia Tablet the IR Blaster does not work, there is no signal coming out of it at all. What about you other guys here. Does IR Blaster work or not with you?
nicky-xda said:
Does IR Blaster work or not with you?
Click to expand...
Click to collapse
no.
IR Blaster not working: Good to know i'm not the only one with that issue
Who knows if this is considered as a bug and will some time in the near future be worked on and hopefully fixed?
Enhanced tutorial,
hope you'll like it !
Tutorial in 4th version available
YOU are a legend, you and a note stating that this device don't have a separate recovery so I had to use "fastboot flash boot ..." instead <3
So long since I last installed a custom rom that I forgot how and lost my how-to
PS: I still miss the IR-blaster since I had the stock ROM when the device was new :cyclops:
ettkatthej said:
YOU are a legend, you and a note stating that this device don't have a separate recovery so I had to use "fastboot flash boot ..." instead <3
So long since I last installed a custom rom that I forgot how and lost my how-to
PS: I still miss the IR-blaster since I had the stock ROM when the device was new :cyclops:
Click to expand...
Click to collapse
Hi,
sorry, i'm not sure I fully understand your message.
Do you need some help ? Is Something not clear in tuto ?
See you
djibe89 said:
Hi,
sorry, i'm not sure I fully understand your message.
Do you need some help ? Is Something not clear in tuto ?
See you
Click to expand...
Click to collapse
Guess I got a bit overwhelmed by it finaly working, it was just a long and confused thank you..:angel:
Jumped in at stage 7.
ettkatthej said:
Guess I got a bit overwhelmed by it finaly working, it was just a long and confused thank you..:angel:
Jumped in at stage 7.
Click to expand...
Click to collapse
Is there Something not clear in my tuto I could enhence ??
Not success in rooting sgp321 android 4.4.4 292 version, using the bin4try.，can somebody helps?
dickzoe said:
Not success in rooting sgp321 android 4.4.4 292 version, using the bin4try.，can somebody helps?
Click to expand...
Click to collapse
Use Easy Root Tool, KingRoot or Vroot.
thank you for your advice, I just rooted via kingroot. however, during unlocking bootloader process, after insert the unlock code via fastboot, it shown: failed (remote :command not allowed. ) Any clue?
dickzoe said:
thank you for your advice, I just rooted via kingroot. however, during unlocking bootloader process, after insert the unlock code via fastboot, it shown: failed (remote :command not allowed. ) Any clue?
Click to expand...
Click to collapse
service menu shown: bootloader unlock allowed: no
Any helps?
Related
[GUIDE/TUTORIAL] Asus Transformer Prime to Android 7.1/LineageOS 14.1
[GUIDE/TUTORIAL/HOWTO] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat/LineageOS 14.1
This detailed step-by-step guide helps you transform your Asus Transformer Prime with Android 4.1.1 to a powerful one with Android 7.1 (Nougat).
### I'll make a few comments like this, read these or you may miss something.
### The Asus Transformer Prime codename is TF201.
Try to prefer USB2 connections, but USB3 works fine too.
CHANGELOG
v11. Improvemed unlock section
v10. Updated links
v9. ROM v39 and removed obsolete info
v8. ROM v35 and enhenced link for OpenGapps
v7. Refresh pack for ROM v32 and TWRP recovery 3.2.3-0
v6. Google Play certification
v5. Updated djibe pack for easier install (kang recovery 3.1.0-1, SuperSU, drivers if fails at Step 6) + switched to v26 of Katkiss
v4. TWRP Kang recovery 3.1.0-1
v3. Tweaks and walkthrough
v2. Android 7, many hints added for more accurate tutorial
v1. Initial release
BEFORE STARTING
Make sure you have the latest official updates for your tab :
In Android, go to Settings -> About tablet -> System Update
### Make sure you read all comments starting by ###
To make sure your tab is the correct model, go to Settings -> About tablet.
The details below are listed :
• Android 4.1.1 (JellyBean; Nvidia logo bottom right on boot)
bootloader V 10.4.2.18
### To verify bootloader version, shut down tab. Then hold Power + Volume- for 3 seconds and release.
### You are in bootloader : on top left corner is written Android (...) epad-10.4.2.18.
### To quit bootloader, press Volume- to go over the Android icon, then Volume+ to confirm.
### If not V 10.4.2.18, check official updates for your tab before starting this tutorial
### or check more info on Asus support web page and download the version identical to the Firmware Description written top left corner of the bootloader
### Asus support is here : https://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_BIOS/
• GPS 7.9.13
• Wi-Fi 7.1.0.24
• BT 10.33
• Camera FT201-0x9900
• Ecran MXT-2.0 build-170
• Kernel 3.1.10.00002-9599d0cf [email protected]
o #1 SMP PREEMPT Thui Nov 22:12:01 CST 2012
• Build nr JR003C.WW_epad-10.4.2.18-20121122
Still in Settings -> About tablet, tap 7 times on build number to unlock Developer menu.
0) BACKUP YOUR DATA
Backup SMS, photos, contacts before going any further (ex: use the backupyourmobile app).
Check that backup is located on microSD card.
Then copy the backup on your PC.
1) DOWNLOAD
djibe Transformer Prime pack v2: http://bit.ly/djibeTransformerPrimev2
(contains Windows Universal Naked drivers + android_winusb if step 6 is difficult + Asus UnLock_Device_App_V6.apk + fastboot.exe + adb.exe + nvflash.exe + HairyBean Bootloader and various recoveries necessary + SuperSU 2.82).
Unzip the file on Windows desktop.
+ ROM KatKiss Nougat v39 Android 7.1
XDA Thread: https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Download here: https://downloads.timduru.org/android/tf201/K.A.T/KatKiss/7.x/dev/ or https://www.androidfilehost.com/?fid=14943124697586357425
+ OpenGapps ARM 7.1 ARM Pico (NO OTHER DISTRIB THAT ARM PICO please): https://opengapps.org/?arch=arm&api=7.1&variant=pico
You must have a microSD card (FAT32 format), copy the zip files from Katkiss ROM, OpenGapps and SuperSU.
Then insert it in the tab.
2) INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PRIME TF201
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code:
shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Once driver installation is completed, reboot PC as usual.
- Windows Vista/Windows 7 :
Go to folder /Universal Naked Drivers 0.72 you unziped earlier (on Windows desktop).
Select file android_apxusb.inf, then right click -> Install.
Force driver installation and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Then plug tablet to PC (USB2 port) to end driver installation.
### If it fails to install you may try using Windows device manager :
### In Windows Device Manager menu -> Right-click on Asus Android Device -> Update Driver Software -> Let me pick -> Have disk -> Browse to the .inf file and install BOTH .inf files.
### See this post if still doesn't work : https://forum.xda-developers.com/showpost.php?p=75240547&postcount=166
- For Linux, I have no experience. Every tools should be here : https://github.com/AndroidRoot/androidroot.github.io/tree/master/download
- Copy the UnLock_Device_App in tablet's internal memory
Tab should normaly be seen in Windows explorer as TF201.
Check MTP file transfer protocol is active on the tab.
Copy the UnLock_Device_App_V6.apk in the root folder of the tab.
3) UNLOCK BOOTLOADER OF ASUS TF201
Tablet must be fully charged to 100 %.
In Android, go to Settings -> Security -> Check Unknown Sources.
Then Settings -> Developer options -> Enable USB debugging.
Launch the preinstalled app File Manager to install UnLock_Device_App_V6.apk.
### If it fails to install, delete your Google Account. Go to Settings -> Accounts. Delete the Google Account.
Launch the UnlockApp.
Accept User agreements. Your warranty is now void.
Accept and click to unlock the tab,
let the tab restart and work.
After reboot , "This device is unlocked" is written on top left screen.
### It probably won't work that simple.
### The solution is here, but I didn't have to test it: https://forum.xda-developers.com/t/howto-unlock-tf700t-in-2020.4157143/post-85255809
4) PREVENT BRICK : NVFlash
This step is optionnal but highly higly highly recommended, your tab will never be bricked after it !!!
1ST PART --------------------
Tab shut down, press Power + Volume- for 3 seconds and release, you are in the bootloader.
Use Volume- to move cursor over the USB logo, confirm with Volume+, you are in the fastboot mode.
Connect Transformer Prime to PC.
Select the "Files" folder you you unziped earlier.
Do Shift + right click on folder -> Open a Command Line.
Type:
Code:
fastboot -i 0x0b05 flash recovery flatline_tf201.img
and confirm with Enter.
### If you get error "fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program",
### type the command starting with a dot :
Code:
.\fastboot -i 0x0b05 flash recovery flatline_tf201.img
A blue bar appears on the tablet indicating flash success.
Wait until command line reports the flashing success.
then type :
Code:
fastboot reboot-bootloader
and confirm with Enter.
This time in Bootloader, use Volume- to select RCK (recovery) and confirm with Volume+.
You are in the flatline recovery.
Use Volume- to go to Advances, confirm with Power.
then wheelie, confirm (Power button),
then i accept the above statement (Power button),
then Step 1: flash AndroidRoot BL, tab powers down.
Start tab with Power only,
let the blue bar fill completly and start Android normally.
Once in Android, shut it down.
Start tab in bootloader Mode again (still Power + Volume- ;-) ), go to recovery again (RCK).
Connect tab to PC.
In recovery, return to Advanced -> wheelie then select Step 2: generate wheelie blobs.
It generates the backup files !!!
Open another Windows command prompt for fastboot mode and type :
Code:
adb pull /data/media/AndroidRoot
.
Backup files are stored in your "Files" folder. Make another backup of these files in a safe place.
(7 files are saved : recovery.bct, create.bct, bootloader.ebt, blob.log, blob.bin, pt_restore.log and pt_patch.log)
### If
Code:
adb pull /data/media/AndroidRoot
doesn't work : start Android normally, connect to PC as multimedia storage and
### navigate to My Computer -> Transformer Prime TF201 -> Internal Memory -> Android Root and copy the files in here.
Shut down tab.
2ND PART, NvFlash ----------------
Copy these 7 files in the folder "files/nvflash" (Another copy, in addition to the backup you made).
Connect tab to PC.
Start tab in Nvidia APX Mode : Hold Power + Volume+ for 3 seconds.
Anything happens, it's normal, screen stays black.
The tab is visible as an external drive and is called APX.
Open another Windows command prompt on the nvflash folder.
Type :
Code:
wheelie --blob blob.bin
and confirm with Enter.
If successful : the tab launches in bootloader mode and the Command prompt writes a few lines.
Type in command :
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
then :
Code:
nvflash --resume --read 14 factory-config.img
then :
Code:
nvflash --resume --read 7 unlock-token.img
You have to backup 3 new files : bricksafe.img, factory-config.img and unlock-token.img.
Copy these files in a safe storage with your blobs for future repair if needed.
### If you need to restore those backups one day, follow the tutorial of craigacgomez : https://forum.xda-developers.com/showthread.php?t=1927818
### If you have error "not enough space for GApps (error 70), follow this tutorial https://forum.xda-developers.com/showpost.php?p=73403429&postcount=137
5) RECOVERY
(Only applies to stock bootloader V 10.4.2.18).
Charge tab to 100% before continuing.
Start it in bootloader mode (Power + Volume-).
Connect it to PC.
Set the icon over the USB selection.
Confirm with Volume+; you are again in fastboot mode.
Open a command prompt on the /files folder.
Type :
Code:
fastboot devices
.
if the serial number is written, tab is well connected.
### Or check driver installation if not.
then type :
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
and wait for the "finished" success message,
then type :
Code:
fastboot -i 0x0b05 reboot-bootloader
,
and confirm with Volume+ to get into RCK (recovery, again), it is now TWRP 2.6.3.0.
6) BOOTLOADER
Once in TWRP recovery, type in command prompt :
Code:
adb devices
-> terminal returns : 012345678ABCDEF recovery.
Type :
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now on the tab, still in TWRP recovery, go to Install then click on HairyBean_Bootloader_TWRP2.5.zip
(file is in Internal memory, in folder /sdcard).
Swype to the right to confirm flashing, wait until Successful message appears.
Now click Reboot System and Do Not Install when SuperSU is proposed.
Let the tab reboot with another blue bar. Let it work.
The tab reboots and launches the HairyBean TWRP recovery (androwook).
In Windows command prompt, type :
Code:
adb reboot-bootloader
,
tab reboots in bootloader mode and the USB icon is gone, it's perfect.
### If Windows doesn't recognize your tab, or recognizes it as VID_0B05&PID_4C83, try the fix from XTCrefugee included in my pack : folder \Drivers android_winusb if hairybeen TWRP not recognized
### Install this .inf driver file as you did earlier
###
### YOUR BOOTLOADER IS NOW IN 10.6.1.27.1 VERSION
###
In command prompt, type :
Code:
fastboot -i 0x0b05 flash recovery twrp-3.2.3-0_KANG-tf201t.img
Wait till blue bar completes.
When finished message appears in terminal,
type :
Code:
fastboot -i 0x0b05 reboot-bootloader
, tab reboots.
Now enter in new recovery with Volume+ : recovery is now TWRP Kang 3.2.3-0 Recovery
### Your tablet will be seen by Windows as a TF201T now !
7) SET FILESYSTEM TO F2FS
F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Go to Wipe -> Advanced Wipe, select only the Data partition,
then tap on Repair or Change File System -> Change File System and tap on F2FS.
Swype to force partition system as F2FS. Wait till done prompts. Then go back to Advanced Wipe.
### If TWRP sends you this log in red : E:Failed to get default contexts and file node for storage files,
### Reboot to TWRP recovery again before going any further.
Repeat the operation of F2FS conversion for the Cache partition.
8) INSTALL ANDROID NOUGAT 7.1
Still on TWRP Advanced Wipe menu,
select Dalvik Cache, System, Cache, Data AND Internal Storage and Swype to force cleanup. Wait till completion.
Back to Home screen, tap Install, then Storage: Internal Storage and change it to microSD card -> OK.
Select KatKiss* .zip, and Add More Zips,
select SuperSU.zip, and Add More Zips,
then open_gapps-arm-7.1-pico*.zip and Swype to force install. Be patient.
### Make sure once again you have the Pico Gapps version or system will hang.
### If TWRP crashes to its Home screen, you microSD might be in cause. Find another one, and then try to install Zips 1 by 1.
### If error installing Gapps, see this thread : https://forum.xda-developers.com/android/help/fix-error-70-install-gapps-t3311779
When done prompts, tap on Wipe Cache/Dalvik and swype to confirm, wait.
Go back to Home when done.
Then Reboot -> System.
Let the tab start during at least 15 minutes.
9) START ANDROID N 7.1
### During first setup, manually toggle Wifi ON using the Wifi icon on the bottom right corner. If you don't, the setup app will crash.
### It can crash a few times before turning on, keep activating it.
Configure Android as you like.
In Settings -> Mediascanner filters, uncheck Scan.
In Settings -> About, tap 7 times on build number, it unlocks the Options for developers in Settings.
Enter this new menu.
In the Hardware acceleration, try both GPU rendering active and disabled.
I can't figure which one works best. Share with us.
Good to know about this ROM:
Bluetooth requires to be turned on twice before it turns on.
A few things including the navbar buttons can be tweaked in Settings => System UI Tuner.
AND more on XDA Katkiss thread (See DOWNLOAD CHAPTER ABOVE)
10) ROOT
Open app SuperSU to see more details about the Root access.
After ROM first launch, go to Settings -> About tablet.
Tap 7 times on build number, it will unlock the Developer menu.
In the developer menu -> Try to turn ON and OFF the Force GPU option and tell me what is the faster one.
(I think I prefer when GPU forcing is disabled).
11) PERFORMANCES AND OVERCLOCK
Source of benchmarks: http://androidmodguide.blogspot.fr/p/blog-page.html
Install Kernel Adiutor app from Google Play Store.
Launch app and go to Settings -> Kernel -> CPU :
Check Apply on boot and change CPU Maximum Frequency to 1600 or 1700 Mhz, set Governor to Interactive
Now Kernel -> I/O Scheduler :
Check Apply on boot and set Scheduler to Zen, then Readahead to 1024 Ko (or 2048. Try yourself)
Now Kernel -> Various :
Check Apply on boot and set TCP congestion to Cubic (or Westwood)
12) VARIOUS FIXES
### Your tablet doesn't see the Wifi ? (that is on Channel 13 by example).
Try this first : in the Wifi screen (where you see all visible networks), tap on the three-dots icon to open the menu -> Advanced wifi parameters.
Tap on the Wifi region code item to select the region : chose the corresponding region.
Now verify your Wifi network is visible.
If not, try this :
Open Kernel adiutor, Menu -> Build.prop editor.
In key search field, type wifi.
Click ro.wifi.channels -> Edit -> in the value field, set 13. Confirm with OK.
At the same time, you can set wifi.supplicant_scan_interval=180 to 180 (seconds) to reduce number of scans and reduce battery usage.
Restart tab, your wifi network should be visible again.
### Your keyboard isn't in the correct language
Go to Android Settings menu -> Languages & inputs -> Physical keyboard -> Android keyboard
Enjoy your new tab ;-)
djibe
Thanks : @timduru, matthill.eu, Kang for updated TWRP, TWRP team, Android Root Team, Lineage OS team, TacoNikky, Saber
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
HorthLithperer said:
Thanks for the step-by-step. I've worked my way to nougat and the path there is kind of forgotten after a while. Different bootloader, different file systems, sort of lose track of things.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Thanks for your support. It was a tough job to explain step by step.
Took me 3 days to discover all the details.
thanks
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
yo29570 said:
really great work.
i want to add a comment : When trying to unlock bootloader, it kept on asking pw for google account (and double authentification disabled). I deleted google account from prime and it went through.
Click to expand...
Click to collapse
Thx for feedback.
I had the same problem and used the tab factory reset.
I've updated tutorial and told to delete the Google Account.
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Woodrow256 said:
I just wanted to thank you for making these instructions. Ive never delt with any android device with this many steps. Compared to a nexus 6p this is nuts. Ive messed around with Motorola and Samsung phones but this tablet is a whole other league. You made it very simple to turn my daughters slow old tablet into a relevant one. I still cant believe there was that much to it. Its only 10 steps...lol
Click to expand...
Click to collapse
Glad you liked it and tab is healthy again !
I've made tuts for Xperia Tablet Z and Samsung devices too if you are interested
Problem with step 8 - INSTALL Android 6 ROM
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
deltabert said:
Hello djibe89,
First of all, I would like to thank you very much for this well documented step-by-step guide for upgrading the TF201! It was no problem for me, a novice in this, to follow.
However i do have encountered a problem with booting after the installation of step 8. And i hope you are able to help me with this. When i try to boot the device after Successful installing KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip, and Beta-superSU-v2.52.zip, the device seems to be in a boot-loop. The OS never starts up.
I also tried the older KatKiss-6.0_TF201_028.zip with the two other zip files, but the result is the same.
Until step 8, all installations went without major problems. (i made a document from your instructions and documented every step i did, (including serial number received from fastboot etc). So my TF201 is now Unlocked and the bootloader TWRP is at version 2.8.3.0.
There is only one thing i received at step 7, wich i think i should mention. When i do Wipe -> Format Data, i receive the following message when it's Done:
Updating partition details ...
... done
Full SELinux Support is present.
(in red) E: Failed to get default contexts and file node for storage files.
MTP Enabled
Formatting Data using make_extfs function
You may need to reboot recovery to be able to use /data again.
Updating partition details ...
... done
I did not pay attention to this message, because there was also the Successful message.
But perhaps it does have something to do with my problem of not being able to boot into KatKiss.
Hope you are able to help me with this.
(Maybe i will try to install Nougat for the TF201, since the recovery with TWRP is OK.)
Kind regards, Bert
Click to expand...
Click to collapse
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
djibe89 said:
Hi, I'm glad you liked it.
Seems like you chose wrong Filesystem format " Formatting Data using make_extfs function".
We need a F2FS partition.
Go back to your TWRP 2.8 recovery,
wipe all partitions,
chose /data partition and change filesystem to F2FS.
Make sure /Cache partition is F2FS too.
Then you can Install the zips.
Keep in touch.
Merry christmas from France
Click to expand...
Click to collapse
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today (27 dec.) i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
Got the tab in APX mode again (Windows Device Manager shows Asus T. P. APX..)
So i went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
deltabert said:
Hello djibe89,
Thank you for answering my question.
But before receiving your answer I was already trying to do the steps again (from step 4), which was (looking back) obviously a bad idea. I am afraid I made a mess of it right now. First of all i should have read the error msg carefully to see the file system type. I was aware that this KatKiss is using f2fs?
I already send you a pm describing what i had done, and that i had to stop experimenting until after Christmas
Today i tried an other attempt to revive my tab, and started by: 2ND PART, NvFlash---
But unfortunately i am not able to get the tab in APX mode again.
Then i skipped this en went on with 5 - RECOVERY
I do get the fastboot screen; with the menu's RCK - Android - USB - Wipe Date, and went to USB.
Giving the command fastboot devices gives the serial number, so its connected.
Then i gave fastboot -i 0x0b05 flash recovery twrp_tf201t.blob which gave sending 'recovery' <7934 KB>...
OKAY [2.213s]
writing 'recovery'...
OKAY [ 3.534s]
finished. total time: 5.747sthen a reboot bootloader with: fastboot -i 0x0b05 reboot-bootloader
After this i had the TWEAMWIN screen again.
with adb devices i get the 012345678ABCDEF recovery message. So, adb can connect.
But re-installing HairyBean_Bootloader with adb push HairyBean_Bootloader_TWRP2.5.zip /sdcardgives an error on the tab.
Then i realized that i have just re-installed TWRP 2.6, which is intended for JB bootloader! So i booted the tab to fastboot and installed the TWRP 2.8 with:
fastboot -i 0x0b05 flash recovery twrp.blob That went OK.
Now i tried to install KatKitt6 again, now with all partitions formatted as f2fs.
But i stil don't get Katkitt6 booting. It keeps rebooting.
Besides this, I am still worried that NvFlash might be no longer on the tab...
And i don't get the FlatLine booting with volume-up and power anymore...
===============================================================
Today, 28 dec. i did an other attempt and made photo's from the screen of the tab.
From within TRWP 2.8.3.0, I started at Step 7 – SET FILESYSTEM TO F2FS
Wipe :: Format Data, uses ext4 filesystem (as described in the tutorial) and takes indeed a long time.
Next Wipe :: Advanced Wipe ONLY the data folder, and set to F2FS
Also with the Cache partition also set to F2FS
Step 8 – Install Android 6 ROM. From TWRP Wipe :: Advanced Wipe. Select Dalvik Cache, System, Cache and Internal Storage. Swipe to cleanup. NO mention of changing the filesystem to F2FS so I left these as they are!
Installation of the tree .ZIP files, see pictures below:
Unfortunately, i am only able to put links to photo's when i have at least posted 10 posts. Since i am new here i try an other way of linking to the photos:
Step 7 and 8 - Photo 1 https: // deltabert.stackstorage.com/s/gszDWyVd9sqHiQs
Step 7 and 8 - photo 2 https: // deltabert.stackstorage.com/s/Ju0tmwMIUjJXHg4
Step 7 and 8 - photo 3 https: // deltabert.stackstorage.com/s/o0tTQ3tPBHF85Wu
Step 7 and 8 - photo 4 https: // deltabert.stackstorage.com/s/Cls41PHHcCa0TKr
And when I press Reboot, after Wiping Dalvik Cache, the tab keeps rebooting! This time I see no error messages.
And believe me, I left it booting for hours…
Any idea as what I could do next?
Click to expand...
Click to collapse
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
ALDO_MAC12 said:
did you ever get through this part?
im on the same boat.....finished everything successfully but once i install the ROM it keeps rebooting and stays on the TWRP until i reboot again
Click to expand...
Click to collapse
Hi ALDO-MAC12,
Unfortunately, i have not yet got my TF201 working. I'l wait now until djibe89 has time to react.
(When i opened his zip file i noticed he has also a France language description, and he is at the moment in France, So i guess he is a French-Canadian, on vacation in France.)
I did study the original posts from timduru and TacoNikky, but i can find no differences with the description of djibe89. Noticed there is also a Android 7 rom from timduru. But i think i should first get to manage the hole process.
For me all this is new. My tab became so horribly slow that i only sparsely used it anymore. So that's why i would like to give it a try.
BTW, i do get the tab in APX mode; with volume up and power, i get a black screen but in Windows Device Manager there shows up the Asus Transformer Prime APX ... driver.
If you're running Windows 10, you need to delete all your other android drivers, then disable the signature checking on your driver installation and install the Naked Universal driver.
Super SU wants update
Works for me on windows 10. Make sure tablet is plugged in directly and not into keyboard also. Although Super SU is now reporting an update in necessary. Is it recommended in update Super SU after installation? Btw thanks for bringing new life to my tablet!
Have you tried not to change /cache partition to f2s2. The original KatshMallow thread says:
This ROM is for TF201 and F2FS only
Convert just /data partition to F2FS
Click to expand...
Click to collapse
...
Hello all,
Thank you for thinking with me, I appreciate this very much! I will react to the suggestions given.
@lazuhrus, I think the Universal Naked Drivers 0.72 are correctly installed on my Win-10 PC. I followed the procedure for Win-10 to disable driver control. To confirm this: I am able to use fastboot from Win-10; fastboot devices gives me the serial number of the tf201.
Also the command adb devices gives me: 012345678ABCDEF recovery.
Further, when I bring the tf201 (with volume UP and power) in APX mode, I get a dark screen on the tab, but in Windows Device Manager there shows up the Android device: Asus Transformer Prime APX Interface.
So for me this seems OK. This lets me conclude that the Universal Naked Drivers 0.72 are correctly installed and working. Or am I overlooking something here?
Btw, I do this on the bare tablet, without the keyboard dock.
With volume DOWN and power, I get the tab in TWRP version 2.8.3.0.
And installing KatKiss seems to go well (see the screenshots I posted in #10 from the TWRP format and install process).
@ shaDNfro, I did change the /cache partition to f2fs, as the screenshots are showing too.
However, there is one strange thing. After the last install (post #10) when I am in TWRP and connect the tab to my PC (win10) I see in the File Explorer an entry for an ASUS Transformer Pad TF300T; while mine is an TF201!!
Picture File Explorer: https: // deltabert.stackstorage.com/s/Nj1C01jTyZ5MoWB
And in the Device Manager I see also references to the wrong tab type!
(But you can see the Asus Android Composite ADB Interface.
Picture Win10 Device Manager: https: // deltabert.stackstorage.com/s/zK2LIoAthr4jKJ7
(added spaces around // because i am as novice not (yet) able to post links)
Hopefully anyone can help me with this...
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
djibe89 said:
Hi guys,
I am French from France indeed
- Maybe try to reformat the /cache partition in EXT4 (instead of F2FS).
Then wipe all partitions and install all zips again.
- It is normal that your tab is seen as TF300 as the TWRP 2.8.3.0 is originaly openrecovery-twrp-2.8.3.0-tf300t.blob.
I no longer have my tab so it's tricky to help you. I'll try anyway
Click to expand...
Click to collapse
Thank you djibe89,
I really hope you can help me with this, I become a little desperate...
I wonder if there is something wrong with the bootloader (HairyBean_Bootloader_TWRP2.5.zip). When I boot the tab with vol-down and power I get the following bootloader info: Android cardhu-user bootloader <1.00 e> released by “WW_epad-10.4.2.15-20120917†A03
Do you know if this is correct?
OK, I put the tab in TWRP 2.8.3.0 mode.
Formatted the /Cache partition using make_ext4fs
Then I wiped Dalvik Cache, followed by /System, which formats to ext4fs.
Then format /Data, first with make_ext4fs, and when finished, I change the filesystem of /Data to f2fs. Wiped all other partitions, except Micro SDcard (not sure if this is the internal or external SDcard)
Then I installed the three .zip files. KatKiss-6.0_TF201_029.zip, open_gapps-arm-6.0-pico-20160320.zip and BETA-SuperSU-v2.52.zip.
I also put the MD5 checksum file of KatKiss-6.0_TF201_029.zip on the sdcard and the install procedure checks the .zip successful.
When install is done: Successful, I wiped Dalvik Cache and rebooted the tab.
But then I have the same reboot problem: First i see a blue bar for one second, then the tab boots with the ASUS splash screen at medium intensity, then switches for a moment to high intensity and back to medium intensity, and after a few seconds it reboots and it starts over again.
When I leave the tab booting for two hours, I can feel it is doing something; the backside is becoming slightly warm; processor: ~ 45°C.
The bootloader is part of HairyBeen isn't it? Could I re-install the correct HairyBean_Bootloader_TWRP2.5.zip again, by putting it on the external sdcard and selecting it from TWRP 2.8.3.0?
fastboot, adb and Nvidia APX Mode are still functioning, so there must be a solution...
Hopefully you have a good suggestion?
Kind regards, Bert
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
djibe89 said:
Yo Bert,
you must be in distress.
Maybe it's time to look for a NVIDIA APX restoration.
I hope you still have your backup files.
I don't know anything about it,
so read all Google carefully to proceed.
That's why I motivated you to backup APX in my tutorial, since we never what can happen with Android hardware.
Keep in touch
Click to expand...
Click to collapse
Hi djibe89,
I will look into the restoration option. I do have the APX backup files.
Will be continued....
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S3 International i9300 Any version to Android 9
This detailed step-by-step guide helps you transform your Samsung Galaxy S3 International i9300 to a powerful one with Android 9 Pie / LineageOS 16.
Verify your phone is i9300 before going further: in Android, go to Settings > About > Check model is GT-I9300.
If not, quit this tutorial.
CHANGELOG ------------------------
v7. Moved to Android 9 Pie + Wifi fix
v6. Updated links and Samsung USB drivers, revert TWRP to 3.2.3-0 for correct Install (3.4 crashes with failed to map..), switched to Magisk root, removed F2FS format
v5. Updated links and pack (removed hybrid kernel, updated TWRP 3.3.1-0), added Android Pie alternative, backup IMEI partition
v4. Pack refresh : Hybrid kernel v13, OpenGapps download link
v3. Pack refresh : Hybrid kernel v11.2, TWRP recovery 3.2.3-0, Boeffla config 2.5.20
v2. Moved to Android 7.1, new pack, custom kernel, latest Odin + kernel
v1. Initial release for Android 6
1) DOWNLOAD
- djibe Galaxy S3 i9300 pack: http://bit.ly/djibe-galaxys3-pack
(contains preconfigured Odin 3.13.1 + Samsung USB drivers + TWRP 3.2.3-0 recovery + Magisk 21.1 + wifi-fix-semcosh).
Unzip files.
+ ROM LineageOS 16 Unofficial: https://forum.xda-developers.com/t/rom-unofficial-9-0-0-lineageos-16-0-beta-20-09-2020.3875899/
Download (select latest build): https://androidfilehost.com/?fid=8889791610682941485
Or LineageOS 14.1: https://github.com/Mibo5354/i9300_builds/releases
+ OpenGApps ARM 9 pico: https://opengapps.org/?arch=arm&api=9.0&variant=pico
+ a microSD card. Copy ROM, Gapps, Magisk + wifi-fix-semcosh on microSD card (FAT32 format) and insert it in phone.
+ Charge phone to 100 %
2) BACKUP DATA
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use apps like Backupyourmobile ans SMS Backup & Restore to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
3) FLASH TWRP 3.2 RECOVERY
Shut down phone.
Remove back cover.
Boot in Download Mode : hold Home + Power + Volume- for 3 seconds and release.
Confirm with Volume+.
Connect phone in USB, wait for bootloader drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify Auto Reboot and Re-Partition are NOT ticked while F. Reset Time is ticked.
On right panel > AP > select twrp-3.2.3-0-i9300.img.tar
### Don't use other menus like BL, CP or CSC (I desactivated them but we never know).
### Warranty will be Void after next click ###
Click Start.
Power Off phone when PASS! green message appears.
### If Odin is stuck at Initializing step (Odin fails to flash TWRP) : use a different usb port AND cable and try again > reinstall Samsung USB drivers > uninstall Samsung Kies > use a different version of Odin > use a different PC.
Wait a few seconds, then unplug phone and remove battery.
4) BACKUP IMEI PARTITION AND PARTITIONS (NANDROID BACKUP)
Insert battery and boot in Recovery Mode : Hold Home + Power + Volume+ until you see the Samsung logo then release and wait a few seconds for TWRP recovery to boot.
If it asks for Keep System Read Only ? -> Swipe to Allow Modifications.
Go to Backup > you can select the partitions you want to save.
Select at least EFS partition to backup your IMEI. If a flash fails and partition is damaged you will still be able to restore this partition and use the phone.
If IMEI is lost during a flash, phone won't be able to reach cellphone networks.
I prefer to backup EFS, Boot, Data and System.
Now type Select Storage > Select Micro SD card and confirm with OK
Now Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
5) WIPE PARTITIONS
Go to Wipe > Format Data
Type yes and confirm with bottom right Check icon.
Then go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup from step 2), then Swipe to Wipe,
then back.
Go back to TWRP Home screen > Reboot > Recovery and Swipe to confirm.
At reboot, if TWRP asks for Keep System Read Only ? > Swipe to Allow Modifications.
6) FLASH ROM, GAPPS, WIFI-FIX
Back to TWRP Home menu. Then tap on Install > choose LOS*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > open_gapps*.zip,
then Add more Zips > wifi-fix-semcosh.zip,
then Swipe to confirm Flash.
Wait for operation to end.
Tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 10 minutes.
6) ROOT ACCESS
Configure Android.
Then shutdown phone.
Boot in recovery mode: Hold Power + Home + Volume+ until Samsung logo is displayed and release buttons.
Go to Install > select Magisk.
Swipe to flash then reboot System.
No extra steps for root. Magisk starts with Android.
Open Magisk Manager app to manage root permissions.
8) EXTRA
You can use GPS Status & Toolbox app for faster GPS fix.
For faster phone, go to Settings > About.
Tap 7 times on Build number.
Now go to Settings > System > Avdanced > Developer options.
Set Windows animation scale, Transition animation scale and Animator duration scale to 0.5x.
Still in Developer options, set Default USB configuration to File transfer.
For better battery use Dark mode.
Go to Settings > Display > Style > Style > Dark.
You can chose between Dark mode Default or Black right below.
Enjoy,
djibe
Thanks : SparXFusion, @rINanDO, @ChronoMonochrome, @pascua28, @ciyanogen, @hgunduz295, @theandroid02, @ComicoX, @side
Team InFusion, JDC Team, LineageOS team, TWRP team
Next version will allow you to increase available size on your Galaxy S3. See you soon
Hi guys, whole new tuto is released for enhenced flashing experience.
Hi guys, do you think LOS 15 is stable enough to use it in this tutorial ?
Ooops, didn't even think LOS15 wouldn't be available for this top phone !
Too bad
Refreshed pack for latest recovery and kernel.
Enjoy
Pack updated for State of the Art flashing.
Hybrid kernel v13 is in my pack, if you are looking for it everywhere ...
Is it necessary to flash the Hybrid Kernel? Or can I use the stock kernel?
bsetiawan said:
Is it necessary to flash the Hybrid Kernel? Or can I use the stock kernel?
Click to expand...
Click to collapse
You can keep stock kernel. No pb.
djibe89 said:
You can keep stock kernel. No pb.
Click to expand...
Click to collapse
Thank you for the confirmation.
Updated tuto if you want to test Android 9.
Updated downlaod link.
Updated download link for june build.
Updated tutorial for Android 9, Wifi fix and Dark mode
Op
Is there a way to get the phone back to jellybean 4.3 after completing this tutorial?
Spudgun22005 said:
Is there a way to get the phone back to jellybean after completing this tutorial?
Click to expand...
Click to collapse
Hi, you can find your ROM there: https://www.sammobile.com/samsung/galaxy-s-iii/firmware/#GT-I9300
ROM download link dead
MLX said:
ROM download link dead
Click to expand...
Click to collapse
Hi, sorry for that.
You may try newer ROM there: https://forum.xda-developers.com/f/galaxy-s-iii-android-development.1566/
Finally ported TWRP to the Medion Lifetab P10505 with working touch.
No guarantees are given, if you damage your tablet, all you do is on your own risk. I have the original ROM from Medion, if you need a full restore.
Please note that the TWRP recovery was not much tested and may be buggy. I didn't test with encryption or the restore process.
Please follow these steps:
1. Download all the files from Mega:
https://mega.nz/#F!pvQCQCxL!dfCHhGkliNSj-Wd3NcRV2ghttp://
2. Unpack all files into the same directory
3. If not done already, install the Intel Driver Package and reboot your PC
4. Unpack the ADB Tools into the directory
5. On your tablet go to your settings and enable USB debugging in the developer options. If you don't see the developer options menu under settings, goto about tablet and tip the build number seven times fast which will reveal the Developer options in the Settings.
6. Copy the file UPDATE-SuperSU.zip to your tablet (via USB or to memory card)
7. Switch off your tablet
8. Press and keep pressed the On/Off button and Volume Down button until you see the bootloader menu. Please press the buttons at the same time.
9. Now connect the table via USB cable to the PC.
10. Open a command window on your PC and change to the above created directory .
11. type the command: fastboot oem unlock (you can lock it again after the whole process if you want)
If this doesn't work goto the below section: Install recovery through flash
12. next type: fastboot flash recovery final_P10505_working_TWRP_3.0.2.0.img
13. Use the volume up or down button until Recovery mode is displayed.
14. Press the On/Off button shortly to start the new TWRP recovery menu. Please be patient until it fully loads. May take a couple of minutes.
15. Now choose install from the menu.
16. Proceed to the folder where you store the UPDATE-SuperSU.zip and select the file and swipe to install.
Note: If you forgot to copy the file to the tablet you can use the windows explorer to copy it to your tablet. There is a new device called Vi10 plus
(as mentioned it is only a port not build from source)
17. The Zip file should install
18. Use the back button to go back to the main menu of the recovery and select reboot and then system.
19. Now you have rooted the device and can create backups in the TWRP recovery.
20. To verify use any root checker tool from play store.
21. Feel free to hit the Thanks button
Install recovery through flash:
If there are any errors you can download the original ROM from Medion.de. You need then the Intel Platform Flash Tool Lite to install the ROM from Scratch (all your data will be lost).
When you run the flash tool, open the file from Medion.de and it will unpack the zip-file in the folder C:\Users\Your account name\.flasher\.download\p1050x-6.0-factory-v2.3
Proceed to the folder Just rename the file final_P10505_working_TWRP_3.0.2.0.img to recovery.img and replace the original file from Medion. Then hit the flash button.
Actually the Intel tool will perform the same command as above.
PS: I read that P10506 is hardware like the same as P10505, so it may work there as well, but no guarantees.
PPS: Credit go to the creators of the TWRP file for the Chuwi Vi10 plus (Highbook), which I don't know their names.
thank you for this, I used it on my P10506, the only difference was thead the command in section 12 has changed to:
fastboot flashing unlock
Cooool!
Did everything on my P10506.
Now waiting untill booting is finished...... CHECK!!
Testing with a root checker........ CHECK!!
That is great!
Thank you!
simplex3 said:
Did everything on my P10506.
Now waiting untill booting is finished...... CHECK!!
Testing with a root checker........ CHECK!!
That is great!
Thank you!
Click to expand...
Click to collapse
You're welcome,
but surely room for optimization of this tablet. On mine it happens after quite some that it becomes very laggy.
Hope yours is running better.
Bernie_W said:
You're welcome,
but surely room for optimization of this tablet. On mine it happens after quite some that it becomes very laggy.
Hope yours is running better.
Click to expand...
Click to collapse
Seems to work fine.
No lags. Okay, not more laggy then it was before rooting.
But now i'd like to flash a custom rom... Any suggestions?
Regards.
simplex3 said:
Seems to work fine.
No lags. Okay, not more laggy then it was before rooting.
But now i'd like to flash a custom rom... Any suggestions?
Regards.
Click to expand...
Click to collapse
I haven't seen any custom roms for this tablet, but I actually didn't look much. The problem is that it is nearly impossible without sources to create one.
any new mirrors available? mega zip file offline...
P10506
Thanks for the wonderful news! If anyone (Bernie?) could make the files / TWRP image available again, they'd make me and the previous poster even happier
Looking to root and TWRP my familys two P10506s - one still on 5.1 - should I update it to 7.1.1 (last available image from Medion) first?
Download Link
Somebody here who have the files available and can upload it again?
Would be great.
Thanks
Bye
Amy New version for P10506? My tablet Constantly crasing on original software
Asciola said:
P10506
Thanks for the wonderful news! If anyone (Bernie?) could make the files / TWRP image available again, they'd make me and the previous poster even happier
Looking to root and TWRP my familys two P10506s - one still on 5.1 - should I update it to 7.1.1 (last available image from Medion) first?
Click to expand...
Click to collapse
Maybe you can flash android x86.
1,Flash tw08a-87z8 bios using flashrom in ubuntu.
2,Push esc key to enter bios.
3,Install android ,linux or windows using usb/sd boot.
Some medion and onkyo tablets are compatible.
I have written more details on my wiki.
TA2C-74Z8 - SmileTabLabo
Onkyo TA2C-74Z8はODS株式会社製造のAndroidタブレット。スペック 型番 TA2C-74Z8 製造元 オーディーエス株式会社 CPU Intel Atom Z8350 G...
wiki3.jp
Rebrand-Update-Tool HWOTA7 for Huawei P9-Plus-VIE
The classic HWOTA Tool is available for all newer Huawei models. Now it is also available for the P9-PLUS-VIE
→ It is programmed for use with Android 7 (Nougat) and does not work on Android 8 (Oreo) - with the exception of the Update to Oreo.
Don't use this Tool to update your phone from Android 6 to Android 7 or Android 8.
You must already have Android 7 on your phone.!
Update to Oreo from Nougat is possible, but once you're on Oreo, the tool can not be used again until downgraded to nougat.
→ The same Tool for P9-EVA is different: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Features of HWOTA7 for P9 Plus VIE:
Update your Firmware with FullOTA-MF Firmware (3 zip files, two renamed) = Using the script /1. Change firmware
Rebrand between L09-L29-AL10 (your hardware does not change on VIE) = Using the script /2. Change location
Debrand from Vodafone, Telekom or other to: open cust ( current: 5 oeminfo files)
Note: If your Phone has SIM Lock, Debranding does not unlock mobile network - you can do that with HCU Client by DC Unlocker
The best feature is: You can update the P9-Plus-VIE to the official Android 8 (Oreo) unofficially with HWOTA7. This requires a rebranding of your device to VIE-AL10. How to manage this is explained in Post #2: https://forum.xda-developers.com/showpost.php?p=77650678&postcount=2
→ How to get back to the original model from Oreo is explained in Post # 4: https://forum.xda-developers.com/showpost.php?p=77650687&postcount=4
Note: To return to the original model related oeminfo is required - should your oeminfo not be included in the HWOTA7 tool, make a backup of the oeminfo with TWRP before Rebranding. If you give it to me, I can integrate it into the tool.
Requirements:
Bootloader Unlock code → if you do not have it, it can be read out with HCU Client by DC Unlocker
Developer Options enabled → OEM Unlock + ADB Debugging in charging only mode + USB Debugging (in this order) enabled
HiSuite HDB in Settings on the phone disabled, HiSuite on PC closed
Working USB Connection (drivers) between P9 Plus and PC (MTP, ADB and Fastboot → Allow access to the phone, accept RSA key fingerprint)
Windows 7, 8.1, 10 (the tool does not work on Mac or Linux or on Virtual machine)
Battery should be charged
Backup your important data (folders from internal storage such as WhatsApp, DCIM, downloads, music, etc. - as well as user apps with data, contacts, calendars, sms, etc.) → The internal storage is erased several times during this process.
Follow the instructions
How HWOTA7 works and what to keep in mind:
Download HWOTA7, extract it on PC and place HWOTA7 on: C:\HWOTA7 - without subfolders between.
Do not change the folder structure. The tool has two working folders:
→ C:\HWOTA7\tools\Windows - you can use: cmd-here.exe (run as Administrator) to check ADB/Fastboot or to flash an image later
→ C:\HWOTA7\update - this is the main working folder. You have to copy in this folder the FullOTA-MF firmware (3 zip files, two renamed)
If you are on custom ROM, first go back to Stock Firmware ("Using script" and "Change firmware" - use the Firmware that matches your device and cust)
HWOTA7 is self-explanatory. It detects what to do and prompts you to press certain key combinations or enter the unlock code.
→ The USB cable between the phone and PC remains connected throughout the process!
→ Only press "Enter" in the terminal if the described step, in the line before, was executed.
→ If you face an error like: "adb: error: connect failed: no devices/emulators found" - close Terminal, reboot phone into Fastboot mode and restart HWOTA7
The HWOTA7 tool is started by double clicking on "update_eng.bat"
The phone is connected to the PC via USB and you start with the key combination: VOL- and Power Button key into Fastboot mode.
When the Bootloader is locked, the tool unlocks the Bootloader with the code. Thereafter, a factory reset is performed by clearing the internal storage = Lowlevel Wipe.
When the Bootloader is open, the tool automatically flashes TWRP and prompts you to press (and hold) VOL+ and Power Button to start into TWRP.
Then you click 2x in the terminal on "Enter"
→ Before you choose: 2. Using the script and 1. Change firmware or 2. Change location - make sure, the FullOTA-MF Firmware is already in the update folder: C:\HWOTA7\update - and two zip files are renamed!
Rename the two zip files of the FullOTA-MF firmware → incorrect renaming such as "update_all_hw.zip.zip" does not work
update.zip = update.zip (do not rename)
update_full_VIE-AL10_all_cn.zip -rename to: update_all_hw.zip
update_data_full_public.zip - rename to: update_data_public.zip
Important - The difference between four different situations:
1) When the Bootloader is closed, HWOTA7 opens it with the code, a "lowlevel" factory reset is performed and the device must then boot into the system. In the setup everything can be skipped (which is possible) - but the developer options must be switched on (1.ADB Debugging + 2.USB Debugging enabled). And HiSuite HDB disabled.
2) If you select "Change firmware" to flash the firmware, the tool copies the ZIP files to the phone in the /data directory, flashes the Nocheck recovery, and installs the firmware. In this case, you also need to boot into the system and check if Developer options with the required settings are enabled.
3) But if you do the step: "Change location" - it is different! The tool will flash the corresponding "oeminfo", close the Bootloader and request the Unlock code to unlock the device and force a "lowlevel" factory reset → In this case (only), you should NOT boot into the system after the reset. Wait until the EMUI recovery is 100% done with the reset. Then comes the message "Reset succesful, device will restart" Now press (only) the VOL+ button and keep it pressed so that the device starts into TWRP. Now click on "Enter" in the terminal. HWOTA7 now copies the firmware to the device, flashes the Nocheck recovery, reboots and flashes the firmware belonging to the "oeminfo". After this step, the device must be booted into the system.
4) If the device boots into the system and you have a black screen, with an input field in the middle and possibly the keyboard (do not get worried) - the Bootloader was locked by the firmware during rebranding. In this case, press the Power Button to restart and hold down the VOL- button during the restart to start the device into Fastboot mode. Close the Terminal Script and restart update_eng.bat. Click on "Enter" in the Terminal and HWOTA7 will ask you for the Unlock Code and unlock again the Bootloader. Confirm the unlock on the device with the keys, then there is a factory reset followed by a reboot into the system. Now everything is fine.
Where can I get the firmware I need?
Note: The firmware must match your device and your "cust" - if you want to update, or coming back from a Custom ROM to Stock firmware - If you do a "rebranding", the firmware must match the "oeminfo" that you "rebrand"
Install "Firmware Finder" from the Playstore
In Settings (3 dot menu/settings) change to "Show only FullOTA" In main window "Add model" Example: VIE-L09C432. Click on FullOTA-MF Firmware (that matches) and "Check Firmware Access" and "Check Availability" If it says: "The firmware is not approved for installation" - I would not recommend . If it shows: "Firmware approved for installation Models VIE-Lxx" (and it matches your device/cust or the cust you want to rebrand)- click on Download.
Tip: If you enable in Developer Options "Keep phone awake during USB charging" you make sure, the Download get not corupted. Additional I would try to open the zip file after Download in a zip viewer to check if the zip file is complete.
The other possibility is, download the zip files to PC instead on the phone. Finally, it is needed on the PC and needs to be copied to the C:\HWOTA7\update
If you click in Firmware Finder on Download you will see 4 zip files - but you need only 3 of them: update.zip, update_data_full_public.zip and the third file must match your device (which you like to update or rebrand to) When you see the 4 files, choose the 3 files you need.
When you click on "Share Firmware" - then you can store the Links in a txt file. In this case you can download the files on PC. When you click instead "ok" Firmware Finder will download the Firmware to the Phone.
Alternatively you can use the Direct Link on PC:
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
Enter the correct model name and cust (Example: VIE-L09c432) and press enter. Choose only FullOTA-MF. Click on FILELIST and wait until a new Window pops up with the Links you need for Download. However, here you dont see if the Firmware is approved for installation.
The Third possibility - Firmware Finder for PC:
http://pro-teammt.ru/projects/hwff/v2/GetLatestVersion.action
Unzip it and double click on FirmwareFinder.exe. Click on "Common Base" and enter your model name with cust. Search on "Type" for FullOTA-MF and click on FILELIST. After you can copy with right click on changelog and above in the symbol "check availability" you can check, if the Firmware is approved (even with your IMEI, if you like)...
→ In the second post there is a step by step guide to rebrand the P9 Plus VIE to VIE-AL10 (including the links) and update to Android 8 Oreo.
Download P9PlusVIE-HWOTA7:
https://www.androidfilehost.com/?fid=1322778262904007988
MD5: 1edc0c8aedbf3f3470fb419dc67d7c26
→ Extract the zip on your PC, the zip contains the folder: HWOTA7 - Copy the folder to C:\ = C:\HWOTA7
Have fun
Credits:
@Atarii VIE-NoCheck Recovery
@OldDroid Android 7 TWRPs for many Huawei devices, Lead Developer/Maintainer Open Kirin Team
@Pretoriano80 Android 8 TWRP for many Huawei devices
@urbanmec Huawei Tweak Professor
XDA:DevDB Information
Rebrand-Update-Tool-HWOTA7-P9-PLUS-VIE, Tool/Utility for the Huawei P9 Plus
Contributors
Tecalote
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-09-18
Created 2018-09-18
Last Updated 2018-09-18
Update Huawei P9 Plus VIE to official Android 8 Oreo
Unofficial method to update European models of Huawei P9 Plus VIE to official Android 8 Oreo
- for VIE-L09 and VIE-L29
Originally, all models of the P9 Plus VIE and P9 EVA should receive the Android Oreo update. Unfortunately, Huawei has decided to only supply the Chinese models with Android 8.
For this reason, there is an unofficial way to update to the official Oreo → by rebranding the European models to VIE-AL10.
Note: This Guide is for P9 Plus VIE → (P9-EVA HWOTA7 with Update Guide to Oreo you can find here: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849)
Oreo runs smoothly and well on P9 Plus, the battery last longer and with Android 8 there is Treble Support.
Since it is possible to update P9 Plus to Oreo - Huawei P9 VIE is officially supported by the OpenKirin Team :https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
See OpenKirin supported devices: https://openkirin.net/devices/
Here is a small Guide how to go back from OpenKirin ROM to EMUI: https://forum.xda-developers.com/showpost.php?p=77905152&postcount=833
Preparation for the update to Oreo:
If you are on any Custom Rom - go back to Stock firmware first - before rebrand to another location!
You should be on the latest approved Firmware for your device - if you have not the latest approved Firmware, use HWOTA7 Tool to update your Firmware.
Do for every case a Backup (TitaniumBackup /Huawei Backup - without System-Apps/Settings) before. TWRP Backup makes no sence, because you can not restore it on Oreo! Make sure, the Update-Firmware is copied to the folder C:\HWOTA7\update - and two zip files are RENAMED as mentioned in OP → read OP Post#1. Update your Firmware by using the script (HWOTA7 Terminal: 2. Using the script + 1. Change firmware)
Instructions for updating to Oreo by rebranding your phone to VIE-AL10:
Requirements:
A) HWOTA7 Tool
B) Bootloader Unlock Code for your device
C) Micro SD Card → formatted as exFAT
D) For rebranding from VIE-L09 or VIE-L29 to → VIE-AL10 you need to download the following 2 Firmwares:
A) VIE-AL10c00b399SP20 /Android 7 (this Firmware is required for the Update to Oreo):
update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1891/g1755/v139083/f1/full/update.zip
update_full_VIE-AL10_all_cn.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1891/g1755/v139083/f1/full/VIE-AL10_all_cn/update_full_VIE-AL10_all_cn.zip
update_data_full_public.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1891/g1755/v139083/f1/full/public/update_data_full_public.zip
B) VIE-AL10C00B537 (8.0.0.537) OREO
update.zip:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/update.zip
update_full_VIE-AL10_all_cn.zip:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/VIE-AL10_all_cn/update_full_VIE-AL10_all_cn.zip
update_data_full_public.zip:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/public/update_data_full_public.zip
→ rename for each Firmware two zip files as described in OP (Post #1)
Step-by-step:
0) Developer Options enabled (7x click on Build-Number in Settings /About phone) - In Developer Options: OEM Unlock, ADB Debugging + USB Debugging (in this order) enabled, HiSuite HDB (in Settings /Adv.Settings /Security) disabled, HiSuite on PC closed, working USB Connection
1) Connect your device with USB to PC and start from HWOTA7 main folder: update_eng.bat - Accept possibly the RSA query on the display of the P9 Plus
2) Restart your P9 Plus into Fastboot mode (use restart/restart and press VOL- /or shutdown phone and press VOL- and Power Button)
→ Note: During all steps USB Cable stays connected between phone and PC and you only press "Enter" in the terminal when the described step, in the line before, was executed.
3) HWOTA7-terminal detects if Bootloader is open or closed - if the Bootloader is closed go to 4) - if the Bootloaer is open go to 7)
4) Terminal ask you for the Unlock code - enter the Unlock code and confirm the Unlock on the phone
5) Your P9 Plus reboots and an automatic factory reset is done with internal storage wipe (lowlevel reset) - wait until the phone reboot to system. Skip everything during setup (except what can not be skipped) - Important: Enable Developer Options with ADB Debugging and USB Debugging
6) Restart your P9 Plus into Fastboot mode - now hit "Enter" Button - HWOTA7 Terminal will flash automatically TWRP for Android 7 and gives you the order to boot into TWRP by pressing VOL+ and Power Button (dont hit "enter" before this step is done)
7) In TWRP swipe to allow system modification - now hit "enter" (2x) in the Terminal - after a short while you will see: Upgrade Options
8) 2. Using script: 2.Change location - you will see a list of available "oeminfo" - use: 1.VIE-AL10c00
→ Note: The Firmware for VIE-AL10c00b399SP20 (Nougat) must be already in the update folder (and two zip files renamed)!
9) HWOTA7 flashes now oeminfo for VIE-AL10, Bootloader is getting closed, confirm the Unlock on device - automatic factory reset is executed, wait until 99% and 100% restarts the phone → NOW PRESS VOL+ to boot the phone into TWRP instead of system!
10) Allow system modification in TWRP and hit "Enter" Button for Terminal - HWOTA7 copies now the firmware to the directory: /data/update/HWOTA - phone will restart automatically and flashes the Firmware with NoCheck EMUI Recovery.
→ After your P9 Plus has started into the system - you may see a black screen with an input field and a keyboard - if yes, go to 11) - if no, go to 13)
11) Close HWOTA7 Terminal and press Power Button on P9 Plus to restart your Phone, restart phone, in the moment of restart press VOL- Button to boot into Fastboot Mode → Bootloader is closed. BTW: Chinese Brands dont have FRP.
12) Open update_eng.bat, click enter, enter the Unlock code, confirm Unlock on phone, phone makes a Factory reset with lowlevel wipe. Then the P9 Plus starts automatically into the system. Now you have already rebranded to VIE-AL10c00b399SP20 (Nougat) :good:
13) Accept the terms and conditions (Huawei + Google Services) and skip the rest, what can be skipped. Do not be nervous, your P9 Plus has no IMEI at the moment and no mobile network. This is normal. In the settings in the search bar, search for "Trust Space" and "HiSuite HDB" - disable both. Enable again Developer Options and inside: ADB Debugging and USB Debugging (in this order).
14) Click enter in Terminal, select 2. "No, I would not" and HWOTA7 will be closed. → Change now the Firmware in the update folder to: VIE-AL10C00B537 (8.0.0.537) OREO (remember: two zip files has to be renamed!)
15) Start again update_eng.bat. Reboot phone into Fastbood Mode. Hit "enter" for Terminal - TWRP will be flashed automatically - reboot with VOL+ and Power Button into TWRP - allow system modification - hit "enter" in HWOTA7 Terminal
16) Use Upgrade options: 2.Using the script - 1.Change firmware (Same brand update /but Oreo)
17) Click enter in Terminal, Firmware will be copied to: /data/update/HWOTA - "System update should start automatically" → if you receive any error like: "connect failed, no devices/emulators found" - go to 18) - if everything is okay go to 19)
18) Close HWOTA7 Terminal and use menu of TWRP to reboot into Bootloader, start again update_eng.bat - TWRP will be flashed again - boot into TWRP with VOL+ and Power Button - allow system modification - hit "enter" in HWOTA7 Terminal - Firmware will be copied to: /data/update/HWOTA - Phone will make reboot and flash the Firmware for Oreo automatically.
19) You have now successfully updated to Android 8. :good: Phone will reboot into VIE-AL10C00B537 (8.0.0.537) OREO
→ You should accept the terms and conditions (Huawei + Google Services) - otherwise Playstore will not work later! Do not enable WLAN and do not set up your phone (Fingerprint etc)right now! - skip, what can be skipped. → You will have "unknown IMEI" and no mobile network at the moment, that is normal. Open Settings/System and enable again Developer Options/ADB+USB Debugging. In Settings /Security+Privacy you can find "Trust Space" - disable it - and in same menu you find in "More" "Allow HiSuite to use HDB" - disable it! → Now we must help the phone to recognize the IMEI and enable mobile network and NFC on VIE-L09 and Dual-SIM on VIE-L29 as well as disable Chinese apps, which we do not need in Europe (and some of them would not work here)
20) Downloads:
TWRP for OREO: P9-VIE_EVA-8.0.0-TWRP-v4.img https://www.androidfilehost.com/?fid=1322778262904008816 - we need this to flash the important changes to system without the need of Root!
This TWRP is made by @Pretoriano80 for Honor 9 Lite. I made just small changes for assert hi3650. You can backup and restore everything, except data! There is no access to /data - means: you can not do Factoryreset from TWRP - and decryption of the internal storage for the TWRP session is not working. → For Backkup and restore data you can use HiSuite or Huawei Backup or Titanium Backup. MTP ist working, when you just disable/enable it once.
Network-Patch zip files (new released 03.03.2019):
→ select the zip according to your original model (which you had before rebranding to VIE-AL10)
→ Copy the zip file to the external SD or to the USB Stick, which you connect to P9 Plus after with OTG cable. Since TWRP can currently not access /data (internal storage) - you can not flash this Patches without → external SD or USB OTG
→ The Network Patch zip files can be used for b537. If you are already on Oreo and have an older Firmware (b528, b535), you must update first to b537.
→ Update from older Oreo Firmware to b537: see Post #5
VIE-L09_b537-SingleSIM_NetworkPatch-v2.5.zip: https://www.androidfilehost.com/?fid=1395089523397898649
MD5: c22b40706584852ee1b1873fc7c28e54
VIE-L29_b537-DUAL-SIM_NetworkPatch-v2.5.zip: https://www.androidfilehost.com/?fid=1395089523397898655
MD5: 9f8f5df0f8abfe5afe49097b6bc6c4d3
VIE-EVA-FaceUnlock-Oreo-v1.5.zip: https://www.androidfilehost.com/?fid=1395089523397898647
MD5: 973d006c55fa812d722b653a57c844c0
21) Copy the downloaded TWRP (from STEP 20) into the folder C:\HWOTA7\tools\Windows - connect P9 Plus with USB to PC - right click on cmd-here-exe (run as administrator) - type: adb reboot bootloader (enter, to restart your P9 Plus into Fastboot mode)
Code:
fastboot flash recovery_ramdisk P9-VIE_EVA-8.0.0-TWRP-v4.img
22) Disconnect the USB cable from P9 Plus and press (with the left hand) VOL+ and Power Button (with the right hand) and keep pressing until the Phone is rebooted into TWRP.
23) On the first Screen click on "Cancle" (because decryption is not working for now) but swipe to confirm to "Allow System modification"
→ Go to: Install /select storage: Micro SD (or USB-OTG) and flash the downloaded NetworkPatch.zip file. If you like, you can use the function down left "Add zip file" and choose the VIE-EVA-FaceUnlock-Oreo-v1.5.zip
24) Swipe to confirm flashing the Network Patch (and the optional added VIE-EVA-FaceUnlock-Oreo-v1.5.zip file)
25) If you had used an older NetworkPatch before flashing the newest one - go back to the main menu of TWRP, go to wipe → advanced wipe and choose only "cache" (not Dalvik) → but if you are new on Oreo b537 you can skip this step
26) Reboot to the system
27) Finally, Playstore and any keyboard is needed. Download the apks from here (February 2019): https://www.androidfilehost.com/?w=files&flid=290472
28) Install it, enable keyboard, open Playstore and log into your account. After that reboot your phone. Now you can update apps, download and install your favorite apps and additional all other Google apps from Playstore → do not flash GApps instead!
29) After you have installed all required files, you have currently TWRP installed → this is good for Users, which like to have Root and disabled OTA.
Root Guide can be found here: LINK WILL COME SOON
→ But if you like to enable OTA instead:
A) Download and flash: Enable-Hwota.zip from here: https://www.androidfilehost.com/?w=files&flid=290480
B) Go back to the main menu of TWRP and Reboot to Bootlader
C) flash in Fastboot mode the Stock EMUI Recovery
Code:
fastboot flash recovery_ramdisk VIE-b537-EMUI-RECOVERY_RAMDIS.img
Download from here: https://www.androidfilehost.com/?fid=1395089523397898696
Reboot Phone and enjoy
If you search for older files (Network Patches etc) for older Firmwares, you can also search my folder on Android Filehost:
https://androidfilehost.com/user/?w=settings-dev-files&flid=131030
Note: It is not possible to lock the Bootloader on to VIE-AL10 rebranded phone with Network Patch and FaceUnlock! This would revert all the required changes and in the worst case push your phone into a bricked state.
→ But what you can do with installed EMUI Recovery (instead of TWRP): You can do from settings /system /reset a Factoryreset with wipe of the internal storage (to clean up previous instalations) → in this case the Factoryreset lowlevel does not revert the changes! The only difference is: When you get Push notifications, the Badges over the app symbol on Homescreen will change from numbers to points (which is standard on Oreo) → which is currently not change able in settings without Factoryreset.
Known issues:
VoLTE and WiFi-Calling is is visible in the menu - but does not work for now!
If you want synchronisation between Google calendar and EMUI calendar - you need to install Google calendar from Playstore.
If you like to use Google Assistant and have problems to teach this app with your voice "Hello Google" - just open settings /apps & notifications /standard (default) apps - and choose Google Assistant as default app (then it will work).
→ Please read also the next few posts (Root, current firmware with eRecovery, Update Firmware on Oreo with HWOTA8, going back to EVA-AL10 Nougat and rebrand back to original model)
→ Currently working to update this posts (will be ready soon).
Instructions for root
Instructions for root access
Root is not required, but if you still wish, here is the guide:
Due to the fact TWRP cannot access the encrypted data partition, you cannot JUST flash Magisk!!
→ A) But you can flash Magisk with TWRP using a workaround
→ B) Alternatively it is possible to flash a Magisk patched ramdisk.img in Fastboot mode
A) Workaround for flashing Magisk with TWRP – for Advanced Users:
1) Download the favorite Magisk version from here (all releases): https://github.com/topjohnwu/Magisk/releases
The actual and newest stable version you can get always from here too: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2) Copy the flashable Magisk-vXX.zip and Magisk Manager apk to external SD – and make sure, you have Developer options with 1) ADB Debugging and 2) USB Debugging (in this order) enabled.
3) Reboot device to TWRP, cancle Password, allow system-modification (swipe to confirm)
4) On the main menu go first to "Mount" - down left click on "Select storage" and choose "Micro SD"
5) Go back to main menu and open "Advanced" and open "Terminal"
NOTE:
If you have got a OTA-Firmware Update with “Patch02” or “Patch01” before flashing the Network Patch (after Network Patch, you will not see this in "About phone"!) or if you don’t remember, then use following both Lines in Terminal, but if you are sure, you have only Firmware without Patch 01 or Patch02, then use just "Keep Force encrypt" Line. Write the Lines in TWRP/Terminal exactly.
6) Write following code with Terminal:
Code:
echo KEEPVERITY=true>>/cache/.magisk
echo KEEPFORCEENCRYPT=true>>/cache/.magisk
→ Confirm each Line with blue/white checkmark on keyboard, before writing the next Line and confirm also the second Line (if you use two)
7) Go back to the main menu to "Install" and flash Magisk - after that reboot phone without wipe of Dalvik/Cache!
8) Search for Magisk Manager on Homescreen - if it is not installed, just install the Magisk Manager apk
9) Open Magisk Manager → everything should be okay
10) Open normal settings /apps & notifications /Magisk Manager /permissions and make sure Magisk Manager has permission for storage.
11) From Magisk Manager menu above left, section “Downloads” – download and install directly “Busybox for Android NDK” by osmosis – save log and reboot phone.
→ If Magisk get a major update, uninstall first Magisk from Magisk Manager and use “uninstall” button. “Uninstall complete” The phone restarts automatically. After that you can flash the new Magisk and reflash the modules.
B) Flashing Magisk with patched ramdisk.img in Fastboot mode:
If you don’t want flash Magisk with the TWRP workaround – you can use a Magisk patched ramdisk.img instead.
1) You can patch ramdiks.img from update.app by yourself, with following method:
Extract the update.zip of the current installed Firmware, because we need the UPDATE.APP.
Download Huawei Extractor v0.9.9.5 from here: https://forum.xda-developers.com/showthread.php?t=2433454
In the settings of the Huawei Extractor disable "verify header checksum" - then put with drag and drop the UDPATE.APP into Huawei Extractor and extract by right click the RAMDISK.img (on earlier Android Versions it would be: BOOT.img)
2) Copy the original RAMDISK.img to your phone to the internal storage in the folder: Download
3) Install the latest Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4) Open Magisk Manager, Magisk Manager ask you "Install Magisk-vx.zip?" - first click on: no thanks
5) Since internal storage is encrypted by default, you must first enable the checkbox: "Preserve force encryption"
5) If you have installed a OTA-Firmware Update with Patch01 or Patch02 – then enable additional the checkbox "Preserve AVB 2.0/dm-verity" in Magisk Manager.
6) Then click on "Install" - "You want to install Magisk-v1x.zip now?" - Install - Patch Boot Image File...
7) Navigate to Download folder, and choose RAMDISK.img
8) Magisk will now patch the RAMDISK.img and and once that's done, Magisk will save the patched ramdisk.img with the new name: patched_boot.img in the "Download" folder on internal storage.
→ Do not be confused - this is just named “patched_boot.img, but it is in fact the patched ramdisk.img !
9) Go to Settings /Apps & notifications/Apps and uninstall Magisk Manager
10) Now you must flash the “patched_boot.img” – Reboot your phone into Fastboot mode
Android 8:
Code:
fastboot flash ramdisk patched_boot.img
10) Reboot phone, install again newest Magisk Manager, open it and you will be asked: "Requires Additional setup - to you want to proceed now" Yes. → This step is required for to work properly.
Google Playstore certification
You can try it with method by @zgfg:
https://forum.xda-developers.com/showpost.php?p=79070144&postcount=1574
→ If it does not work you can try advanced method:
1) Set your phone into Flight Mode (no network should be connected)
2) Open Settings/Apps & notification/Apps and down right in the dot menu click on: show systemprocessing
3) Go step by step into following Apps (if there): Google - Google Play Store - Google Play Services - Google-Service-Framework - each has the entry: storage - delete ONLY cache /not data
4) Open with Mixplorer the directory:
/data/data/com.android.vending/shared_prefs - search for the xml file: finsky.xml
5) Open finsky.xml with TEXT Mixplorer Text Editor
6) Search inside finsky.xml for: <boolean name="device-google-certified"value="false" - change it to:
Code:
<boolean name="device-google-certified"value="true"
- means, you change only "false" to: "true"
7) click on the save symbol to save the changes! - close Mixplorer and everything in the Background
8) Disable Flight Mode (so Phone search for network connections)
9) Reboot your Phone
10) Open Playstore menu /settings/ =certified
If you have problems with current version of Magisk and using Gpay (Google Pay), try following workaround:
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
How to uninstall Magisk:
A) Before you doing an OTA Update, it is required to uninstall Magisk → and also make sure, to have Stock EMUI Recovery installed (instead of TWRP).
B) In case for a “major” Magisk update it is also sometimes necessary to uninstall Magisk before installing the new version, because with directly update the phone could get a Bootloop. (But normally Magisk updates can be done directly and without uninstalling Magisk before).
C) If your device can not boot into system due to an incompatible Magisk Module.
a + b) If you can boot normally to system, you can uninstall Magisk from Magisk Manager - just use the "Uninstall" button “Uninstall complete”. Magisk will be uninstalled and Magisk files deleted from /data directory. Thereafter, the P9 is restarted automatically.
c) If your device can not boot into system due to an incompatible Magisk Module, you can flash the original EMUI Stock ramdisk.img (which is not patched with Magisk)
→ ramdisk.img must match the Firmware version of your device
For the current Firmware VIE-AL10 b537 you can download the original ramdisk.img here:
VIE-b537-RAMDISK.img:
https://www.androidfilehost.com/?fid=1395089523397898698
You can flash it in Fastboot Mode:
Code:
fastboot flash ramdisk VIE-b537-RAMDISK.img
Alternatively, you can flash the image with TWRP.
In this case you flash the img with TWRP by using: "flash img" - but important is, you must flash it to: ramdisk (and NOT to recovery_ramdisk !!)
Soon you have installed the EMUI ramdisk.img, the device can boot to system again and Magisk is disabled.
Credits:
@osm0sis Busybox for Android NDK
@Didgeridoohan MagiskHidePropsConfig module
@topjohnwu Magisk root
Restore Firmware - downgrade to Nougat - rebrand back
Restore current firmware (if you are on EMUI or OpenKirin ROM) → check out following Post:
https://forum.xda-developers.com/showpost.php?p=77905152&postcount=833
How to go back from Oreo to Nougat → and rebrand back
A) Method by using HiSuite (on PC):
1) If you have Magisk Root - uninstall Magisk with Magisk Manager (Button Uninstall)
2) Make sure, you have EMUI-Stock-Recovery installed (it does not work with TWRP)
3) Download Huawei HiSuite: https://consumer.huawei.com/minisite/HiSuite_en/
4) Update HiSuite on PC to (minimum) version: 8.0.1.302_OVE and connect your Phone with PC and HiSuite.
5) Let HiSuite install HiSuite App on your Phone - accept the Permission requests. Once that is done:
6) Click on "Systemupdate" - a new window pop up and show you your current version, click on the Link "Change version" - then you can downgrade to the latest Android 7 AL10 firmware
7) → then it is possible to use HWOTA7 again for rebranding back...
B) Method by using HuRUpdater → requires external SD or USB OTG:
If you want to go back from unofficial Oreo to Nougat and rebrand back to your original brand, you can do it with simply steps.
→ Note: HuRUpdater can not only be used for Downgrade, it can also be used for Update Firmware - It depends only on which firmware you pack together with HuRUpdater in the folder (which you have created on external SD or USB OTG)
→ The Firmware must be FullOTA-MF (same renaming than with HWOTA7 Tool)
1) Bootloader must be open
2) Flash TWRP for Oreo Download TWRP by Pretoriano80: https://www.androidfilehost.com/?fid=1322778262903998750
3) Backup your data with Huawei Backup (because TWRP can not acces data for now, because it has no encryption/decryption support)
4) Make a folder on your external SD and name it: Downgrade or Update (or however)
5) Copy the 3 Firmware zip files into the folder and make sure, two zip files are renamed (same as you did for HWOTA7)
6) Download HuRUpdater_0.4.zip from here:http://www.mediafire.com/file/r14sor2g4cbugzw/HuRUpdater_0.4.zip
7) Copy HuRUpdater into the same folder together with the firmware zip files. If you have the Nougat AL10 zip files inside, you will downgrade.
The folder contains now 4 files:
HuRUpdater_04.zip
update.zip
update_all_hw.zip
update_data_public.zip
8) Boot into TWRP. It will ask you for password. Just cancle. In TWRP open "Wipe" - but dont wipe anything - you must use the Button on the right Format Data. Confirm with typing: yes. Soon data is formatted, go back to the main menu and open Reboot - but do not reboot System - you must Reboot Recovery
→ Note: Format data is only important until we have TWRP with working data decryption
9) After TWRP is rebooted go "Install".
10) Navigate to the folder which containes the files and flash ONLY HuRUpdater_04.zip In some seconds the Akku vibrates - in this moment press for one second the VOL- Button. Now HuRUpdater will flash automatically the FullOTA-MF Firmware.
11) Once it is done, use on the left: Wipe Cache Button. After go back to the main menu and Reboot RECOVERY.
12) Your device has rebooted now into EMUI Stock Recovery. From there perform Wipe Cache Partition and Factory reset and boot to system.
Once you are back to Nougat - you can use again the HWOTA7 Tool to rebrand back to your original brand. Just use Change location (for your original cust) and make sure, the Firmware is in the update folder..
Credits:
@zxz0O0 Many thanks for HuRUpdater
HuRUpdater Thread: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
How to update older Oreo Firmware to → b537
How to update manually the Firmware from Oreo b528 or b535 to → b537
This method is based on VIE-EVA-Nocheck EMUI-Recovery for Oreo.
Required for the Firmware update is installed TWRP https://www.androidfilehost.com/?fid=1322778262903998750
Additonal information to the manual Firmware-Update from b535 (or even from b528) → to b537 → or even to next version in the future:
1) Download current Firmware VIE-AL10C00B537 (8.0.0.537):
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/update.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/VIE-AL10_all_cn/update_full_VIE-AL10_all_cn.zip
2) Let Windows show file extensions (to make sure you have at the end not zip.zip) and rename the last two zip files - (update.zip - do not rename)
update_data_full_public.zip - rename to: update_data_public.zip
update_full_VIE-AL10_all_cn.zip - rename to: update_all_hw.zip
3) Download FirmwareUpdate_onOreo_from-externalSD.zip file and extract (unzip) it:
https://www.androidfilehost.com/?fid=1395089523397898767
Inside is the folder: HWOTA and contains two files. Do not rename that files.
4) Create a folder on your external SD with the Name HWOTA in the main directory (dont use another name!) - or copy the HWOTA folder from unzipped Firmware-Update.zip instead to your external SD
5) So you have now the folder HWOTA on your external SD (without Subfolders between)
6) The folder HWOTA must contain:
eva_vie_recovery_nocheck.img
ExtSD-FirmwareUpdateScript.zip
update.zip
update_all_hw.zip
update_data_public.zip
7) Now boot to TWRP, cancle Password, allow system modification, go to Install, select storage: Micro SD - and flash ONLY the one zip file with the name: ExtSD-FirmwareUpdateScript.zip
8) The phone will automatically reboot and needs a while to flash automatically the No Check EMUI-Recovery and this needs also a while until the Firmware will be flashed automatically as well as Phone reboots after. Just wait, until it boot up.
→ if you have Root, there is no need to Unroot before and you will loose no installed apps but probably Playstore and/or Keyboard (if the apps were not updated, if the were updated, you will not loose Playstore and not Keyboard). If Playstore is missing, just install the Playstore apk and Keyboard apk and reboot phone. → Links for the apks in Post #2
Nothing will be wiped, except mobile network settings are gone and some additional Chinese Apps are installed.
9) Flash again TWRP and select your NetworkPatch.zip (that matches your real device) and in the middle you find the button "add zip" just add: Faceunlock.zip
→ flash both together with swipe to confirm and reboot phone without wipe anything.
Note: You must use the new released Files from Post #2 step 20-29: https://forum.xda-developers.com/showpost.php?p=77650678&postcount=2
10) You are now on b537 - The Chinese Apps are automatically deleted and everything works as it should
Enjoy :good:
And here it is ? Can't wait to try it. On holidays right now, I'll test it by two weeks, I just need to recover a Windows laptop as I'm using Linux right now. Anyway, thank you a lot for the effort!
thank you so much for the hardwork. Love to see this happening for the p9 plus. keep the good work up. i will try out the tools this weekend.
Just to be sure, to update an european modelo (c432) we need to follow instruction in post 1 and post 2 ?
Fil76 said:
Just to be sure, to update an european modelo (c432) we need to follow instruction in post 1 and post 2 ?
Click to expand...
Click to collapse
Hi, welcome in this Thread
→ Reading OP (Post # 1) is required because some information from there is required in Post # 2. OP is a general overview of how the tool works and what to look for.
Post # 2 is an exact guide for rebranding the European model to VIE-AL10 and updating to Android Oreo.
On Oreo, initially no IMEI is detected and there is no mobile network available - the P9 Plus must therefore be adapted. This is done by means of a zip file, which you choose according to your original model. The zip must be flashed with TWRP, after a factory reset must be performed with the EMUI Stock Recovery.
Yes, if you want your device to work with the Chinese firmware on Oreo, then you must read both Instructions and following the Guide.
I spent a lot of time for free into this project, so that the user is able to get the "impossible" possible. Everything was tested thoroughly by me and others.
FYI: I am not responsible for any mistakes or bricks that occur if someone do not follow the instructions exactly
Post #3 - Root instructions → ready
Fantastic to see this tool also for P9 Plus!
Thank you very much for the time and the work spent to create this tool!
edit:error in progress
Fil76 said:
edit:error in progress
Click to expand...
Click to collapse
? Please more detailed, if you need help
i had fastboot connection problem due to cable (one original and one not) and cause i'm dumb i didn't rename a nougat file correctly and got nrm90 test key as build number
resolved after installing oreo update (i tried restarting all the procedure with hwota setting again al10 but nrm90 etc remain)
But i'm in working progress cause i installed oreo and build numer now it's correct
now i'm continuing following your guide
let's hope....lol
edit2:YEAH ALL FINE THANK YOU FOR YOUR TOOL
the only one problem that i got that everytime i boot i got message that bootloader is unlocked
Fil76 said:
YEAH ALL FINE THANK YOU FOR YOUR TOOL
the only one problem that i got that everytime i boot i got message that bootloader is unlocked
Click to expand...
Click to collapse
That's not a problem
That's always on every Android version from Marshmallow /Nougat /Oreo above..
If the Bootloader is opened you will get this message as long the Bootloader is unlocked.
And there's nothing what could be done to hide this message.
But the other side is, without unlocked Bootloader you couldn't change anything.
And if you would relock the Bootloader - you would loose all the settings necessary for European VIE to work properly on Oreo
First of all, thanks @Tecalote and team to let my Vie-p9 plus fly again^^, i followed each step carefully and successful debrand and upgrade to Oreo, everything works like a charm and after restore all the apps and all works without problem only NFC(because i need google pay as my transport payment method), the nfc icon show in the pull down drawer but it grey out and no respond. And inside setting> device connection> only have bluetooth, Multi-screen, usb and printing options but only missing the NFC.
is it any way to fix it?
htc_black said:
First of all, thanks @Tecalote and team to let my Vie-p9 plus fly again^^, i followed each step carefully and successful debrand and upgrade to Oreo, everything works like a charm and after restore all the apps and all works without problem only NFC(because i need google pay as my transport payment method), the nfc icon show in the pull down drawer but it grey out and no respond. And inside setting> device connection> only have bluetooth, Multi-screen, usb and printing options but only missing the NFC.
is it any way to fix it?
Click to expand...
Click to collapse
Hello @htc_black
What was your original model? VIE-L29 ? - okay, I am sorry. I saw just right now, that L29 includes also NFC - I did not know that. I will upload corrected zips for L29 in about 30 minutes.
I thought, it is the same than on EVA (EVA L09 = NFC, no Dual SIM, L19+L29 = no NFC, but Dual SIM) - but VIE has NFC on L09 as well as on L29....
So, it can be fixed, no problem.
I had only L09 to test and dont own L29
After upload the corrected zip, please install and let me know, if it works! Thanks
Tecalote said:
Hello @htc_black
What was your original model? VIE-L29 ? - okay, I am sorry. I saw just right now, that L29 includes also NFC - I did not know that. I will upload corrected zips for L29 in about 30 minutes.
I thought, it is the same than on EVA (EVA L09 = NFC, no Dual SIM, L19+L29 = no NFC, but Dual SIM) - but VIE has NFC on L09 as well as on L29....
So, it can be fixed, no problem.
I had only L09 to test and dont own L29
After upload the corrected zip, please install and let me know, if it works! Thanks
Click to expand...
Click to collapse
Finally finally finally:laugh: rebranded , updated to Oreo and rooted :victory: :laugh:
Thank you so much for your great effort and helping us
Really you are a genius
Everything is working well, only NFC is not working but the rest is perfect
From VIE-L29 to VIE-AL0
meshoo00oo said:
Finally finally finally:laugh: rebranded , updated to Oreo and rooted :victory: :laugh:
Thank you so much for your great effort and helping us
Really you are a genius
Everything is working well, only NFC is not working but the rest is perfect
Click to expand...
Click to collapse
NFC patch is just uploading, coming in a few minutes. I post it here
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Sorry for my bad English.
צבי זלצברג said:
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Click to expand...
Click to collapse
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
jwoegerbauer said:
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
Click to expand...
Click to collapse
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
The file is in the forum. But to make your life easier here are the link.
https://drive.google.com/drive/folders/18B-srDVia_H4aDt7uvCDUxg2e4R5kVVY?usp=sharing The file is of type .exe and that extracts when you run on the pc, the problem is that I was suspicious about the virus so I threw the file in the total virus (if you don't know what it is, just search) and 6 programs pointed it out as malware but many others didn't find anything including karpersky and bit defender, there to make sure the files were there i renown they from .exe to .zip and I looked and the files really were there but as I don't want to take the risk I didn't extract and I didn't even try anything. The file that fix the encryption are inside doogee n20.exe, the guy said it will be in .exe and when you run it extracts the file in the C folder of the computer I recommend you to rename it from .exe to .zip because if the file have a virus you can screw your pc when running
Da-Judges said:
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
Click to expand...
Click to collapse
you can use the pixel experience lite https://github.com/ponces/treble_build_pe/releases ( remenber the lite version, because is 2,5 gig) i try and instal in my phone and worked but i cant access my storage so i search and here are the solution https://forum.xda-developers.com/t/...loop-after-any-custom-rom-doogee-n20.4357313/ i dont try it but if you want here are the solution
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
Hi, did you find N20_utils?