hello
i reinstalled my ROM after installing FREEDOM and the google play wasn't working
i installed it about a month ago and it worked out fine, i rooted the phone again but didn't do anything with it
today after using the phone for a couple of hours i plagged the charger in and then i saw that the screen is all black
and all that says is :
fastboot mode started
udc start
i tried everything with the power + vol down and it keeps getting into the same screen
the phone just stuck in this and i can't recover it
i have read the other questions that people wrote here about this problem and couldn't find an answer
PLEASE HELP ME SOLVE THIS!!!
nir3011 said:
hello
i reinstalled my ROM after installing FREEDOM and the google play wasn't working
i installed it about a month ago and it worked out fine, i rooted the phone again but didn't do anything with it
today after using the phone for a couple of hours i plagged the charger in and then i saw that the screen is all black
and all that says is :
fastboot mode started
udc start
i tried everything with the power + vol down and it keeps getting into the same screen
the phone just stuck in this and i can't recover it
i have read the other questions that people wrote here about this problem and couldn't find an answer
PLEASE HELP ME SOLVE THIS!!!
Click to expand...
Click to collapse
I was in the same situation tonight. I have the AT&T variant. I found the answer on droidforum(dot)net by member HARVESTERX:
"OK, so you're booting into fastboot and trying to ADB from there? Have you tied booting into recovery (since you said that you were able to successfully flash one)? I'm on the Verizon G2 so not too familiar if it's the same on your model, but to get into recovery I power on the phone by pressing and bring the power and volume - buttons at the same time. After seeing the LG logo I have to release both buttons and press and hold power and volume - once more which takes me into the factory reset mode. From here press the power button a few times as if I'm doing a factory reset and it loads up TWRP from there.
This has saved my ass once already because I wiped my internal storage mount by accident and deleted all my backups and ROMs, so I used a Windows XP computer (can't get any other version of Windows to recognize my device...well I know how but it involves more time than I have at the computer as it's not mine) and pushed a ROM over using ADB that way. It's been a few days so hopefully you've fixed the issue... "
This method put me into TWRP and I was able to RESTORE my phone to the backup I had done earlier this evening.
I hope this helps!
JACE759
Hi all
First of all sorry for asking this question but after search for hours I have come across no answers.
My device wont boot, it gets stuck on the LG logo. I also cant seem to boot in Download mode to restore back to stock. The device in a G2 International and is unlocked. I have installed PC drivers etc but will not work. I turn off device completely, even tried disconnecting battery on mother board, and pressed up to boot in DL mode but it will not work just boot into LG logo again. Now i CAN get in the restore hard reset screen by pressing power and V down but it stays on the device restore screen after I have pressed power button a couple of times. Also PC will now see device when in this mode either.
Any help or pointing in the right direction would be a lot of help.
Attached are two images
Thanks You XDA community
Rueben
Rueben_ said:
Hi all
First of all sorry for asking this question but after search for hours I have come across no answers.
My device wont boot, it gets stuck on the LG logo. I also cant seem to boot in Download mode to restore back to stock. The device in a G2 International and is unlocked. I have installed PC drivers etc but will not work. I turn off device completely, even tried disconnecting battery on mother board, and pressed up to boot in DL mode but it will not work just boot into LG logo again. Now i CAN get in the restore hard reset screen by pressing power and V down but it stays on the device restore screen after I have pressed power button a couple of times. Also PC will now see device when in this mode either.
Any help or pointing in the right direction would be a lot of help.
Attached are two images
Thanks You XDA community
Rueben
Click to expand...
Click to collapse
You didn't specify if you were using a Windows PC, or a Linux OS. A Linux operating system could see the device even when Windows doesn't. Using Linux and the ADB toolkit - I would push a custom recovery to the device and then reboot into the new recovery. After that it should be easy to mount the device and install a new ROM.
Ah! Reading again, I see "installed drivers", so you must be using Windows. Try using Linux.
Thanks, so I tired the unbrick method of short circuiting the mother board and then using linux to see the partions push aboot, boot and laf img this allowed me to boot into download mode and then using flash tool to flash a UK based 4.2.2 ROM the device is now working perfectly. Thanks for you help. MOD you can close this thread now.
Link for method I used here.
================================
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
So here is my sadness. i got my Zenfone2 back Z00A (ME551L) from having the screen repaired from asus themself. it was sluggish so i factory reset and it corrupted. i tried to flash the stock ram but then it went to hell. long story short i ended up wiht the White USB screen which means hard brick(correct if im wroong). i followed http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 to try and get it back to normal. the 1st time it flashed it worked in the Downloader (FW+OS complete). But when using Flash tools it hung up on the yellow flash button. I have no clue what happend. I try to start from the beggining but it wont complete like it did at 1st. So im stuck with the 4 color boot to fastboot. Wont connect to ADB so i cant sideload or recover from ADB in recovery. any help plz. i just miss my zenfone 2 ahha.
so in recap:
It wont flash fully in Flashtools 1.14.
Wont FW+OS complete in the downloader tool(only FW finishes)
No recovery mode options like it disappeared
When i let it boot normal it says updating with the android guy for 30 seconds then goes to dead guy with error.
plz any help would be outstanding and helpful
fuzydino said:
So here is my sadness. i got my Zenfone2 back Z00A (ME551L) from having the screen repaired from asus themself. it was sluggish so i factory reset and it corrupted. i tried to flash the stock ram but then it went to hell. long story short i ended up wiht the White USB screen which means hard brick(correct if im wroong). i followed http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 to try and get it back to normal. the 1st time it flashed it worked in the Downloader (FW+OS complete). But when using Flash tools it hung up on the yellow flash button. I have no clue what happend. I try to start from the beggining but it wont complete like it did at 1st. So im stuck with the 4 color boot to fastboot. Wont connect to ADB so i cant sideload or recover from ADB in recovery. any help plz. i just miss my zenfone 2 ahha.
so in recap:
It wont flash fully in Flashtools 1.14.
Wont FW+OS complete in the downloader tool(only FW finishes)
No recovery mode options like it disappeared
When i let it boot normal it says updating with the android guy for 30 seconds then goes to dead guy with error.
plz any help would be outstanding and helpful
Click to expand...
Click to collapse
Check my signature below...charge fone after flashing in xfstk,when in bootloader , select power off and charge.
read all the thread
timbernot said:
Check my signature below...charge fone after flashing in xfstk,when in bootloader , select power off and charge.
read all the thread
Click to expand...
Click to collapse
awesome your are my hero . worked like a charm!
Marvelous stuff
Hello Fellows,
First I'd like to explain my situation in details.
my phone fell while i was walking on the street and it got some dirt on it, so ( foolishly ) I decided to clean it.... and yeah... i washed my phone like washing a dish... i like rinsed the phone in water and in other cleaning liquids for no more than 3 seconds it was all quick thingy... anyway after washing it.... i directly powered it ON and it powered but the screen was OFF ( so i decided to power it OFF, solder it and to remove any clues of water inside on the board or something... after that i used a hairdryer ( which is not recommended ) but i used it at a descent distance so that no harm would be caused to the board... as i was only subjecting air to let water if any existed to dry..
i put the phone in rise and kept it for 1 day... after 1 day i wanted to check out how stuff went.. so i powered it ON and the screen actually turned ON and the vibrator, even the hardware back-light lighted up perfectly but here's the problem I'm facing.
the phone only boots into TWRP 3.1.0.0 no matter what i do.. things i tried:
1- flashed some ROM, through TWRP
2- used "Fixed Contexts" in TWRP
3- Repair File System "System partition" through TWRP
4- used file manager inside TWRP and checked if the internal storage is working and indeed i can show all my files, through TWRP
5- also used the file manager to access "System" Partition and everything was there, through TWRP
6- change File System into EXT4 "System partition" through TWRP
7- Resize File System "System partition" through TWRP
8- Wiping all Partitions "Excluding the internal storage"
and NON WORKED..
note that whenever i attempt to flash a ROM the result shows successful with no errors ..
so whats the problem in here?
i have a guess but i need help in order to apply it.. i think the VOL- is pressed and stuck somehow Electrically on the board ( but no physically as i can press the volume down and hear its tap or whatever you call it.. i even managed to boot into fast-boot and it worked.
is there anyway i can disable the vol- button temporary to see if its causing the problem?
the only thing is i cant see my ROM booting... not even the boot animation showing... just the boot-loader and automatically it goes into the recovery
also i have kernel log attached below followed by the recovery log
EDIT: i also forgot to mention that my PC recognize the phone and i have access to my internal storage.. no problems with transfer speed as well
after tons of attempts and searching online and flashing stuff and blablabla... (i flashed every recovery image op2 support )
FINALLY
I found the solution my self, and everything is back to normal...
the phone was stuck at the early stage of the booting process and maybe couldn't find the boot image in order to boot up the android OS, so all i did was i plugged in the phone into the PC, i started everything in fastboot mode on phone and on PC then i just sent the following command to my phone.
Code:
fastboot continue
fastboot then(meaning after the command) wasnt able to recognize the phone anymore so i knew that its now trying to search for partitions other than recovery.. i waited like 10 seconds and booom it booted into the best ROM i've ever used ( and actually missed ) which is Official RR from our great maintainer "nicesoni_ash"
P.S: the vol- as i said was really stuck and i noticed it not working while on RR ROM, so i just clicked it many times and tried mixing vol+ with vol- .. after many many attempts vol- worked and i then rebooted to make sure if everything is back to normal and no recovery auto boots and indeed it smoothly booted up :laugh:
thanks a lot for all who tried to help out in here or on oneplus forums :highfive:
#back_to_resurrect_and_will_always_remix
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I would consider it as bricked, after all attempts failed and go with the unbrick guide here on xda or oneplus forums, maybe this way it can be ressurected.
You probably have already backed up your data..
Damn, that hurts..
mithu.creative said:
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Click to expand...
Click to collapse
sorry for this late reply but yes i have tried flashing every ROM from stock to Custom ones even i flashed EVERY SINGLE RECOVERY IMAGE OUR PHONE SUPPORTS XD and non worked... first aid.. qualcomm toolkit... non...
hello bro, i updated a magisk module v4android and when i reboot, it boots up in twrp. and since then it keeps booting into twrp. So, i used fastboot continue and when it boot int the home i deleted that module.
but fastboot continue only works once. After that if i switch-off and switch-on the phone, it goes into twrp. it needs fastboot continue everytime.
please provide me a permanent solution. few other users are facing this too. plz reply i'm waiting.
Hey,
with the help of some others in a Discord server (thanks @thesanjayp#6251 on discord) i managed to find the issue. Appearantly there was a change in /dev/block/bootdevice/by-name/misc for some reason. There was a similar problem on the old LG Optimus G Pro which i owned, so i remembered this.
As I'm not sure if we can just wipe the partition or not, i got a working misc.img attached.
In any terminal (adb shell, twrp terminal or an terminal app in a rom) make sure you have su rights, and then execute the following command:
Code:
dd if=/path/to/misc.img of=/dev/block/bootdevice/by-name/misc
Make sure to adapt the path to the misc.img though to the location you saved it to.
The misc.img I used is attached to this post.
PS: Im not responsible for any broken phones if this didnt work for you.