I am new to this site and read the posting rules nonetheless, information here is quite overwhelming. I hope that this is the appropriate location for this posting.
I have searched this site and other sites and have not found instructions (perhaps easier ones) on this topic, so I wanted post some basic ones here. Hope it helps.
(To my dismay, I couldn't figure out how to upload images and zip files from computer)
First you will need to install the Android/Windows SDK files
Install and unpack the android-sdk_r24.4.4.1-windows.zip (developer.android.com/studio/index.html#downloads) to your "C:"
I renamed my file by removing the "-windows" to make it easier for the PATH/Variables
After extraction, goto C:\Android-Sdk\SDK Manager.exe
Right click on the SDK Manager, Run as Administrator
Select all files under TOOLS
Check: Updates/New and Installed
Click Install Packages
Accept License
After done reboot
repeat steps, open SDK Manager
this time under TOOLS, uncheck installed Android SDK and check not installed and new version available
Click install packages
Accept License
After done reboot
Now Installing PATH to Windows 10
Click "Windows + E" (or Go to "this PC" folder)
On top, click on "System properties"
On the left, click on "Advanced System Settings"
Click on "Environment Variables"
Under System variables, click on "Path" and click "edit"
Click "New"
Type "C:\android-sdk\tools"
Click OK
Again under System Variables, click on "Path" and click "edit"
Click "New"
Type "C:\android-sdk\platform-tools
Click OK to all the rest
Press windows and type "CMD" and right click on it and select run as administrator
Type ADB
If installed correctly you will see all of the ADB command lines printed on your screen.
Your computer is ready to Communicate with your Android phone.
You will see the corresponding commands for backup and restore.
Backup and Restore Using ADB
ADB Backup
Make sure that your "USB dubbuging option" is on
Connect your phone phone/tablet using USB connection
Open your folder where you want you want to download your backup(s)
for example C:\My Phone Backup
Click the "File" option on top
Select the "Open command prompt as administrator"
Type "ADB Devices"
If an MTP message pops on your phone, click "OK"
Type adb backup -all -apk -f -backup.ab
Check your phone, it will give you to backup with or without the backup
Click either one
Once completed, you should have a quite a large backup.ab file in your destination folder
ADB Restore
Follow all of the steps above
Type adb restore backup.ab
--------------------------------------
For System Backup / Restore
Follow the above steps
Type adb backup -all -system -f -backup.ab
(make sure that the location of the system backup is different then the location of the apk backup)
As I mentioned before, If you Type ADB in CMD (Command Prompt in DOS) it will print the ADB shell command line.
I used to use TitaniumBackup to transfer apps and data from one Android phone to another when both devices are rooted. Recently I got a phone which currently does not have root access, so TitaniumBackup would not be useful. Most apps are not an issue, but I have trouble transferring a few apps and their data.
I was thinking to use adb to backup each app+data separately, and tried using the following command on the old (and rooted) phone:
adb backup -f <appname>.ab -apk <app_package_name>
but I got the following message:
Now unlock your device and confirm the backup operation.
The strange thing is that there is nothing there for me to accept when I unlock the phone or when I keep the phone unlocked.
Also when backing up all apps via "adb backup -apk -shared -all -f all.ab", I still get the same message: Now unlock your device and confirm the backup operation. And this happens on two computers I have tried so far. Very weird.
I just tried another phone, and had no problem with the adb backup command (I did see the confirmation request on the phone). So the problem seems to be with this particular phone (LG G2 with root).
Any suggestions as to how to handle the transfer? Any better alternatives?
Thanks, it worked for me.
atk9010 said:
ADB Backup
Make sure that your "USB dubbuging option" is on
Connect your phone phone/tablet using USB connection
Open your folder where you want you want to download your backup(s)
for example C:\My Phone Backup
Click the "File" option on top
Select the "Open command prompt as administrator"
Type "ADB Devices"
If an MTP message pops on your phone, click "OK"
Type adb backup -all -apk -f -backup.ab
Check your phone, it will give you to backup with or without the backup
Click either one
Once completed, you should have a quite a large backup.ab file in your destination folder
ADB Restore
Follow all of the steps above
Type adb restore backup.ab
--------------------------------------
For System Backup / Restore
Follow the above steps
Type adb backup -all -system -f -backup.ab
(make sure that the location of the system backup is different then the location of the apk backup)
As I mentioned before, If you Type ADB in CMD (Command Prompt in DOS) it will print the ADB shell command line.
Click to expand...
Click to collapse
I had to update the driver for my phone. Once done it worked for me. thanks.
This is perfect if you have a damaged touch screen. It's always good to have different backup methods for any unforeseeable future. However outaded, It's effective.
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
Soft-Bricked my phone this morning flashing a Substratum Theme. Don't ask, I don't know why but it did.
Did a factory reset, Pixel Flasher, set up Magisk, rebooted - got Pixel is Starting. - couldn't get out of it and this was AFTER I recopied all my stuff back over form the last update I had on my Computer and Swift/Google Backups.
Factory reset, same thing happened while doing a reboot at some point int he process.
THIRD Factory reset, got everything done, restored, up and running, just did a reboot and it's back.WTF?? And how do I get out if this?
How are you factory resetting the device?
Also, perhaps something that you are restoring is causing the boot issue. You shouldn't restore data from Swift Backup immediately after fully re-imaging your phone - if that is part of what you are doing.
NippleSauce said:
How are you factory resetting the device?
Also, perhaps something that you are restoring is causing the boot issue. You shouldn't restore data from Swift Backup immediately after fully re-imaging your phone - if that is part of what you are doing.
Click to expand...
Click to collapse
No, I’m doing the factory reset in recovery. Then when the phone booths up just going through the bare minimum of settings to get to the home screen so I can flash the newest update and get routed. Since it’s a factory update and I need to disable verity and verification I have to wipe again anyway and then I go through the whole set up process, let google restore all my apps and stuff and then I use swift back up to restore my apps and data.
I wonder if when I do my back up from Swift I should just do data instead of letting the apps overwrite them selves
Searching online it looks like I can still connect with ADB. I’ll see if I can use the flashing tool and maybe re-flash without wiping
Ahh, gotcha. You can try what you said but I would also suggest re-imaging your phone with the matching factory image that you are currently running. You can do a proper, full re-image through recovery without wiping your phone.
NippleSauce said:
Ahh, gotcha. You can try what you said but I would also suggest re-imaging your phone with the matching factory image that you are currently running. You can do a proper, full re-image through recovery without wiping your phone.
Click to expand...
Click to collapse
How do I do that?
HipKat said:
How do I do that?
Click to expand...
Click to collapse
A lot of commands lol. I will update this comment in just a moment once I head over to my desktop. Typing this out on my phone would be a real disaster, haha.
Alrighty! Here is that update:
1. Ensure that you have the latest version of platform-tools somewhere on your hard drive. Also ensure that your phone has ADB enabled - which you said yours has enabled already - so you should be all good there.
2. Download the correct, most updated factory image here:
--> https://developers.google.com/android/images
3. Extract the contents of the factory image into your platform-tools folder. If you want to root, also be sure to extract the init_boot.img from image.zip file that is inside of the main factory image zip file.
4. Right-click and edit the flash-all.bat file and remove the "-w" near the bottom of the document. "-w" means "wipe". Make sure to save the document after making this change.
5. Copy the directory of your platform-tools folder.
6. Open CMD as an administrator.
7. In CMD, change directories to your platform-tools folder. The command is:
cd DirectoryLocationYouCopiedGoesHere
8. Connect your phone to your PC over USB.
9. In CMD once it is navigated to the platform-tools folder (which should also contain the extracted factory image files at this point), type the following commands:
adb reboot-bootloader
**This will reboot your phone into the bootloader**
flash-all
**This will run the flash-all.bat script which will re-image your phone with the downloaded factory image. It will not wipe your phone if you remembered to remove the "-w" line as mentioned above. Also, DO NOT interact with your phone while this command is running. It will automatically boot itself once it is done - which can take up to 5-10 minutes.
10. You can probably do the rest on your own from this point. But the basis of what comes next would be installing Magisk, copying the init_boot.img over to your phone, patching it in Magisk, copying the patched init_boot.img back over to your computer, booting your phone into recovery mode once again (via CMD) and then running the following command in CMD as admin:
fastboot flash init_boot MagiskPatchedInitBootFileNameGoesHere.img
**This will flash the patched init_boot.img file**
Then use this command:
fastboot reboot
**That will take your phone out of recovery and cause it to boot normally**.
I actually have to run to a birthday party right now so I can't write any more specific details. If you don't feel comfortable doing this all, please let me know. If that's the case, I'll make a video showing how to do this tomorrow or something, haha.
NippleSauce said:
A lot of commands lol. I will update this comment in just a moment once I head over to my desktop. Typing this out on my phone would be a real disaster, haha.
Click to expand...
Click to collapse
Lol,I’m hip
NippleSauce said:
A lot of commands lol. I will update this comment in just a moment once I head over to my desktop. Typing this out on my phone would be a real disaster, haha.
Alrighty! Here is that update:
1. Ensure that you have the latest version of platform-tools somewhere on your hard drive. Also ensure that your phone has ADB enabled - which you said yours has enabled already - so you should be all good there.
2. Download the correct, most updated factory image here:
--> https://developers.google.com/android/images
3. Extract the contents of the factory image into your platform-tools folder. If you want to root, also be sure to extract the init_boot.img from image.zip file that is inside of the main factory image zip file.
4. Right-click and edit the flash-all.bat file and remove the "-w" near the bottom of the document. "-w" means "wipe". Make sure to save the document after making this change.
5. Copy the directory of your platform-tools folder.
6. Open CMD as an administrator.
7. In CMD, change directories to your platform-tools folder. The command is:
cd DirectoryLocationYouCopiedGoesHere
8. Connect your phone to your PC over USB.
9. In CMD once it is navigated to the platform-tools folder (which should also contain the extracted factory image files at this point), type the following commands:
adb reboot-bootloader
**This will reboot your phone into the bootloader**
flash-all
**This will run the flash-all.bat script which will re-image your phone with the downloaded factory image. It will not wipe your phone if you remembered to remove the "-w" line as mentioned above. Also, DO NOT interact with your phone while this command is running. It will automatically boot itself once it is done - which can take up to 5-10 minutes.
10. You can probably do the rest on your own from this point. But the basis of what comes next would be installing Magisk, copying the init_boot.img over to your phone, patching it in Magisk, copying the patched init_boot.img back over to your computer, booting your phone into recovery mode once again (via CMD) and then running the following command in CMD as admin:
fastboot flash init_boot MagiskPatchedInitBootFileNameGoesHere.img
**This will flash the patched init_boot.img file**
Then use this command:
fastboot reboot
**That will take your phone out of recovery and cause it to boot normally**.
I actually have to run to a birthday party right now so I can't write any more specific details. If you don't feel comfortable doing this all, please let me know. If that's the case, I'll make a video showing how to do this tomorrow or something, haha.
Click to expand...
Click to collapse
Flashing now. For future reference, in CMD, you need to run adb kill-server, then adb-devices before rebooting to bootloader (I'm not a TOTAL ADB noob lol). In my case, none were found so I just disconnected and reconnected the USB from the phone and it found it.
Also, Pixel Flasher was not able to work in Recovery or in the Pixel Is Starting state, which shows up on the tool as ADB - probably not rooted.
I'll update when it's done
Grrrr, no luck. Right back to Pixel is Starting.
Back to the hard way
HipKat said:
Grrrr, no luck. Right back to Pixel is Starting.
Back to the hard way
Click to expand...
Click to collapse
When you're on this screen, normally it's a launcher thing. Have you flashed any mods for launchers?
If you're still able to access your settings through the notification bar, you should be able to go to apps in your settings and open the Play Store to temporarily download another launcher. This will at least allow you to get some usage from your phone.
Curiousn00b said:
When you're on this screen, normally it's a launcher thing. Have you flashed any mods for launchers?
If you're still able to access your settings through the notification bar, you should be able to go to apps in your settings and open the Play Store to temporarily download another launcher. This will at least allow you to get some usage from your phone.
Click to expand...
Click to collapse
It's an encryption thing with the unlock method, pin, fingerprint, etc form everything I've read, and I read a lot and no one has been able to get past it without a wipe. I've used Nova Pro with the same settings over many devices
You can't get to apps. You can get to settings but if you select Apps and try to open an app, the only options are Uninstall and Force Stop
It's in the data on the Swift Restore. Everything is good after restoring Google Backup, and Swift missing Apps. I restored only data on system apps and user apps and the next reboot gave me this error. I wonder if I should NOT restore system data... I almost didn't just to see what happened, but I would have anyway
Confirmed, not restoring System Data was the fix. Funny, I have restored Sys Data Twice before today....
HipKat said:
Flashing now. For future reference, in CMD, you need to run adb kill-server, then adb-devices before rebooting to bootloader (I'm not a TOTAL ADB noob lol). In my case, none were found so I just disconnected and reconnected the USB from the phone and it found it.
Click to expand...
Click to collapse
In adb you do not have to run those commands. Adb devices would just let you check if an adb enabled device is connected. Adb kill-server only needs to be run if you had already used adb commands with your connected device, disconnected it and then reconnected it. That would kill the originally established and utilized adb connection which would then allow you to establish another one - which I suppose I should have mentioned considering you had tried things over adb prior to my comment, haha. My apologies.
But regardless, I'm glad that you got it working again! So it was that Swift Backup restore after all? That is good to know. Awesome stuff.
NippleSauce said:
In adb you do not have to run those commands. Adb devices would just let you check if an adb enabled device is connected. Adb kill-server only needs to be run if you had already used adb commands with your connected device, disconnected it and then reconnected it. That would kill the originally established and utilized adb connection which would then allow you to establish another one - which I suppose I should have mentioned considering you had tried things over adb prior to my comment, haha. My apologies.
But regardless, I'm glad that you got it working again! So it was that Swift Backup restore after all? That is good to know. Awesome stuff.
Click to expand...
Click to collapse
Yeah, I should know better than to restore old System Data. It used to be a no-no, but the first 2 times I did a restore after first rooting and then a wipe a few weeks ago, I hadn't even thought of it. That's what 78 years away from the Rooting game does to you.
As for those commands, ADB-Devices came back with nothing till I did kill-server. Probably just something on my end