Related
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
So I made a mistake and I tried to flash the newest aokp build 3 without a backup. I got my new phone a while back and never made a backup.
I flashed build 3 and (accidentally) some old gapps and I kept getting stuck on the Google screen.
Next I tried pushing files through the Gnex tool kit and manually through fastboot. I keep getting errors that there is no insecure boot or that the device is not connected. attempts at a temporary insecure boot on the tool kit fail.
Next I tried a wipe and then just installing build 3 without google apps so I could add the correct one after boot, but it is again stuck.
So now I'm really not sure what to do. Any suggestions?
Rule number 1 : STOP using toolkits!!
now, can you get into cwm recovery?
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
You could eithther try to flash back to stock or you could boot into TWRP & adb push a different ROM. (You did try Wipe Data / Factory Reset right?)
MK17 said:
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
Click to expand...
Click to collapse
I think what thegtfusion was trying to say was: if you wouldn't have used a toolkit in the past, you would have known how to fix your bootloop.
Buy anyway:
1) Boot into recovery and plug into your PC
2) Open a command prompt (in the folder where you have adb.exe and fastboot.exe)
3) Push the ROM (and kernel if it doesn't come with it) you want to flash to your device: adb push /path/to/ROM.zip /sdcard/
4) Reboot into fastboot mode
5) Erase your old ROM: fastboot erase system
6) Erase your old kernel: fastboot erase boot
7) Reboot into recovery
8) Wipe /data and /cache
9) Flash your ROM & kernel in recovery
10) Reboot. Done.
EDIT: Ninja'd by 3rdstring!
Screwing up is part of the learning process. It's actually a great way to learn how your phone really works.
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
MK17 said:
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
Click to expand...
Click to collapse
Try uninstalling all drivers and reinstalling them.
Sent from my Galaxy Nexus using xda premium
Drivers
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
MK17 said:
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
Click to expand...
Click to collapse
did you install android-sdk (and added adb/fastboot to your $PATH) or are you using binary versions of adb and fastboot downloaded elsewhere?
if it's the latter, commands should be run from the directory where you extracted them.
about the drivers, i think you need to go to device manager and update drivers manually to the ones you installed (refered here in the post before mine), assuming you're on windows.
sent from my i9250
You're booted into TWRP when trying adb?
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
MK17 said:
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
Click to expand...
Click to collapse
he didnt have usb debugging on.
sent from my i9250
Just for understanding, USB debugging is only activated through recovery?
It's also under settings >> developer options so you can use adb while the android is running.
3rdstring said:
It's also under settings >> developer options so you can use adb while the android is running.
Click to expand...
Click to collapse
Of course,but that is hard to get to when your phone doesn't boot
MK17 said:
Of course,but that is hard to get to when your phone doesn't boot
Click to expand...
Click to collapse
USB Debugging needs to be enabled in Android for ADB to work in Android.
CWM and TWRP have USB Debugging enabled by default, so ADB will work fine in recovery with no other action from the user.
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
Hi Guys,
I wanted to do a clean install. So,i formatted Cache, System.
But by mistake i formatted Data also.
Now the ROM zip file is also lost.
Can anybody help me as how to install a new OS now.
Cheers!!!!
Can't you mount data and enable USB storage?
Sent from my Nexus 7 using xda app-developers app
use GSM TOOLKIT
Device Driver installation is getting failed.. I am able to mount though...
Connect to a computer and paste TWRP ou CWM and a ROM.
In last case, reboot to fastboot and flash google image through Galaxy Nexus toolkit.
I am not able to connect to Computer and copy any files to Phone.. But using Toolkit i should be able to push ROM to Phone.. please correct me if i am wrong...
mac4rfree said:
I am not able to connect to Computer and copy any files to Phone.. But using Toolkit i should be able to push ROM to Phone.. please correct me if i am wrong...
Click to expand...
Click to collapse
You must flash a google image through nexus toolkit and your problem will be solved.
Nope don`t make it so complicated. Flash a rom + gapps though adb sideload.
http://teamw.in/ADBSideload
mac4rfree said:
I am not able to connect to Computer and copy any files to Phone.. But using Toolkit i should be able to push ROM to Phone.. please correct me if i am wrong...
Click to expand...
Click to collapse
Connect to the toolkit and flash a stock image. I had the same problem with you. Flashing stock image is the best option.
So do the following:
1. Download toolkit (mskip) and install drives (if not installed already)
2. Coonect your phone to a pc
3. Enter fastboot mode
4. From the toolkit choose the rom you want to flash
5. then choose the option to flash stock image (option 9 i think)
6. Sit back and relax
7. start rooting your phone again.
GOOD LUCK!:fingers-crossed:
Like most people here I also advice the same solution because this solution saved my friend who was in the same situation as you.
1. Download and install Galaxy Nexus Toolkit to PC
2. Download Galaxy Nexus Stock Factory Image from Google
3. Do the 3 finger boot (power+volume up+volume down) to get into Fastboot mode
4. Plug in phone to Pc
5. Launch Galaxy Nexus toolkit and Select the option that says extract and install stock factory image
New Problem.. My phone restarted and it went to bootloader screen.. now the GSM Tool Kit is saying "Waiting for device"... Now what to be done???
What has this got to do with Development again?
Sorry My Bad... I posted it in wrong section..
I downloaded and installled GSM Tool kit. I downloaded the Google image but when i tried to flash it is booting to bootloader screen but after that Tool kit is saying <waiting for phone>
I pushed the older zip file to sdcard using adb push command and installed it..
Please help me. I've accidentally deleted and wiped everything in my phone include rom and nand backup. Right now my phone only can boot into recovery and fastboot.
How do I transfer a zip rom into twrp?
My pc did not recognize my phone (in recovery and fastboot mode) although driver has been installed. I can't use ADB, GNex toolkit or what so ever tool. I have search in previous thread but with no solution.
Please advise.
me2kimi said:
Please help me. I've accidentally deleted and wiped everything in my phone include rom and nand backup. Right now my phone only can boot into recovery and fastboot.
How do I transfer a zip rom into twrp?
My pc did not recognize my phone (in recovery and fastboot mode) although driver has been installed. I can't use ADB, GNex toolkit or what so ever tool. I have search in previous thread but with no solution.
Please advise.
Click to expand...
Click to collapse
You will have to get the correct drivers installed on your pc. Then you can either push a rom to the sdcard with adb or use a factory image and fastboot. Installing the driver correctly is your only option.
Sent from my Galaxy Nexus using Tapatalk 2
Toolkit...
Get the fastboot drivers right and flash stock ROM..
Beamed from my Maguro
I have install the driver from toolkit. But I think its useless when my pc show no response (not detect) my phone when connected. BTW I've tried it in ubuntu and XP(installed in virtualbox).
Any other solution on how to make my pc detect the phone?
Perhaps you need to change the udev rules in Ubuntu?
SOLVED!
The culprit is micro usb cable. The cable that one I used are partially function. It can be use to charge but can't transfer data.
Change to another cable and follow the step as video tutorial below and my phone revive again. Thanks all.