Database Users

No operating system installed

I tried to install a new rom after updating TWRP 2.3.0.0. after all was complete it stuck on the boot screen. I then tried with the Nexus Root Toolkit to use a restore from backup. Same problem. I then tried to flash stock and unroot. Same problem. I then tried a number of things through TWRP from backups I had their. Same problem. At present I have no OS and I can only boot into TWRP, turn if off or look at the GOOGLE screen. I have run out of ideas and would appreciate any help offered.

If you have tried everything else (flashing a ROM zip etc.) Then you should flash the factory image from Google.
Don't use the script/batch file as that will wipe your internal storage.
Just flash system and boot.
Sent from my Nexus 7 using xda premium

Sometimes a rom takes a long time to boot for the first time, please be very patient. Also, try wiping everything from /system, and then re install a custom rom from your /sdcard partition. also make sure your roms are for the nexus 7 not galaxy nexus or other similar devices. ONE MORE THING 4.1.2 wont flash with 4.1.1 bootloader.

jmtend said:
I tried to install a new rom after updating TWRP 2.3.0.0. after all was complete it stuck on the boot screen. I then tried with the Nexus Root Toolkit to use a restore from backup. Same problem. I then tried to flash stock and unroot. Same problem. I then tried a number of things through TWRP from backups I had their. Same problem. At present I have no OS and I can only boot into TWRP, turn if off or look at the GOOGLE screen. I have run out of ideas and would appreciate any help offered.
Click to expand...
Click to collapse
There was a bug in TWRP V2.3.0.0 use fastboot to flash V2.3.1.0 and then reflash the rom
Sent from my BAKED Nexus

spaceman860 said:
There was a bug in TWRP V2.3.0.0 use fastboot to flash V2.3.1.0 and then reflash the rom
Sent from my BAKED Nexus
Click to expand...
Click to collapse
Got it working. Thanks all for your suggestions.

jmtend said:
Got it working. Thanks all for your suggestions.
Click to expand...
Click to collapse
How did you fix it? I have no OS and my internal SD card was erased too I don't know how to flash from fastboot

Adb push a ROM.
-Brought to you by Marino's Nexus 7-

AshleyPem28 said:
How did you fix it? I have no OS and my internal SD card was erased too I don't know how to flash from fastboot
Click to expand...
Click to collapse
I know many people hate the talk about toolkits but I was in the same situation and I used Wug's toolkit and it saved me. I downloaded 4.1.2 image directly from Google, as the toolkit only has 4.1.1.
I tried to return to stock on my own and it just went from bad to worse. I would of spent more time trying to fix it on my own but I was on a very tight time constraint. It will unroot your device but it is easy to root again.
Sent from my Nexus 7 using xda app-developers app

Billchen0014 said:
Sometimes a rom takes a long time to boot for the first time, please be very patient. Also, try wiping everything from /system, and then re install a custom rom from your /sdcard partition. also make sure your roms are for the nexus 7 not galaxy nexus or other similar devices. ONE MORE THING 4.1.2 wont flash with 4.1.1 bootloader.
Click to expand...
Click to collapse
THANK YOU the "ONE MORE THING" is all I needed to know for the same problem!

[Q] Nexus 4 wont work after new cyanogenmod update

Hi guys im sort of new to the android scene and im having problems with my nexus 4, i downloaded the newest cyanogenmod nightly and flashed it, it messed up part way through. i rebooted the phone and now its just stuck at boot animation. i have wiped the cache the dalvik cache and done a factory restore.
i have tried reflashing the nightly but it stick stops part way through, i want to add the new rom to the /sdcard but i dont know how, its not showing in android file manager and i have tried using adb push command.
im sure its a noob question but any ideas?
P.s sorry i know there are posts similar to mine but tried them and wont work

If adb push won't work in recovery you might try flashing the factory images with fastboot. System.img is really all you'd need.

estallings15 said:
If adb push won't work in recovery you might try flashing the factory images with fastboot. System.img is really all you'd need.
Click to expand...
Click to collapse
sorry i have no idea how to do that, i just need to access the file system so i can dump a rom to install

AW: [Q] Nexus 4 wont work after new cyanogenmod update
You can try to sideload a new ROM via 'adb sideload' in the recovery.
Sent from my Nexus 4 using xda premium

TobiS87 said:
You can try to sideload a new ROM via 'adb sideload' in the recovery.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
i have tried to side load a rom onto it but that didnt work adb gave a error

