Database Users

Fastboot> Recovery dosen't find *.img file on SD card

Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks

What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.

You didn't unzip them did you?

You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.

Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.

Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery

I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?

MyTouch won't boot into recovery (but boots normally)

Very weird problem here. The phone will boot into the OS just fine but whenever I try to boot into the recovery to flash a rom... it just hangs on the MT3G screen.
I've tried re-flashing RA 1.7.0G and the clockwork, same problem.
It's a 32B if that makes any difference.

I had this same problem where the recovery partition on the phone went corrupt on me. I have the same phone and carriuer as you. I read and read for a fix. The one that eventually worked for me was repeatedly trying to flash Amon RA 1.7.0 through rom manager. That was also what cause the problem seeing as I ran out of ram flashing it through there. I also tried fastboot and failed (I was able to do it once it was back up). and terminal and adb. GOOD LUCK MAN.

Jimmy Conley said:
I had this same problem where the recovery partition on the phone went corrupt on me. I have the same phone and carriuer as you. I read and read for a fix. The one that eventually worked for me was repeatedly trying to flash Amon RA 1.7.0 through rom manager. That was also what cause the problem seeing as I ran out of ram flashing it through there. I also tried fastboot and failed (I was able to do it once it was back up). and terminal and adb. GOOD LUCK MAN.
Click to expand...
Click to collapse
Much thanks for this advice...I didn't want to have to start all over again...I was able to get Amon's recovery working again by keeping retrying the flash...loll...it finally work...NOt messing with Rom Manager no more....

I had this happen to me today on RC1. I stupidly flashed Clockwork Recovery from within ROM Manager, only to discover that it wouldn't boot into recovery and just sat at the green MyTouch boot screen.
I was able to flash Amon_RA from within ROM Manager (the phone sat there for like 10 minutes before finally saying "Flash Successful!" or whatever), and I was then able to load RC2 without issue, clear the dalvik-cache, etc.
Never touching ROM Manager again.

I did the same thing. (Tried to flash Clockwork Recovery from within ROM Manager.) I haven't ever done a recovery like this...but I figured since it was an option on ROM Manager that everything would be fine and dandy. It wasn't. Hung at MT3G screen when booting into recovery. Flashed AMON_RA from ROM Manager and everything works now. No more ROM manager for me!

my phine (1st gen mytouch 3g) is rooted and has the current 5.08 blah blah version of cyanogenmod. i downloaded the new version today and tried flashing via rom manager (again a 1st timer with this app) and figured it would work. gets stuck at green mytouch logo. i will keeo trying to flash the amon ra back. the only laptop i have access too doesnt recognize any android phone so i cant transfer files back and forth >_< not a fun day
on the other hand it boots fine after about 20 min into cyanogen 5.8 blah blah version lol

