Develop Bugs

[Q] Phone Stuck on Android Flasher while flashing radio. Need help/information.

Edit:
i have successfully flashed the new radio via the adb. seems that the android flasher was the problem. thanks and this thread can be closed/deleted or whatever you do with outdated threads
Hello xda community.
I am a noob on xda-developers and i hope, i am not asking a too obvious question, but i didn't find helpful posts regarding problems with android flasher.
Yesterday i followed the noob guide to flash Revolution v3.0 data++ version.
I used revolutionary to s-off and installed superuser via recovery.
I did a Nandroid Backup, just to make sure.
I then used Android Flasher 2.2.0.5 to install the CM7r2 hboot and afterwards flashed the Revolution v3.0 ROM.
Everything worked fine, my apps and contacts got restored via titanium backup, but since (even on stock rom) i have been having issues with my wifi, i decided to upgrade to a new Radio version (from 5.11.05.27 to 5.17.05.23).
And here is the problem:
I started Android Flasher, which first didn't recognize the phone, but then started flashing with this message:
"error: device not found
< waiting for device >
security: off
finished. total time: 0.001s
"
Now my phone is stuck (as we speak right now) not responding on the fastboot screen, with a loading bar in the top right corner that is nearly full. Trying to press finish on the Android Flasher has given me no response (although the program seems to still respond).
After reading in the forums, that flashing the radio is a crucial part of the phone and it screwing up might brick it, i want to be very careful and not unplug my phone or try to force Android Flasher to close.
So the qestion is: What should i do? Is there any way to get Android Flasher to finish the process, or find out what the current status is?
I have attached a picture of the Android Flasher window as it is right now. I won't shut down my phone or my computer, being scared of the risks involved. Any help would be greatly appreciated.

I guess you can click "Finish" on the GUI to see if it closes properly. I'm a bit more worried about what happens when you do a battery pull on your phone though. Although the GUI said that device wasn't detected making me think that nothing was flashed, the fact that fastboot loading bar appeared makes me think otherwise.

I did try and click finish on the GUI but onfortunately with no result. I can copy the log, but finishing doesn't seem to work...

I honestly don't know what to tell you. You may have to force Android Flasher to close then a battery pull on your phone and hope nothing gets corrupted during the process. I think you don't have any other choice on the matter.
Try to wait for other people to give you some input on this since I never experienced this kings of issue when using Android Flasher.

Thank you very much, that's what i was afraid of... I'll wait and hope someone comes up with a solution, at least it's no: "you were to stupid to use the search function" question
edit:
After installing android debug bridge and finding the phone was not connected to the pc anymore, i decided to pull the usb cable which restored full functionality to the phone. It just seems now, that Android Flasher is not working at all anymore...
I will try another way to flash the radio, thank you stankyou for the quick and helpful reply
edit2:
i have successfully flashed the new radio via the adb. seems that the android flasher was the problem. thanks and this thread can be closed/deleted or whatever you do with outdated threads

Have you tried posting this problem in the AF thread? And have you made sure to install the necessary drivers needed? You might also want to run AF with admin privs.

[Q] Reflashing to Stock on Incredible with occassional boot loop?

A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?

kmandel said:
A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?
Click to expand...
Click to collapse
You can reflash the phone to stock with what incredible users call an ruu (rom update utility), however flashing older versions or downgrading the os is not allowed with s-on (security on). His best bet in my opinion would be to root and s-off the phone, and then flash a custom rom. However if hes not into all of that he can try to do an ruu and see if it fixes things. Doing so will wipe the phone compleetly and he will loose all of his apps and data. A pc running windows xp or newer is required.
1. Download the ruu http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, and place it somewhere on your pc.
2. Download and install HTC Sync http://dinc.does-it.net/HTC-Sync/3.0.5606/setup_3.0.5606.exe.
3. On the phone go to menu - settings - applications, uncheck fastboot if it is checked and then select development, and make sure usb debugging is checked.
4. Connect the phone to the pc with the usb cable, and wait for any drivers to install on the pc. The phone should be in charge only mode.
5. On the pc run the ruu file and follow the instructions it gives you.
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.

cmlusco said:
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.
Click to expand...
Click to collapse
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.

kmandel said:
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.
Click to expand...
Click to collapse
Well not like it originally came from the factory 2 years ago (with froyo), but if they were still selling them today or you get a replacement, that is how it would come from the factory. The last update 4.08.605.2 fixed all the major issues and shouldnt give any major trouble. The only other option would be to root.
Verizion is pretty good with customer service, you may have to find a knowledgable employee but they can do it for you.

We tried the "ruu" approach without success. The drivers installed on the PC, the phone goes into debug mode, and we can even run "adb" manually and talk to the phone. However, when either "ruu" or "Ht Sync" try to talk to the phone they just say the phone is not connected.
If we run the task manager on windows we can actually see "ruu" invoking "adb" and there is no long timeout. It appears that ruu just doesn't like the answers.
Again running adb manually for example with the shell option seems to do all you expect adb to do. This is with both the versions linked above and the updates they end up offering.
Any ideas?

