[Q] Extracting /data/media from a powered off nexus 4 : Any pointers? - Nexus 4 Q&A, Help & Troubleshooting

Hello all,
After a 2 day search on XDA and other forums, i decided to post a question (hopefully not a repeated one).
Hopefully the answer may be as simple as "NO", but would appreciate any help/guidance
1. I am using a unrooted nexus 4 with 4.4.3 update in place. Locked bootloader.
2. The phone died due to battery drain. Upon charging it, the phone boots up but gets stuck at merging circles and doesnt go beyond.
3. Unfortunately, I do not have a complete backup of my pictures (dont know why i stopped taking a backup after a while).
4. Now, the phone do gets into recovery mode etc and i tried wiping the cache, but no luck.
5. The best I could do till now is to have adb installed on my PC. The device does gets detected in adb sideload mode alone.
Is there any way I could take a backup of my /data/media before i try rooting it or do a hard reset?
I tried using adb backup, but all i see as status of the phone as adb sideload (since I am in recovery and tried to use apply update using adb).. hence cant use adb backup -shared ! Any ideas to this data out from the powered OFF phone ?
Thanks for any response in advance.
Regards,
Varun

You have a custom recovery, correct? Have you tried flashing your ROM?

ph37rd said:
You have a custom recovery, correct? Have you tried flashing your ROM?
Click to expand...
Click to collapse
I dont think so. I did not make any changes to the ROM (planning to do until now).
Also, it is not a custom recovery but just the recovery mode (from the OEM), that I get with only 4 options :
1. Reboot
2. Use adb to update
3. Wipe data/reset
4. Wipe cache

bluevaruns said:
I dont think so. I did not make any changes to the ROM (planning to do until now).
Also, it is not a custom recovery but just the recovery mode (from the OEM), that I get with only 4 options :
1. Reboot
2. Use adb to update
3. Wipe data/reset
4. Wipe cache
Click to expand...
Click to collapse
if only I could get into adb mode from adb sideload, i guess i can do a backup -shared ....but not sure how to do that without unlocking boot loader (leading to data loss).
As i recently learned, this is a stock recovery I am into...
Thanks !!

If you're on the stock recovery I'm afraid you're not going to be able to use adb to pull any files.
Sent from my Nexus 5 using XDA Free mobile app

You can't do anything as your bootloader is locked.

Related

Cant boot phone just stays at "Google boot screen

