Database Users

[Q] "No os installed" Help!

i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!

Did you make a backup? You can also use any of the multiple toolkits available to you to reload the stock ROM. Also, questions should be in the QA section to avoid clutter.
Sent from my Nexus 7 using xda premium

graydiggy said:
Did you make a backup? You can also use any of the multiple toolkits available to you to reload the stock ROM. Also, questions should be in the QA section to avoid clutter.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
can you show me the tools (i am a noob at android) or maybe help me in skype or team viewer?

Get an OTG cable and load the Nexus 7 factory image from a USB drive.

kevinperyea said:
i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!
Click to expand...
Click to collapse
Do you have the stock charger? That cable works for connecting to PC.

http://forum.xda-developers.com/showthread.php?t=1766475
This is your best bet.

Boot into recovery and mount then copy across your chosen Rom from your pc and flash
Sent from my HTC One X using xda premium

Easy way out
kevinperyea said:
i have tried to install a custom rom on my nexus but failed as when i meant to factory reset i deleted everything from my sd card (internal memory) so all i have is TWRP (team win recovery project) and fastboot and nothing else. also i cannot connect my nexus to my pc so i cant flash a new rom on to the device. PLEASE some one help me!
Click to expand...
Click to collapse
i always use this method to flash roms as it cuts the hassel of copying the rom into the device for flashing and its very easy actually......just Follow these Steps.. :fingers-crossed:
Download Wug' Nexus Toolkit
Install it and Boot your device into TWRP recovery
Now (assuming that you have Proper Nexus 7 drivers) Open the Toolkit and connect you device to the PC.
Now click the launch button under "Advanced Utilities"
On your device click advanced and the ADB Sideload.
Check mark Wipe Dalvik Cache and Wipe Cache and Swipe to start Sideload.
Now on your PC, click 'sideload update' under "ADB Sideload Update".
Click ok in the next pop-up and now Browse to the custom Rom that you want to flash.
The rom will be uploaded to your device temporarily for flashing and then it will be DELETED once it is Flashed.
This can take upto 30minutes depending on your computer's SPEED.
The rom will be flashed and the device will boot up.
I AM NOT RESPONSIBLE IF YOUR DEVICE BREAKS, OVER HEATS, OR YOU SPILL COFFEE ON IT. DO THIS AT YOUR OWN RISK..!!!
HIT THANKS IF I HELPED...

hassam_tariq2003 said:
i always use this method to flash roms as it cuts the hassel of copying the rom into the device for flashing and its very easy actually......just Follow these Steps.. :fingers-crossed:
Download Wug' Nexus Toolkit
Install it and Boot your device into TWRP recovery
Now (assuming that you have Proper Nexus 7 drivers) Open the Toolkit and connect you device to the PC.
Now click the launch button under "Advanced Utilities"
On your device click advanced and the ADB Sideload.
Check mark Wipe Dalvik Cache and Wipe Cache and Swipe to start Sideload.
Now on your PC, click 'sideload update' under "ADB Sideload Update".
Click ok in the next pop-up and now Browse to the custom Rom that you want to flash.
The rom will be uploaded to your device temporarily for flashing and then it will be DELETED once it is Flashed.
This can take upto 30minutes depending on your computer's SPEED.
The rom will be flashed and the device will boot up.
Click to expand...
Click to collapse
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.

Username invalid said:
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.
Click to expand...
Click to collapse
Hey....Cool Down Bro..
Everybody has different opinions about everything and i am not imposing it, I am just suggesting.

Username invalid said:
Cuts the hassel of copying the rom into the device... how hard is it to copy a zip file from your computers download folder to your device download folder? I found it to be much easier to have all my flashables on my device for reflashing with MultiRom without the need of my computer. The majority of the time just flashing the ROM will not be sufficient; flashing gapps and patches is also needed for it to work properly. And I think it would be extremely concerning if it took up to 30 minutes, even if the computer used was USB 1 with 3400 RPM IDE hard drive. It would not be possible to use a toolkit as his device is unrecognized by his computer, does not have the proper ADB interface driver needed to interact with the toolkit and does not have USB debugging enabled.
Click to expand...
Click to collapse
This wouldn't help at all considering that it looks like OP panicked and did a full internal wipe.
OP, if you have TWRP working I would suggest booting into TWRP, going to Advanced > ADB sideload and then find the ROM zip you were trying to install, then open up command prompt and use adb sideload <path-to-zip> (how exactly you go about doing this last step depends on where you get adb-- any of the previously linked toolkits should include an adb.exe file though that you can run).

