Damn I'm dumb, I thought I'd have a go at attempting to make it so the bottom buttons would be hidden as I use gestures anyway
I modified the .prop file as a tutorial recommended but now after the Google logo (unlocked bl) I just get a black screen
I can access recovery which gives me the options START, RESTART BOOTLOADER, RECOVERY MODE and POWER OFF.
I am going to guess I need to bring it back to stock somehow - how would I go about doing this?
Any help is appreciated, Thanks
Kevin
TRIED:
Relocking and unlocking the bootloader - was hoping it would format the phone but it appears it keeps the build.prop.
I can boot into clockworkmod recovery but I'm scared to flash it for the moment before I get some advice from you guys
[EDIT] I see that Fastboot detects it - so I guess I can flash stuff.
In an attempt to fix this I flashed the stock rom from Google that ATGAdmin pointed out. Here's what I did below
0. Download above recovery image, extract into a directory with fastboot
1. Hold down power for 10 seconds to power off
2. Hold down voldown and then power for a few seconds until recovery appears
3. Run flash-all.bat or flash-all.sh if on Linux.
4. Phone should reboot.
Now device is stuck on nexus X logo, attempting reflash... Same problem
Halp D:
why dont you do restore the build.prop to the original one and also do a wipe cache and wipe dalvik from CWM
My phone wasn't booting because of the broken build.prop and as such how was I supposed to restore it?
Now that I've flashed the stock rom I am now stuck at the nexus X logo, so I'm not sure what to do at this point, thanks for the help munchy_cool
kn100 said:
My phone wasn't booting because of the broken build.prop and as such how was I supposed to restore it?
Now that I've flashed the stock rom I am now stuck at the nexus X logo, so I'm not sure what to do at this point, thanks for the help munchy_cool
Click to expand...
Click to collapse
You could sell me your phone:fingers-crossed: lol.... Hope you fix it
if you still have recovery clear dalvik cache and cache.
if you do not have recovery search for fastboot commands to do so as I guess you can still go into fastboot mode.
Recovery still works fine and I can boot into clockwork mod etc, it all appears to be working fine, except I just noticed in clockwork mod it's not able to format SDCard whatsoever - if this helps at all - I haven't flashed clockworkmod just to keep my options open, I just boot to it.
Any suggestions, I've tried flashing the google stock rom twice now and it doesn't appear to work.
boot in CWM and do a wipe dalvik and wipe data+cache bro ....
Try using mskip toolkit to flash stock image just done the exact same thing and works a treat. Didn't have any faults myself was just tinkering with it. Hope it helps
Sent from my Nexus 4 using xda premium
Booted into CWM
Wipe data/factory reset:
Wiping data, Formatting /data, Error mounting Data!
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure!
Skipping format
Data wipe complete.
wipe cache partition
Formatting /cache
Cache wipe complete
Wipe Dalvik cache
**page just refreshes, assume it just wiped**
After reboot stock recovery is used and again I am stuck at the X.
go into mounts, mount the data partition manually and then do a factory reset.
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
kn100 said:
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
Click to expand...
Click to collapse
Glad you fixed it:good:
glad you can now enjoy it
kn100 said:
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
Click to expand...
Click to collapse
Awesome bit of kit. Glad you got it sorted pal
Sent from my Nexus 4 using xda premium
Congratulations, you have been the first to almost* break their N4. You have now began the famous tradition for this model , many shall follow, but we shall always know of your name first.
, glad it's fixed
Heheh I'm quite proud of that! Reminds me of the old Motorola modding days with P2K and P2K05, Any of you guys part of that back in the day?
For what it's worth, all that needed doing was flashing system via fastboot.
kn100 said:
Heheh I'm quite proud of that! Reminds me of the old Motorola modding days with P2K and P2K05, Any of you guys part of that back in the day?
Click to expand...
Click to collapse
Hahaaha I remember those days (hint-my avatar)
As a side note, you could have just followed the Galaxy Nexus guides for restoring to stock, but just replacing the system image files with those applicable to the Nexus 4.
Related
I am trying to change into CyanogenMod-5 for Nexus One.
I've unlocked the bootlader and installed Amon_RA's recovery image.
Also I copied the ROM to my sdcard and wiped before I tried to flash.
The trouble only appears when I have to reboot into recovery mode. When I press recovery the start up X sign appears but only to be followed by the little andriod man next to a !warning sign.
What am I doing wrong?
Radissen said:
I am trying to change into CyanogenMod-5 for Nexus One.
I've unlocked the bootlader and installed Amon_RA's recovery image.
Also I copied the ROM to my sdcard and wiped before I tried to flash.
The trouble only appears when I have to reboot into recovery mode. When I press recovery the start up X sign appears but only to be followed by the little andriod man next to a !warning sign.
What am I doing wrong?
Click to expand...
Click to collapse
Redownload and flash the recovery image.
Have tried a couple of times (well that was with the same download but is said "OKAY" every time).
Radissen said:
I am trying to change into CyanogenMod-5 for Nexus One.
I've unlocked the bootlader and installed Amon_RA's recovery image.
Also I copied the ROM to my sdcard and wiped before I tried to flash.
The trouble only appears when I have to reboot into recovery mode. When I press recovery the start up X sign appears but only to be followed by the little andriod man next to a !warning sign.
What am I doing wrong?
Click to expand...
Click to collapse
I think you have to hold down Volume up and power button or volume down and power button. One of these two should fix it for you.
When I do that i come to this screen
IT only says something like:
Reboot system now
apply update.zip
wipe data/factory reset
wipe cache partition
E:Can't open/cache/recovery/command
It's working EXACTLY like this for me...
Unfortunately it "should" work fine when using Fastboot, but won't work from Recovery directly via the bootload.
In other words... Try to do the "Fastboot boot recovery.img" and see if you have success... Mine works perfectly well when done this way. (Note: Use the proper file you have for the recovery image... I'm assuming you know how to properly run Fastboot?)
Radissen said:
When I do that i come to this screen
IT only says something like:
Reboot system now
apply update.zip
wipe data/factory reset
wipe cache partition
E:Can't open/cache/recovery/command
Click to expand...
Click to collapse
That looks like the original recovery, are you sure you installed the amon_ra recovery correctly??
Well I followed this guide
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Nexus_One_Firmware_to_CyanogenMod
and it did says OKAY on my PC. But I'm not really sure how it is supposed to look when it's been installed.
So I redownloaded everything a I got the phone rooted and had no problem installing the new ROM and addon. But now my Nexus one i stock doing this over and over again
Forgot to wipe berfore...
NOW IT WORKS PEFECT!
Thank you so much
Yep, make sure you make a nandroid backup. And whenever you have a bootloop its most likely that you forgot to wipe.
Cheers!
tontonHD said:
Yep, make sure you make a nandroid backup. And whenever you have a bootloop its most likely that you forgot to wipe.
Cheers!
Click to expand...
Click to collapse
S*** forgot to do a nandriod backup. Is that a problem?
Radissen said:
S*** forgot to do a nandriod backup. Is that a problem?
Click to expand...
Click to collapse
No, its not you can make a backup whenever you want. In my situation I did a backup of Cyanogen 5.0.2 with all my apps and settings and another one of MoDaCos Desire rom so it basically takes me 3 minutes to switch between roms
Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root.
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.Try a stable ROM like CM7 and see what happens. I didn't want to do too much damage so haven't tried this option yet.
2.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Edit: I just tried Newtrino rom and stuck @ Moto screen which says unlock.
Edit 3/4/2012: Please go to the last post for the solution. Tenfar's CWM is old and cannot deal with latest ROMs. Use ROMRACERS latest CWM or touch based Koush's CWM for future ROM flashing.
Old CWMs will give you sleepless nights!
Ok tried restore again after wiping data, cache & dalvik cache.
Now after reboot, My Moto Logo screen says unlock and just starts flashing.
I can still get into recovery......
can someone please help me......
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
vsg005 said:
What you can do is: install a "stable" ROM of Gingerbread:
--Go in recovery, put a .zip of the ROM on your sdcard (with your computer), and after wiping data, install it .zip.
--Or you install a new ROM with fastboot
Anyway, be careful with your battery, because if it is empty, with no ROM on your phone, it'll be crap!
Click to expand...
Click to collapse
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Masterguy said:
thank you for your response. However I tried that already Nutrino GB ROM. Again, I would go to 'M' screen which says unlocked and its stuck there for ever.
I used tenfar's CWM. Not sure if I need to use any other CWM. Also since my phone doesn't boot, I'm not sure how I can install any other CWM
Click to expand...
Click to collapse
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
littleemp said:
Don't worry, soft bricks are easy to recover on the Atrix thanks to us being able to access fastboot.
For flashing a new recovery:
While your phone is off, press Volume Up + Power to power up, then release when a menu appears on your screen and navigate with volume down until you see Fastboot, select it with the volume up key.
Get the necessary files for fastboot, place them all in a folder called "moto" in your C: drive, and type in the following in a cmd window (assuming you're using windows and that the recovery image is called recovery.img):
C:/Moto> fastboot flash recovery recovery.img
C:/Moto> fastboot -w
C:/Moto> fastboot reboot
Now access your recovery wipe dalvik cache, cache, factory reset and then flash a new ROM. It SHOULD boot without issues. I personally use Koush's Clockworkmod Touch, also remember that Neutrino tends to get "stuck" sometimes after the first attempt to boot and requires a battery pull and then you try to boot again. (It takes a while)
Click to expand...
Click to collapse
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
flash the latest recovery and wipe everything in recovery and flash neutrino again. It should work after that. try neutrino 2.2 though. 2.5 still has it's kinks.
1st off, relax. It's difficult to brick your phone from this point Just don't get any bright ideas with .sbfs lol.
As others have said, make sure you're on latest recovery.
Question: are you installing from internal or external SD? Internal is recommended for flashing most ROMs.
Sent from my MB860 using xda premium
Masterguy said:
Many people also seem to have suggested RACEROM CWM. Which one would you suggest? I'm so nervous about all this now. Just have this butterfly in my stomach
Click to expand...
Click to collapse
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Solved:boot loop issue
littleemp said:
As someone else said, the ONLY thing you should NEVER do is flash an .sbf or go through an OTA update, that's a surefire way to hard brick your phone. From this point on it's VERY DIFFICULT to completely brick your phone using software only.
RomRacer's CWM is based I think on v5.0.2.7? Koush's latest recovery is v5.8.1.5. I honestly couldn't name any tangible differences other than the touch interface, which is the reason I use it in the first place. (I hate mashing volume keys like a madman) It really doesn't matter which CWM you use, but when I soft bricked my phone I recovered with CWM Touch.
I would recharge your battery to 100% before trying to recover it, as that is one less headache to worry about, but if your phone starts saying 'Battery is too low to flash', do not panic, you only need a USB cable you don't mind sacrificing (doesn't have to be new). I will go into detail in case you actually need to do this.
Just make sure you use the fastboot -w command and wipe EVERYTHING through CWM before trying to flash anything else.
Click to expand...
Click to collapse
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Masterguy said:
Thanks I was able to fix my boot up issue using ROMRACERS CWM. I didn't use any command prompt or anything. I just downloaded zip file from this thread, entered recovery mode -->Install Zip from SD card --> Chose ROMRACERS zip --> it automatically flashed the recovery and I then rebooted recovery under advanced options.
After that Wiped data,cache & Dalvik Cache and proceeded to install CM9 and it booted up up flawlessly.
I'm kind of surprised that tenfar didn't add a not to use his CWM as the latest ROMs use latest ext format.
That seems to be issue. However, I'm pleased with your guidance and final output. Thanks a lot dude.
Click to expand...
Click to collapse
Thank you sooo much. I was having this exact problem. I did what you suggested and my phone works. Thanks!
Hello there, I just got my N10 32MB a few weeks ago and after playing with the stock rom for a bit decided to try some custom roms. I've tried CM10.1M3 and Paranoid and a couple others all with the same result. I flash them and they stay on the loading screen forever. I've used the Nexus 10 Toolkit donater version and I'm no stranger to dropping a custom rom on an android device I've been playing with them since the original Motorola Droid. I would have thought the N10 would have been cake to do this on but nothings is working. The ONLY rom it will take is the stock rom 4.22. I was able to successfully re-install it via adb after wiping all the roms off of the device. If anyone has any insight I would really appreciate it.
Go back in recovery, format /system, wipe data/factory reset, reflash ROM, gapps, reboot. Normal steps for flashing a ROM.
And you didn't use ADB to reflash stock images, but fastboot. Damn toolkits...
Sent from my Nexus
I'm no expert , but my first time I got the same result as you, what saved my bacon
Was that I done a backup first.
If I were to guess what my problem was
Maybe a corrupt donwload
And then make sure you do these steps
In recovery (cwm,tcwm)
Wipe -> Factory reset -> Cache and Davilk cache
Then go in
Install -> ROM -> Gapps
I take no responsibilities in case it bricks yours... but this as work for me.
Plus YouTube makes it really easy to do...if you need a videos tut's...
Sent from my Nexus 10 using xda app-developers app
Thanks for both the replies. Yes, I've done all this formatted system wiped both cache redownloaded the files tried sending them to the device from different PC's. You're right I didn't flash the rom via adb it was fastboot, I ened up having to sideload something via adb in tcwm maybe it was when I returned it to stock unrooted and relocked it to start all the way from square 1. I'm really at a loss I've let it sit at the boot screen for as long as 30 min and nothing starts up. It only seems to want to run stock 4.22.
ironhelix said:
I'm no expert , but my first time I got the same result as you, what saved my bacon
Was that I done a backup first.
If I were to guess what my problem was
Maybe a corrupt donwload
And then make sure you do these steps
In recovery (cwm,tcwm)
Wipe -> Factory reset -> Cache and Davilk cache
Then go in
Install -> ROM -> Gapps
I take no responsibilities in case it bricks yours... but this as work for me.
Plus YouTube makes it really easy to do...if you need a videos tut's...
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Make sure your boot loader is unlocked. I remember having this issue on my Skyrocket awhile back. It would hang on the custom ROM installs.
cowabunga said:
Make sure your boot loader is unlocked. I remember having this issue on my Skyrocket awhile back. It would hang on the custom ROM installs.
Click to expand...
Click to collapse
It is...I even relocked it and unlocked it again as well as unrooted and rooted again to make sure.
I am stock everything and bootloader unlocked, I flash the 4.3 update via adb, but now it doesn't boot into the os, it get's stuck on the 'Nexus' boot screen.
Can someone assist me, thanks! I don't want to wipe data or reflash the rom.
Same problem here. Searching the forum for a solution... :/
Deeco7 said:
I am stock everything and bootloader unlocked, I flash the 4.3 update via adb, but now it doesn't boot into the os, it get's stuck on the 'Nexus' boot screen.
Can someone assist me, thanks! I don't want to wipe data or reflash the rom.
Click to expand...
Click to collapse
Go into custom recovery and factory reset
From my BLACKED OUT N4
spaceman860 said:
Go into custom recovery and factory reset
From my BLACKED OUT N4
Click to expand...
Click to collapse
I don't think you read my first post. I don't want to wipe data and have no custom recovery installed.
Deeco7 said:
I don't think you read my first post. I don't want to wipe data and have no custom recovery installed.
Click to expand...
Click to collapse
Did you try wiping cache
From my BLACKED OUT N4
I actually have the same problem. I had root, but I wasn't using a custom recovery. The OTA appeared as available in the notifications so I chose to install it. I set it aside and it appeared to install, but when it went to boot up, it got stuck on the X animation. I left it there while I tried to research the issue, but after 20 minutes of looking at the X I tried doing a factory reset with the stock recovery. It said it succeeded, so I rebooted. I've now been looking at the X animation for 7 minutes.
naxir said:
I actually have the same problem. I had root, but I wasn't using a custom recovery. The OTA appeared as available in the notifications so I chose to install it. I set it aside and it appeared to install, but when it went to boot up, it got stuck on the X animation. I left it there while I tried to research the issue, but after 20 minutes of looking at the X I tried doing a factory reset with the stock recovery. It said it succeeded, so I rebooted. I've now been looking at the X animation for 7 minutes.
Click to expand...
Click to collapse
edit: ^^^ same here. Root, no custom recovery.
After the update mine was stuck on the loading screen for a while, maybe a half hour. Gave up on that, did a factory reset from the recovery menus, but it still won't start up.
Any suggestions?
spaceman860 said:
Did you try wiping cache
From my BLACKED OUT N4
Click to expand...
Click to collapse
Yes, same problem.
Try reflashing, maybe something went wrong during the flash.
Sent from my Nexus 4 using Tapatalk 4 Beta
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
andyabc said:
Try reflashing, maybe something went wrong during the flash.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried reflashing, still no go.
kzoodroid said:
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
Click to expand...
Click to collapse
Looks like a factory reset is the only viable option. What is the best way to back everything up, if I cannot boot into OS?
Folks,
After trying a lot of option, I did a full restore flashing the entire 4.3 new image.
Worked, but lost everything on the phone.
kzoodroid said:
You use the stock recovery to clear cache, format I think is what recovery says, if that doesn't work then you have to do a factory reset weather you want to or not. This worked for me.
This is from efrant's guide to flashing in general section:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this.
Click to expand...
Click to collapse
Deeco7 said:
Tried reflashing, still no go.
Looks like a factory reset is the only viable option. What is the best way to back everything up, if I cannot boot into OS?
Click to expand...
Click to collapse
You can backup data using adb, its a simple command to copy the internal storage but I'm not sure what the exact command is as I never had to use it.
I flashed 4.3 following efrant's guide, no dice. I tried erasing boot/recovery and formatting cache/system/userdata and then doing so again, no dice. I did a factory reset and then flashed using flash-all.sh, no dice. It hangs on X animation. I've been letting it go for 5+ minutes each time, should I be waiting longer? Is there something else I can try?
kzoodroid said:
You can backup data using adb, its a simple command to copy the internal storage but I'm not sure what the exact command is as I never had to use it.
Click to expand...
Click to collapse
Code:
adb backup-f boot boot.img
adb backup-f system system.img
adb backup-f data.img date
Would this be the commands?
kzoodroid said:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
My 'phone couldn't get past the X so I followed the above. Wiping the cache didn't work so I chose wipe data/factory reset, answered yes to delete all user data and the screen showed "Wiping data ... Formatting /data ... Data wipe complete". The menu then returns with reboot system now highlighted. What's supposed to happen next?
If I choose reboot system now, the 'phone just reboots to the bootloader. If I choose wipe data/factory reset, the data is wiped again and the menu returns again, same as before. If I do nothing, nothing happens, at least according to the screen. What am I missing?
I was able to use flash-all.sh in 4.2.2 and it booted fine. I tried the ota again and same issue. Some apps autoinstalled when I installed 4.2.2, so I guess I can re-flash 4.2.2, make sure no apps download, then try the OTA again, but I'm not sure what else I can try to get 4.3 to install.
Yeah I also had the same problem. Tried to apply OTA from rooted stock. I flashed 4.2.2 via fastboot without wiping user data and got it to start in 4.2.2 again. Backed up all the important files and app data with Titanium, factory reset and then flashed 4.3. Rooted and then restored all the app data. Had a small issue with the r/w permission on some of the folders that affected the Gallery app not being able to work properly but did a fix and it all works fine now.
Sent from my Nexus 4 using Tapatalk 4 Beta
Deeco7 said:
Code:
adb backup-f boot boot.img
adb backup-f system system.img
adb backup-f data.img date
Would this be the commands?
Click to expand...
Click to collapse
No that's not it. I saw a tutorial somewhere on how to backup the Nexus 4 using adb but I can't find it. Someone in here knows how to do it and/or there is already a thread on it.
it would be something like --- adb pull all storage/emulated/0 --- to get all your data off the sdcard but I'm not sure of the syntax I used plus you need to designate where to put the data you just pulled. I only looked at the how to once and very briefly as I didn't need to use it. I'm not sure how you backup user data but you would need to pull the image off the device.
I have most of my data backed up to either Google or in my Box account using Helium backup so I don't care about losing any doing a factory restore so I have no need to know how to do an adb backup.
---------- Post added at 09:24 PM ---------- Previous post was at 09:17 PM ----------
This isn't the guide I saw before but I think it will work. I cut out the relevant section from the article.
http://www.dotkam.com/2013/01/16/backup-and-reset-nexus-4-cracked-and-locked-screen/
One thing I knew I could do for sure is to backup the “sdcard”. I knew this because of two things: I have “USB Debugging” on, which means I can use adb, and “sdcard” is not owned by root, which means it can be “pulled”/”read” by adb. Hence the first step is clear:
./adb pull /sdcard/ /destination
At this point all the pictures / videos / music, etc.. are backed up. Now I need to backup my SMS, contacts, etc.. Information that lives in Android “databases”. For example contacts usually live here “/data/data/com.android.providers.contacts/databases”. Which can’t be simply “pulled” as pitures, since they are protected, and hence cannot be read by adb directly.
---------- Post added at 09:34 PM ---------- Previous post was at 09:24 PM ----------
I found this thread in the galaxy nexus forum and maybe it will work, it was using syntax similar to what you posted.
http://forum.xda-developers.com/showthread.php?t=1420351
So I have tried many things to flash 4.3, but none have worked. Flashing 4.2.2 works and it's how I recover from getting stuck on the nexus boot screen which happens whenever I flash 4.3.
I have tried:
Simple OTA. Performed when I had root and also from fresh 4.2.2 install.
Flash using fastboot and all .img files separately, wiping the cache afterwards.
Flash using flash-all.sh script included with the factory image.
I have tried doing the above wiping cache before/after and doing a factory reset before/after. The MD5 checksum of the .tgz is correct, so the file downloaded correctly. However, all roads lead to being stuck on the "X" animation during boot up. I always allow 5+ minutes for it to progress beyond, but it hasn't.
Hi,
I tried out ubuntu touch and wanted to revert to stock before flashing cm (because I havn't had a rom on my storage).
After flashing the stock image via fastboot (using that flash-all.sh included in official download) my nexus stucks at boot animation.
Then I flashed recovery (I tried both, CWM and TWRP) and tried to do a factory reset -> unable to mount internal storage, also the space of my internal storage was 0MB (obviously because it can't mount anything), so it exited with an error. Then I formatted just every partion in CWM and I was able to mount again, flashed stock image ... stuck at boot animation. Tried flashing cm via sideload... stuck at boot animation.
Google didn't helped me.
Does somebody know what to do now?
Thanks
Bagbag
After you flash the stock image boot into the stock recovery and do a factory reset. Should solve your problem
Sent from my Nexus 5
jd1639 said:
After you flash the stock image boot into the stock recovery and do a factory reset. Should solve your problem
Sent from my Nexus 5
Click to expand...
Click to collapse
Oh ye, i tried it, but if i try to enter it, there's just a droid with a red triangle.
bagbag said:
Oh ye, i tried it, but if i try to enter it, there's just a droid with a red triangle.
Click to expand...
Click to collapse
Hit vol up when you see that. It's normal
Sent from my Nexus 5
jd1639 said:
After you flash the stock image boot into the stock recovery and do a factory reset. Should solve your problem
Sent from my Nexus 5
Click to expand...
Click to collapse
you should only have to clear the cache...factory reset shouldn't be necessary. Remember if you do have to do a factory reset, it will wipe all your storage completely if you use stock recovery to do it. Don't forget to back everything up first!
hp420 said:
you should only have to clear the cache...factory reset shouldn't be necessary. Remember if you do have to do a factory reset, it will wipe all your storage completely if you use stock recovery to do it. Don't forget to back everything up first!
Click to expand...
Click to collapse
The OP just flashed the factory image, flash-all, do he doesn't need to worry about data any more, too late for that
Sent from my Nexus 5
jd1639 said:
Hit vol up when you see that.
Click to expand...
Click to collapse
Does not work, it just stays at the screen with dat red triangle. Also vol up + power at same and other things I found in google don't work.
I already made backups, but anyway, they wouldn't help me in any way, if I don't have a working phone..
bagbag said:
Does not work, it just stays at the screen with dat red triangle. Also vol up + power at same and other things I found in google don't work.
I already made backups, but anyway, they wouldn't help me in any way, if I don't have a working phone..
Click to expand...
Click to collapse
Boot into fastboot mode. Then from your pc with your device hooked up via usb type fastboot boot recovery. See if that will get you into recovery
Sent from my Nexus 5
It says 'cannot load 'recovery'' and also, I tried flashing ubuntu touch again and it worked.
Edit:
I think it has something to do with my /data partition. It said unable to mount /data again. After fixing that (for some reason it works if I select "format /data and /data/media (/sdcard)" (CWM) I can also format /data. But there a difference between that an all other partitions: for every other partition its like that: mount -> format -> unmount, but for /data it just don't do the last step, it stays mounted.
No on an idea? Do I need to send it in?
Try downloading The Root Toolkit Here.
Connect your phone, open the toolkit. On The First Page select "Soft-Bricked/Bootloop" and Flash Stock+Unroot.
This should Help.
Yeeeeeeey, I have no idea what the tool did, but it works now
Thank you for the tip
Bagbag