Related
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
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 ...
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!
SOLVED
I can't boot into recovery (op logo displayed for about 10 seconds, then the screen became black)
ore boot the system (op logo is displayed for about 0.1 seconds, then the screen became black)
i've already tried to follow the steps in Mega Unbrick Guide, but i can't "Make the device show as Qualcomm 9008" also after have followed the
appropriate guide)
please help me!
if someone succeeds to solve the problem i'll pay him/her via paypal
Thaks!!
Go to Oneplus website and download oxygen os version 3.2.4 OTA and flash that via adb sideload , also as a sidenote use your PC to boot into fastboot mode and try flashing the firmware that way if the first method doesn't work....
how?
Xceeder said:
Go to Oneplus website and download oxygen os version 3.2.4 OTA and flash that via adb sideload , also as a sidenote use your PC to boot into fastboot mode and try flashing the firmware that way if the first method doesn't work....
Click to expand...
Click to collapse
i can't flash via adb sideload because i have can't boot into recovery.
How can i flash into fastboot mode? what have i to tipe?
Plug phone into PC and type - adb reboot bootloader , this should enter fastboot mode then use the adb commands to flash the firmware which should be adb sideload oxygenos.zip just obviously rename the OTA zip file to oxygenos before running the command... Hope this helps buddy.
What were you doing actually? And is your bootloader unlocked?
Xceeder said:
Plug phone into PC and type - adb reboot bootloader , this should enter fastboot mode then use the adb commands to flash the firmware which should be adb sideload oxygenos.zip just obviously rename the OTA zip file to oxygenos before running the command... Hope this helps buddy.
Click to expand...
Click to collapse
I've tried, but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
cannot read oxigenos.zip
zTweaked said:
What were you doing actually? And is your bootloader unlocked?
Click to expand...
Click to collapse
yes, my bootloader is unlocked,
i've tried to flash via adb but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
"cannot read oxigenos.zip"
i've put the renamed zip on desktop and in "c\program files (x86)\minimal adb and fastboot" directory
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
TheReverend98 said:
yes, my bootloader is unlocked,
i've tried to flash via adb but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
"cannot read oxigenos.zip"
i've put the renamed zip on desktop and in "c\program files (x86)\minimal adb and fastboot" directory
Click to expand...
Click to collapse
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
[email protected] said:
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
Click to expand...
Click to collapse
yes, i'm running the command window from that folder where adb is,
but i've tiped
:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update oxigenos.zip
archive does not contain 'android-info.txt'
error: update package 'oxigenos.zip' has no android-info.txt
because i can operate only in fastboot mode
Are you sure you are typing it right because you keep typing oxigenos instead of oxygenos ...
Xceeder said:
Are you sure you are typing it right because you keep typing oxigenos instead of oxygenos ...
Click to expand...
Click to collapse
oh..sorry! sometimes when i write in english i do some errors with the letters
anyway, this wasn't the problem, 'cause i had renamed the rom's zip in the same way
now i'm booting cm, hope it works all right!
Go to blusparks kernel thread from there download the latest recovery. Boot your phone into fastboot, then flash that recovery. Boot into recovery then flash whatever you wish!
Here is the recovery:
http://forum.xda-developers.com/devdb/project/dl/?id=21065
TheReverend98 said:
oh..sorry! sometimes when i write in english i do some errors with the letters
anyway, this wasn't the problem, 'cause i had renamed the rom's zip in the same way
now i'm booting cm, hope it works all right!
Click to expand...
Click to collapse
Did it work??
Also I just wanted to ask. Were you on the Oxygen OS Community Builds when this happened?
AJay27 said:
Did it work??
Also I just wanted to ask. Were you on the Oxygen OS Community Builds when this happened?
Click to expand...
Click to collapse
yes, anyway, i solved the problem
how did you solved the problem? could you please explain? so that we can solve it if anyone of us faces this problem...
solving
sahed01 said:
how did you solved the problem? could you please explain? so that we can solve it if anyone of us faces this problem...
Click to expand...
Click to collapse
I've installed this tool: http://forum.xda-developers.com/showthread.php?t=2317790
then manually booted the phone into fastboot mode
in the directory of Minimal ADB and Fastboot i've put the twrp-3.0.2-22-oneplus3.img and renamed the file into twrp
then i've flashed the file with this command: fastboot flash recovery twrp.img
once booted into recovery i've paste the cyanogenmod rom file into the phone and installed by the classic way (WIPE cache, sys, data, davilk//INSTALL cm file// OPTIONAL INSTALL gapps, kernel, su)
restart the phone, done!
TheReverend98 said:
I've installed this tool: http://forum.xda-developers.com/showthread.php?t=2317790
then manually booted the phone into fastboot mode
in the directory of Minimal ADB and Fastboot i've put the twrp-3.0.2-22-oneplus3.img and renamed the file into twrp
then i've flashed the file with this command: fastboot flash recovery twrp.img
once booted into recovery i've paste the cyanogenmod rom file into the phone and installed by the classic way (WIPE cache, sys, data, davilk//INSTALL cm file// OPTIONAL INSTALL gapps, kernel, su)
restart the phone, done!
Click to expand...
Click to collapse
.
thank you for sharing this! ?
[email protected] said:
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
Click to expand...
Click to collapse
Hi Gary can you send me the files to email [email protected] because I'm having the same issues. Thanks
So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.
msmall82 said:
So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.
Click to expand...
Click to collapse
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
In fastboot type in fastboot devices and if it comes back with your device number your good to go
mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
Click to expand...
Click to collapse
I know the command I want, I'm asking where I run it from? Do i run it while my phone is in Android connected to my PC or do I run the command from fastboot while my phone is in the bootloader mode??? When I have my phone connected normally and run an "adb devices" it doesn't find my phone but obviously it recognizes my phone otherwise it wouldn't have been able to copy dePixel8 and unlock my bootloader.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????
mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
Click to expand...
Click to collapse
I guess what I am saying is how the heck do I boot into the TWRP IMG ? My bootloader is definitely unlocked, I have SU on my internal storage, I have the IMG in my minimal fastboot folder. I just need to know how the heck to boot into "recovery mode" using the :
fastboot boot "path to".img
If I run that command while my phone is connected normally with USB debugging enabled it just says "waiting for devices"
Am I missing something here...?
[QUOTE.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????[/QUOTE]
Run the command with your phone in bootloader mode and your computer in fastboot
msmall82 said:
So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.
Click to expand...
Click to collapse
First off get rid of minimal. That is not your current problem, but you will have problems later. It is old, it doesn't know about our partitions or handle their larger size. Get googles
https://developer.android.com/studio/releases/platform-tools.html
Put the TWRP img in the same folder, skip the path
Fastboot BOOT {twrpfilename.img}
mac796 said:
[QUOTE.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????
Click to expand...
Click to collapse
Run the command with your phone in bootloader mode and your computer in fastboot[/QUOTE]
You need to follow the steps I gave you. You need su2.79 , and rc1 on your internal storage. Then you need TWRP rc1 boot image on your computer. Put it in your platform tools folder or wherever you got your other firmware. Put phone in bootloader mode, then open a command window where you have TWRP boot image saved , type in fastboot devices, to make sure computer is seeing the phone, then the command should be fastboot boot TWRP.img, then install rc1 off your phone storage, then boot to system once, then boot back to recovery and install su 2.79 sr3
mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
In fastboot type in fastboot devices and if it comes back with your device number your good to go
Click to expand...
Click to collapse
OK I figured it out, while the phone is booted into Android you have to actually issue the command to reboot it into the bootloader mode otherwise it won't detect the phone (at least it wouldn't on my PC)
I ran this command from my minimal fastboot folder (shift + right click -> open command prompt)
I then typed this:
adb reboot bootloader
Then once it is rebooted into bootloader mode issue the
fastboot boot .img command
It then rebooted into TWRP, and I was able to flash the SU zip
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice!
Delete
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice![/QUOTE]
Good deal. Yea I usually use ADB to put phone in bootloader mode it's faster
TonikJDK said:
First off get rid of minimal. That is not your current problem, but you will have problems later. It is old, it doesn't know about our partitions or handle their larger size. Get googles
https://developer.android.com/studio/releases/platform-tools.html
Put the TWRP img in the same folder, skip the path
Fastboot BOOT {twrpfilename.img}
Click to expand...
Click to collapse
Thanks Tonik, got SU on there and all is right with the world, already installing Ti Backup and root explorer and such.....ahhh so relieved.
Love all of you lol
mac796 said:
Delete
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice!
Click to expand...
Click to collapse
Good deal. Yea I usually use ADB to put phone in bootloader mode it's faster[/QUOTE]
Thanks man, I figure other people might run into these problems so I might as well post about them. If I booted directly into the bootloader my PC wouldn't recognize the phone, if I issued the command to reboot it would. Weird...but whatever, I'm unlocked and rooted....
THANK YOU!