http://forum.xda-developers.com/showthread.php?t=2010312
Follow the steps, but only flash the system.img. Once it boots, move your ROM over. Reboot into recovery. Flash.

[Q] Help, boot issue

Hi everyone,
So I have never ran across this issue before. I haven't had any problems with my device and yesterday I wanted to test out the new Jelly Bam update rom from their site. The rom would not boot pasted the "Google" spash screen so I rebooted in to recovery and did a full wipe and restored via backup to my previous rom just like normal. Well then I noticed that normally when I connect my phone to my computer I see my internal memory drive pop up which I am able to click on and then access my files, but this time when I accessed it I have a hand full or folders like 0, twrp, android, etc and I had to double click on o folder to access my memory with all my files. I thought that was weird so I went on about my day. Later I tried to do a fresh install of my current rom PACman but even after doing a fresh install the phone will not boot passed the Google spash screen, and now twrp doesn't even see my backup file because its being directed to this new partition with all the folders I was talking about. I even tried using the file manager in twrp to move the backup to that twrp folder but twrp doesn't even see it.
So as of right now I can get in to twrp but I can not boot my device pasted the google splash screen. I also can't access my memory through my pc since nexus does not allow it with twrp. What do I do? My thoughts are that something got screwed up with the partitions when I flashed the Jelly Bam rom so I will need to go back to stock, does that sound about right? I was thinking of following these instructions to go back to stock and then move on from there, any thoughts or alternatives? http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
Thank you

Trying this method to return to stock: http://www.wugfresh.com/nrt/
If no one has any input I will assume I am following the right path.

I flashed factory images a couple weeks ago and in order for TWRP to see the nandroids I copied back to my phone I put them in the following path: /sdcard/TWRP/BACKUPS/stringofrandomnumbersandletters/
Are your TWRP backups in a similar location?
If you've decided to go back to stock, I'd suggest using the following guide by efrant... http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda app-developers app

It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium

It looks like twrp is now looking at my twrp folder in my sd card 1 not sd card 0 where I have had my backups and all my files. After trying again, I moved the TWRP backup to the sd card 1 twrp folder, twrp recognized it and I restored from backup....but when I reboot I am still stuck on the Google screen. Not sure what to do.

Underground_XI said:
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Since I can't move anything to my memory, any suggestions?

If you've got adb and the proper drivers installed on your PC you could try:
Code:
adb push ROM.zip /sdcard/ROM.zip
from the command prompt. Obviously use the name of the actual ROM.
Edit: ignore that, just read the post where you managed to restore! D'oh!
Have you tried clearing both caches?

The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users

synergeticink said:
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
Click to expand...
Click to collapse
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app

chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that's were I am stuck right now. I am not a pro at using adb commands, never used it till I got my nexus 4. Right now when I launch the cmd it shows "C:\Users\My User Name\Desktop>", not sure where to go next. I guess I am not sure what I should be pushing at this point either.

Oops...it seems I was editing my post at the same time you were responding to it...take a look at my previous response again
I'm fairly new around here but I can help with the adb commands if you need. Hang in there
Sent from my Nexus 4 using xda app-developers app

chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. I tried wiping cache/dalvik/system/factory reset and then both restoring from backup or flashing the latest PACman rom which is in my sd card. Right now I am reading the http://forum.xda-developers.com/showthread.php?t=2018179 guide to see if I can use adb to flash my rom or another recovery. Makes sense if its the recovery not letting me flash anything, but i'm not a dev. At least I am able to get in to recovery to begin with, good sign I guess.

If you can boot into bootloader and recovery there are many options to help get you up and running again. That guide by Jubakuba is really good but if wiping and restoring your backup from within TWRP didn't work I would highly suggest reading efrant's guide on returning to stock...I posted the link in an earlier reply.
Sent from my Nexus 4 using xda app-developers app

I was able to flash cwm using adb, now trying to do a fresh install

Nope, doing a fresh install didn't work. Now its time to restore to stock. ......

One problem:
"
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;"
UPDATE; Got it, instructions were not clear.

synergeticink said:
UPDATE; Got it, instructions were not clear.
Click to expand...
Click to collapse
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app

chef_christoph said:
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Its weird adb will not work on the computer unless the files are in the platform-tools folder in androi sdk. trial and error, just finished flashing system....

should I do this command, I really don't want to lose my stuff:
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
Well, I didn't and finished the process...did a reboot when I was done...now its on the Google screen...just waiting....I'm seeing a Nexus X splash screen!!!...
Update: Its taking a very long time, hopefully it works...going to give it another 10 mins