i stupidly changed from CWM recovery to TWRP and forgot to make a backup.
I went to install the Revolt rom so copied it to the memory and it installs fine but when i go to reboot it just sits on the "Google" boot screen with the unlocked padlock at the bottom and never gets anywhere.
Any ideas or advice on what i can do?
Does adb work?
Wipe cache?
If you would have read through the thread, you would have seen that the ROM doesn't boot past the Google logo. The ROM doesn't work.
Sent from my Nexus 4 using xda premium
But how can I get another ROM.zip onto the device since I can't get onto it (I can access TWRP) but how can I get the zip onto it?
nexus toolkit doesn't pick it up so no ADB. My other nexus gets picked up fine
Sent from my Nexus 4 using xda premium
Roshi69 said:
But how can I get another ROM.zip onto the device since I can't get onto it (I can access TWRP) but how can I get the zip onto it?
nexus toolkit doesn't pick it up so no ADB. My other nexus gets picked up fine
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Try configuring the drivers from here. Can you mount USB Storage? Does your computer recognize fastboot?
It picks up my other nexus that is working fine but with being stuck in a boot loop i dunno what to do. with my s3 i would have just put a new rom on the external SD
just got it into download mode :s and 2 new random devices have appeared. check the links below.
all i want to be able to do it put a new .zip on the device so i can get it going.
https://www.dropbox.com/s/jux2lvkn63fjq2q/IMG_20130118_181401.jpg
https://www.dropbox.com/s/nk7rozieurd7ofg/IMG_20130118_181407.jpg
Roshi69 said:
It picks up my other nexus that is working fine but with being stuck in a boot loop i dunno what to do. with my s3 i would have just put a new rom on the external SD
just got it into download mode :s and 2 new random devices have appeared. check the links below.
all i want to be able to do it put a new .zip on the device so i can get it going.
https://www.dropbox.com/s/jux2lvkn63fjq2q/IMG_20130118_181401.jpg
https://www.dropbox.com/s/nk7rozieurd7ofg/IMG_20130118_181407.jpg
Click to expand...
Click to collapse
Can you get into fastboot?
possibly. what commands do i have to try? i know fastboot did work for my last device so its configured and working ok
Roshi69 said:
i stupidly changed from CWM recovery to TWRP and forgot to make a backup.
I went to install the Revolt rom so copied it to the memory and it installs fine but when i go to reboot it just sits on the "Google" boot screen with the unlocked padlock at the bottom and never gets anywhere.
Any ideas or advice on what i can do?
Click to expand...
Click to collapse
This happened to me 2 times yesterday. I was flashing new kernel and roms and then I keep getting the Google logo for every new rom I tried. I fixed this problem by doing these steps..
I'm using TWRP so ..
-Wipe
-Cache / Dalvik cache / factory reset / system / format data / and internal storage (Make sure u wipe internal storage and format data! This will stop the Google logo loop. NOTE: U will lost everything if you do this step)
-Then I reboot into TWRP after the wipe
-I download nexus 4 toolkit v1.3 Toolkit dl link
-mount /system/ in TWRP
-Put the below stock rooted rom into put_files_to_push_here (it's inside installed path of the nexus 4 toolkit)
-Push This stock rooted rom using #13 option in nexus 4 toolkit
-It will ask if u using a custom rom or insecure image type yes
-It will ask u where to push ur file to.. just type /system/
-wait 2-3 mins to push. If everything goes well it should say "Finished xxx secs"
-Install the Stock rooted rom using TWRP
-reboot
Roshi69 said:
possibly. what commands do i have to try? i know fastboot did work for my last device so its configured and working ok
Click to expand...
Click to collapse
I think I was wrong. You can't push/flash a ROM through fastboot. Are you absolutely sure that you can't mount your SD card to your PC in TWRP recovery? I can't mount my SD using CWM but I can using TWRP.
enyceckk said:
This happened to me 2 times yesterday. I was flashing new kernel and roms and then I keep getting the Google logo for every new rom I tried. I fixed this problem by doing these steps..
I'm using TWRP so ..
-Wipe
-Cache / Dalvik cache / factory reset / system / format data / and internal storage (Make sure u wipe internal storage and format data! This will stop the Google logo loop. NOTE: U will lost everything if you do this step)
-Then I reboot into TWRP after the wipe
-I download nexus 4 toolkit v1.3 Toolkit dl link
-mount /system/ in TWRP
-Put the below stock rooted rom into put_files_to_push_here (it's inside installed path of the nexus 4 toolkit)
-Push This stock rooted rom using #13 option in nexus 4 toolkit
-It will ask if u using a custom rom or insecure image type yes
-wait 2-3 mins to push. If everything goes well it should say "Finished xxx secs"
-Install the Stock rooted rom using TWRP
-reboot
Click to expand...
Click to collapse
got it all sorted and going. when trying to push to device i get "error: device not found" what way should i connect the phone? whilst in recovery and i've checked "mount system"?
Thanks so much for the help guys much appreciated!
Roshi69 said:
got it all sorted and going. when trying to push to device i get "error: device not found" what way should i connect the phone? whilst in recovery and i've checked "mount system"?
Thanks so much for the help guys much appreciated!
Click to expand...
Click to collapse
Do u have adb driver installed on ur pc? If you do, it should show ur device near top left of toolkit. It should say " ADB mode List of devices attached" If you can see ur device with the serial number then everything should work fine.
You can install the driver using toolkit.. it's the #1 option
When pushing the file, u should be in TWRP (where u see install.. wipe etc..) and mount /system/ should have an X on it.
enyceckk said:
do u have adb driver installed on ur pc? If you do, it should show ur device near top left of toolkit. It should say " adb mode list of devices attached" if you can see ur device with the serial number then everything should work fine.
You can install the driver using toolkit.. It's the #1 option
when pushing the file, u should be in twrp (where u see install.. Wipe etc..) and mount /system/ should have an x on it.
Click to expand...
Click to collapse
it worked!!! Thank you so much!!!

[Q] All methods of factory/hard reset seem to work, but then boots into old system

I'm having the weirdest problem and I'm wondering whether it is hardware or software. I have searched everywhere and only found one person with a similar situation and he had already sent it back for repair before anyone responded with things for him to try.
My 16gb Nexus 7 is rooted/unlocked using the Nexus Root Toolkit and at the latest OTA version. It had been working fine for months. Suddenly one day I had serious problems (which I can discuss if anyone cares, but I don't think the original problems are relevant at this point.) I gave up troubleshooting and decided to do a factory reset. But no matter what method I do, the next time I boot the device it comes back into my same buggy system and nothing was wiped or reset at all. All of these methods appear to work and give the normal messages you would expect, but then nothing changed. It's like the Flash ram is somehow set to read-only so attempts to write to it are failing.
What I have tried:
Settings Factory Data Reset and press the Erase Everything button. The tablet pauses a while, then shuts down and reboots. The old system comes back.
I go into recovery mode, choose function wipe data/factory reset, scroll down to Yes to confirm it. A bunch of progress messages show on the screen that the partitions are being formatted. I boot afterwards and the old system comes back.
I follow all the steps in articles like this: http://forum.xda-developers.com/showthread.php?t=1907796
Every fastboot command completes normally with progress messages showing that it worked. I reboot and the old system comes back.
Here is another clue: The fastboot oem lock command completes normally, but nothing changes. The padlock icon at the next boot is still open.
That's why I say that the tablet is acting as though the Flash memory is set to read-only somehow because nothing ever changes. Is it possible that this is a hardware problem, or is there something else I can do in software?
Bump One for OP
hope your problem gets solved...
I go into recovery mode, choose function wipe data/factory reset, scroll down to Yes to confirm it. A bunch of progress messages show on the screen that the partitions are being formatted. I boot afterwards and the old system comes back.
Click to expand...
Click to collapse
1. If you wipe this way and then do not install another rom, then the old system will just reload.
2. Which recovery are you using TWRP or CWM? Maybe try an alternative recovery?
3. Go into recovery/mounts and storage/ then select format system and then install another rom such as stock and see what happens..
killall said:
1. If you wipe this way and then do not install another rom, then the old system will just reload.
2. Which recovery are you using TWRP or CWM? Maybe try an alternative recovery?
3. Go into recovery/mounts and storage/ then select format system and then install another rom such as stock and see what happens..
Click to expand...
Click to collapse
1. I guess my wording was ambiguous. When I said that the old system comes back, I didn't mean only that the old OS comes back, but that EVERYTHING comes back immediately including all my apps, settings, wallpaper, widgets, everything looks like it always did. I don't get the first-time screens inviting me to log in, or anything like that. The system boots completely normally as though I hadn't used those methods of wiping the user data.
Also one of the things I tried was loading a new system using fastboot commands and the new system seemed to get loaded OK. But I reboot and the buggy system is back and my user data has not been wiped.
2. I'm not sure what you mean and will research that later this evening. For now, I can tell you that I used the Nexus Root Toolkit and I am using whatever it installed.
3. I'm not sure what you mean, but will research that and if I can figure it out, I will try it this evening.
Is it a clue that the command "fastboot oem lock" seems to work, but the lock status doesn't change?
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Try looking for a rooted stock rom in a zip file like this one and put it on your sd card. When you have entered recovery and wiped data/factory reset, then select install from sd card, find the zip and select. The recovery will then flash it and when you reboot, you should be at the setup pages.
Using the Nexus toolkit and ADB is challenging at the best of times. Maybe it is easier if you just use the recovery method as explained above.
killall said:
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Try looking for a rooted stock rom in a zip file like this one and put it on your sd card. When you have entered recovery and wiped data/factory reset, then select install from sd card, find the zip and select. The recovery will then flash it and when you reboot, you should be at the setup pages.
Using the Nexus toolkit and ADB is challenging at the best of times. Maybe it is easier if you just use the recovery method as explained above.
Click to expand...
Click to collapse
When I go into the recovery mode at boot time, the menu says I am using "Android system recovery <3e>"
According to all documentation I have seen, erasing the user partition is all I should need to do to wipe out all of my data, and this works perfectly on a different tablet that I have. I really shouldn't need to do anything else, which is why my situation is so strange.
The Nexus 7 doesn't have an SD card slot so I can't do the things you are saying that involve installing things from sd. Maybe there is a way to do the same thing via the portion of Flash that simulates an sd card, but the recovery menus don't have any way to do that, at least not that I can find.
I saw that you are rooted then I assumed you were using a custom recovery like Clockworkmod or TWRP.
When I wrote SD I meant the internal storage, sorry for the confusion.
I would be flashing a recovery again, it seems to be causing the problem. You can do this through Nexus tools.
killall said:
I saw that you are rooted then I assumed you were using a custom recovery like Clockworkmod or TWRP.
When I wrote SD I meant the internal storage, sorry for the confusion.
I would be flashing a recovery again, it seems to be causing the problem. You can do this through Nexus tools.
Click to expand...
Click to collapse
When you say to use "Nexus tools", do you mean the the tools that are part of the Nexus Root Toolkit? I did use those tools to format and rebuild the recovery partition, and it didn't help at all.
If you mean tools that I need to install as apps within Android, that isn't possible at the moment because the tablet is so unstable that when I reboot, I get all my old stuff for a few seconds so I know nothing changed, and then it reboots before I have a chance to do anything.
If you mean that I should mount the Android flash ram as a folder on my PC, I only seem to be able to do that for the few seconds that the system is booted and then the folder drops off. The only mode where I can keep the tablet powered on and stable is the boot menu and the recovery menu. Is there a way to mount the drive at that time?
Phonetrips said:
When you say to use "Nexus tools", do you mean the the tools that are part of the Nexus Root Toolkit? I did use those tools to format and rebuild the recovery partition, and it didn't help at all.
If you mean tools that I need to install as apps within Android, that isn't possible at the moment because the tablet is so unstable that when I reboot, I get all my old stuff for a few seconds so I know nothing changed, and then it reboots before I have a chance to do anything.
If you mean that I should mount the Android flash ram as a folder on my PC, I only seem to be able to do that for the few seconds that the system is booted and then the folder drops off. The only mode where I can keep the tablet powered on and stable is the boot menu and the recovery menu. Is there a way to mount the drive at that time?
Click to expand...
Click to collapse
Fast boot a custom recovery. Fastboot recovery c:/path/recovery.IMG
Path being whatever path you have to the recovery you chose to download. Then wipe data/factory reset, maybe wipe cache and dalvik since you're there. Then reboot, see what happens. Still buggy, download another ROM, there are stock-ish ones out there, or you can choose cm or AOKP
Sent from my Nexus 7 using xda app-developers app
VonEsch said:
Fast boot a custom recovery. Fastboot recovery c:/path/recovery.IMG
Path being whatever path you have to the recovery you chose to download. Then wipe data/factory reset, maybe wipe cache and dalvik since you're there. Then reboot, see what happens. Still buggy, download another ROM, there are stock-ish ones out there, or you can choose cm or AOKP
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iv'e done all that and nothing changes whatsoever. The problem isn't that I have a buggy Android system, but rather that all commands to format and erase that system are ignored.
Actually I was wrong, I never did load a recovery image like you said, although I did at one point use one that the Nexus Root Toolkit installed.
So I found a recovery image, downloaded it, and did this:
fastboot flash recovery openrecovery-twrp-2.3.3.0-grouper.img
But nothing changes, partly because maybe I don't know what to do with this thing that I just loaded. If I use the menu to go into recovery mode, I get the normal recovery menu I have always gotten.
Phonetrips said:
Actually I was wrong, I never did load a recovery image like you said, although I did at one point use one that the Nexus Root Toolkit installed.
So I found a recovery image, downloaded it, and did this:
fastboot flash recovery openrecovery-twrp-2.3.3.0-grouper.img
But nothing changes, partly because maybe I don't know what to do with this thing that I just loaded. If I use the menu to go into recovery mode, I get the normal recovery menu I have always gotten.
Click to expand...
Click to collapse
Flash the cwm one, maybe that will work?
Sent from my Galaxy Nexus using xda app-developers app
Phonetrips said:
Iv'e done all that and nothing changes whatsoever. The problem isn't that I have a buggy Android system, but rather that all commands to format and erase that system are ignored.
Click to expand...
Click to collapse
VonEsch said:
Flash the cwm one, maybe that will work?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Before I try a different one, can you please tell me what is supposed to happen after I give that fastboot command to flash the recovery image, Should the tablet go into that recovery manager immediately, or do I need to do something first to make it show up?
I went ahead and found/downloaded the cwm one. The same thing happened: I don't see it running and if I go into recovery mode I get the normal recovery, not this one.
killall said:
What I am trying to say (very badly) is the system on your phone will hold all your settings along with the OS. When you factory reset/wipe data, it will clear everything out....but, if you then reboot the phone, it will have to reload the old OS as it has nothing to load otherwise. This will include all your previous apps and settings.
When you have wiped all your data, you need to install another 'system/rom' to allow the phone to boot it. Or as I said, it will just reboot the old one.
Click to expand...
Click to collapse
Sorry, but this is completely wrong. When you do a factory reset, it wipes /data and /cache, which doesn't affect the OS at all because the OS resides on the /system partition. When you do a factory reset and reboot, you will run into the initial setup screen for whatever ROM you have installed. No user data/apps will be present.
Phonetrips said:
Before I try a different one, can you please tell me what is supposed to happen after I give that fastboot command to flash the recovery image, Should the tablet go into that recovery manager immediately, or do I need to do something first to make it show up?
I went ahead and found/downloaded the cwm one. The same thing happened: I don't see it running and if I go into recovery mode I get the normal recovery, not this one.
Click to expand...
Click to collapse
This seems really screwy. I'd say either your device is defective, or... Well I don't really know what else it could be. The fact that fastboot commands fail is a good indicator that something is screwed up. Have you tried wiping things through fastboot? It may be worth a shot, just know how to flash a ROM through it when you're done. I'm talking "fastboot erase -----" where ---- is replaced by system, data, or whatever. Just DO NOT erase the bootloader. Boot, however, is fine.
If all of this fails, it would seem that the device memory is defective.
About your recovery question, it will only go into recovery when you tell it to either from bootloader or ADB. And stock Android will try to remove CWM, so first time you need to go to recovery straight from the bootloader and let it make itself permanent when it asks.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Sorry, but this is completely wrong. When you do a factory reset, it wipes /data and /cache, which doesn't affect the OS at all because the OS resides on the /system partition. When you do a factory reset and reboot, you will run into the initial setup screen for whatever ROM you have installed. No user data/apps will be present.
Yes, this is what is supposed to happen, but on my machine when I do all those things, there is absolutely no change and the system continues to boot exactly as it was.
This seems really screwy. I'd say either your device is defective, or... Well I don't really know what else it could be. The fact that fastboot commands fail is a good indicator that something is screwed up. Have you tried wiping things through fastboot? It may be worth a shot, just know how to flash a ROM through it when you're done. I'm talking "fastboot erase -----" where ---- is replaced by system, data, or whatever. Just DO NOT erase the bootloader. Boot, however, is fine.
If all of this fails, it would seem that the device memory is defective.
About your recovery question, it will only go into recovery when you tell it to either from bootloader or ADB. And stock Android will try to remove CWM, so first time you need to go to recovery straight from the bootloader and let it make itself permanent when it asks.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have used fastboot erase ---- and fastboot format --- for system and everything else. Whether or not I flash new code to those partitions, all of this is ignored and the system continues to boot as it always has, with all my stuff.
After flashing the alternate recovery images, absolutely nothing changes when I choose Recovery Mode from the fastboot menu.
I talked to Google Play support and they sending out a replacement one. They never asked whether I had ever unlocked or rooted it and I didn't volunteer anything, just told them the symptoms I am having. But I have to send the old one back after I receive the new one, and there is a chance they won't accept if for warranty service when they see it,
Phonetrips said:
I talked to Google Play support and they sending out a replacement one. They never asked whether I had ever unlocked or rooted it and I didn't volunteer anything, just told them the symptoms I am having. But I have to send the old one back after I receive the new one, and there is a chance they won't accept if for warranty service when they see it,
Click to expand...
Click to collapse
That is true, since you can't change anything, they will probably know you voided the warranty. The only thing you could do is brick it permanently by erasing the bootloader... Not sure if that would work/help.
Sent from my Nexus 7 using Tapatalk HD

Unable to load custom recovery

*UPDATE* Finally got it to work thank you sooo much!!!
Files Needed:
custom recovery
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.3.1-steelhead.img
CM 10.1
http://download.cyanogenmod.com/?device=steelhead&type=nightly (Latest CM Nightly Build)
gapps
http://goo.im/gapps/gapps-jb-20121212-signed.zip
1) Enable Debugging over USB (Using Nexus Q App)
2) adb reboot bootloader
3) fastboot oem unlock, confirmed unlock... Nexus Q wiped
4) Enabled USB again
5) adb push cm-10.1.0-RC4-steelhead.zip /sdcard/
6) adb reboot bootloader
7) fastboot boot recovery-clockwork-6.0.3.1-steelhead.img
When you say it never loaded, are you talking about on screen? My guess is that you need to do a factory reset, because I've randomly had to do the same when video output was simply broken for no apparent reason. Easiest way is to power cycle your Q and hold down on top of the ball until the fast red flashing gives way to the spinning blue. Then when it's done booting into the system, reboot it to your bootloader and proceed as you've outlined above, but honestly just go ahead and only boot into recovery. Wait to flash it until you're in CM. Make sure to wipe everything in CWM before you install CM. I would also highly recommend making frequent backups because I randomly lose video and have to factory reset and I think others do as well. And I still haven't figured out what causes it.
Hopefully this helps you out
Sent from my Nexus 4 using Tapatalk 2
Malnilion said:
When you say it never loaded, are you talking about on screen? My guess is that you need to do a factory reset, because I've randomly had to do the same when video output was simply broken for no apparent reason. Easiest way is to power cycle your Q and hold down on top of the ball until the fast red flashing gives way to the spinning blue. Then when it's done booting into the system, reboot it to your bootloader and proceed as you've outlined above, but honestly just go ahead and only boot into recovery. Wait to flash it until you're in CM. Make sure to wipe everything in CWM before you install CM. I would also highly recommend making frequent backups because I randomly lose video and have to factory reset and I think others do as well. And I still haven't figured out what causes it.
Hopefully this helps you out
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
what CWM file did you flash? recovery-clockwork-6.0.2.7-steelhead.img? or the one birdman provided? if its the one birdman provided can you uploaded it and send me a link?
The problem is when i do everything i outlined above and adb reboot recovery it reboots the nexus Q and the TV just stays black... custom recovery never loads or am i suppose to press/spin/punch something?
I wasn't able to flash custom recovery on my Nexus Q either, I had to do "fastboot boot recovery-clockwork-6.0.2.7-steelhead.img" like Ricardo mentioned in his post on G+ https://plus.google.com/115049428938715274412/posts/VDdpi6VTepC.
I think I'm on the version 6.0.3.1 that's available via Rom Manager. But yeah, don't try to flash recovery from fastboot. Just boot to it, flash CyanogenMod, wipe data, reboot system, and then set up recovery from within CM using Rom Manager.
Sent from my Nexus 4 using Tapatalk 2

