Develop Bugs

[Q] Desire stuck in bootloader loop after hboot downgrade - HELP!!

I have serious problems with my phone that I could really use some help with as at the moment I'm completely screwed - I've already spent hours reading forums but have yet to find advice that will help. Here's whats happened:
I have an A8181 HTC Desire, and I took an OTA update yesterday that bricked my wifi. At this point I thought it would be easiest to root my phone, and after checking that my hboot version was 0.93, I read advice that said to downgrade this to 0.83, which I duly did.
Now, my phone is stuck in a bootloader loop - I get the 3 androids on skatebooards with FASTBOOT in red, and I can choose from:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I select bootloader I then get:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I can access recovery and apply update.zip roms successfully (I've only tried official HTC 2.2 roms as the phone isnt rooted), but after doing so it just goes back to the bootloader loop.
If I select FASTBOOT then I'm just back at the first screen.
I've tried clearing cache and factory reset aswell, but I still can't get past this 2 screen loop.
It's like the bootloader just can't load whatever rom is installed.
Because the phone isn't booting up, I can't use adb or any other pc tools as the device is not detected on my pc - although it does show up in device manager on windows.
I'm close to sending this back to try a warrantly claim, although I'm worried that by trying to fix this I may have invalidated this.
I'd really appreciate any help or advice as to how I can get out of this and get my stock 2.2 back.
Cheers

If your computer using windows, have you installed hboot drivers?
If you have those installed your pc should detect the phone.
unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

You shouldn't have had to downgrade your bootloader. If you can, go back to the newer.
The wifi issue, was widespread on desires, I had it also after a "pushed" update from HTC (european model, unlocked). I downloaded a stock 2.29 froyo. Had to make a gold card also. Took several tries, wipe cache, but eventually successful.
Then, I rooted, and went to CyanogenMod7 rom with clockwork recovery.

Help - Bricked M9 - yes my fault come read and laugh (and help)

Hi all, I need help with a big big problem.. Long story short, I bricked the phone. I think it's gone forever but I'm trying to ask here if someone got ideas.
First I want to say I got another M9 rooted, custom rom installed etc and got no problems, but I did it long time ago, with older methods, while now I tried using Windroid Toolkit (http://forum.xda-developers.com/showthread.php?t=2499926).
Here's the story:
- Unlocked phone via HTCdev ==> OK and everything worked;
- Downloaded and installed Windroid Toolkit, and with this installed TWRP 3.0.0 ==> OK and everything worked;
- Always via Windroid toolkit installed SuperSU ==> Windroid Toolkit sends you in recovery TWRP and you select the right supersu.zip file. Installation completed ok, but when I rebooted phone, it went in loop: showed start white screen with HTC logo and red text ("This build is for development bla bla bla") for X seconds, then reboot, and so on forever.
At that point I was still safe because I could still enter bootloader/ recovery etc, BUT... Don't ask how, don't ask why :crying: :crying: :crying: , shame on me I entered recovery / ADVANCED/ WIPE and wiped: dalvik cache, cache, system, data, internal storage... ( yes I know.. total stupidity :silly: ).
So now I am stuck at white screen with HTC logo and red text. I cannot reboot, I cannot even switch off phone keeping POWER button pressed! ("yeah you moron, you deleted os!" I know I know..).
If I connect phone to PC i hear the USB Windows sound but giving "adb devices" says "List of devices attached" like nothing is connected.
Also tried with RUU.exe but nothing (first version I found for M9, it is just to tell you it cannot see the device "Ensure your device is connected to USB").
Now I am waiting for the phone to run out of battery so I can try to VOL DOWN + POWER btn but I have no hope...
So in the end, do you have some idea?
I am very angry because I always rooted and installed custom roms, starting from HTC Diamond, always bought only HTCs and never had a problem, now I did this bulls**t with the phone I bought as gift for my father..
Thanks everyone any help will be appreciated.

try VOL UP + POWER
i start with HTC Diamond too, used one X, M7 and now M9, it really hard to brick compare to previous phone

Press VOL DOWN + POWER until you reboot to bootloader. From there reboot to recovery and flash custom rom.
fyi I always wipe dalvik cache, cache, system, data when installing custom rom coming from other roms and I don't have any issues whatsoever.

Most likely just change supersu for version 2.65. M9 is finicky about supersu.
Beamed in by telepathy.

If you were not S-OFF and wiped "real" firmware partitions like hboot, radio and so on your device is not bricked at all as the others already stated
1. Try VOL UP + POWER or VOL DOWN + Power until you reboot to Bootloader
2. Enter Download / Fastboot mode and flash new recovery using fastboot flash recovery yourRecoveryFile.zip
3. Reboot into recovery
4. adb push yourCustomRomFile.zip /sdcard
5. Flash Custom Rom
6. Full Reboot
7. Enter Recovery
8. Flash supersu 2.65 or 2.71 Beta
9. Full reboot
10 Be happy

Ok guys really thank you, so do you say its is not bricked. I will try as soon as I have time and/or battery dies (already tried with VOL DOWN + POWER but not with VOL UP + POWER ).
With my other M9to flash custom rom I had to get S-OFF with Sunshine app.
If I can enter recovery, can I flash a custom rom even if i am S-ON? Now I am in unlocked state and S-ON.
Eventually can I try restore my other M9 backup, done with TWRP 2.8.7.1, to this M9 having TWRP 3.0.0-0? I will check but I think they got same firmware (3.35.401.12).
Thanks again everyone

You don't need to be S-OFF to flash a custom ROM. You only got to check if the ROM base matches the firmware that is currently installed on your device
S-OFF unleashes just a little bit more freedom to play with your device, but at the same moment the risk of making a mistake and really bricking the device is highly increased.
Sent from my HTC One M9 using XDA Labs

This is a good example of why I hate toolkits and advise people never to use them, unless you already know how to do all this stuff manually. It's too easy to get into trouble you don't know how to get out of.
Try pressing all three buttons until you reboot if the other options don't work.

iElvis said:
This is a good example of why I hate toolkits and advise people never to use them, unless you already know how to do all this stuff manually. It's too easy to get into trouble you don't know how to get out of.
Try pressing all three buttons until you reboot if the other options don't work.
Click to expand...
Click to collapse
Yes you are right, before to start play with roms and stuff I usually lost days and days reading everything possible for every passage, while this time I was like "Oh cool a toolkit! Easy way let's do it!". Anyway I don't want to give responsibility to Windroid toolkit, only my fault I did things without thinking too much.
Respect for eveyone working hard to give us knowledge and this beautiful forum!
I will keep you informed thanks again everyone

Ok guys here I am.
Everything ok now thanks everyone again.
With phone switched off due to dead battery I was able to start with VOL DOWN + PWR and I could reach bootloader, download mode and recovery. Installed custom ROM, flashed SuperSU 2.65 and now I am on the road again :good::good::good:.
Only problem left is since I installed ROM (ViperOneM9 4.3.0) I cannot use adb: adb devices return "unauthorized".
I read various posts and the problem seems to be the phone not showing prompt to accept RSA key.
If I connect my other M9 everything is ok.
I think to have tried most of everything people suggest in different posts:
- updated android sdk
- reinstalled android sdk
- deleted adbkey and adbkey.pub in my %user%/.android folder (it recreates files but still no prompt on phone)
- reinstalled drivers on PC
- reinstalled rom with wipe during aroma installer
- looking in the phone in "system/data/misc/adb" for keys files but my folder is empty (checked on my other fully working M9 and that folder is empty too)
- tried install Minimal ADB and Fastboot [4-27-16] http://forum.xda-developers.com/showthread.php?t=2317790
- toggled USB debugging on/off rebooting phone and PC
If you have more advice I am glad to hear.
Thanks again to everyone to get my phone back working!

Is your other m9 running the same rom? The problem wont be the pc. If you can see one you can see all. Adb is versatile like that..
Try adb at twrp or one of the other booting modes. I'm quite sure adb is twrp only..
Beamed in by telepathy.

shivadow said:
Is your other m9 running the same rom? The problem wont be the pc. If you can see one you can see all. Adb is versatile like that..
Try adb at twrp or one of the other booting modes. I'm quite sure adb is twrp only..
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi, on other M9 i have same rom but 4.2.1 version (4.3.0 on not working one).
If I go on recovery or bootloader or download mode adb return "list of device attached" like it dosnt feel nothing connected. On the other M9 all is ok.
I just tried install a VM with Windows 7 but I am not able to let it see the USB device

Thread closed at OP's request. He has been able to resolve the issue.

Soft/Hard brick when chainfire rooting

Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!

My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478

Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.

Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised

thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything

I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device

I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140

Thanks, Mike01680. trying now

When i go into sideload i can see the device listed on adb devices!

Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!

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

Bootloader unlock bootloop on 2.0

Hey guys,
So I was able to return my HW to a normal state on AW 2.0. It turns out as soon as I unlock the bootloader, it goes into a bootanimation bootloop (a few times, it displayed an error then finally booted AW). And I can't get into the stock recovery. It seems like this one is screwed up somehow. Flashing TWRP works though.
I really don't understand this. I thought this was supposed to be like a Nexus/Pixel device. Has anyone else experienced this behavior? I would really like to unlock it and flash Negalite ROM.
Thanks!
Edit: OK so the watch only works if I flash the custom ROM from AW 1.5 using TWRP. It goes all the way and doesn't bootloop. SO WEIRD.
---------------
Original post:
Hi everyone,
I got my HW today and it's already messed up! I've been flashing ROMs and such for a long time now but I'm stomped. Initially, I wanted to install Negalite ROM.
Here's what happened:
- I used my watch for a bit on 1.5, connected it to my phone, did the initial setup and OTA updated to 2.0.
- I decided to unlock the bootloader. Worked but watch got stuck on a recovery bootloop (with the open bugdroid). Managed to get rid of it by factory resetting through TWRP (which I fastbooted).
- Watch was restarting (on 2.0) but got stuck on another bootloop (on Nougat bootanimation). Sat there for about 20 min.
- I decided to downgrade to 1.5. Used fastboot to flash boot.img, recovery.img and system.img. The system.img gave me an error at first while flashing but proceeded all the way (9 steps out of 9) with success (?)
- Now the watch is still stuck on bootanimation (I think it's the MM one, with the flying around dots) and won't go any farther.
Note: I can get into fastboot and TWRP 3.0.3 is installed. But multiple factory resets from TWRP don't change anything. I can't adb push anything to the watch from TWRP either (I tried the ADB sideload option). ADB drivers should be OK on my Windows 7 x64 machine (I used Google drivers from the SDK).
Any HELP please? I really don't know what to do now since I can't push any file to the watch... and I've read many threads on here to no avail.
Thanks in advance.
edit: IT BOOTED! I used a different system.img (the one from sturgeon-m6e69f-factory-e659286a.tgz) and flashed it with fastboot and IT WORKED! Thanks to whoever posted this version! Now I will try again to install Negalite.