Develop Bugs

[Q] Display Brick?

I tried to root my N7 (2013) today and i ended up with a black screen.
I used these instructions, but got a bootloop on the Nexus Logo.
http://forum.xda-developers.com/showthread.php?t=2382051
So i tried to do a factory reset via TWRP, without luck (errors in twrp)
I couldn't even mount to get an ROM on the device.
Then i tried to do a factory restore with the *.img files from:
http://forum.xda-developers.com/showthread.php?t=2381582
Still no boot (only nexus logo).
So i tried to do a factory reset via the stock recovery.
After this all i got is an black screen.
First i thougt it was hardbricked. But i recognized that the device manager from windows 7 shows the device.
could not get adb to work while it shows "Android ADB Interface"
But if i turn it off and boot with volume down pressed i can get into bootloader ("android bootloader interface" at device manager)
And then i can connect via fastboot. but still nothing on the screen...
Is there more to restore than recovery/system/boot ? any display driver or kernel, so that the screen will start working again?
Otherwise i will go to the store and get me a new one.

Have you tried to reflash twrp? Or flash cwm instead? Mine didn't want to take twrp but flashed cwm without issues.
Sent from my SCH-I535 using Tapatalk 4

If you can get into bootloader (ie. fastboot sees the device), you should be able to at least throw the stock image back on there by running the included flash-all script provided by Google.
You should be able to replace the recovery as well. TWRP2 works nicely for me. Maybe download your copy again (http://techerrata.com/browse/twrp2/flo) and check the md5 has to make sure your download is good. Then flash with "fastboot flash recovery <*.img>". From there you can then install whatever you want.
As long as you can get into the bootloader, your options are many.

i just tried the flash-all script provided by google.
But still just a black screen...
I could flash a custom recovery, but i think this would not help the display problem.
if no one else have an idea for a solution i will lock the bootloader and bring it to the store tomorrow.
edit: got a new one. already rooted and with working twrp.

kitkat rom problem - help me please - android n00b

hi, recently i decieded to install CM11 on my samsung galaxy nexus, i downloded it and then i reset facotry my phone, but when i wanted to install it from Bootloader i got an error, then i thohgt it cause of old bootloader so i wanted to update it but THE problem showed up, i cant come into my android it wont be come, please help me out

If all you did was a normal factory reset, it should boot up fine. If you did something like wiped system, then you need to get to a computer and use ADB. If you wiped system then you have nothing to boot to

i think i do that too, but i got a backup too, what is ADB, how should i use it ?

the error is: set_metadata_recursive: some change failed
E:erro in /sdcard/0/0/cm-11-20131130-UNOFFFICAL0maguro.zip
(stat7)
insstalation aborted.

the.farbod said:
i think i do that too, but i got a backup too, what is ADB, how should i use it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
If you have a backup though, why cant you just restore the backup? Can you not get into the recovery anymore?

kinda curious, OP why didnt you just wipe everything in recovery mode and flash it??
1) adb reboot bootloader
2) fastboot flash recovery ***recovery.img*** (i like to rename the image to "recovery" for the ease of my own useage)
3) press vol rocker to recovery mode and flash away!
I personally use TWRP, but a lot of people prefer CWM, they are both amazingly easy to use.
worst case, you flash the stock 4.3 image from google to get everything back on track.

[Q] can't unlock bootloader

Hey everyone,
My nexus 7 is bricked. I have tried everything now. I am trying to just unlock the bootloader now. I get this screen. It just gets stuck here. I have tried different cables, different usb ports, different computers. but maybe i should try another computer with different drivers? Not sure what to do...

wolverineclaws said:
Hey everyone,
My nexus 7 is bricked. I have tried everything now. I am trying to just unlock the bootloader now. I get this screen. It just gets stuck here. I have tried different cables, different usb ports, different computers. but maybe i should try another computer with different drivers? Not sure what to do...
Click to expand...
Click to collapse
Oh, in TWRP it says I have no OS installed and it says I have 0 mb. it just boots to google logo and does nothing.

Try this method, http://forum.xda-developers.com/showthread.php?t=2389107
Sent from my Nexus 7 2013 using Tapatalk

wolverineclaws said:
Oh, in TWRP it says I have no OS installed and it says I have 0 mb. it just boots to google logo and does nothing.
Click to expand...
Click to collapse
Can you use fastboot to flash the stock recovery? If you can, do it, and run a factory reset and cache wipe.

Aerowinder said:
Can you use fastboot to flash the stock recovery? If you can, do it, and run a factory reset and cache wipe.
Click to expand...
Click to collapse
The boot loader is locked and doesn't want to unlock. It just hangs at 'erasing userdata'.
Sent from my Nexus 5 using XDA Premium 4 mobile app

wolverineclaws said:
The boot loader is locked and doesn't want to unlock. It just hangs at 'erasing userdata'.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you still boot into TWRP after all you've tried? You could get a zip of stock recovery, flash it with TWRP, and factory reset that way. If you can't find a zip, I can make one for you.

