Database Users

[Q] aciidentally deleted my rom please help

i deleted my rom so my nexus 4 just boots up and google image loads how do i install back my stock rom and also usb connection is also not possible as it does load any rom please help me

Use adb to push a ROM to your phone and flash it or use fastboot and flash the system.img
Sent from my Nexus 4

spaceman860 said:
Use adb to push a ROM to your phone and flash it or use fastboot and flash the system.img
Sent from my Nexus 4
Click to expand...
Click to collapse
can you explain indetail since im just a beginner

How did you root your phone did you install the drivers on your computer or did you use a toolkit
Sent from my Nexus 4

sum93 said:
can you explain indetail since im just a beginner
Click to expand...
Click to collapse
Do you have a computer? You said something about usb support. You need to plug your usb cord into the computer and connect your nexus 4. It gets a lot more complicated in the next few steps so let me know if you can plug in your nexus 4.

sum93 said:
can you explain indetail since im just a beginner
Click to expand...
Click to collapse
There's 3 main components.
1) Bootloader
2) Recovery
3) System
If you have previous rooted your rom, then you most likely have a custom recovery, such as TWRP or CWM.
If you can get into recovery, then you can mount your data partition, and do something like
adb push name-of-rom-file.zip /sdcard
and any other zips you need.
From there for clean-measure you can format /system , /cache and dalvik-cache, then go to "Install" and choose the rom zip you wish to install (though if you plan on using a rom different than your original you may wish to do a 'factory reset' in recovery to clean the main /data area to avoid settings conflicts).
Once you've installed the roms + addons you want, you should be able to reboot into it.
If you did not root your rom, and likely do not have a custom recovery, that's something that can be installed via fastboot from the bootloader, so let us know which options you have available to you.
This can go easy or hard depending on how much knowledge you have of ADB and Fastboot, or if you instead used a toolkit to do it for you (meaning you wouldn't easily know where to run adb/fastboot).

Read this thread - http://forum.xda-developers.com/showthread.php?t=2010312

how to push rom file inside the intenal momery
kbeezie said:
There's 3 main components.
1) Bootloader
2) Recovery
3) System
If you have previous rooted your rom, then you most likely have a custom recovery, such as TWRP or CWM.
If you can get into recovery, then you can mount your data partition, and do something like
adb push name-of-rom-file.zip /sdcard
and any other zips you need.
From there for clean-measure you can format /system , /cache and dalvik-cache, then go to "Install" and choose the rom zip you wish to install (though if you plan on using a rom different than your original you may wish to do a 'factory reset' in recovery to clean the main /data area to avoid settings conflicts).
Once you've installed the roms + addons you want, you should be able to reboot into it.
If you did not root your rom, and likely do not have a custom recovery, that's something that can be installed via fastboot from the bootloader, so let us know which options you have available to you.
This can go easy or hard depending on how much knowledge you have of ADB and Fastboot, or if you instead used a toolkit to do it for you (meaning you wouldn't easily know where to run adb/fastboot).
Click to expand...
Click to collapse
i did the root through nexus tool kit so how do i copy rom files inside internal memory and also how do i mount the drive

sum93 said:
i did the root through nexus tool kit so how do i copy rom files inside internal memory and also how do i mount the drive
Click to expand...
Click to collapse
This is why you shouldn't use toolkits without knowing the process behind it read this guide it will show you how to fix it
http://forum.xda-developers.com/showthread.php?t=2010312
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
Sent from my Nexus 4

HELP: Possible bricked phone?

I'll try to make this brief.. long-time lurker, first time poster.
My Nexus 4 currently is in a brick state. I had PA 3.99 RC2 installed, and when attempting to flash a new font file, the device will now no longer boot, stalling at the boot logo. I foolishly did not make a back-up (though I thought I did.. probably tapped the wrong button). From that point, I tried a data wipe as well as a cache/dalvik cache wipe, and the same thing happens.
I have an old back-up (about a week or 2) on my phone from a different ROM (I believe MIUI) but when I attempt to restore it with Clockwork Mod Recover I get an "md5 mismatch error."
Currently, I do not have the proper Nexus 4 drivers on my computer - when I plug my device in, it does not show up for me to drag/drop anything in to it to flash it. Is it still possible to install the proper USB drivers in its current state?
I plan to try installing the drivers and android SDK and then sideloading a ROM onto it with ADB, but I'm not sure if I'll be able to install the drivers properly for the phone to show up on my computer, and I won't be able to check until I get back to my desktop computer (my laptop has restricted privileges so I can't install drivers) until tomorrow.
Anyone else have any other ideas or suggestions? Please let me know.

