Develop Bugs

[Q] Bricked A100

Hello everyone,
I accidentally flashed using CWM recovery the stock rom and over it the Flexreaper ROM.
Now the problem:
Booting normally: Boot verified failed
Booting recovery: Recovery verified failed
Fastboot: Yes it works, but it's locked, can't flash anything.
ADB is not available.
Any suggestions how to fix this or get a unlocked bootloader again ?
Greetings, sniperfield

sniperfield said:
Hello everyone,
I accidentally flashed using CWM recovery the stock rom and over it the Flexreaper ROM.
Now the problem:
Booting normally: Boot verified failed
Booting recovery: Recovery verified failed
Fastboot: Yes it works, but it's locked, can't flash anything.
ADB is not available.
Any suggestions how to fix this or get a unlocked bootloader again ?
Greetings, sniperfield
Click to expand...
Click to collapse
Sounds like you locked your bootloader while on a modded rom? If that is the case you hosed it, sorry to say. You need access to fast boot or adb to fix it, if you have neither its locked for good.
OK one thing, did you try booting with update.zip and holding volume down + power?
With luck it will install the stock rom so you can start over.
Tapatalked from my Galaxy S II.

pio_masaki said:
Sounds like you locked your bootloader while on a modded rom? If that is the case you hosed it, sorry to say. You need access to fast boot or adb to fix it, if you have neither its locked for good.
OK one thing, did you try booting with update.zip and holding volume down + power?
With luck it will install the stock rom so you can start over.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Yes locked bootloader + modded rom
update.zip doesn't work (how should it with a broken recovery ?)
but i which update.zip you mean exactly ?
Is there any hope with APX-Mode maybe ?

sniperfield said:
Yes locked bootloader + modded rom
update.zip doesn't work (how should it with a broken recovery ?)
but i which update.zip you mean exactly ?
Is there any hope with APX-Mode maybe ?
Click to expand...
Click to collapse
APX mode has so far proven completely useless for us, we don't have the SBK keys for our device.
The update.zip method is, partly, activated BEFORE recovery is, if you watch the bootloader text while booting up holding volume down, you'll see it look for update.zip before moving on to recovery, and TWRP and CWM don't look for it on their own, unless its something extra just on our versions of the those recoveries.
If fastboot DOES work, the only thing I can really suggest is attempt flashing CWM recovery.img, but of course, the bootloader will likely block it. You could also attempt to flash the bootloader blob again, which will accept fastboot oem unlock, but the normal method is through android's system, not fasboot.
...or hell just throw fastboot oem unlock at it anyways. If the bootloader is still the same, just locked, they may just unlock it. If the bootloader was replaced, it won't work either.

Good days;
I also have a tablet brick from yesterday. And I am very angry. Tape-worm the tablet with CWM and for supues the unblocked bootloader. Tape-worm installed this room http: // forum.xda-developers.com/showthread.php? T=1574897 and empece to having problem with CWM, since not me leia the external card SD for what not podia to do backup, or to load a new rom. at the time I put to look and lei, that was a problem probably of compatibility of the card SD or that was returning to realize again everything the process of unfreezing of bootloader. and this way I did it. again this process, which was the same that it uses previously and I me work. Http: // forum.xda-developers.com/showthread.php? T=1557445.
I restart the tablet, and from this moment, have the logo of green maple tree, and a phrase of red color that he says: " recovery verified failed .... " it does not start the tablet, and it does not also leave me to enter the recovery. if I try to enter the recovery this message goes out for me.
Erasing cache before SD update...
SD update cmd: recovery -
update_package=SDCARD:update.zip
Booting kernel recovery image
please, I am driven to despair, have tried flashear with different roms, with distitnas cards mike SD, with formats in fat, fat32 and ntfs. and do not manage to do anything. I have tried to install again everything across the PC, but the PC neither recognizes me the tablet, when I connect it to the PC, even the connection of the usb nor is heard, since this one does not manage to be ignited completely. And I am not going to take her to the SAT to whom receive from me 100 €, , Since for other 100 € mas I buy myself the new nexus. but it gives me great anger, because really I like a heap this tablet and it was going less than two weeks with her. Please, to say to me what should be, if necesitais mas information, to say it to me. Thank you very much

