in a bad situation - Samsung Galaxy Nexus

i went to relock unroot the GN and for some reason i can only boot into fastboot mode and cwm recovery. cwm recovery says there is no files so cant do a restore. i assumed i installed the sdk files correctly bc the cmd says list of devices attached when i type adb devices. also in device manger it says adb working prperly. but when i type adb reboot bootloader in the sdk platform tools it says device not found. if this is possible to fix any ideas how? and sorry to bother you just dont know what to do

If it's saying "device not found" it sounds like a driver issue. This is a real PITA with this phone! I wish I had better advice other then to search for and keep trying different drivers. I had the same issue and kept trying different drivers, at one point I was sure I tried every driver out there and I still couldn't get it. Then I went through again installing the same exact drivers that I did before and all of the sudden one decided to work.
Sent from my Galaxy Nexus using Tapatalk

do you think its bc of i cant enable usb debbuging

If you can boot into fastboot mode and CWM you will be fine.
In CWM you could try mounting USB storage, copying over a ROM of your choosing and flash away. Not sure if this feature still works in CWM with MTP. If that doesn't work you can use fastboot to flash an official image.
If you successfully re-locked the phone then you wouldn't still have CWM.

i tried mounting storage and nothing says no files. just dont understand how it earsed every single thing expect cwm recovery. i look at the phone and it sasy fastboot command error

with fast boot still working ur fine. Find and use toolkit 2.0. If it lists ur serial number tour drivers are OK. If you start with reboot bootloader cmd it will give that error. Go straight to flashing rom. Also you cant use USB mount in CWR anymore :/
Sent from my Galaxy Nexus using xda premium

i just wanna bring it back to locked state

is there a certain toolkit i should install?

pizzaguy24 said:
is there a certain toolkit i should install?
Click to expand...
Click to collapse
Like VTR said, use toolkit 2.0 :http://forum.xda-developers.com/showthread.php?t=1400871

There is no USB mass storage in CWM. Why don't you just reflash stock images in fastboot..?

joshnichols189 said:
There is no USB mass storage in CWM. Why don't you just reflash stock images in fastboot..?
Click to expand...
Click to collapse
1. Yes, do what joshnichols said...
2. Sorry, joshnichols, but the option to mount as a storage device does actually exist in CWM - it's found in the Mounts and Storage menu
3. pizzaguy24, I recommend that you do what joshnichols said anyway, and bypass CWM
Terminators run on Android...

skynet11 said:
1. Yes, do what joshnichols said...
2. Sorry, joshnichols, but the option to mount as a storage device does actually exist in CWM - it's found in the Mounts and Storage menu
3. pizzaguy24, I recommend that you do what joshnichols said anyway, and bypass CWM
Terminators run on Android...
Click to expand...
Click to collapse
Sorry, you are correct but it does not work with the Galaxy Nexus because our phones don't support mounting USB storage.. I was thinking it might as well not be there for us

joshnichols189 said:
Sorry, you are correct but it does not work with the Galaxy Nexus because our phones don't support mounting USB storage.. I was thinking it might as well not be there for us
Click to expand...
Click to collapse
oic...
Terminators run on Android...

Related

Think I hard bricked my GNEX

