Device bricked after factory reset? - Nexus 5 Q&A, Help & Troubleshooting

Hey everybody,
I have some serious trouble with my nexus 5. It started to be slow and some apps weren't working well. So I decided to reset to factory default. I had the OTA 4.4.2 installed and it was rooted (folowing the root thread here in the forum).
After the factory reset the phone rebooted and now it is stuck in the screen with the green android thing.
Can someone help please?
Thanks!

Got a picture?
Sent from my Nexus 5 using Tapatalk

Sounds like you wiped your OS. Adb push a ROM to your phone and you'll be fine
sent from my HAMMERHEAD neXus

CRIME INC. said:
Sounds like you wiped your OS. Adb push a ROM to your phone and you'll be fine
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
ya its not bricked u just need to side load the rom with adb and flash you should be able to get in to recovery by holding volume- and power but if not then youll have to flash with adb.
for future a brick is when a device does not turn on at all none responsive a paper weight

How did you perform factory reset? From settings? Or did you go into custom recovery and wipe something there?
If you used the settings option, I am curious to know why that erased your OS.
Do you have a nandroid backup of 4.4?

Related

[Q] [Help] Stock, unrooted, untouched 1920 Nexus S stuck in boot animation

Hi, completely lost with what to do so hoping you guys can help me out. I am relatively clueless (but hopefully able to follow direction).
Heres the story:
Bought a Nexus S second hand for Rogers here in Canada. Been working great for 3 months or so.
The phone, to my knowledge, has never been rooted in anyway, hacked, etc.
So I have had Go Launcher and its associated widgets installed for some time. No issues. About a week ago I got an update notification for 2.3.6 (I was previously on 2.3.4, and even though I checked it never did find 2.3.5)
Now I heard about issues with tethering, and since I never had the search pop up issue I kept ignoring this.
Well today, the Go Launcher got 'stuck' while I was switching orientation( horizontal to verticle) and once it got unstuck recevied a ton of force close notices. I decided to power it off. It got stuck in the power off animation. I pulled the battery.
Since then, it gets stuck in the boot animation (rainbow x?). I have pulled battery numerous times, one time it sat in the animation for 20 min or so, only to restart itself and do it again.
I went to fastboot, and rebooting that way does nothing. Also, I can't go to recovery, when I do it restarts, and then the Android pops up, but eventually I get an Exclamation mark and Android and need to pull battery.
I don't think I can hook it up to the pc because I don't think I enabled usb debugging.
What are my options, any help would be greatly appreciated!
You need to flash the clock work recovery to put a new rom, first install the usb drivers for the nexus and the using dos flash the clock work recovery
Sent from my Nexus S using XDA App
Sent from my Nexus S using XDA App
Is that possible even though I'm pretty sure usb debugging is not enabled?
Any idea what caused this?
Surely there is a way to reset?
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Follow up to step 7 in the nexusshacks how to root guide and goto recovery mode now, select mounts and thrmen mount usb storage and copy a downloaded rom like cyanogen mode and goto install from zip and fromsd sdcard to install and then advance>clear delvik cache and clear cache partition before installing the rom
Sent from my Nexus S using XDA App
brad2332 said:
OK so did the rooting procedure but stopped before actually hitting the rooting stage.
Any ideas what happened?
Could it have been Go Launcher? Or maybe enabling orientation switching caused it to freak out...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you don't tick the prevent force close, a month ago mine were stuck on home screen and keep forceclosing, all i do is just install another launcher press home screen and voila
The android ! Is the recovery. Stock recovery.
You can try a factory reset from in there.
Or do the entire unlock bootloader and root thing. Unlocking will wipe the phone anyways so just try a factory reset from recovery.
At the ! There is a button press that brings you to the options. I can't recall for sure what it is though. I think it is volume up and press power but I am not certain. If you can't figure it out on your own just look it up.
You probably corrupted your sdcard partition while pulling the battery while it was trying to unmount. If that's the case your sdcard is now bad and the only way to fix is to send it in to service.
Sent from my Nexus S 4G using xda premium
So just went ahead and rooted and now running cm7.
Unfortunately lost everything on the phone but had no choice. It was not possible to get into fastboot and use recovery. It hung at the exclamation mark.
Oh well. First time using CM7.... pretty good... mostly just seems to be stock android?
Sent from my Nexus S using XDA App
Again the exclamation mark IS the stock recovery.

[Q] Not enough free space/help please?

