Database Info

[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4

I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .

stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad

Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.

killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck

Or just read the stickies.

I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers

Thank you so much for this! You saved my phone!

volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?

Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..

volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
External, like on this picture.

Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue

volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks

Just the button. You can DIY, it's easy.

worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5

incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:

eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T

ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.

help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you

Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.

[Root] lenovo k4 note running on marshmallow (6.0) official rom

This procedure has been tested on LENOVO K4 NOTE MARSHMALLOW (S219) and it worked perfectly fine.
i posted this thread since the previous procedures only covers rooting prior to S218.
verified working on s219
DISCLAIMER:
I JUST FOLLOWED THE PROCEDURE PROVIDED BY "AYAN CHOUDHURY" ON YOUTUBE CHANNEL SO CREDIT GOES TO HIM.
IF SO HAPPENED THE PROCEDURE WAS MADE BY ANOTHER DEV AND WASN'T QUOTED PROPERLY BY MR. AYAN COUDHURY. MY APOLOGIES AND GIVE CREDIT TO THE ORIGINAL OWNER OF THE PROCEDURE
I WON'T BE RESPONSIBLE FOR ANY DAMAGE, SOFT BRICK, HARD BRICK, AND OTHER INSTANCES FOR YOUR DEVICES AS IT WORKED PERFECTLY FOR ME 3-4X BEFORE POSTING THIS THREAD.
original vid: https://www.youtube.com/watch?v=fPx8QWnYLNo
Before we start:
Here is the details of my handset
Model: Lenovo K4 note (PH) [MTK MT6753 8CORE 1.3GHZ 3.00GB RAM]
Model #: A7010a48
OSv: marshmallow 6.0
Android security patch level: April 1, 2016
Kernel ver: 3.18.19+ [email protected] #1, su jun12 18:27:10 CST 2016
Build number: A7010a48_S218_160612_ROW
Step 1:
download all necessary files.
all files and links are not mine and credit goes to the owner of the files
adb tools : https://drive.google.com/open?id=0B16daNyhWTx1djhqSkJ6QkFKaUk...
recovery(i.e TWRP) : https://drive.google.com/open?id=0B16daNyhWTx1RlB0U01sUkVHMjg...
aroma file manager: https://drive.google.com/open?id=0B16daNyhWTx1TmJqRmxIUUI3YUU...
Super Su : https://drive.google.com/open?id=0B16daNyhWTx1V2ZobTI0RVpKQ1E...
xposed installer : https://drive.google.com/open?id=0B16daNyhWTx1N2RDc2Y4TzlWaWM...
xposed framework : https://drive.google.com/open?id=0B16daNyhWTx1QmlRTHhXOUMydDQ...
step 2:
a. back up any necessary files from your handset.
b. since some computers doesn't show your lenovo k4 note while on recovery mode, it is imperative to put aroma file manager and supersu on your sd card. "do not extract. just copy them as it is"
take note that the next step will definitely hard reset your device.
step 3:
a. enable developer option on your handset. go to system settings/about and click build 7x or as it says "you are now a developer"
b. go to developer option do this two things
enable oem unlock
allow usb debugging
c. once you are done please connect your device to your laptop
step 4:
a. run adb server (go to adb folder, shift+right mouse click and choose open command window here.
b. it will prompt you to allow your pc to connect/control your devices just click YES
c. on your command window, type ADB DEVICES (it will detect your lenovo k4 note)
d. once detected type ADB REBOOT-BOOTLOADER (your device will reboot)
e. once rebooted, type FASTBOOT DEVICES to verify if you are already in fastboot mode
f. if connected proceed to step 5. if not please repeat procedure
step 5:
a. once connected go to adb folder on your computer. you will see a file named unlock recovery.bat
if not, copy this text
call adb.exe devices
call adb.exe reboot bootloader
call fastboot.exe getvar all
call fastboot.exe oem unlock
call fastboot.exe format userdata
call fastboot.exe erase recovery
call fastboot.exe flash recovery recovery/recovery.by.gursewak.img
call fastboot.exe getvar all
call fastboot.exe reboot
echo done successful please press any key to continue
echo disconnect your phone and press power button untill phone reboots
pause
Click to expand...
Click to collapse
to notepad and save as batch file, name it as UNLOCK_RECOVERY.bat
b. click the UNLOCK_RECOVERY.BAT then it will ask you on your device to confirm, (will add screen shot later on) just press volume up button
c. once the process has been done, (will take few seconds) extract recovery.img to adb folder
d. go to your previously opened command window and type
FASTBOOT FLASH RECOVERY RECOVERY.IMG (the one you extracted)
step 6:
a. once flashed, disconnect your device (it will show a tiny text telling you transmission ok)
b. press and hold the power button for few seconds to turn off the device
IT IS IMPERATIVE THAT YOU WON'T TURN ON THE DEVICE UNLESS THE NEXT STEPS ARE DONE. IF YOU ACCIDENTALLY TURNED ON YOUR DEVICE REPEAT TO STEP 1.
c. press and hold vol up+vol down+ powerbutton simultaneously for few seconds, once you felt a vibration, release power button whilst still holding the vol up and down button
it will show the lenovo screen then go black. (don't worry it means you successfully flashed recovery.img)
d. connect the device to your computer
if lenovo shows on your device, now is the time to recopy aroma file manager and supersu. if not just wait for the screen to turn back on.
e. once twrp recovery is on, go to mount and check SYSTEM. (do not touch anything aside what i unstructed)
d. go back to previous menu and go to install
install aroma file manager and wait for it to finish
f. once installed it will go directly to aroma file manager, go to system folder and scroll down. look for recovery-from-boot.p and delet it
g. once deleted exit aroma file manager (button can be found on right corner)
h. go back and install beta supersu which you copied. (browse sd card)
i. once flashed, reboot system,
step 7:
a. if you made it this far, then you are almost done.
b. just finish the lenovo start up.
c. once done, connect your device again on your computer and copy xposed apk and xposed arm to internal or sdcard
d. install xposed apk
e. turn off your device
step8:
a. reboot to recovery (press vol up and down and power button simultaneously, once you felt a vibration release power button whilst holding vol up and down button. lenovo screen will show and it will eventually go to twrp recovery)
b. click install and install xposed arm
c. onced install. reboot system.
THERE YOU GO... YOU ARE DONE. YOU CAN VERIFY ROOT BY DOWNLOADING ROOT CHECKER FROM GOOGLE PLAY STORE.
WELL I WAS FORCED TO ROOT MY K4 NOTE JUST TO PLAY POKEMON GO.
I WILL UPLOAD SCREEN SHOT ONCE I ALREADY COMPILED THEM. THANK YOU
IF YOU LIKE AND HELPED YOU A LOT PLEASE HIT THANKS AND LEAVE A MSG.
IF YOU HAVE QUESTIONS, JUST COMMENT IT HERE.

Thanks it worked. I was about to complain when twrp recovery does not show up. BUT IT WORKED THANKS

xposed isn't necessary to root the phone. Am I right? Maybe you should explain that in the OP. You'll get people confused down the road if they don't already know what they're flashing.
Sent from my f320 using XDA Labs

Will it work on s219?
I just badly wanna root amd this is the easiest way i found..
Thanks:cyclops:
And yes,one more question,
During unlocking the bootloader, will it only format my phone or both phone and sd card?

infected_162k said:
Will it work on s219?
I just badly wanna root amd this is the easiest way i found..
Thanks:cyclops:
And yes,one more question,
During unlocking the bootloader, will it only format my phone or both phone and sd card?
Click to expand...
Click to collapse
yup....and yuhooooo.
it worked like a charm.thank you very very much:fingers-crossed:

infected_162k said:
yup....and yuhooooo.
it worked like a charm.thank you very very much:fingers-crossed:
Click to expand...
Click to collapse
hi
will it erase internal phone memory (i mean after flushing ROM can i get my data using any recovery software)
i am also using same s219 Rom model lenovo k4 note phone.
Actually i deleted some files unexpectedly from internal memory but i want them back, so i tried many ways but no software is identifying internal memory as a drive. I tried to root using root apps but marshmallow not allowing.
i found this topic, but i have only doubt is after flushing the rom can i recover my data using any recovery software?
Thanks in advance

thank you so much!
now to answer some queries and give thanks...
@Duffy144: glad you like it.
@Bdwilk: thank you for the input, i will do that.
@infected_162k: i haven't tried yet since i haven't been able to check latest OTA, but i will try it now since s218 causes lag and memory leak when using facebook messenger. and as you've said. thanks for the confirmation for s219, at least i am more confident. btw, does this really solve the memory leak of the s218?
@anvesh.k yes it will delete all files as the procedure requires you to factory reset your handset.

Rooted K4 Marshmallow
Damn. Finally. I got root. Can finally get rid of that Cell Broadcast. Thanks Sir ansei. The unlocking of bootloader, flashing of twrp and supersu process is pretty much straight forward and will only take you about less than 10 minutes.
Am not sure if this is a systemless root i have. If so, it's great. I am on S_219. Zero performance or stability issues.
I feel my K4 Note runs smoother and snappier compared to S150 row. Still getting the hang of the revamped user interface though.
Overall, Marshmallow 6.0 S_219 runs great with unlocked bootloader, twrp and supersu.

Can someone confirm if this works with 2 gb / 32 variant?

RK_D2502 said:
Damn. Finally. I got root. Can finally get rid of that Cell Broadcast. Thanks Sir ansei. The unlocking of bootloader, flashing of twrp and supersu process is pretty much straight forward and will only take you about less than 10 minutes.
Am not sure if this is a systemless root i have. If so, it's great. I am on S_219. Zero performance or stability issues.
I feel my K4 Note runs smoother and snappier compared to S150 row. Still getting the hang of the revamped user interface though.
Overall, Marshmallow 6.0 S_219 runs great with unlocked bootloader, twrp and supersu.
Click to expand...
Click to collapse
Can you recovered old data after rooting the device?

anzei19 said:
@infected_162k: i haven't tried yet since i haven't been able to check latest OTA, but i will try it now since s218 causes lag and memory leak when using facebook messenger. and as you've said. thanks for the confirmation for s219, at least i am more confident. btw, does this really solve the memory leak of the s218?
Click to expand...
Click to collapse
Amm, about that memory leak thing, i basically know what that is cause it was a huge problem in my father's phone(gionee m3). But i exactly don't know how to know if it's still there or not as I use messenger hardly 2-3 times a week. guide me about this so I can tell you exactly.
Another thing that will help other users: I have to factory reset my phone due to a google error ( unable to communicate with Google server). I was not sure about root and xposed will be gone or not. But here is the result : lost both, root and xposed. Just flashed both again, super su and xposed framwork, worked

anvesh.k said:
Can you recovered old data after rooting the device?
Click to expand...
Click to collapse
Old data? Not sure what you are referring to. After the unlocking of bootloader, flashing or twrp and root, restarted the phone in normal mode. Went through the setup wizard and all. Reinstalled my usual stuff. Back to where I left in Lollipop. Zero issues with Marshmallow 6.0 S_219.
Sir Ansei, everything is fine except 1 minor issue, when rebooting to TWRP, I often get the black screen. Power cycling the phone works. Any ideas?

RK_D2502 said:
Old data? Not sure what you are referring to. After the unlocking of bootloader, flashing or twrp and root, restarted the phone in normal mode. Went through the setup wizard and all. Reinstalled my usual stuff. Back to where I left in Lollipop. Zero issues with Marshmallow 6.0 S_219.
Click to expand...
Click to collapse
May be what he trying to tell is he accidentally deleted some of his important stuff and now he wants to get it back with the apps that use root to dig around. But as per my experience, it only work if that portion of sd card of internal storage is stayed untouched not if overwritten by something else. But if you already rooted, just give it a try...maybe you'll be lucky...

infected_162k said:
May be what he trying to tell is he accidentally deleted some of his important stuff and now he wants to get it back with the apps that use root to dig around. But as per my experience, it only work if that portion of sd card of internal storage is stayed untouched not if overwritten by something else. But if you already rooted, just give it a try...maybe you'll be lucky...
Click to expand...
Click to collapse
Thanks for understanding my problem

call fastboot.exe flash recovery recovery/recovery.by.gursewak.img - needs to be edited? make sure path is correct and image name.
call fastboot.exe flash recovery recovery.img
Just put recovery.img in the same folder

I cannot get fastboot to recognize my device & perform the bootloader unlock. Whenever I type in " adb reboot bootloader" or click on that "unlock_recovery.bat" file, I get booted into a dark screen where "fastboot" is written at the bottom & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Please tell how to get past this!

sujitmohanty2012 said:
I cannot get fastboot to recognize my device & perform the bootloader unlock. Whenever I type in " adb reboot bootloader" or click on that "unlock_recovery.bat" file, I get booted into a dark screen where "fastboot" is written at the bottom & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Please tell how to get past this!
Click to expand...
Click to collapse
you should install fastboot driver

setpam25 said:
you should install fastboot driver
Click to expand...
Click to collapse
@setpam25 Is there a specific driver for that.? If yes, could you please share the link to download that?
My system currently has the lenovo usb driver 1.16, windows 10 mtk vcom preloader & ADB interface driver (by google) properly installed!

Does this work on s230 update marshmallow

Please help me,
I am stuck there until I reboot system

How to Root the CAT s60 ... ... and more !!!

Since i am afraid, that my Guide will dissapear in the other Thread,
i post this guide in a new Thread !
I have just uploaded a collection of, how i have named it, - s60 essentials - there are ALL files included to flash stock, update to .033, flash twrp recovery and root.
(this is for Win7 x86, you have to check if it works for other versions yourself, sy..)
Here is my collection
HOW TO.... Stock, Update, custom recovery and root your s60 !!!!
Disclaimer: if you brick your phone, it's your fault, i have tested this way of rooting my s60 now for a several times and it works 100%
SO READ TWICE, CHECK TWICE, BEFORE YOU CLICK ONCE !!!!! i will not take any responsibility !!!
Thanks to everybody who contributed here in this thread (Cesarq, OpenMinded, Tuschi, BetonJohn, etc.......) the software in the link
is the collected data, freely available in the net and linked in the original Thread several times, i have only bundled one package and wrote
this, hopefully usefull guide.
in principle do as follows: (I will only explain once how to sideload or load via recovery, afterwards i will only state what kind and what file)
Prerequists
- install USB drivers (for recovery and adb)
- install "minimal ADB and fastboot"
- copy the two updates (update032 & update033) into the folder, where you have installed "minimal ADB and fastboot" (makes live easier later)
- install QPST (the version of QPST is the one from Androidmtk and should be virusfree
(The version of QFIL in my collection is the one without reboot, so you have to reset/reboot your phone manually (resetbutton below hatchdoor on your phone) whenever
stated in this guide.
- format micro SD card in fat32 ! and copy SuperSU.zip onto it.
- connect a WORKING USB cable to your phone (Not to your PC atm !!!)
getting twrp (for saving your old firmware only)
- power off phone.
- start minimal adb on your PC
- start QFIL (part of QPST) on your PC
- press VOL+ & VOL- simultanousely and connect phone with PC (it will vibrate once, top right LED starts blinking red, screen stays black) - DOWNLOAD MODE -
(just in case: to leave Download mode, press and hold power button for apprx. 15 seconds)
- as soon as you connect your phone to the PC, QFIL should show the Phone/port in the topline allready, if not, either try to manually select the port, or you probably still have
a problem with the USB drivers !
- tick in QFIL Flat Build (top left)
- QFIL - select Programmer, "browse" to the saved location of "update-twrp-recovery-nobootpatch" and select the "prog_emmc.blablabla...mbn" file and doubleclick
- QFIL - "load XML" ,select rawprogramm, doubleclick, select patch0, doubleclick
- QFIL - click on "download"
- if everything was OK up till now, it should start download - BE PATIENT- and read the status window on QFIL, when it shows "finish download"....
- disconnect phone from PC
- press and hold simultanousely POWER and VOL+ and use a small tool to push the reset button on the phone under the hatch, while still pressing Power and Vol+ !
- the phone should now be in twrp recovery. If so, do a full backup now to your (allready inserted and fat32 formatted) microSD card!!!
when done
- Power off your phone !
flashing stock 31.02
- enter download mode again (Vol+ & Vol-, connect phone to PC.......)
- this time in QFIL, browse in programmer path to "s60_stockFW_31.02" and select the programmer from there
- load XML's (the onces that belong to Stock31.02)
- start download... this will take a while !!!! BE PATIENT !!!!
- when QFIL status window shows finish download, push the reset button on the phone and let it reboot.
- it is normal, that the phone should restart itself 2, maximum 3 times at the first start, but sometimes it ends up in a bootloop (Cat Logo, reboot, CAT logo, reboot, etc, etc, .......)
(The bootloop mainly happens, if you clear, in twrp recovery, the whole OS, but that's no issue either...)
- if it ends up in a bootloop, no worries, just continue ! Believe me, i did the process now several times ! )
you are back on stock 31.02 !
-Power off your phone again
Updating to 032
- bring up minimal ADB sideload on your PC (start it, if not allready done in previous step (getting twrp)).
- press and hold POWER and VOL+ button on your phone - RECOVERY MODE -
- when in stock recovery select (with Volume keys) "adb sideload" and click the Powerbutton
- connect your phone to the PC
- on PC, type into the black ADB Terminal window "adb sideload update032.zip" and hit enter
- if drivers are there, phone will start downloading the update now.
- when complete, select clear cache, and clear data then reboot your phone.
- again, same as in the step (flashing stock), if bootloop, no worries, just continue, if it boots up, let it boot up and then..
you're on 032 now
- Power off the phone again
Updating to 033
- do the same steps as described under "Updating to 032" only difference, type in adb window " adb sideload update033.zip"
After updating to 033 your phone should boot up normally now, NO MORE BOOTLOOP !
getting twrp
- this is the same step as above "getting twrp" only difference, this time, no backup needed and...
- when in twrp-recovery, select "install" browse to your micro SD-card, and...
- install SuperSU.zip from SDcard.
- once more, clear cache and data and reboot.
The phone should boot up now, you should be on FW 033, with custom recovery and root !!!
That's all !!!

Would a TWRP or fastboot flashable stock recovery let us apply future OTA updates without wiping and starting from stock 031 if we're using systemless root like Magisk?
From stock recovery you can reboot to bootloader which puts us in fastboot (you can select boot mode with Vol +/-), so I'm thinking if we could boot TWRP from fastboot (without flashing, obviously), we could back up the stock recovery. Then when the next update comes around, we flash stock recovery back, apply the update, then reflash TWRP.
I tried fastboot boot recovery.img from update-twrp-recovery-nobootpatch but I got
FAILED (remote: unknown command)
and rebooting into recovery from there just got me stock recovery which makes sense.

QCN please
Hi guys, can anyone share me QCN backup of S60 because i've lost it! Thanks.

Last update for Android 6.0 was from 766 days ago.
Any suggestions on how to patch?
Thanks a million

Chuwi hi9 Pro unlock, root, TWRP, etc.

If you dont have full ROM backup from your device or official ROM, dont do anything in terms of modding but to install vcom drivers (in my case they wont work without Virtual Serial Port Drivers) for bootloader, and adb/fastboot drivers, make sure theyre working, install Miracle Box / SPFlashTool (or similar ?) to be able to backup/flash your ROM/partitions from/to your device.
Check if it works for you (ie backup your ROM and try to flash something (cache) back.
Now when people are scared enough I want to tell you that it is almost impossible to kill (brick) your MTK phone, it happens mostly when people flash something that is not suppoused to be flashed (something from another device), the worst case if you flash wrong preloader or erase preloader but even after this there is a chance for resurrection. it takes time and efforts though.
++++++++++++++++++++++++++++++++++++
This is TWRP 3.2.2.0 recovery for Chuwi hi9 Pro.
Partitions available for backup:
boot, recovery, system, vendor, data (not incl. data/media = internal sd), cache and "para" (if you have got "recovery loop" - flash "para")
.img flashable - boot, recovery
look for detailed instructions for coomon things in other treads, like
- how to install bootloader vcom drivers and adb / fastboot drivers
- How to work with adb / fastboot command from your computer cmd window.
- how to use Miracle Box / SPFlashToll
This is detailed instruction how to make SPFlash backup out of your phone though Miracle Box does it in one click (well, almost)
- how to unlock bootloader (fastboot mode)
- how to use toilet paper (manual mode)
- how to install twrp recovery
- how to root
Unlock, Install, Root in one post
++++++++++++++++++++++++++++++++++++++
So, main point of this thread is TWRP, youll need:
- roll of toilet paper
- spflashtool backup (just in case)
- backup of your data (if you care) - your data will be erased during the process.
- unlocked bootloader
- twrp image
If something went wrong (highly unlikely), but "if".
Worst case scenerio: your phone will not boot into system / recovery
Solution: reflash (fastboot or flash tool): boot / recovery / system
Worst case scenerio: flash factory ROM (SPFlashTool)
Steps to do when you have all knowledge and all files ready.
IN YOUR CURRENT SYSTEM
In settings->System->About tablet -> click several times "build number" untill you see message "now you are developer"
In settings->System->Developer options: Enable USB debugging and OEM Unlock, connect cable
REBOOT INTO FASTBOOT
Power off, Power on holding "vol+"
Youll see black screen with 3 strings of menu (very small font):
- recovery
- fastboot
- system
use "vol+" for navigation, use "vol-" to confirm your choice (fastboot)
OR from your pc cmd window (shift+right click on adb folder -> choose "open command window here") type: adb reboot bootloader
press Enter
UNLOCK BOOTLOADER
on your pc (if cmd window is not ooened yet: shift+right click on adb folder -> choose "open command window here") type: fastboot oem unlock
press Enter
watch your phone and pc screen for messages
if you have vision problems, make sure you have a magnifying glass.
INSTALL TWRP
download hi9pro_twrp.img to your /adb folder
from the same cmd window type:
fastboot flash recovery hi9pro_twrp.img
*
Reboot into twrp and flash Magisk
*
Basically this is it
There is no command from fastboot to reboot into recovery (correct me)
You can power of, power on holding "vol+", choose "recovery" from menu
command to reboot into system: fastboot reboot
+++++++++++++++
* NEW *
Infect_Ed has posted TWRP recovery that he has compiled from source. DOWNLOAD FROM HERE
We don't know how to make twrp recovery work with encrypted data partition.
Read next paragraph if you are OK to trade security (encripred userdata) for functionality.
++++++++++
==========
In case you want to have your userdata decrypted (and full functional twrp), use following steps:
*** Please, note all userdata AND internal SD will be wiped during the process***
If you care
Save Internal SD card content to your ext.SD or computer
Make a Titanium backup of user apps (check Enable external data backup in Titanium settings)
If Titanium fails to write to your ext.SD than change Titanium backup folder location to int.SD
and after backup is done copy Titanium backup folder to ext.SD or PC.
Disable any passwords/pins from Settings->Security & Locations
(I know they are stored in /data/.. and will be erased anyway but just in case)
- Reboot into TWRP
- ftom TWRP -> Wipe ->Format userdata -> Confirm with "yes"
do not reboot into system
- flash encryption_prevener_hi9pro.zip to prevent system automatically encrypt userdata (it is used to insert modified fstab.mt6797 into vendor/etc)
- reboot system
- restore your int.SD content and apps
============
Link to official ROM/Firnware
*** Read this if you have Recovery Loop - no matter how you boot (buttons, from twrp recovery or from adb/fastboot shell) your device you always end up in TWRP recovery ***
- download 2018-09-29--para.zip
- unzip it - there is a folder 2018-09-29--para with 3 files inside
- connect your phone in twrp recovery mode to your computer
(you may need to turm "enable mtp" option in TWRP->mount)
- copy that folder into your sd card, the path is : TWRP/Backups/Hi9Pro
- click "Restore" (on the next screen make sure ExtSD is chosen as backup path)
- check checkbox "para", run restore, reboot
explanation: para is a partition contains last issued kernel reboot flag(command), like "reboot to recovery, reboot to system, etc." I think there is one flag that tells to kernel something like "reboot to recovery, do something untill its done", since this "something" never done, device reboots into recovery over and over again. This happend to me when I tried "factory reset" command from android settings, so android have sent my device into recovery mode where that "factory reset" command had to be performed but never done because its now not stock recovery but twrp.
**** If you have following problems:
Unknown Baseband -> Unknown IMEI -> NO sim card -> NO cell network
Look here first
****
***** If you came here from there.*****
and you are following their instructions, please, note, step 7. Unlock bootloader : DO NOT DO command "fastboot flashing unlock", just skip it.
Also, try to avoid "fastboot boot recovery.img" command to reboot into recovery (just use physical buttons for reboot). I'm not sure but something caused "recovery loop" in one case at least.
****** back-to-encr.zip if you want to encrypt your decrypted userdata (original fstab.mt6797 will be flashed, no data loss, you will not be able to mount userdata in TWRP, first boot may take long time due to encryption process - 10-60 min- depends how much data do you have)
******* twrp_recovery_chuwi-hi9pro_infectEd-XL is same Infect_Ed recovery adopted for our screen.

Hello. I made a mistake last week. I flashed accidently twrp with a scatter File from the HI9 Air through the spflashtool on the Hi9 Pro. Now it doesnt turn on etc. Is it hardbricked or can i still get it back to life?

No, its not complitely bricked if flash tool still recognizes your phone in bootloader mode. Most likely youve made same mistake I did. Depends of how you flashed that recovery - recovery only or full sisyem WITH new recovery. most likely you flashed only recovery partition. than, first, try to reflash backed recovery & next to recovery ("para") partition. in "download only mode" therell be an error "pmt has changed" than try "format & download" and "firmvare upgrade" - use scatter file contained only those two partitions. if you didnt make a backup ill put here that "para" partition and you can use hi9pro twrp img. in case this wont work, you may want to reflash the whole rom. We need to find factory rom image (from Chuwi or someone who did a back up prior he entered his credintals - thats another mistake Ive made Ive dumped a rom with all my logins information). if I have time I'll try "factory reset" to make a backup from "clean" system.
again, its almost impossible to brick mtk completely. even if flash tool doesnt recognize you phone (dead battery) there is a jump-pins method.
upd. Just looked @ Air scatter and found that Air recovery partition size is same as Pro (~16mb). now I dont know haw was that possible to overwrite next to recovery partition(s) and I think I used same Air img as you did and I've got size warning message when I flash it. anyway here is archive with scatter for recovery and para. just add twrp hi9 pro recovery (rename recovery.img to recovery.bin) and try to flash.

I didnt made a Backup (stupid me) i flashed the recovery file with a scatter file. When i plug the device in the pc the USB sound comes and its recognized as MEDIATEK USB PORT (COM8), but its removed automatic (USB Sound for disconnecting) The Screen stays black. So i have to wait for a Rom and a scatter File then?
---------- Post added at 19:50 ---------- Previous post was at 19:39 ----------
I tried your idea. I got an error Message: "Status Preloader Invalid" The Preloader File Format is invalid.

you know how to use flash tool , first you have to press "download" THAN connect usb cable.
but this is a good sign (pc recognize something), you may want to google for something like "unbrick mtk 6797 sp flash tool" for more info
this is archive w. 4 1st partitions (incl preloader)
Ive gotta go. Dont smash your tablet its 100% repairable, well 99.999%

thats how it looks
https://photos.app.goo.gl/9EK8vTwcTS3fDf1a7
---------- Post added at 20:21 ---------- Previous post was at 19:58 ----------
Still get an error Message for the PRELOADER. I read some Tutorials and dont find a Problem in my setup or my doing. Sucks :-/ But Thank you very much for your help

is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?

Good Morning.
Bootloader is unlocked, no matter which key combinations ill try the screen stays black. When i have the usb cable at the PC (no matter which Port or cable) it the plugin - plugout sound plays every few seconds/minutes (not the same time in between). It is recognized as "MediaTek USB Port (COM4)" (different PC i tried). When ill try to install the vcom drivers i get the message that the best drivers are already installed and that are the mediatek usb port driver.
Image of the device manager: https://ibb.co/erkW6e
zelipukin said:
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Click to expand...
Click to collapse
---------- Post added at 07:34 ---------- Previous post was at 07:07 ----------
zelipukin i made a short Video about the behavior. The Device seems to activate when i push vol+ or power, but it looses connection when i stop holding the button or sometimes even when i hold the button.
https://drive.google.com/file/d/1m3YLrH5ZaVLttcSfDxx3RvL0DaXPcxzk/view?usp=sharing

...thinking
Just tried...seems like backups I made(and posted here) from Miracle Box is incompatible with SP Flash.
SP Flash doesn't like this and doesn't like that when tries to restore those backups but Miracle Box restores individual partitions or whole ROM w/o problem.
SP Flash is so inconvenient if you try to make a backup ... its also inconvenient when you try to restore.
Where did I get that Miracle Box for free ?
Let me figure out something...
....
This is something beyond my understanding but let me to describe what I did
- in SP Flash I choose scatter file and recovery.bin (like I sent to you)
- download only - no go
- download+format - no go
- firmware update - warning message about wrong partition size or something like this - Ignored - Flashed
- Bricked again (like yours - black screen - that's it)
- OK, I have several backups. Tried all of them - none of them works... except one
- Flashed that backup with SP Flash - no questions, no warnings, no errors - device came alive
- Flashed only recovery.bin - everything went fine
- Tried to find difference btw different backups - but couldn't find any
- So I tried to flash those files (to try 3.zip) several times and everything went OK, so this is 100% working backup.
Try it and see what happens, then we can go somewhere else. I still suspicious about those MTK Usb Com(8) instead of preloader usb. Also if you used "Firmware upgrade" option once, I beleive you'll need full ROM flash. Keep looking for it @ Needrom.com.
Strange things happen. Couple years ago I lost MTP connection with my MiMax. I tried everything possible but no luck - have to use UMS Enabler so I can read/write ExtSD at least, but MTP works with Chuwi.
I spent numerous hours trying to connect Chuwi in preloader mode until found that solution about Virtual Serial Port drivers.

Thanks for your help so far. Seems like my Device is half dead after 2 Hours of use

I'll tried to change the Drivers for the mediatek, it shows the device now with the preloader, but i think it doesnt work right. when i change the usb port it comes back as MediaTek USB Port (COM4). I made you a 15 Second Clip of the behavior.
https://drive.google.com/file/d/1m7wyIlIYJLN7ikmgUTzHBJtBdbZQrYaa/view?usp=sharing
Really weird. :-/
---------- Post added at 14:55 ---------- Previous post was at 14:40 ----------
and no chuwi hi9 pro rom at needrom yet. :-/

Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"

i think i used the upgrade one, after download only didnt work.
Ill tried the same method with changing drivers.
I will sit this one out, till you have uploaded the rom
Thanks for helping me out!
zelipukin said:
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
Click to expand...
Click to collapse

Just a few questions after using Hi9 Pro for about a week:
1) Where is the microphone ? Is it the small hole under the volume button ? (Strange position)
2) On the back side the two metallic stripes separating the plastic of the metal body are they something like antennas ? (LTE or WiFi or both ? )
3) What is the version of Bluetooth ? (4.0 or 4.1 or 4.2 ? )
4) Is it possible to use some kind of fast charging with a suitable charger or software app (firmware update) ?
MediaTek has a technology called "Pump Express" or something like that...
5) Do you have sudden, unexpected pop-ups of full screen advertisements while you are working with your tablet ?
How do we get rid of them ?
6) How do I find the LTE band the tablet is actually using while it's in use ?
I don't mean the table of supported bands, I mean the active band while using it.
Thanks!

1) looks like and its logical bc its close to mouth than if they put it in the bottom.
2) not sure, but most likely
3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
4) too many different opinions, cant find the truth
5) none so far
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated

