Hey guys and guyettes!
I somehow managed to put my One mini into a boot loop!
None of the options on the fastboot menu do anything other than turn the screen black and then go back to the boot menu... If anyone has any ideas on how to fix this it would be greatly appreciated!
And before anyone asks for whatever reason, no it is not rooted!
Things I've tried:
- Using ADB and SDK to unbrick it
- Hard resets, recoveries and factory resets
The last thing I did before it started the loop was install King of Thieves (a game).
Before the loop it ran out of power so I plugged it in and it went to the menu like it usually does then it just started too loop!
Thanks for any suggestions
~James
I'm currently chasing the same thing on my wife's phone. This is the 2nd time this has happened. (the first time was replaced by factory warranty). The ROM and everything is completely stock so I'm trying to unlock the bootloader using the HTC dev tools and I can flash the Unlock_code.bin but the screen never prompts me to actually unlock it... I'm hoping someone has a tried and true way of fixing this.
iceterminal said:
I'm currently chasing the same thing on my wife's phone. This is the 2nd time this has happened. (the first time was replaced by factory warranty). The ROM and everything is completely stock so I'm trying to unlock the bootloader using the HTC dev tools and I can flash the Unlock_code.bin but the screen never prompts me to actually unlock it... I'm hoping someone has a tried and true way of fixing this.
Click to expand...
Click to collapse
I have the bootloop menu which suddenly appeared for no apparent reason seeing as I haven't rooted the phone. It's an annoying problem that I see many people have except most people I see haven't quite got the same problem as myself...
Same issue...
I have a customer's phone, having the same issue. The customer brought it to me like this and I thought I would try to repair it. He is mentally challenged and so I really wanted to help him. But it's doing exactly what the OP stated. I even tried the same things before I found this thread. Unlocked the bootloader (but it did not actually bring up the screen to unlock the bootloader, the WinDroid Universal Toolkit simply stated it was unlocked). And yes, I did acquire the unlock.bin or whatever it was called.
So the phone will do nothing but reboot. I'm not sure how it got this way or if it can be fixed. That is why I am here.
Any ideas?
Thanks!
Da
PAinguINx said:
So the phone will do nothing but reboot. I'm not sure how it got this way or if it can be fixed. That is why I am here.
Any ideas?
Da
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=57727218&postcount=1365
probably this is the case
Hello, I have bricked my lg g2, I started to try to unlock the bootloader on my phone so I could flash custom roms and such. Well, being the dumb idiot like I am, I used the wrong unlocker for the wrong variant of the G2. It was stuck in fastboot mode. As I was about to get out of the brick that I had, I deleted aboot. This was the real mistake. It wouldent let me put on the aboot.bin back into the phone because of some directory problem on my computer... (ended up being my fault... AGAIN...) well, now, It doesnt even boot anymore... It vibrates as if it would turn on, then just goes to an extremely dark screen (looks like it's still off...) I tried to put aboot.bin back into the phone via command prompt, I figured out how to find the directory of aboot.bin, but it just waits for the phone. If there is any way I can save this phone, I would love to. I am inexperienced in rooting androids and flashing and this whole root thing was a mistake :silly:
Thanks
- soups
delicioussoups said:
Hello, I have bricked my lg g2, I started to try to unlock the bootloader on my phone so I could flash custom roms and such. Well, being the dumb idiot like I am, I used the wrong unlocker for the wrong variant of the G2. It was stuck in fastboot mode. As I was about to get out of the brick that I had, I deleted aboot. This was the real mistake. It wouldent let me put on the aboot.bin back into the phone because of some directory problem on my computer... (ended up being my fault... AGAIN...) well, now, It doesnt even boot anymore... It vibrates as if it would turn on, then just goes to an extremely dark screen (looks like it's still off...) I tried to put aboot.bin back into the phone via command prompt, I figured out how to find the directory of aboot.bin, but it just waits for the phone. If there is any way I can save this phone, I would love to. I am inexperienced in rooting androids and flashing and this whole root thing was a mistake :silly:
Thanks
- soups
Click to expand...
Click to collapse
doubtful it can be fixed if it wont boot, but you can try asking your question in the g2 q&a. maybe some expert in your device forum can help.
Hey,are you able to boot into boot loader...if you can just lock the boot locker back and type the reboot command from PC itself
arunbiju969 said:
Hey,are you able to boot into boot loader...if you can just lock the boot locker back and type the reboot command from PC itself
Click to expand...
Click to collapse
sorry, but that is actually the worst possible thing you could do in this situation. locking the bl back will prevent you from flashing any further software if needed or possible, to fix this issue.
the g2 bl isnt unlocked as you suggest. it is bypassed with an exploit and not really unlocked.
bweN diorD said:
sorry, but that is actually the worst possible thing you could do in this situation. locking the bl back will prevent you from flashing any further software if needed or possible, to fix this issue.
the g2 bl isnt unlocked as you suggest. it is bypassed with an exploit and not really unlocked.
Click to expand...
Click to collapse
Ok, is there a command that I can use to boot back up?
delicioussoups said:
Ok, is there a command that I can use to boot back up?
Click to expand...
Click to collapse
its been a long time since i used my g2, thats why i suggested you ask in the g2 help forum in post #2.
please dont take my correction of the other guys post as there being a fix for yours. i really believe there is not, but his advice was blatantly wrong, so i had to correct it.
i think aboot is download mode/fastboot (if you have that). so deleting that when the phone cant boot is very bad. if the phone was booting, and rooted, it would be easy to put on a new aboot with dd code.
bweN diorD said:
its been a long time since i used my g2, thats why i suggested you ask in the g2 help forum in post #2.
please dont take my correction of the other guys post as there being a fix for yours. i really believe there is not, but his advice was blatantly wrong, so i had to correct it.
i think aboot is download mode/fastboot (if you have that). so deleting that when the phone cant boot is very bad. if the phone was booting, and rooted, it would be easy to put on a new aboot with dd code.
Click to expand...
Click to collapse
Alright thank you!
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.
Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.
Have you came across the ota .IMG file?
I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.
I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.
Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk
I've run into a huge problem that I hope someone here can help me with. I currently have a USA model XZ that is on Nougat 7.0. Completely stock, bootloader locked and everything. I've been reading and researching all the necessary steps to flash a custom rom on the XZ and am prepared. Have all the files I need, am following the steps in order and making sure I don't skip or overlook anything, but my problem is at the first few steps.
I am trying to backup my TA partition, but the problem is when I flash a 6.0 FTF. I flashed a European FTF, flashtool said successful, but when my phone booted, I reached a screen that said "To start Android, enter Password". I did not have a password on my phone to unlock, a pin, nor a pattern. I had it at swipe to unlock and made sure of it before I flashed the .FTF file. I googled, tried reading some threads here, but no luck. I entered my Google account password that was associated with my phone, nothing. It gave me 20 tries and if I got it wrong 20 times, it would factory reset I believe. Out of fear an panic, I flashed the newest USA FTF from Xperifirm and everything worked like normal. All my files, apps, and settings were there as if nothing ever happened.
Has anyone ever seen that screen? I wished I would've taken a picture, but I was completely afraid that I softbricked or did something wrong with my phone. I would love to try out a custom rom, but would prefer that I still have all my DRM keys intact. Could anyone help out? Thanks in advanced for reading and helping!
So, the title speaks for itself. I advised them to go through google, since most likely her phone is synced online and google has a request page for it
https://support.google.com/accounts/troubleshooter/6357590#ts=6357650
Click to expand...
Click to collapse
Other than that, my main question is, if that fails, is there anyway to boot to twrp, either simply booting it via fastboot, or flashing, without wiping her data.
The first thing that came to my mind was copying off of from recovery, but if bootloader still locked, that prob wont work right?
I've never messed with google pixel phones, but ya know, on the old nexus i have, the second u unlock the bootloader it wipes userdata.
Or any other methods?
Any ideas?
You're thinking correctly. There's not a way to boot/flash recovery without the bootloader being unlocked. You're looking at trying to figure out the code/password, or working with google like you've mentioned. Which BTW, kudos for bringing this up!