OK, found a mistake. I didn't realize that to do the ruu flash I needed to turn off the phone and vol-down/power it into htboot mode.
With that done the update program sees the phone notices it has lastest firmware and offers to update it to the same version. I say yes, and the phone reboots and the PC tells me it will take 10 minutes to flash, then 2 seconds later tells me it succeeded and the phone reboots.
Obviously it did not flash anything. Am I missing something?
Also any pointers on how to flash an earlier stock rom (and where to find it)?

[Q] Bricked Phone...Peculiar Situation

Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!

As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.

Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again

This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app

I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it

Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.

Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that

[Q] (Help: Can't boot) Lollipop + eager urge for Xposed

I'm going to be away soon and won't have easy access to a non-professional PC (meaning any computer I may have access to - I won't have admin rights with). I didn't want to wait for a root+TWRP dev package for Lollipop to be released. I wanted to just get it done, (I was having bad problems with KitKat on some select apps because of LG's 4.4 coding, long story, but I won't even go there...)
I saw that I can go to the LG support site via a link from Android Central and manually upgrade to Lollipop way before the OTA rollout even begins. I had heard rumors of people having problems, read posts, and learned how to avoid it all. I reset everything before upgrading. I did many factory resets after getting Lollipop, (I know, a lot). I got rooted and set mostly everything up.
I wanted to get Xposed loaded, BADLY. I looked it up for Lollipop and realized that I'd have to flash a custom recovery. I expected as much. When I looked that up, I realized that I would have to either use a downgrade-upgrade method (which I didn't feel like going through) or a mandatory requirement of factory reset though a process. I had already set up all of the system stuff and restored from Titanium backup most of my apps. There was no way I would factory reset because I hate resetting-up the system stuff. - - - - - BIG MISTAKE 1
So I found a thread for the D850 (AT&T) version (no I didn't flash a bad radio or anything, I thought I knew what I was doing because I was only flashing recovery stuff for Lollipop, not an AT&T rom or radio.) This was to install TWRP without downgrading or resetting. The instructions said to copy files from an aboot.img and other boot images and such (to replace the recovery) on to the internal memory and use a terminal to type in code. I did it and rebooted it.
I made a horrible mistake.
When I held the power button on the phone, nothing happened. I found out that when plugging it in to the PC, it seems to be in download mode. It was fully charged. When using the restore/brick recovery software, I have tried different cables, different computers, checking to see if anything is corrupt, different USB ports, etc. with the files... Nothing will work. I keep getting an error with a red box about the model or something. "Model Information Check Fail"
So basically I have broken boot images on my device. I need to fix these.
Where do I go from here? All because I wanted Xposed on Lollipop without resetting.
Click to expand...
Click to collapse
I have this situation. I messed up with laf.img and aboot.img too (from D850, thinking it was harmless since trying to install custom recovery only) and device won't turn on but PC recognizes as download mode but can't flash. Please read above. I'm bricked and all restore methods have failed so far.
Source from u/nicksteron on reddit.

I'm having this issue now too. It seems the thing I downloaded and tried broke my boot images.
Have you been able to fix this?
I'm trying the LG Flash Tool but it stops me at the model check fail as well. Gonna try a kdz method next.
EDIT: I tried the KDZ method with LG Flash Tool 2014 using both a KitKat and Lollipop based ROMs and I get an error. The S/W Upgrade progress gets to 4% and then the error shows up. I need my phone. Help?!

Question Bricked for Days and usable WiFi is $$$ for vanlife, help!

I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.

When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.

bigdog1459 said:
When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.
Click to expand...
Click to collapse
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.

nastyneighbor said:
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.
Click to expand...
Click to collapse
Damn. I'm sure you have tried some of the manual flashing guides out there too?

nastyneighbor said:
I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.
Click to expand...
Click to collapse
Not sure when you said you used "Stock Recovery Flash Tool" if you meant the "Android Flash Tool". But just in case you didn't, that can force flash partitions with it. Probably your best shot.
Android Flash Tool
flash.android.com

Android Flashing Tool online unbricked me the other day. You have to be patient with the tool as it took me several tries. It will totally wipe your phone, but at this point you just need to rescue your device. Keep us posted.

thanks for the tip. i'm trying the android flash tool again now. and will keep trying it until it at least passes the download stage. and yes i tried all the manual flashing guides out there...and hybrid combos of all as well. i mean i'm positive its my fault for missing SOMEthing somewhere but many hours have been spent with overall negative progress.
my track record is still zero hard bricked devices or soft ones I couldn't fix over all these years so i'm not too worried but i could use my phone back haha
will keep posted as requested. ty again.

I know this doesn't help your immediate situation, but when flashing anything like custom kernels, I would advise not to use some random app to flash it with, just follow the directions in the OP of the kernel's thread, and make sure you have up to date Platform Tools and driver. CleanSlate and many or all the custom kernels also require flashing more than just the boot.img.
Good luck, I hope you get it back working for you.

Hey guys, the Android Flashing Tool finally worked for me and I am up and running again. Thanks for your help and tips. Hacking phones is more important every year and thus I truly value your skills and advice. This community must survive the new world order. much love folks