That has happened to me also when using ClockworkMod Recovery & ROM Manager.
I recommend to use fastboot for recovery flashing:
(0. If you don't have the Android SDK, get it. Also get your favorite recovery img)
1. Copy fastboot.exe, adb.exe, AdbWinApi.dll & AdbWinUsbApi.dll to %WinDir%\System32
2. Connect your phone via usb to your PC. Shut it down and then boot while pressing back + power until you're in fastboot. Start CMD and run "fastboot devices"
3. If and when you get an ID, you're ready to go.
4. Type "fastboot erase recovery"
5. Move the recovery image to C's root folder (C:\) and in CMD type "CD.." for example like three times until you're in C:\.
6. Type "fastboot flash recovery [your recovery image]"
(for example "fastboot flash recovery recovery-RA-Magic32A-6.35-v1.6.2.img")
After that, shut down your device and reboot while pressing home + power until you're successfully in recovery!
This works for me.

Help! Can't boot / cant get into recovery. ..

I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .

jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!

i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?

jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.

you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot

Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium

Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?

jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.

So I can literally flash a different recovery from within another?

jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium

Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks

Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk

I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.

Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.

firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.

My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.

Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.

Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+

" x " appears on the screen

Malfunction " x " appears on the screen !! help me what is going on

Haha... you'll need more information than that if you want real help.
Based on the limited information though I suspect your phone is stuck in a bootloop. I'd hook it up to the PC via USB and check the logcat. Probably something screwed up.. Maybe time to restore your latest backup.

Did you flash any ROM if so, did you clean your Dalvic+REgular Cache

If you don't have an Recovery:
- Connect your Micro SD on PC
- Download and insert on SD the stock ROM of your Nexus One
- Power ON your Nexus with Volume Down Pressed.
- Autmotically Restore Nexus (You should say Yes xD)
At this time, you decide if you want to be root and install other ROM

you better just list your setup info before doing anything
locked/unlocked bootloader
rooted/unrooted
which recovery are you using
what rom are you running stock/custom
what were you doing when this happened
a couple safe things you can do in meantime is to pull battery and reinsert and power on
if it goes back to X, pull battery and DO NOT power on. Hold down the pwr button and trackball at same time and see if you can get into recovery
the third is hold down trackball/vol-/power at same time while X is on screen and see if you can get to recovery that way
if you can't get to recovery you will need to fastboot new recovery, assuming you are unlocked
once you get into recovery do a nandroid if you are rooted
and copy it to pc as a secondary backup
it is possible you may need to try the passimg method in wiki
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#Unroot_.2F_Restore_your_Nexus
also to do fastboot commands you need usb debugging selected on phone--hope it is

Hello, i have a similar problem with my n1
the phone starts and just shows the nexus X - (waited for 15 min. nothing happend)
i can go to the bootloader / fastboot menu with PWR + (Vol-) but i can not go to the recovery mode. -> the phone reboots and get stuck at the X
the phone is rooted
blackrose / hboot 7.35.5017
radio 5.12.00.08
recovery was ext4
i had a german ics miui rom installed and tryed to install the latest ics miui us rom after it didn't booted the miui us rom i turned the phone off and tryed a few hours later to turn it on to reflash the german ics miui rom.
1.)
i tryed to install a new recovery image ->
recovery-clockwork-5.0.2.0-passion &
recovery-RA-passion-v2.2.1
(still get stuck at the X if i try to go to recovery mode)
2.)
i tryed this one with the passimg.zip but nothing happens if i put in the sd card :/
(with nothing i mean the green text show that the sd card is checking for PASSDIAG.zip and PASSIMG.zip but dosn't found it)
i also tryed:
3.)
erased boot
flash boot from passimg.zip (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed)
4.)
erased cache
erased userdata
started again with 1.)
5.)
got frustrated and erased system -.-
any ideas?

study it ,thank you
study it ,thank you

Hmm, sorry if its obvious but i have no idea what it could be or what i have to search to find the solution. Would be nice if you could give me a hint. Of course im not asking for a step by step solution. Thank you.
Send from my awesome SE K800i

