Develop Bugs

Help, soft bricked my device.

I was attempting to unlock/root and long story short, now I have TWRP installed, and I can get to FASTBOOT but if i try to boot normally I get the Nexus logo, and no further. When I unlocked, I installed TWRP then loaded it. After leaving TWRP it said 'Seems you are not rooted, want to root"? or something to that effect. I clicked YES and now I'm stuck. Since I had just unlocked it, it *should* have reset my entire device(which was all stock anyway) so I am not sure what went wrong. I have been trying everything I know but I'm now out of ideas. Would appreciate any help. I see now that the version of SuperSu that it would have pushed would have been wrong, would that be preventing the tablet from booting?

If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app

ronni.rasmussen said:
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.

Landara said:
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Click to expand...
Click to collapse
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app

ronni.rasmussen said:
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.

Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app

Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
I would suggest you just restore your N7 back to stock. No need for root yet, seriously! But this should help get you going in the right direction.
Power it off completely. Hold Power + Volume down until it boots into the bootloader. Run the following commands:
fastboot devices (to confirm you are connected)
fastboot flash recovery recovery.img
If you haven't unlocked your N7 yet, run fastboot oem unlock first.

ronni.rasmussen said:
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.

Landara said:
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Click to expand...
Click to collapse
Start over by downloading recovery, Superuser and a clean stock rom image.
But before that you could try to reset all data in recovery (factory reset) and cache if you haven't tried.

http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!

Landara said:
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Click to expand...
Click to collapse
Super

Help! Have I screwed up my bootloader?

So in the rush to get CyanogenMod installed on my newly-S-Offed phone, I downloaded CWM from the appstore and started looking through the various devices to flash ClockWorkMod Recovery to. I selected the vanilla HTC One, not the verizon-specific model. I have not yet rebooted my phone yet, but I am worried that doing so will brick the phone since I technically don't have the right bootloader. Looking through CWM's list on my phone, there is not a verizon-specific model bootloader. There is one on Cyanogen's site (can't post the link due to XDA restrictions), but it appears to involve rebooting the phone. How should I go about safely flashing a good bootloader onto my phone?

ab2 said:
So in the rush to get CyanogenMod installed on my newly-S-Offed phone, I downloaded CWM from the appstore and started looking through the various devices to flash ClockWorkMod Recovery to. I selected the vanilla HTC One, not the verizon-specific model. I have not yet rebooted my phone yet, but I am worried that doing so will brick the phone since I technically don't have the right bootloader. Looking through CWM's list on my phone, there is not a verizon-specific model bootloader. There is one on Cyanogen's site (can't post the link due to XDA restrictions), but it appears to involve rebooting the phone. How should I go about safely flashing a good bootloader onto my phone?
Click to expand...
Click to collapse
CWM is a custom recovery, not bootloader. Download your choice of CWM or TWRP, reboot into the bootloader and use Fastboot to flash it.

NotATreoFan said:
CWM is a custom recovery, not bootloader. Download your choice of CWM or TWRP, reboot into the bootloader and use Fastboot to flash it.
Click to expand...
Click to collapse
I am referring to ROM Manager from the android app store. When you bring it up it asks you to flash your bootloader. The bootloader I selected was the one for the Vanilla HTC One.

I don't use ROM Manager, but I just installed it on my phone. The prompts all refer to recovery, and make no mention of bootloader. See below.
Sent from my HTC6500LVW using Tapatalk

ab2 said:
I am referring to ROM Manager from the android app store. When you bring it up it asks you to flash your bootloader. The bootloader I selected was the one for the Vanilla HTC One.
Click to expand...
Click to collapse
Its most likely referring to the recovery, not the bootloader; Assuming you're root, Rom Manager is there to flash custom ROMS and custom recoveries. I don't think you'll have bricked your phone if you installed a bad recovery, but I think your best bet would be install a compatible one manually.
SO pick a thread and follow the directions under installation:
http://forum.xda-developers.com/showthread.php?t=2416273 CWM
http://forum.xda-developers.com/showthread.php?t=2416431 TWRP
i'd pick twrp

Well my phone will reboot safely, which is good.
However, rebooting into fastboot or recovery just reboots into normal mode. Recovery will say the first time that it's going into recovery, but will reboot again and go into normal.
Thoughts?

Success! I just had to keep scrolling. there was a version in Rom Manager, all the way down at the bottom under "m7vzw." Flashing that did the trick.
Thanks for the help.
Cheers.