[Q] Nexus 4 problems.

I'm having a big problem with my Nexus 4 here lately. I tried to root it about 2 days ago, and it did not work. So i downloaded TWRP and my computer read it the same as the Nexus 4 root toolkit by WugFresh. I opened TWRP and it asked me to flash or boot (it was on flash), and i think i clicked "Recovery" and it made my Nexus not boot up, it was just at the logo screen. Then i tried to flash TWRP to the bootloader and System and it flashed TWRP, now it won't go into android. It just takes me into the TWRP interface. In the TRWP interface there are 8 options( Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot). I pressed "Reboot" and i when press System, Recovery, or Bootloader it tells me that the is no OS installed, I've looked up how to install OS back via WugFresh's toolkit, but it's still not working (maybe because I'm on a old computer). So I'm kinda panicking, is there anyone i can call,or take my phone to, or can you guys help PLEASE!?!
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Okay, i'll try that right now..
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Yiddish said:
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Click to expand...
Click to collapse
Try install these drivers: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
chromium96 said:
Try install these drivers
Click to expand...
Click to collapse
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Yiddish said:
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Click to expand...
Click to collapse
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
chromium96 said:
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
Click to expand...
Click to collapse
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Yiddish said:
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Click to expand...
Click to collapse
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
Oh, i see. Okay here i go
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
Okay, it got past the Google screen, now it's been on the multicolored X for about 10 minutes+ not doing anything
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
How long will i be on the X loading screen??
Yiddish said:
How long will i be on the X loading screen??
Click to expand...
Click to collapse
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Thanks! I think it was just the ROM i chose. I just downloaded Slim Bean, this seems to be working( the startup screen looks cool ) I'm on the "Android is upgrading..." screen and it says "Starting apps." at the moment.
Okay, SlimBean took more than 10 minutes, so i factory reset and tried again, and it's still not booting up. ):
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Any ideas why it's still not working??
Yiddish said:
Any ideas why it's still not working??
Click to expand...
Click to collapse
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
BobWalker said:
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
Click to expand...
Click to collapse
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Yiddish said:
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Click to expand...
Click to collapse
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
BobWalker said:
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
Click to expand...
Click to collapse
Where do i get Gapps??

