Like most people, usually when I go to install a new rom, I just boot into recovery and format system/data/cache...etc before the installation. Unfortunately, this method is not as thorough as I would like and a lot of stuff is left behind. Therefore, I'm looking for a method that essentially erases everything but the bootloader. From what I understand, the only way to accomplish this is through adb.
So I have a few questions:
What are the adb commands to delete everything in preparation of a completely fresh install? - rom,kernel,recovery,radio etc...
Will this affect essential parameters such as booting into the bootloader, battery stats,charging,hardware interface, etc?( I would like to avoid messing with anything like that)
These are the following files that I have:
cwm_recovery.img
stock_rom.zip
custom_kernel.zip
stock_radio.zip
After deleting everything, I assuming the first thing to install would be the recovery image - from which the remaining zip files can be installed(in the order listed?).
How do you install the aforementioned recovery.img using adb?
What are the adb commands to push the remaining zip files onto the internal sd card?(no external sd available)
But if I deleted everything, would an sdcard still be mounted? If not, what are the adb commands to remount everything needed for the remaining items?
Lastly, is there a better way of doing this?
I know it's a lot to cover but after searching through many forums and blog posts, I can't seem to find any info on doing exactly this. Just bits and pieces about adb commands and troubleshooting botched installs of various devices. So any info would be appreciated.
You can simply flash everything via fastboot.
What you're proposing is unnecessary, there's simply no need to wipe the entire device like that. All you need to do is flash the stock images via fastboot (look at section 8 in my guide thread.
Transmitted via Bacon
Related
I've looked all over, but cannot find anything on the problem I am having.
I go through the steps to load the current factory image onto my nexus s 4g through terminal on my mac, but for some reason it doesn't load everything. Here's what it says in terminal about the items that can't load:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
And here's what my folder looks like where I'm loading everything from:
I guess I can't post a picture from an outside source, so I'll just type in what my folder looks like:
boot.img
bootloader-crespo4g-d720spric1.img
flash-all.bat
flash-all.sh
flash-base.sh
image-sojus-jro03r
image-sojus-jro03r.zip
radio-crespo4g-d720sprilf2.img
there are files in the unzipped folder (image-sojus-jro03r) named:
android-info.txt
recovery.img
system.img
userdata.img
These seem to be some of the files that are missing, but even when i drag them over to the main folder, they still don't load. maybe something to do with the fact that they are .sig's?
I drag the flash-all.sh file into terminal and it loads and writes everything except for these .sig's, which I truthfully don't know what they are. Now I can't get into the correct recovery mode, it just shows some weird blue-lettered options that are different then the normal recovery options. That is why I think the fact that these .sig files are not loading is the problem.
I also booted up the new operating system and signed on, but for some reason none of my apps can download.
Sorry for my noobness, but I'm sure I'm missing one easy step that will fix my problems.
Does anyone know what I'm going through?
Any help is much appreciated.
Alright. I've searched the web and found a few different things. It seems that it's common for those .sig files to not load. Also, i loaded the factory image again and was able to download my apps.
I also now foolishly realize that to get a good version of recovery, I need to root my phone. I'm in terminal now, and for some reason adb is not showing my phone in adb devices. This wasn't a problem when I loaded the factory image, but now it's a problem when I'm trying to do this: http://forum.xda-developers.com/showthread.php?t=1129759
step 5 is a problem, but hey, I can turn off the phone and go into fastboot mode myself. I guess step 7 is the next problem I'm dealing with. Here's what I get in terminal when I do step 7 manually (I put a *#* where my name is just so everyone knows):
MacBook:~ *#*$ /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img
-bash: /Users/*#*/Desktop/adb-fastboot/recovery-clockwork-5.0.2.0-crespo.img: Permission denied
Does anyone know what I'm dealing with this time around?
You probably need to enable adb in Settings --> Developer Options. If it's an issue with adb while in recovery, i'm pretty sure the stock recovery (which will be overwritten on every boot from a stock ROM) doesn't allow it. What you need to do is flash a new recovery in fastboot (not in recovery).
Commands (while in fastboot mode):
/path/to/fastboot devices <-- this will tell you if your phone is connected properly
/path/to/fastboot flash recovery /path/to/recovery.img <-- this will flash the new recovery
You'll need to type in the path to fastboot unless you have it in somewhere like /bin or a more convenient environmentally recognised location. The command you typed there is the same as trying to open the .img file as a script, you want to tell fastboot to flash the file to the phone and not open it with the computer.
Edit: Also, once you root, you probably want to delete /system/etc/install-recovery.sh. That file replaces any custom recovery with stock each time you boot.
Thanks Harbb.
That's what I ended up doing, using fastboot. it worked perfectly. I did try to find the /system/etc/install-recovery.sh file in root explorer, but could not find it. don't know where it is.
Everything is rooted and restored on my custom rom to where I was previously using titanium backup.
Here's the tutorial I was using: http://forum.xda-developers.com/showthread.php?t=1129759
with this video being a walkthrough of the previous tutorial: http://www.youtube.com/watch?v=sP9ZDWmbLVM
I was actually using the recovery img in the android folder that I downloaded from the tutorial, and not the one he told me to download, which was my problem in the end. Here's the link to the download page where I should have downloaded it from: http://forum.xda-developers.com/showthread.php?t=988686&highlight=clockwork+4.0.0.2
Thanks again Harbb, much appreciated.
No worries buddy, glad you got it sorted.
Bear with me: Right now my nexus is stuck in a bootloop. My nexus had been partially rooted, everytime i went to download the OTA 5.0.1. update it would just take me to TWRP, and i didn't know what to do with that. So I finally tried to fully root the phone, and also use TWRP to install the OTA update. Now I'm stuck, I've tried wiping the cache/factory reset. How do I got about flashing it back to stock without losing all my data?
(apologies for the title, I thought originally that I had killed mtp and adb, but I figured out how to get them back just after posting)
Thanks!
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Ben36 said:
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Click to expand...
Click to collapse
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
The reason I say read the guides is simply it saves me or anyone else typing out a massive guide that already exists in many places.
If you're looping then something is more than likely wrong with the system not the data. So flashing just the system will keep your data safe (as long as you flash the same android version as you previously had, lollipop or kitkat)
You need to be in the bootloader not recovery and use the command fastboot flash system system.img
Google img's are here - https://developers.google.com/android/nexus/images
(just keep unzipping until you find the individual img files)
photobumm said:
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
Click to expand...
Click to collapse
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
_MetalHead_ said:
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
Click to expand...
Click to collapse
So I have adb and fastboot running. And I changed the flash-all.bat file. However, I don't understand what I do now? I downloaded the Hammerhead zip and it has a bunch of things in it. Which files do I put into the adb/fastboot folder and how do I then flash them?
In the hammerhead file it lists the bootloader, flash-all, radio and then a zip file "image-hammerhead...". What files am I using and what is the code that I input? Is this the same sa flashing a rom?
I also tried placing the system.img in the adb folder, and then using the
Code:
fastboot flash system system.img
but it gives me an error "cannot load 'system.img'
So now my issue is I get a "error: could not load 'system.img'. after running
Code:
fastboot flash system system.img [code/] . I also tried with boot.img. Same error.
I ran the "flash all" script, by accident, a screenshot of the terminal is attached.. I'm still stuck in a the boot loop, however, and if try to enter recovery mode an android lying down with a red triangle is present. The above "error: could not load..." is still present.
Create a folder and put fastboot in it.
So you unzipped the stock image. You said you have some images in the folder and a zip image.
Unzip that second zip.
There you will find the rest of the images you need.
Now take the recovery, bootloader, system, userdata, cache, and radio images and move them into the folder which you created for fastboot.
Rename the bootloader image to bootloader. img
Now when looking at that open folder containing all the images and fastboot hold down shift and left click and select "open command promt from window"
Type
/fastboot erase bootloader
/fastboot flash bootloader bootloader.img
/fastboot reboot-bootloader
/fastboot erase recovery
/fastboot flash recovery recovery.img
/fastboot erase radio
/fastboot flash radio radio.img
Repeat for the rest of the image files
Finally type /fastboot reboot
Profit.
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
P. S. Make sure your phone is booted in fastboot mode first.
Oh and that android is stock recovery
U fixed it?
So for some reason I still kept getting that error. I ended up restoring to stock using the nexus root toolkit. So it all worked out in the end.
What is the most thorough wipe and full reinstall I can do?
I have flashed different OS' before but it still carries forward baggage like random folders and TWRP files.
Is there a way to get my phone to the most basic level there is (inc no TWRP) with the newest OS/Kernel?
xinfernal said:
What is the most thorough wipe and full reinstall I can do?
I have flashed different OS' before but it still carries forward baggage like random folders and TWRP files.
Is there a way to get my phone to the most basic level there is (inc no TWRP) with the newest OS/Kernel?
Click to expand...
Click to collapse
What I tend to do with Bacon is to go back to the last version of firmware that Cyanogen put out, which you can read about here (https://forums.oneplus.com/threads/oneplus-one-rom-cyanogen-os-13-1.440959/).
I'll download the Fastboot images (https://www.androidfilehost.com/?fid=24591000424960109)
Unzip to wherever on your computer.
Copy a working version of adb/fastboot binaries to the same directory where you unzipped your Bacon images.
Search the unzipped folder contents for a the shell file called "flash-radio.sh" and open it with a text editor of some sort.
In there you'll have a few scripts that call the fastboot binary to flash all of the unzipped binaries/images to their respective partitions on the device. If you're savvy enough you can modify/add to this shell file so that it flashes everything for you in one fell swoop (Recovery, Boot, Cache, System, Userdata, etc.). If not then you'll need to run each command individually in a terminal/powershell/command prompt window (example "fastboot flash system system.img" or "./fastboot flash recovery recovery.img" or even "sudo ./fastboot flash boot boot.img"; depending on your computer setup you may need to make the fastboot binary executable but that's a deeper conversation.).
Finally just to entertain superstition I'll do the flash for about three times. Any respectable developer will tell you that this is probably bad practice just because an emmc/flash-based memory can only take so many read/writes in its lifetime, but again that's a deeper conversation. I'm sure that there are also device forensic specialists that will tell you that the only ultimate wipe you can ever do on an emmc is pulverization with a decent sledgehammer.
Manually reboot the device or if you're still in fastboot just run an iteration of fastboot reboot.
Profit.
So I may be doing something totally idiotic, but I seem to be stuck at the most simple part of unlocking my bootloader.
I follow this to step 2:
https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
when it says "Set up ADB" I follow the link to this:
https://www.xda-developers.com/install-adb-windows-macos-linux/
until I get to step 7. When I enter the command 'adb devices' I never get a serial number nor a prompt to allow or deny USB Debugging access. I never get see my device’s serial number in the command prompt.
So doing a bit of digging I have looked into ensuring my ADB and One Plus driver was installed correctly, and I even purchased a new data transfer cable to make sure that wasn't the issue.
I check my device drivers and see get an error in my ADB Interface driver, but after following a few tutorials I'm still lost as to whether its updated or if I'm doing so incorrectly, or if that's even the problem.
Any direction would be appreciated.
I am running Windows 8.1 and my device is Android 10, model GM1915.
NephilimHoss said:
So I may be doing something totally idiotic, but I seem to be stuck at the most simple part of unlocking my bootloader.
I check my device drivers and see get an error in my ADB Interface driver, but after following a few tutorials I'm still lost as to whether its updated or if I'm doing so incorrectly, or if that's even the problem.
Click to expand...
Click to collapse
Hallelujah!!
Finally found a way to manually install the correct driver from a tutorial on visualgbd{dot}com, so now my device is recognised.
I had to find where my drivers were being default downloaded since they weren't in the place the tutorial indicated, but that was the only hitch.
SO. On to the actual unlock. :fingers-crossed:
So I need help.
I followed an XDA video tutorial which was a bit difficult for a newbie, but I think I did everything correctly up to installing TWRP.
I got to the point of flashing my ROM and jumped to the Eelo website instructions:
- Go to main menu, then tap Wipe.
- Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.
- Return to the previous menu and tap Advanced Wipe.
- Select the Cache and System partitions to be wiped and then Swipe to Wipe.
- Sideload the /e/ .zip package:
- On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
- On the host machine, sideload the package using: 'adb sideload filename.zip'
I followed this and while the package did not sideload, I beleive my recovery partition was wiped I seem to be stuck.
I'm at the point where I feel I need to Flash OEM Stock and start over, but I am getting a bootloader loop.
Really need help. I feel at this point I'm going to start making things worse as I look at various tutorials and whatnot.
In case additional information is helpful:
My device does not show up in my device list, but it is detected with "fastboot devices".
I attempted to flash TWRP with "fastboot flash boot <TWRP.img> and it writes to 'boot-a'. But when I then try to boot into recovery mode, instead of booting into TWRP I enter the fastboot screen.
I tried using mauronofrio's Tool All In One to flash stock ROM and possibly fix the partition, if thats what the problem is, but I cant tell it did anything.
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