i wiped my cache partition on my gnex in cwm... which then got me into a bootloop. now whenever i hit recovery it goes to twrp and i accidently wiped my system on it. now it cant connect to the computer, my nexus rootkit doesnt detect an adb device and i do not have a backup or rom on my sdcard. my fastboot is working and whenever i boot it normally it is stuck at the google screen with an unlocked bootloader symbol. PLS HELP! thx in advance.
use the adb sideload option in twrp to put a rom into your storage via adb, so you can flash it. dont use the toolkit, use adb from your computer. the command is shown on the screen when you enable the adb sideload option.
Related
So I wanted to flash CarbonRom on my phone, but wanted to do a complete wipe of everything (pictures, music, etc) and then push the rom via adb but I ran into a problem.
So I booted into cwm (v6.0.3.1) did wipe data/factory reset, wipe cache partition, in mounts and storage I did format sdcard, format system, format cache, format data and /data/media (/sdcard), then wipe dalvik cache, and fix permissions. After that I opened up the GNex Toolkit v11.1.0 and entered push files to device, then it said “the toolkit will check for insecure boot.img” It asked am I using a custom rom or insecure boot.img I said no, it booted into fastboot and loaded boot.img then loaded back into cwm and then asked me to select file, I entered carbon* set the location, then about 20 seconds later said “An Error Occurred. You are not using an Insecure Boot Image”
I also tried this, unzipped CarbonRom and copy/pasted boot.img into sdk/platform-tools, then held down shift opened command prompt typed in fastboot devices, my device showed up, then typed in fastboot flash boot boot.img then booted into cwm, and tried to push files again through the GNex toolkit and the same thing happened “An Error Occurred. You are not using an Insecure Boot Image” I also tried this with another Rom (Vanilla RootBox) but got the same error.
I finally tried this, went to My Computer, Local Disk (C: Drive) Galaxy Nexus Toolkit, root, copy/pasted boot-insecure-jdq39-toro.img to sdk/platform-tools, typed in fastboot flash boot boot-insecure-jdq39-toro.img, then went into gnex toolkit and tried the push file and got the same error. I realize I could do adb push in sdk/platform-tools but I’m new to command lines and felt more comfortable using the toolkit.
I think there must be an easier way to do this. Before thinking of adb push to load the rom I was hoping that maybe there was someway that I could wipe everything and then mount my phone as a storage device and just drag and drop the rom and gapps onto my device and then install the zip from sdcard, but then I got this whole boot.img thing (I don’t know what it is) so my plan of dragging and dropping probably wouldn’t have worked. or maybe it would have? is it possible to do that CWM or TWRP? If so what would happen to the boot.img step?
I’m all out of ideas as to what to do next. Any help/advice is greatly appreciated! Thank you
why are you using a toolkit? it did nothing for you
1) you will never be able to mount your phone, so dont even bother.
2) adb push a rom to your phone or adb sideload it.
3) STOP USING A TOOLKIT
Zepius said:
why are you using a toolkit? it did nothing for you
1) you will never be able to mount your phone, so dont even bother.
2) adb push a rom to your phone or adb sideload it.
3) STOP USING A TOOLKIT
Click to expand...
Click to collapse
Thank you so much! I stopped using the toolkit and just pushed it via adb with command prompt in sdk/platform-tools and it worked!
However next time if I want to flash a rom and do a full wipe of my phone will I have to flash the boot.img via fastboot (taken from the rom) & then push the rom via adb? (sdk/platform-tools) or just push via adb and do nothing to the boot.img ? I'm assuming do nothing wtth boot.img and that it was just the toolkit that was giving me that strange error, is this correct?
Thanks, again
I tried to root my tablet and after I installed TWRP, my friend wiped the device by accident including the system which leaves me without an OS.
We cannot access the recovery mode and we are stuck at the fastboot mode. The tablet also does not show up on the computer when plugged in via USB. Anyone know the solution?
http://techerrata.com/browse/twrp2/flo
fastboot erase recovery
fastboot flash recovery openrecovery-twrp-2.7.1.1-flo.img
And then flash anything you want.
Or use Toolkit http://www.wugfresh.com/nrt/
Check soft bricked/bootloop and "flash to stock + unroot"
I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent
I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.
Hi all.
After OTA upgrade to android 6 of unlocked unrooted nexus 7 2013 WiFi i decided to unlock and install twrp.
I used adb and fastboot to flash version 2.8.7.
It went smooth but after reboot to recovery, twrp shell returns "can't mount *" for all partitions. And the device is bootlooping into this state (unless I boot into bootloader).
The worst part is that my pc wont recognise the tablet when connected. Adb devices returns an empty list. So i cant even flash stock recovery or do anything uing adb/fastboot.
HELP!!!!
[solved] falshed factory image manually using fastboot
It seems fastboot recognized the device while adb/pc couldn't.
I downloaded Android 6 factory image from google and flashed-all that.
Just updating in case some other noob who doesn't fully understand adb/fastboot relations.