not sure why you are flashing boot images
do you have a nandroid--copy your sdcard with the nandroid to pc--all of sdcard
are you flashing thru fastboot in command window
did you read my post above on getting to the fastboot screen--can you do that--the one with the 3 androids
pwr/vol-/trackball same time, may take 20-30 seconds
if you can get there, put your recovery image in your fastboot folder on pc, normally tools--assuming you have sdk installed, your phone must have usb debugging checked--I hope
open a command window and change directory to the tools folder or wherever the fastboot.exe file is. Something like:
cd/
cd/ android/android-sdk-windows/tools for me
then on same line type
fastboot devices (it should show your phone H#)
fastboot erase system
fastboot flash recovery recovery.img (or the exact name of the recovery image, checked by right clicking on the img file in your tools folder and looking under properties)
I would use amonra you listed above and check the md5 if possible
hopefully the recovery will flash
if not you can go to the wiki link i posted above and try passimg metthod from there, use correct one. don't add the .zip. Windows will had it automatically.
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems

rugmankc said:
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
Click to expand...
Click to collapse
thank you very much
i already tryed everything else what you wrote but i didn't wiped 3 times... after erasing recovery partition 3 times i was able to flash a new recovery and it started.
Thanks a lot!

Glad that you got it

[Q] Factory image restore fail : stuck at writing system

Hello everyone!
I tried to restore the stock image using Nexus 4 Tool Kit (both the original one and the Wug's one), and everytime I tried, the script stucked at "writing system".
I manually flashed system and userdata images with Wug's tool kit and everything went well but I only have 5Gb memory instead of 16.
Does anyone know why?

Try this http://forum.xda-developers.com/showthread.php?t=2033692
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Sent from my Nexus 4

OP...
In future, don't use a toolkit. Do it yourself

I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?

4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
When going into recovery the warning sign is the splash screen for stock recovery. This likely means that you have not yet flashed a custom recovery yet, which is necessary to flash CM. First read this guide to unlock the bootloader (if you havent already), then flash a custom recovery (preferably TWRP). After you have installed the recovery, download CM as well as the latest gapps package and place them somewhere on your internal sd. Boot into recovery and go to the wipe menu, then swipe to factory reset. Finally flash the rom and gapps, and then reboot.

4OnTheFloor said:
I'm having a similar problem to the OP - I'm trying to do a factory restore, and am unable to flash the "system" image. I can't boot, recovery mode won't work anymore (I get a red warning sign instead)...
I think all of this has to do with me being naieve and following a youtube video instead of the CM wiki to install CM 10.1.
How can I unbrick my phone?
Click to expand...
Click to collapse
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.

noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I am using the .bat file... I've also tried the toolkit, and both appear to use the same basic procedure, and they stop at "writing system" no matter what.
Does anyone happen to know how the .bat file and toolkit get access to the phone? ...because I can't see it in adb (I'm guessing it's because I can't boot the phone.) However I can get into fastboot and recovery modes on the device.
I cannot get the device (nexus 4) to boot or connect in ADB mode to my computer. What can I do??
UPDATE - PROBLEM FIXED
I un-bricked my phone
SOLUTION this is what worked for me, your mileage may vary
Install ADB drivers, etc. from Android SDK (google how to do this)
Flash custom recovery (can be done easily with Nexus 4 Toolkit here on XDA) - I used TWRP Touch Recovery.
Once that is done, shut the phone off completely and boot into Fastboot (hold volume down and power)
Use volume keys to select Recovery Mode, then hit Power
In recovery mode:
Wipe > Advanced Wipe > Check off the box beside "System" > Swipe to Wipe
Go back to recovery mode main screen:
Wipe > Format Data > Follow the instructions on the screen
I think this step is what did it. When having problems with partitions, just format everything and start over
Now we should be able to write to the System partition, meaning you can flash a ROM and get your phone to boot again.
Follow the rest of these instructions to quickly flash the stock Android image from Google onto your phone.
Go back to recovery mode main screen, once again:
Reboot > Bootloader > Follow any additional instructions it gives you
Download Google Nexus 4 factory stock image "occam" (Google it)
When that is downloaded, open it with 7zip. Inside there are some files, one of which is called image-occam-jdq39.zip. Inside are some images - unzip those as well. You'll need the system.img file in a bit...
Using Wug's Nexus Root Toolkit (Google it - install it on your Windows PC):
Open the program
Launch advanced utilities
Hit the System button to permanently flash to System partition. Hit "ok" on the window that pops up.
Find the system.img file I mentioned back on step 10 and select that, when prompted, and open it.
If all went well, your device will now boot into the stock Android ROM.

noobdeagle said:
if you are doing a factory restore and DONT need to flash everything individually than don't. yes its good to know how to do it manually but if your flashing everything back just use the script that google provides.
reboot to bootloader/fastboot and run the flash-all.bat file and its all done for you. no toolkits no playing with commands that you dont know properly etc.
if you dont know how to do it right pick the least complicated option.
Click to expand...
Click to collapse
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.

Soundchasr said:
I too am stuck at writing system. I"m not sure what you mean when you said "run flash-all.bat". Where do I get that?
Thanks.
Click to expand...
Click to collapse
The system takes awhile to write, how long have you guys wait before you say its "stuck"?
Sent from my Nexus 4 using Tapatalk 4 Beta

About 20-25 minutes.

Yea, that's way too long.
Sent from my Nexus 4 using Tapatalk 4 Beta

Stuck, but working
I was flashing the 4.3 image using the included flash-all.bat (but I edited it to remove -w parameter so that it wouldn't wipe my data).
In the 'writing system' step, the command window got stuck. In the phone screen, at the bottom, it said 'writing' for a while and then that also went away. I waited for ~40 min, and still the command window was at 'writing system', so I closed the command window, and booted my phone by selecting start from the bootloader.
And voila! It worked. Booted in under a minute, the flash was a success, I got JB 4.3 without losing any of my data.
Lost my root and custom recovery though. But I knew that would happen. Gonna try SuperSu for 4.3 now, after flashing TWRP.

Had the same problem, tried everything! With my tiny powers, but it kept stucking at "writing system" . I thought that I bricked the device, so for the last hope, I installed WugFresh's Nexus Toolkit and did a Fast Stock + unroot. It Installed everything flawlessly! I'm gonna donate to that guy! He's a godsend savior.