Hey,
I had installed TWRP and CM10.2 with no issue, ioroot11.
I let my buddy use the device, he jacked it up...its stuck in the LG boot logo loop... I can still boot in to TWRP but cm10.2 is gone along with everything else that was on the storage. Its clear now he wiped everything.
I need clear step by step instructions on how to overcome this issue.
Id rather just find a way to get cm back on to the storage but if i have to i will do a stock re install.
I need a list of working drivers, how to get adb set up and working correctly (adb devices says offline for my device atm), what commands to use to push cm10 back on to the device, what state the phone needs to be in order to push the cm10 zip (i only have bootlogo, download mode and twrp as device state options).
or i need a list of everything that is needed to install stock. as far as that goes, i need a direct link to sprints .tot file and directions on how to get that going.
TLR
Stuck in LG logo boot, still have TWRP..need help getting ANY type of rom installed. ADB push or Stock re install....
Thanks ahead of time to anyone who helps.
you guys are awesome!
HEWHOCORRUPTS said:
Hey,
I had installed TWRP and CM10.2 with no issue, ioroot11.
I let my buddy use the device, he jacked it up...its stuck in the LG boot logo loop... I can still boot in to TWRP but cm10.2 is gone along with everything else that was on the storage. Its clear now he wiped everything.
I need clear step by step instructions on how to overcome this issue.
Id rather just find a way to get cm back on to the storage but if i have to i will do a stock re install.
I need a list of working drivers, how to get adb set up and working correctly (adb devices says offline for my device atm), what commands to use to push cm10 back on to the device, what state the phone needs to be in order to push the cm10 zip (i only have bootlogo, download mode and twrp as device state options).
or i need a list of everything that is needed to install stock. as far as that goes, i need a direct link to sprints .tot file and directions on how to get that going.
TLR
Stuck in LG logo boot, still have TWRP..need help getting ANY type of rom installed. ADB push or Stock re install....
Thanks ahead of time to anyone who helps.
you guys are awesome!
Click to expand...
Click to collapse
For back to stock there's a thread in general forums you can also use the Verizon method with sprint files.....or you can read bout adb and download and setup on PC then push a ROM to TWRP and just flash.....you should always make a backup when your up and going again....I didn't post links cause I figured you could Google...instead of me
Thanks for your reply.
I have looked all over and was unable to find any information on what needed to be down to get adb working correctly on my device.
will you kindly link me to something explaining how to get adb working correctly with my phone. links to all the files needed.
when i use adb devices, it lists my device as offline. what state does my phone need to be in?
as for the stock restore, i download the sprint files but when i go to extract the TOT file, it does not extract correctly. will you please link me to the correct drivers needed for this process.
Thanks!
HEWHOCORRUPTS said:
Thanks for your reply.
I have looked all over and was unable to find any information on what needed to be down to get adb working correctly on my device.
will you kindly link me to something explaining how to get adb working correctly with my phone. links to all the files needed.
when i use adb devices, it lists my device as offline. what state does my phone need to be in?
as for the stock restore, i download the sprint files but when i go to extract the TOT file, it does not extract correctly. will you please link me to the correct drivers needed for this process.
Thanks!
Click to expand...
Click to collapse
Did you ever get your device back running? Im having the same problem? any help?
Related
Can I recover my dead SG5 with system dump via CWM?
What can I do with it?
It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.
fffft said:
It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.
Click to expand...
Click to collapse
[Q] Somebody give me SCL23's build.prop(original)
I changed build.prop
My android phone is SCL23
AKA Galaxy S5
I am Korean but now I live in Japan for work.
So I used GalaxyS5 for KDDI AU
Some application didn't work on my phone.
Even impossible to install
So I tried to root. Then changed model and vendor from GalaxyS5 to Galaxy S4
But it didn't work for using those apps
So I copy all of texts of build.prop of GalaxyS4.
Then my phone dead.
AU's logo is the only thing I can see.
Before did that
I had do googling and find SCL23's CWM with Chinese letters.
It works well.
Factory reset? YES
Boot? NO
Can not normal boot
Odin mode
I connected phone to PC.
Fail to install USB driver.
I think it cause of phone's hardware and build.prop is not same.
I have external SDCard.
Odin work via USB
And I can go into CWM recovery mode.
So I think if I can find .zip, able to flash, of SCL23's build.prop
I can copy it into extsdcard with friend's android
Then go into CWM and flash it.
I need SCL23's build prop
And somebody make it .zip please
I don't know how to make it.
Please help me.
And thank you for read this poor English
fffft said:
It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.
Click to expand...
Click to collapse
I wrote it few days ago.
Nobody replied to me.
So I thought many ways and did googling for recover.
I found link of system dump of SCL23.
So now I want to know about what can I do with it for my android phone's revive.
Please help me
If you have a system dump made while your phone was working properly, you can simply restore that to resolve your problems. It's not clear that that is the actual case though.
In the alternative, the apparent cause of your problems is a non-viable build.prop. You should be able to boot to CWM and then use a ADB shell under CWM to rename or delete /sideload the bad build.prop file and replace it with a good copy. If you didn't keep a good copy, you can download the stock firmware for your phone and use winrar to extract the proper stock build.prop for your phone.
More than likely, if you can boot to recovery mode, then you will be able to boot to download mode as well. So Odin use should be possible. You can use Kies to install a driver. But try CWM first.
.
fffft said:
If you have a system dump made while your phone was working properly, you can simply restore that to resolve your problems. It's not clear that that is the actual case though.
In the alternative, the apparent cause of your problems is a non-viable build.prop. You should be able to boot to CWM and then use a ADB shell under CWM to rename or delete /sideload the bad build.prop file and replace it with a good copy. If you didn't keep a good copy, you can download the stock firmware for your phone and use winrar to extract the proper stock build.prop for your phone.
More than likely, if you can boot to recovery mode, then you will be able to boot to download mode as well. So Odin use should be possible. You can use Kies to install a driver. But try CWM first.
.
Click to expand...
Click to collapse
I tried everything you told to me.
But very problem is install USB driver.
Kies failed to find and install USB driver. It worked well before I did it.
So I can not do anything with ADB commands because of USB driver.
But only Odin work to phone.
So I can install CWM. And I can go into CWM recovery mode.
Of course I can go to Download mode.
Can I do something with Linux?
Can I mount My Phone with Linux without install USB driver and then change build.prop.bak to build.prop?
I really appreciate to your reply.
Thanks to your kindness.
If your USB driver was properly installed before the problem, it will continue to work just fine, at least for CWM mode. Build.prop will not interfere with that. So just go to the CWM command line and use the ADB commands to push (replace) the build.prop file.
Are you certain that Odin doesn't recognize the phone in download mode. Ensure that you are entering download mode by removing the phone battery, replacing it, then pressing and holding in order, the volume down, then home, then power key until you see the screen light up. Odin should see the phone and it should not matter if the build.prop file is corrupt. Only the normal boot will be affected by that.
If you have problems connecting ADB or Odin, a far more likely suspect is a bad USB cable. Try a different cable or USB port. And ensure that you are entering download mode in the manner described above. When Odin recognizes your phone, you can write a stock firmware image to you phone to recover.
I haven't used CWM for quite a while (I much prefer TWRP), but it should offer you a command line. So as an alternative, use your PC to write a good copy of the build.prop file to your SD card. Then in CWM you could mount the external SD card, then copy the file from the card to your system directory. In this method, you wouldn't even require the USB driver.
You have lots of options and there are lots of ttutorials on using CWM, ADB and so forth if you need elaboration. You should certainly be able to resolve this issue even though it may be a pain in the neck or somewhat intimidating if it is unfamiliar territory. Nevertheless you can fix it if you are patient.
If the worst case,an alternative would be to pay a cellular repair shop to do the software repair for you. Entirely up to you which is the better approach.
.
Hi guys,
I attempted to restore my G2 (D802 international 32GB) back to the stock kitkat firmware from Cyanogen Mod 12. While attempting the restore, the lg support tool gave me an error saying it had failed, however when I disconnected the device it was apparently still doing something.
I now am at a stage where I get no recovery, download, or fastboot mode, etc, however my device is connecting to my PC as qhsusb_bulk in device manager. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2582142 in order to help remedy the issue, however it didn't work. I'm guessing it could have something to do with the fact that I had CM12 rather than the stock firmware of which I extracted the necessary files for my device (I extracted the files from an IMEI number provided KDZ) in place of the files provided on the thread.
Could someone help point me in the right direction? Do I need the image files from CM12, or the stock images despite the device running CM12 before hand? am I following the right process?
Thank you very much in advance for any help anyone can provide, I really appreciate it!
PS. Sorry if this has been covered before, I just haven't been able to find anything else.
Were you able to find out what the problem was? I am on CM12 myself on my G2 D802. Got some problems with TWRP. It wouldnt restore backups, and had problems with flashing ROMs ang gapps so I flashed CWM with flashify and now when I try to reboot to recovery I just get the LG logo and boot verification issue... Would really appreciate if you could share your solution if you were able to find one
Hi all,
I need your help - I installed the CM13 official, but I'm not happy with it and want to go back to CyanogenOS (Stock). I already downlaoded several files, but the sideload fails with "incompatible file system" even after factory reset.
My guess is that the CM13 bootloader needs to be downgraded, but I don't know how to do that. But that guess may be wrong....
Any help appreciated - device not working right now except for recovery & fastboot.
Have you tried with qfil?
fkoehn said:
Hi all,
I need your help - I installed the CM13 official, but I'm not happy with it and want to go back to CyanogenOS (Stock). I already downlaoded several files, but the sideload fails with "incompatible file system" even after factory reset.
My guess is that the CM13 bootloader needs to be downgraded, but I don't know how to do that. But that guess may be wrong....
Any help appreciated - device not working right now except for recovery & fastboot.
Click to expand...
Click to collapse
Just download the cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip and extract the recovery. Download cm-12.1-YOG4PAS3OH-ham-signed.zip too. Flash the COS stock recovery with fastboot. Then boot your phone up and do an adb reboot recovery. Go to adb sideload mode and do an adb sideload cm-12.1-YOG4PAS3OH-ham-signed.zip in Terminal or cmd. Wait until it's finished. You should be back on stock rom. To download the file just google for Cyanogen OS support. You will find the files to download.
http://4pda.ru/forum/index.php?showtopic=701320&st=1320#entry46208060
use it , care all data will be lost .
fkoehn said:
Hi all,
I need your help - I installed the CM13 official, but I'm not happy with it and want to go back to CyanogenOS (Stock). I already downlaoded several files, but the sideload fails with "incompatible file system" even after factory reset.
My guess is that the CM13 bootloader needs to be downgraded, but I don't know how to do that. But that guess may be wrong....
Any help appreciated - device not working right now except for recovery & fastboot.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=261NdvyULeU - This may help.
Hello I am new to the world of flashing and I thought i'd give rooting a try. I followed a guide on this website (http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568) but I messed up- I do not have a ROM (i think) now, so I cannot use my phone.
I, obviously, made a backup using TWRP but apparently it didn't save and/or I cannot find it.
I cannot figure out how to push a file onto my phone as it is only recognisable by my PC when it is in fastboot mode. I am able to access recovery mode but I do not know what to do from here. Any help would be appreciated as I really need my phone .
Thanks, Ethan
Indeed you bricked your phone. You need to perform full recorvery. The guide is on this forum amost 1st of topic.
Follow this link it will recor you phone to stock 3.x oxygen then just upgrade on MM
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
P. S. THE guide works 100% so if its not working for you read it correctly
Try to go to the advanced menu (if you're using TWRP) and find an option called Adb Sideload or something. Now shift + right click the folder on your pc where the ROM is and click on open command prompt here. Then you can just type adb sideload filename.zip
Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.
BooBzi said:
Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.
Click to expand...
Click to collapse
Push the OOS rom via usb to the phone, command: adb push namerom /scard
Next time check the drivers installation result first.
I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!
chaojimbo said:
I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!
Click to expand...
Click to collapse
I had problems with ADB drivers, anyway got back to life:
1) booted to TWRP
2) adb push ".zip" /sdcard/.
3) tried installing it at TWRP, no success, so get back stock recovery and flashed the file there.
So my issue is resolved. thanks!