I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?
chaotic646 said:
I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?
Click to expand...
Click to collapse
I'm not the guy who can tell you what you need to do, but I will tell you that I have read other posts by people in your position. There are ways to push the necessary files to your phone, either toolkits or command prompt type setups, sorry but that's all I have. Google is your friend though. Galaxy Nexus toolkit, start with that, it's around here somewhere
Sent from my Galaxy Nexus using Tapatalk 2
You cannot mount the sd on the gnex through recovery. There is no SD to mount.
To move a file to your phone you must push it with adb
adb push nameofzip /storage/sdcard0
Sent from my Nexus 7 using xda premium
El Daddy said:
You cannot mount the sd on the gnex through recovery. There is no SD to mount.
To move a file to your phone you must push it with adb
adb push nameofzip /storage/sdcard0
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
ADB wont even open up. This sucks.
chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
Click to expand...
Click to collapse
Yes, you do that on recovery mode.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
Click to expand...
Click to collapse
do it in recovery.
chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
ADB wont even open up. This sucks.
Click to expand...
Click to collapse
Have you installed adb drivers? You probably should have done this already, unless you used a toolkit to unlock and root...
To install drivers, download the naked driver located here: http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Then, follow this guide to install them correctly.http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
If they are set up correctly you will be able to push the rom to your internal storage booted in recovery with adb. A list of adb commands is here: http://forum.xda-developers.com/showthread.php?t=1812959
If you aren't comfortable with that I recommend that you flash the stock images to your phone with fastboot following this guide: http://forum.xda-developers.com/showthread.php?t=1626895
This should be all the info you need. I'll be around to answer questions you may have. Just post them here.
Good Luck.
It fails because it says Im using an insecure bootloader
chaotic646 said:
It fails because it says Im using an insecure bootloader
Click to expand...
Click to collapse
What fails and when?
El Daddy said:
What fails and when?
Click to expand...
Click to collapse
The Galaxy Nexus Toolkit, which uses adb to push files to the phone. It gets about halfway through the process then fails because it says Im using an insecure bootloader
None of the info I gave you has anything to do with the toolkit. If you want to use it I cannot help you. Sorry. If you want to read my thoughts about toolkits check my sig.
However, If you follow what I posted in post #7 I will help you though the process as long as it takes.
El Daddy said:
None of the info I gave you has anything to do with the toolkit. If you want to use it I cannot help you. Sorry. If you want to read my thoughts about toolkits check my sig.
However, If you follow what I posted in post #7 I will help you though the process as long as it takes.
Click to expand...
Click to collapse
I cant follow the guide you linked to install the drivers, because it instructs me to enable usb debugging...I have no rom installed on my phone so I cant enable it.
OK. I'm not sure if you can install the driver without debugging activated. But, I know you can install the fastboot driver when booted in the bootloader because I have done it.
1) Boot into the bootloader. (power + vol. up and down)
2) Connect to your pc
3) Open your device manager and you should see "android 1.0"
4) Right click on that and choose update driver.
5) Choose install from my computer and then install the naked driver.
6) Click done and then it should show Galaxy Nexus Bootloader Interface.
You will now be ready to flash the stock google image. Follow this guide.
You'll be up and running again. You can then flash a custom recovery and ROM if you so choose. OR just roll with stock.
chaotic646 said:
I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?
Click to expand...
Click to collapse
Use Odin bro...its in the forum
Sent from my Galaxy Nexus using xda premium
Dafuqq guys. The easiest way is flashing the stock fastboot images from google. Just flash them.in fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
I'd stick with el daddy. .he seems to be directing you in a way that gets you away from that stupid kit and you're learning the proper way.. .with adb. Next time something happens you'll be far better off.
I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.
chaotic646 said:
I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.
Click to expand...
Click to collapse
Because you're not supposed to open up adb by double clicking on it.
You're supposed to navigate to the location where it is using CMD and do commands from there.
chaotic646 said:
I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.
Click to expand...
Click to collapse
Go to the directory where you have adb.exe
Shift+Right Click the blank space (Don't click any files)
Click Open Command Prompt Here
Now you can use all the adb commands there.
Good luck
El Daddy said:
OK. I'm not sure if you can install the driver without debugging activated. But, I know you can install the fastboot driver when booted in the bootloader because I have done it.
1) Boot into the bootloader. (power + vol. up and down)
2) Connect to your pc
3) Open your device manager and you should see "android 1.0"
4) Right click on that and choose update driver.
5) Choose install from my computer and then install the naked driver.
6) Click done and then it should show Galaxy Nexus Bootloader Interface.
You will now be ready to flash the stock google image. Follow this guide.
You'll be up and running again. You can then flash a custom recovery and ROM if you so choose. OR just roll with stock.
Click to expand...
Click to collapse
You are a very patient person. I hope you help me when I get in a jam. You make these forums what they are - awesome. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2

