Related
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2
JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.
RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.
Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars
Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps
If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.
mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.
Then just use the sideload, it works quite well for me.
mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.
No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement
stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone
Hello XDA, I got my Galaxy Nexus stock and OTA upgraded it to 4.1.1 Jellybean. I unlocked and rooted the phone and while installing roms I accidentally formatted and factory reseted my phone. I can get into boot loader, and I have CWM installed. If I could just move a rom onto the phone I could boot it. Problem is I cant figure out how to. Keep in mind I am also using a mac. Can anyone help me figure out how to push a rom zip onto the sdcard? Any help would be appreciated, thanks!
Mac infos
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
Help
My ADB debugging wasnt on at the time, and now I cant push files to it, anyone have any ideas?
colinrball said:
My ADB debugging wasnt on at the time, and now I cant push files to it, anyone have any ideas?
Click to expand...
Click to collapse
You can abd push from a custom recovery
Alright so USB debugging isnt on but I can still use adb commands? How?
You have to boot into a custom recovery (CWM or TWRP) and use adb commands.
for ex. adb push NameOfRom.zip /sdcard/
I just tried that and my terminal returned
device not found
Don't mount anything don't do anything special in recovery at all.
You're booted into recovery?
Also...I found when I wasn't using naked drivers that it took ~30 seconds for ADB to actually be recognized.
Maybe wait a minute and try again.
If not unplug and plug in.
I can use fastboot commands and it it recognized in fastboot, can I flash a stock rom from this mode?
colinrball said:
I can use fastboot commands and it it recognized in fastboot, can I flash a stock rom from this mode?
Click to expand...
Click to collapse
If you're using fastboot...that means you're not in custom recovery.
Navigate to recovery in that menu.
Or use fastboot boot ______________.img to boot into a custom recovery if you have one downloaded and in your platform tools directory.
But yes, you COULD do that.
But I wouldn't yet.
You'll lose all of your data/apps/etc.
There are Google factory images for the GSM & Verizon versions
[HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock
Jubakuba said:
If you're using fastboot...that means you're not in custom recovery.
Navigate to recovery in that menu.
Or use fastboot boot ______________.img to boot into a custom recovery if you have one downloaded and in your platform tools directory.
But yes, you COULD do that.
But I wouldn't yet.
You'll lose all of your data/apps/etc.
Click to expand...
Click to collapse
There is nothing on my phone, I have CWM installed, however there are no ROMs on the sdcard to flash through CWM. How would I move a file onto my sdcard that I could flash with CWM via fast boot?
colinrball said:
There is nothing on my phone, I have CWM installed, however there are no ROMs on the sdcard to flash through CWM. How would I move a file onto my sdcard that I could flash with CWM via fast boot?
Click to expand...
Click to collapse
I've explained this process already.
Post three of my guide.
Good luck.
|
|
|
v
You don't flash fastboot images via CWM. If you have CWM installed & you're booted in to bootloader (fastboot) mode use the volume keys to reboot into recovery
Jubakuba said:
If you're using fastboot...that means you're not in custom recovery.
Navigate to recovery in that menu.
Or use fastboot boot ______________.img to boot into a custom recovery if you have one downloaded and in your platform tools directory.
But yes, you COULD do that.
But I wouldn't yet.
You'll lose all of your data/apps/etc.
Click to expand...
Click to collapse
I tried pushing a zip to the phone while using adb and a custom recovery. My terminal says it pushed the files to my SD card, however when I go to install the zip, no files appear. Even when I restart recovery there are still no zips found. Any ideas?
Thanks,
Maybe try...
adb push NameOfRom.zip /sdcard/NameOfRom.zip
or
adb push NameOfRom.zip /data/media/NameOfRom.zip
3rdstring said:
Maybe try...
adb push NameOfRom.zip /sdcard/NameOfRom.zip
or
adb push NameOfRom.zip /data/media/NameOfRom.zip
Click to expand...
Click to collapse
Its still giving me a failed message, error flashing zip
Hi everyone, i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
This evening once i installed the OTA Update for my Galaxy Nexus (which was running Android 4.2) the process failed at the end (as usual -.-) and i got stuck at bootloader.
I've wiped it completely ending up with no OS installed on it, nothing on SDCARD (Internal storage in this case).
The problem is that, i have no drivers installed on my PC for this phone.
I've already downloaded the latest version of Android 4.2 to flash (.zip), but there's no way i can transfer the file to the phone without the drivers.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Any idea of what can i do now?
I may even pay on paypal for a quick help to get my phone back on working
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
ttabbal said:
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
Click to expand...
Click to collapse
Actually i do have a custom recovery which is CMW, but i can't seem to get my internal storage mounted using i'ts options.
I will try to push the .zip using the ADB on the recovery mode.
After checking the logs i can now see :
Enable to mount /usb-otg
(Using NexusRootToolkit i just flashed TWRP as recovery mode)
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
NPasta said:
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
Click to expand...
Click to collapse
You mean besides the post right above yours?
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Click to expand...
Click to collapse
Save the pain, just flash the stock ROM from fastboot already....
Mach3.2 said:
Save the pain, just flash the stock ROM from fastboot already....
Click to expand...
Click to collapse
This. I don't see what the problem is here.
marcelloLins said:
i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Click to expand...
Click to collapse
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
help-a-noob
Having similar problem: no OS installed. Got bootloader and TWRP. adb push doesn't work: computer can't find device. how do I get to fastboot? HALP!
HALP...
That's classic..
Read this:
http://forum.xda-developers.com/showthread.php?t=1812959
Then follow this:
http://forum.xda-developers.com/showthread.php?t=1626895
gunner1937 said:
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
Click to expand...
Click to collapse
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
marcelloLins said:
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Click to expand...
Click to collapse
You are mistaken, root doesn't stop a system update. I can vouch for that myself, even though i know that it doesnt matter just from reading some people's posts around here.
You weren't exactly explicit on your first post, so I presume you didnt/dont have the correct baseband version for that specific OTA to apply. Very common.
Oh and if you've never been able to OTA update successfully, it's not "usual" for the rest of us. You should work towards becoming more verbose and objective when troubleshooting. That will make you more experienced.
Sent from my i9250
marcelloLins said:
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
Click to expand...
Click to collapse
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
dicksonjoe said:
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
Click to expand...
Click to collapse
Try installing the ADB Drivers manually in order for your PC to recognize it.
Have you tried putting it other modes such as Download Mode and check if your pc installs any driver?
You will have to ADB PUSH the OS image to your internal memory and use CW to flash the rom from the sdcard, but you will need the drivers installed or adb wont be able to see your phone
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
edgarzin said:
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
Click to expand...
Click to collapse
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
AndyYan said:
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
Click to expand...
Click to collapse
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
for example usb mount via twrp dont work for me
edgarzin said:
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
Click to expand...
Click to collapse
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
AndyYan said:
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
Thanks!! Now its working! in twrp, advanced mode, adb sideload, then i executed the command you told me!!! saved my phone
My current situation: Rooted phone with unlocked bootloader and CWM. No rom loaded on the phone. No roms on SD card. Is there anyway to flash a rom on my device in my current predicament?
Persianity said:
My current situation: Rooted phone with unlocked bootloader and CWM. No rom loaded on the phone. No roms on SD card. Is there anyway to flash a rom on my device in my current predicament?
Click to expand...
Click to collapse
I know you can do it from your computer through fastboot. Or you could mount your phone on your computer, move a ROM from the computer to the phone, and flash it from recovery.
bananagranola said:
I know you can do it from your computer through fastboot. Or you could mount your phone on your computer, move a ROM from the computer to the phone, and flash it from recovery.
Click to expand...
Click to collapse
I tried connecting it via ADB but since there is no ROM loaded on my phone, USB Debugging is inactive. Is there a way for me to connect it without enabling USB Debugging?
Boot into fastboot. ADB works there. Push your rom to /sdcard and flash it via recovery
adb push location_of_downloaded_rom /sdcard/
Click to expand...
Click to collapse
Another alternative is sideloading it if you have TWRP
Persianity said:
I tried connecting it via ADB but since there is no ROM loaded on my phone, USB Debugging is inactive. Is there a way for me to connect it without enabling USB Debugging?
Click to expand...
Click to collapse
ADB debugging option in settings only pertains to a booted Operating System
iLeopard said:
Boot into fastboot. ADB works there. Push your rom to /sdcard and flash it via recovery
Another alternative is sideloading it if you have TWRP
Click to expand...
Click to collapse
fastboot and recovery are different things
adb does not work in fastboot
fastboot does not work in recovery
adb push will work in recovery
Pirateghost said:
ADB debugging option in settings only pertains to a booted Operating System
fastboot and recovery are different things
adb does not work in fastboot
fastboot does not work in recovery
adb push will work in recovery
Click to expand...
Click to collapse
Right, once again getting terms confused. I was in the same situation last week and went in circles between fastboot and recovery and you are correct, adb push does work in recovery.
iLeopard said:
Right, once again getting terms confused. I was in the same situation last week and went in circles between fastboot and recovery and you are correct, adb push does work in recovery.
Click to expand...
Click to collapse
Thank you both for your help. I did not want to go through Odin and wipe my SD card. Love!!!!
Hi,i have read the tutorial for upgrade MM.
I have installed the driver and adb work correctly on Windows.
After reboot in recovery adb doesn't recognize s6e+.
When i push apply update from adb ,update from adb is disabled.
Thank You
A.S.LaVey said:
Hi,i have read the tutorial for upgrade MM.
I have installed the driver and adb work correctly on Windows.
After reboot in recovery adb doesn't recognize s6e+.
When i push apply update from adb ,update from adb is disabled.
Thank You
Click to expand...
Click to collapse
? When you put phone in recovery mode, did you select adb sideload option before sending file to phone? Also when you paste zip folder with firmware, did you remove .zip from the end of it?
Yes,the recovery write in the phone screen "update from ADB is disabled".
S6e+ is listed in the device AS Samsung usb composite,if i force manually "windows_ usb driver",Windows 10 don't accept.The ADB sistem work only the phone is tourned on,for me
A.S.LaVey said:
Yes,the recovery write in the phone screen "update from ADB is disabled".
S6e+ is listed in the device AS Samsung usb composite,if i force manually "windows_ usb driver",Windows 10 don't accept
Click to expand...
Click to collapse
Are you using the "15 second adb driver"?
Yes
A.S.LaVey said:
Yes
Click to expand...
Click to collapse
Not sure of what you could be doing wrong because it's compatible with Windows 10 and worked for me and others. What's you current build number?
Someone reported a similar issue on a Note 4 that related to the recovery being messed up. The only way they were able to fix it was by using ODIN to flash back to stock, booting into recovery and resetting to factory defaults, and then flashing the stock image with ODIN again. Have you tried this already? I would recommend using SmartSwitch to back up your phone and then try the ODIN, factory reset, ODIN method to see if it will restore your ADB sideload functionality.
Below is a link to the Stock image and ODIN files.
(5.1.1) 2AOJ1 ODIN files for clean flash or restoring to STOCK. Credit to: Yamaha169
https://drive.google.com/file/d/0B1dPgClURCHJTjA3dF82WnNiMzg/view
meek2100 said:
Someone reported a similar issue on a Note 4 that related to the recovery being messed up. The only way they were able to fix it was by using ODIN to flash back to stock, booting into recovery and resetting to factory defaults, and then flashing the stock image with ODIN again. Have you tried this already? I would recommend using SmartSwitch to back up your phone and then try the ODIN, factory reset, ODIN method to see if it will restore your ADB sideload functionality.
Below is a link to the Stock image and ODIN files.
(5.1.1) 2AOJ1 ODIN files for clean flash or restoring to STOCK. Credit to: Yamaha169
https://drive.google.com/file/d/0B1dPgClURCHJTjA3dF82WnNiMzg/view
Click to expand...
Click to collapse
1- Phone flashed to stock
2-Full W/Factory res.
3-Flash again
4- Reboot in recovery press" apply update from ADB " and recovery answers "update from ADB is dsabled"
the phone in recovery mode and adb mode doesn't recognised from Windows 10 V1511 (don't appear in device manager)
A.S.LaVey said:
1- Phone flashed to stock
2-Full W/Factory res.
3-Flash again
4- Reboot in recovery press" apply update from ADB " and recovery answers "update from ADB is dsabled"
the phone in recovery mode and adb mode doesn't recognised from Windows 10 V1511 (don't appear in device manager)
Click to expand...
Click to collapse
Do you have Samsung Smart Switch installed on the computer so you have Samsung's latest drivers?
I'm on Windows 10, Version 1511, Build 10586 and no matter what I try I'm unable to reproduce the situation your in. So I'm not sure what is happening.