Rirere said:
This wouldn't help at all considering that it looks like OP panicked and did a full internal wipe.
OP, if you have TWRP working I would suggest booting into TWRP, going to Advanced > ADB sideload and then find the ROM zip you were trying to install, then open up command prompt and use adb sideload <path-to-zip> (how exactly you go about doing this last step depends on where you get adb-- any of the previously linked toolkits should include an adb.exe file though that you can run).
Click to expand...
Click to collapse
I was replying to the other persons comment, not to the OP. Obliviously he would not be able to connect his device to the computer and use a toolkit.

Factory Reset wiped out the internal SD card! I thought it's not meant to happen?!

This is the first time I'm using a device that doesn't have an external SD card, but I've all along understood that the internal SD card does not get wiped when you do a factory reset, and I'm sure I read that again on another thread just the other day.
My N7 is rooted using Wug's toolkit, with CM10.2 and Bulletproof kernel.
Yesterday I decided to do a factory reset (under Settings, Backup & Reset, Factory Data Reset), but after I did it, all the stuff I had on the internal SD was gone, including my backup files, the ROMs I had transferred there, etc.
Surely this is not meant to be the case, is it??

internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?

sfhub said:
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
Click to expand...
Click to collapse
Thanks for that! (Thanks coming your way). Well, better to know now than later! The down side is that I lost my CWM backups and my Titanium Backup files, but the good thing is that I think I have a TWRP backup that's on my computer.
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?

Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.

oohyeah said:
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
Click to expand...
Click to collapse
I am not sure what issue you are having with TWRP, but you can flash it to the recovery partition and boot to it automatically. If that's the only reason you don't like it, I'd work on fixing the install rather than jumping to another recovery.
oohyeah said:
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Click to expand...
Click to collapse
I would probably do it from recovery. I don't know what CWM does on this platform as I've only used it on other platforms.

What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Sent from my Nexus 7 using xda app-developers app

