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.

[GUIDE][TOOL][ROOT]Cubot Note Plus (MTK6737T) Root with Magisk V0.3

!!! YOUR WARRANTY IS NOW VOID !!!​
THIS TOOL IS FOR CUBOT NOTE PLUS ONLY.
neither I nor the XDA Forum is responsible for your phone brick or your cat triggers an atomic apocalypse. YOU has been responsible for your phone and you are doing everything at your own risk.​
This is a tool for rooting the CUBOT NOTE PLUS ONLY.
NOTE: THIS TOOL IS IN ALPHA STAGE
RoCuNo+_v0.3 is online.
Downloads see post 2
This tool can root your Cubot Note Plus and patch your boot.img for working with Magisk.
this tool can make this in seperate steps or All-In-One. For now the bootloader must stay UNLOCKED for root to work.
A guide to doing this by yourself with adb is also in this post.
NOTE: ALL YOUR DATA GET LOST. SAVE YOUR IMPORTANT DATA FIRST. (Videos, Pictures, Music and all you can save.)
What this tool can do:
Unlock/Relock your Bootloader
Root/Unroot your Cubot Note Plus (Unroot dont work for now)
[*]Make a Dump of your Boot Partition as boot.img
Install MagiskManager-v5.4.3 and Magisk-v14.0
Please download the attached zip and unzip it somewhere and rightclick on RoCuNo+_V*.bat and start as Administrator.
Read all carefully and choose your option. Follow the instructions on screen STEP BY STEP!!!
Better way is to choose the AIO because that makes all for you except a few steps.
Downloads see post 2
GUIDE
OEM UNLOCK + ROOT + MAGISKMANAGER APP
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. go in RoCuNo+ Directory on PC
08. press Shift + Right Mouse Click
09. Open Command Prompt here
10. type
Code:
adb reboot-bootloader
11. type [ODE]fastboot oem unlock[/CODE]NOTE: ALL YOUR DATA WILL BE DELETED
12. press VOL+ Button on phone to oem unlock
13. type
Code:
fastboot flash boot patched_boot.img
14. type
Code:
fastboot reboot
15. if you have unlocked your bootloader, make your setup
16. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
17. enable "USB DEBUGGING" (Go to "Menu --> Settings --> Developer Options")
18. type
Code:
adb install -r -d -g MagiskManager-v*.*.*.apk (set the Version numbers for *)
OEM LOCK
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. go in RoCuNo+ Directory on PC
08. press Shift + Right Mouse Click
09. Open Command Prompt here
10. type "adb reboot-bootloader"
11. type "fastboot oem lock"
12. press VOL+ Button on phone to oem lock
13. type "fastboot reboot"
UNROOT
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. Download SP Flashtool and Firmware for Cubot Note Plus
08. Start SP Flashtool and choose the MT6737T_Android_scatter.txt from the Cubot Note Plus Firmware Folder.
09. Turn off the Cubot Note Plus.
10. Click on Downloadbutton and connect the Cubot Note Plus to PC.
NOTE: ALL YOUR DATA WILL BE ERASED. MAKE A BACKUP IF YOU NEED.
11. After Flashing is complete, reboot Phone.
Old Guide
Save your data.
Connect your phone to PC and make sure all drivers are installed. (Boot up to normal system, recovery and fastboot to get sure.)
Open a CMD Prompt on your PC and switch to Directory where you have unzipped the RoCuNo+. (e.g. C:\Users\YourName\Desktop\RoCuNo+ or You can go to RoCuNo+ folder and Shift+Rightclick on empty space and click "open Command Prompt here".)
Type:
Code:
adb reboot-bootloader
Than:
Code:
fastboot oem unlock
NOTE: ALL YOUR DATA WILL BE DELETED
Press VOL+ on Phone if asked
wait for device for unlock
Type:
Code:
fastboot reboot
Setup your phone until you come to system.
Enable "Developer Options" Menu. Go to Menu --> Settings --> About Phone and tap Built Number 7 times until a message appears that you are now an Developer.
Enable USB DEBUGGING and OEM UNLOCKING in Menu --> Settings --> Developer Options.
Enable UNKNOWN SOURCES in Menu --> Settings --> Security
Copy MTK-Engineering-Mode.apk and MagiskManager-v5.4.0.apk on your and install this to apps.
open the MTK-Engineering-Mode app tap on MTK Settings and swipe to Log and Debugging.
Tap on User2Root and than the Root button.
NOTE: UNPLUG AND RECONNECT YOUR PHONE. DONT CLOSE THIS APP OR DO SOMETHING ON THE PHONE. YOU LOSE YOUR ROOT IF YOU DO SOMETHING.
Go back to CMD Prompt on PC and type:
Code:
adb root
adb shell dd if=/dev/block/mmcblk07p of=/sdcard/boot.img
Now open MagiskManager app and tap the Install button.
Choose to inject in boot.img
Point Magisk to the boot.img.
after Magisk has succssesfully patched the boot.img it will copy it to /sdcard/MagiskManager/patched_boot.img.
Copy your boot.img from sdcard AND the patched_boot.img from sdcard/MagiskManager to the RoCuNo+ folder on your PC.
Go to CMD Prompt and type:
Code:
adb reboot-bootloader
than type:
Code:
fastboot flash boot patched_boot.img
when flashing is ready, type:
Code:
fastboot reboot.
on phone go to MagiskManager app and check if Magisk and Root are on green state.
You succssesfully have rooted your Cube Note Plus.
Take care of the boot.img and the patche_boot.img in case we need them on some day.
DONT RELOCK YOUR PHONE BECAUSE YOU CANT WRITE ON /SYSTEM PARTITION WITH LOCKED BOOTLOADER. (for now.)
I hope that helps many people with his/her phone and maybe someone can make TWRP or a Custom Rom for our phone. Now the Door is Open.
if someone found better solution for some tasks here please let us know.
Changelog
RoCuNo+ v0.3
Delet the Unroot Section because it doesent work for now.
update Magisk Manager App to 5.4.3.
Update Guide.
Update patched_boot.img.
RoCuNo+ v0.2
complete rework.
all should now work.
now the original verified-boot.img from Cubot is implemented. so root and unroot works now.
ive patched the original verified-bood.img with magisk so no boot.img dump has to be made.
the tool now detects what state you are and boots the state needed for his job.
only magisk manager app has to be installed on device and the tool do this for you.
the tool detects if you are already oem unlocked or not. so if you already unlocked you dont
need to do that again. it also detects in witch state your phone and boots the right mode.
Credits to XDA-Developer Schwester_Gabi (https://forum.xda-developers.com/member.php?u=5264039) and the Flampinko.IT Team ([email protected])
you can use this tool on your own risk but its not allowed to share this tool in other forums or blogs or something. but you can write about this tool and link
than over to the XDA-Developer Forum under (https://forum.xda-developers.com/android/general/guide-cubot-note-plus-mtk6737t-root-t3695272)
it is also not allowed to copy the code or change anything in this programm. Only Schwester_Gabi or the Flampinko.IT Team is allowed to change the code.
If you have any Ideas to implement in this tool than post it over to XDA-Developers Forum (https://forum.xda-developers.com/android/general/guide-cubot-note-plus-mtk6737t-root-t3695272)
or send us an Email ([email protected]). If you like our work please make a donation to help us.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZXVV3MZX2NVK6
please respect the developers work and stick to the rules.
Credits and special thanks to:
topjohnwu for the awesome Magisk
themonsterit for MTK-Engineering-Mode App
Schwester_Gabi for finding the way and coding the RoCuNo+ programm
all the people who write solutions for problems that i read to find the way too root.
XDA-Developer Team to giving us such a great Platform to share our stuff with the world.

Cubot Note Plus Stock Rom:
V8:
Mirror 1
V7:
Mirror 1 / Mirror 2
SP Flash Tool for Cubot Note Plus Stock Rom:
Mirror 1 / Mirror 2
Cubot Note Plus Stock Scatter File for flashing:
Mirror 1 / Mirror 2
RoCuNo+_v0.1(Alpha):
Mirror 1 / Mirror 2
RoCuNo+_v0.2:
Mirror 1 / Mirror 2
RoCuNo+_v0.3:
Mirror 1

Problems:
i got some problems with dumping boot.img. the partiton size is 16M and the dd dump is also 16M but if i try to flash it back fastboot says the file is to large for partition. thats why unroot doesent work for now. Magisk patch the boot.img and resize them to 8M. than flashing works fine and all works. if someone can point me in the right direction would be very nice. if you have some questions please write here or pm me.
if someone can make a scatter file for this phone or had the scatter file it would be nice to share so we can try to backup the phone with SP Flash Tool. thanks.
if you found some bugs please tell it here so i can fix it.

Nice

Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)

Matthius said:
Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)
Click to expand...
Click to collapse
not now. i hope that someone can make an TWRP or CWM for the Cubot and share it with us.

Matthius said:
Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)
Click to expand...
Click to collapse
did you use the RoCuNo+ Programm or have you done all by yourself ? what do you use ? step by step or the AIO routine ?

