Gentlemen/ Ladies,
Any Pro here? Can anyone tell me step-by-step...NO-BS...how to back-up my android OS + data, here , please !?
I ran into some difficulties...I am trying to fully backup my Nexus 5 at this stage.
I was told I need a few things, 15-seconds ADB installer, SDK , TWP-3.2.1-1
{
"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"
}
When I typed in DOS, in my computer i got a response:
"adb" is not recognized as in internal or external command operable program or batch file
I am having so much problems with that SDK Android thing, ...Someone here at this forum gave me this :
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
What are those SDK Tools/ & Android SDK platform-tools,....? How to get it working for adb error in DOS?
True instructions step by step please.....the above instructions, are no where near from what I saw on screen !
Thank you,
STDupont said:
Gentlemen/ Ladies,
Any Pro here? Can anyone tell me step-by-step...NO-BS...how to back-up my android OS + data, here , please !?
I ran into some difficulties...I am trying to fully backup my Nexus 5 at this stage.
I was told I need a few things, 15-seconds ADB installer, SDK , TWP-3.2.1-1
When I typed in DOS, in my computer i got a response:
"adb" is not recognized as in internal or external command operable program or batch file
I am having so much problems with that SDK Android thing, ...Someone here at this forum gave me this :
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
What are those SDK Tools/ & Android SDK platform-tools,....? How to get it working for adb error in DOS?
True instructions step by step please.....the above instructions, are no where near from what I saw on screen !
Thank you,
Click to expand...
Click to collapse
Using TWRP custom recovery is the best option.
I have a N5 also.
Install adb/fastboot on PC, download TWRP for your device in .img format, rename the TWRP file to "recovery.img", place the recovery.img in your fastboot folder on PC, boot your device into fastboot mode, connect your device to PC, open a cmd terminal on PC.
Then type:
fastboot devices
Then press enter, it should return a serial number, then type:
fastboot flash recovery recovery.img
Then press enter, it should flash the recovery, then type:
adb reboot recovery
Then press enter, it should reboot device into TWRP. Then select the "Backup" option in TWRP, on the next screen, select the partitions you want to backup, then swipe the slider, then you'll have a backup of everything you want to backup. To restore the backup, boot into TWRP and select "Restore" then find your backup and restore it.
Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage, to ensure that the backup does not get lost, corrupted or wiped accidentally, I recommend storing a copy of the backup on PC or some other external storage(flash drive, external hard drive, etc..).
Sent from my LGL84VL using Tapatalk
Droidriven said:
Using TWRP custom recovery is the best option.
I have a N5 also.
Install adb/fastboot on PC, download TWRP for your device in .img format, rename the TWRP file to "recovery.img", place the recovery.img in your fastboot folder on PC, boot your device into fastboot mode, connect your device to PC, open a cmd terminal on PC.
Then type:
fastboot devices
Then press enter, it should return a serial number, then type:
fastboot flash recovery recovery.img
Then press enter, it should flash the recovery, then type:
adb reboot recovery
Then press enter, it should reboot device into TWRP. Then select the "Backup" option in TWRP, on the next screen, select the partitions you want to backup, then swipe the slider, then you'll have a backup of everything you want to backup. To restore the backup, boot into TWRP and select "Restore" then find your backup and restore it.
Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage, to ensure that the backup does not get lost, corrupted or wiped accidentally, I recommend storing a copy of the backup on PC or some other external storage(flash drive, external hard drive, etc..).
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,
Thank you so much for yr reply, I truly appreciated, I MEAN IT !
Just a few things for confirmation:
-"place the recovery.img in your fastboot folder on PC"..........I take it after I download &installation TWRP on my PC, there will be a fastboot folder on my PC, right?
-"Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage"......
Thank you very much !
STDupont said:
Hello,
Thank you so much for yr reply, I truly appreciated, I MEAN IT !
Just a few things for confirmation:
-"place the recovery.img in your fastboot folder on PC"..........I take it after I download &installation TWRP on my PC, there will be a fastboot folder on my PC, right?
-"Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage"......
Thank you very much !
Click to expand...
Click to collapse
You will not be installing TWRP on your PC, you will only be downloading the TWRP recovery.img and storing it in your fastboot folder. Renaming the file to "recovery.img" as well as storing it in your fastboot is not "required", but it does simplify things to make it easier. Otherwise, when you type the fastboot command to flash the recovery, you would have to use the specific file name that you downloaded and the exact path to where it is stored on your PC. Renaming the file and storing it in your fastboot folder simplifies the command to
fastboot flash recovery recovery.img
Instead of
fastboot flash recovery (specific name of the file you downloaded)(exact path to the file on your PC)
Whereas renaming to recovery.img and storing in your fastboot folder removes the need to be specific and flashes recovery.img from fastboot folder by default without having to be specific.
When you install adb/fastboot on PC, you will have a fastboot folder. You can get the installer from the link below.
https://androidmtk.com/download-15-seconds-adb-installer
As for the part about TWRP storing the backup on internal. What I mean is, the N5 doesn't have an sdcard slot for external sdcard, this means that TWRP will store the backup that it creates on your internal storage by default, you'll find the backup in your TWRP folder on your phone. Copy it from your TWRP folder on your device and move it to your PC or some other storage location other than on your phone.
Storing backups on internal can be risky, sometimes your device can get corrupted or can even accidentally get wiped for no apparent reason, if either of these issues happens, the data that you had stored on internal will not be accessible, if this happens, you may not be able to restore that backup. To ensure that you don't screw yourself out of being able to use the backup, you can store it on a flashdrive. If your copy on the phone gets corrupted or if your phone gets soft bricked or accidentally wiped, you won't be able use the copy that is on your internal storage in your device. If that happens, you will have to connect the flashdrive to your phone via OTG cable, then you can boot into TWRP and use the restore option, once you have the restore feature open, you can choose which storage you restore from, choose the OTG flashdrive and you can restore the copy that is on the flashdrive instead of the copy that is stored on your phone.
Did you understand that this time?
I also recommend backing up your personal data(such as contacts and photos and such using some other means other than TWRP), then, after flashing your custom ROM, you can restore that personal data back to your phone so that you have it available in your new ROM. You can back your contacts up to Google and your photos to Google Photos or just copy the photos to PC using Windows file manager. Other types of data must be backed up by other means depending on what type of data is in question, such as using adb to backup your apps and app data then using adb to restore your apps and app data.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You will not be installing TWRP on your PC, you will only be downloading the TWRP recovery.img and storing it in your fastboot folder. Renaming the file to "recovery.img" as well as storing it in your fastboot is not "required", but it does simplify things to make it easier. Otherwise, when you type the fastboot command to flash the recovery, you would have to use the specific file name that you downloaded and the exact path to where it is stored on your PC. Renaming the file and storing it in your fastboot folder simplifies the command to
fastboot flash recovery recovery.img
Instead of
fastboot flash recovery (specific name of the file you downloaded)(exact path to the file on your PC)
Whereas renaming to recovery.img and storing in your fastboot folder removes the need to be specific and flashes recovery.img from fastboot folder by default without having to be specific.
When you install adb/fastboot on PC, you will have a fastboot folder. You can get the installer from the link below.
https://androidmtk.com/download-15-seconds-adb-installer
As for the part about TWRP storing the backup on internal. What I mean is, the N5 doesn't have an sdcard slot for external sdcard, this means that TWRP will store the backup that it creates on your internal storage by default, you'll find the backup in your TWRP folder on your phone. Copy it from your TWRP folder on your device and move it to your PC or some other storage location other than on your phone.
Storing backups on internal can be risky, sometimes your device can get corrupted or can even accidentally get wiped for no apparent reason, if either of these issues happens, the data that you had stored on internal will not be accessible, if this happens, you may not be able to restore that backup. To ensure that you don't screw yourself out of being able to use the backup, you can store it on a flashdrive. If your copy on the phone gets corrupted or if your phone gets soft bricked or accidentally wiped, you won't be able use the copy that is on your internal storage in your device. If that happens, you will have to connect the flashdrive to your phone via OTG cable, then you can boot into TWRP and use the restore option, once you have the restore feature open, you can choose which storage you restore from, choose the OTG flashdrive and you can restore the copy that is on the flashdrive instead of the copy that is stored on your phone.
Did you understand that this time?
I also recommend backing up your personal data(such as contacts and photos and such using some other means other than TWRP), then, after flashing your custom ROM, you can restore that personal data back to your phone so that you have it available in your new ROM. You can back your contacts up to Google and your photos to Google Photos or just copy the photos to PC using Windows file manager. Other types of data must be backed up by other means depending on what type of data is in question, such as using and to backup your apps and app data then using adb to restore your apps and app data.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,
Yes, I understand and know a few things about Windows OS, but when it comes to Android OS, bootloader, fast boot, TWRP...I am a 101-stupid ! But yes, what you are telling me are very similar to Windows OS backup onto external device, which I need....I am going to do tonight,....if I run into any difficulties, sure will keep you informed,....
Once again, I truly appreciated your help, I MEAN IT !
Droidriven said:
You will not be installing TWRP on your PC, you will only be downloading the TWRP recovery.img and storing it in your fastboot folder. Renaming the file to "recovery.img" as well as storing it in your fastboot is not "required", but it does simplify things to make it easier. Otherwise, when you type the fastboot command to flash the recovery, you would have to use the specific file name that you downloaded and the exact path to where it is stored on your PC. Renaming the file and storing it in your fastboot folder simplifies the command to
fastboot flash recovery recovery.img
Instead of
fastboot flash recovery (specific name of the file you downloaded)(exact path to the file on your PC)
Whereas renaming to recovery.img and storing in your fastboot folder removes the need to be specific and flashes recovery.img from fastboot folder by default without having to be specific.
When you install adb/fastboot on PC, you will have a fastboot folder. You can get the installer from the link below.
https://androidmtk.com/download-15-seconds-adb-installer
As for the part about TWRP storing the backup on internal. What I mean is, the N5 doesn't have an sdcard slot for external sdcard, this means that TWRP will store the backup that it creates on your internal storage by default, you'll find the backup in your TWRP folder on your phone. Copy it from your TWRP folder on your device and move it to your PC or some other storage location other than on your phone.
Storing backups on internal can be risky, sometimes your device can get corrupted or can even accidentally get wiped for no apparent reason, if either of these issues happens, the data that you had stored on internal will not be accessible, if this happens, you may not be able to restore that backup. To ensure that you don't screw yourself out of being able to use the backup, you can store it on a flashdrive. If your copy on the phone gets corrupted or if your phone gets soft bricked or accidentally wiped, you won't be able use the copy that is on your internal storage in your device. If that happens, you will have to connect the flashdrive to your phone via OTG cable, then you can boot into TWRP and use the restore option, once you have the restore feature open, you can choose which storage you restore from, choose the OTG flashdrive and you can restore the copy that is on the flashdrive instead of the copy that is stored on your phone.
Did you understand that this time?
I also recommend backing up your personal data(such as contacts and photos and such using some other means other than TWRP), then, after flashing your custom ROM, you can restore that personal data back to your phone so that you have it available in your new ROM. You can back your contacts up to Google and your photos to Google Photos or just copy the photos to PC using Windows file manager. Other types of data must be backed up by other means depending on what type of data is in question, such as using adb to backup your apps and app data then using adb to restore your apps and app data.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,
I am getting the same thing ! I copied that TWRP-3.2-1 Hammerhead, and renamed the copy as you said as recovery.img, and moved it to 15 second ADB installer folder.
Started my phone as you said, also in developer's mode, with USB scanning for device error. Then I tried in Recovery mode, same thing.
Any suggestion ? Was it something I did wrong ?? Million thanks ,
STDupont said:
Hello,
I am getting the same thing ! I copied that TWRP-3.2-1 Hammerhead, and renamed the copy as you said as recovery.img, and moved it to 15 second ADB installer folder.
Started my phone as you said, also in developer's mode, with USB scanning for device error. Then I tried in Recovery mode, same thing.
Any suggestion ? Was it something I did wrong ?? Million thanks ,
Click to expand...
Click to collapse
Did you actually install adb as this thread says to do?
https://forum.xda-developers.com/showthread.php?t=2588979
Once you actually have it installed, open Windows file manager and select your C drive, then you'll see the adb folder instead of a fastboot folder(this folder will have the adb and fastboot .exe files), place the recovery.img in that folder.
On your device, go to system settings>developer options and make sure you have the USB debugging option enabled. If you don't have the developer options setting, go to system settings>about phone, scroll down until you see "build number", tap the build number 10 times quickly until you see a message telling you that you have enabled developer options, then go to developer options and enable USB debugging.
Then open the Windows cmd terminal, boot your device into fastboot mode, connect device to PC, open a Windows cmd terminal, type the command:
fastboot devices
Press enter, if it returns the serial number, you're connected. Then continue with the command:
fastboot flash recovery recovery.img
Then press enter, it should flash the recovery, then type the command:
adb reboot recovery
Press enter and it should reboot the device into TWRP. Then continue on with using the Backup option in TWRP to create your n android backup.
There are plenty of threads here at XDA that completely explain how to flash TWRP via fastboot and plenty of threads here that describe how to create backups using TWRP. Try reading some of those threads and you'll understand it much better and it will probably answer any other questions that you have.
Just do a Google search for:
"How to flash TWRP via fastboot Nexus 5"
Use those instructions.
Then do a Google search for:
"How to create android backup via TWRP"
Those two searches should tell you what you need to know.
If you can't understand these simple instructions that I've given as simple as I can make them or if you can't understand the information that you find with these two searches that I've described, then, you should forget about flashing any kind of ROMs on your device because you'll probably brick your device due to your lack of understanding.
I don't know why you haven't already tried Google searching about this process to understand it. Don't be lazy, do your research.
Sent from my LGL84VL using Tapatalk
---------- Post added at 10:59 PM ---------- Previous post was at 10:31 PM ----------
STDupont said:
Hello,
I am getting the same thing ! I copied that TWRP-3.2-1 Hammerhead, and renamed the copy as you said as recovery.img, and moved it to 15 second ADB installer folder.
Started my phone as you said, also in developer's mode, with USB scanning for device error. Then I tried in Recovery mode, same thing.
Any suggestion ? Was it something I did wrong ?? Million thanks ,
Click to expand...
Click to collapse
One more thing that I forgot to add, you have to unlock your bootloader before you can flash TWRP on the device. To do this, verify that you have enabled the "OEM unlock" option in developer options, then open a Windows cmd terminal and type
fastboot oem unlock
Press enter, it will unlock bootloader but it will also wipe a personal data when you unlock the bootloader so make sure you have your important personal stuff backed up before you unlock the bootloader.
Then you can continue with flashing TWRP.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Did you actually install adb as this thread says to do?
https://forum.xda-developers.com/showthread.php?t=2588979
Once you actually have it installed, open Windows file manager and select your C drive, then you'll see the adb folder instead of a fastboot folder(this folder will have the adb and fastboot .exe files), place the recovery.img in that folder.
On your device, go to system settings>developer options and make sure you have the USB debugging option enabled. If you don't have the developer options setting, go to system settings>about phone, scroll down until you see "build number", tap the build number 10 times quickly until you see a message telling you that you have enabled developer options, then go to developer options and enable USB debugging.
Then open the Windows cmd terminal, boot your device into fastboot mode, connect device to PC, open a Windows cmd terminal, type the command:
fastboot devices
Press enter, if it returns the serial number, you're connected. Then continue with the command:
fastboot flash recovery recovery.img
Then press enter, it should flash the recovery, then type the command:
adb reboot recovery
Press enter and it should reboot the device into TWRP. Then continue on with using the Backup option in TWRP to create your n android backup.
There are plenty of threads here at XDA that completely explain how to flash TWRP via fastboot and plenty of threads here that describe how to create backups using TWRP. Try reading some of those threads and you'll understand it much better and it will probably answer any other questions that you have.
Just do a Google search for:
"How to flash TWRP via fastboot Nexus 5"
Use those instructions.
Then do a Google search for:
"How to create android backup via TWRP"
Those two searches should tell you what you need to know.
If you can't understand these simple instructions that I've given as simple as I can make them or if you can't understand the information that you find with these two searches that I've described, then, you should forget about flashing any kind of ROMs on your device because you'll probably brick your device due to your lack of understanding.
I don't know why you haven't already tried Google searching about this process to understand it. Don't be lazy, do your research.
Sent from my LGL84VL using Tapatalk
---------- Post added at 10:59 PM ---------- Previous post was at 10:31 PM ----------
One more thing that I forgot to add, you have to unlock your bootloader before you can flash TWRP on the device. To do this, verify that you have enabled the "OEM unlock" option in developer options, then open a Windows cmd terminal and type
fastboot oem unlock
Press enter, it will unlock bootloader but it will also wipe a personal data when you unlock the bootloader so make sure you have your important personal stuff backed up before you unlock the bootloader.
Then you can continue with flashing TWRP.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello,
I have it installed. Actaully I was encountering errors but don't want to waste yr time here either.
I will take a close look of the links you provided. I understood what you said, it makes perfect sense. And I know a lot about Windows OS and other stuff, just NOT Android OS and all these.
I also mentioned the developer's mode was ON and USB error detecting was ON, as well. And you are RIGHT ON, ....
Thanks again,
It just when it comes to execution,
STDupont said:
Hello,
I have it installed. Actaully I was encountering errors but don't want to waste yr time here either.
I will take a close look of the links you provided. I understood what you said, it makes perfect sense. And I know a lot about Windows OS and other stuff, just NOT Android OS and all these.
I also mentioned the developer's mode was ON and USB error detecting was ON, as well. And you are RIGHT ON, ....
Thanks again,
It just when it comes to execution,
Click to expand...
Click to collapse
It takes some getting used to, but with proper research based on your device model number and the thing you want to do on that model, it is easily overcome.
Sent from my LGL84VL using Tapatalk
Related
I have just receieved my G1 back from HTC repair as the motherboard was fried..
i have just installed root and rc 9.
how do i recover my previous backups to get back to my original state as i have nandroid files saved on my sd card but am not sure how to open them
infernix said:
Originally Posted by trmacdonal
How to Restore your phone on a Windows PC using a Nandroid backup
I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.
What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/showpost.php?p=3083753&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img
Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Your phone should now be restored exactly as you had it when it was backed up.
Click to expand...
Click to collapse
Please try to search for your answer before posting to prevent multiple duplicate threads. Thanks.
Update: When you flash the recovery and supersu files make sure to have the remove encryption file on sd card aswell and add it to the list and flash and if you hang at boot screen.. boot into recovery and wipe cache.. reboot.
WINDOWS USERS ONLY.... USE AT YOUR OWN RISK
Make sure you have the proper drivers and make sure you have a real good usb cable... This rar has the usb drivers and the files already in the folder just drop onto desktop and run cmd.exe
Files Needed: http://www.filedropper.com/nocturnaladbfastboot
http://www.filedropper.com/removeencryption
DO NOT FORMAT SYSTEM!!!!!!!!!!!!!
Make sure you are in bootloader or this will not work..
Key combo to get into bootloader or recovery via hard keys.
power off
volume up + power = recovery
volume down + power = bootloader
from bootloader you have several choices to boot, just pres volume down to choose, power to select.
1. To make sure you are connected run command (adb devices) enter
2. Once you see your device run command (adb reboot bootloader) Then..
3. Run command (fastboot boot boot.img) wait for downloading dialog...
4. Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure...
5. once the screen says okay on tablet.. push the vol down button until you see recovery mode and then push power to start twrp recovery..
6. Once in twrp flash SuperSU246.zip and recovery.zip remove_encryption.zip then reboot... you should have root on reboot:good:
Instructions
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
ahunter said:
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
run them just as there posted make sure all files on the sd card and you should be fine..
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
ahunter said:
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
Click to expand...
Click to collapse
Make sure you uninstall and reinstall the usb drivers in the folder and run the cmd from the folder and if still nothing try a new cable and usb port... when you run command adb devices do you see your listed as numbers and some letters?
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
ahunter said:
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
Click to expand...
Click to collapse
there is a problem after you boot into bootloader i had the same problem for days.. i just played with cables and drivers use the ones inside the folder they worked for me...
I'll keep trying. It has be the drivers.
I followed these directions to a T, but for some reason the device can not read the SD card while in recovery. Any clues as to why this is happening?
So I was online shopping for my first tablet when I came across this thread. . . It led me down to the local WALMART and I picked one up. I successfully completed the process, or so I thought. I went to reboot after flashing everything, and twrp says " no OS installed! Are you sure you want to reboot?"
What did I do wrong?
I have tried several times to download the remove encryption file must be a bad link or something. Is there another download site or can someone send to me plz
Nvm I ran it over with my car because I couldn't get the download link to work. If anyone wants it for parts send me a message. Its brand new only been used maybe 2 weeks. The most wear and tear on it was my Buick regal hitting it at about 45 mph in a pissed off rage. don't think all the insides are smashed tho. Possibly a good fixer upper
Is this fastboot and adb custom versions?
I have adb and fastboot in my path (runable from anywhere)..
ADB says the version release is the same number.
do I need to use your versions for the tablet?
http://www.filedropper.com/removeencryption
does not work, link changes to http://www.filedropper.com
and asks me to upload a file?
Link working sorry...
http://www.filedropper.com/roottwrpremoveencryption
TWRP 3.0
http://www.filedropper.com/twrp3recovery
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>fastboot flash recovery twrp_
recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15558 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.830s
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>
Copied the two zip files to both a 4gb fat32 formatted microsdhc
and internal storage via MTP to the device then ran ADB 1.0.32
and rebooted to bootloader. (adb finds device fine)
fastboot devices reported device number fastboot.
flashed TWRP in package you uploaded yesterday.
it says both internal and external cards are empty?
internal card has files that the manufacturer put there,
but TWRP can't see them?
What am I doing wrong?
Any ideas how to fix?
log says 'unable to find crypto file'
and it couldn't mount /data or /storage filesystems
>>>
installed TWRP3 that allowed the installs although it still
could not open /data. It did find the external card installed
from there.
I am guessing the forced encryption made /data unreadable.
hopefully now with the encryption removed the /data
partition will be readable.
>>>
I reran recovery to check and log now has no failures!!!
I'm guessing the changed boot.img fixed the issues it was having.
*smiles*
cant get files. takes me to a site to sign up. can you dropbox link them please?
I just won this tablet in a contest. Anyone have the remove_encryption.zip file? I managed to find all of the other required files but none of the links in this thread work anymore.
whats the problem with the links? site says free but wants me to pay. losing my head here, and it seems im not the only one
Bad filedropper links
Filedroper no links available, asks us to register and pay for stuff that's not there anymore
can you like put them on Google drive, SendSpace, DropBox, Mega.nz and/or ZippyShare
This guide is meant to less techie people, and written in detail. Please don't mind me if I overexplain. If you have any questions, feel free to comment them.
Also, I am not responsible for anything you do to your phone; you assume your responsibility for anything you do because of this guide.
Scenario:
So, lets say that you tried to flash an zip file on your android using sideload, but the zip required another file to be in the same directory as it, in order to work.
After flashing the zip and getting an error, your phone may not get pass the logo of the brand and be soft bricked.
Also, you formatted your external sd as internal, and cant access your usual location with files in the recovery.
In this case, don't worry, as I'm here to help you unbrick your phone without reinstalling the rom.
Things you will need:
your phone
a computer connected to your phone with an usb cable
the proper drivers for your phone
a custom recovery like cwm or twrp installed on your phone
probably root, although I'm not sure
and finally the adb (android development bridge) utility
Where to get a custom recovery?
- https://www.xda-developers.com/how-to-install-clockworkmod/
or search on xda under at your device's forum
Where to download adb from?
- https://forum.xda-developers.com/showthread.php?t=2588979 (this one comes with the drivers)
- https://dl.google.com/android/repository/platform-tools-latest-windows.zip (just the adb files)
So lets get started:
First, get your phone into Recovery mode (on samsung hold power button volume up and home button), and connect it to your pc with a usb cable.
Open ADB by shift + right clicking the folder platform-tools in witch it is located. Click on "Open Command Prompt window here" or "Open Powershell window here" (depends on your windows settings).
You need to find a location on your phone that is accessible through the flash zip menu from your recovery. (from sdcard / from sdcard1 or whatever your external sd is called)
In my case, i could get to see folder 0 and obb from "flash zip from sdcard".
To find a suitable folder:
In the window, type
Code:
adb.exe shell
if you opened cmd, or
Code:
./adb.exe shell
if you opened powershell.
This will open a terminal that will run commands on your phone.
(Now you can type commands in the cmd window that will be run on your phone.)
Type in
Code:
cd /sdcard/0
to go to the main sd card location that is accessible in recovery when you go to flash a zip from there. (if you can get to another folder where you could a flash a zip from, change the location to that place)
You can use here the command
Code:
ls
to view objects in the folder you are in.
After you are done, type
Code:
exit
to exit.
To solve the soft-brick, you need to reflash the zip, but with the files it needed in the same directory.
Type in the ADB window
Code:
./adb.exe push "location of the file you are sending" "location of the folder you are sending to (eg. /sdcard/0)"
if you are in powershell, or without the ./ if you are in cmd.
Use this until you have sent all the files needed for a successful flash.
Then just use the "flash zip" utility from your recovery with the location you have sent the files to, on your phone, to complete the flash, and solve the half-brick.
Restart your phone and you should be good to go.
Thanks to the following threads, that helped me put this together, and solve this problem on my phone:
https://forum.xda-developers.com/showthread.php?t=1927198
https://forum.xda-developers.com/showthread.php?t=2588979
Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!
I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...
C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk
I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.
You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work
My Android phone (Motorola Edge) can no longer start properly after a failed system update. The message I get is: "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
I've tried restarting it in recovery mode which didn't work. I've read that I may be able to install some software via USB and rescue the system but I have no idea how that's done. I've looked at some different rescue software such as Rescue and Smart Assistant (which would only let me rescue the phone which will erase all data) and Dr.Fone but the reviews aren't convincing and the unofficial software programs generally don't support Motorola phones. Does anyone know how to fix my phone without losing my data?? Any help is much appreciated.
Also; I'm in no way a developer so I need everything explained to me like I'm 12 years old.
hi, kid welcome to xda.
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
[email protected] said:
hi, kid welcome to xda.
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
Thank you so much for your input. Unfortunately I can't make it work. When I type 'adb devices', I get this text:
List of devices attached
ZY227HQ2BX sideload
I've attached more info. Not sure if this has something to do with "USB debugging"?
all things right,
that sideload appears because you have stock recovery {no need to worry}
you don't need to erase system, (it is like optional)
and the error ANDROID_PRODUCT_OUT....... is because as i said earlier you have to copy the path of the file not file name.
how to copy path of the file ?
well, simple on windows, open the folder in which system file is present. and again open command prompt type (remember to be in fastboot mode in mobile phone)
fastboot flash {drag and drop system file from folder to command prompt}.
it should look like (but not the same, it is an example)
fastboot flash E:/newfolder/nexus/files/system.img
tell me if you face any problem (also include screenshots like you did, great right?)
What file is the system file in this folder?
[email protected] said:
all things right,
that sideload appears because you have stock recovery {no need to worry}
you don't need to erase system, (it is like optional)
and the error ANDROID_PRODUCT_OUT....... is because as i said earlier you have to copy the path of the file not file name.
how to copy path of the file ?
well, simple on windows, open the folder in which system file is present. and again open command prompt type (remember to be in fastboot mode in mobile phone)
fastboot flash {drag and drop system file from folder to command prompt}.
it should look like (but not the same, it is an example)
fastboot flash E:/newfolder/nexus/files/system.img
tell me if you face any problem (also include screenshots like you did, great right?)
Click to expand...
Click to collapse
Hi again, I've spent all weekend trying to figure it out but so far no luck.
I don't know where to find the system file in the folder I downloader (see attached photo in my reply above this). I also tried making a service-batfile with guidance from YouTube but it seems my phone is locked so it doesn't work.
well sorry i was quite busy so i was not able to reply.
first thing first do you need your data
if so boot into twrp. find twrp image for your phone then use command in fastbootmode
fastboot boot and drag and drop twrp file.
after successfully booting into twrp use option to backup and backup your data in any external storage like sd card.
after that run flash all.bat inside your downloaded folder.
i will completely wipe and reinstall your firmware.
then after it again in fastboot mode boot into twrp and restore your backup that's it.
[email protected] said:
well sorry i was quite busy so i was not able to reply.
first thing first do you need your data
if so boot into twrp. find twrp image for your phone then use command in fastbootmode
fastboot boot and drag and drop twrp file.
after successfully booting into twrp use option to backup and backup your data in any external storage like sd card.
after that run flash all.bat inside your downloaded folder.
i will completely wipe and reinstall your firmware.
then after it again in fastboot mode boot into twrp and restore your backup that's it.
Click to expand...
Click to collapse
I tried doing it but no success (I really want to keep my data). See attached photo
bro first try fastboot oem unlock then try this command
note. if some pop up ask to click ok in phone click to conform unlocking phone to flash other files (twrp)
[email protected] said:
bro first try fastboot oem unlock then try this command
note. if some pop up ask to click ok in phone click to conform unlocking phone to flash other files (twrp)
Click to expand...
Click to collapse
I get this message:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.061s
Will unlocking the device delete my data?
SirOinksalot said:
I get this message:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.061s
Will unlocking the device delete my data?
Click to expand...
Click to collapse
try some windows app to recover it.
sorry unocking will delete data
[email protected] said:
try some windows app to recover it.
sorry unocking will delete data
Click to expand...
Click to collapse
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
SirOinksalot said:
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
it will work but need to be modified as your frimware is different i mean hybrid which does not contain system image.
try to clear caches using fastboot : fastboot clear cache
and try to reboot hope it will work. acctuly i have exams so i am a quite busy now a days sorry
SirOinksalot said:
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
How did you resolve your issue ?
[email protected] said:
it will work but need to be modified as your frimware is different i mean hybrid which does not contain system image.
try to clear caches using fastboot : fastboot clear cache
and try to reboot hope it will work. acctuly i have exams so i am a quite busy now a days sorry
Click to expand...
Click to collapse
Hello buddy,hope your exams are over and you passed them all with wonderful grades!
I am facving the similar problem and unable to find a solution.Would you mind having a look at this ? Thank you!