geckocavemen said:
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Click to expand...
Click to collapse
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign. I remember doing some searches and it seemed like this was normal. I remember the reason was that the N7 would always rewrite the recovery or something. From your responses, I'm guessing it's not normal?
The only way I could get into recovery was using the Wug toolkit using USB debugging/ADB, which really sucked, cos if it bootlooped and I can't get into the system to turn on USB debugging, then I'm not sure what I would do (though I read there's some way around it or something). I had never encountered any such thing with all my many other devices which all run CWM.
So what's up with all that?

"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery

User_99 said:
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
Click to expand...
Click to collapse
This will work fine. If you have no aversion to installing apps, Rom Toolbox Lite gives you power widgets you can put on your desktop then go to recovery with one touch. I use Quick Boot PRO, although the free version of that all may do recovery also. One might work for you until you want to play with mods.
Sent from my Nexus 7 using Tapatalk 4

oohyeah said:
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign.
Click to expand...
Click to collapse
That is stock recovery.
You need to get rid of /system/etc/install-recovery.sh
You can get rid of it by hand, or just install SuperSU from TWRP. Then flash TWRP to the recovery partition.

Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!

oohyeah said:
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
Click to expand...
Click to collapse
None of your blunders has anything to do with TWRP.

khaytsus said:
None of your blunders has anything to do with TWRP.
Click to expand...
Click to collapse
OK let me get something straight.
Obviously, the factory resetting that wiped out all internal storage (the original point of the thread) has nothing to do with TWRP, and I never said it did. On this point though, I'm surprised that it doesn't seem to be more well known that a factory reset would do wipe out all your data (did several searches and only found 'confirmations' that your internal SD data would be left untouched), though I'm glad that I know it now.
The suggestions on different ways to boot into recovery were helpful, though I believe that I would still have encountered the dead android, or would I not have?
What's certainly still not clear to me though is regarding the problem of not being able to boot into recovery and getting the dead android with the exclamation/triangle. After the first few replies, I expected to hear that this was NOT meant to be the case and that I did something wrong in the process or whatever.
However, what I seemed to get was that this is the expected behavior, and what I needed to have done was to "get rid of /system/etc/install-recovery.sh".
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.

oohyeah said:
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
Click to expand...
Click to collapse
Dead android = stock recovery, so normal there.
When you flash a custom recovery on a stock ROM, there is a file, /system/etc/install-recovery.sh, or I actually prefer just renaming /system/recovery-from-boot.p, which will automatically verify your recovery image and restore it to stock if it doesn't match. So you must always remove this file, or the ROM will restore the stock recovery on boot.
TWRP makes it easy to remove either file by mounting /system in read-write mode and using its built-in file manager to remove it. You can do the same in CWM using adb.
As for point 3, yes, try to reboot into recovery again. If you didn't remove (either file), you'll find stock recovery again.

Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.

oohyeah said:
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
Click to expand...
Click to collapse
It really depends on what ordering you do your actions in.
/system/etc/install-recovery.sh doesn't exist on a stock factory shipped system.
It only gets put in place after you install an OTA. If you do all your upgrades using the factory images, you'll never encounter it.
What it does is during your boot process, it will check to see if your recovery is different than what it expects (ie stock). If so, it will install stock recovery by taking the stock kernel and patching it.
If any of the following are true, it will not overwrite your recovery:
/system/etc/install-recovery.sh is missing (or modified to not run as the original file)
/system/recovery-from-boot.p is missing
you are not running the stock kernel
The most common way for install-recovery.sh to be missing is you always used factory images.
The most common way for install-recovery.sh to be modified to not do the original function is if you installed SuperSU. It will overwrite install-recovery.sh with its own.
So in all the back and forth, it is quite possible you got rid of install-recovery.sh or had it modified simply by installing root.
If you then subsequently installed custom recovery, it would stay in place.
Previously you were installing TWRP and flashing it onto the tablet, but upon booting into android, install-recovery.sh realized it wasn't stock recovery, and overwrote TWRP with stock recovery.
That is why whenever you rebooted, you got fallen android (which is stock recovery)
If the way you installed cwm is to use "fastboot flash recovery cwm.img" then the only reason it is around is because something else you did got rid of or modified install-recovery.sh. cwm would be no more immune to install-recovery.sh than twrp was.

oohyeah said:
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
Click to expand...
Click to collapse
Just to clarify, you didn't lose root. You just lost the supersu app, a root permission manager, because it was installed to your /data partition. The su binary was still in /system, all you would have had to do was install supersu from the market.

I'm not sure what else you were expecting from a "factory reset"

creaturemachine said:
I'm not sure what else you were expecting from a "factory reset"
Click to expand...
Click to collapse
Did you read the thread? He explained his reason for expectation quite well.
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?

Skaziwu said:
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Click to expand...
Click to collapse
Depending on which level you are looking at, it didn't really change the behavior, but rather how your data is organized.
Factory reset has always wiped out /data.
On older devices, they put the /sdcard in a separate partition and formatted fat32.
These are the ones that were surviving a factory reset.
On newer devices, the internal /sdcard is starting to migrate onto a directory in /data and the "sdard" you see is "virtual". Since it is on /data, when you wipe data, the virtual sdcard is also wiped.
Some recoveries try to simulate the previous behavior by doing a "rm" of every directory except the virtual sdard when you choose to wipe, instead of the erase/format that Android is doing.
The advantage of keeping the sdcard as a directory under /data is you don't need to decide how much space to split between the sdcard and your /data. Also permissions on files are more flexible being in an ext4 filesystem. Finally since everything is emulated and accessed via MTP, you don't need to unmount the filesystem, so your PC can access it.
There are also cons with this approach, but that is what Google is going with.

HELP Unable to Decrypt Nexus 4 4.3 rooted

I encrypted my nexus 4 a couple of months ago, and I had no issues until I wanted to flash a custom rom. I installed a custom recovery (Clockwork Recovery), and tried to wipe the cache, find the zip file, but it said that it was unable to mount sdcard. I figured that this was due to the encryption, and tried to factory reset the phone. I was unable to do so through the recovery and through the settings app. I followed instructions from the following thread to flash a stock image: http://forum.xda-developers.com/showthread.php?t=2010312 , which was unsuccessful. In the end, I still have all my data, and the encryption remains. Any ideas how to get rid of it?

When running encryption you have to side load everything. Try to side load the ROM you want. if that dose not work download factory image and fast boot it over.

illru said:
When running encryption you have to side load everything. Try to side load the ROM you want. if that dose not work download factory image and fast boot it over.
Click to expand...
Click to collapse
Could you give me directinos on how to do this? Or a link to another thread or video?

SpectralFlames said:
Could you give me directinos on how to do this? Or a link to another thread or video?
Click to expand...
Click to collapse
I believe to sideload you use adb and place the zip you want in the adb's folder, plug your phone into recovery, and use the command adb sideload (zip file name) or something or the sort and you should be good to go, have you tried
fastboot erase system
data
cahc?
Sent from my Nexus 4 using Tapatalk

IRX120 said:
I believe to sideload you use adb and place the zip you want in the adb's folder, plug your phone into recovery, and use the command adb sideload (zip file name) or something or the sort and you should be good to go, have you tried
fastboot erase system
data
cahc?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
When in recovery it says that it can't mount sdcard so it doesnt allow me to do anything through recovery. That was the main issue when trying to flash a rom

[Q] Nexus 4 with No OS - Bricked?

Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?

Any help? Please

Goto cmw and install your ROM via adb.
Under option install zip there will be a choice for flashing zip via adb. Just select that in cmw and connect your phone to laptop.
Now in laptop you should have adb files in a folder and paste your ROM in that adb folder.
Next do as it is written in cmw and it will be flashed
Sent from my Nexus 4 using xda app-developers app

suvasco said:
Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?
Click to expand...
Click to collapse
You cant brick your phone as long as fastboot and recovery works.
boot into fastboot.
if your recovery is not working : reflash your recovery
Then boot into recovery and install rom via sideload;
From your pcadb sideload):
http://teamw.in/ADBSideload