Schwester_Gabi said:
did you use the RoCuNo+ Programm or have you done all by yourself ? what do you use ? step by step or the AIO routine ?
Click to expand...
Click to collapse
I had already unlocked the bootloader myself prior to this, looking for a way to root it before I saw this article (I gather this is the first available root method for this device), and also manually installed MagiskManager and the MTK-Engineering-Mode apk's and from then on I used the ruCuNo+ bat to complete it.
I followed stage 6, then 7, then 3. Pointed the Magisk to the original boot img, got it patched, sent it to PC and flashed the boot image with ADB. After turning on the phone, Magisk ended up with two green ticks so everything was good to go.
{
"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"
}

Matthius said:
I had already unlocked the bootloader myself prior to this, looking for a way to root it before I saw this article (I gather this is the first available root method for this device),
Click to expand...
Click to collapse
yes it is. i searched over a week to find a root solution but nothing found. so i make it by my self and want to share this with the world :highfive:
Matthius said:
and also manually installed MagiskManager and the MTK-Engineering-Mode apk's and from then on I used the ruCuNo+ bat to complete it. I followed stage 6, then 7, then 3. Pointed the Magisk to the original boot img, got it patched, sent it to PC and flashed the boot image with ADB. After turning on the phone, Magisk ended up with two green ticks so everything was good to go.
Click to expand...
Click to collapse
thats also a way :good: maybe i implement this for users who already unlockt the bootloader. then the the phone must not be factory reset again. :good: thanks for telling me this way i dont think of bevor

