Develop Bugs

stuck on BOOT LOOP & cant get into recovery!

Hello guys.... so I flashed a rom about 6 months ago, and yesterday my phone died and when I put it on the charger it was stuck on boot loop. I tried to go into recovery but when I do it also goes into boot loop. I've also tried the ADB command, but it says "Adb is not recoznices as an internal or external commad operable program of bactch file" so i'm out of ideas right now..i can't really flash another rom if I can't get into recovery can anybody help me? thanks in advance...

jy_ventura said:
Hello guys.... so I flashed a rom about 6 months ago, and yesterday my phone died and when I put it on the charger it was stuck on boot loop. I tried to go into recovery but when I do it also goes into boot loop. I've also tried the ADB command, but it says "Adb is not recoznices as an internal or external commad operable program of bactch file" so i'm out of ideas right now..i can't really flash another rom if I can't get into recovery can anybody help me? thanks in advance...
Click to expand...
Click to collapse
In fastboot, you can only use fastboot commands. Choose fastboot from the HBOOT menu, and when connected to your computer, it should say "FASTBOOT USB." Then, you should be able to do a "fastboot devices," and your device should show up. Please provide the output of "fastboot getvar all" and we can better judge how to proceed.

Captain_Throwback said:
In fastboot, you can only use fastboot commands. Choose fastboot from the HBOOT menu, and when connected to your computer, it should say "FASTBOOT USB." Then, you should be able to do a "fastboot devices," and your device should show up. Please provide the output of "fastboot getvar all" and we can better judge how to proceed.
Click to expand...
Click to collapse
It says
***unlocked***
Supersonic evt3 ship s on
Hboot- 2.18.0001
Microp-041f
Touch panel-atmel224_16ab
Radio-2.15.00.12.19

jy_ventura said:
It says
***unlocked***
Supersonic evt3 ship s on
Hboot- 2.18.0001
Microp-041f
Touch panel-atmel224_16ab
Radio-2.15.00.12.19
Click to expand...
Click to collapse
That's not what I asked for, but it might be enough. You'll need to relock the device (fastboot oem lock) and then flash the 5.07.651.1 firmware.zip via RUU mode.
Here's the file you need to download, and place the file in the same folder on your computer from which you're running fastboot.
So, after relocking, at the command prompt reboot to RUU mode.
Code:
fastboot oem rebootRUU
Then flash the firmware zip.
Code:
fastboot flash zip firmware.zip
Once complete, the command prompt will come back, and you can reboot back to the bootloader.
Code:
fastboot reboot-bootloader
At this point, you will have the stock recovery, and hopefully it'll boot into it. So, when you get back to HBOOT, choose the "RECOVERY" option. If all is well, you'll get the red triangle with exclamation point, which is the stock recovery. Press both volume buttons and the power button at the same time to bring up the menu, and choose the option to reboot the device now. Hold the volume down button immediately after choosing to reboot so you can get back into HBOOT.
From there, you just have to unlock again, and then you should be able to flash a custom recovery.
Make sure you are running these commands from the folder with fastboot.exe in it. Otherwise they will give you the error you mentioned in your OP.

This may sound dumb but im having a problem relocking the device. My computer is not registing my phone.
Captain_Throwback said:
That's not what I asked for, but it might be enough. You'll need to relock the device (fastboot oem lock) and then flash the 5.07.651.1 firmware.zip via RUU mode.
Here's the file you need to download, and place the file in the same folder on your computer from which you're running fastboot.
So, after relocking, at the command prompt reboot to RUU mode.
Code:
fastboot oem rebootRUU
Then flash the firmware zip.
Code:
fastboot flash zip firmware.zip
Once complete, the command prompt will come back, and you can reboot back to the bootloader.
Code:
fastboot reboot-bootloader
At this point, you will have the stock recovery, and hopefully it'll boot into it. So, when you get back to HBOOT, choose the "RECOVERY" option. If all is well, you'll get the red triangle with exclamation point, which is the stock recovery. Press both volume buttons and the power button at the same time to bring up the menu, and choose the option to reboot the device now. Hold the volume down button immediately after choosing to reboot so you can get back into HBOOT.
From there, you just have to unlock again, and then you should be able to flash a custom recovery.
Make sure you are running these commands from the folder with fastboot.exe in it. Otherwise they will give you the error you mentioned in your OP.
Click to expand...
Click to collapse