ab2 said:
Well my phone will reboot safely, which is good.
However, rebooting into fastboot or recovery just reboots into normal mode. Recovery will say the first time that it's going into recovery, but will reboot again and go into normal.
Thoughts?
Click to expand...
Click to collapse
The S-Off exploit removes stock recovery, so it will go nowhere until you flash CWM or TWRP. Fastboot will work regardless.
Sent from my HTC6500LVW using Tapatalk

ab2 said:
Success! I just had to keep scrolling. there was a version in Rom Manager, all the way down at the bottom under "m7vzw." Flashing that did the trick.
Thanks for the help.
Cheers.
Click to expand...
Click to collapse
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?

I've never used that command personally. I have Quick Boot (Reboot) from the market and use it for getting into recovery and fastboot from Android.
Sent from my HTC6500LVW using Tapatalk

ab2 said:
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
Click to expand...
Click to collapse
Do you have fastboot unchecked under power settings? Phone doesn't totally reboot with that checked.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

ab2 said:
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
Click to expand...
Click to collapse
adb reboot recovery = takes you to recovery
adb reboot bootloader = takes you to fastboot/booloader
I don't believe adb reboot fastboot is a command, so it just does adb reboot

[Q]How to root and unlock the latest build

So I just picked up this device couple days ago. It's running 4.4.2
This has surely been asked before but how do I root this build? I only found TUTs for 4.3 here on xda
Thanks
PS. This is my first nexus device
//Sent from somewhere in your house

Wug's Nexus Root Toolkit v1.8.2
http://forum.xda-developers.com/showthread.php?t=2389107

lzzar said:
So I just picked up this device couple days ago. It's running 4.4.2
This has surely been asked before but how do I root this build? I only found TUTs for 4.3 here on xda
Thanks
PS. This is my first nexus device
//Sent from somewhere in your house
Click to expand...
Click to collapse
Fastboot commands to unlock bootloader and install TWRP. Then flash a root zip.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
Fastboot commands to unlock bootloader and install TWRP. Then flash a root zip.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which command is to unlock the bootloader?
//Sent from somewhere in your house

lzzar said:
Which command is to unlock the bootloader?
//Sent from somewhere in your house
Click to expand...
Click to collapse
fastboot oem unlock

okay so I unlocked the bootloader and flashed recovery. I can boot normally but not into recovery. it gives me the android with the red triangle.
I know the BL is unlocked cause I see the lock symbol at the Google screen
I tried both cwm and twrp
Help?

lzzar said:
okay so I unlocked the bootloader and flashed recovery. I can boot normally but not into recovery. it gives me the android with the red triangle.
I know the BL is unlocked cause I see the lock symbol at the Google screen
I tried both cwm and twrp
Help?
Click to expand...
Click to collapse
It sounds like you still have the stock recovery installed instead of the custom one you're trying to flash. What command are you using to flash the custom recovery? It should be:
fastboot flash recovery [insert recovery filename here].img
Then, use the volume buttons to boot into recovery from the bootloader. Your custom recovery should boot up.

Yeah I used that command. I have used it before on my Optimus 3D
//Sent from somewhere in your house

lzzar said:
Yeah I used that command. I have used it before on my Optimus 3D
//Sent from somewhere in your house
Click to expand...
Click to collapse
Are you using the proper TWRP? You may try the command again.
Edit: In order to flash you have to CD from a folder containing adb.exe and fastboot.exe. Otherwise nothing will flash. Download this folder https://docs.google.com/file/d/0B_nizg6yUZ0NbWNvZHFMR1h6LVE/preview?pli=1 and Stick TWRP in the folder. That folder was put together by Rootjunky.com http://m.youtube.com/watch?v=6k4rCaMPSQ8
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

Nevermind guys, I got it working! !
Changed a little stuff (usb port and cable, wiped data before flashing)
//Sent from somewhere in your house