Schwester_Gabi said:
yes it is. i searched over a week to find a root solution but nothing found. so i make it by my self and want to share this with the world :highfive:
thats also a way :good: maybe i implement this for users who already unlockt the bootloader. then the the phone must not be factory reset again. :good: thanks for telling me this way i dont think of bevor
Click to expand...
Click to collapse
No worries, great work - hopefully, we may see some custom recovery to come in the future from someone. Wish this phone actually had its own page on XDA, but I doubt it has enough widespread support for that, who knows.

Matthius said:
No worries, great work - hopefully, we may see some custom recovery to come in the future from someone. Wish this phone actually had its own page on XDA, but I doubt it has enough widespread support for that, who knows.
Click to expand...
Click to collapse
Yes. custom recovery for the phone would be great. if I knew better, I would make one myself. but I've read a lot. maybe I'll try it in future to make one.
i think this phone dont get his own page. but maybe the Cubot vendor get his own where we can put all related Cubot threads together in his own sub section. :good:

i got a error after "fastboot oem unlock" -> "FAILED (remote:Unlock operation is not allowed)". i think, bootloader is not unlocked, what can i do?
oops: had forget "OEM UNLOCKING in DevMenu"

spunky1a said:
i got a error after "fastboot oem unlock" -> "FAILED (remote:Unlock operation is not allowed)". i think, bootloader is not unlocked, what can i do?
oops: had forget "OEM UNLOCKING in DevMenu"
Click to expand...
Click to collapse
yes. that was the point. :good:

I think the sequence in the Guide is a bit wrong. In the Guide I read:
Schwester_Gabi said:
...
Type:
Code:
adb reboot-bootloader
Than:
Code:
fastboot oem unlock
NOTE: ALL YOUR DATA WILL BE DELETED Press VOL+ on Phone if asked wait for device for unlock...
... (this comes now after)
Enable USB DEBUGGING and OEM UNLOCKING in Menu --> Settings --> Developer Options
...
Click to expand...
Click to collapse
If I follow this I get (in very small fonts) as another user here in this thread:
Unlock failed...return to fastboot in 3s
Click to expand...
Click to collapse
And no unlock of the bootloader seems possible.
Because first I need to do OEM UNLOCKING in the Dev. Options, which seems very clear. Only after I can fastboot oem unlock
What I further not quite understand in this post, is it either the Guide or the Batchfile I have to follow? Or is it a mixture of both what I need to do?
As I think the Batchfile cannot enable the Developer Tools in the System, or?
Lastly and most important: on my phone I don't see a mmcblk07p only a mmcblk0p7, so this throws an error:
Schwester_Gabi said:
...
adb shell dd if=/dev/block/mmcblk07p of=/sdcard/boot.img
...
Click to expand...
Click to collapse
I guess that mmcblk0p7 is ment, so I did a dd with mmcblk0p7, and I let patch this file with Magisk to the file: patched_boot.img
But here I am very not sure and if I flash now a wrong img-file with this:
Schwester_Gabi said:
...
fastboot flash boot patched_boot.img
...
Click to expand...
Click to collapse
I strongly guess that is it with my new phone
So could you please confirm that it was just a typo in the first post here?
How can I know which of these files in /dev/block is the boot.img?
Thank!!!

francwalter said:
I think the sequence in the Guide is a bit wrong. In the Guide I read:
...
Type: Than:
If I follow this I get (in very small fonts) as another user here in this thread:
And no unlock of the bootloader seems possible.
Because first I need to do OEM UNLOCKING in the Dev. Options, which seems very clear. Only after I can fastboot oem unlock
Click to expand...
Click to collapse
For this Problem the batch says first enable dev options and OEM unlock and than go to next step.
francwalter said:
What I further not quite understand in this post, is it either the Guide or the Batchfile I have to follow? Or is it a mixture of both what I need to do?
As I think the Batchfile cannot enable the Developer Tools in the System, or?
Lastly and most important: on my phone I don't see a mmcblk07p only a mmcblk0p7, so this throws an error:
I guess that mmcblk0p7 is ment, so I did a dd with mmcblk0p7, and I let patch this file with Magisk to the file: patched_boot.img
But here I am very not sure and if I flash now a wrong img-file with this:
I strongly guess that is it with my new phone
So could you pleas confirm that it was just a typo in the first post here?
How can I know which of these files in /dev/block is the boot.img?
Thank!!!
Click to expand...
Click to collapse
Yes. Its a typo. You can flash it.
Btw i am on the way to rework the whole Programm for better use and better instructions. Give me some time because iam very busy at the moment. But I will update it soon.
And remember its an 0.1ALPHA for now. So its not perfect :angel:

Oh Great! It works
Thank a lot for your work!!!

As a noob, I did not get what to do after installing the Magisk manager. So I have it installed, but it shows no root. How can I then install the root?
I used the "RoCuNo+_v0.2.bat" in admin mode and although I got through the unlock and root, I am stuck on what to do on Magisk in the phone.
I was able to root my galaxy tab, but perhaps I am too noob for these instructions?
(Btw while booting I get the "this phone is unlocked and cannot be trusted" text)

Ran into a bit of an issue here, I received an official OTA so I uninstalled Magisk by clicking uninstall within the APK, now my phone is stuck on the boot logo. I've tried to flash the original boot img, but I can't get into the system to confirm flashing it on the device. It displays under <adb devices> but when issuing the <fastboot flash boot> command it says <waiting for any device> and nothing occurs.
Not sure how to proceed without wiping the whole thing. Anything I can try?

So I did a factory reset and used the "RoCuNo+_v0.2.bat" again as follows:
First enabled developer mode, USB Debugging unknown sources, OEM unlock
Then ran the tool:
1 - unlock bootloader - success
3 - root - success
5 - install magisk - here the phone first boots, then it erases data, then does again all the "setup your phone, wifi, accounts etc"
"Orange state - this device is unlocked..." appears in the boot
Magisk is not installed in the apps.
OEM unlock is greyed out (but enabled)
So the tool worked differently, or I am missing something.
Perhaps there are new versions of this phone?