jy_ventura said:
This may sound dumb but im having a problem relocking the device. My computer is not registing my phone.
Click to expand...
Click to collapse
Do you have the correct drivers installed (or any drivers)?
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
These drivers should work: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

i have all drivers and i reinstalled just in case but i only get as far as it saying hboot usb plug on my phone but it doesnt pop up and open in my computer
Captain_Throwback said:
Do you have the correct drivers installed (or any drivers)?
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
These drivers should work: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse

jy_ventura said:
i have all drivers and i reinstalled just in case but i only get as far as it saying hboot usb plug on my phone but it doesnt pop up and open in my computer
Click to expand...
Click to collapse
For the purposes of this exercise, you need to select "FASTBOOT". Once you select that, it should change from FASTBOOT to FASTBOOT USB if the drivers are installed correctly.
Nothing is supposed to open on your computer - I'm not sure what you mean by that. You have to open a command prompt, and navigate to the location of fastboot.exe on your computer, which you're presumably downloaded previously.

Im not sure what I meant either sorry its been a long day. So, okay I have the correct drivers because it does say FASTBOOT USB but when I try in that command i get an error message stating it's not recognize internal or external.
Captain_Throwback said:
For the purposes of this exercise, you need to select "FASTBOOT". Once you select that, it should change from FASTBOOT to FASTBOOT USB if the drivers are installed correctly.
Nothing is supposed to open on your computer - I'm not sure what you mean by that. You have to open a command prompt, and navigate to the location of fastboot.exe on your computer, which you're presumably downloaded previously.
Click to expand...
Click to collapse

jy_ventura said:
Im not sure what I meant either sorry its been a long day. So, okay I have the correct drivers because it does say FASTBOOT USB but when I try in that command i get an error message stating it's not recognize internal or external.
Click to expand...
Click to collapse
Again, you have to run the command from the folder with fastboot.exe in it. Are you doing that? Please provide a screenshot of the folder contents and the command prompt.

I dont think I am because this is literally what i have the phone plugged into my pc and then I have command prompt running.... so when you say i have to run the command from the folder...i guess i'm lost as in what folder since my phone is on the screen that says fastboot usb... sorry! noob completely!
Captain_Throwback said:
Again, you have to run the command from the folder with fastboot.exe in it. Are you doing that? Please provide a screenshot of the folder contents and the command prompt.
Click to expand...
Click to collapse

jy_ventura said:
I dont think I am because this is literally what i have the phone plugged into my pc and then I have command prompt running.... so when you say i have to run the command from the folder...i guess i'm lost as in what folder since my phone is on the screen that says fastboot usb... sorry! noob completely!
Click to expand...
Click to collapse
Have you downloaded fastboot to your computer?
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
You can download fastboot from here: https://www.htcdev.com/process/legal_fastboot_win
Wherever you save that is the folder you need to open the command prompt from, and where you need to put the firmware zip file.

no i havent....but i have it now... its done downloading now
Captain_Throwback said:
Have you downloaded fastboot to your computer?
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
You can download fastboot from here: https://www.htcdev.com/process/legal_fastboot_win
Wherever you save that is the folder you need to open the command prompt from, and where you need to put the firmware zip file.
Click to expand...
Click to collapse

So I downloaded it but I keep getting an error message that it cannot start due to adbwinapi.dll is missing. Ive reinstalled it a few times....im lost completely
Captain_Throwback said:
Have you downloaded fastboot to your computer?
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
You can download fastboot from here: https://www.htcdev.com/process/legal_fastboot_win
Wherever you save that is the folder you need to open the command prompt from, and where you need to put the firmware zip file.
Click to expand...
Click to collapse

jy_ventura said:
So I downloaded it but I keep getting an error message that it cannot start due to adbwinapi.dll is missing. Ive reinstalled it a few times....im lost completely
Click to expand...
Click to collapse
You shouldn't be running anything related to adb. Just follow my instructions. Everything I said is for fastboot, not adb.

I really dont know what im doing wrong I downloaded the fastboot and then the filmware i put them both in one same folder and then when command prompt came up i got an error...idk what im doing wrong!
Captain_Throwback said:
You shouldn't be running anything related to adb. Just follow my instructions. Everything I said is for fastboot, not adb.
Click to expand...
Click to collapse

