Database Users

[Q] My MT4G has bootloop, and adb says device offline. I will thank who can hlp

I have a MT4G with S-0ff. I dont know how it happened but I got it all messed up. I can get to the engineering menu then select recovery. But thats about it ( which I see a phone with warning sign in red) and when I run the command "adb devices" in adb/tools It says"error:device offline". I have tried everything even changing different usb ports. ( I have many roms and clockworkmod3.005 and 2.0 ,, version available)
Can someone help me please, I will thank you (will give thanks)
Good bless you.

ilkercatal said:
I have a MT4G with S-0ff. I dont know how it happened but I got it all messed up. I can get to the engineering menu then select recovery. But thats about it ( which I see a phone with warning sign in red) and when I run the command "adb devices" in adb/tools It says"error:device offline". I have tried everything even changing different usb ports. ( I have many roms and clockworkmod3.005 and 2.0 ,, version available)
Can someone help me please, I will thank you (will give thanks)
Good bless you.
Click to expand...
Click to collapse
What did you do before this, when phone was in working condition?

I dont know
Phone simply does not go into recovery. When I go into engineering menu then click recovery phone just freeze with my touch 4g logo on it.

ilkercatal said:
Phone simply does not go into recovery. When I go into engineering menu then click recovery phone just freeze with my touch 4g logo on it.
Click to expand...
Click to collapse
do you have the engineering hBoot or the stock hBoot? Can you boot into a fully working ROM?

it happened to mine as well...did you flash a new kernel on it....sometimes on a rom if you flash a new kernel to lets say overclock your phone or some sort it goes into a BootLoop where the Mytouch boot screen keeps rebooting but does not go into any rom...if you can get to recovery wipe cache and try to reboot..if you cant get to recovery try getting to it through the normal Hboot (volume down +power key)..hope it helps

ilkercatal said:
Phone simply does not go into recovery. When I go into engineering menu then click recovery phone just freeze with my touch 4g logo on it.
Click to expand...
Click to collapse
If you can boot completely, install ROM Manager and flash a recovery with it. If you can't boot, then you can flash a recovery using the fastboot tool from the Android SDK, but only if you have the engineering bootloader (0.85.2007)

neidlinger said:
do you have the engineering hBoot or the stock hBoot? Can you boot into a fully working ROM?
Click to expand...
Click to collapse
I see only stock bot. ( turning phone on while holding vol- down rocker button)

i only see stock menu

When adb said my device was offline I just typed in (While it was connected)
Code:
adb kill-server
adb start-server
any my device was online.

Are there anyone who knows what they are talking about? Or, most people just say things to be busy or something. Come on people if you dont know how, why waste your time

did you find anything that helped? My phone keeps restarting as well.. i even updated cmw and used cm7 rom.... still keeps restarting... it happened after i used the royal senseless rom..

myk0 said:
did you find anything that helped? My phone keeps restarting as well.. i even updated cmw and used cm7 rom.... still keeps restarting... it happened after i used the royal senseless rom..
Click to expand...
Click to collapse
did you do a complete wipe prior to flashing the your newest rom?

neidlinger said:
did you do a complete wipe prior to flashing the your newest rom?
Click to expand...
Click to collapse
yea.. wiped and formatted everything

i have a similar issue im trying to reboot my phone with adb. it is telling me that my adb is out of date the daemon starts but it tells me my device cant be found any ideas? and would an outdated adb be the reasson i cant find my device?

uroboch said:
i have a similar issue im trying to reboot my phone with adb. it is telling me that my adb is out of date the daemon starts but it tells me my device cant be found any ideas? and would an outdated adb be the reasson i cant find my device?
Click to expand...
Click to collapse
Install the usb driver for the glacier and reboot your computer
Sent from my GT-P3113 using xda app-developers app

[SOLVED] Bootloop. No recovery. Bootloader locked.

================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit

The same just happened to me, wtf

Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.

GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too

Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.

Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop

Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...

GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters

Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?

I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.

Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.

p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?

And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.

p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT

Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.

I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!

Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.

hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin

gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?

Hi GusGold No its 9008

Bootloop after ota to 6.0.2

Hello everyone,
here what's happenend:
I have downloaded the ota normally
charge enough
click on install
the installation looked normal
after the installation was finished it boots normally until the "Android was updating, optimize apps.." come that runs from 0 to 89 apps and then it reboots
and at this point something went wrong.
the oneplus bootlogo appeard and the boot animation plays. but when it finished the screen is black and after a few seconds the "android was updating" banner appeard again.
then it goes again in the bootanimation and so on..
i've restarted my phone by pushing the powerbutton once. still not working.
My phone is stock!
no root
no costum recovery
I hope you can help me.
Cheers, Confused.

