Database Users

Accidentally erased my OS. Need help getting it back.

Made a silly mistake. I was going to flash M-kernel to my device after updating to 4.2.2 and while I was in Team Win recovery I chose to wipe cache and system. I flashed the kernel and now when I select to reboot it says "No OS installed! Are you sure you wish to reboot?" I still have the file to flash 4.2.2 but don't know how I can get it on the device in it's current state. Any help would be greatly appreciated.
I tried this method here: http://forum.xda-developers.com/showthread.php?t=1667929 however I can't get Unmount/sdcard to work in the recovery menu and therefore can't push the OS file using the cmd prompt.

You may have to fastboot the system.img and boot.img into place. How did you root? Did you use root and unlock? Did you use wugs? Do you have android sdk and fastboot installed?
Btw, I did this too. I was preparing to flash a rom, did a factory reset, wipe system, and (understand I had just gotten this device at the time LOL) wiped internal storage. Which meant my backups and update.zips were gone. The nexus 7 doesn't seem to have a way to mount twrp from recovery to side load files so I just used fastboot to fix it.

hlxanthus said:
You may have to fastboot the system.img and boot.img into place. How did you root? Did you use root and unlock? Did you use wugs? Do you have android sdk and fastboot installed?
Btw, I did this too. I was preparing to flash a rom, did a factory reset, wipe system, and (understand I had just gotten this device at the time LOL) wiped internal storage. Which meant my backups and update.zips were gone. The nexus 7 doesn't seem to have a way to mount twrp from recovery to side load files so I just used fastboot to fix it.
Click to expand...
Click to collapse
I use Root Tool Kit to root and unlock. I have android sdk installed on the PC but not sure what fasboot is. Can you explain how to "fasboot the system.img and boot.img into place"?