jy_ventura said:
I really dont know what im doing wrong I downloaded the fastboot and then the filmware i put them both in one same folder and then when command prompt came up i got an error...idk what im doing wrong!
Click to expand...
Click to collapse
What do you mean when the command prompt came up? I asked for screenshots for this reason. Difficult to be able to determine the issue if you don't provide enough information.

Okay back to the start, I have both files in one folder....do I extract?
Captain_Throwback said:
What do you mean when the command prompt came up? I asked for screenshots for this reason. Difficult to be able to determine the issue if you don't provide enough information.
Click to expand...
Click to collapse

jy_ventura said:
Okay back to the start, I have both files in one folder....do I extract?
Click to expand...
Click to collapse
Extract the fastboot zip.

Okay I extracted files now im here...
Do I run fastboot?
Captain_Throwback said:
Extract the fastboot zip.
Click to expand...
Click to collapse

How to restore Download Mode if all you have is Fastboot

This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here

Artifesto said:
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Click to expand...
Click to collapse
How would one go about repairing a broken download mode when all I can do is boot into a broken recovery? I cannot issue any fastboot commands as the device is only recognized as an ADB Bridge device. Are there ADB equivalent commands to accomplish the same things as you have detailed here?
SPRINT LS980 (was on Rooted Stock C and borked phone with D OTA) and a broken TWRP 2.7.1.0 Recovery

natefuhr said:
How would one go about repairing a broken download mode when all I can do is boot into a broken recovery? I cannot issue any fastboot commands as the device is only recognized as an ADB Bridge device. Are there ADB equivalent commands to accomplish the same things as you have detailed here?
SPRINT LS980 (was on Rooted Stock C and borked phone with D OTA) and a broken TWRP 2.7.1.0 Recovery
Click to expand...
Click to collapse
well you should never install any OTA with a custom recovery install. you should always keep at least one backup on your phone to restore to in these events. but i would try downloading a rom and installing via sideload before nuking any partitions. which is easy with TWRP. the sideload menu should be in Advanced then ADB Sideload and the command is adb sideload filename.zip and it will take awhile depending on the file size. make sure the file name is simple and it is placed in the folder you are running the sideload from.

Artifesto said:
well you should never install any OTA with a custom recovery install. you should always keep at least one backup on your phone to restore to in these events. but i would try downloading a rom and installing via sideload before nuking any partitions. which is easy with TWRP. the sideload menu should be in Advanced then ADB Sideload and the command is adb sideload filename.zip and it will take awhile depending on the file size. make sure the file name is simple and it is placed in the folder you are running the sideload from.
Click to expand...
Click to collapse
Yes yes I know... it was a moment of weakness late at night and I didn't think before telling the girl to go ahead and upgrade. That being said... Part of the problem now is that the one backup she made just up and disappeared. The ADB sideload option just hangs and never actually does anything. The original Stock Rooted file I had still on the sd partition doesn't fix the issue when I flash it... it looks like it flashes ok but on the next boot it just drops me back into TWRP right where I began. And download mode is still borked.
So let's talk thermonuclear resolution on this motherlover.... where do I begin?
Sent from my SM-N900P using Tapatalk

natefuhr said:
Yes yes I know... it was a moment of weakness late at night and I didn't think before telling the girl to go ahead and upgrade. That being said... Part of the problem now is that the one backup she made just up and disappeared. The ADB sideload option just hangs and never actually does anything. The original Stock Rooted file I had still on the sd partition doesn't fix the issue when I flash it... it looks like it flashes ok but on the next boot it just drops me back into TWRP right where I began. And download mode is still borked.
So let's talk thermonuclear resolution on this motherlover.... where do I begin?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
hmmmmm.... I've been able to get my G2 into fastboot by holding Volume + and Pwr after it setting for awhile turned off.. may be stupid but have you tried that button combo or Volume + and Volume - with Pwr

Could u tell me the command cause i went adb sideload filename.zip and it comes up file not found and i put it in my platform-tools folder any ideas i have adb version 1.30...it was above the version that they said you need on the twrp site
whatsamatta u alumni 1990-2011

Fastboot???
Artifesto said:
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Click to expand...
Click to collapse
How do I get to fastboot. I can get to recovery but that's it. Download is not working. The Vol+/- and Power just gets me to key controls.