I recently upgraded my P920 to 4.0.4 using xbsall's port, then installed BadSoul's mod. Today I downgraded to GB again, following the guide because my phone had become so slow as to be unuseable. When I reached the android setup screen, my phone displayed the message "Not enough free space. Clean up your data and try again." Attempting to connect to a wifi network causes the same message to appear. There are 5.57GB free.
Because of this, I can't install apps from the market, and the same method of rooting that I've used before (megatron_windows) isn't working either.
I tried using CWM to restore my backup earlier, but after doing so I was unable to boot - the LG logo would appear for a couple of seconds, then the phone powered off again.
So...my question is, how can I get my phone restored to a useable state again, if that's even possible at this point?
Silly question bit... did you try factory reset?
Sent from my 3D phone.
lzzar said:
Silly question bit... did you try factory reset?
Sent from my 3D phone.
Click to expand...
Click to collapse
I hadn't actually...thanks for the suggestion. I just tried it and ...you are amazing, thank you -so- much. I hadn't even thought of that, too much stress. Factory reset worked
So...I guess there are no silly questions then
SabreMc said:
I hadn't actually...thanks for the suggestion. I just tried it and ...you are amazing, thank you -so- much. I hadn't even thought of that, too much stress. Factory reset worked
So...I guess there are no silly questions then
Click to expand...
Click to collapse
Haha sometimes it's just the simplest things we forget
Sent from my 3D phone.
lzzar said:
Haha sometimes it's just the simplest things we forget
Sent from my 3D phone.
Click to expand...
Click to collapse
not working even after factory reset. Still 0 mb free. any other suggestions.
cant root.
cant change recovery.
recovery just restarts itself.
cant boot into recovery by key pressing..any help plz desperate
anivesh said:
not working even after factory reset. Still 0 mb free. any other suggestions.
cant root.
cant change recovery.
recovery just restarts itself.
cant boot into recovery by key pressing..any help plz desperate
Click to expand...
Click to collapse
Try to flash recovery with fastboot
Code: fastboot flash recovery
Sent from my 3D phone.
lzzar said:
Try to flash recovery with fastboot
Code: fastboot flash recovery
Sent from my 3D phone.
Click to expand...
Click to collapse
can you guide me how to do it.
i am not familiar with that.
please
It's a cache overload.
You don't need to factory reset , just clear the cache it'll solve your problem.
Should you encounter this problem again , factory reset would erase your data and leave you with a lot of work to be done , erasing the cache is rather painless.
Cheers.

[Q] Total device failure: URGENT ASSISTANCE REQUIRED!

