Related
So im stuck with my nexus with no OS... after flashing pure shamu it booted to just a password box... I input my password and it said i had corrupt data. I hit reset... wiped phone... all files GONE... Now what do i do. I cant mount to put recovery on.... I cant do anyting with this phoen right now... anyone had this happen... If so what steps to remedy?
Sounds like you need to try and fastboot the original google files, nuke and repave....
flash the stock img then start again
Flashing stock as we speak... was hoping another optino.... but after years of doing this I kinda know better... live and learn
hell
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
asphalte7 said:
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
Click to expand...
Click to collapse
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Evolution_Freak said:
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
asphalte7 said:
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
Click to expand...
Click to collapse
Should be able to boot twrp now.
but i have to unlock first ... my device is locked
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
you cant unlock it without booting up and enabling allow oem unlocking in the developer options
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
If you can boot to TWRP recovery, then you can ADB push a ROM to recovery and boot it.
Edit: Sorry, I missed the fact that TWRP had been deleted too.
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Evolution_Freak said:
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Click to expand...
Click to collapse
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
Or, if you are still in fastboot, issue this command > fastboot reboot recovery
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
asphalte7 said:
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
Click to expand...
Click to collapse
Then I'm afraid you may be stuck. A RMA may be in your future if no one else can offer a solution.
simms22 said:
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
Click to expand...
Click to collapse
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
asphalte7 said:
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
Click to expand...
Click to collapse
flashing twrp..
fastboot flash recovery recoveryname.img
and flashing a factory img is done while the phone is in its bootloader. there are instruction how here on xda. but to be honest, i dont know if that will work. where did you buy your n6 from btw?
Ok so, this is my first post on xda, and because my (sprint) Nexus 6 is stuck on a boot loop. When powered on, goes to googles boot animation, then says "Android is starting... optimizing apps # of 127, and then once it reaches the end, it just goes into the animation again. I somehow have usb debugging disabled, and oem locked. I have no idea what i did to cause this, but esentially I unlocked the phone, and rooted it, and then i tried to disable encryption, and thats where things went south. clearing chache does not help, niether does factory reset. Attempts at flashing factory images are fails. even the guy at sprint cant do it. Besides fixing it, my only other option is to send it in to google and get a reaplacement...for $200. PLease help me solve this issue and i will be eternally grateful :3
SorryLols said:
Ok so, this is my first post on xda, and because my (sprint) Nexus 6 is stuck on a boot loop. When powered on, goes to googles boot animation, then says "Android is starting... optimizing apps # of 127, and then once it reaches the end, it just goes into the animation again. I somehow have usb debugging disabled, and oem locked. I have no idea what i did to cause this, but esentially I unlocked the phone, and rooted it, and then i tried to disable encryption, and thats where things went south. clearing chache does not help, niether does factory reset. Attempts at flashing factory images are fails. even the guy at sprint cant do it. Besides fixing it, my only other option is to send it in to google and get a reaplacement...for $200. PLease help me solve this issue and i will be eternally grateful :3
Click to expand...
Click to collapse
OK. So...do u know how to use fastboot? If yes...do a fastboot format data and fastboot format cache..also...do u have stock recovery or twrp?
I got that bootloop when I flashed a bad boot image. Easily fixed by flashing a good one...
But, let's clarify a couple of things:
Did you relock your bootloader while flashing?
Do you have a custom recovery (TWRP)?
If the answer to both of those are "yes", you might get out of this by using these commands:
fastboot format userdata
fastboot format cache
This will allow you to enter TWRP and restore a backup or flash a ROM.
If you didn't relock your bootloader you shouldn't have any problems flashing. Clarify what your trying to do, please (are you using a toolkit, etc).
If the answers are 1-yes and 2-no, then your probably SOL.
Didgeridoohan said:
I got that bootloop when I flashed a bad boot image. Easily fixed by flashing a good one...
But, let's clarify a couple of things:
Did you relock your bootloader while flashing?
Do you have a custom recovery (TWRP)?
If the answer to both of those are "yes", you might get out of this by using these commands:
fastboot format userdata
fastboot format cache
This will allow you to enter TWRP and restore a backup or flash a ROM.
If you didn't relock your bootloader you shouldn't have any problems flashing. Clarify what your trying to do, please (are you using a toolkit, etc).
If the answers are 1-yes and 2-no, then your probably SOL.
Click to expand...
Click to collapse
The answers are indeed 1-yes and 2-no. What is SOL an is there any way of fixing it?
SorryLols said:
The answers are indeed 1-yes and 2-no. What is SOL an is there any way of fixing it?
Click to expand...
Click to collapse
SOL = "S**t Out of Luck".
There is currently no know way of fixing it.
Your only avenue is to RMA it.
I got into problems yesterday. I've encrypted my device some months ago and it was working fine.
Last night I don't what happend but it switched off itself and once i tried to start it, I saw bootsreen, then lock screen and after inserting pin, nothing happens, I only see black screen with some light in the background.
Now Issue it, I have soo many important files on my device, is there any way to copy that data? Because i'm not able to access it via usb since my device is not able to reboot itself properly after lockscreen..
I will appreciate any help, and will give reward once i'll get my data back.
Thank you.
Ps: I'm using 5.0.2 (XT1068)
Pss: I tried to wipe cache but it didn't helped.
No one?
I'm able to boot into fastboot and adb also but in ADB my device is listed as unauthorized device and i'm not able to see confirmation dialogue on device screen :/
transp0rt3r said:
I got into problems yesterday. I've encrypted my device some months ago and it was working fine.
Last night I don't what happend but it switched off itself and once i tried to start it, I saw bootsreen, then lock screen and after inserting pin, nothing happens, I only see black screen with some light in the background.
Now Issue it, I have soo many important files on my device, is there any way to copy that data? Because i'm not able to access it via usb since my device is not able to reboot itself properly after lockscreen..
I will appreciate any help, and will give reward once i'll get my data back.
Thank you.
Ps: I'm using 5.0.2 (XT1068)
Pss: I tried to wipe cache but it didn't helped.
Click to expand...
Click to collapse
If you have unlocked bootloader then TWRP should be able to mount /data so you could copy it to your pc using adb.
LuK1337 said:
If you have unlocked bootloader then TWRP should be able to mount /data so you could copy it to your pc using adb.
Click to expand...
Click to collapse
Sadly it's not, I'm gonna take to nearest service center tomorrow, if they are unable to do it, i guess try this TWRP method.
If you have any other idea, let me know.
Thanks
transp0rt3r said:
Sadly it's not, I'm gonna take to nearest service center tomorrow, if they are unable to do it, i guess try this TWRP method.
If you have any other idea, let me know.
Thanks
Click to expand...
Click to collapse
Flashing TWRP will require bootloader unlock which wipes your data.
You can boot in twrp without install
Fastboot boot twrp-2.xxxx.img
Then you can use adb to pull files.
reddevilx said:
You can boot in twrp without install
Fastboot boot twrp-2.xxxx.img
Then you can use adb to pull files.
Click to expand...
Click to collapse
It will require unlocked bootloader (unlocking = wipe data)
LuK1337 said:
It will require unlocked bootloader (unlocking = wipe data)
Click to expand...
Click to collapse
Yeah right, sadly I had to wipe my all data. :/
Still thanks for the advice.
Hi Guys.
So recently I posted about resetting nexus 6 to factory default so I can send it off for a warranty repair.
In the mean time. I've dropped it about 20 times.
The glass is cracked and the screen is broken too.
I want to back everything up before sending the device off for a repair but there's a problem.
The device has a pin at boot and I can't get in because the digitizer is dead.
Whenever I try to use adb it just says "offline".
Is there any way I can get around this and make a backup??
please help thanks
can i dirty flash something from bootloader? i don't care if it breaks all the apps because I just want to boot the device and pull /sdcard/ via adb. Any help pleeeeeeeeaaaaase
joncy92 said:
can i dirty flash something from bootloader? i don't care if it breaks all the apps because I just want to boot the device and pull /sdcard/ via adb. Any help pleeeeeeeeaaaaase
Click to expand...
Click to collapse
first off, question and need for help gets posted in the q&a/help section, ill ask a mod to move your thread there. and secondly, you can flash the factory img via fastboot, via your bootloader
Use an otg cable and mouse to punch in the pin? Or will that not work that early in the boot process?
btw, you can boot into the recovery and use adb.
thanks for replies. I can't get into recovery it asks for a password. When I try to access the device through ADB it says "device offline"
If I flash factory through bootloader will it wipe all the pictures n stuff?
joncy92 said:
thanks for replies. I can't get into recovery it asks for a password. When I try to access the device through ADB it says "device offline"
If I flash factory through bootloader will it wipe all the pictures n stuff?
Click to expand...
Click to collapse
if you unlock the bootloader, it will. if its already unlocked, you can flash a certain way, to keep your data.
simms22 said:
if you unlock the bootloader, it will. if its already unlocked, you can flash a certain way, to keep your data.
Click to expand...
Click to collapse
hi thanks.
Bootloader is unlocked and device running chroma rom and twrp recovery. i think forced encryption is on but I didn't decrypt the device.
Please advise how to flash and keep data. If I reflash will the pin disappear so i can backup??
joncy92 said:
hi thanks.
Bootloader is unlocked and device running chroma rom and twrp recovery. i think forced encryption is on but I didn't decrypt the device.
Please advise how to flash and keep data. If I reflash will the pin disappear so i can backup??
Click to expand...
Click to collapse
itll probably ask you for your code again. and if you could get into recovery, you could make a nandroid backup of your rom, then restore it onto another n6 later. anyways, i *think* you just avoid flashing the userdata.img, but i could be wrong. see if you can google it.
simms22 said:
itll probably ask you for your code again. and if you could get into recovery, you could make a nandroid backup of your rom, then restore it onto another n6 later. anyways, i *think* you just avoid flashing the userdata.img, but i could be wrong. see if you can google it.
Click to expand...
Click to collapse
how will I get into recovery after flashing? Won't it still be asking for a password?
joncy92 said:
how will I get into recovery after flashing? Won't it still be asking for a password?
Click to expand...
Click to collapse
you will have a stock recovery after flashing the factory.img, youd have to flash twrp again, via fastboot via your bootloader. if you will still have that issue, i dont know.
joncy92 said:
Hi Guys.
So recently I posted about resetting nexus 6 to factory default so I can send it off for a warranty repair.
In the mean time. I've dropped it about 20 times.
The glass is cracked and the screen is broken too.
Click to expand...
Click to collapse
How could this be a warranty repair?
Hi,
Well as I said I'd dropped in after logging a warranty repair with Motorola. The problem was with the volume rocker getting stuck when I pressed the up or down buttons.
I was just giving some background
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
claytonjn said:
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you lock the bootloader just to be clear?
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
gee2012 said:
Did you lock the bootloader just to be clear?
Click to expand...
Click to collapse
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
simms22 said:
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
Click to expand...
Click to collapse
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
have you tried fastboot oem unlock again ?
uicnren said:
have you tried fastboot oem unlock again ?
Click to expand...
Click to collapse
Yes, it says it needs to be enabled in developer options
Sent from my Developer Edition Galaxy S5 using Tapatalk
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
uicnren said:
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
Click to expand...
Click to collapse
It says it will reboot in 5 seconds, but after 5 seconds the screen just goes blank. It appears the device is off, but maybe not.
Do you know what adb commands I would need to use to recover from this state?
Sent from my Developer Edition Galaxy S5 using Tapatalk
claytonjn said:
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
Click to expand...
Click to collapse
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
simms22 said:
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
Click to expand...
Click to collapse
Unfortunately that is not working for me (Not allowed in locked state!)
uicnren said:
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
Click to expand...
Click to collapse
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
claytonjn said:
Unfortunately that is not working for me (Not allowed in locked state!)
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Click to expand...
Click to collapse
If you have TWRP, boot to bootloader and use the following fastboot commands:
fastboot format userdata
fastboot format cache
Then boot to TWRP, connect to PC. Download a ROM to your PC and drag and drop in the root of internal storage. Then flash the ROM from TWRP, boot up, enable OEM unlock. Then boot back to bootloader and:
fastboot oem unlock
You should be good after that.
holeindalip said:
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
Click to expand...
Click to collapse
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
claytonjn said:
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
Click to expand...
Click to collapse
Follow my instructions listed above.
Evolution_Tech said:
Follow my instructions listed above.
Click to expand...
Click to collapse
II'm attempting that now.but fastboot format userdata and fastboot format cache fail. after booting into twrp the Nexus shows up in My Computer, but internal storage does not. I can push a ROM zip to the device with adb, but haven't figured out how to flash it yet because touch doesn't work...
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
claytonjn said:
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
Click to expand...
Click to collapse
glad you got it back, persistence pays off.
Lesson learned today? QUIT RE-LOCKING YOUR BOOTLOADER!
You can lock boot loader, you just have to make sure your phone boots first before locking it