Try wugfresh tool kit from here: http://www.wugfresh.com/nrt/

suvasco said:
Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?
Click to expand...
Click to collapse
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!? - What you can do is some leg work and look up how to ADB push instead of saying you dont know what that is. Now if you rooted your phone yourself at some point an ADB push was probably done. This is why most hate toolkits(if thats what was used) since it does not help you learn anything.
Search my friend but its like starting from scratch but if you have a working recovery still thats one less step...
adb push -> rom to phone
boot into recovery
flash rom
go on with life......:good:

playya said:
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!? - What you can do is some leg work and look up how to ADB push instead of saying you dont know what that is. Now if you rooted your phone yourself at some point an ADB push was probably done. This is why most hate toolkits(if thats what was used) since it does not help you learn anything.
Search my friend but its like starting from scratch but if you have a working recovery still thats one less step...
adb push -> rom to phone
boot into recovery
flash rom
go on with life......:good:
Click to expand...
Click to collapse
That, or use adb push or sideload from recovery.
Sent from my Nexus 7 using Tapatalk

korockinout13 said:
That, or use adb push or sideload from recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes... sorry I forgot to add sideload and if you not sure what that is please use Google
Edit; My bad I see instructions and website for sideloading were posted area in here

OS wiped accidentally from TWRP recovery

I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Click to expand...
Click to collapse
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk

Exiwolfman said:
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?

Your phone should boot into recovery, so as long as it goes on and boots all u do u is use ur pc to move file over and flash it...
Sent from my Nexus 6P using Tapatalk

Kalaxy said:
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Click to expand...
Click to collapse
Boot into bootloader (hold power and system on), flash the though recovery through adb, mount your .zip,, flash your .zip through recovery. Sorry if that doesn't make sense, I've been drinking with the roommates, lol.
Edit: if that doesn't work, send me an IM and I will help you in the morning
Sent from my Huawei Nexus 6P using XDA Labs

Which state is your phone in right now? Is it bootlooping or in recovery?
Sent from my HTC 10 using Tapatalk

The same thing happened to me also! The whole /data (incl. sdcard) partition went corrupt (showed up in TWRP as eemc instead of ext4) & the /vendor failed to mount.
First I had to repair the /data partition (unfortunately the data was lost, as it repaired to a blank partition). I ended up having to go home (was at work at the time) & hook the phone up to the PC & download the ROM & transfer it onto the sdcard. I'm not entirely sure why/how this happened, but I believe it was because a corrupt vendor IMG. Although that theory doesnt include why the /data partition corrupted, it only explains why the /vendor partition failed to mount.

Fastboot flash system system.img
?

removed

I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?

Have a look here how to load in bootloader, flash, etc.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.

5.1 said:
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
Click to expand...
Click to collapse
Thats what I thought. JUst wanted to make sure I could get into bootloader still

dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Yes TWRP has a reboot to bootloader option available. So you can access fastboot via bootloader to flash the necessary images. Just don't forget to re flash TWRP image again in case the stock recovery image was flashed beforehand.

The odd thing was that I did choose that option to boot to bootloader in twrp and it didn't work. I ended up having to reboot to bootloader manually. Not a big deal. All is working now, but thought that was interesting.

Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Click to expand...
Click to collapse
Exactly which partitions did you wipe? system? data? Internal Storage (userdata)? all of the above? Hopefully you did not wipe userdata (all your stuff). Were you on a stock ROM? You should be able to d/l the Google image from the same build you were on, extract system and data and fastboot flash those. Don't flash userdata. All your stuff should be there. Follow the tutorial on how to set up fastboot and selectively flash partitions.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
This thread got hijacked at least 3 times. Let's hope OP can find his way back.

pocholo36 said:
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Click to expand...
Click to collapse
Try this Hope you get solution to your problem of installing adb and fastboot tools in the correct manner.

I just by mistake deleted my internal storage.
I have TWRP, how do i put the ROM on there and flash it? Someone please help.
Thanks