zelipukin said:
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
Click to expand...
Click to collapse
Yes, it is a very small hole at the bottom right as you hold it, with a size of the edge of a needle!
zelipukin said:
1)3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
Click to expand...
Click to collapse
Thank you.
zelipukin said:
5) none so far
Click to expand...
Click to collapse
But how did you do that ?
Did you add an Ad Block after rooting the tablet ?
The kind of ads I get, is more of suggested apps to install from Google Play.
It is literally bombarding me with an exhaustive rate.
I went to settings to "advertisements" of Google and it says that I can't turn it off.
Could it be some app that I installed that is spamming me this way ?
Can you suggest something to stop it ?
zelipukin said:
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
Click to expand...
Click to collapse
I installed LTE Discovery and although I'm not rooted it seems that it works OK and it's showing me the bands.
The signal strength is lower than a mobile phone at the same position, same time, same provider.
Do you have an equal signal strength like your mobile phone ?
One more question:
7) Is it feasible for a developer to build a custom ROM for this device if he wants to or there are certain restrictions forbidding custom firmware ?
Is there any chance for a custom ROM in the future, because I don't think Chuwi will upgrade to 8.1 or better Android.
Thank you!

Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed. I didn't do any system modifications except installing Magisk and modules - ExCard Access Enabler, init.d injector, Magisk SELinux Manager, ViperX (slightly better sound from speaker)
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.