pio_masaki said:
APX mode has so far proven completely useless for us, we don't have the SBK keys for our device.
The update.zip method is, partly, activated BEFORE recovery is, if you watch the bootloader text while booting up holding volume down, you'll see it look for update.zip before moving on to recovery, and TWRP and CWM don't look for it on their own, unless its something extra just on our versions of the those recoveries.
If fastboot DOES work, the only thing I can really suggest is attempt flashing CWM recovery.img, but of course, the bootloader will likely block it. You could also attempt to flash the bootloader blob again, which will accept fastboot oem unlock, but the normal method is through android's system, not fasboot.
...or hell just throw fastboot oem unlock at it anyways. If the bootloader is still the same, just locked, they may just unlock it. If the bootloader was replaced, it won't work either.
Click to expand...
Click to collapse
can you please give me a exact link for a update.zip ? there are so many different versions -.-
yes bootloader blocks recovery.img flash ...
how can i to flash a bootloader blob with locked fastboot ? ;o
tried already fastboot oem unlock, does not work, bootloader seems replaced
and thank you for trying to help me, if it's really bricked, i'm going to buy a nexus tablet 7 ;D

[Q] Nexus 7 stuck at Google logo and can't unlock bootloader

Hi all
Interesting issue that I've searched here and Google for and not getting far, my searching skills may not be the best though as I'm fairly new to this.
My Nexus 7 was working fine, put it on the side, came back and it's turned off. Thinking it's flat I charge it and try to boot it with no success. Pressing the power for a while does get it to turn on but it gets as far as the Google logo and stays there.
I've factory reset it in the recovery and nothing
I've tried to flash the stock image from Google but when unlocking the bootloader it just sticks on "yes" forever and nothing happens.
What can I do at this point?
Cheers

Acksaw said:
Hi all
Interesting issue that I've searched here and Google for and not getting far, my searching skills may not be the best though as I'm fairly new to this.
My Nexus 7 was working fine, put it on the side, came back and it's turned off. Thinking it's flat I charge it and try to boot it with no success. Pressing the power for a while does get it to turn on but it gets as far as the Google logo and stays there.
I've factory reset it in the recovery and nothing
I've tried to flash the stock image from Google but when unlocking the bootloader it just sticks on "yes" forever and nothing happens.
What can I do at this point?
Cheers
Click to expand...
Click to collapse
Have you heard of Wugfresh Tool kit ? (aka Nexus Tool Kit) It is in the development section or you can google it. It is quite famous.
It will do anything actually from drivers to repair a device stuck on google logo. Just make sure you select the correct option.
You will need unlocked bootloader to flash stock images. And to do either of those, you will need drivers!
Install drivers and use it to recover your device. If you still have trouble, quote me back and I will help you to my best of ability.
Look into the forum before posting your questions. There are so many similar problems and you can easily find a solution by reading their questions and their possible solution.
Good Luck!

I'm having issues with my nexus 7 (2013). It will not boot up,it's stuck on Google logo. I am able to put in fastboot mode. I'd like to do a hard reset/wipe but I cannot enter recovery mode; it just goes to the Google logo and doesn't show me the recovery menu. I thought I could try doing it through adb but bootloader is locked. Downloaded WugFresh toolkit but it requires correct build number, which I do not know. I tried different ones but everything fails. AND USB debugging is not enabled, but I cannot do it through my tablet because it won't pass bootloop. I haven't been able to enable it remotely. So, any help with getting this tablet up and awake?! It's not rooted BTW, its running stock 6.0 marshmallow

MGreen1216 said:
... issues with my nexus 7 (2013) ... stuck on Google logo. I am able to put in fastboot mode ... doesn't show me the recovery menu ... bootloader is locked. Downloaded WugFresh toolkit but it requires correct build number, which I do not know. I tried different ones but everything fails. AND USB debugging is not enabled, but I cannot do it through my tablet because it won't pass bootloop. I haven't been able to enable it remotely. So, any help with getting this tablet up and awake?! It's not rooted BTW, its running stock 6.0 marshmallow
Click to expand...
Click to collapse
Interesting, and troubling for you, I'm sure.
-- What do you mean, in fastboot it doesn't show you the recovery menu? If you are into (more properly) bootloader mode, the Recovery option has to be there. Do you mean you just can't select it, or that it won't work when you do select it?
-- Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img".
-- Have you tried unlocking the bootloader via fastboot? Is it possible OEM Unlock is already/still enabled somehow?
-- Also.... Wug's NRT doesn't need the correct verion/build. The last option in the drop-down menu on the NRT is this: << Android *.*.* - Any Build >>
HTH

