Related
(I'm running CM 6.1)
I recently tried to use Titanium Backup to delete Gmail from my phone so I could install the new version (it kept giving me an error during installation), but when the phone reset to complete the uninstallation it gets stuck at a screen that shows an Android coming out of a box with a progress bar at the bottom. The bar fills up to about a quarter then flashes and restarts again. I can hit some buttons and this text comes up:
ClockworkMod Recovery v.2.5.0.1
Finding update package...
Opening update package..
Verifying update package..
Installing update..
(then it restarts)
This is preventing me from booting into recovery, or doing a hard reset, or anything really. It comes up right away when I start my phone up. Has anybody had any experience with this? Please tell me there's a way around this..
EDIT: ISSUE SOLVED!
This was pretty easy to get around, I wasn't too familiar with adb so it made it pretty difficult.
-Download a new recovery ROM if necessary
-Move the image to your android-sdk/platform-tools folder
-open up a command prompt, navigate to the platform-tools folder and enter the following code
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard/
adb flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb reboot recovery
-Then when that reboots your phone it should put you back into the recovery ROM and from there you can access your phone as usual.
i had a problem similar to this when trying to upgrade to a froyo rom (it wasn't a boot loop, but the progress bar would get about halfway and then freeze). i started the phone and held 'home' and 'back' and selected 'clear data' and then was able to reinstall. i see a lot around here that people have problems if their battery is too low as well...so if you're under 30% you might try charging and trying again
The problem is that I can't do anything when it boots up because it goes right to this progress bar screen, holding Home+back then Power doesn't do anything, same with any other button combination. Also the battery's at 100%, I charged it overnight to see if that was the problem but it didn't help.
Remove the battery, put it back in, hold down the home button when you start the phone - that should take you into recovery.
It doesn't though, when I say nothing works I mean nothing works. I've booted into recovery many times before but now this screen comes up every time I start it regardless of what button combination I try.
Then your only option would be to RUU and re-root. Have you tried that?
I just tried, but my phone is basically in a vegetative state right now, my computer doesn't recognize it when it's plugged in because of this loading screen thing that keeps repeating. I was thinking about getting a new phone for Christmas, maybe this is a sign
explosivo98 said:
I just tried, but my phone is basically in a vegetative state right now, my computer doesn't recognize it when it's plugged in because of this loading screen thing that keeps repeating. I was thinking about getting a new phone for Christmas, maybe this is a sign
Click to expand...
Click to collapse
assuming that the power light comes on when you have it plugged in, you should be able to get it going. boot into fastboot (vol down and power) and then you should be able to either get to recovery, or push adb commands from there to get it working again. I have never had to do this, but I have seen others report victory after using these methods. here are 2 threads about adb
http://forum.xda-developers.com/showthread.php?t=690362
http://forum.xda-developers.com/showthread.php?t=532719
good luck
I should be able to boot into recovery but it still goes to this install process that restarts indefinitely no matter how many ways I try to start it up. I tried Power+Home, Volume down+power, Home+back then power, but this installation screen comes up every time. When I plug it into the computer it's being charged, but it never recognizes it as being connected. So basically I can't flash or do a Nandroid backup (which I would usually do in this situation) because I can't access any of the tools to do it.
vol down and power doesn't get you to fastboot (NOT recovery) ?
explosivo98 said:
I should be able to boot into recovery but it still goes to this install process that restarts indefinitely no matter how many ways I try to start it up. I tried Power+Home, Volume down+power, Home+back then power, but this installation screen comes up every time. When I plug it into the computer it's being charged, but it never recognizes it as being connected. So basically I can't flash or do a Nandroid backup (which I would usually do in this situation) because I can't access any of the tools to do it.
Click to expand...
Click to collapse
did you read the second link? it says this:
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next lineNow you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
The device is showing up weird on the list, and none of the commands seem to be working. Here's what it looks like
{
"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"
}
Oops, not quite what I was trying to show there. I tried adb reboot recovery but after rebooting the phone still starts in this install process for Clockworkmod. I tried putting the update file on the SD card using adb but that didn't work either.
explosivo98 said:
Oops, not quite what I was trying to show there. I tried adb reboot recovery but after rebooting the phone still starts in this install process for Clockworkmod. I tried putting the update file on the SD card using adb but that didn't work either.
Click to expand...
Click to collapse
download a different recovery like amon ra and try to install that thru adb, then reboot recovery
EDIT: if I read that post of your cmd box correctly it looks like you lost superuser, right? get the apk and push it thru adb, then get the recovery and then try to reboot into recovery.... report back.
il Duce said:
download a different recovery like amon ra and try to install that thru adb, then reboot recovery
EDIT: if I read that post of your cmd box correctly it looks like you lost superuser, right? get the apk and push it thru adb, then get the recovery and then try to reboot into recovery.... report back.
Click to expand...
Click to collapse
The installation of recovery files always needs me to boot into my current custom recovery, which I can't do. I have SU permissions, that post wasn't really what I wanted to show. I tried to reboot into recovery but the phone always reboots right back into the install that I'm stuck on.
explosivo98 said:
The installation of recovery files always needs me to boot into my current custom recovery, which I can't do. I have SU permissions, that post wasn't really what I wanted to show. I tried to reboot into recovery but the phone always reboots right back into the install that I'm stuck on.
Click to expand...
Click to collapse
you really ought to read the threads I posted. these are not "recovery files" as you call them. It tells you how to do this with commands in fastboot, you do not need to boot into your recovery, it should work in fastboot, here is yet another link to a thread, I leave you to your reading, the answers are there, specifically how to to what you are trying to while in fastboot, not in recovery.
http://forum.xda-developers.com/showthread.php?t=517874
Fastboot doesn't recognize the phone as plugged in, all the adb commands seem to work but when I try anything with fastboot it hangs at <waiting for devices>. I also checked the device list and it showed none.
explosivo98 said:
Fastboot doesn't recognize the phone as plugged in, all the adb commands seem to work but when I try anything with fastboot it hangs at <waiting for devices>. I also checked the device list and it showed none.
Click to expand...
Click to collapse
Make sure Fastboot is working
Open up Command Prompt
type the following
Code:
cd C:\android-sdk-windows-1.5_r2\tools === Press Enter
fastboot devices === Press enter, your device should be listed
fastboot shell === You should see a # in the next line
type fastboot and press enter for general commands
Fastboot is definitely working, here's what it looks like (note how it doesn't detect any device)
But adb works fine with the phone:
Oh sweet jesus I finally fixed it. Pushed the new recovery image to it and flashed it, then reboot recovery worked. Thanks for all the help!
explosivo98 said:
Oh sweet jesus I finally fixed it. Pushed the new recovery image to it and flashed it, then reboot recovery worked. Thanks for all the help!
Click to expand...
Click to collapse
Nice work! Now please post a detailed step by step of HOW you did it here, and then save this thread as a favorite so you can help the next person in a similar spot! Glad you finally got it.
sent from my hero, which no longer sucks ass
Hi!
I´ve got problem with my MM... I want to sell it, but i can´t do hard reset to delete my email account. If I holt Power + X, there is a triangle for a while it is loading, but suddenly stops and starts mobile normaly... If I do reboot to recovery Its only restart... If i go to setting and click factory reset, it do nothing... So I can´t go to recovery.. Have anybody some advice? (sry 4 my English)...
Motorola milestone 2.3.4 cm7
Ensure you have update.zip on your sd
No I haven´t... I´m not sure, what update to copy to sd... Because I haven´t got update.zip of the Rom wich I have in phone.. U think, I can copy some update to sd and flash it with terminal?
EDIT: I tried to flash custom recovery image with terminal... but i write read only... :/
According to your first post you are on CM7
According to your second one looks like for some reason the update.zip has been removed from your sd so you can't get into OpenRecovery.
Try to serach the forum for OR reinstall manual, you can even find link to OR page in the first post of the CM7 firmware
Yes, it was it! I copy new OR folder to sd than a could go back to recovery.. THANK YOU SO MUCH
u have 2 figure out how to get recovery installed in your MM.
such as 'update.zip' should be copyed 2 your sdcard.
and then when u get into triangle ,choose the 'apply update.zip',thats what so called recovery ui.
hope can help u~
Motorola Milestone Hard reset
To reset your phone to factory settings it will erase all
Data on your phone like image contact sms video and application so make sure to delete your data or you may backup your date by pc after that do the following step
, touch Menu > Settings
> Privacy > Factory data reset > Reset phone.
Warning: All data on your phone will be deleted.
Motorola Milestone Hard reset with keys
Power off device. Press camera key + power key for about 10-12 sec (even 15 sec) (You will see Motorola logo then a
Yellow exclamation point in a white triangle.)
push both (1st) Volume UP + (then) camera key in this order for Android System Recovery menu.
{
"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"
}
Select Wipe / Factory reset with Volume down key (or with D pad) then push POWER key (or CENTER D Pad) to hard reset.
read about Crash recovery – Restarting Motorola Milestone here motoask.com/motorola-droid-general-discussion-f31/how-to-hard-reset-of-motorola-milestone-t3059.html
jakson0100 said:
Motorola Milestone Hard reset
To reset your phone to factory settings it will erase all
Data on your phone like image contact sms video and application so make sure to delete your data or you may backup your date by pc after that do the following step
, touch Menu > Settings
> Privacy > Factory data reset > Reset phone.
Warning: All data on your phone will be deleted.
Motorola Milestone Hard reset with keys
Power off device. Press camera key + power key for about 10-12 sec (even 15 sec) (You will see Motorola logo then a
Yellow exclamation point in a white triangle.)
push both (1st) Volume UP + (then) camera key in this order for Android System Recovery menu.
Select Wipe / Factory reset with Volume down key (or with D pad) then push POWER key (or CENTER D Pad) to hard reset.
read about Crash recovery – Restarting Motorola Milestone here motoask.com/motorola-droid-general-discussion-f31/how-to-hard-reset-of-motorola-milestone-t3059.html
Click to expand...
Click to collapse
Hi I have a similar problem...sort of...
I wish to reset the phone to sell, I'm not fussed if it is stock rom or not, but still need to do a factory reset of sorts.
Now the difficult bit...the backlight has gone (new screen is around £15 but don't have time to mess around with it). However without the backlight it is difficult to see what is happening on screen (you can just see the menus but the problem is the recovery menu it is too small to read).
Similar to the poster above, the factory reset from within android settings does nothing, so recovery menu is probably my only option.
Therefore, can someone tell me button sequence to perform a factory reset (i.e. which menu item in recovery is "Wipe / Factory reset" and what confirmations follow it - I can see which line is selected but can't read anything).
Alternatively, since I can access via ADB and remotely view the screen, what is the fix to the factory reset within Android. Using HO!NO!CM7.2.0RC0 ROM.
Thanks.
Ok, two menu position down...is the answer, I think.
EDIT: Nope, that didn't work...still have background image etc still present.
Will I need the update.zip in order to perform a full reset too?
AnandMore's How-To Guide For Beginners
Xiaomi Redmi 2
{
"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"
}
Intro:
This thread will serve as a location for basic how-to guides for the Xiaomi Redmi 2. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index:
Post #1 - Rooting your Redmi 2
Post #2 - Flashing Custom Recovery
Post #3 - Flashing Custom ROMs
Post #4 - Flashing Custom Kernels
Resources:
Everything you need for Xiaomi Redmi 2 is available in the below given thread -
[INDEX] Xiaomi Redmi 2
Rooting your Redmi 2:
This guide will root your device through Stock MI Recovery(Works with TWRP also), but this is not Native Root. A new app named SuperSU will be installed, which will give root Permission.
Note:
Rooting does not Void Warranty.
Caution:
This is a safe process, but I am not responsible for anything bad that happens to your phone.
In most cases this approach of rooting should not block OTA updates.
Steps to follow for rooting:
Download the Root.zip and Copy the file to the folder 'Internal storage' (root of internal storage).
(File at the end of thread)
Open the Updater app, Press the 3 dots at Right Top Corner, A menu will open. Tap on “Choose Update Package“ and select the Root.zip File.
Wait until device will reboot.
After reboot a new app SuperSu will be installed.
Open the app and Choose "Continue".
Choose "Normal", Don't Choose TWRP/CWM, device will go into Boot Loop.
Note - Don't Choose TWRP/CWM, it will brick your device.
After sucessful updation , press ok.
Your Phone has now Root Permission.
Open any app using Root permission and SuperSU will ask for Permission.
Enjoy your rooted Redmi 2.
Un Root The Device:
For Un Root , open the SuperSU app,tap on Settings, Choose Full Unroot.
Your Device is Un Rooted Sucessfully. The SuperSU app will be removed.
Flashing Custom Recovery:
From Mobile:
Install Flashify app from Playstore
Once installed, access the application through app drawer.
Allow root access now and get navigate to Flashify’s home screen.
First take a backup of your recovery in case something goes wrong. (RECOMMENDED)
Now tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.
After successful flashing it will ask you to reboot your device.
Done! You have custom recovery on your phone.
From PC:
Enable USB debugging, go to settings>about phone and then tap on Android/MIUI version 5 times. Developer Options will be enabled. Now go back to settings>Developer options and enable USB debugging.
ADB and Fastboot Drivers installed on your PC. I can provide you the drivers but it would be a better option to install MiFlash to get all the necessary drivers and Miflash software with you for future use.
Install Miflash on your PC. Lets suppose we installed it in C:\Xiaomi folder.
You can see two folders, proceed to "adb' folder
Then proceed to "Google" folder.
Proceed to "Android" Folder.
We are at our destination.
Now Hold down "Shift" button on your computer keyboard and right click with mouse on an empty part of the window. You will see that in the menu that appears, you have an option - "open command window here". Click on that
To verify if ADB is working and installed correctly, type "adb version" in the command window that opened without the code. You should get the adb version which means its working fine.
Turn off your Phone. When its completely switched off, press and hold "Volume Down" and "Power" button together and then the phone will turn on in Fastboot mode.
Use the USB cable to connect Phone to PC.
Copy the Recovery.img in the Android folder where we are running the Command prompt. (C:\Xiaomi\adb\Google\Android in my case as i installed Mi flash in C:\Xiaomi folder)
Now go back to command promt and enter the following commands -
Code:
fastboot devices
Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command to flash recovery image -
Code:
fastboot flash recovery recovery.img
Once you enter this command, the recovery image will be flashed on your device. Once it is completed, enter the final command to reboot your phone -
Code:
fastboot reboot
Your phone will reboot.
You have have now completed flashing custom recovery replacing Stock Mi recovery on your Xiaomi Redmi 2.
Flashing custom ROMs:
Steps to Follow:
Download and transfer the custom ROM you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
Select “Wipe” from TWRP main menu and do a “Swipe to Factory Reset” on the bottom of screen.
Note: This will factory reset your device. If your custom ROM doesn’t require a factory reset, then simply skip this step.
Go back to TWRP main menu, tap on “Install” and select the custom ROMs .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom ROM installation process. This may take some time.
Once your ROM is successfully flashed, you’ll see “Wipe cache/dalvik” option, select it and then do “Swipe to wipe” on bottom of screen.
Once cache & dalvik wipe completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom ROM you just flashed. Since this will be the first reboot after flashing a new ROM, it might take some time to rebuild cache and finish boot, have patience.
Flashing Custom Kernels:
Steps to Follow:
Download and transfer the custom Kernel you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
In the TWRP main menu, tap on “Install” and select the custom Kernel .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom Kernel installation process. This may take some time.
Once flashing completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom Kernel you just flashed. Since this will be the first reboot after flashing a new Kernel, it might take some time to rebuild cache and finish boot, have patience.
For list of all available Roms visit this thread :
http://forum.xda-developers.com/redmi-2/how-to/available-custom-marshmallow-roms-redmi-t3278535
Click to expand...
Click to collapse
Better if you make lollipop ROMs thread too
Superb work bro thanks ...u
Isn't MIUI rooted out of the box already? [emoji52]
Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
Developer ROMs are. Global ROMs aren't.
Device comes with global ROM :3
noobpremium said:
Better if you make lollipop ROMs thread too
Click to expand...
Click to collapse
I made both lollipop and marshmallow roms in one thread. So you think i should make seperate one for lollipop.
Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
All roms(Beta,developer,stable) for Redmi 2 are not Pre rooted.
Added videos tutorials for better understanding.
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
my phone also rebooting. please help me. how to go to recovery?
srmohanrajan said:
my phone also rebooting. please help me. how to go to recovery?
Click to expand...
Click to collapse
1) Switch off the phone.
2) Press the Volume Down, Volume Up and the Power Button at the same time, about 2-3 seconds until the mi logo shows up.
3) Recovery mode menu will appear.
Fr3ak23 said:
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
Click to expand...
Click to collapse
Follow the same steps to boot into recovery and flash SuperSU v2.4.6 zip via recovery
(And remember you are responsible if anything happens to the device)
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Fr3ak23 said:
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Click to expand...
Click to collapse
No problem bro !
✌
Great !
New CM 12.1 is awesome, finally the camera works
I am curious on why I keep on losing root access. I never had that issue with any other phones and custom ROMs.
This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Code:
adb reboot bootloader
fastboot oem unlock
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Code:
adb reboot bootloader
fastboot flash recovery TWRP-PB2-650_3.0.2.img
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.
First boot into recovery (757):
{
"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"
}
Mount System RW (102):
File Manager 1 (010):
File Manager 2 (019):
Install SuperSU (243):
Celebrate
third post reserved for whatever
fourth post reserved for whatever
fifth post reserved for whatever
is this working for phab2 pb2-650m?
I assume so. The original work was based on a 650M but I can only validate my additions on the 650Y since I don't have a 650M
Synman said:
This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.
Click to expand...
Click to collapse
You should make a video of the procedure. So you are saying after flashing the recovery, have to press power and volume up+down together until phab2 posts. What is posts? Do you mean reboots? And what do you mean by roll the finger?
Synman said:
This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Code:
adb reboot bootloader
fastboot oem unlock
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Code:
adb reboot bootloader
fastboot flash recovery TWRP-PB2-650_3.0.2.img
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.
Click to expand...
Click to collapse
Hey thank you for the method. My device is PB2-650m Philippine version. Twrp recovery installed without issue , but after flashing supersu, would not boot. Stuck on second boot. I flashed UPDATE-unSU.zip to unroot and factory reset device. Flashed SuperSu-v2.79 and rooted without issue.
Too bad you didn't make a video...
Synman said:
Too bad you didn't make a video...
Click to expand...
Click to collapse
I did not have time. My phone got stuck on 2nd boot and was trying to figure out way to fix it. I fixed it by deleting supersu and factory resetting. I found different SuperSU version and worked. Thanks to you for providing me and the other phab2 owners with custom recovery.
Anyone get voLTE to work on this phone (PB2-650Y)?
query
http://support.lenovo.com/in/en/products/Tablets/PHAB-Series/PHAB2/downloads/DS118503
Did anybody flash PB2-650M OTA update. If you did, is there a way to flash it on rooted device?
thanx
thanx 4 news, got updated just niw 1.4 gb approx. Lets see.
stock rom for pb2-650m
I bought this phone last month. I gonna root my device and install twrp recovery. before that i wanna know whether stock rom available for this? if yes, please share me the link.
l.a.s.
Was searching for it, Lenovo smart assistant etc.. but couldn't find one.
I tried "adb" command in Linux. But not working. Saying "????? No permission". If anyone having USB driver means please share it with me.
lenovo companion appi installed above app,
I nstalled above app, and in search found mobile assistant appfor lenovo, guess it automatically installed usb driver s
Adb command working. And also I unlocked my bootloader. Gonna flash twrp. Any custom ROM for this device?
Stock Android 6.0.1 Marshmallow for TextNow
Device Compatibility: Moto G (3rd Gen) 2015 (xt1548 ONLY)!
Android Version: 6.0.1
Build No. MCI24.107-70
System Version: 24.62.70.osprey_sprint.sprint.en.US.sprint
Kernel Version: 3.10.49
Baseband: M8916_2020632.44.321.54R
Carrier/Provider: TextNow (Sprint MVNO Subsidiary)
Android Security Patch Level: January 5, 2017
Build Version SDK: 23
PRL Version: 25060
ROM & FIRMWARE FILES:
DOWNLOAD LINK: https://drive.google.com/folderview?id=0B7-zQU1VihD3aHZ4N1VJelY0d2c
This link provides download access to the following files: bootloader.img, gpt.bin (Partition Updater), NON-HLOS.bin (Modem, AKA "Baseband"), fsg.bin (Radio Firmware), recovery.img (Stock 6.0.1 Recovery), boot.img (Stock 6.0.1 Kernel/Ramdisk), system.img_sparsechunk files (a series of /system image files which, when flashed, comprise the ROM itself) An executable flash-all.bat file is also included, which is basically a script instructing fastboot as to each and every partition to be flashed.
Because the TextNow Moto G3 was shipped with Android 5.1.1 firmware, and because no firmware update or OTA has since been released for the TextNow variant, many key firmware components are outdated (e.g., Baseband, Bootloader, Partition Index, Radio Firmware, WLAN Drivers, etc). I have compiled this stock MM ROM in fastboot flashable format to ensure that all relevant firmware partitions are updated during installation of the stock ROM. Future releases of this ROM, which will center on bug fixes and stability improvements, will be compiled in TWRP flashable zip format.
REQUIREMENTS & INSTRUCTIONS:
1. An Unlocked Bootloader;
2. A Windows PC or Mac;
3. The Android SDK Platform Tools, or, preferably, the latest version of Minimal ADB & Fastboot. Download the program from this link for Windows PC and install once download is complete. https://drive.google.com/file/d/0B7-zQU1VihD3TnhTNVVVZGZ4bVU/view?usp=drivesdk
4. On your PC or Mac, install the most recently released version of "Motorola Device Manager." This piece of software installs and periodically updates the correct USB Drivers for your Motorola smartphones or tablet. A current version can be downloaded here, on the Motorola/Lenovo website: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
5. Power on and allow your Moto G3 to boot into the OS. Go to SETINGS, then select ABOUT PHONE, find BUILD NO. and tap it approximately 7 or 8 times until you see a toast confirming that DEVELOPER OPTIONS is enabled. In DEVELOPER OPTIONS, enable OEM Unlocking and USB Debugging.
6. Once you have downloaded the stock ROM installation & firmware files from the above link, place these files on your PC Desktop, in the same directory/path as ADB/Fastboot. Connect your Moto G3 to your PC or Mac using an OEM or high quality equivalent micro USB to USB syncing/charging cable. In your ADB/Fastboot directory, open a command window by holding the SHIFT key and simultaneously right clicking with your cursor in the folder/directory of the path sought. In this instance, the ADB/Fastboot directory would be correct. In the command window type: "adb reboot bootloader" .....Your device should boot into AP Fastboot mode from the Android OS. If it doesn't, you may manually boot into fastboot mode by first powering off your Moto G3. Then, hold Power and Volume Down simultaneously until the recovery menu appears. From recovery (if stock recovery) simply use Volume Down to navigate to Bootloader option then press Power to select. Once in Fastboot Mode, open another command window in the ADB/Fastboot directory, then type,: "fastboot devices". The command window will return with a string of numbers under an entry titled "connected devices". The numbers are actually your device serial number. (If no numbers are returned following the command, or if a prompt appears saying "waiting.....", then your device is not properly communicating with ADB/Fastboot via your PC or Mac. Try switching USB Ports, switching syncing cables and/or uninstalling/reinstalling Motorola Device Manager.
7. Upon establishing a proper connection between your PC and Moto G3, click on and run the executable file titled "flash-all.bat" (located n the directory of files from the below link), sit back & wait a minute or two. Your Bootloader', Partition Index, Modem, Radio Firmware & Stock Recovery will be updated to Stock Android 6.0.1 Marshmallow. Your /system partition will also be flashed with a series of img_sparsechunk files, updating your Android OS to Stock 6.0.1.
** It should be noted here that once your partition index & bootloader have been updated, you will not have the option to downgrade either of these partitions at a later time. In fact, attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick. Your Modem (NON-HLOS.bin) and Radio Firmware (fsg.mbn) may be downgraded with no reported adverse effects.
8. Now, you will need to root your stock Marshmallow OS. (Many of the addon pre-installed applications on this stock ROM require superuser access.) To root the ROM, you will need to flash SuperSU v2.79 systemless root .zip via TWRP recovery. Links for both files are here:
@squid2's TWRP v3.0.2-r5: https://drive.google.com/file/d/0B7-zQU1VihD3ajYwR25xZ3dFT3c/view?usp=drivesdk
@Chainfire's SuperSU v2.79 Systemless Mode zip: https://drive.google.com/file/d/0B7-zQU1VihD3VFBidGk4SjFkQUE/view?usp=drivesdk
9. Upon initial boot, setup, etc., go ahead and update your PRL & Data Profile to ensure your versions are the most recent. Under SETTINGS, scroll down to SYSTEM UPDATES. Turn WiFi off and Cellular Data on. First choose the option to update your PRL. Once successfully updated, choose the update Profile option. A reboot will be necessary in order for these changes to take effect.
Add-ons Included (in /system/apps) & Credits:
TextNow v5.3.0 by TextNow, Inc.
SuperSU v2.79 by @Chainfire
BusyBox v49 by @denys Vlesenko
Fast Cleaner v3.2.8 by the @OPDA Team
Kernel Adiutor-Mod v1.0-07/18/2016 by @yoinx
CyanogenMod 13 File Manager v3.0.0 by The CyanogenMod Team
Google Nexus MM Boot Animation (Dark Theme)
Nova Launcher v 5.0.3 by @teslacoil Software
Candy Icons v2.3.3 @Vukasin Andelkovic
VIPER4ARISE FX v2.5.0.5 by VIPER ACOUSTICS & A.R.I.S.E SOUND SYSTEMS
Esira Music Player v1.0 by @A.R.I.S.E SOUND SYSTEMS
I also want to say a huge thanks to @dearmasfamily for his TextNow based stock Android compilations on the Moto E LTE 2015 (xt1526). His modifications to apns-config.xml and eri.xml on the Moto E LTE were a lifesaver during my network configurations for TextNow on the Moto G3. And thanks to @squid2 for his hard work on custom kernels for Osprey. His detailed explanations on boot image support have given me a much broader understanding of the systemless root methodology. Finally, @ResistanceIsFutile, your keen eye for detail, research, and general editing skills have been invaluable. Thank you.
Sent from my Lenovo TB3-850F using XDA-Developers Legacy app
Also for XT1543 please !
Heyner_Gomez said:
Also for XT1543 please !
Click to expand...
Click to collapse
I agree -- TextNow subscribers would benefit from a stock 6.0.1 MM ROM for the T-Mobile (or GSM unlocked) variant of Osprey. Unfortunately I do not own a xt1543. I would need a device at least tentatively in order to flash & dump firmware partitions for a stock MM build.
Looking Good
Easy to understand and presentation looks very much polished
- Good Job Sir :good:
Hark do I see special editing as well. . .
Build it and they will come
The OP download link for the ROM & Firmware files - if you use the "Download All" tab "top Right" corner there, will Zip all files together in an easy all at once download of them in two zipped parts.
Thank you @ResistanceIsFutile. Been messing around on XDA Forums Premium for Android to create my post. You taught me a great deal on thread composition & I am grateful for it. I'll be linking the ROM & firmware files within an hour or so. Also i will be including a patched boot.img for systemless root support. Simply flash SuperSU v2.79 via TWRP (files to be included in link) and root access should be without issue. My messaging settings are undoubtedly the culprit. Please send me a friend request. I'll fix the PM issue shortly.
@MotoJunkie01 Your certainly welcome, as I've learnt many things from you as well.
Friend request sent out. Don't know why I've waited so long really. I believe your the first.
I see your due a celebration on a couple counts, hope Saturday is the best for you.
RIF
{
"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"
}
I need testers to install and provide input on this.
I'm currently running LineageOS 14.1. I read this bit of your post:
"attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick."
I'm not sure I understand it fully. I apologize if this is a rather basic question, but if I install this from Lineage, will I have any problems? If I choose to install this, what should I avoid in the future to prevent a hard brick?
Thanks for your hard work!
tsakowich6217 said:
I'm currently running LineageOS 14.1. I read this bit of your post:
"attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick."
I'm not sure I understand it fully. I apologize if this is a rather basic question, but if I install this from Lineage, will I have any problems? If I choose to install this, what should I avoid in the future to prevent a hard brick?
Thanks for your hard work!
Click to expand...
Click to collapse
No. You should have no problems at all. In a nutshell, stock firmware packages contain files to flash the bootloader (bootloader.img) and a partition table updater file (gpt.bin). Once these two partitions are updated, downgrading isn't an option. This doesn't mean you can't downgrade a stock ROM, say from 6.0.1 to 5.1.1. Downgrading is no issue at all as long as you avoid bootloader.img and ,gpt.bin.
Installing custom ROMs, like LineageOS, doesn't put you at any risk in this regard. You may upgrade or downgrade at your leisure. My warning in the thread merely cautioned against downgrading the bootloader and partition table in stock firmware packages.
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Then, hold Power and Volume Down simultaneously until the recovery menu appears. From recovery (if stock recovery) simply use Volume Down to navigate to Bootloader option then press Power to select.
Click to expand...
Click to collapse
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Hello @Gravemind2015
I'm limited as I no longer have a Moto G (3rd Gen) 2015 (xt1548).
I've just looked as to the manufactures steps (as these questions interests me).
These are for an External Reset and Clear Cache Partition though, but share common steps,
I couldn't find as steps called out solely to enter Recovery Mode specifically other than these sets of instructions .
External Reset.
https://mobilesupport.lenovo.com/us/en/products/CELL-PHONES/ANDROID-SERIES/MOTO-G-3RD-GEN/documents/MS105537
Android 5.x (Lollipop)/Android 6.x (Marshmallow) External Reset Steps
1.With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
2.Press the Volume Down key to highlight Recovery mode.
3.Press the Power key to restart into Recovery mode.
4.The screen will display an Android robot with a red exclamation mark.
5.While holding down the Power key, press and release the Volume Up key, then release Power.
6.Use the volume keys to scroll to Wipe data/factory reset and press the Power key to select it.
7.Scroll down to Yes - erase all user data and press the Power key to select it.
Clear Cache Partition.
https://mobilesupport.lenovo.com/us/en/Solution/MS112729
Android Version 6.0 (Marshmallow) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Down button. While still holding Volume Down button, press and release the Power button.
3.Press and release the Volume Down button until you reach Recovery Mode.
4.Press and release the Power button to select Recovery Mode. The device will restart. An image of an Android robot with a red exclamation mark will appear.
5.Press and hold the Power button, press the Volume Up button once and then release the Power button.
6.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it. If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Once the cache wipe has completed, press the Power button to select Reboot System Now.
Android Version 5.0 (Lollipop) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Up and Volume Down buttons and the Power button at the same time until the device turns on.
3.From the Boot Mode selection menu, press the Volume Down button to scroll to Recovery and the Volume Up button to select it. The device will restart. An image of an Android robot with a red exclamation mark will appear.
4.Press and hold the Power button, press the Volume Up button once and then release the Power button.
5.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it.
6.If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Press the Power button to select Reboot System Now.
Hope this helps and clears as with what the Moto site instructs.
ResistanceIsFutile said:
Hello @Gravemind2015
I'm limited as I no longer have a Moto G (3rd Gen) 2015 (xt1548).
I've just looked as to the manufactures steps (as these questions interests me).
These are for an External Reset and Clear Cache Partition though, but share common steps,
I couldn't find as steps called out to enter Recovery Mode specifically other than these sets of instructions .
External Reset.
https://mobilesupport.lenovo.com/us...ROID-SERIES/MOTO-G-3RD-GEN/documents/MS105537
Android 5.x (Lollipop)/Android 6.x (Marshmallow) External Rest Steps
1.With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
2.Press the Volume Down key to highlight Recovery mode.
3.Press the Power key to restart into Recovery mode.
4.The screen will display an Android robot with a red exclamation mark.
5.While holding down the Power key, press and release the Volume Up key, then release Power.
6.Use the volume keys to scroll to Wipe data/factory reset and press the Power key to select it.
7.Scroll down to Yes - erase all user data and press the Power key to select it.
Clear Cache Partition.
https://mobilesupport.lenovo.com/us/en/Solution/MS112729
Android Version 6.0 (Marshmallow) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Down button. While still holding Volume Down button, press and release the Power button.
3.Press and release the Volume Down button until you reach Recovery Mode.
4.Press and release the Power button to select Recovery Mode. The device will restart. An image of an Android robot with a red exclamation mark will appear.
5.Press and hold the Power button, press the Volume Up button once and then release the Power button.
6.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it. If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Once the cache wipe has completed, press the Power button to select Reboot System Now.
Android Version 5.0 (Lollipop) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Up and Volume Down buttons and the Power button at the same time until the device turns on.
3.From the Boot Mode selection menu, press the Volume Down button to scroll to Recovery and the Volume Up button to select it. The device will restart. An image of an Android robot with a red exclamation mark will appear.
4.Press and hold the Power button, press the Volume Up button once and then release the Power button.
5.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it.
6.If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Press the Power button to select Reboot System Now.
@MotoJunkie01 states this-
Hope this helps and clears as with what the Moto site instructs.
Click to expand...
Click to collapse
Well, the lenovo support link you provided seems to have the accurate process. Bootloader unlocking page also has the same instructions. [Power off> power+volume down and it goes into bootloader(fastboot) mode rather than to recovery]
Anyways, this will be off-topic for this rom thread so I'd hope someone with access to this particular model with this carrier can test which method is correct Thanks for replying.
Broadcasted from Zeta Reticuli
Removed My own Content
ResistanceIsFutile said:
It could be the hard buttons keying sequences (power and volume) and then the use the Volume button to scroll and then which one (button) is needed to be used to select Recovery.
As I'm remembering getting into Recovery required to do it multiple of times when I had the phone - again using the proper keying of the hard buttons in the right orders.
At Least these buttons are side mounted on Moto's and not on the back as another phone I have.
Click to expand...
Click to collapse
Yes they are hard button combination.
The instructions I outlined (works with my XT1550 ) are the general instructions which are identical in rest of osprey thread except in this tutorial.
I had assumed that the firmware of these models were identical except for radio.
I was just wondering if this model really has a different mechanism or it's just a mistake in original post
Broadcasted from Zeta Reticuli
Gravemind2015 said:
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Hi ©Gravemind2015....thank you for pointing out my clerical error. Instead of "recovery" I should have said "bootloader' or " fastboot" menu in that particular instance. I'll edit the instructions accordingly.
So i can just go and flash this via twrp?
MimzyDesigns said:
So i can just go and flash this via twrp?
Click to expand...
Click to collapse
This build is not a TWRP flashable zip. Needs to be flashed via fastboot. The next release will be TWRP flashable.
I ran flash-all, but now I'm stuck at "fastboot flash -u system system.img_sparsechunk.1"
Had been sitting there for about 30 minutes before I gave up and unplugged to try again. Same result.
Any advice?
Edit:
Error message before it hangs up:
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.247s
tsakowich6217 said:
I ran flash-all, but now I'm stuck at "fastboot flash -u system system.img_sparsechunk.1"
Had been sitting there for about 30 minutes before I gave up and unplugged to try again. Same result.
Any advice?
Edit:
Error message before it hangs up:
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.247s
Click to expand...
Click to collapse
Did the partitions up until that point successfully flash?
This does happen before that as well. But besides boot and sparsechunk.0 everything else works fine.
Edit:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash -u system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.244s