Related
I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!
That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App
Wait. I have a normal reboot. Maybe mine is messed up?
Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.
Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer
jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse
I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...
Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App
Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.
OK I apologize ahead of time for what is probably a ridiculously easy question for most.
The ATT 1X is my first android and this is the first phone that I've rooted.
I read for hours and followed the instruction to a T. I rooted, unlocked the bootloader and installed CWM.
I can get into Recover/Boot mode or whatever you call it on phone startup, I have the Super user icon in my files, but I have no idea what to do now.
I found a ROM that I thought was worth a shot (CleanROM 2.5) but I don't know what to do. I've read and researched for hours now and everyone's problems seem to be complicated but no one talks about this.
I downloaded the ROM to my computer but I don't know what to do with the files, I can't find a .bat file or anything to initialize it and I am stuck.
I've wiped the data and done everything in the steps but I'm stuck at actually installing it. I know I'm obviously doing something wrong but I feel like I'm very close to what needs to be done.
Any help is welcome, thanks
deblas66 said:
OK I apologize ahead of time for what is probably a ridiculously easy question for most.
The ATT 1X is my first android and this is the first phone that I've rooted.
I read for hours and followed the instruction to a T. I rooted, unlocked the bootloader and installed CWM.
I can get into Recover/Boot mode or whatever you call it on phone startup, I have the Super user icon in my files, but I have no idea what to do now.
I found a ROM that I thought was worth a shot (CleanROM 2.5) but I don't know what to do. I've read and researched for hours now and everyone's problems seem to be complicated but no one talks about this.
I downloaded the ROM to my computer but I don't know what to do with the files, I can't find a .bat file or anything to initialize it and I am stuck.
I've wiped the data and done everything in the steps but I'm stuck at actually installing it. I know I'm obviously doing something wrong but I feel like I'm very close to what needs to be done.
Any help is welcome, thanks
Click to expand...
Click to collapse
I recommend you check QA thread found in a sub forum under your devices section and you review the stickied post for ROM install or Google "android install custom ROM " (remove quotes). Too much info on this already to type it all back out here. Did you watch you tube newb video you agreed to have watched when getting an xda account?
Essentially you now made it so your phone has the ability via CWM Recovery to now boot to that to install ROM zip or continue to use rooted stock ROM (how you flashed that zip for superuser is baasically same as how you flash a cwm compatible ROM zip (MOST but not all ROMs)) which with SuperUser can now run privelleged code if it is made to or requires it to run.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
Thanks. I know this must seem so stupid, but I've been searching this forum, google, youtube and pretty much everything else for how to do this and I get it all and understand what's happening.
I just don't know where to put this ROM (which folder) to get it to install.
deblas66 said:
Thanks. I know this must seem so stupid, but I've been searching this forum, google, youtube and pretty much everything else for how to do this and I get it all and understand what's happening.
I just don't know where to put this ROM (which folder) to get it to install.
Click to expand...
Click to collapse
So after all that searching you never came across instructions informing you to put the zip on your phones storage?
You should probably just hold off a bit on flashing anything then. Not being mean but it sounds like you are confused by the process and end result. Step back and do some basic checklisting.
Sent from my HTC One X using Tapatalk 2
Download the rom you want and DO NOT UN ZIP IT. THEN PLACE THAT ZIP ON PHONE STORAGE AND BOOT INTO YOUR CUSTOM RECOVERY . HIT INSTALL FROM SD CARD AND MAKE SURE THE ROM YOU DOWNLOADED IS LISTED BUT DONT FLASH YET. GO BACK THE THE MAIN SCREEN OF RECOVERY. NOW MAKE A BACKUP. WHEN THAT IS DONE GO BACK TO MAIN RECOVERY SCREEN AND HIT WIPE PHONE DATA AND THEN CONFIRM. THEN GO AND HIT CLEAR CACHE OPTION. THEN GO BACK AND GO TO ADVANCED AND CLEAR DALVICK CACHE. NOW YOUR READY TO FLASH. GO TO INSTALL ZIP FROM SD AND FLASH YOUR ROM. FIRST BOOT ALWAYS TAKES LONG AFTER FLASHING A NEW ROM :thumbup:
Sent from my HTC One X using XDA
Pirateghost said:
So after all that searching you never came across instructions informing you to put the zip on your phones storage?
You should probably just hold off a bit on flashing anything then. Not being mean but it sounds like you are confused by the process and end result. Step back and do some basic checklisting.
Click to expand...
Click to collapse
Been posting on the internet for decades, don't worry about being mean. I'm here to learn. I rooted, unlocked the bootloader and installed CWM so that I could take advantage before the phone asked me to update the software to the 1.85 version.
My phone works fine now, and I did everything correctly which is what I was setting out to do. I'm in no rush to flash a ROM, but now that I'm ready I'm itching to try it out.
Driggity420 said:
Download the rom you want and DO NOT UN ZIP IT. THEN PLACE THAT ZIP ON PHONE STORAGE AND BOOT INTO YOUR CUSTOM RECOVERY . HIT INSTALL FROM SD CARD AND MAKE SURE THE ROM YOU DOWNLOADED IS LISTED BUT DONT FLASH YET. GO BACK THE THE MAIN SCREEN OF RECOVERY. NOW MAKE A BACKUP. WHEN THAT IS DONE GO BACK TO MAIN RECOVERY SCREEN AND HIT WIPE PHONE DATA AND THEN CONFIRM. THEN GO AND HIT CLEAR CACHE OPTION. THEN GO BACK AND GO TO ADVANCED AND CLEAR DALVICK CACHE. NOW YOUR READY TO FLASH. GO TO INSTALL ZIP FROM SD AND FLASH YOUR ROM. FIRST BOOT ALWAYS TAKES LONG AFTER FLASHING A NEW ROM :thumbup:
Click to expand...
Click to collapse
This is the process as I understand it and as stupid as it sounds, I'm hung up on where in phone storage to place the zip file of the rom. I don't see a storage folder, an SD folder, nothing that seems obvious and nothing that is in any of the things I've been reading or watching.
deblas66 said:
Been posting on the internet for decades, don't worry about being mean. I'm here to learn. I rooted, unlocked the bootloader and installed CWM so that I could take advantage before the phone asked me to update the software to the 1.85 version.
My phone works fine now, and I did everything correctly which is what I was setting out to do. I'm in no rush to flash a ROM, but now that I'm ready I'm itching to try it out.
This is the process as I understand it and as stupid as it sounds, I'm hung up on where in phone storage to place the zip file of the rom. I don't see a storage folder, an SD folder, nothing that seems obvious and nothing that is in any of the things I've been reading or watching.
Click to expand...
Click to collapse
Plug phone into computer. When prompted, select Disk Drive. On computer, browse to your computer, open the 'disk drive', and copy the zip there. THAT is your sdcard as seen by your phone.
Pirateghost said:
Plug phone into computer. When prompted, select Disk Drive. On computer, browse to your computer, open the 'disk drive', and copy the zip there. THAT is your sdcard as seen by your phone.
Click to expand...
Click to collapse
Seriously?
Wow I feel dumb. I was looking for a sub folder or directory specifically for storage and backup.
Thanks, I think that should be enough for me to do this tonight.
deblas66 said:
Seriously?
Wow I feel dumb. I was looking for a sub folder or directory specifically for storage and backup.
Thanks, I think that should be enough for me to do this tonight.
Click to expand...
Click to collapse
Yeah, some phones you may have to drag down notifications and tap USB mode or USB connected notification (it has standard USB icon and only appears when phone attached to computer). Then tap either USB storage mode or the button to enable USB drives. Then on computer just like a thumb drive it adds drive letter. Copy anything there that is /mnt/sdcard or /sdcard on phone. BE SURE TO EJECT DRIVES BEFORE AND TAP TO DISABLE USB ON PHONE IN THAT ORDER THEN UNPLUG FROM USB (failure to do so COULD result in data loss or corruption which you DO NOT want to happen to a ROM zip)!
Then boot in to recovery choose install zip from sdcard (not apply update from sdcard) as install from allows you to browse for any zip and install. Usually Vol up and down moves through menus and power or search button is enter. BE SURE THE ROM YOU DOWNLOAD IS SPECIFICALLY MEANT FOR YOUR DEVICE OR YOU COULD EASILY BRICK YOUR DEVICE. PLEASE REVIEW HOW TO RUN NANDROID BACKUPS AND RUN ONE BEFORE INSTALLING A DIFFERENT ROM.
I CAN NOT STRESS ENOUGH IF UNSURE DON'T PROCEED, BE SURE YOU RUN NANDROID BACKUPS AND ENSURE YOU FOLLOW INSTALL DIRECTIONS INCLUDED WITH YOUR ROM. ALSO, NEVER FORMAT EMMC (AKA INTERNAL SDCARD) IT ALMOST GUARENTEES A BRICKED DEVICE.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
Wow that was easier than I thought.
Thanks for the help guys and sorry I missed such an easy step.
ROM installed.
deblas66 said:
Wow that was easier than I thought.
Thanks for the help guys and sorry I missed such an easy step.
ROM installed.
Click to expand...
Click to collapse
Is all good, and now you see why we were kinda scratching our heads wondering what was up a little . Glad we could help get you going though welcome to the world of custom ROMs. Please just be careful and always do backups and take it slow and read things 2x before even attempting once. While it can be easy to do it is also easy to accidentally brick your device (make it not work and have to be sent out for repairs).
Sent from my SGH-T989 using Xparent Green Tapatalk 2
Most of the time when one flashes a new ROM one has to do a data wipe (factory reset), and it erases all one's personal files like movies, music, pictures etc, quite annoying to say the least.
I found a way to avoid this, and it's pretty simple:
1-in CWM go to mount,
2-mount both data and system,
3-format them both.
This will perform the factory reset without erasing our precious files (the installed apks will be gone though, but no biggie if you backed up them with Titanium).
Then you can wipe cache + dalvik and flash your new ROM.
I used this method to go from ICS to CM 10.1, from CM 10.1 to Paranoid Android, and finally back to ICS, without loosing a single kb of my files.
Edit:
I have a p6210, no idea whether it works on other models or not. I guess it does but who knows...
Give it a try if you feel like it, but don't forget to make a back up before in case it goes wrong.
After flashing, your files won't be in the mnt/sdcard anymore but in a newly created folder in mnt/sdcard/0, or, depending the rom you are using, in storage/sdcard/0.
Or, some roms may create a file called legacy and stock everything there, or sometimes your files may be stocked before the sdcard folder, search for either /0 or /legacy.
Use a root browser and have a look, your files are still in your device (have a look as well at your storage in general settings, it will show how many gbs are in your tab).
Once you have found your files all what you have to do is to move them back where they belong, ie the /sdcard folder, it takes 10 seconds.
unclefab said:
Most of the time when one flashes a new ROM one has to do a data wipe (factory reset), and it erases all one's personal files like music, pictures etc, quite annoying to say the least.
I found a way to avoid this, and it's pretty simple:
1-in CWM go to mount,
2-mount both data and system,
3-format them both.
This will perform the factory reset without erasing our precious files.
Then you can wipe cache + dalvik and flash your new ROM.
I used this method to go from ICS to CM 10.1, from CM 10.1 to Paranoid Android, and finally back to ICS, without loosing a single kb of my files.
Give it a try if you feel like it...
Click to expand...
Click to collapse
Not cool man.Fu** lah.I lost everything.Around 7 GB of files.Fu** lah.I have no backup.I thought it would work.I was going from cm10.1 to cm10.What am I going to do?
Re: Easy way to keep one's personal data after flasing a new ROM
ALWAYS create a backup before erasing/flashing ANYTHING!! It's always as a precaution, to avoid losing something that you don't want to. And it only takes like 5 seconds literally. I lost some stuff when I unlocked the bootloader on my nexus10 by factory resetting, and I must say I didn't have a smile on my face. But it happened, u live n learn. I'm afraid if u wiped without making a nandroid backup your probably out of luck. Unless your skilled in using forensics techniques to try to recover it. Can't think of any options tho.
Sent from my SCH-I535 using xda app-developers app
Balaram12 said:
Not cool man.Fu** lah.I lost everything.Around 7 GB of files.Fu** lah.I have no backup.I thought it would work.I was going from cm10.1 to cm10.What am I going to do?
Click to expand...
Click to collapse
What did you do?
Did you follow the exact procedure?
I flashed again some roms today and it worked again.
But one thing is that the files are not in the mnt/sdcard anymore but in a newly created folder in mnt/sdcard/0, or, depending the rom you are using, in storage/sdcard/0.
Or, some roms may create a file called legacy and stock everything there, or sometimes your files may be stocked before the sdcard folder, search for either /0 or /legacy.
Use a root browser and have a look, your files are still in your device (have a look as well at your storage in general settings, it will show how many gbs are in your tab).
Once you have found your files all what you have to do is to move them back where they belong, ie the /sdcard folder, it takes 10 seconds.
This said, meishkov is right, one should allways have a back up in case anything goes wrong, I should have mentioned it in the OP but I forgot, my bad...
Edit:
OP edited.
Oh well, noone tried?
Would be nice to hear some reports...
Balaram, it would be fair from you to detail a bit what happened and to tell if you found back your files.
Anyway, this method worked for me and I thought that it might have interested some people here, roms flashers and devs alike, but if that s not the case then no worries.
If someone feels that I should erase the whole thread just tell me and I ll do it...
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
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.