...aaaand it's rooted.
I did everything again using the adb -command instructions.
So did not use the .bat tool.
Used the step-by-step instructions.
Thanks a lot! Finally I can use macrodroid properly.

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!

Bricked after Downgrade to Pie, adb not working, pls help

[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"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"
}
Any thoughts please?

I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.

akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.

strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)

who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.

TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.

who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition

[UNOFFICIAL]TWRP 3.6.0 for Infinix Zero 8/8i X687/X687B

{
"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"
}
Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. Started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of features. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Rich (BB code):
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or
you are getting fired because the alarm app failed. Please do some research if
you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me
for messing up your device, I will laugh at you.
Key Features:
Custom Firmware installation
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Backups of partitions in TAR or raw Image format
Ability to choose which partitions to back up and which to restore
Restore backups from internal storage, external SD storage or OTG devices
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Partition wiping
File Manager(copy, move, rename, delete etc)
Terminal access
ADB Root Shell
Onscreen keyboard
Easy selection of internal/external storage
and more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. TeamWin call this scripting engine OpenRecoveryScript.
Working
Decryption
MTP
fastbootd
USB OTG
Not Working
Decryption in Android 12
If you encounter any that are not listed, do let me know here
Download
For Infinix Zero 8 X687 https://androidfilehost.com/?fid=17825722713688252724
For Infinix Zero 8i X687B https://androidfilehost.com/?fid=17825722713688253090
Instructions
Unlock Bootloader
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery TWRP.img
See this guide for flashing GSI
Credits
TWRP Lead Developers:- Dees_Troy, bigbiff and Captain_Throwback
@mastersenpai05 for initial TWRP at here
@kusti420 for all the testing
@lopestom for helping a lot in decryption
Sources
TWRP Sources
TWRP Gerrit Instance
TWRP Website
Device Tree

Pro

mastersenpai05 said:
Pro
Click to expand...
Click to collapse
indeed

can it work for x687b

flash done
but when install any file like disable dm_verity got error...
and when install update.zip got error .. the file for x687b and the phone seen as x687
can i change that ?

Neutrino656 said:
flash done
but when install any file like disable dm_verity got error...
and when install update.zip got error .. the file for x687b and the phone seen as x687
can i change that ?
Click to expand...
Click to collapse
Take screenshot and give recovery.log with below command
adb pull /tmp/recovery.log
Thanks

here it is
recovery.log - dcb6c593
Starting TWRP 3.5.2_10-MASTERSENPAI-48d9d47e on Thu Aug 12 13:55:58 2021 (pid 357) RECO - dcb6c593
controlc.com

How to unlock bootloader ?

Blacxx said:
How to unlock bootloader ?
Click to expand...
Click to collapse
You need to enable the developer option to activate OEM unlock and USB Debugging
To enable the developer option, Go to your Settings -> About phone -> Now tap on the Build Number 7-8 Times until you see a toast message “You are now a developer!“
Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
Download and Extract the Downloaded ADB fastboot Zip file on your PC.
Now connect your phone to the computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
Now type the command in your command windowadb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloaderadb reboot bootloader
Once your phone reboots into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers correctly installed.
Now enter the command given below to verify whether your device is been connected properly to PC."fastboot devices"
This command will list the connected devices. If your phone’s serial number shows up, you are good to go and may continue. If the phone is NOT listed, this indicates that your drivers are not installed correctly. To keep the setup, you must fix your drivers to list your device under fastboot devices.
If the phone is recognized by the command above, proceed to boot into bootloader by tapping down the volume down button on your phone and select the BOOT TO DOWNLOAD MODE option with power key. Now you can unlock the bootloader with the following command: Remember that this step will wipe EVERYTHING off the phone."fastboot flashing unlock"
Notably, if this command does not work you can try to use the below command:"fastboot oem unlock"
You will get a confirmation on your Android device’s screen, Navigate to yes and hit the Power button to unlock the bootloader of your device.
Once the bootloader is unlocked, your smartphone will automatically reboot into bootloader mode.
Now again you can enter the command to reboot your device to the system "fastboot reboot"
Your Android device will now reboot and during this, all data will be erased.
That’s It!
That’s all you have to do to unlock the bootloader