I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Not that its much help but if you are bricked like I was, it was quite easy to replace the main board with a used one from Ebay.
No chance you had NV Flash snapshots?
Good luck with it,
Feend
In all honesty it simply sounded at first to be a permissions issue for SystemUI.apk.
But if you can get to fastboot I would try Reformatting your system partition and flashing another ROM. Then factory reset your data partition.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
sbdags said:
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Click to expand...
Click to collapse
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
UndisputedGuy said:
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow. Thanks a lot for posting this information. I had no idea. Would using the factory reset within CWM or in the settings be dangerous?
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
So doing this completely hard bricks the device? meaning NO bootloader? It almost seems like the bootloader factory reset is touching the block that holds the recovery. Isnt there source code for this bootloader? Couldnt this be solved?
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow i am very glad i stumbled across this.. there should be a sticky about this or something!! Thanks for the very helpful post
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I have to agree, I'm REALLY glad I came across this. I'd noted that in a few of the "My tablet is bricked" threads that people had bricked after accidentally clicking something in the bootloader screen and had vowed not to touch anything in the original bootloader.
Thanks for the heads up on this.
sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Game over
sbdags said:
Game over
Click to expand...
Click to collapse
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
sbdags said:
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
Click to expand...
Click to collapse
That's a bummer for them but good to know nvflash can fix it. and f*** Asus for locking the jb boot loader to prevent nvflash... Maybe this is a stupid comment but I think they would sell more devices if they didn't do stuff like this... I know when I look into purchasing a device I come here first to make sure there is android development and unbricking procedures. ( I saw nvflash for tf300t and that's pretty much the reason I picked that tablet). Its a bummer that companies like Asus are much more concerned with making money by repairing bricked devices. (Although I do love Asus hardware. I own a tf300t and a nexus 7...its a love hate thing... Damn you Asus)
Sent from my Nexus 7 using xda app-developers app
D.MADROX said:
I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
Click to expand...
Click to collapse
I have worked with six or seven who used the wipe data on the bootloader; two recovered.
If you have any chance to recover you have to work at it. First apx mode is useless unless you previously flashed Nvflash.
We need adb, fastboot, or recovery working. Here is a thread for your use to get control of your tablet.
You mention rebooting into recovery. Stock, cwm, or twrp?
As you progress through this list the tablets have a way of evolving. This can happen even if you haven't gotten anything to function as you wish. That means you have to do them again; three times may be the charm.
I would like very much to know about your mention of recovery. Can you still get into recovery and which?
How about a current update before you begin using that link.

[Q] Imp:Phone wont start up.PLS HELP

Hi,
So i decided to install NOVA launcher and kept it as default launcher.
No when i wanted to go back to google launcher the system was getting crashed and some error like : "systemui" is not working was poping up.
Meanwhile i was getting notifications of whatsapp messenger and i could use it but when i was trying to exit the app , again the problem occured.
Thats when i decided to reboot the phone to my bad luck it is not going further after "FOUR CIRCLES(red,green,yellow and blue) which comes after google logo.
I had previously owned S2 and when i used nova launcher and tried to switch back ( aftr uninstalling nova) it automatically use to use google launcher.
Please help.
Thanks & Regards,
V
If it won't boot you may have to fastboot the factory image can you get into recovery and do you have a custom recovery If so try clearing cache in it
Sent from my SAMSUNG-SGH-I727
jd1639 said:
If it won't boot you may have to fastboot the factory image can you get into recovery and do you have a custom recovery If so try clearing cache in it
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I went into recovery and tried factory reset as well as wiping cache but it takes for ever.
So again , i just have powered off the phone and waiting for suggestions.
I guess i need to flash factory image ?
Thnks
V
vzuwOw said:
I went into recovery and tried factory reset as well as wiping cache but it takes for ever.
So again , i just have powered off the phone and waiting for suggestions.
I guess i need to flash factory image ?
Thnks
V
Click to expand...
Click to collapse
How long is forever? Give it a good 10 minutes, maybe longer
Sent from my SAMSUNG-SGH-I727
vzuwOw said:
Hi,
So i decided to install NOVA launcher and kept it as default launcher.
No when i wanted to go back to google launcher the system was getting crashed and some error like : "systemui" is not working was poping up.
Meanwhile i was getting notifications of whatsapp messenger and i could use it but when i was trying to exit the app , again the problem occured.
Thats when i decided to reboot the phone to my bad luck it is not going further after "FOUR CIRCLES(red,green,yellow and blue) which comes after google logo.
I had previously owned S2 and when i used nova launcher and tried to switch back ( aftr uninstalling nova) it automatically use to use google launcher.
Please help.
Thanks & Regards,
V
Click to expand...
Click to collapse
I need you to answer a few questions before anyone can help...
Do you have a custom recovery installed? (Eg. TWRP or CM?)
- If not, are you rooted?
- If you do, have u made a Backup through your custom recovery?
- If you're not rooted, do you have warranty?
- If you don't have warranty, how long have you had you're phone for, because Google provide warranty for a certain amount of time with your phone.
Basically, if you have a custom recovery installed or are not rooted with warranty, don't panic.
In not an advanced user but I know done stuff... And there's always a way!
Sent from my Nexus 5 using Tapatalk
jd1639 said:
How long is forever? Give it a good 10 minutes, maybe longer
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Gave good 10 + mins
Will try it one more time.I guess it should hardly take about 30 secs or so.
Oh, and also, see if you can fastboot by pressing the power button and volume down whilst booting up. If you can't, then try pressing power button + volume up + volume down whilst booting up.
Sent from my Nexus 5 using Tapatalk
zz
:good:
ProVickers said:
I need you to answer a few questions before anyone can help...
Do you have a custom recovery installed? (Eg. TWRP or CM?) - NO,2 month old phone , full stock.
- If not, are you rooted? NO
- If you do, have u made a Backup through your custom recovery? NO,I dont mind if my data is lost
- If you're not rooted, do you have warranty? YES,but now i stay in different country.so count it as NO
- If you don't have warranty, how long have you had you're phone for, because Google provide warranty for a certain amount of time with your phone. have been using since 2 months
Basically, if you have a custom recovery installed or are not rooted with warranty, don't panic.
In not an advanced user but I know done stuff... And there's always a way!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Answers in BOLD
ProVickers said:
Oh, and also, see if you can fastboot by pressing the power button and volume down whilst booting up. If you can't, then try pressing power button + volume up + volume down whilst booting up.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can do that , it is showing me options over there like recovery,poweroff,bootloader recovery,etc.
If factory reset doesn't work then you option is to flash the factory image. Have you unlocked the bootloader?
Edit, you'll want to review this. http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5
jd1639 said:
If factory reset doesn't work then you option is to flash the factory image. Have you unlocked the bootloader?
Sent from my Nexus 5
Click to expand...
Click to collapse
No,I hav'nt modded my phone.
Just tried using nova launcher and uinstalled so this prob.
PS: I this any how to do with google search.Because i had disabled it from settings.
vzuwOw said:
PS: I this any how to do with google search.Because i had disabled it from settings.
Click to expand...
Click to collapse
This is probably why it crashed. Your phone doesn't have a launcher to boot into. That's the reason it is boot looping. As mentioned earlier, you'll have to flash the factory image.
jd1639 said:
If factory reset doesn't work then you option is to flash the factory image. Have you unlocked the bootloader?
Edit, you'll want to review this. http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 5
Click to expand...
Click to collapse
UPDATE : i can go into fastboot by pressing power + volume down
There earlier when i clicked on recovery it showd me option for cache wipe and data factory reset but instead of that i see a red triangle which has a exclamation mark on a sleeping android logo.
I have nt unlocked the bootloader.
El Daddy said:
This is probably why it crashed. Your phone doesn't have a launcher to boot into. That's the reason it is boot looping. As mentioned earlier, you'll have to flash the factory image.
Click to expand...
Click to collapse
Yea, i feel the same. I forgot it was google launcher and its a nexus phone.
If it would have been some other trebuche launcher(like in samsung) , this problem would'nt have persisted.
vzuwOw said:
UPDATE : i can go into fastboot by pressing power + volume down
There earlier when i clicked on recovery it showd me option for cache wipe and data factory reset but instead of that i see a red triangle which has a exclamation mark on a sleeping android logo.
I have unlocked the bootloader.
Click to expand...
Click to collapse
That is the stock recovery. You can press both volume buttons at the same time, to show the recovery options.
Flashing the factory image is very easy. You put your phone in fastboot mode, plug it into your computer, and simple run the Flashall.bat (or .sh depending on your OS.)
Touchwiz Home in Samsung devices does not rely on google search. Our Nexus has a launcher that requires google search to run. Otherwise you can install AOSP launcher.
Beauenheim said:
That is the stock recovery. You can press both volume buttons at the same time, to show the recovery options.
Flashing the factory image is very easy. You put your phone in fastboot mode, plug it into your computer, and simple run the Flashall.bat (or .sh depending on your OS.)
Touchwiz Home in Samsung devices does not rely on google search. Our Nexus has a launcher that requires google search to run. Otherwise you can install AOSP launcher.
Click to expand...
Click to collapse
Done.
Phew
Thanks a lot everyone.
Sent from my Nexus 5 using Tapatalk
@jd1639
@Beauenheim
@ProVickers
@El Daddy
Thanks a lot all of you Cookies are in transit
Sent from my Nexus 5 using Tapatalk
vzuwOw said:
@jd1639
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5
Repeated Post.
vzuwOw said:
Repeated Post.
Click to expand...
Click to collapse
@vzuwOw if you run into this problem again just fastboot flash the system.img, not the flash-all.bat. it would have kept the rest of your settings and you wouldn't have to redo your while phone.
Sent from my Nexus 5

[Q] Help

I flashed an AOSP version of 5.0 lolipop. When this happened, I lost root. My bootloader is unlocked, but when i go to Recovery, i see the android with the text "no command" underneath. I no longer have CWM, google apps, or anything useful. What I want is to go to a factory stock. I dont care about root. If i have it, great, if not, oh well. Now in a normal world, i would plug phone into pc and go through the fastboot. But the data channel in my microUSB doesnt work. I can transfer files through airdroid? What can i do?
caseylitz said:
I flashed an AOSP version of 5.0 lolipop. When this happened, I lost root. My bootloader is unlocked, but when i go to Recovery, i see the android with the text "no command" underneath. I no longer have CWM, google apps, or anything useful. What I want is to go to a factory stock. I dont care about root. If i have it, great, if not, oh well. Now in a normal world, i would plug phone into pc and go through the fastboot. But the data channel in my microUSB doesnt work. I can transfer files through airdroid? What can i do?
Click to expand...
Click to collapse
What you have is the stock recovery, push power and vol up and release the keys after 1 second. Without a pc you're pretty much sol getting a custom recovery and root or flashing the factory image
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What you have is the stock recovery, push power and vol up and release the keys after 1 second. Without a pc you're pretty much sol getting a custom recovery and root or flashing the factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
so, what can i do with the stock recovery? Is there anything I can download to pc, then send over wifi to phone?

Categories

Resources