additional Information
i'm able to open the recovery mode

confusedx3 said:
i'm able to open the recovery mode
Click to expand...
Click to collapse
If you are able to boot into twrp then follow the guide mentioned below (Twrp has MTP enabled just in case u didn't know) :
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826

thank you for the answer.
i dont have twrp installed i've only the stock recovery
what if i do a factory reset ?
i read this as a solution here:
https://www.reddit.com/r/oneplus/comments/3mtavv/opt_stuck_in_boot_loop_after_ota_update/
do you think that work in my case ?

confusedx3 said:
thank you for the answer.
i dont have twrp installed i've only the stock recovery
what if i do a factory reset ?
i read this as a solution here:
https://www.reddit.com/r/oneplus/comments/3mtavv/opt_stuck_in_boot_loop_after_ota_update/
do you think that work in my case ?
Click to expand...
Click to collapse
Yes

i am also stuck at same situation but the prob is i hav no recovery installed and i dont want to loose my internal data...is there a way to roll back ????

same here
I also installed through the software update button.
Everything seemed to work fine till optimizing apps.
Then my phone was showing starting apps...
it did it for an indefinite time and then i pressed the power button to reboot the phone.
however now it is not moving beyond the android logo and i dont want to lose my data so i am not clearing data.
i tried clearing my cache.
Any help please?
I am using stock recovery,unrooted phone,OOS 3.0.2

Soft-Bricked Samsung Galaxy A500FU with broken home button

Well this is my first post here.I flashed cm 14.1 on my devices with gapps through twrp.I managed to get to recovery with the adb drivers (as I mentioned I have a broken button so pressing Volume Down+Power+Home won't work).Everything was ok but due to the critical bugs of this rom (was still in development) I decided to downgrade to cm 13 which had less bugs.So I tried getting into recovery but everytime I gave the command in it would reboot to the system (not even in stock recovery).So I decided to flash the stock rom with odin and then try entering recovery mode.After flashing I actually realised that I f*cked up cuz I couldn't wipe the system data/davik cache,due to the fact that my home button is broken and so i cant access my stock recovery.Now my device is in bootloop...I already have a usb jig and it will just make it boot into download mode where i cant really do much.Any help would be appreciated.

RemainCalm said:
Well this is my first post here.I flashed cm 14.1 on my devices with gapps through twrp.I managed to get to recovery with the adb drivers (as I mentioned I have a broken button so pressing Volume Down+Power+Home won't work).Everything was ok but due to the critical bugs of this rom (was still in development) I decided to downgrade to cm 13 which had less bugs.So I tried getting into recovery but everytime I gave the command in it would reboot to the system (not even in stock recovery).So I decided to flash the stock rom with odin and then try entering recovery mode.After flashing I actually realised that I f*cked up cuz I couldn't wipe the system data/davik cache,due to the fact that my home button is broken and so i cant access my stock recovery.Now my device is in bootloop...I already have a usb jig and it will just make it boot into download mode where i cant really do much.Any help would be appreciated.
Click to expand...
Click to collapse
And the stock rom doesn't boot ?

McFy said:
And the stock rom doesn't boot ?
Click to expand...
Click to collapse
No my phone is in bootloop.Random vibrations occur now and then.

RemainCalm said:
No my phone is in bootloop.Random vibrations occur now and then.
Click to expand...
Click to collapse
So flash twrp and then reboot on twrp using adb I thought it work on dl mode
Say if that have work and hit tank please

McFy said:
And the stock rom doesn't boot ?
Click to expand...
Click to collapse
McFy said:
So flash twrp and then reboot on twrp using adb I thought it work on dl mode
Say if that have work and hit tank please
Click to expand...
Click to collapse
Well I don't think adb recognizes a device in download mode.
Will try though

RemainCalm said:
Well I don't think adb recognizes a device in download mode.
Have you try ? O hope is still a way to unbrick may be try to repair your botom if you can
Click to expand...
Click to collapse

McFy said:
RemainCalm said:
Well I don't think adb recognizes a device in download mode.
Have you try ? O hope is still a way to unbrick may be try to repair your botom if you can
Click to expand...
Click to collapse
Not yet.Phone is dead i need to charge it first.There is no way of turning off the devices while it boots up.You can either restart it or let the battery die.I cant really fix my home button cuz in order to do so i would need to remove the screen,thus damaging the Amoled panel.I could send the phone back to samsung idk
Click to expand...
Click to collapse

RemainCalm said:
McFy said:
Not yet.Phone is dead i need to charge it first.There is no way of turning off the devices while it boots up.You can either restart it or let the battery die.I cant really fix my home button cuz in order to do so i would need to remove the screen,thus damaging the Amoled panel.I could send the phone back to samsung idk
Click to expand...
Click to collapse
Yes maybe samsung can repair it depend of your country ...
Click to expand...
Click to collapse

RemainCalm said:
McFy said:
Not yet.Phone is dead i need to charge it first.There is no way of turning off the devices while it boots up.You can either restart it or let the battery die.I cant really fix my home button cuz in order to do so i would need to remove the screen,thus damaging the Amoled panel.I could send the phone back to samsung idk
Click to expand...
Click to collapse
Boot back to download mode and reflash twrp and set "auto-reboot, should boot back to recovery then + you will need to factory reset on recovery before flashing stock as the data actually stays
Click to expand...
Click to collapse

jimbomodder said:
RemainCalm said:
Boot back to download mode and reflash twrp and set "auto-reboot, should boot back to recovery then + you will need to factory reset on recovery before flashing stock as the data actually stays
Click to expand...
Click to collapse
Thanks for replying .I gave my a500fu who is a better geek than me to try and fix it.I will either get back my phone and try this or just tell him to do this.Thanks again I hope you are the one that saves my potato :fingers-crossed:
Click to expand...
Click to collapse

jimbomodder said:
Boot back to download mode and reflash twrp and set "auto-reboot, should boot back to recovery then + you will need to factory reset on recovery before flashing stock as the data actually stays
Click to expand...
Click to collapse
Didnt work phone boots back to system.

RemainCalm said:
Didnt work phone boots back to system.
Click to expand...
Click to collapse
Then you'll need to fix home button, it's not part of screen. It's got its own circuit underneath

Think my G6 may be bricked...

I do not have a great track record when flashing ROMS etc on LG devices..
Today I decided to flash my device back to total stock in prep for the incoming Oreo update and also the dreadful battery life i've been experiencing.
I tried using LGUP first but found that once the device completed it's boot, it got to the 'Android is starting' screen before rebooting.. It did this a few times before I turned it off and booted it into download mode.
I then used LG bridge and flashed everything directly through the Bridge software - This was successful however when it boots it is now doing the same thing.
It will show the boot animation, flash very quick the 'Android is updating/booting/upgrading' white screen before rebooting, showing 'erasing' very quickly then showing the boot animation again.
What am I missing here? Why is this happening?

For some reason flashing stock bricks the phone just factory reset it though the recovery. Tell me did you succeed...

ZinX09 said:
For some reason flashing stock bricks the phone just factory reset it though the recovery. Tell me did you succeed...
Click to expand...
Click to collapse
So yes, I managed to resolve this somehow.
As I managed to get into fastboot mode, reflashed TWRP and formatted the data partition - reflashing via bridge tool causes the same issue again and I only managed to get eh device to boot after I accidentally booting into safemode and allowing the device to finish optimising. Rebooting into normal mode then worked just fine.

adaimespechip said:
So yes, I managed to resolve this somehow.
As I managed to get into fastboot mode, reflashed TWRP and formatted the data partition - reflashing via bridge tool causes the same issue again and I only managed to get eh device to boot after I accidentally booting into safemode and allowing the device to finish optimising. Rebooting into normal mode then worked just fine.
Click to expand...
Click to collapse
I meant for you to reset through the stock recovery but i guess that works as well.

ZinX09 said:
I meant for you to reset through the stock recovery but i guess that works as well.
Click to expand...
Click to collapse
Oh I see, sorry.. I couldn't get into stock recovery - it would simply erase the device and reboot each time. That was part of the problem..

adaimespechip said:
Oh I see, sorry.. I couldn't get into stock recovery - it would simply erase the device and reboot each time. That was part of the problem..
Click to expand...
Click to collapse
Hello i have the same problem how to fix it showing erarsing for sek and that's it.

Mercz23 said:
Hello i have the same problem how to fix it showing erarsing for sek and that's it.
Click to expand...
Click to collapse
Have you tried to boot to the stock recovery and factory reset it the phone.

same problem here, how did you boot safe mode??