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.
Related
I used galaxy toolkit install touch screen CWM, then log into CWM install su.zip and reboot system, next time I log in CWM, i see a X mark on android robot stomach. then I tried to flash CWM again using galaxy toolkit, now i get error code on fastboot 'FASTBOOT STATUS- download 0058d000'.
what went wrong?
citrix80 said:
I used galaxy toolkit install touch screen CWM, then log into CWM install su.zip and reboot system, next time I log in CWM, i see a X mark on android robot stomach. then I tried to flash CWM again using galaxy toolkit, now i get error code on fastboot 'FASTBOOT STATUS- download 0058d000'.
what went wrong?
Click to expand...
Click to collapse
Not sure.
Here are some suggestions:
1) Lose the toolkit and flash things manually -- it is easier to see where things go wrong if you do things step-by-step yourself.
2) Don't use the touch version of CWM -- I've seen issue with it.
I'll gladly guide you though doing it manually if you cannot figure it out.
Use my sig bud.
As far as the error, I'm not sure what that means.
Doesn't seem like a fastboot error...but rather something the toolkit is displaying.
Possibly missing the .img? Try redownloading it.
Jubakuba said:
Use my sig bud.
As far as the error, I'm not sure what that means.
Doesn't seem like a fastboot error...but rather something the toolkit is displaying.
Possibly missing the .img? Try redownloading it.
Click to expand...
Click to collapse
no, it on the phone, right on bottom of bootloader screen, not in toolkit.
this is why people shouldn't use toolkits.
try to remove battery for a few mins, plug it back it, 3bc to bootloader.
is teamwork win recovery more reliable than clockwork?
i used galaxy toolket 7 to flash teamwork recovery, i can use it immediately but after reboot, it is gone, display a android robot with ! mark on the head. same with clockwork.
what is command for manually flash recovery? team win and clockwork.
citrix80 said:
is teamwork win recovery more reliable than clockwork?
i used galaxy toolket 7 to flash teamwork recovery, i can use it immediately but after reboot, it is gone, display a android robot with ! mark on the head. same with clockwork.
what is command for manually flash recovery? team win and clockwork.
Click to expand...
Click to collapse
It is disappearing because there are two files placed on your system by an OTA update. You need to delete the two files and re-flash your custom recovery. The two files are:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
efrant said:
It is disappearing because there are two files placed on your system by an OTA update. You need to delete the two files and re-flash your custom recovery. The two files are:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
Click to expand...
Click to collapse
Delete those will cause any problems? or not able to receive future OTA updates?
how to find thos files?
citrix80 said:
Delete those will cause any problems? or not able to receive future OTA updates?
how to find thos files?
Click to expand...
Click to collapse
Nope. No problems. Those files don't exist on a stock rom. Ota updates place them there.
Use a file explorer with root access, or via adb.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Nope. No problems. Those files don't exist on a stock rom. Ota updates place them there.
Use a file explorer with root access, or via adb.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
ok. it worked. Thanks.
I also found error code in fastboot is caused by PdaNet, I installed it from rooting guide. I closed the running pdanet then error code went away. don't know why.
citrix80 said:
ok. it worked. Thanks.
I also found error code in fastboot is caused by PdaNet, I installed it from rooting guide. I closed the running pdanet then error code went away. don't know why.
Click to expand...
Click to collapse
This is why I always recommend to uninstall all old drivers and use 1wayjonny's naked drivers. The are far better than anything else, and you don't have to install third-party software like pdanet just to get drivers.
Sent from my Galaxy Nexus using Tapatalk 2
Well, here's a suggestion;
Try to stay calm, and not to freak, when freaking, people temt to make things worse, by flashing unneccessary stuff, downloadig programs, etc. ...
Try to flash things manually, first bootloader, radio, boot, system then recovery.
If you still get the error code, try using Odin mode.
Worse-case scenario: You maybe need to JTAG it. But that is only in WORST-CASE!
You could also contact Google, see if they know what to do (Which they probably would, because they wrote the program/s)
efrant said:
This is why I always recommend to uninstall all old drivers and use 1wayjonny's naked drivers. The are far better than anything else, and you don't have to install third-party software like pdanet just to get drivers.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I downloaded 1wayjonny's naked drivers. how to install it?
citrix80 said:
I downloaded 1wayjonny's naked drivers. how to install it?
Click to expand...
Click to collapse
The driver has to install twice - once when your device is booted normally, and once when your device is booted in fastboot mode. But before you install, you have to remove the previous drivers, both in fastboot mode and in normal boot.
Uninstall all old drivers
1) Open Device Manager on you PC;
2) Plug your phone to your PC (when your device is booted normally);
3) Make sure that (on your phone), that you have USB Debugging enabled in Settings;
4) Uninstall anything you see in device manager related to Android, by right-clicking on whatever the item is and clicking uninstall;
5) Unplug your phone;
6) Reboot your phone in fastboot mode;
7) Plug your phone to your PC;
8) Uninstall anything you see in device manager related to Android, by right-clicking on whatever the item is and clicking uninstall;
9) Reboot your PC;
Install 1wayjonny's drivers
1) Open Device Manager on you PC;
2) Plug your phone to your PC (when your device is booted normally);
3) Make sure that (on your phone), that you have USB Debugging enabled in Settings;
4) You may see a prompt to install drivers. If you do, select manual install (or whatever the option is called) and navigate to the folder where you extracted 1wayjonny's drivers and select the file (can't remember the name off-hand);
5) Unplug your phone;
6) Reboot your phone in fastboot mode;
7) Plug your phone to your PC;
8) You may see a prompt to install drivers. If you do, select manual install (or whatever the option is called) and navigate to the folder where you extracted 1wayjonny's drivers and select the file (can't remember the name off-hand);
9) Reboot your PC.
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
closed
Read this whole thread. THE WHOLE THING. Preferably thoroughly.
edited
AJThePwnapple said:
Even though I have a factory cable, do you want me to go into fastboot using your method?
I tried flashing the images but my computer doesn't recognize the device (can't install otter2-prod-04) and stays at <waiting for device>. Will it be different using your method?
Sorry if I come off a bit noobish, I'm brand new to this.
Click to expand...
Click to collapse
you need the drivers (should have been mentioned on that thread.)
If you have a fbcable, use it. on windows, device manager, uninstall the current driver if there is any, and use KFU to install the fastboot driver. (only use kfu for the driver, don't do anything else.)
Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.
AJThePwnapple said:
Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.
Click to expand...
Click to collapse
No problem, i'm happy to help
I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC
Same here...
obsolete1 said:
I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC
Click to expand...
Click to collapse
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...
yudanjah said:
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...
Click to expand...
Click to collapse
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.
melvsmis ster said:
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.
Click to expand...
Click to collapse
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck
gnandez said:
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck
Click to expand...
Click to collapse
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr then plug device to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?
melvsmeister said:
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr tn plug devicle to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?
Click to expand...
Click to collapse
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help
gnandez said:
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help
Click to expand...
Click to collapse
I guess I'm missing some steps here or maybe I need to do something to make it work since my adb is not detected in TWRP but I can have it if I let it boot to blue kindle logo. I'm still having a hard time in pushing ROM due to "No space left on device" error and even though I can push gapps I can't find it in TWRP. I'll just wait for someone who might had the same issue and have other solution to resolve this problem. Thanks for your help!:good:
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
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Potetsjokolade said:
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Click to expand...
Click to collapse
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Username invalid said:
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Click to expand...
Click to collapse
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Potetsjokolade said:
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
Click to expand...
Click to collapse
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
bananagranola said:
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
Click to expand...
Click to collapse
Tried both manually with adb, and with WugFresh toolkit. I got WugFresh to run TWRP temporarily.
Potetsjokolade said:
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Click to expand...
Click to collapse
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
How can I do that when my N7 does not show up on
adb devices
Click to expand...
Click to collapse
Getting "waiting for device"
Potetsjokolade said:
How can I do that when my N7 does not show up on
Click to expand...
Click to collapse
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Username invalid said:
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Click to expand...
Click to collapse
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Potetsjokolade said:
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Click to expand...
Click to collapse
openrecovery-twrp-2.6.3.0-flo.img is for the WiFi model. TWRP for the LTE model is openrecovery-twrp-2.6.3.0-deb.img.
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
EDIT: Nevermind that stupid question
Potetsjokolade said:
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
Click to expand...
Click to collapse
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Username invalid said:
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Click to expand...
Click to collapse
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Potetsjokolade said:
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Click to expand...
Click to collapse
What do you see if your computer Device Manager with USB Debugging on?
Username invalid said:
What do you see if your computer Device Manager with USB Debugging on?
Click to expand...
Click to collapse
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Potetsjokolade said:
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Click to expand...
Click to collapse
I've never had that problem so I can't speak from experience.
http://forum.xda-developers.com/showthread.php?t=2428061&highlight=mtp
http://forum.xda-developers.com/showthread.php?p=44219641#post44219641