Develop Bugs

Bricked HTC One

I have my One s-off and the other day I flashed the stock 4.3/Sense 5.0 ROM and the stock recovery thinking I would be fine to accept the OTA. Yesterday the OTA came and I accepted the download and told it to install. It got 3/4 done with the install and then threw the red exclamation mark inside of a triangle. I can not boot my phone past the HTC screen and I do not have a custom recovery installed. I can boot into the bootloader, but when I try fastboot commands my computer just says waiting for device indefinitely and makes no noise when I plug my phone in, which leads me to believe the computer isn't recognizing it. I tried preforming a factory reset, but that did not solve anything. Oddly enough, I had my phone turned off overnight, but this morning at 7am it turned itself back on and sat at the HTC screen. I had an alarm set for 7am so this gave me hope as it still remembers that.
Any advice would be much appreciated!

Same situation here. Kitkat OTA bricked my Verizon HTC one. I'm S-off/unlocked with base rom. I can get to bootloader and can run fastboot, but can't seem to be able to find RUU for Verizon HTC one. Anyone can help?

smallwei said:
Same situation here. Kitkat OTA bricked my Verizon HTC one. I'm S-off/unlocked with base rom. I can get to bootloader and can run fastboot, but can't seem to be able to find RUU for Verizon HTC one. Anyone can help?
Click to expand...
Click to collapse
I was able to get my computer to recognize my phone, flash TWRP through fastboot, and then boot into TWRP to sideload the stock 4.4.2/Sense 5.5 ROM.

Banished Angel said:
I was able to get my computer to recognize my phone, flash TWRP through fastboot, and then boot into TWRP to sideload the stock 4.4.2/Sense 5.5 ROM.
Click to expand...
Click to collapse
How did you sideload the ROM? (I have CWM recovrey... should I change to TWRP?) Can you help me out with steps you took? Thanks much!
---------- Post added at 06:53 PM ---------- Previous post was at 06:34 PM ----------
smallwei said:
How did you sideload the ROM? (I have CWM recovrey... should I change to TWRP?) Can you help me out with steps you took? Thanks much!
Click to expand...
Click to collapse
I think I got it. Here is the instruction for sideloading. Going to give it a shot now. Thanks much!
http://forum.xda-developers.com/showthread.php?t=2317986

first off. this is not a brick. Brick means the phone is a brick screen doesn't turn on cant do anything if you can get to hboot you have a chance.
im guessing it loaded everything onto you phone but hboot and the system itself. what you can do is this.
fastboot flash recovery *.img
(* cwm, twrp, phils)
fastboot reboot-bootloader
enter recovery
if you can get in recovery, flash a rom that is 4.4.2 only (in case some or all the firmware was installed)
if you cant get into recovery you will need to return the bootloader to lock status and run the RUU

I put my phone in a nice black screen of death bootloop. All because of CWMR. After 1 hr of pulling my hair out trying to get back to bootloader, I managed and flashed TWRP. After that, everything was easy as pie. I think that is the last time I use CWMR.

adb push
Dont forget that both recovery will allow adb push if you can get there.. Just adb push your zip to your m7.. On liunx it looks something like this....
Code:
[email protected] ~ $ adb devices
List of devices attached
FA395S900356 recovery
[email protected] ~ $ adb push test.zip /sdcard/0/
5358 KB/s (183834805 bytes in 33.504s)
[email protected] ~ $

zalez said:
I put my phone in a nice black screen of death bootloop. All because of CWMR. After 1 hr of pulling my hair out trying to get back to bootloader, I managed and flashed TWRP. After that, everything was easy as pie. I think that is the last time I use CWMR.
Click to expand...
Click to collapse
yeah, my One didnt like CWMR at all from day one. :crying:

Had the same issue yesterday. As described. I just a thread I posted in help just yesterday, and pulled the error from manually flashing the ota .zip with via stock recovery.
I had no solution, and just waited for Santod and flashed.
Now I also got the black screen. You can get back to boot loader, not easily, but you can.
if I have helped you please press the thanks button.

[Q] Help Unrooting!

Please don't refer me to any more threads or forums........
I'm sure this has been done and done and talked about but I've been reading the **** out of forums and comments for a few hours now and trying to unroot my Sprint LG G2.
I had it running stock like a champ. rooted it. worked great. then I was attempting to flash lollipop and it required a recovery update (No Problem) I downloaded the correct files and bam! it says your phone is not rooted this requires a root (or something like that) I was already rooted SuperSU installed and root checker said I was fine. so what the hell I swipe to root while inside recovery and it goes to some black screen with tiny text saying fastboot: processing commands and won't leave the screen. I tried booting into recovery and same thing happens. Tried to reboot normal and I'm stuck on the LG logo with my led flashing between blue and green slowly. I CAN boot into download mode and I'm following this
http://pastebin.com/WTm1xFXz
and this
http://forum.xda-developers.com/showthread.php?t=2687929
to unbrick but having this error "Failed PreviousLoad()
Did I not get the right .dll file? I doubt it cause I only saw one...or is it the wrong .tot file? there was 3 or so
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Please help!
When i'm in download mode the phone does say I am rooted. is there a way to just re-flash recovery and restore from my backups I did before all this? if I have to wipe this thing clean and start over I don't really mind I just need to get my phone back haha this is the first time this has ever happened to me and I consider myself tech savvy so idk what I did here (except re rooting in recovery like an idiot) thanks so much!