Kirbyscream said:
I'll try to make this brief.. long-time lurker, first time poster.
My Nexus 4 currently is in a brick state. I had PA 3.99 RC2 installed, and when attempting to flash a new font file, the device will now no longer boot, stalling at the boot logo. I foolishly did not make a back-up (though I thought I did.. probably tapped the wrong button). From that point, I tried a data wipe as well as a cache/dalvik cache wipe, and the same thing happens.
I have an old back-up (about a week or 2) on my phone from a different ROM (I believe MIUI) but when I attempt to restore it with Clockwork Mod Recover I get an "md5 mismatch error."
Currently, I do not have the proper Nexus 4 drivers on my computer - when I plug my device in, it does not show up for me to drag/drop anything in to it to flash it. Is it still possible to install the proper USB drivers in its current state?
I plan to try installing the drivers and android SDK and then sideloading a ROM onto it with ADB, but I'm not sure if I'll be able to install the drivers properly for the phone to show up on my computer, and I won't be able to check until I get back to my desktop computer (my laptop has restricted privileges so I can't install drivers) until tomorrow.
Anyone else have any other ideas or suggestions? Please let me know.
Click to expand...
Click to collapse
Adb works in recovery, so you can install adb drivers, then use "adb push" or "adb sideload". Try installing the same ROM version you had before (PA). It might work, and also save your data.

abaaaabbbb63 said:
Adb works in recovery, so you can install adb drivers, then use "adb push" or "adb sideload". Try installing the same ROM version you had before (PA). It might work, and also save your data.
Click to expand...
Click to collapse
Took awhile to get ADB drivers to work (fastboot was recognizing it fine)... pushed over the .zip file and just installed it, and everything works great! Thank you!

Nexus 7 (2012) partially wiped and can't restore

Nexus 7 was running slow. I had Teamwin recovery on the device and was stock 4.3 unlocked/partially rooted. Booted device into recovery and wiped cache, dalvik, usb otg, sd int, and sd ext, and data. Teamwin somehow remained. While trying to use WugFreshs tool I must have restored the recovery to stock...maybe. The device is now always on and will not turn and you cannot get into recovery but you can reboot and get to the bootloader. At this point I tried the flash stock/unroot soft-brick feature of Wugfresh and it does not work even if I enabled Force Flash Mode.
Tried doing this thru adb but have limited adb skills and with the instructions I was following it assumed USB debugging was enabled (my device was wiped so not sure about that).
Any help will be greatly appreciated! Thank you!

yagermeister said:
Nexus 7 was running slow. I had Teamwin recovery on the device and was stock 4.3 unlocked/partially rooted. Booted device into recovery and wiped cache, dalvik, usb otg, sd int, and sd ext, and data. Teamwin somehow remained. While trying to use WugFreshs tool I must have restored the recovery to stock...maybe. The device is now always on and will not turn and you cannot get into recovery but you can reboot and get to the bootloader. At this point I tried the flash stock/unroot soft-brick feature of Wugfresh and it does not work even if I enabled Force Flash Mode.
Tried doing this thru adb but have limited adb skills and with the instructions I was following it assumed USB debugging was enabled (my device was wiped so not sure about that).
Any help will be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Going to try MSkip's toolkit to see if it helps found here: http://forum.xda-developers.com/showthread.php?t=2510913