And we have BOOT... thank you everyone! Now I have to root this sucker!

Nexus 4 stuck on Google screen and twrp

I had the paranoid android rom on my nexus 4 and i tried to install a new rom. the zip must have corrupted because while installing it it failed. And now it wont boot. It goes to the google screen, shuts down, then launches into the twrp menu. Yes i factory reset and wiped before i tried to install. What can i do? I have no bootable rom on my nexus 4 right now?

anyone? Basically my nexus 4 wont boot. I want to mount the nexus 4 using twrp so i can trasfer a rom file over but it wont mount. Any help?

rmhumtex97 said:
anyone? Basically my nexus 4 wont boot. I want to mount the nexus 4 using twrp so i can trasfer a rom file over but it wont mount. Any help?
Click to expand...
Click to collapse
Did you try a 4.4 rom by any chance? there are 1,000's of post to use CWM to be safe, and did you back up you previous rom to restore from TWRP?
If you still have a 4.4 rom zip on you device look for help on flashing CWM http://forum.xda-developers.com/showthread.php?t=1993331
If all else fails you can also try a factory reset http://www.wugfresh.com/nrt/ there is an option to tick on soft-bricked / bootlook in Wugs toolkit.

You can't "mount" your nexus 4. You can use adb to push the appropriate zips over. Or use fastboot to flash .imgs.

Timboe73 said:
Did you try a 4.4 rom by any chance? there are 1,000's of post to use CWM to be safe, and did you back up you previous rom to restore from TWRP?
If you still have a 4.4 rom zip on you device look for help on flashing CWM http://forum.xda-developers.com/showthread.php?t=1993331
If all else fails you can also try a factory reset http://www.wugfresh.com/nrt/ there is an option to tick on soft-bricked / bootlook in Wugs toolkit.
Click to expand...
Click to collapse
Yes i did try a 4.4 rom. I noticed that soft bricked thing in wugs toolkit right before i saw this post, so yeah thats what im doing right now. I should have tried the flashing cwm thing because i do have the 4.4 rom on my device, but ill just wait until google releases it or its stable.

rmhumtex97 said:
Yes i did try a 4.4 rom. I noticed that soft bricked thing in wugs toolkit right before i saw this post, so yeah thats what im doing right now. I should have tried the flashing cwm thing because i do have the 4.4 rom on my device, but ill just wait until google releases it or its stable.
Click to expand...
Click to collapse
I'm using the Nexus 5 port atm and it is stable, i used to skim over the instructions but that extra 5 minutes of reading the flashing instructions will save you hours of searching for a way to get out of a error.

3 options:
1. Adb sideload the things you'd like to flash.
2. Adb push the files onto the device while in recovery.
3. Fastboot flash the factory images.

Going back to stock ready for 4.4

I want to go back to stock to get ready for the 4.4 KitKat it's update. I'll probably flash another ROM anyways but I'd like to try the stock one first. So I'm running aokp, ktmanta kernel, rooted, and philz touch recovery. I know I need the stock recovery, stock ROM, and stock kernel to get the update. Now how can I get those without wiping SD card (which happens when flashing factory image). I don't care if the system is wiped but I want all my files, data, pics, and vids on the SD card saved. Anybody can explain how?
Sent from my Nexus 10 using xda app-developers app

abdel12345 said:
I want to go back to stock to get ready for the 4.4 KitKat it's update. I'll probably flash another ROM anyways but I'd like to try the stock one first. So I'm running aokp, ktmanta kernel, rooted, and philz touch recovery. I know I need the stock recovery, stock ROM, and stock kernel to get the update. Now how can I get those without wiping SD card (which happens when flashing factory image). I don't care if the system is wiped but I want all my files, data, pics, and vids on the SD card saved. Anybody can explain how?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Hi,
The only problem will be your apps, because you won't be able to restore it data without root. However you can factory reset on recovery (probably in your case clean for new ROM install), then just flash boot.img, system.img and recovery.img. I did it many times already, and they never failed to work.
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