deathsquad737 said:
Could u tell me the command cause i went adb sideload filename.zip and it comes up file not found and i put it in my platform-tools folder any ideas i have adb version 1.30...it was above the version that they said you need on the twrp site
whatsamatta u alumni 1990-2011
Click to expand...
Click to collapse
i would try to rename your rom to something simple, like rom.zip. there cannot be any spaces in the name and it does need to be in the same folder you run the command from like you seem to be doing.
gelito81 said:
How do I get to fastboot. I can get to recovery but that's it. Download is not working. The Vol+/- and Power just gets me to key controls.
Click to expand...
Click to collapse
did you try vol+ and power together? When a functioning rom is installed it asks to do a factory reset but it may get into fastboot if you nuked that partition. i haven't tried this yet but if you're in adb sideload in twrp maybe the command
Code:
adb reboot fastboot
might help

Artifesto said:
i would try to rename your rom to something simple, like rom.zip. there cannot be any spaces in the name and it does need to be in the same folder you run the command from like you seem to be doing.
did you try vol+ and power together? When a functioning rom is installed it asks to do a factory reset but it may get into fastboot if you nuked that partition. i haven't tried this yet but if you're in adb sideload in twrp maybe the command
Code:
adb reboot fastboot
might help
Click to expand...
Click to collapse
Tried all of the above.... they all just send me into recovery or broken download mode
damn

I'm screwed. I gave this a try and now all I get is a black screen. The phone will connect to my computer but I can't send any commands to it through the command prompt. When it connects to the computer it opens a bunch of different drives and says I need to format them. I can't get into download mode and when I try to send a command in the prompt it just says waiting for device. Any ideas?
Edit: It shows up in device manager like this: http://i.imgur.com/NXGxpcX.png

http://forum.xda-developers.com/showthread.php?t=2582142 try that
Sent from my VS980 4G using XDA Free mobile app

how i can enter in FASTBOOT mode ?

I'm not sure if you can help me here. I have a Verizon G2 and am trying to reset to factory for a repair. I am trying to get into download mode, but only get fastboot when pressing volume up while powered off and plugging in my USB cord. Any help would be greatly appreciated.

razer_ins said:
how i can enter in FASTBOOT mode ?
Click to expand...
Click to collapse
Flash xdabbbeb 24a bootstack zip
WHATSAMATTA U ALUMNI
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Crossxcalibur said:
I'm not sure if you can help me here. I have a Verizon G2 and am trying to reset to factory for a repair. I am trying to get into download mode, but only get fastboot when pressing volume up while powered off and plugging in my USB cord. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Read 2 post above yours i answered your ?
WHATSAMATTA U ALUMNI

For everyone who is having issues with drivers see the video below to get fastboot to work:
https://www.youtube.com/watch?v=NaK5OxUeDKM

[Q] Help Hard Brick!

Hi, I hope you can help me.
I was charging my phone, but when I wanted to turn it on, it gets stuck on the huawei screen. So I try to enter to the recovery, I have installed Open TWRP 2.8, but nothing, it gets stuck too, on the TWRP logo. So I decided to flash a stock recovery, I put the phone in fastboot mode, try to flash the recovery and apparently it worked all right but when I try to enter to the recovery, returns to TWRP, and no matter what recovery and how many times I flash returns to TWRP. It's like the phone is in read-only mode because don't flash.
Something else, when is stuck on the TWRP logo, I can use ADB commands and shell.
Any idea to recover my phone? now I'm desperate....
Thank you very much in advance.
P.D. sorry for my bad English....

try to flash twrp 2.7 (or other older version of twrp then yours) instead of stock recovery or reflash 2.8.1 even you are already on it... i had the similar problem

mlsvcbbn said:
try to flash twrp 2.7 (or other older version of twrp then yours) instead of stock recovery or reflash 2.8.1 even you are already on it... i had the similar problem
Click to expand...
Click to collapse
I try but nothing, maybe it's screw up the partitions on my internal storage card? ...I don't know...any idea?

can you enter into twrp menu?

mlsvcbbn said:
can you enter into twrp menu?
Click to expand...
Click to collapse
No, it stays in the splash screen, but I can enter to ADB.

then try to type cmd: adb reboot bootloader (press enter) then : fastboot flash recovery (name of your twrp. img) (enter) then: adb reboot recovery (enter)
---------- Post added at 04:34 PM ---------- Previous post was at 04:30 PM ----------
but first of all, type: adb devices (enter), to see if your phone is recognized