Aerowinder said:
Can you still boot into TWRP after all you've tried? You could get a zip of stock recovery, flash it with TWRP, and factory reset that way. If you can't find a zip, I can make one for you.
Click to expand...
Click to collapse
I can still bit to twrp recovery. I couldn't find a zip recovery. I have the stock image unzipped. Can you tell me how, or possibly make it for me? Is it as simple as just zipping the recovery.img file?
Sent from my Nexus 5 using XDA Premium 4 mobile app

wolverineclaws said:
I can still bit to twrp recovery. I couldn't find a zip recovery. I have the stock image unzipped. Can you tell me how, or possibly make it for me? Is it as simple as just zipping the recovery.img file?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, but you need a little scripting also. This should work for you: https://db.tt/CVJoj5wY
Flash in TWRP, then use TWRP to reboot recovery.

Aerowinder said:
Yes, but you need a little scripting also. This should work for you: https://db.tt/CVJoj5wY
Flash in TWRP, then use TWRP to reboot recovery.
Click to expand...
Click to collapse
Thanks for all your help Aerowinder. Unfortunitely this is what it says. Well, it says successful with this in the log
Updating partition details
E: Unable to mount ' /system'
E: Unable to mount ' /cache'
E: Unable to mount ' /cache'
E: Unable to set emmc bootloader message.
E: Unable to mount ' /cache'
installing ....
checking for MD5 file...
skipping MD5 check...
Flashing Stock K)T49H Recovery...
Updating partition details...
E: Unable to mount ' /system'
E: Unable to mount ' /cache'
Then I reboot it back into recovery and it goes back to TWRP recovery...

wolverineclaws said:
Thanks for all your help Aerowinder. Unfortunitely this is what it says. Well, it says successful with this in the log
Updating partition details
E: Unable to mount ' /system'
E: Unable to mount ' /cache'
E: Unable to mount ' /cache'
E: Unable to set emmc bootloader message.
E: Unable to mount ' /cache'
installing ....
checking for MD5 file...
skipping MD5 check...
Flashing Stock K)T49H Recovery...
Updating partition details...
E: Unable to mount ' /system'
E: Unable to mount ' /cache'
Then I reboot it back into recovery and it goes back to TWRP recovery...
Click to expand...
Click to collapse
I'll be 100% honest with you, the first thing I did with both my N5 and N7 was unlock the bootloader. But, can you use fastboot to flash a stock factory image zip (link in my signature)?
If not, will it allow fastboot erase cache?
What version of TWRP are you using, and why is your bootloader locked with TWRP installed? Did you relock it?

Aerowinder said:
I'll be 100% honest with you, the first thing I did with both my N5 and N7 was unlock the bootloader. But, can you use fastboot to flash a stock factory image zip (link in my signature)?
If not, will it allow fastboot erase cache?
What version of TWRP are you using, and why is your bootloader locked with TWRP installed? Did you relock it?
Click to expand...
Click to collapse
I'm using TWRP 2.6.3.1.
I can kind of flash the stock image back. I don't think it really works though. I checked the driver under device manager. It says it is for a nexus 4.. I downloaded and installed the google driver from their site. Is there a different one I should be using?
I did relock the bootloader. I thought I had flashed back the google stock image just fine, but apparantly not. What happened was randomly yesterday the tablet was stuck at the google boot screen. I went in to recovery and it said there was no OS installed. So I figured the best thing to do was the return it to stock. It is weird because it just hangs at certain commands. Like fastboot oem unlock or fastboot format etc.... Could it be a driver thing? The tablet responds to other commands though. :/

wolverineclaws said:
I'm using TWRP 2.6.3.1.
I can kind of flash the stock image back. I don't think it really works though. I checked the driver under device manager. It says it is for a nexus 4.. I downloaded and installed the google driver from their site. Is there a different one I should be using?
I did relock the bootloader. I thought I had flashed back the google stock image just fine, but apparantly not. What happened was randomly yesterday the tablet was stuck at the google boot screen. I went in to recovery and it said there was no OS installed. So I figured the best thing to do was the return it to stock. It is weird because it just hangs at certain commands. Like fastboot oem unlock or fastboot format etc.... Could it be a driver thing? The tablet responds to other commands though. :/
Click to expand...
Click to collapse
You can try to uninstall the drivers (also tick the box in the dialog that pops up). Scan for new hardware, and keep deleting drivers until you can't anymore. Then grab the latest ones from my signature, if you didn't have them already. Mine shows up as Android Bootloader Interface. Also, make sure you're using USB 2.0 ports.

Aerowinder said:
You can try to uninstall the drivers (also tick the box in the dialog that pops up). Scan for new hardware, and keep deleting drivers until you can't anymore. Then grab the latest ones from my signature, if you didn't have them already. Mine shows up as Android Bootloader Interface. Also, make sure you're using USB 2.0 ports.
Click to expand...
Click to collapse
yeah, I tried that. I feel like I have tried everything... I'm sure if I didn't relock the bootloader things would be different. Well, I'm going to see if JTag could be able to repair it. for 50 bucks it would be worth it. Thanks for all your help though!

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!

[Q] HTC One M8 (bricked?)

Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything

thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.

I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom

thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.

thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.

Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?

thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.

Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error

Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw

thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.

Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.

@thetinyjesus You could also try this app. No PC necessary.

Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe

thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.

Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks

If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.

Okay once im back home ill show the output

Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.

Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted

Anyone?