Related
My TF300 is on stock and is unrooted with a locked bootloader. However, despite this, it is no longer booting into the stock ROM. It gets stuck on the bootanimation phase with the loading circle constantly circling round, even after a few hours. It hasn't moved on from this stage unfortunately and I was wondering if there was anything that could be done? I know I could try wiping my data, but there are files and app data that I would not like being lost so is there any way they would be salvageable? Thanks for any help
If ADB is accessible, you could pull /sdcard/, and save it on your computer.
While waiting at the animation, plug it in to your computer, open a terminal, cd into whichever directory ADB resides, and run
Code:
adb devices
If it returns your tablet, then run
Code:
adb pull /sdcard/
adb pull /data/
It should copy everything from your internal storage and your app data into the directory containing ADB, but I'm honestly not sure if you could pull /data/ without root access. And even if you did, I'm not sure how you could safely restore the files without breaking something (or especially without root). At the very least, you'll have the contents of your internal storage.
At that point, you should be OK to wipe your data.
If that doesn't work, then assuming you're on the 4.2 bootloader, you could boot into the bootloader by holding Volume Down as you start your tablet, and you will automatically be in fastboot mode. This should allow you to flash a stock blob with fastboot. Instructions to do so have been posted throughout this forum.
If all else fails, it should still be under warranty since it's locked, so you could get a free replacement. I'm thinking the data wipe should be enough, though. Good luck.
Thank you kindly. I'll thank you later as I seem to be out of thanks today. Admittedly though, I'm not too experienced with this stuff and don't really know which directory ADB is in
Am I right in opening the command window inside sdk--> platform tools?
If so, no devices show up when running the "adb devices" command although I can see my TF300 in device manager
UndisputedGuy said:
Am I right in opening the command window inside sdk--> platform tools?
If so, no devices show up when running the "adb devices" command although I can see my TF300 in device manager
Click to expand...
Click to collapse
That's the right place, unfortunately. I'm assuming you have the ADB drivers installed and everything. Otherwise, install them, and try again.
If you can still get into the bootloader, you should be able to fastboot flash a stock blob. I don't believe that wipes data or your SD card, but I could be wrong. I know that flashing them in a custom recovery wipes both, but I don't think the fastboot method wipes either. Unless tobdaryl or someone else more experienced than I can think of another option, your only next move is using your warranty.
EndlessDissent said:
That's the right place, unfortunately. I'm assuming you have the ADB drivers installed and everything. Otherwise, install them, and try again.
If you can still get into the bootloader, you should be able to fastboot flash a stock blob. I don't believe that wipes data or your SD card, but I could be wrong. I know that flashing them in a custom recovery wipes both, but I don't think the fastboot method wipes either. Unless tobdaryl or someone else more experienced than I can think of another option, your only next move is using your warranty.
Click to expand...
Click to collapse
Thanks again for your help. I'll need to look into using fastboot to flash a stock blob.
I was able to find the device using adb and then run the "adb pull /sdcard/" command (thanks a ton for the help in doing that) but it seems like it's only pulling my files from my downloads and Ringtones folder and even then, it doesn't pull all of them within my downloads folder. Any idea on why this is happening?
UndisputedGuy said:
I was able to find the device using adb and then run the "adb pull /sdcard/" command (thanks a ton for the help in doing that) but it seems like it's only pulling my files from my downloads and Ringtones folder and even then, it doesn't pull all of them within my downloads folder. Any idea on why this is happening?
Click to expand...
Click to collapse
No, I have no idea why it's only pulling a couple directories. It should pull everything from the internal storage since the command includes the whole /sdcard/ directory. I hope someone else knows. If you remember the names of your most important folders, you could try pulling them individually to see if it gives you an error message. If it does, we have a starting point to fix it. If it pulls them fine, then I'll probably be stumped.
EndlessDissent said:
No, I have no idea why it's only pulling a couple directories. It should pull everything from the internal storage since the command includes the whole /sdcard/ directory. I hope someone else knows. If you remember the names of your most important folders, you could try pulling them individually to see if it gives you an error message. If it does, we have a starting point to fix it. If it pulls them fine, then I'll probably be stumped.
Click to expand...
Click to collapse
Thanks! I shall probably try that soon, but I currently want my files from the download folder so will have another stab at that. Thanks again for the assistance :good:
I have been able to pull some files using ADB and thank you greatly for your assistance in doing so. I hadn't really used ABD before but now I'm more familiar with it, so thanks. I have a question regarding using the fasboot method to flash a stock blob. Do I need an unlocked bootloader for flashing a stock blob? The guides I've found have suggested as such. My bootloader is locked.
Honestly, I'm not sure. I would imagine it would do a signature check before flashing, and since you'd be using the official ASUS firmware, it would pass. All I know for sure is that fastboot works on locked tablets. I have no idea to which extent it works.
EndlessDissent said:
Honestly, I'm not sure. I would imagine it would do a signature check before flashing, and since you'd be using the official ASUS firmware, it would pass. All I know for sure is that fastboot works on locked tablets. I have no idea to which extent it works.
Click to expand...
Click to collapse
Thanks again. You've been a great help
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
UndisputedGuy said:
Thanks again. You've been a great help
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
I was just about to post that your first step should be to wipe data and see if it boots before we get caught up in fastboot. That is a last resort here. If wiping data may work, fastboot is more work than necessary.
Just to confirm that my tablet did indeed start working again after wiping the data although the stock Asus Backup App fails to restore my app backups from a while ago. It stops at 15%.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I'll try to keep it short and keep a clear overview.
I rooted my Nexus 5 with the Towelroot app. Everything went perfectly fine (I had to do a recovery, but after that, Nexus running smooth and it was rooted.
Then I decided to try something stupid. Alter the Nfcnci.apk so that the NFC TAG scanning app was silent instead of the end.ogg noise when scanning a NFC tag.
It all went wrong when I merged the unpacked .apk files back into a .rar and convert it to a .apk with "formatter" program.
When I tried to put the NfcNci.apk app back in the system/app folder with authorisation 664 it didn't work anymore. the stock app crashed.
The nfc part of my phone wasn't working anymore ! (when opening NFC tools, i got a NFC ERROR message... apparently, i did something wrong when trying to replace the app with my modded version)
So i did the most stupid thing I could have done: instead of putting the original NfcNci.apk file back into the system/app folder I did a hard reset recovery (go into Recovery mode, wipe data)............
Now, with my freshly recovered nexus 5..... I CAN'T GO INTO SETTINGS to turn on USB debugging (because I clearly wanted to put the original 4.4.3 image back on my phone)
so i'm stuck with a phone that :
1) is rooted.
2) doesn't go into settings so I can't turn on USB debugging
3) doesn't go onto the app store because i can't link my google account because i can't go into Settings.
4) is actualy a dumbphone now. The only thing I can do is use stock apps and call and text someone.
Could someone PLEASE put me out of my misery?
i'm litteraly crying here. I had this phone for 2 weeks.....
I want to unroot the damn thing and go back to the way it was....
Best regards,
Tom
1) questions go into the Q&A forum.
2) you shouldnt mod stuff when you're not sure what you are doing
3) factory reset in recovery does not fix any mods you have made to /system, it only wipes data.
4) follow this to go back to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Fastboot doesn't need usb debugging on. Flash the stock files with fasboot. You will get back to stock but ur data will get erase.
or simply just flash the system.img which won't erase ur data
Code:
fastboot flash system system.img
varuntis1993 said:
Fastboot doesn't need usb debugging on. Flash the stock files with fasboot. You will get back to stock but ur data will get erase.
or simply just flash the system.img which won't erase ur data
Code:
fastboot flash system system.img
Click to expand...
Click to collapse
Yup, just pull the stock factory image from Google developers website and unpack it. Put system.img into your fastboot directory. Use CMD (assuming you're on Windows) and CD to that location and fastboot flash system system.img, like he said.
If you have trouble with fastboot follow the first link given to you.
thanks
Thank you all very much for your help.
I managed to put the stock img back to my phone.
the problem was that my phone wasn't unlocked, therefore I couldn't enter the fastboot command lines.
Phone is back to stock 4.4.3.
@Zepius you are right, you shouldn't mod stuff if you don't know what you are doing, but you do have to go through a learning process... you also had to do it for the first time once, right?
I think my big mistake was, not to follow the amazing guides here in XDA on how to root, change apk's etc etc...
one more question. IF you take a stock app (NfcNci.apk) do you have to sign it to be able to get it to work?
All i wanted to do was unpack the apk, change a sound file and repack it so that the darn NFC tag doesn't make that sound when I scan a tag, waking up my wife when i put it to sleep mode...
well, guess i'll hang the tag somewhere outside of our room
again, thank you all for your help and not bashing me.
Tom
tom_el_camino said:
I think my big mistake was, not to follow the amazing guides here in XDA on how to root, change apk's etc etc...
one more question. IF you take a stock app (NfcNci.apk) do you have to sign it to be able to get it to work?
Click to expand...
Click to collapse
Don't sign system apps, just take the AndroidManifest.xml and META-INF folder out of the original .apk, open the modified one with 7zip or your alternative and paste it in.
hey everyone,
I was looking around for a possible way to get around the root catchers, ie. android pay, snapchat, etc. and someone casually mentioned they use a clean partition to use those services and then boot their rooted partition for everything else. I've checked my secondary slot (_a) and it doesn't boot at all so im sure I've only got half some stuff flashed to it.
Is it as simple as switching to my secondary, booting into bootloader and simply flashing the required files like I did for my main partition? or do I need to just fastboot my system.img and boot.img? More importantly, does this actually work?
-I'm on 7.1.1 with TWRP alpha2 and SR5
Thank you thank you!
edit1: found this through some searching, my new question is assuming I use the "_a" prefix for the commands I should not touch my active slot correct?
edit2: It worked! For anyone wondering I just used the first set of commands from the thread linked in edit1. My custom kernel stayed on the system and I am able to use apps that normally lock out root!
I think it's important to flash both partitions and use the ignore secondary option and also make sure that the -w is not in the command line . Don't know the specifics, but a normal flash includes some files in the other partition, files it won't find if you only flash one slot. I could be wrong, but that's how I did it. Couldn't get it to run right when I only flashed one slot.ymmv.
dtrud0h said:
I think it's important to flash both partitions and use the ignore secondary option and also make sure that the -w is not in the command line . Don't know the specifics, but a normal flash includes some files in the other partition, files it won't find if you only flash one slot. I could be wrong, but that's how I did it. Couldn't get it to run right when I only flashed one slot.ymmv.
Click to expand...
Click to collapse
Alright so to confirm, since I seem to always confuse myself, as long as I remove the "-w" and use the command to not touch the other partition my data and what not should be fine? I haven't messed with the flash all in a while so I might just manually input those commands to make certain I don't mess up haha.
I'll tell you what happened with me.
I could run the altered.scripts/bat files, but the last segment wouldn't run.. . meaning the script would flash boot, and radio but wouldn't run the update command portion. I had to copy and paste into fastboot the last instruction anyway. I don't know why but that's what happened. One thing is to make sure image file message in the script matches what you have downloaded and extracted
. Either edit the bat or sh file accordingly.
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.
robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.
I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks
What version of twrp ?
I only use rc1, never seen this.
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snoping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT: Just saw help thread, Ill post there.
EDIT 2: I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
If you've already factory reset, I'd just download the factory images and flash those to start fresh. In the future, you could either use the magisk uninstaller to clear out magisk files, or you could mount magisk in recovery and delete the module causing issues.
jsauder2 said:
If you've already factory reset, I'd just download the factory images and flash those to start fresh. In the future, you could either use the magisk uninstaller to clear out magisk files, or you could mount magisk in recovery and delete the module causing issues.
Click to expand...
Click to collapse
Tried flashing new image and its keeps failing. Im using this Pixel 2XL guide.
I keep getting this:
JJT211 said:
Tried flashing new image and its keeps failing. Im using this Pixel 2XL guide.
I keep getting this:
Click to expand...
Click to collapse
You need the latest Platform Tools. Happened to me last night after I messed up installing TWRP and had to install factory images.
Its still not working. Let me summarize exactly what ive done.
I think im installing the platform tools correctly.
According to guide (windows) I just open command line and type:
adb --version
fastboot --version
That means Platform tools have been installed.
I then take the unzip the new factory image and place it inside the Platforms tools folder. I then navigate to the factory image folder from command line and type:
flash-all
I then get:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
followed by a failed message
So do yall think im bricked? Can anyone confirm what I've done above is correct?
Idk bro. I doubt it's bricked. I had adb and fastboot installed for years but they weren't the newest version. This was giving me the errors you are receiving. You're screenshot from earlier is exactly where and when I would get the error. Download the official Platform Tools from Androids site. I'm sorry this is happening
JJT211 said:
So do yall think im bricked? Can anyone confirm what I've done above is correct?
Click to expand...
Click to collapse
Very doubtful you're bricked. Try downloading the newest platform tools from Google's page if you haven't already. If it still doesn't work, I would try flashing the pieces individually through fastboot instead of using the flash-all command
Thanks for the swift replies talk.
Yea I grabbed the most recent version Platform tools from Google.
When you say flash individually vs flash all, what do you mean? Can you provide an example?
I dont know if you have done this already and I remember doing this with my og Pixel. The firmware has to be extracted from the zip (which I see you did already) and shown in pic1. Then there is a second zip inside that has to be extracted as well (pic2) and all of those files placed in the platform tools folder then you should be able to flash all. It will start to flash then pause for a min or two and look like there is something wrong but, then it should continue and reflash your phone.
JJT211 said:
Thanks for the swift replies talk.
Yea I grabbed the most recent version Platform tools from Google.
When you say flash individually vs flash all, what do you mean? Can you provide an example?
Click to expand...
Click to collapse
arodey said:
Idk bro. I doubt it's bricked. I had adb and fastboot installed for years but they weren't the newest version. This was giving me the errors you are receiving. You're screenshot from earlier is exactly where and when I would get the error. Download the official Platform Tools from Androids site. I'm sorry this is happening
Click to expand...
Click to collapse
Thanks man, I think my problem is close to this.
My previous laptop had an old version of Minimal ADB on it from a while back. I tried updating that, and still no luck. So I grabbed my work laptop that has never had any Android SDK stuff on it. I then downloaded most current Platform tools from Google. Using the same guide above, I installed both adb and fastboot. From the platform tools directory, it would recognize my phone when using 'adb devices' command and I could also reboot to bootloader using 'adb reboot bootloader' command. I then unzipped and copied factory image to same Platform tools folder. I moved to image directory and tried 'flash-all' command it could not recognize the command. See below
Code:
C:\Users\Me\Desktop\platform-tools\crosshatch-pd1a.180720.031>flash-all
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
To me that says that fastboot is not installed. But I definitely installed it.
Code:
C:\Users\Me\Desktop\platform-tools>fastboot --version
fastboot version 28.0.1-4986621
Installed as C:\Users\Me\Desktop\platform-tools\fastboot.exe
C:\Users\Me\Desktop\platform-tools>adb --version
Android Debug Bridge version 1.0.40
Version 4986621
Installed as C:\Users\Me\Desktop\platform-tools\adb.exe
Is there something Im doing wrong??
I don t know why but when I got my Pixel 3 I had to use Windows 10 Power Shell and fastboot commands were recognized. Min fastboot would not show fastboot commands but only ADB commands as operable.
JJT211 said:
Thanks man, I think my problem is close to this.
My previous laptop had an old version of Minimal ADB on it from a while back. I tried updating that, and still no luck. So I grabbed my work laptop that has never had any Android SDK stuff on it. I then downloaded most current Platform tools from Google. Using the same guide above, I installed both adb and fastboot. From the platform tools directory, it would recognize my phone when using 'adb devices' command and I could also reboot to bootloader using 'adb reboot bootloader' command. I then unzipped and copied factory image to same Platform tools folder. I moved to image directory and tried 'flash-all' command it could not recognize the command. See below
Code:
C:\Users\Me\Desktop\platform-tools\crosshatch-pd1a.180720.031>flash-all
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
To me that says that fastboot is not installed. But I definitely installed it.
Code:
C:\Users\Me\Desktop\platform-tools>fastboot --version
fastboot version 28.0.1-4986621
Installed as C:\Users\Me\Desktop\platform-tools\fastboot.exe
C:\Users\Me\Desktop\platform-tools>adb --version
Android Debug Bridge version 1.0.40
Version 4986621
Installed as C:\Users\Me\Desktop\platform-tools\adb.exe
Is there something Im doing wrong??
Click to expand...
Click to collapse
Archangel said:
I dont know if you have done this already and I remember doing this with my og Pixel. The firmware has to be extracted from the zip (which I see you did already) and shown in pic1. Then there is a second zip inside that has to be extracted as well (pic2) and all of those files placed in the platform tools folder then you should be able to flash all. It will start to flash then pause for a min or two and look like there is something wrong but, then it should continue and reflash your phone.
Click to expand...
Click to collapse
IT WORKED!!
So not only do you need to extract that 2nd zip file into same directory but apparently you also need to keep that 2nd original zip file in there as later on during the install, the script tells it to extract it. It wont work without that original zip.
Thanks everyone!!
Awesome brother glad you got it working!
JJT211 said:
IT WORKED!!
So not only do you need to extract that 2nd .zip file into same directory but apparently you also need to keep that original .zip file in there as later on during the install, the script tells it to extract. It wont work without that original zip.
Thanks everyone!!
Click to expand...
Click to collapse
Good work man!!!
Been a while since I used magisk. Does Google Pay still work if bootloader is unlocked and magisk enabled?
Sent from my Pixel 3 XL using Tapatalk
bigdave79 said:
Been a while since I used magisk. Does Google Pay still work if bootloader is unlocked and magisk enabled?
Click to expand...
Click to collapse
Yes.
JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
I had to RMA mine it did the exact same thing
JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
Flash Factory image . I had the same thing after messing some magisk modules.