Neutrino656 said:
here it is
recovery.log - dcb6c593
Starting TWRP 3.5.2_10-MASTERSENPAI-48d9d47e on Thu Aug 12 13:55:58 2021 (pid 357) RECO - dcb6c593
controlc.com
Click to expand...
Click to collapse
Same specs right?

mastersenpai05 said:
Same specs right?
Click to expand...
Click to collapse
yes
the changes in device name and fingerprint

Neutrino656 said:
You need to enable the developer option to activate OEM unlock and USB Debugging
To enable the developer option, Go to your Settings -> About phone -> Now tap on the Build Number 7-8 Times until you see a toast message “You are now a developer!“
Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
Download and Extract the Downloaded ADB fastboot Zip file on your PC.
Now connect your phone to the computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
Now type the command in your command windowadb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloaderadb reboot bootloader
Once your phone reboots into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers correctly installed.
Now enter the command given below to verify whether your device is been connected properly to PC."fastboot devices"
This command will list the connected devices. If your phone’s serial number shows up, you are good to go and may continue. If the phone is NOT listed, this indicates that your drivers are not installed correctly. To keep the setup, you must fix your drivers to list your device under fastboot devices.
If the phone is recognized by the command above, proceed to boot into bootloader by tapping down the volume down button on your phone and select the BOOT TO DOWNLOAD MODE option with power key. Now you can unlock the bootloader with the following command: Remember that this step will wipe EVERYTHING off the phone."fastboot flashing unlock"
Notably, if this command does not work you can try to use the below command:"fastboot oem unlock"
You will get a confirmation on your Android device’s screen, Navigate to yes and hit the Power button to unlock the bootloader of your device.
Once the bootloader is unlocked, your smartphone will automatically reboot into bootloader mode.
Now again you can enter the command to reboot your device to the system "fastboot reboot"
Your Android device will now reboot and during this, all data will be erased.
That’s It!
That’s all you have to do to unlock the bootloader
Click to expand...
Click to collapse
Its need driver ?

Blacxx said:
Its need driver ?
Click to expand...
Click to collapse
Infinix Zero 8i USB Driver for Windows (Official Mobile Driver)
Download the official Infinix Zero 8i USB Driver for your Infinix Mobile. We also provide all other Infinix Mobile drivers for free.
gsmusbdriver.com

Neutrino656 said:
Infinix Zero 8i USB Driver for Windows (Official Mobile Driver)
Download the official Infinix Zero 8i USB Driver for your Infinix Mobile. We also provide all other Infinix Mobile drivers for free.
gsmusbdriver.com
Click to expand...
Click to collapse
Ok thanks bro

Neutrino656 said:
here it is
https://controlc.com/dcb6c593
Click to expand...
Click to collapse
Thanks, will fix it later. I am somewhat busy right now. If you get any other issue too, please do let me know with logs.

sure

Neutrino656 said:
sure
Click to expand...
Click to collapse
Here is the update.zip flashing fixed build. https://oshi.at/seHmaB
Test it and let me know.
also, in recent Android versions, disabling dm-verity needs to flash vbmeta.img like fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
So don't use that dm-verity disabler
Thanks

HemanthJabalpuri said:
Here is the update.zip flashing fixed build. https://oshi.at/seHmaB
Test it and let me know.
also, in recent Android versions, disabling dm-verity needs to flash vbmeta.img like fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
So don't use that dm-verity disabler
Thanks
Click to expand...
Click to collapse
can i flash it via recovery or i must flash via fastboot

i have disabled verity and verification before
is that ok or i have to do it again ..
every time i flash a file

Neutrino656 said:
can i flash it via recovery or i must flash via fastboot
Click to expand...
Click to collapse
You can flash recovery in either fastboot or existing cuatom recovery or in rooted rom.
For vbmeta, only use fastboot mode with above command.
Also as long as vbmeta is not back to stock(i.e., when you flash stock rom) you don't need to flash again and again.
Flashing once is enough.
Thanks