Develop Bugs

[Q] Semi-bricked Nexus and not sure what to do

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.

[Q] Stuck on flashing

I accidentally deleted the files inside internal storage via TWRP->Delete Internal Storage. And voila!
I already used 1-click restore and I got stuck at sending 'system' for 3hrs++ and also tried NRT Flash Stock + Unroot mode and also stuck at flashing.
What else can I do?

ren_sk8er said:
I accidentally deleted the files inside internal storage via TWRP->Delete Internal Storage. And voila!
I already used 1-click restore and I got stuck at sending 'system' for 3hrs++ and also tried NRT Flash Stock + Unroot mode and also stuck at flashing.
What else can I do?
Click to expand...
Click to collapse
Try using ADB Sideload. (Google it please). It should work with your problem as long as you have the drivers on your computer and ADB installed.

thor6577 said:
Try using ADB Sideload. (Google it please). It should work with your problem as long as you have the drivers on your computer and ADB installed.
Click to expand...
Click to collapse
What will i put on the ADB Sideload? i already have the stock google factory image. What should I put there? thanks!

ren_sk8er said:
What will i put on the ADB Sideload? i already have the stock google factory image. What should I put there? thanks!
Click to expand...
Click to collapse
Here is a guide that sfhub posted on how to use ADB sideload for stock 4.3 flo ROM JSS15Q version (latest).
http://forum.xda-developers.com/showthread.php?p=44882205#post44882205
Follow the instructions on there and you should be fine

thor6577 said:
Here is a guide that sfhub posted on how to use ADB sideload for stock 4.3 flo ROM JSS15Q version (latest).
http://forum.xda-developers.com/showthread.php?p=44882205#post44882205
Follow the instructions on there and you should be fine
Click to expand...
Click to collapse
I still have a problem, I cannot transfer file through adb sideload(temporarily boot to TWRP using WugFresh's NRT). I think root privilege has something to do with this because when I type adb root it says locked.
Fastboot is not also my option now. because I'm stuck at sending system..
--- I thought my stock recovery is not working geez. haha! I just rape the vol up and power button and the wild stock recovery appeared! yeaah! I'm now sending update.zip via adb sideload. after 2 days!!!! yeaah!

ren_sk8er said:
I still have a problem, I cannot transfer file through adb sideload(temporarily boot to TWRP using WugFresh's NRT). I think root privilege has something to do with this because when I type adb root it says locked.
Fastboot is not also my option now. because I'm stuck at sending system..
--- I thought my stock recovery is not working geez. haha! I just rape the vol up and power button and the wild stock recovery appeared! yeaah! I'm now sending update.zip via adb sideload. after 2 days!!!! yeaah!
Click to expand...
Click to collapse
Arrggh. ADB Sideload sending always stops at 58%. Any tips?

FINALLY! After !()#@()# years.;D haha! I've updated to stock via ADB Sideload with the right OEM USB Cable. Yeaah!:>

[Q] Am I bricked?

Please help! I am new to this and am worried I bricked my phone.
I successfully rooted my Verizon Samsung Galaxy Nexus using a toolkit. It was then working fine with 4.2.2. I wanted to install Shiny Rom 4.4.2. I thought I successfully backed up apps and data using Titanium Backup.
I successfully moved the correct zip files to my phone, and realized I needed Clockworkmod recovery. I followed a procedure to get this on my phone by using my computer's command prompt. I successfully booted into Clockworkmod recovery and followed the process of wiping data/factory reset, successfully installed radio and bootloader recommended to install with ShinyROM but got stuck and could not install the ShinyROM itself. I think it is because it requires a later version of Clockworkmod. The one I downloaded using the procedure was 5.5.0.4, but I think I need a later version. I tried following the same procedure using my computer's command prompt and it got stuck at "waiting for device". I cannot get out of Clockworkmod recovery now (even battery pull, etc.). I then found some threads saying I need to restore my old ROM first. (I think) the only ROM on my phone is ShinyROM. I am stuck and stressed out because I do not know of a way of "pushing" the new version of Clockworkmod to my phone.
Can I fix this, or do I need to start shopping?

[email protected] said:
Please help! I am new to this and am worried I bricked my phone.
Can I fix this, or do I need to start shopping?
Click to expand...
Click to collapse
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?

memaro_maro said:
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?
Click to expand...
Click to collapse
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.

[email protected] said:
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.
Click to expand...
Click to collapse
set up fastboot and flash twrp then.

xzilem said:
set up fastboot and flash twrp then.
Click to expand...
Click to collapse
Thanks. I found another thread that led me to the same conclusion, except I was able to do it with CWM and fastboot the latest version using ADB sideload. I still haven't posted enough to link, but here were the details from user camblue.
"
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not" have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
"

[Q] Boot Loop and not entering recovery!

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.

Yet another OTA softbrick thread. How screwed am I?

Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about

I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...

adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.

adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...

Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient

badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...

adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery

Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!