Had a problem with audio playback (volume always high no matter what). Decide to flash. PAC for my Sprint LS980. I see this:
Seems to be a lot of confusion so I'll clear things up..
ZV7->ZV8->ZVA is how the ota history goes, with ZVB on the way.
If you're on stock ZVA, your aboot (bootloader) may not be downgraded, in that case, use FreeGee from Play Store to install a recovery, it will automatically downgrade your aboot.
if you have the ZVA Radio, just flash furnace or dr87's kernel after you flash an AOSP ROM, all done.
Click to expand...
Click to collapse
Sorce: http://forum.xda-developers.com/showthread.php?t=2669074
Seeing the last sentance, I think that if I flash ZVA Radio, SlimKat ROM (the one that causes me problems) and then dr87's kernel I could try a ZVA experience. I flashed SlimKat again becuase I was going to change anyway, I wanted to try it with ZVA.
Tell myself why not, I do it.
Fails but I didnt pay much attention. I reboot.
Stuck in fastboot mode and cant escape. Recovery is a no-go.
Tried flashing both ZV7aboot.img and twrp2.6.3.0.img into their appropriate partitions (boot and recovery).
Still having problems, but now I cant do any button combination (except DownloadMode. Cant turn off) after ZV7aboot.img flash.
I dont want to erase my memory (~26GB of valuable data). Is there a way to flash a ZV8Radio.zip from fastboot? I think thats my problem, but Im not too sure. Just access to recovery would allow my to fix my problems.
Thanks anyone for any help! I think I really screwed myself over this time. Thanks everyone!
Edit: Anyone know where to get a boot.img and system.img for the Sprint LS980?
zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.
Savoca said:
zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.
Click to expand...
Click to collapse
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.
RevolcFael4 said:
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.
Click to expand...
Click to collapse
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.
Savoca said:
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.
Click to expand...
Click to collapse
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.
RevolcFael4 said:
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.
Click to expand...
Click to collapse
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2
Savoca said:
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2
Click to expand...
Click to collapse
Thanks for the link! That was extremely helpful.
What I did to gain access to twrp again was:
Download boot.img from the link.
Download aboot.img from link.
Download twrp.img (but this isnt necessary, file is already available on phone. No need.)
* Enter command 'fastboot flash boot boot.img'
* (If you hold power it starts showing LG Logo.)
* Go back to Fastboot. Enter command 'fastboot flash aboot aboot.img'
* Now TWRP access is regained! Phone doesnt boot normally, must flash ROM and stuff again.
Thanks a lot! This was an okay first fastboot experience.
Soft Bricked Sprint LS980?
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
Click to expand...
Click to collapse
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
x_lord said:
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
Sorry for not replying, but I see you managed to fix your problem. All you needed to do was download .img files, then enter commands through fastboot. Although it is slightly more complicated than that, its the rough outline of what needs to be done to fix it. Nice work fixing your problem. I came back to this thread to remind myself of the commands that need to be entered (My comments help myself).
I think I am just going to copy-paste the quoted box above if anyone needs instructions how to do this. Thanks for the quick guide I can use to help others!
bricked , simple fix?
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible
True2This said:
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible
Click to expand...
Click to collapse
Sorry, I barely understood what to do originally. What you have to do next is to reflash the aboot/boot/ whatever partitions but getting to that position might be difficult. Maybe some sort of command would allow you to connect to it oncemore?
Sorry, try to look into it more and see if a dev could help. Try posting something in /r/lgg2 but then again I cant be certain anything would happen. Good luck!
Easy guide
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!
Unbrick Ls980 formatting partitions
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
RevolcFael4 said:
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!
Click to expand...
Click to collapse
i tried this with almost all model files but still on fastboot any other option?>
I want to say thank you so much for this thread. Just got a new (refurb) G2 switching carriers to T-Mo and my idiot self used the wrong root program and soft bricked to fastboot. 4 .img files later and a few commands and I don't think I've ever been so happy to see a download screen on a phone...
juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
GREAT, You are a life saver :laugh:
juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
wow.. worked flawlessly... thank you very much :good::good::laugh::laugh:
Hi guys,
yesterday I accidentally wiped my phone and the rom's in it. So now I have to somehow get a rom on the sd card so I can flash it. Recovery works (twrp), fastboot mode works, however I can't use adb to push zips on to my sd card, I've tried on 3 different PC's 2xWindows and one mac
fastboot finds my device and adb doesn't. I've tried configuring the adb_usb.ini file with the Vendor ID of my device which I found, but adb still doesn't find it. My system is wiped so I don't have a system to go in and transfer files the normal way and my backups have been deleted so that isnt working either. I've also tried to return my phone to 100% stock with a tool I found on the OnePlus forums Thread from forum , however this didn't work fastboot crashes midway. My only option is to flash an .img file containing some system rom(which I didn't find) so I can then load files to my sd card or to get adb to work in some way so I can push the zips on to the sd card. If you can help in any way because I'm all out of ideas. It's been two hard days and this is the last thing I'm trying, otherwise I have to buy a new phone.
It's not soft bricked but I think the first method shown here could work:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Sounds like your trying to access your phone using ADB in fastboot, this will not work. For ADB recovery, you have to enter TWRP or CWM and choose ADB sideload mode to activate phone for receiving of ROM zip using adb sideload romfile.zip. Fastboot is like EFI or BIOS boot prompt on a PC, and ADB is like a variant of GRUB bootloader with support for PXE installing the phones OS by ways of adb sideload (as reference).
Hello, folks.
I'm still new to all this and I'm completely stuck trying to get TWRP installed. Gone through all the steps, and everything I could find on Google as well, yet fastboot won't do anything for me.
What I've been trying is: adb devices shows device, reboot bootloader boots into download mode, fastboot devices returns nothing, fastboot flash recovery twrp.img(4.4, hopefully the right one?) returns waiting for any device.
Rooted and bootloader is unlocked, twrp file is in same folder as adb and fastboot which is where admin cmd prompt is open to.
I've downloaded the samsung and google drivers.
Confirmed device is recognized in device manager.
Tried different USB ports.
Tried installing via the TWRP manager app, get an error installing any version.
Feels like I must be missing something stupid. Just trying to get a new ROM to hopefully speed this thing up.
Thanks for any advice!
EDIT - skip to bottom
The use of fastboot to interact with bootloader firmware is NOT universal among Android handset makers.
In particular, Samsung. Fastboot hasn't worked with Samsung android devices for a long time (it possibly never did).
The nearest analagous equivalent is Samsung's "Odin" software (for Windows PCs).
There is also "heimdal" for *nix machines which attempts to replicate the behaviors of Odin.
The handset boot mode most closely corresponding to "fastboot" is Samsung's "Download" (or "Odin") mode. On the Note 3 you enter that mode from a cold start with a three-finger salute: Vol-Down+Home+Power. A splash screen will show up allowing you to "Cancel" (normal boot) or "Download" mode.
It is harmless to enter that mode if you want to look at what the screen looks like, but you might have to pull the battery to get out of it if you don't use Odin.
Search XDA for "Odin" ( or heimdal), you will find plenty of posts
Flashing TWRP:
The TWRP images are not filesystems, but just a large (bootable) binary blob file (containing a kernel, ramdisk, and device tree).
That means you can simply use the "dd" command (as the root user) to write the .img blob into the recovery partition, using a shell/ terminal. Could be using either adb or a terminal emulator app. You just need to have a root prompt.
Obviously you need to be cautious about this, making sure you are blasting bits into the correct partition (the recovery partition).
e.g. see
ls -ld /dev/block/platform/msm_sdcc.1/by-name/*
bftb0 said:
EDIT - skip to bottom
The use of fastboot to interact with bootloader firmware is NOT universal among Android handset makers.
In particular, Samsung. Fastboot hasn't worked with Samsung android devices for a long time (it possibly never did).
The nearest analagous equivalent is Samsung's "Odin" software (for Windows PCs).
There is also "heimdal" for *nix machines which attempts to replicate the behaviors of Odin.
The handset boot mode most closely corresponding to "fastboot" is Samsung's "Download" (or "Odin") mode. On the Note 3 you enter that mode from a cold start with a three-finger salute: Vol-Down+Home+Power. A splash screen will show up allowing you to "Cancel" (normal boot) or "Download" mode.
It is harmless to enter that mode if you want to look at what the screen looks like, but you might have to pull the battery to get out of it if you don't use Odin.
Search XDA for "Odin" ( or heimdal), you will find plenty of posts
Flashing TWRP:
The TWRP images are not filesystems, but just a large (bootable) binary blob file (containing a kernel, ramdisk, and device tree).
That means you can simply use the "dd" command (as the root user) to write the .img blob into the recovery partition, using a shell/ terminal. Could be using either adb or a terminal emulator app. You just need to have a root prompt.
Obviously you need to be cautious about this, making sure you are blasting bits into the correct partition (the recovery partition).
e.g. see
ls -ld /dev/block/platform/msm_sdcc.1/by-name/*
Click to expand...
Click to collapse
Took some further research, but I now have TWRP successfully installed!
Thank you kindly
Few notes for future searchers: from your adb folder run 'adb shell' then 'su' to get the root prompt, then enter the above command. Also the /sdcard/ folder is internal storage, actual sdcard path is /storage/extsdcard/
Hello everyone,
I recently decided too install the LineageOS.
Everything went fine, but I forgot Gapps and didnt want too use my phone without them so I decided too install the ROM again but this time with the apps.
I followed the linageos guide but accidently wiped everything before I could
Code:
adb push filename.zip /sdcard/
(dunno if thats the problem)
Im using TWRP 3.1.1-1. I can get into Recovery Mode. While in fastboot modus my pc detects my phone as an OnePlus, in Recovery modus its just android.
Code:
fastboot devices
shows my serial number. OEM is unlocked.
while in recovery mode
Code:
adb push filename.zip /sdcard/
gets me
Code:
No such file or directory
Code:
adb push C:\User\...filename.zip /sdcard/
gets me
Code:
failed to copy.. remote couldnt create file
while in fastboot mode I get
Code:
no devices/emulator found
Copying by dragging the file into internal storage doesnt work neighter.
I dont know what I did different besides the wipe before the copying. Maybe the wipe deactivates USB Debugging?
Maybe someone sees where my problem is.
Thanks
r717
I guess you don't have an OTG Drive.
you could always go 100% stock again and then flash LineageOS
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.13/
well first thanks for your reply. I flashed the original recovery and tried 2 sideload now. Seems to be driver problems. So I have to try every solution with Win10 and OP5 drivers I guess?
Make sure the Android drivers on your computer are up to date and also that you don't have any old drivers from a previous phone. I accidentally wiped everything on my OP5 once but when I connected it to my Windows 10 computer the OP5 was still recognized as a storage device--but I used TWRP not the stock recovery and also used the file explorer in TWRP. With the stock recovery you should still be able to side load flash the stock ROM from your computer. If you can't it's likely a driver issue.
I had once a similar issue, although not exactly this, just something with drivers.
A long process to fix was to install Linux as a virtual machine in Windows and that worked well. I could do all I needed, the phone was quickly recognized.
Virtualbox or VMware both are free/have a free version and I used Ubuntu.
Give it a try if all else fails.
So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?
noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.
Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.