yagermeister said:
Going to try MSkip's toolkit to see if it helps found here: http://forum.xda-developers.com/showthread.php?t=2510913
Click to expand...
Click to collapse
Goo.im that hosts Mskip's image files isn't working so can't auto or manually download everything his tool needs...ideas anyone?

Mine is also knackered, I have no write access at all to the flash memory; i've even tried the wheelie option in flatline and even that can't write to it. I get the impression that all these toolkits really do is run the flashall.batch file that's in the stock recovery downloaded from google. From reading the threads, some seem to have success after flashing dozens of times. So what I'm going to do is loop the flashall.bat and leave it repeatedly flashing for a few hours. I'd also use the second most recent stock firmware to easily avoid the 4.23 bootloader issue or do what is says in the stock flashing thread. The extracted downloaded stock roms will be in wugs program files directory, just copy fastboot/adb/ dll files from the main directory and run flashall a few times.
I downloaded MSkip's toolkit a few days ago, so its on here somewhere, But for me it just crashes, doesn't even attempted to flash. Guessing it's a complied batch file which uses fastboot/ adb, so you should be capable of doing anything that it can do.

Stuck in CWM no valid rom to flash

So I just repaired my broken screen and after booting I had an old custom rom on my Nexus so I downloaded a new rom with Gapps file. Well for some reason I decided to delete some older files, which included some older roms. Well the rom failed and now my nexus stays booted into CWM recovery. It won't let me mount the storage to add files from my computer for some reason. Also I've tried Rom toolkits and they keep getting stuck waiting for device.
There must be some easy way to ADB push some files to my download folder right?

rezistrat said:
So I just repaired my broken screen and after booting I had an old custom rom on my Nexus so I downloaded a new rom with Gapps file. Well for some reason I decided to delete some older files, which included some older roms. Well the rom failed and now my nexus stays booted into CWM recovery. It won't let me mount the storage to add files from my computer for some reason. Also I've tried Rom toolkits and they keep getting stuck waiting for device.
There must be some easy way to ADB push some files to my download folder right?
Click to expand...
Click to collapse
1) First, beware of discharging the tablet by letting it sit with either the bootloader (fastboot mode) or the custom recovery running. I will presume you can get the tablet into full-shutdown when you are not working on it... unless you say otherwise. Make sure you keep the tablet charged to prevent the situation from getting worse.
2) Your mention of "mounting" is a little bit ambiguous; but as an alternative you can put a ROM on a USB memory stick and mount it via a OTG cable. TWRP can do this; I'm not sure about CWM as I don't use it.
3) Yes you should be able to push a big ROM file via adb when a custom recovery is running.
There a a couple of things that could prevent this:
a) you don't have drivers on your Win-doze PC working correctly,
b) you have a flaky USB hardware link,
c) the ext4 filesytem which is in the userdata partition is so bolluxed up that it can't be mounted, so even if there are no problems such as (a) or (b), there is no "destination" for the ROM file to be copied to. You could try to flash a ROM directly from an OTG-mounted USB key, but it will still fail if the /data partition ca't be mounted.
Note that condition (b) above sometimes has the behavior that small files such as the bootloader or boot image can be transferred (e.g. via fastboot flash or adb push), but larger files will error out or stall. That is simply because if you have a flaky conection, the probability of failure increases in proportion to the amount of data being transferred. Sometimes these types of problems can be resolved by using a different USB port on the PC, or different data cable; other times using a different PC.
From your description it is not clear whether you have condition (a), (b) or (c) going on; please clarify.

Thanks for the reply. I used the toolkit which was awesome. Side loaded factory image and finally it worked
I somehow deleted my recovery as well so no adb but fast boot worked fine. Needless to say I thought I was bricked thank god for developers
Sent from my SPH-L900 using xda app-developers app

