The mom needed a device and I dug out my ol OP3 (rooted). It was stuck in a boot loop and I decided to flash it back to the original factory settings. But from there on it would never boot into RECOVERY only into FASTBOOT. So with ADB still working I used the many available "Mega Unbrick Guide for A Hard Bricked OnePlus 3". The main problem was it would load and then faced with 3 errors upon trying to boot. Corrupted MD5, error with recovery and something else. I never had a problem with the drivers part and the main hang up was with either using the x64 or the x86 driver. But with no luck neither worked and always showed the same FAIL.
After many hours of no luck, during a load the phone disconnected on its own and the computer showed that something changed and no longer recognized the previous connected device.
Now resulting in no response to any action of any combination of buttons. Please explain how this can happen again, and could possibly be prevented in the future. I have rooted may devices with loads of help from the XDA community and have now experienced my first hard brick..kinda embarrassing when I told the mom she would have a killer device in about an hour resulting in full embarrassment!
After leaving it on the charger for a bit, it still was able to connect to the computer and run yet an UNSUCCESSFUL install with MSM download tool v3.0.
Thanks guys for reading.
@adjday
Try THESE
Related
All,
I have used my GS3 for awhile now without issue. I'm abroad for the forseeable future, so I've only been using it for Wi-Fi calling and internet/apps. Regardless, Kies NEVER worked for me, and my computer never recognized the USB device. Up until recently, I've just used my iPod for music, so no problem.
Fast forward and my friend, who also has a GS3, tried to update my drivers and root/flash my phone so I can drag and drop files the way he does with his. I let him do this because I'm newb to this, and because he assured me he knew what he was doing as he'd done it to his and his girlfriend's phone.
As it turns out, he has an international version (he used ToolKit instead of QCom ToolKit) and he tried to root the wrong files to my phone. At first, I thought it was hard-bricked (which really puts me in a tough position since I won't be back in the States until January), but I don't think even his root attempt worked properly.
So where I'm at now:
The phone will not boot up. When I turn it on I get the Samsung Galaxy S III logo, but android never loads. The phone will charge via USB and the wall.
I can access recovery bootup
I can access download bootup (the ability to do the two above lead me to believe it isn't hardbricked, I read on these forums, if I can get to download bootup then it's probably fix-able)
I've combed the forums and the internet, in general, for a fix. I downloaded the factory restore settings from samsung-updates (sorry if I cannot plug this site, it's not intentional, simply to provide as much info as possible), but Odin always "FAIL"s when I attempt to apply it.
Additionally, I've attempted to recover via recovery bootup/reset, and then load the factory restore setting via Odin. This did load them, but the phone did not boot up.
QM ToolKit was acknowledging the phone, so I attempted to boot the correct files using ToolKit (the ALLINONE option) and this worked correctly, as expected via QM ToolKit. But still the phone would not boot up.
The phone sits at a black screen after the GSIII logo with the blue LED lit up.
Any tips or advice would be appreciated. I'm in quite a situation.
sadly i have the same problem, this happened randomly and cant get my device to boot
If you Odin tmo stock image tar and odin recognized your device and all went well then boot into stock recovery factory reset then reboot. It should boot up if all is well. When you plug to pc does your computer recognizes it?
Sent from my SGH-T999 using xda app-developers app
Provided your boot loader and download manager partitions are working(as it appears to be the case) you can get your phone back to a "working" state.
What I suspect happened is that at some point during the process of playing with it, your partition table got hosed and now android is borked. I would recommend re-partitioning it but I don't have enough info around me and available to give you instructions to do so. I'll do some digging and try to get back to you.
I've tried searching and there doesn't seem to be a solution to this problem for this device.
Yesterday I was flashing ROMs, namely AICP, but I accidentally pressed Reboot to Bootloader in CWM. I got stuck in bootloop after that and it kept returning to recovery. I google'd for a solution and found this(androidforums-.-com-/esteem-all-things-root/478814-how-get-out-clockworkmod-recovery-bootloop.html), which I downloaded and foolishly flashed (devices unsimilar). Flash is successful, and I reboot my phone.
It now will not show the LG splash screen, nor will it enter Download Mode. When connecting the device via USB, it does not seem to add a COM port on the computer. What it does do is try to install a driver named QHSUSB_DLOAD which fails to install.
Could someone please help me solve this problem? Thanks..
dylanraga said:
I've tried searching and there doesn't seem to be a solution to this problem for this device.
Yesterday I was flashing ROMs, namely AICP, but I accidentally pressed Reboot to Bootloader in CWM. I got stuck in bootloop after that and it kept returning to recovery. I google'd for a solution and found this(androidforums-.-com-/esteem-all-things-root/478814-how-get-out-clockworkmod-recovery-bootloop.html), which I downloaded and foolishly flashed (devices unsimilar). Flash is successful, and I reboot my phone.
It now will not show the LG splash screen, nor will it enter Download Mode. When connecting the device via USB, it does not seem to add a COM port on the computer. What it does do is try to install a driver named QHSUSB_DLOAD which fails to install.
Could someone please help me solve this problem? Thanks..
Click to expand...
Click to collapse
Hate to say two things to you bro:
1) You didn't search very hard, because there was a related thread on page 3 with "QHSUSB_DLOAD" in the title
http://forum.xda-developers.com/showthread.php?t=2781522
I forgive though, but just letting you know.
2) You're screwed. The phone is hard bricked. No way to get it back to life.
How do I know? Well, look who's the creator of the thread just linked to.
Read the entire thread. It's not very long.
PS: PM me if your phone is still under warranty and you want advice on how to get it replaced. If you still aren't under warranty, then you're doubly screwed.
So my phone has been this way since Nov 2017, there are files that I need access to and would truly appreciate some guidance
I was experiencing issues with the bluetooth on nextbit previously so I installed a new rom after flashing the device. Once the rom also gave issues I decided to revert back to the Nextbit 7 OS and one fine day when the phone restarted it wouldnt go past the "nextbit" splash screen. Tried installing the OS again however the PC wouldnt recognize the phone anymore, switched laptop to a Mac and got the same issue
Any help would be greatly appreciated
It wont let me post a URL link. I have taken www out hopefully it allows to view the video, shows exactly whats wrong
youtube.com/watch?v=ImIk5CErWf0
It looks there's something wrong with the system boot, since it's reaching the blue boot-animation and it stays there (probably before loading the adb stuff). Fortunately u did unlock the bootloader and that annoying initial screen may be helpful this time, did u try to reach recovery or fastboot mode from there (pressing some volume key)? It's pretty hard for it to be broken there too and in such a case I would think about some hardware fault. Anyway from the recovery (I hope u have TWRP, if not install it with fastboot) you should be able to do whatever u want, including recovering your files or (re)installing a rom
Hi everyone.
I have been reading a few posts about bootloops in hopes that someone would have been facing the same issue as me. It seems my case is a bit different. I am desperate for some help!
My Max 3 came initially with a chinese ROM but I followed some wonderful tutorials here and I unlocked it and installed initially the xiaomi.eu ROM. Then a couple of months later I installed AOSiP ROM, I updated it a couple of times dirty flashing over it, and settled in exactly the "AOSiP-9.0-Pizza-nitrogen-20190719" build. And there i was, for 4 months, all stable, then suddenly today I was going to unlock the phone with my fingerprint and asked for password.
This happens exactly 1 time per day but I noticed that today it was the second time. Then doesn't matter how many times I put my password correctly, it would keep asking for my password. So I decided to restart the device... and then the bootloop issue started. It starts, reaches the moment in which the AOSiP logo shows and (not even 1 second until the logo shows) freezes, and restarts the device.
I can access the recovery without issues so I didn't panic yet, I backed up all I could, wiped everything I could, started from zero: firmware 9.9.3 + AOSiP-9.0-Pizza-nitrogen-20191117 + gapps. The bootloop still there, in exactly the same way. So at this point I have no clue what could be the reason. I was always careful not to trigger any anti-rollback, it was all going good, now not even with a full factory reset seems to work. I even reinstalled the recovery.
Any ideas? does anyone know what could I try next? Thank you very much advance.
I forgot to attach some logs. I got using the TWRP Advanced > Copy Log option.
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
diegoocampo said:
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
Click to expand...
Click to collapse
The mi max 3 has arb enabled, so flashing old rom can cause it to brick.
Have you tried different button combinations to enter fastboot? If you can get to fastboot, just flash a fastboot rom, if that works.
If the brick is caused by triggering ARB, then that may cause some issues, and may need an Authorized Account to flash the ROM from scratch, with some qualcomm flashing tools things.
Though, there may be some way to bypass the authorization for mi max 3 on the internet and have your device unbricked.
Thank you for your replies. Yes probably ARB, I thought my phone had never installed a ROM with ARB and so I was safe to install xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1 (which it is also to be pre-ARB), but I guess I made a mistake at some point.
Situation now:
- with Mi Flash I am getting the authorization error with almost any ROM, with very old ROMs I am not even able to start the flashing process
- with Qualcomm QFIL tool I always get an error "function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes". And I also tried with the patched files from here https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I think at this point I tried everything that can be tried. My bootloader was unlocked, but at this point I am not even sure if its unlocked anymore since I can't see anything on the device screen.
The only positive thing is that the phone always shows under the Windows 10 device manager "Qualcomm HS-USB QDLoader 9008", so at least is a bit alive, and with the Mi Flash at least for some ROMs starts the flash process. I am not sure if disassembling it and trying things like removing the batter would make any difference.
If anyone knows any other way to bypass authorization please let me know.
Here I am back with another update:
- I fixed the full brick by disassembling the phone and disconnecting the battery, with the battery disconnected I could finally flash a Chinese ROM. That however was just the beginning... more problems came
- Common problem I guess is that after booting with that Chinese ROM i was getting a message about how the encryption was interrupted. This was easy, just changed the file system of Data and formatted it and it was fixed.
- Now I am stuck in another hard to solve problem. Any ROM that boots will not allow me to use WiFi or SIM cards. And the reason is that the IMEI is not set anymore. Reading about it I see that this is related with the EFS partition being corrupted. Nothing seems to work now. I don't have any EFS backup . Anyone knows how to fix the IMEI in this case?
Hi Everyone,
I have a 5T running android 9 - completely stock. The device is SIM free, I have never customised it at all - if anything it's never been connected to a PC even.
A few days ago I was using my phone as normal (on whatsapp) but it completely froze. It now boots up to the "Your device is corrupt and cannot be trusted and may not work properly" - it freezes on start up and won't work at all.
- I can get to the fastboot screen
- I can get to the recovery screen to install from ADB
The fastboot screen says in red - device state - locked.
The device is a clean, un-customised phone. Only a few days prior I checked for any OTA updates but I haven't received android 10 yet.
I haven't flashed phone firmware or anything for years now. (By years, I literally mean years - back in the Nokia 8210 days). My only other experience of flashing firmware was with Samsung phones and 'debranding' them.
As I was not trying to root the device or anything - how do I fix this issue? I've searched the forums but I cannot fine a scenario similar to mine therefore I'm a bit confused as to what to do to resolve it.
I've tried to sideload this - oneplus.com/uk/support/softwareupgrade/details?code=PM1574156155944 via recovery but it says installation failed.
Any help appreciated thanks!
Sounds like you're straight out of luck to recover any data if your device is completely stock, as to unlock your bootloader to access encrypted data would mean a factory reset. You could try try one of the unbrick tools using the guide here. You will lose your data.
I tried the unbrick tool here - forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
... and it doesn't work. The phone now boots to a blank screen with a constant white LED.
Could this be a hardware issue?
I'm not too concerned about losing my data - already gave up on trying to keep my data when the problem first occurred!
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
oneplus5t_ said:
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
Click to expand...
Click to collapse
Problem fixed?
unfortunately not. Any ideas on next steps?
That's an odd issue for sure. My only idea would be installing TWRP and maybe formatting from there and using fix permissions etc. to see if it has any effect.
I've done some googling to try and understand "TWRP" but I'm not sure I fully understand. Are there any forum posts I can refer to?
- phone has been flashed several times
- before this whole saga dev mode was enabled, but only to reduce animation scale - USB debugging was never enabled
- the phone has always been stock / sim free - never rooted
Thanks
Can you get into recovery? If yes then try connecting to a pc whilst in recovery as it should let you open your phones internal storage on PC but im not too sure if stock recovery allows it, (TWRP) does. Then copy whatever files you need. Let us know if you can get into fastboot mode aswell
It sounds similar to an issue I have just experienced with a friends 5T. In my case it's a hardware issue (seems like Wi-Fi has died). Just for kicks try to flash the Android 7 firmware. For some reason it allowed me to boot the phone fine and use it, albeit without any Wi-Fi. I sideloaded OOS 4.7.6 and that seems to be the last version 7. You could also use the older unbrick software. Academic I fear as I think you have a hardware issue.