XxLordxX said:
Hi,
The only problem will be your apps, because you won't be able to restore it data without root. However you can factory reset on recovery (probably in your case clean for new ROM install), then just flash boot.img, system.img and recovery.img. I did it many times already, and they never failed to work.
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Can I flash these through recovery? Because I'm not sure how to do it using commands. I have wugs toolkit. I think it has the option for flashing stock boot, and recovery but I'm not sure if it has stock system. Plus I don't think root will be an issue because I'm unlocked (obviously since I'm running a custom ROM lol) so it shouldn't be too hard to reroot it. Thanks for your help.
Sent from my Nexus 10 using xda app-developers app

abdel12345 said:
Can I flash these through recovery? Because I'm not sure how to do it using commands. I have wugs toolkit. I think it has the option for flashing stock boot, and recovery but I'm not sure if it has stock system. Plus I don't think root will be an issue because I'm unlocked (obviously since I'm running a custom ROM lol) so it shouldn't be too hard to reroot it. Thanks for your help.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I don't believe you can flash .img with recovery, the only way would be using "dd" command via a terminal/cmd when your tablet is connected. Using the commands is easy, I'll write a script later for installing it, but for now do the following:
Open a cmd on the folder you have fastboot.exe (Wugs toolkit is a good idea) then copy the .img files there (not the zip neither the .tar.gz, extract both and you'll see some .img files, copy them all), plug your Nexus 10 turned on recovery (after the factory reset for clean install) and type:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Hope this helps,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster S4

XxLordxX said:
Hi,
I don't believe you can flash .img with recovery, the only way would be using "dd" command via a terminal/cmd when your tablet is connected. Using the commands is easy, I'll write a script later for installing it, but for now do the following:
Open a cmd on the folder you have fastboot.exe (Wugs toolkit is a good idea) then copy the .img files there (not the zip neither the .tar.gz, extract both and you'll see some .img files, copy them all), plug your Nexus 10 turned on recovery (after the factory reset for clean install) and type:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Hope this helps,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster S4
Click to expand...
Click to collapse
OK thanks that's how I used to flash kernels on my xperia play because it didn't have a recovery. The recovery was buil in with the kernel so that makes sense. Thanks
Sent from my Nexus 10 using xda app-developers app

I'll try this I. A little and post how it goes
Sent from my Nexus 10 using xda app-developers app

Ok I've made cwm backup with philz recovery just in case and titanium backup of all my apps. Now Im gonna copy them to my computer as a precaution. I think I might just copy all 20 gb from my tablet to the cpu and then do a stock image flash and be done with it just to be safe. It'll take forever to transfer all the files but its better to be safe than sorry. But before i do that ill try this way. Im just downloading all the required files for wugfresh toolkit so i can do it.

when is g10 getting 4.4 official update?

kakataditya said:
when is g10 getting 4.4 official update?
Click to expand...
Click to collapse
I'm not sure but it should be coming soon. That's why I want to get my tablet ready for the ota. I like to try stock first before flashing custom Roms. I'm sure well have it within a week or two.
Sent from my Nexus 10 using xda app-developers app

Ok I have some more questions before I go about this. Can I just flash the factory image but delete the userdata disc from the zip first. Im using wugs toolkit and im gonna use flash to stock and unroot option. But i dont want to lose the sd card data so if i delete userdata disc inside the factory img zip will it still work but without wiping sd card? thanks

ok nevermind. I was able to extract the stock image and get the seperate images now im gonna open the command windo and flash them as soon as i copy my backups to the cpu first just in case. Thanks for your help @XxLordxX this is pretty helpful because now i know how to do it by myself without relying on a toolkit.

ok i finally did it. Im turning it on now hopefully my sd data is still there or im screwed. It was too much to backup

And all is good YES! thanks a lot for your help.
This thread can now be used to discuss 4.4 if people want to

So I'm trying to do the same thing.
Downloaded the factory files from Google, got it all flashed and booted up and config'd. But here is the thing. If I reboot into fastboot and then go to reboot into recovery (which I want to be stock recovery) it just gives me the android with a red triangle...
I have seen this before but I can't remember how I resolved it.
I tried manually via fastboot flashing recovery but to no avail.
Thoughts?
PZ

zoomy942 said:
So I'm trying to do the same thing.
Downloaded the factory files from Google, got it all flashed and booted up and config'd. But here is the thing. If I reboot into fastboot and then go to reboot into recovery (which I want to be stock recovery) it just gives me the android with a red triangle...
I have seen this before but I can't remember how I resolved it.
I tried manually via fastboot flashing recovery but to no avail.
Thoughts?
PZ
Click to expand...
Click to collapse
Thats actually a good sign. Thats the stock recovery. If you need to get out of it just hold down power button for 30 seconds. But now you should be ready for the ota update.

Just hit power then the up down keys. That will show the options

Flashed stock on mine yesterday. Now waiting for KitKat update
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from a TW ROM on my monster S4