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
Related
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
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.
Hello all,
My brother has been having problems with his Google Play store (force closing, etc) as well as some other Google services. He wasn't even able to actually load Play Store and browse, so to fix his problem I decided the best route would be to start clean and do a factory reset. This worked well, for about 2-3 hours until he told me he wanted me to put the Google Edition 4.3 JB ROM on his phone. (He's a hipster, trololol)
So I looked up the thread of the AOSP Google Edition 4.3 JB for his GT-I9505. Having flashed my Galaxy S3 many times with UltimaROM and various other ROMs, I figured his S4 wouldn't be much different to any of the other Galaxy devices we've had in the past. So I download TWRP, and also rooted his phone via Motochopper. Once I installed TWRP I hit wipe and wiped the data and dalvik cache. Then I installed the ROM. Few moments later and we reboot the phone.
Phone decides to go into a boot loop, so I go back into TWRP and wipe again like I would with my Galaxy S3, but still getting a boot loop.
I really should have made a back-up of his original stock ROM (I made a boo-boo, I know ) but I figured he had nothing to lose. The problem now is that I can't flash any other ROMs because normally I would just transfer the .zip's onto the phone and then install from there. He doesn't have an SD card either, and mines doesn't work anymore (water damage...).
So my question is, what other ways can I transfer .zip's onto his phone so we can flash another ROM and not let his phone be a huge expensive paper weight.
I know about ADB and I downloaded the ADT Bundle from Google's site, but I have no idea how to execute adb or fastboot. They open cmd but then immediately shutdown again after a flash of a wall of text.
I'm able to access recovery & download modes fine. I've tried "mount" but when it mounts the S4, Windows doesn't pick up on it like it would if I were to do MTP otherwise I'd be able to transfer files no problem.
Can anyone help please?
man...use PhilzRecovery and use adb to flash the rom!
Put the flashable zip in the same folder wich contains adb.
Select from PhilzRecovery "install zip from sideload"
Connect the phone to pc and in the adb window type "adb sideload ..........." (wehere "............." is the name of the flashable zip.
I restored my phone once in this way
otherwise...buy a cheam 2gb micro sd card and put the flashable zip on it.
Select install zip from sdcard and that`s it.
Or you can use adb file explorer to copy the flashable zip on internal memory
there are many solutions for your problem.
The easyest would be the one using "adb sideload"
I hope i helped you!
Have a nice day!!!
PS: to open adb window do this way "press and hold shift while click-ing right click on the folder that contains adb files"
you will get a menu containg "open command window here" and click on it!
In the windows that appears type "adb devices" just to see if the phone is correctly recognised by windows.
Remember that using Philz Recovery is the most secure way.
Twrp has some weird problems formatting data(i don`t know why)
to put the phone just boot into recovery mode and adb should recognize your phone!
http://forum.xda-developers.com/showthread.php?t=2265477 Just follow this. I guess it's a soft brick and you'll just need to flash the stock firmware.
EDIT: Seems I was wrong, but the ADB tip will come in handy though. Thanks!
Ok I think I may have bricked / soft-bricked the phone. I've tried flashing the stock ROM (different firmwares) with and without a PIT file and they all keep failing. Yet if I flash a ROM like Cyanogen Mod it'll get to the Cyanogen Mod boot screen, but then crash there?
The phone is definitely a i9505, so I can't see what the hell I'm doing wrong. :/ It was an Orange UK model, but it was factory unlocked when bought new and he's been using o2 sim's ever since.
All I do is flash .tar.md5's with Odin 3 v1.85, and then install .zip's in the recovery (Philz Recovery)
For the stock ROM I'm just flashing with Odin.
I've never had so much drama with a phone before. -__-
EDIT: Solved this on my own. Had to flash MH8 since I'm on a secured bootloader.
Thanks anyway.
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
HellaBester said:
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
Click to expand...
Click to collapse
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
osugsxr said:
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
Click to expand...
Click to collapse
Yeah I considered that but no everything is up to date. It seems more like the RSA auth fingerprint is not being recognized. Plus it does recognize the phone, it just tells me it is unauthorized.
Get back into Recovery mode and use ADB from there
votinh said:
Get back into Recovery mode and use ADB from there
Click to expand...
Click to collapse
How do I get into recovery without being able to "adb reboot recovery"?
unomicu how
Bump. Anything guys? Really struggling here....
Can you get in recovery using button combination?
votinh said:
Can you get in recovery using button combination?
Click to expand...
Click to collapse
Nope, doesn't seem like it. Though I can get into download mode no problem.
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
HellaBester said:
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
Click to expand...
Click to collapse
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
super114 said:
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
Click to expand...
Click to collapse
Heyoo, just in the last hour or so I've got it all fixed!
I did a full system, data and cache format om CWM after that there was no OS or amnything of the sort, then I was able to mount the SD and adb push cm11 + gapps-kk to the sdcard, I flashed those two zips restarted, failed, then i did a system reset (resets everything but the OS) and I popped out in CM11 with a perfectly fresh install. got all that setup and am golden now ::
Congratz
Check the .android folder
My problem started when I tried to connect another phone which happened to be the same type of phone as the previous one. Not sure if that's actually related, but my working hypothesis is that ADB gets confused in this scenario. I tried everything listed here and in many other places, and nothing seemed to work. Finally, I did this:
1. Rename .android folder in your user directory (~/username/.android on Mac OSX) to .android_bak (for safe keeping).
2. Restart the adb daemon: "adb kill-server" followed by "adb start-server"
After that, I got the authentication confirmation on the phone (don't forget that part, of course) and all was well.
These steps merely recreate the .android folder and get rid of any authentication credentials you already have. Note of course that this will impact all other phones you may be connecting.
OK guys, sorted it out.
The update file that our YotaPhone 2 is downloading to the phone, with a size of 1GB, is flashable with TWRP.
But only a very little amount of space is left after update is flashed. Only enough for SuperSU. If you want to flash XPosed too, you've to delete a file you could install from playstore for example. I've decided to kick chrome out of /system/app.
The flashable file you could find in /data/data/com.symphonyteleca.update/files
If you choose to reboot and update it is gone after reboot. Save it to another location, please
If you're phone is not downloading this bigger update, i've uploaded it to my mega cloud drive for you:
https://mega.nz/#!MtN2lLZA!SQ_QtByF1T_txqjToGMBhnNxASmxR_NoEMwiFQGhBak
Thanks for the advice. I had the same low storage issue after flashing via TWRP. Phone was very slow and couldn't install or update any apps. I had to delete the system/chrome.apk from TWRP as doing it from a rooted es explorer didn't fix the issue.
Can i put this zip on a USB stick - connect the stick to a otg cable.
boot the phone to TWRP with adb fastboot from a PC and install the zip from otg storage ?
Or there are some special steps?
std_ said:
Can i put this zip on a USB stick - connect the stick to a otg cable.
boot the phone to TWRP with adb fastboot from a PC and install the zip from otg storage ?
Or there are some special steps?
Click to expand...
Click to collapse
This should be possible.
btw. i deleted system/media/bootanimation.zip (this frees up 50MB) instead of the chrome.apk
You can replace it with a smaller one from here: http://forum.xda-developers.com/android/themes/bootanimations-50-flashable-t3059659
Yes seems i can flash it with otg but maybe something is missing from this zip as even if i write it in TWRP my phone still can't boot.
Do you know what is in emmc_appsboot.mbn from original 5.0.0-RU1.1.124.zip and how can i flash it?
I'm starting to suspect corrupted partitions or a hardware problem with the emmc memory.
std_ said:
Yes seems i can flash it with otg but maybe something is missing from this zip as even if i write it in TWRP my phone still can't boot.
Do you know what is in emmc_appsboot.mbn from original 5.0.0-RU1.1.124.zip and how can i flash it?
I'm starting to suspect corrupted partitions or a hardware problem with the emmc memory.
Click to expand...
Click to collapse
There's nothing missing in this zip. boot.img, modem, system partition image. I've flashed it from internal sd. And well booted perfectly. Is it looping? Hanging around @ bootlogo?
If it looks like it loops just wait. Complete files on phone need to be reoptimized.
Hi,
in TWRP the zip flashes for 15 sec and then if i go to Reboot - i see the warning on the top 'No OS installed are you sure you want to reboot.'
After that it just stays on 'Powered by Android' logo forever, not looping.
Even if i clear cache and Dalvik Cache and reboot still stays the same.
Both power+up and power+down just go in Downloading... so no recovery is flashed.
In "TWRP>wipe>advanced>System>Repair or change file system" it says /system ext4 size 1509MB used 1500MB free 9MB
So i guess system is flashed properly.
After successful flash of 124 RU zip via TWRP via OTG cable and USB flash drive, it was still waiting at Android logo but then just of curiosity i have tried yota flasher and it went OK.
Now android is running and it downloads update of 1GB.
Still i wish there is a low level tool like ODIN for this phone it will be easier to fix bricked phone.
Hi, I dont know too much about twrp. What do you mean by "the update file is too big and the phone cant install app updates after"? Do you mean you only had about 1.5 ish gb of free storage before installing it?
Also, is this actually an update that wont delete my data?