I flashed franco kernel nighltie r364 on a JB 4.2 stock rom on a Galaxy Nexus, now the internal SD won't mount..
Have I permanently lost all the data? can someone please explain how I can recover/resolve this.
I've tried to mount it in TWRP and it's unselected (default set to mount), yet after a reboot I still can't access the internal sdcard.
Also, no apps work, I guess it's cause they're all on the internal sdcard.
Finally the name 'legacy' appears under the sdcard0 folder (it actually looks like a file now with a golden star against it), I see this using root explorer; the only app that works.
If anyone can help it would be appreciated...
---
smash'n
SGS2 GT-I9100
Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.
beekay201 said:
Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.
Click to expand...
Click to collapse
I'll pm you, if you don't mind
---
smash'n
SGS2 GT-I9100
beekay201 said:
Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.
Click to expand...
Click to collapse
Thanks for poiting me in the direction of adb!
I swear I'll never mess with a Nexus again.
I resolved all I needed but took 12hrs and no sleep to get adb to recognise (with a bit of tom foolery) and pull the files we needed.
I"m just gona wipe the whole phone and start a fresh.
Now time to enjoy the rest of our hols.
At least we saved our child's photos.
Thanks again.
---
smash'n
SGS2 GT-I9100 (and never will be Galaxy Nexus)
UPDATE.
I just want to update this thread regarding my experience.
Firstly, this problem occured again!!
This is how I solved it;
[SOLVED]
Well I spent allnight/day (18hrs really)reading and conducting a whole host of procedures, from; using adb too resorting back to stock.
Needless to say nothing worked correctly!!
What I eventually did was to use WUGFRESH Galaxy Nexus Toolkit v1.6.4 and it stripped (reformatted) the phone and placed a clean stock firmware back.
I say reformatted hestitantly, as all other methods that I used and know of (from my time modding my S2) didn't work, at all (when applied to this phone) as each time the internal storage 'could not be mounted or accessed', I can only imagine something was severely corrupted.
WUGFRESH downloaded the necessary files and during its running, automatically indicated that some files could not be accessed or weren't present on the phone (I read this via the cmd screen on WUGFRESH), it then tx and loaded the necessary files (what I can describe as a reformat) and after all processes I rebooted and vola! access to internal storage regained.
Also, just to add, [before I started the process] the same WUGFRESH SW also allowed me to pull files from the internal storage (personal family photos and videos), even though adb wouldn't mount the storage or push or pull files from the phone, all other procedures/methods I tried wouldn't work either! WUGFRESH was the only one that worked.
After everything, I conducted a nandroid! what a headache, and it aint even my phone (it belongs to my fiancè).
Thanks for all the support in the thread, needless to say I hope all my experience in the last 18hrs helps someone else.
---
smash'n
You're holding it wrong. You should have read the stickies, but your goal wasn't to learn anything anyways so..
and another thing: not that I use it, but it's WUGFRESH toolkit - at least get the name right. It bothers me when people don't call stuff by their names.
don't create 2 threads for the same issue. Reported.
soz on the wrong naming of WUGFRESH.
REPORTED? Why? my two threads were ligit!, all posted in Q&A, based on the same issue but within two areas
1. stock recovery
2. this thread
---
smash'n
SGS2 GT-I9100
So it took you 18 hours and you never tried ADB or Fastboot by itself?
toolkits are nothing more than a front end hiding the commands from the user by using ADB and Fastboot...congrats on learning nothing in the process? I see nothing in your resolution that indicates that the GOOGLE provided tools would not work.
Sigh....another toolkit thread. YAY!
Pirateghost said:
So it took you 18 hours and you never tried ADB or Fastboot by itself?
toolkits are nothing more than a front end hiding the commands from the user by using ADB and Fastboot...congrats on learning nothing in the process? I see nothing in your resolution that indicates that the GOOGLE provided tools would not work.
Sigh....another toolkit thread. YAY!
Click to expand...
Click to collapse
YES, I tried adb cmds and bootloader/fastboot (as I mentioned above) same as I would on a S2, each time reverting back to stock on this nexus never gave access to the internal storage; this was the problem.
Hence I used a toolkit, and it worked.
I'm not an expert in modding android but I know some stuff, and this nexus wasn't playing to a rule book, as all the adb cmds and methods I found online (and are basic) never worked, no thread gave a solution that worked, similar google searchers.
I didn't go into this blind, but I never expected so much hassle modding this phone, as I rooted it and flashed a stock ROM weeks/months ago without problems.
As for learning anything (you're the 2nd person to mention it), I've learned a lot from the xda community (personally) and through threads.. though the issue I experienced was never written about in the sense I experienced it and had to resolve it.
---
smash'n
SGS2 GT-I9100
Related
Okay i have a big problem...
I have rooted my device, however didn't run the ENG build, so my recovery is dependent on the pushing of the update.zip...
I flashed the myfroyo5 after pushing the update.zip... and ADB worked great, found the device in HBOOT and recovery.
Now after flashing this ROM, when i try and reboot back HBOOT no devices found.. however when i'm at the home screen with Myfroyo5 booted up, it sees the device..
Now i can't run any update, or get into clockwork recovery because i can't push the update.zip, because ADB can't see my device....
Please help! Any idea how i can get it to see my device with Myfroyo5? Otherwise i'm stuck with Myfroyo5 and can't reverse or do anything with it
Before all i did was change the option from device storage, to charge only, and that's how it worked...
again any ideas are appreciated!
wow 58 views and no one has any ideas? Please help!
Try turning on USB debugging mode?
Yes its always on, always check marked
I feel like I did have a similar problem at one point, but I don't remember how I resolved it. Sorry.
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
tubaking182 said:
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
Click to expand...
Click to collapse
Must your replies always, ALWAYS have some snarky bit about how the person asking the question screwed up?
Humans are prone to error. You have valuable insight but beating someone's ego up before you give it really offsets your kindness.
Sent from my T-Mobile myTouch 3G Slide using XDA App
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I see your point but, as I recall, the ENG build came after root had been put out there for a day or so. I'm also pretty sure it came after SlideMeRoot1.
Things like this, along with simple mistakes, can cause these errors. You are helpful but I just find the "hey, dummy" tone to be overkill.
Not everyone who screws up is out to **** up your day, ya know? I've been having my own ENG build problems because I made a mistake. It doesn't mean I don't know how to follow directions, it just means I made a mistake, the way every human on the planet does.
I apologize, as well, because my own real life smiley fun tone doesn't translate well to the forum. IE: you good kid.
tubaking182 said:
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using XDA App
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
Just use CR new root method for the ota update and then follow the steps to flash ENG build. wouldnt that work? cause its unneccessary for the device to be recognized in hboot in adb that way =\ just guesing
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
javolin13 said:
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
Click to expand...
Click to collapse
do u have root in the shell script when u try to push the files over?
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
javolin13 said:
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
Click to expand...
Click to collapse
i mean u could always just unroot and start from square one
can't unroot if my device is not seen with adb in hboot / recovery
javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Suntar said:
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Click to expand...
Click to collapse
Thanks for the idea, but flashing the ENG build is pointless unless i can push the flash_image, and mtd0.img to /data/local... which for some reason my phone will not allow me to do this part;
Code:
type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
I unlocked my bootloader and flashed a Bigxie Jellybean rom this morning for the first time.
Everything was going great until I tried to reboot for the 4th time and now there is no boot animation.
I tried doing a factory reset in CWM as well as wiping the cache but it didn't help.
I also don't have the Jellybean zip file any more.
What do I do now?
Is there a way to push the zip file to my phone and try again?
Use search, there's a lot of threads about this; next time read before you do stuff, hope this serves as a lesson.
Sent from my i9250
Read? All I've done for the last 2 days is read. And when I finally tried it everything worked well.
Anyway, I managed to fix it. Pushed over the update file with Wugfresh Toolkit and flashed it again.
Eliott said:
Read? All I've done for the last 2 days is read. And when I finally tried it everything worked well.
Anyway, I managed to fix it. Pushed over the update file with Wugfresh Toolkit and flashed it again.
Click to expand...
Click to collapse
Glad you solved it.
You asked a good question "Is there a way to push the zip file to my phone and try again?", awnsered and asked by people like probably dozens of times now. How can you miss it? Simple, you didn't search well.
This was the first result, on regional google, for the search tag "xdadev push zip". Sure, we could have used other tags like "android push zip", but it's for a subforum on Archos Gen8, Gen9; it tells you how to push a script, which is a file, then the command gotta be the same. Oh, what's this, ADB!?
Once again, regional google search first hit was this when searching for tag "adb". Reading the linked webpage, you see a bit down further
Copying Files to or from an Emulator/Device Instance
You can use the adb commands pull and push to copy files to and from an emulator/device instance's data file. Unlike the install command, which only copies an .apk file to a specific location, the pull and push commands let you copy arbitrary directories and files to any location in an emulator/device instance.
To copy a file or directory (recursively) from the emulator or device, use
adb pull <remote> <local>
To copy a file or directory (recursively) to the emulator or device, use
adb push <local> <remote>
Click to expand...
Click to collapse
Great. We know what is adb, and what can we use it for. So, this topic was about bootanimation disapearing. You solved it by pushing a rom zip and reflashing. You could have just searched for "xdadev android bootanimation galaxy nexus" and you would have found this, the third result on google.
This would tell you where bootanimation file is located at, so you'd have known how to push it, where to push it.
You see, you didn't search well. You spent 2 days searching, I spent 10 minutes, like I didn't know a thing about android.
Hi XDA users,
I am in a strange position right now, it is already two years I browse the site, and root and install custom roms on my phones.
Right now, I have a problem with my galaxy nexus, the device is rooted, I can access CWM recovery, but I did accidentally wipe my internal SD , which means no backup to restore from. I know it s silly, but it had to happen. So I can enter fastboot mode, recovery mode, but as there is nothing to use on the recovery , I d rather go for the fastboot way.
But what I am asking help for is , how can I inject the stock image? I feel the phone is not dead, at all, but I don't know how to proceed, I would gladly try the toolkit, but I m on a mac, 10.8, hence I can't run the toolkit. Anyone to help me get out of trouble please?
I can of course reach a PC, if absolutely needed, but I can make proper procedure on my laptop, it would be better.
Thank you in advance for any direction , advice , one could provide me with.
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40C)
3rdstring said:
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40C)
Click to expand...
Click to collapse
Hi, many thanks for your reply, however, when I use terminal on my mac, the device is not recognised, there is no response . Still I m looking at my phone with the droid on his back, belly open. The main thing is I don't know how to get it recognised by my mac.... rrrrrr !!!! I m confident it will work out some time, but now, I m still stuck. And I m not really easy with adb, but willing to learn...
When in terminal and I type ./fastboot-mac devices it reads " no such file or directory, so what am I doing wrong? Maybe a question , in terminal, when I want to indicate in which folder is the platform-tools-v6 folder , ijust drop it in the terminal window... Am I right or completely wrong?
Usually I tend to read tens of pages in xda, and it is not like I want to be spoon fed, but since yesterday I m trying to go through all the troubles I have, but so far no luck!!!
Thanks anyways to whoever will help me out.
Aur3L said:
When in terminal and I type ./fastboot-mac devices it reads " no such file or directory, so what am I doing wrong? Maybe a question , in terminal, when I want to indicate in which folder is the platform-tools-v6 folder , ijust drop it in the terminal window... Am I right or completely wrong?
Usually I tend to read tens of pages in xda, and it is not like I want to be spoon fed, but since yesterday I m trying to go through all the troubles I have, but so far no luck!!!
Thanks anyways to whoever will help me out.
Click to expand...
Click to collapse
When your in a terminal window you want to change directories to where you have the platform tools & image files before typing in the commands. I'm not sure how you do that on a Mac. Inversely you could copy the platform-tools files & the image files to where ever the terminal window opens.
Well, yes, but it drives me crazy to not know where the terminal is looking at... However, I managed to connect to my phone in fastboot, there was a script I pasted in the terminal window, which I have executed several times, and which made the phone reboot in fastboot mode.
So there is some kind of progress... :fingers-crossed:
What mistake have I done yesterday.....
I also tried through heimdall 1.3.2, which detected the device, but could not load anything properly, so I gave up that option , back with the fastboot mode.
So I m not sure how I will manage it, but I m not done with it now.
Edit: Finally, I managed to get control of the the phone, thanks to the work of Techfanatic9 and his Gnex toolkit for mac. What a relief, but in the meantime it got me to deal with adb, and I guess I will certainly dig deeper in this way to interact with phones .
So, of course, many thanks to 3rdstring for being so helpful and so fast ! All is well that ends well.
this is the link that got me out of trouble , so if you happen to be a mac user and get a bit out of control with your phone , check it out.
http://forum.xda-developers.com/showthread.php?t=1790399
Phone Was working fine on latest PA rom until battery died. Upon charging and rebooting up, the Rom some how got corrupted i guess, because it now just boots logo forever. I don't have any roms on the device itself so can't reinstall anything through recovery to try to fix whatever may have got corrupted. I know there is a way to Side Load with TWRP, but am running into difficulties. I do have the drivers for the nexus installed. I can't directly drop files through windows because it doesn't read in recovery and read up upon researching the Side load function. So I downloaded the ABT bundle zip folder and placed it in C folder, but that's where i'm stuck. I've tried looking a few things up but every time i try to run Adb command in the platforms folder it just opens and closes within a second. not sure what i'm missing. i've tried looking at other ways but most other phones have the capability of just throwing it on to the SD card which helps other people. thanks in advance.
Tl:dr Need to get a rom file onto the Nexus, to install and repair my corrupted rom.
you run adb from COMMANDLINE, it sounds like you are trying to double click the adb.exe....that will never work. adb is a commandline tool
ok, i'm pretty much a noob, don't know how to do that but i'll google it first before i bug any more. thanks again.
Since you are using windows, while looking at the explorer window that contains the adb/fastboot exes, hold down shift and right click somewhere in the blank space within the folder...OPEN COMMAND WINDOW HERE
once you have a DOS prompt open in that location, type 'adb devices' without any quotes to see if your device is being recognized.
there is an entire thread dedicated to walking you through this whole process.
start reading here:
http://forum.xda-developers.com/showthread.php?t=1812959
this site contains all the info you need.
I googled it and got it set up and working. it does recognize my device. now i'm reading up on the command to send the zip file. seriously, thanks for the feedback. been sitting here for like 2 hours trying to figure this out without pulling out my hair and tossing the phone lol.
You could have just read the stickies... Why people don't get curious about things like "RETURN TO STOCK ON ANY GALAXY NEXUS VARIANT" or "ANDROID 101", I'll never understand.
a manta wrote this.
OK so first of all, if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.
I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.
I've tried using usb 2 and 3, no difference. I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.
My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Thank you for the suggestions, tried it but no dice sadly. I kinda am hairy on rooting it too as I just got the phone and it's been a long time since I've done android dev work. If you have any other ideas I'd be welcome to hearing them but again thanks for trying.
simplepinoi177 said:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Click to expand...
Click to collapse
Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.
Strephon Alkhalikoi said:
Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.
Click to expand...
Click to collapse
Great idea! And that's why veterans and those with experience are the best to go to...!
OK so first, thank you so much for all the advice. I've taken awhile to get back to you because this took some time to parse. I'm admittedly kind of a novice at this. So I've used the instructions here https://www.xda-developers.com/how-to-install-twrp/ to try and install twrp. I think I did it right, had the zip contents and img file in the same directory that adb is in, then ran the command...and this is what I got back.
N:\platform-tools>fastboot flash recovery twrp-3.2.3-1-taimen.img
Sending 'recovery' (40960 KB) OKAY [ 1.203s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.219s
as the 'fastboot reboot' command appeared to bring me right back to normal operating for the phone I'm guessing the failed stopped me with that 'flashing not allowed in lock state' there. Am I missing a step?
close, but not exactly right...
you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...
but you don't ever (underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:
Code:
fastboot boot twrp-3.2.3-1-taimen.img
Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...
Good luck to you and hope this helps...
Hey everyone. So I tried this but it also didn't work. Same error 'cannot in locked state' when trying to run the command. I do notice there's a green 'locked' on my phone when it's in the screen after the 'adb reboot bootloader' command. Any ideas?
simplepinoi177 said:
close, but not exactly right...
you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...
but you don't ever (underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:
Code:
fastboot boot twrp-3.2.3-1-taimen.img
Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...
Good luck to you and hope this helps...
Click to expand...
Click to collapse
AshtonHunter said:
OK so first of all,
if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.
I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.
I've tried using usb 2 and 3, no difference.
I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried
looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.
My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?
Click to expand...
Click to collapse
AshtonHunter said:
Hey everyone. So I tried this but it also didn't work. Same error 'cannot in locked state' when trying to run the command. I do notice there's a green 'locked' on my phone when it's in the screen after the 'adb reboot bootloader' command. Any ideas?
Click to expand...
Click to collapse
You would only get this error if your device isn't "unlocked"... I/we were all under the impression that (which is why I quoted) your device is "unlocked"... So maybe some clarification is in order...
There are two types of "unlocking" that can be attributed to the device; 1) your device can be "locked" to a carrier or global region, and it can be "unlocked" so the device can be used on any network anywhere, and 2) all Pixel's (and all smartphones AFAIK) have their bootloader in a locked state, and in order to do any kind of "rooting" or data restore/recovery or modification down to the system level you have to "unlock" the bootloader or have it in an "unlocked" state.
*BEWARE! Before running these commands, please note that running critical will erase/wipe EVERYTHING -- I am pretty sure running both will actually cause this to happen.
Considering all of this, when you said your "...phone is unlocked", you are speaking in terms of #2 I listed above, correct? Basically, you have run the command -- while in Bootloader Mode -- "fastboot flashing unlock" & (just as important, imho) "fastboot flashing unlock_critical", right? Because, if you haven't done these, then your device was never "unlocked" (in the sense that most relates to us and what you are intending) as well as without having one these commands, you had no chance at restoring your /data folder or partition "data" (pun not intended).
After clearing any misunderstanding and/or issues of these type, we might be able to better help after that point...but it is looking like you may need to root or at least do the same steps towards that end to accomplish what you are seeking...
So, get back to me/us on this, and hope this all helps...
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
AshtonHunter said:
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
Click to expand...
Click to collapse
What exactly are you wanting to do now that your bootloader is unlocked, and you have twrp? Can I assume you want to root it?
AshtonHunter said:
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
Click to expand...
Click to collapse
I'm glad you were successfully able to get it done! (clicking a "Thanks!" would be all I would welcome in return)
So, now, you might be able to successfully do what you originally did and restore through adb if you wish...I mean, if you simply have a /data folder that's been backed up, there might not be too many options available for you. Another thing you might try is running a custom recovery (TWRP I believe is the best or only) and restoring -- and/or backing up from your old device/phone, wiping everything, setting phone up, then use that TWRP backup to restore -- but you can only really run a restore if it was a TWRP backup to begin with... One other good way is running a Titanium Backup backup and restoring that way...
Good luck and hope this helps...
please help
simplepinoi177 said:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Click to expand...
Click to collapse
sorry in advance, I'm not very familiar with this webiste.
Im in a similar situation where it wont let me restore my adb backup, I am rooted and the bootloader is unlocked (though twrp is not installed). could you please help, i beg you.