First question, is the download mode you see with a small status bar or the big one?
If you have the big one, download mode should work. The f flash software will verify the tot file. If that goes through you should be golden.
When it asked you in TWRP to root, that is a message telling you system or ROM file did not take.
If you want cm12, use zv8 tot. Root, auto-rec, update TWRP with blastgator bumped TWRP 2.5.1. Flash cm ROM or aosp, then gapps. And go

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....

Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.

I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please

sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.

This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work

emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!

Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE

Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!

It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!

Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk

One Plus 5T dead?

Hey guys, I've given up. For every step I make it gets worse.
I had rooted my OP with Magisk, and one night i decided to update my OP. I woke up and tried to turn on my OP, it went to 1+ screen as usual but then the LED went white and the screen totally blank.. I couldn't do a thing.. I decided to wipe everything on my OP with TWRP recovery mode, but it made it worse. Now when i turn it on it starts a bootloop. Recovery mode is totally gone from the phone, and my computer and ADB can't detect my OP. The only things I can do now is going into bootloader or turning it into an endless bootloop.
Can you guide me through this?

Kastholm9fem said:
Hey guys, I've given up. For every step I make it gets worse.
I had rooted my OP with Magisk, and one night i decided to update my OP. I woke up and tried to turn on my OP, it went to 1+ screen as usual but then the LED went white and the screen totally blank.. I couldn't do a thing.. I decided to wipe everything on my OP with TWRP recovery mode, but it made it worse. Now when i turn it on it starts a bootloop. Recovery mode is totally gone from the phone, and my computer and ADB can't detect my OP. The only things I can do now is going into bootloader or turning it into an endless bootloop.
Can you guide me through this?
Click to expand...
Click to collapse
Look here: https://forum.xda-developers.com/on...bricking-tool-confirmation-t3733012?nocache=1

ADB doesn't work while in the bootloader...
Might still be possible to use fastboot in bootloader mode to flash TWRP, boot to recovery, connect to a computer, transfer over a full OTA zip and flash that.
If nothing else though, the unbrick tool likely works...

Didgeridoohan said:
ADB doesn't work while in the bootloader...
Might still be possible to use fastboot in bootloader mode to flash TWRP, boot to recovery, connect to a computer, transfer over a full OTA zip and flash that.
If nothing else though, the unbrick tool likely works...
Click to expand...
Click to collapse
Probably exactly what the unbrick tool would do, except it would more than likely use stock recovery instead of TWRP.

dabistduja said:
Look here: https://forum.xda-developers.com/on...bricking-tool-confirmation-t3733012?nocache=1
Click to expand...
Click to collapse
Use this tool, it's damn easy making your OP back to original FW out of the box.

l3ones said:
Probably exactly what the unbrick tool would do, except it would more than likely use stock recovery instead of TWRP.
Click to expand...
Click to collapse
So, in other words it'd be less work using fastboot, because you'd have TWRP from the start and could put whatever ROM version you'd want on there straight away... :laugh:

Custom binary blocked by FRP.

My friend's J2 Prime (SM-G532G/DS) happened to be stucked at Security Error (blue screen), no idea how it get there. Tried to flash stock firmware. But after flashing, the phone booted back into the same blue screen, now with a line of red text at the top saying, "Custom binary blocked by FRP. (recovery. img)". Tried many different stock firmware (with 4 files) but none of them solved the problem. Can't boot into recovery, only download mode. Can someone give me detailed step by step on how to fixed this.
If it help, I'm from Malaysia. So maybe the firmware might need to be from this region. Not sure about the origin of the phone though. Also, what could be the reason for this to happen? I'm assuming root. Could it even happen on its own, I mean without rooting or flashing?

also G532G/DS - ARH1 bootloader
i've been going thru lots of ROMs (including testing Lineages), this have never happened to me before.
Flashing stock firmware thru Odin though, require OEM Unlocking ON in Developer Settings.
^ I mean, did you/your friend turn it on before flashing? if not, it actually succeeded?
Only solution might be possible:
Go to stock recovery (POWER + HOME + VOL-UP), wait for it to load, then factory reset from there.
I suppose some images might help!

I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...

JEDAlive said:
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
Click to expand...
Click to collapse
+ OEM Unlock: if disabled, Odin should've failed straight away and no reboot stuff going.
+ Can't get into recovery:
Is it true that you cannot get into recovery? If left stock, It should be an Android with spinning stuff, text is "installing update" then no command for a while ~2min, and it will go to normal recovery.
I mean, it is supposed to do "recovery" :v
+ Images: post it on Imgur (or any online image service). Copy link here, add space between "https://" and all the stuff there. Wont be considered URL i guess (havent tried)