@lzzar Glad you got it figured out.
Short story for anyone who might find this thread after seeing the Red Triangle.
I saw an article on Android Police that there was 32gb refurbs for sale for $170. So, clearly we (XDA members) are not the same as normal users when it comes to troubleshooting and fixing problems. So, I bought my 2 sons 1 each and my wife 1 as well. While my sons are very young (single digit ages), I've taught them how to run code. The N7's arrived yesterday and after they went to bed, I fired up the computer and had all 3 tabs going at once updating from 4.3 to 4.4.2, charging, downloading,....
Unlocked all 3 Bl's and proceeded to install TWRP and ROM/Kernels. Point to remember is that I had too many things going on at once. On the very first recovery.img flash, I got the laying down android with red triangle. Flashed the recovery.img again and again the red triangle, all the while I was downloading ROMs and Kernels on my PC.
Then I realized what I was doing wrong. After flashing the recovery.img, I booted into the OS, then powered off and used the key combo to boot into recovery. Wrong!! What step did I miss? After flashing fastboot flash recovery recovery.img, I had forgotten to Volume up and boot into recovery from straight from there.
Once I realized my blunder, I was much happier. After that, it took me under an hour to install recoveries on all 3, flash ROMs and Franco r13, boot and reflashed SuperSU. Too many things going on at once and maybe a few too many drinks as well.

Yes, the exact same mistake with booting into OS after flashing was what I did too
//Sent from somewhere in your house

Bricked Nexus 7 while installing Lollipop - fastboot kinda works

Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.

Just restart device to bootloader, unpack official Lollipop image and run flash-all.bat within directory with fastboot.
It's very difficult to hard brick..

kuba9519 said:
Fastboot works, but adb doesn't see my device now.
Click to expand...
Click to collapse
FWIW adb only works when booted into Android. Fastboot only works in the bootloader.

kuba9519 said:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Click to expand...
Click to collapse
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now

Nexus still in mortal peril
GalaxySN00B:0 said:
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Click to expand...
Click to collapse
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?

This shows how to get to recovery mode from the dead Android screen http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/
Sent from my XT1080 using XDA Free mobile app

atrielienz said:
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
Click to expand...
Click to collapse
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!

DMF1977 said:
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
Click to expand...
Click to collapse
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.

Use wugs but make sure you tick tablet is in bootloop, worked for me.

atrielienz said:
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Click to expand...
Click to collapse
U can't boot in to android, but u did state earlier that u can boot to the bootloader, and that it was unlocked, so its definitely not hard bricked!

Bootloop and corrupted recovery

So I got an adapter (Finally) for my nexus 5x. Went home and got the WugFresh nexus toolkit. Made a backup, and things were going fine, and then hit root and install twrp. It installed and booted into twrp, and it gave me the not rooted message and rooted me. I restored the backup. So I rebooted it, saw it was doing the boot animation, and came back this morning to it being dead (I had it plugged into my desktop, thought it wouldn't have lost more than 1% of battery when I woke up). I tried booting it up, and it was booting forever and I concluded was bootlooped. Now, when I try to boot into recovery, I get the little android guy dead with the red triangle on top of him. Please help, I'm 14 and don't really know what to do because all my previous rootings went fine. Thanks!

You are on stock recovery. Flash TWRP if you want custom recovery and flash/wipe, or use the factory images to go back to stock. Any experience with adb and fastboot? I'd recommend using fastboot so you have an idea of what's going on and understand how to fix your phone in the future.

Keithn said:
You are on stock recovery. Flash TWRP if you want custom recovery and flash/wipe, or use the factory images to go back to stock. Any experience with adb and fastboot? I'd recommend using fastboot so you have an idea of what's going on and understand how to fix your phone in the future.
Click to expand...
Click to collapse
I know fully well about adb and fastboot. I've rooted all my phones before this manually via them, and i just tried the toolkit because a friend referred it to me. Like i mentioned before i'm in a bootloop and i have no access to it in adb. It just doesn't get recognized.

Hold power + volume down till you boot into the bootloader. Flash away.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Hold power + volume down till you boot into the bootloader. Flash away.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
yeah when i try and boot into recovery is when i get the red triangle above the android guy. there is literally no recovery there. Otherwise, yeah i would flash the firmware

Help!!! My Nexus device is totally messed up. It has ______ problem. What do I do?? @ wugfresh.com since you're already using that toolkit.
if your pc/NRT doesn't recognize your phone check the drivers and consider reinstalling them (the toolkit apparently has an option for that as well). also try playing around with the rotation of your adapter/cable. yes, usb c is supposed to work both ways, but some (cheap) cables seems to have different properties depending on the rotation.

Kevinisyoung said:
yeah when i try and boot into recovery is when i get the red triangle above the android guy. there is literally no recovery there. Otherwise, yeah i would flash the firmware
Click to expand...
Click to collapse
There is, its just the stock recovery. Go to the bootloader and flash TWRP using fastboot. If you have driver issues you might have to manually select the driver I normally have to the first time.