-- When i go into bootloader/fastboot mode, the option is there for recovery mode along with 'start' and 'power off',etc.. However, when I select it,it just hangs on Google logo and never shows me the Android man and recovery options.
-- Sorry, not sure what you mean by this: "Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img"."
I may need some instructions on how to do this please.
-- I have tried unlocking bootloader via WugFresh and Nexus toolkit and via adb but it hangs on erasing user data and also hangs on 'unlock bootloader's screen (left it for over 12 hrs). I doubt anything is unlocked.
--Yes, I tried the "any build" option and nothing works.
Thank you
I'm open to any suggestions.

MGreen1216 said:
--- not sure what you mean by this: "Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img"."
I may need some instructions on how to do this please.
Click to expand...
Click to collapse
Ah, right. I didn't read closely, and didn't realize you might not have used fastboot tools... and please, I'm no expert, so if I'm saying somthing inaccurate, I very much hope someone will correct me.
I'm never sure how much a poster knows, so I'm not sure if you meant you don't know fastboot commands at all, or just the specific ones I mentioned .. fastboot commands are like ADB commands, but run in the bootloader environment. We know you have fastboot commands installed and fastboot drivers installed on your computer because you have adb installed - which includes fastboot, and you said WugFresh's tool was able to run, which means you also have the right fastboot drivers (the NRT uses the same fastboot commands).
fastboot can be used to flash/install custom recovery packages, among a whole lot of other things. So what I mentioned in that command was a possible way to maybe get into a custom recovery if you have to do things like wipes or whatever, even if you can't actually fully install the custom recovery. You might need to do this stuff, if you can't unlock your bootloader and flash the whole official Google Factory Image from their website (which is what I'd try - simple instructions are right there, too).
Flashing the full factory image will wipe your device, of course, but there are simple ways around that, which you can find on this very forum. Good luck.
Let us know how you get on.
<<< Any device that's bootable at all is recoverable...... usually... >>>

[Q] Messed up while trying to root HTC Desire 816 dual sim

So today I decided to root my phone. I unlocked the bootloader by following the instructions on htcdev and it was all fine. Skip forward to when I went to flash CWM Recovery on the phone. I flash it and select recovery in the Hboot menu. After selecting it, the screen would simply go black and no buttons would respond so I was forced to remove the battery and plug it back in. After doing that, it went back into the regular OS however, it said that the software was modified. At this point I had given up on the whole rooting thing and decided just to go back to factory settings so I relock the bootloader and press the factory reset button in the HBoot menu. This however did not work because it just went to the black screen. And now I can't unlock the bootloader again because it just goes to the black screen.
So now my bootloader is locked, with no root privileges, and I can't factory reset it. :crying:
My question is that if there is a way to simply just go back to the factory settings?

cryterion said:
So today I decided to root my phone. I unlocked the bootloader by following the instructions on htcdev and it was all fine. Skip forward to when I went to flash CWM Recovery on the phone. I flash it and select recovery in the Hboot menu. After selecting it, the screen would simply go black and no buttons would respond so I was forced to remove the battery and plug it back in. After doing that, it went back into the regular OS however, it said that the software was modified. At this point I had given up on the whole rooting thing and decided just to go back to factory settings so I relock the bootloader and press the factory reset button in the HBoot menu. This however did not work because it just went to the black screen. And now I can't unlock the bootloader again because it just goes to the black screen.
So now my bootloader is locked, with no root privileges, and I can't factory reset it. :crying:
My question is that if there is a way to simply just go back to the factory settings?
Click to expand...
Click to collapse
Factory reset won't fix either the "software modified" issue or the custom recovery issue. you just need to unlock your device again using the same Unlocktoken from htcDEV and flash the right stock recovery for your to get rid of the custom recovery. but I say let the custom recovery be, It won't hurt to have it.
to get to fastboot and unlock again, if your phone boots correctly to your Rom, connect it to computer, open your command prompt in ADB/Fastboot tools, and type " adb reboot bootloader"

seekfind said:
Factory reset won't fix either the "software modified" issue or the custom recovery issue. you just need to unlock your device again using the same Unlocktoken from htcDEV and flash the right stock recovery for your to get rid of the custom recovery. but I say let the custom recovery be, It won't hurt to have it.
to get to fastboot and unlock again, if your phone boots correctly to your Rom, connect it to computer, open your command prompt in ADB/Fastboot tools, and type " adb reboot bootloader"
Click to expand...
Click to collapse
That's the thing when I try to unlock it again with the same steps in htcdev it simply goes to a black screen and won't unlock. Same thing with the custom recovery. I can't actually go into it it's just a black screen.
Also when i tried the adb reboot i just get "adb server is out of date... ADB server didn't ACK."

cryterion said:
That's the thing when I try to unlock it again with the same steps in htcdev it simply goes to a black screen and won't unlock. Same thing with the custom recovery. I can't actually go into it it's just a black screen.
Also when i tried the adb reboot i just get "adb server is out of date... ADB server didn't ACK."
Click to expand...
Click to collapse
have you checked to see if your adb works on another android device? maybe your platform tools are corrupted

seekfind said:
have you checked to see if your adb works on another android device? maybe your platform tools are corrupted
Click to expand...
Click to collapse
I'll try to re download the files again and check.
Is there any other possible reasons as to why the black screen is happening for the custom recovery?

seekfind said:
have you checked to see if your adb works on another android device? maybe your platform tools are corrupted
Click to expand...
Click to collapse
So I managed to get the adb to work and when i typed in " adb reboot bootloader" it took me to the fastboot menu.
What do I have to do from here?

Messed Up OnePlus 3 (NEED HELP PLEASE)

Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!

You should try Fastboot EDL. search Google. Good luck

scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app

Try reflashing stock firmware with fastboot.

fast69mopar said:
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Windows wont install the drivers on the thread so i cant proceed and the next available date for Oneplus tech is July 24th this is so urgent....any other options?

Nv1dia said:
Try reflashing stock firmware with fastboot.
Click to expand...
Click to collapse
I cant because says flashing isnt allowed

scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Anybody?? Please help

scottwitha5 said:
Anybody?? Please help
Click to expand...
Click to collapse
Update: I followed the Mega Unbrick Guide for a hard bricked Oneplus 3, and now instead of even starting android, this appears, and I cant get into recovery or flash anything because it isnt allowed....please help me

I think your error was to relock the bootloader because if it was still unlocked, you could still reflash the boot.img (but your relocked your bootloader)

Solving it.
Don't worry I shall help you.
This happened to me too.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
To get the drivers and adb along with twrp and root use this toolkit.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Get the Oneplus drivers through this too.
It's not very complicated but ask me for any help.
Use the Method 2 in the Mega UnBrick Guide and download the stock image on to it.
You will lose data all of it.!
Make it boot.
Then tick OEM unlocking
Unlock bootloader through the toolkit.
flash twrp and root done..!!.
You messed up when you ticked off OEM unlocking and fastbooting it.

Question Pixel 6 Pro (no root) stuck in bootloop after official Android update

Hello,
I usually come here to root my phone and choose the best ROM, but this time I'm here because of a problem with the official ROM. I did a simple OTA android update this weekend, and the phone never restarted. There was enough battery so nothing to report during the install. I'm stuck on an infinite bootloop and the recovery commands take me to a no command.
Beyond having lost all my data, I'm worried because no command is working. I have already followed all the tutorials on youtube (including the most improbable techniques of hitting the back of the smartphone or putting it in the freezer for 10min, I know it's stupid, but when you're desperate you try everything).
So I'm coming here to ask for your help, hoping that someone will give me a solution to at least flash a basic image and start over.
Regards

Thiiibs said:
Hello,
I usually come here to root my phone and choose the best ROM, but this time I'm here because of a problem with the official ROM. I did a simple OTA android update this weekend, and the phone never restarted. There was enough battery so nothing to report during the install. I'm stuck on an infinite bootloop and the recovery commands take me to a no command.
Beyond having lost all my data, I'm worried because no command is working. I have already followed all the tutorials on youtube (including the most improbable techniques of hitting the back of the smartphone or putting it in the freezer for 10min, I know it's stupid, but when you're desperate you try everything).
So I'm coming here to ask for your help, hoping that someone will give me a solution to at least flash a basic image and start over.
Regards
Click to expand...
Click to collapse
Since you can get into bootloader and it's locked, go to platform tools and unlock the bootloader. Then you can flash the factory image and proceed from there. This will wipe data.
The other image is the screen prior to entering recovery via pressing power button and vol up.

I would recommend turning on USB debugging first thing when getting any phone.
Android Flash Tool
flash.android.com

The No Command Screen is normal. You just need to press and hold the Power Button and while doing, so press and release the Volume Up key (after about 5 seconds) and then release the Power key as well. This will take you to stock recovery. From there, you could sideload the OTA package [works on a locked bootloader as well] but as already told in a post just above mine, you need to have enabled USB Debugging beforehand.

The bootloader is locked but you can access it, so go to platform tools and unlock it. After that, you can flash the factory image and carry on. It will erase all data.

To sideload an OTA in stock recovery you shouldn't need to have USB Debugging enabled. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip. I'm not aware that this has changed.
To unlock your bootloader you will need to have OEM Unlocking enabled in Developer Options beforehand.