If you are using the toolkit, just select your device, select flash stock firmware and connect your nexus in bootloader mode (fastboot mode, hold volume down and power when it's turned off)
Sent from my Nexus 7 running Android 4.2.2

mihahn said:
If you are using the toolkit, just select your device, select flash stock firmware and connect your nexus in bootloader mode (fastboot mode, hold volume down and power when it's turned off)
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Will doing this cause me to lose everything I have on the Nexus already?

Please help! Stuck on

Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.

Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit

Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?

Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.

efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?

Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium

not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command

In twrp, it keeps saying starting adb sideload feature

i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!

Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"

Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2

Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium

efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2

[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.

[Q] German Nexus 7 in reboot loop after OTA update

Hello,
my rooted but otherwise unchanged Nexus 7 won't boot anymore after the automatic installation of the OTA KitKat update.
It shows the robot lying down with a red warning sign and the text "Kein Befehl" (means: no command). After a minute or so it reboots again ...
I haven't even found a way to turn it off ....
Is there any way to fix it?

Nabeshin said:
Hello,
my rooted but otherwise unchanged Nexus 7 won't boot anymore after the automatic installation of the OTA KitKat update.
It shows the robot lying down with a red warning sign and the text "Kein Befehl" (means: no command). After a minute or so it reboots again ...
I haven't even found a way to turn it off ....
Is there any way to fix it?
Click to expand...
Click to collapse
http://www.wugfresh.com/
Download the Nexus Root Toolkit and use it to repair your N7.

NLBeev said:
http://www.wugfresh.com/
Download the Nexus Root Toolkit and use it to repair your N7.
Click to expand...
Click to collapse
thank you, will try that. So I may rescue the pad but i fear the data will be lost?

Nabeshin said:
thank you, will try that. So I may rescue the pad but i fear the data will be lost?
Click to expand...
Click to collapse
Had the same problem, the only solution for solwing it was flashing the 4.4 via fastboot.
And of course all the data was lost.
It's some sort of bug, you're not the only one and no matter if rooted or not, my nexus was unrooted and with locked bootloader. Google f**ked up something big time.

Nabeshin said:
thank you, will try that. So I may rescue the pad but i fear the data will be lost?
Click to expand...
Click to collapse
In case:
a. the bootloader is unlocked and you can start Nexus 7 in fastboot mode
b. N7 is connected to a PC
c. you can get response from N7 with a command in a Dosbox: fastboot devices
Then there is something you could try first. You need the factory image that fits your model.
(Google factory images: https://developers.google.com/android/nexus/images?hl=de#occamkrt16o)
Example (N7 2012 wifi only)
Factory image nakasig-krt16s-factory-1e882585.tgz; extract and find the zip-file: image-nakasig-krt16s.zip.
You can flash manually that zip-file with the following command in a Dosbox. Fastboot update image-nakasig-krt16s.zip
To flash manually you need the files fastboot.exe - AdbWinApi.dll - AdbWinUsbApi.dll in the same directory as the mentioned zip-file.
These files are in the Nexus Root Toolkit of Wugfresh.

Another victim of Google OTA
NLBeev said:
In case:
a. the bootloader is unlocked and you can start Nexus 7 in fastboot mode
b. N7 is connected to a PC
c. you can get response from N7 with a command in a Dosbox: fastboot devices
Then there is something you could try first. You need the factory image that fits your model.
(Google factory images: https://developers.google.com/android/nexus/images?hl=de#occamkrt16o)
Example (N7 2012 wifi only)
Factory image nakasig-krt16s-factory-1e882585.tgz; extract and find the zip-file: image-nakasig-krt16s.zip.
You can flash manually that zip-file with the following command in a Dosbox. Fastboot update image-nakasig-krt16s.zip
To flash manually you need the files fastboot.exe - AdbWinApi.dll - AdbWinUsbApi.dll in the same directory as the mentioned zip-file.
These files are in the Nexus Root Toolkit of Wugfresh.
Click to expand...
Click to collapse
Great instructions! I also fell victim to the botched OTA. Unlocked but otherwise stock (not rooted). These procedures allowed me to retain documents and music. Many thanks!

[Q] Nexus 10 in bootloop in recovery

Trying to upgrade to KK from 4.2 and now I'm stuck in bootloop teamwin screen. I can get to the fastboot screen (Droid on back with cover open with "Downloading..." below. Tried using SkipSoft tool, but nothing seems to help. Any suggestions?

Hi,
Try downloading and installing the KitKat ROM via fastboot. You can find the file in https://developers.google.com/android/nexus/images#mantaray, after you download you'll have to extract it and then you have two options to follow.
First things first, you'll have to copy the files that were extracted to a fastboot folder, or you can copy the fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll and adb.exe to the folder where flash-all.bat folder is. Then you can execute the .bat by clicking on it twice, remember that you have to have your device on fastboot mode (press and hold both volume buttons then press power button). The only thing is that it will reset your device to stock, so all your data will be lost.
And the second option will save your data, you have to factory reset your device via recovery, then reboot in fastboot. You'll then extract the zip and get all .IMG files in the fastboot folder. Then you'll open a cmd in the folder and type the following:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
This will reflash your device and you'll get to boot in KitKat stock . Good luck, hope this saves your device .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10

I kind of think USB debugging is not enabled. Do you think that can cause a problem?

whitedeacon said:
I kind of think USB debugging is not enabled. Do you think that can cause a problem?
Click to expand...
Click to collapse
Hi,
You can still boot to fastboot with it disabled . So no problems!!
~Lord
Sent from my GT-I9505 using Tapatalk

XxLordxX said:
Hi,
Try downloading and installing the KitKat ROM via fastboot. You can find the file in https://developers.google.com/android/nexus/images#mantaray, after you download you'll have to extract it and then you have two options to follow.
First things first, you'll have to copy the files that were extracted to a fastboot folder, or you can copy the fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll and adb.exe to the folder where flash-all.bat folder is. Then you can execute the .bat by clicking on it twice, remember that you have to have your device on fastboot mode (press and hold both volume buttons then press power button). The only thing is that it will reset your device to stock, so all your data will be lost.
And the second option will save your data, you have to factory reset your device via recovery, then reboot in fastboot. You'll then extract the zip and get all .IMG files in the fastboot folder. Then you'll open a cmd in the folder and type the following:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
This will reflash your device and you'll get to boot in KitKat stock . Good luck, hope this saves your device .
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
Click to expand...
Click to collapse
Tytyty! You totally saved me with this solution you mentioned. I was stuck in a boot loop as well after trying to root my Nexus 10 and I've been searching Google for the past 2 hours for a solution. Yours worked like a charm and I'm back on a stock-rom for now. Going to do more research on the Forums here before attempting this again.

xRyudo said:
Tytyty! You totally saved me with this solution you mentioned. I was stuck in a boot loop as well after trying to root my Nexus 10 and I've been searching Google for the past 2 hours for a solution. Yours worked like a charm and I'm back on a stock-rom for now. Going to do more research on the Forums here before attempting this again.
Click to expand...
Click to collapse
If you want to root easily just use wug freshs toolkit. Or just download twrp. Flash it through fastboot the same way you restored stock (make sure your boot loader is unlocked which can be fine with the command fastboot oem unlock) then flash the supersu zip from chainfires thread
Sent from my white LG Nexus 5

Big thanks!
abdel12345 said:
If you want to root easily just use wug freshs toolkit. Or just download twrp. Flash it through fastboot the same way you restored stock (make sure your boot loader is unlocked which can be fine with the command fastboot oem unlock) then flash the supersu zip from chainfires thread
Sent from my white LG Nexus 5
Click to expand...
Click to collapse
Wug freshs toolkit was definitely a lifesaver for my bootloop. Thanks for all the help on this thread. Glad someonehad the same issue as me and you guys were able to help us!