[Q] [Help]bricked

Guys My friend just bricked his nexus 4 because he did not do the adequeate research and now i'm posting here after searching almost all the help threads Because I don't have any choice left
He had 4.3 running on his nexus 4 with unlocked bootloader and CWM installed and I think a custom kernel
now he went ahead and tried installing the 4.4 OTA for it and it got stuck,Can't get past the Google Screen,i tried a wipe and restore of his old backup of 4.2.2 but that is without root and I don't know why but it was having some issues and could not be restored.
I downloaded his stock 4.4 cause that's what he wanted but the stock firmware flash process isn't going through as explained
1. 1st step I did was download the 4.4 from developers.google.com
2. Then I downloaded ADB, Fastboot and drivers from http://forum.xda-developers.com/showthread.php?t=2010312
3. then as said I extracted all the files and put them into one folder
4. ran adb from cmd and the daemon started working but under listed devices the phone wasn't there though it was connected in fastboot mode to computer at the time. Tried Fastboot devices command also but still nothing.
5. Redownloaded drivers from nexus4tool and tried, still won't detect device
6. So far I can enter fastboot mode and recovery mode, but am clueless what to do now as the adb fastboot won't detect the phone.
7. I myself have a Samsung note 2 so I have managed to keep that good but I really don't know much about nexus 4 so please help
8. Please give me the best course of action so I can have this phone off of my hands and back to my friend with good or solemn news
9. Thanking you'll in advance and sorry for having you'll read so much
First of all, this is not a brick. The problem is caused because you tried upgrading your android OTA in root condition.
Now,
Boot into recovery, wipe data/factory reset
Wipe cache partition
And now try restoring the backup again..
If this doesn't help, try flashing a custom rom..
Of none of them works u can go to the customer service and act dumb like u dont know what happened to ur pjone etc, so u jave a chance to get your phone replaced..
Hit thanks if i helped!!
Sent from my GT-I9082 using XDA Premium 4 mobile app
just flash them 4.2.2 factory images,re install cwm and restore backup.

Categories

Resources