[Soft Brick] No OS Installed

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

[Q] please help

i'm having bootloop after installing 17/02/2013 CM10.1 rom on my gsm gnex. the issues are:
1. i don't have any previous working cm10 rom saved in phone's sdcard.
2. can't get adb working, maybe because i never enabled usb debugging mode before.
fyi, i have never flashed any other roms, just CM roms. please assist..
Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.
eqjunkie829 said:
Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.
Click to expand...
Click to collapse
that requires adb (adb_sideload- correct me if i'm wrong).. my adb is not working.. can't boot to android.. can't find a way to enable usb debugging mode.. so no adb..
Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.
bodh said:
Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.
Click to expand...
Click to collapse
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
Attached is clockworkmod touch recovery for gsm galaxy nexus, maguro. Phone in bootloader mode, open a terminal, cd to directory of fastboot and where you move this file to, type fastboot devices to verify device is connected, then "fastboot boot CWMT6023.img", without the quotes of course. This will temporarily allow you to use clockworkmod recovery, and thus adb, without having it on your device once you have selected "reboot now".
And if that didn't help, try consulting http://forum.xda-developers.com/showthread.php?t=1626895, since i'm thinking you haven't used fastboot in a terminal, but only know it's 'mode', and may need help with drivers.
You also might want to consider just straight out flashing cwm recovery, since YOU NEED TO MAKE BACKUPS!
[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
sorry, i got cwm. but what does fastboot have to do with cwm? i can't use cwm to restore because files can't be sent from computer to it.
as of fastboot in terminal, it seems the phone not connected to computer. is there anything has to do with my drivers? "fastboot device" command shows <waiting for device>
I gave you that link to set up drivers more than anything else. If you already have cwm, boot to it and now you can adb push a rom.zip to your sdcard and install it, wipe caches and perhaps a factory reset [if you're changing to a different rom], OR, you can first try and wipe cache and advanced, dalvik cache to see if that fixes the bootloop.
1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM
EddyOS said:
1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM
Click to expand...
Click to collapse
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
If you think that then you have no idea on how adb works...
That is ONLY applicable when Android is running. As it's not, it's irrelevant...
[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
ADB should work in your custom recovery regardless of USB debugging being enabled or disabled.
I can't tell you how many times I have rebooted into recovery, wiped, then realized I forgot to put a file on my sdcard that I wanted to flash. I then use adb to push the file(s) from within the recovery.
Edit: I really need to refresh prior to responding.
so i can't get adb working because of the driver? thats why i got "waiting for device" when pushing file to phone?
edit: i've installed all the required drivers, it's not my 1st time doing it. MAYBE, this computer never connected to my gnex before, as i've formatted it a few days ago. So the gnex driver was not properly installed.. Is it possible?
If that version of cm 10 is for 4.2.2., then i think you may have an issue accessing adb without first getting the rsa verification, even in recovery (but im not sure). Looks like your only other option would be to fastboot flash stock images. And of course it sounds like driver issues, especially if your fastboot is not even working. Again, that link I posted will get you back up and running. http://forum.xda-developers.com/showthread.php?t=1626895

[Q] Wiped phone completely how do I install rom

I completely formatted my phone and now I am stuck because I forgot that I didnt have an sd card to back up the new rom I want to flash to so how can I move it to my phone? I connected it to a pc but it didnt recognize it
RedJack117 said:
I completely formatted my phone and now I am stuck because I forgot that I didnt have an sd card to back up the new rom I want to flash to so how can I move it to my phone? I connected it to a pc but it didnt recognize it
Click to expand...
Click to collapse
Use ADB while in a custom recovery.
cupfulloflol said:
Use ADB while in a custom recovery.
Click to expand...
Click to collapse
How do I use that?
RedJack117 said:
How do I use that?
Click to expand...
Click to collapse
There are quite a few guides on how to setup and use adb. There is an FAQ stickied on this very subforum that likely has the information you seek. adb push is the command you want to look at.
RedJack117 said:
I completely formatted my phone and now I am stuck because I forgot that I didnt have an sd card to back up the new rom I want to flash to so how can I move it to my phone? I connected it to a pc but it didnt recognize it
Click to expand...
Click to collapse
..or if you want to give a clean you can also use toolkit
hotto. said:
..or if you want to give a clean you can also use toolkit
Click to expand...
Click to collapse
Thing is it won't even recognize my phone at all... I believe drivers are installed or maybe it has to do with the fact that I can't enable us debugging cause my phone doesn't have a rom
Sent from my SGH-T999 using Tapatalk 4 Beta
If the issue is getting the new ROM on the SD card, buy/borrow a small USB adapter so you can access the SD card on the PC without using the phone.
Sent from my Galaxy Nexus using Tapatalk 2
You don't need USB debugging enabled for adb to recognize your device in recovery. USB debugging is needed for adb to work while Android is booted, but not in recovery. The drivers on the other hand, you will need to figure out why those aren't working. Once those work, your custom recovery will allow adb to function. You then can adb push the file(s) to your sdcard.
UncleMike said:
If the issue is getting the new ROM on the SD card, buy/borrow a small USB adapter so you can access the SD card on the PC without using the phone.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What adapter would be helpful in this situation? If you are talking about removing the sdcard, you realize this device doesn't have non-removable memory right?
cupfulloflol said:
You don't need USB debugging enabled for adb to recognize your device in recovery. USB debugging is needed for adb to work while Android is booted, but not in recovery. The drivers on the other hand, you will need to figure out why those aren't working. Once those work, your custom recovery will allow adb to function. You then can adb push the file(s) to your sdcard.
What adapter would be helpful in this situation? If you are talking about removing the sdcard, you realize this device doesn't have non-removable memory right?
Click to expand...
Click to collapse
Yeah im guessing its an issue with my drivers then im not not sure why
RedJack117 said:
I cant enable usb debugging because i dont have a rom to enable it...when i hit adb sideload in recovery it doesnt come up on my computer
Click to expand...
Click to collapse
You don't need USB Debugging to be on to get adb to work in your recovery. As I said previously, USB debugging only matters when you boot into the OS. You don't have an OS to boot into, and even if you did it wouldn't matter in the recovery. I have USB debugging off right now, and use adb in recovery quite often. The state of USB debugging, either on or off, isn't your issue.
ADB doesn't recognize your device because you are having driver issues. Maybe they aren't installed, aren't installed properly, or something else. Figure out what is going on with those, and adb will recognize your device in recovery. You then can use it to push the file(s) you want to flash, or use sideload.
cupfulloflol said:
You don't need USB Debugging to be on to get adb to work in your recovery. As I said previously, USB debugging only matters when you boot into the OS. You don't have an OS to boot into, and even if you did it wouldn't matter in the recovery. I have USB debugging off right now, and use adb in recovery quite often. The state of USB debugging, either on or off, isn't your issue.
ADB doesn't recognize your device because you are having driver issues. Maybe they aren't installed, aren't installed properly, or something else. Figure out what is going on with those, and adb will recognize your device in recovery. You then can use it to push the file(s) you want to flash, or use sideload.
Click to expand...
Click to collapse
Ok I got it to work thank you
RedJack117 said:
Ok I got it to work thank you
Click to expand...
Click to collapse
Why don't you flash Google's stock images ? As you did to update to 4.2.2 .
Sent from my Galaxy Nexus using xda app-developers app
because he doesnt need to.. and he doesn't know how to search... http://forum.xda-developers.com/showthread.php?t=2343269
beekay201 said:
because he doesnt need to.. and he doesn't know how to search... http://forum.xda-developers.com/showthread.php?t=2343269
Click to expand...
Click to collapse
Isn't easiest/fastest way is :-
Code:
fastboot flash system <The system image >.img
????
Sent from my Galaxy Nexus using xda app-developers app
$Parker said:
Isn't easiest/fastest way is :-
Code:
fastboot flash system <The system image >.img
????
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That would definitely be needed, if he was trying to flash Google factory images. He's trying to push a flashable ROM zip to /sdcard/, and those, as you know, are not packaged for fastboot.
a manta wrote this.

[Q] Not really bricked but bricked for the time being

Hello. I currently have 2 S4 minis (I19195). One works perfectly and is mine. I also have only one SD card. I was in the process of installing CM on the new one and I wiped the SD card by accident (it contained the CM installation and gapps package).
The SD card refuses to work with either device now and I don't have a card reader.
The device currently has no OS on it. It's got CWM working, though. I need to get it running ASAP.
Is there a way to a) fix the card or b)get the CM files on it somehow or c)install CM solely through odin?
EDIT: I should also mention it refuses to mount USB storage through CWM.
In CWM you should be able to use adb. Try using adb push to upload files from your computer to the internal sd
Whosat said:
In CWM you should be able to use adb. Try using adb push to upload files from your computer to the internal sd
Click to expand...
Click to collapse
Thanks a lot for your reply, however I can't seem to find the option for adb in CWM.
teokk1 said:
Thanks a lot for your reply, however I can't seem to find the option for adb in CWM.
Click to expand...
Click to collapse
You can either adb push a rom.zip to your internal sdcard. Or side load the zip
Sent from my Nexus 5
jd1639 said:
You can either adb push a rom.zip to your internal sdcard. Or side load the zip
Sent from my Nexus 5
Click to expand...
Click to collapse
The problem is I have no way to access the internal sd card (other than odin, unless that's what you meant).
Also I tried flashing stock back onto it, which failed, and now I get a screen saying "Firmware upgrade enctountered an issue. Please select recovery mode in Kies & try again." I also seem not to be able to enter into recovery anymore, just download mode.
teokk1 said:
The problem is I have no way to access the internal sd card (other than odin, unless that's what you meant).
Also I tried flashing stock back onto it, which failed, and now I get a screen saying "Firmware upgrade enctountered an issue. Please select recovery mode in Kies & try again." I also seem not to be able to enter into recovery anymore, just download mode.
Click to expand...
Click to collapse
Boot into recovery and then from a cmd prompt on your pc type adb devices. It should show your device. If it does then, adb push rom.zip /sdcard. Where rom.zip is a rom you have on your pc and can push it to your device
Sent from my Nexus 5
jd1639 said:
Boot into recovery and then from a cmd prompt on your pc type adb devices. It should show your device. If it does then, adb push rom.zip /sdcard. Where rom.zip is a rom you have on your pc and can push it to your device
Sent from my Nexus 5
Click to expand...
Click to collapse
Unfortunately I can't boot into recovery anymore. Just download mode and the stupid broken screen.
teokk1 said:
Unfortunately I can't boot into recovery anymore. Just download mode and the stupid broken screen.
Click to expand...
Click to collapse
I don't know your device well. Can you download the firmware from sammobile and flash that in Odin?
Sent from my Nexus 5
jd1639 said:
I don't know your device well. Can you download the firmware from sammobile and flash that in Odin?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yep that's exactly what I did.
Anyway, I was just about to post everything I ever did to the phone to clarify. However I figured I should flash CWM once again and maybe get that to work.
After doing that and rebooting the phone EVERYTHING works, it booted straight into the OS and I just finished installing CM which works now. I'm not even going to pretend I understand what happened (and I have a degree in computer science...). Anyway, I'm very happy it works, and thank you both so much for helping me out!
teokk1 said:
Yep that's exactly what I did.
Anyway, I was just about to post everything I ever did to the phone to clarify. However I figured I should flash CWM once again and maybe get that to work.
After doing that and rebooting the phone EVERYTHING works, it booted straight into the OS and I just finished installing CM which works now. I'm not even going to pretend I understand what happened (and I have a degree in computer science...). Anyway, I'm very happy it works, and thank you both so much for helping me out!
Click to expand...
Click to collapse
Glad you got it working again
Sent from my Nexus 5

Categories

Resources