mlsvcbbn said:
then try to type cmd: adb reboot bootloader (press enter) then : fastboot flash recovery (name of your twrp. img) (enter) then: adb reboot recovery (enter)
---------- Post added at 04:34 PM ---------- Previous post was at 04:30 PM ----------
but first of all, type: adb devices (enter), to see if your phone is recognized
Click to expand...
Click to collapse
I try that before (with stock recovery and with another/same version of twrp), but don't flash the recovery, it seems that it does all right but always return to TWRP.
When the phone it's in booloader mode, the "devices" command show ??????6? but in adb show the correct number.

very strange...

chudo51 said:
I try that before (with stock recovery and with another/same version of twrp), but don't flash the recovery, it seems that it does all right but always return to TWRP.
When the phone it's in booloader mode, the "devices" command show ??????6? but in adb show the correct number.
Click to expand...
Click to collapse
The output that you get in fastboot is ok that means that you can operate with fastboot commands, now the thing is that you try to flash something successfully. For that i would recommend you to use the update extractor from the forum and get .img files from an update and then try to flash them in fastboot.
This is a little tutorial for you to get through fastboot commands, where i would suggest you to wipe all before flashing. And most important thing is to not reboot until you flashed all.
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my SM-G850F

tileeq said:
The output that you get in fastboot is ok that means that you can operate with fastboot commands, now the thing is that you try to flash something successfully. For that i would recommend you to use the update extractor from the forum and get .img files from an update and then try to flash them in fastboot.
This is a little tutorial for you to get through fastboot commands, where i would suggest you to wipe all before flashing. And most important thing is to not reboot until you flashed all.
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my SM-G850F
Click to expand...
Click to collapse
Thanks, but the phone no flash, I try to many times but nothing. Even I try with adb to push files but if I reboot the phone, the files are not saved, so I think is something with the internal memory. It's a shame but I'll have to buy another one.

maybe after factory reset your bootloader is somehow in locked state ...

[Q] Random Reboots on ZF2 4gb/32gb

Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.

Suhas_JS said:
Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.
Click to expand...
Click to collapse
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.

kibmikey1 said:
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.
Click to expand...
Click to collapse
Just hard reset or complete wiping of cache, dalvik, data, root and then reload the stock/pre-rooted ROM?

It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.

Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app

i suspect this has alot to do with android 5.0. asus needs to work on getting 5.1 to the device.

Suhas_JS said:
Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
what rom did you install? latest or stock?
did you follow the step one or alternative??
please help me i got the same problem.

kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
stock ROM from Asus[/URL] or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
---------- Post added at 06:54 PM ---------- Previous post was at 06:48 PM ----------
kowsar684 said:
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
Click to expand...
Click to collapse
no problem is still there ...... should i install pre root rom???
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
what is the difference between stock ROM and pre root ROM???

can't install stock rom. how to flass

kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
Thanks a million man.
This saved me instead of sending back the phone rto newegg after a failed cache format.
Repped!!!

I have folowed all step successfuly but reboots are still there, i can't do **** about them, mostly happen installing / updating apps and playing games, sometime it's just random, listening music.

more ideas about why it's happen?

I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.

sandozer said:
I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.
Click to expand...
Click to collapse
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD

Anyone get a random shutdown with the 2.19.40.20 firmware? Happened to me overnight/this morning, at 98 to 96% charge. First time this has happened with this device.
No last_kmsg to share, so will keep a watch on it for now...
Edit: happened a second time, this afternoon. Maybe I will upgrade to 2.19.40.22, or at least install TWRP to see if I can grab a last_kmsg (if I can find it) to see what's going on..

chooks06 said:
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .

@sandozer..5.1 will do a lot of good for a lot of people

sandozer said:
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .
Click to expand...
Click to collapse
If you have not tried resetting the phone, it may be worth a try, though painful to start setting up all over again. You can try using the stock ASUS back up app to do your back up..
Sent from my ASUS_Z00AD

I am on 22 and have random reboots as well?

I had 2 random reboots on the 2gb/16gb version, but I think it was USB cable related. I'd plug the phone into the car and do something fast and then lock it, POOF! Reboot. It hasn't happened in awhile though and I believe I did an OTA update afterwards.

Help I bricked my Oneplus 3

Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))

have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.

bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)

Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs

bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?

Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.

simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"

Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?

ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol

bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?

gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs

Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something

simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))

Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.

simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?

Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..

jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...

simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english

Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.

can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!