zelipukin said:
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed.
Click to expand...
Click to collapse
Me too, I got a sealed and clean tablet from GearBest but If you look closer to that setting, it says that you can turn on or off the specialized ads for you, but you can't close ads completely.
For example, during web browsing do you see ads inside various sites ?
Or when opening apps on your tablet ?
I think we need an ad-blocker for this.
zelipukin said:
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
Click to expand...
Click to collapse
I meant for mobile 4G data, not as a phone.
In my country we have three bands for LTE:
B3, B7, B20.
When the tablet rotates between 3 and 7, I have poor to zero signal.
But I saw with LTE Discovery that when it switched to 20 then the signal is very good.
So, with the help of MTK Engineering I disabled 3 and 7 bands and everything seems OK now.
I hope B20 to be used everywhere near to me.
zelipukin said:
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
Click to expand...
Click to collapse
I'm not familiar with Android internals so much, I am only using a Note II with TWRP and a custom 7.1.2 ROM and I'm missing some simple customizations not available with out Oreo 8.0 stock ROM.
I haven't even tried yet your first post regarding rooting and all the others because I'm not so sure where to find these tools and how to use them.
It could help a lot when you find some time to add more descriptions and links in your first post, if possible like Hi9 Air thread.
Thank you!

I dont know how and why, but I dont have any agressive advertisements. Checked Opera I'm using for webbrowsing - even "block popups" option wasn't checked. Had to download app yesterday (AutoNotification) from gp store and when I started it in a "free mode" there was a message like "to use this app in a free mode you have to agree to see ads", clicked "ok" , then message "downloading..." appeared...and nothing, no ads. I connect my tablet to the internet through my phone but dont think that matter.

Just a few more short questions:
8) Is there any other way to wake up the device instead of pressing the red button ?
For example double tap or maybe using the volume buttons or any other way.
Because I'm afraid of pressing the same button again and again.
9) Does this device have a WiFi 2x2 MIMO ?
I haven't found any particular info on this.
10) What is the kernel of the ROM ?
Is there any GUI compatible like Kernel Aiutor to make changes or take a look at info for the device ?
Thank you!

Lenovo S5 Pro - L58041 (Global) [2020.03.21]

Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!​
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***​
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.​
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***​1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***​1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!​
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!​
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***​
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
​
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** ​1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)​
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***​1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!

Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.

kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto

kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.

Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.

kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?

Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.

kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.

Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:

kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.

Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.

kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.

After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"

kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.

Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).

good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g

nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!

Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...