[Q] Stuck in recovery mode upgrading CM 10 to CM 11

I was running CyanogenMod 10.1.x versions, using ROM Manager to upgrade as new ones were available. However, when I tried to upgrade to 10.2.1 it kept rebooting every several minutes, showing the new bootup screen with the rotating arrow. I tried upgrading to version 11...M9 also with ROM Manager and now it only comes up in recovery mode (CWM v6.0.3.1). There seems to be no way to finalize the installation. I can't sideload from the PC, since, although DeviceManager shows "Google Galaxy Nexus ADB Interface," I do not see any entries in Device Management or in the Explorer, so I can't offload a full backup, nor can I use adb to sideload the new CM. I can't instal from the internal sdcard, since it starts with "...Installing /sdcard/update.zip" and then can't find it - it comes up with the "(no such file or directory)."
Since (except for Device Manager) nothing on the PC recognizes a connection with the Nexus 10, I'm pretty much out of options. I can do a complete "wipe data/factory reset" I suppose, but would like something not so drastic (given no backup). When I look at CWM's display of mounted and unmounted storage, sdcard is unmounted and won't mount. I've even done a full wipe and factory reset, with the same results.
A brand-new install of the Samsung USB Drivers 1.5.33.0 through Skip's app now results in an error message when I reattach the tablet saying the driver install failed. I still show the device in Device Manager.
I have Skip's Universal Android Toolkit v1.0.2 and it seems to recognize that a Nexus 10 is connected, but can't do anything to it (it expects you are originally booted to Android, not recovery.
This is my first Samsung device, so I'm totally unfamiliar using Odin and haven't figured out how to use it to correct the problem.
It seems that, if I can sideload a copy of CM 11, I should be okay, but all roads look closed.
Any ideas?
I'm locked in a loop.
'

Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!

Thanks - will keep trying.
demkantor said:
Third post in this thread
http://forum.xda-developers.com/showthread.php?t=2670400
Will give you instruction to fully restore, but will be worst case scenario, you will also find links to drivers that are confirmed working, may need to manually update them
So yes you are right you should want to use adb sideload to get the proper ROM on
And in the future try to not use ROM manager as issues like this happen all to often, rather just boot to recovery, wipe, flash
Your other option is an sdcard and otg cable to flash a ROM
Let me know if you get stuck, best of luck!
Click to expand...
Click to collapse
I downloaded the latest Android SDK with platform tools and put the cm zip file in the directory with adb.exe. On the tablet, in ClockworkmMod Recovery, I selected "install zip from sideload." The tablet went into sideload mode and instructed me to type "adb sideload <filename>. So I typed: "adb sideload cm-11-20140805-SNAPSHOT-M9-manta.zip" and hit the enter key. The PC reported 100% downloaded. The tablet listed:
Restarting adbd...
Finding update package...
Opening update package...
Installing update...
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I'm at least communicating between the PC and tablet, but the update is still failing. Any hope of trying to flash standard ROM, re-root, and start again?

You need to update your recovery, grab the latest TWRP or CWM .img for manta and flash in via fastboot first, then boot to new recovery then flash ROM

Thanks, I grovel at your feet!
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.

Beartooth01 said:
Thanks for the help. I ended up downloading the newest Android SDK, installing the platform-tools, and flashing the 4.4.2 factory rom. Normally, this loses all of your data (though, through carelessness I hadn't disabled autosave to the Google Cloud, so all was restored). Now I have an unrooted tab with KitKat on it, but it won't take me long to root it again and this time, I'll flash custom ROMs manually, the way I do on my other devices. Once burned...
So thanks again for the help. It did the trick.
Click to expand...
Click to collapse
Great to see @demkantor help get you back up and running ..
@Beartooth01 Can you plz add "SOLVED" to the thread title
Thx Josh