Develop Bugs

Updating to ZVA, phone stuck in fastboot mode, no recovery.

i was updating to zva via twrp and must of fudged something up, the phone wont enter download mode and if im lucky enough to get it to boot to recovery it says the standard entering recovery and then it goes right back to fastboot. i tried pushing files through fastboot but it keeps saying unknown partition.
anyone know what files i need to fix this?

What Rom were you trying to flash, did you follow every direction, did you flash the zva radio or specific kernel for java.?
Sent from my LG-LS980 using Tapatalk

derp rom, followedf the directions to a tee, but i think i may have flashed the wrong radio now:/ i had two in my DL folder..

i have managed to get a stock recovery on it via fastboot..still working on a rom or download mode though
SOLVED: follow this guide if you are stuck in a fastboot reboot. make sure you download the files for your phone.
http://optimusforums.com/threads/gu...epaired-written-to-help-my-dear-friends.9274/

[Brick phone] help needed

I have flashed many phones before my G4 and this is the first time I'm having to ask for help.
The firmware installed was AICP CM13, then the screen went green with a DemiGod message. I held the vol down button to reboot and it came back up. After a few restarts and green screens i figured I needed to reflash the firmware. I booted into Recovery and while wiping the device to flash a new firmware, TWRP crashed. After leaving it for half hour or so, I took the battery out to enter into TWRP so I can flash the new firmware. TWRP is no there to be seen. I hold down the vol down and power button, releasing power for second or two and choose to go into recovery. Every time the phone just gets stuck on the LG screen displaying "Bootloader state :Bootlader unlocked!".
In short, I have no firmware, the device has been wiped and TWRP doesn't seem to be working.
I have tried to flash a KDZ file (H81520A_00.kdz) using the flash guide here. This comes back as unsuccessful saying "connection to server failed". As shown below.
View attachment 3605673
The method to flash an .img file using cmd on the pc includes moving the 4gb .img file to the parent folder of the phone storage. I can't get to move any files whatsoever to my device so figured this method would not work.
Seems if I can somehow flash TWRP, then I should be able to install a new firmware.
Any help much appreciated.

Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!

rav101 said:
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
Click to expand...
Click to collapse
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?

AndHD2 said:
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
Click to expand...
Click to collapse
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi

It is late here and with me being tired I said recovery instead of download. I can boot into download mode but when I try to boot into recovery then it just goes straight to the LG splash screen and it will either remain in that screen or the green Demigod screen would come up.
I'm off to sleep and away from my laptop as I have to be up in 5 hours. Luckily I still have my Note 4 so at least I'm not without a phone in the morning. I will try the steps what you have suggested just as soon as I get back from work.
Many thanks

rav101 said:
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
Click to expand...
Click to collapse
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.

AndHD2 said:
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
Click to expand...
Click to collapse
Hi @AndHD2, I'm sorry but I can't think of anything else

rav101 said:
Hi @AndHD2, I'm sorry but I can't think of anything else
Click to expand...
Click to collapse
I had another demigod type screen but this was grey and not green with less detail. However it did say it were a kernel error.
Is the handset still under warrenty with the bootloader unlocked. I have a feeling its not

Help me restore a softbricked phone

Here has more background http://forum.xda-developers.com/note-4-sprint/development/rom-t3330135/page23 but the TLDR is that my phone is stuck in bootloop, even when I flash a stock image in Odin (Does it matter if I use AP in Odin versus BL? I tried both)
All I can think is that in recovery I did a full wipe on every conceivable thing. I also did a nanderase in Odin one time. Maybe shouldn't have.
This is also compounded by the fact that my phone's home button doesn't work so to get to download mode I am forced to use a jig I cobbled together and essentially hotwire my phone into download mode.
Does someone have a safe, stock ROM so I can get things back to square one? I've tried N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar so I am pretty sure I was on OG5 baseband with OK1 build. But still, if your friend who knew nothing about phones gave you one in a bootloop, which rom would you flash?
Thanks guys.

I've helped with a similar issue before. In short, nand erase all will prevent phone from booting.
You need to install just the stock recovery converted from .img to tar.md5, flash with Odin in AP slot and factory reset and wipe the cache and dalvik in recovery.
To start, you need to extract the recovery.img from the stock tar and use utility to convert it and flash in Odin AP slot. This utility may work, I don't recall which utility I used before because my motherboard and hard drive crashed. Lost everything. Try this one.
http://forum.xda-developers.com/showpost.php?p=45629177&postcount=1
With your broken home key, I'm not sure what the phone does with only recovery flashed. Hopefully it auto boots to recovery seeing only that so you can factory reset and wipe. If so, flash stock after that.
If you can't boot to recovery, you may have to install adb on your computer and try to send the command (adb reboot recovery) from either download mode or timed correctly while it's attempting a boot. I'm thinking with nothing but recovery, the phone will either boot recovery or KIES or Smart Switch will recognize it. You may also convert the boot.img (kernel) with that same utility for Odin flash in AP slot if the phone isn't recognized. The bootloader could also be extracted and flashed with Odin in BL slot.
But hopefully you don't have to do all this workaround stuff to recover. I'd start with just stock recovery converted tar.md5 with utility and factory reset and wipe. If it didn't auto boot into recovery, try the traditional boot to recovery pattern. If not working, then try the adb command from download mode, and so on with other means to either boot in recovery or get KIES or Smart Switch to recognize.
Edit: if you're already able to boot stock recovery, just factory reset, wipe cache and dalvik and power down, remove battery for 30 seconds and flash stock tar.
Sent from my SM-N930P using Tapatalk

Can you elaborate on boot to recovery pattern? I flashed the recovery but it still wouldn't boot to recovery. Is that because the stock tar I flashed is still fouling things up?
Should I land erase again so the stock tar is gone, then try flashing the recovery Image? I don't quite understand why taking parts of the stock tar and flashing them separately is any different than flashing the tar file itself.
Got some reason, adb always says device not recognised, even though Odin has no trouble, so it's probably not a driver issue, but the way I'm starting or running adb.exe

Since you already did the nand erase all in Odin and haven't booted successfully, I don't think you could do any further harm by going it again.
I honestly don't know the usefulness of the feature or instructions when using it, just that from some searching, that stock recovery helps to recover from using it.
Sounds like your home switch is still dysfunctional and you want to try the nand erase all, flash only stock recovery and see if it auto reboots into recovery? You could try.
Did you use this adb installer or follow the OP to try to get phone recognized?
http://forum.xda-developers.com/showpost.php?p=48915118&postcount=1
Edit: Still reading the thread above but it looks like win10 users have to run installer in administrative mode and also use the edited version below. Not sure if the OP corrected the issue but typo of version in OP still exists so I'd try this one and make sure the Samsung driver from Samsung support was also installed.
http://forum.xda-developers.com/showpost.php?p=67779874&postcount=821
I'm still getting my new PC updated with tools but will try this adb installer soon.
Sent from my SM-N930P using Tapatalk

Fyi I'm on Windows 7 if it matters

Blakestr said:
Fyi I'm on Windows 7 if it matters
Click to expand...
Click to collapse
Have you tried traditional adb through installation of Android SDK and setting path as outlined in this guide?
http://www.serverdrivers.com/2016/10/universal-adb-driver-download-for.html?m=1
And did you install the Samsung USB driver from Samsung support on Note 4?
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
I ask because I'm not sure why you get device not found. The installer thread I mentioned earlier claimed that only adb sideload works with the above adb method. I'm thinking it may be Google limiting access in later updates but just a guess.
Sent from my SM-N930P using Tapatalk

My OP3 is Dead! Any help is appreciated!

Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!

alireza.nasibi said:
Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!
Click to expand...
Click to collapse
Try this method now it will work
https://forum.xda-developers.com/showpost.php?p=68245482&postcount=111

The point is I can't flash anything on any partition as phone is locked and can't be unlocked!

alireza.nasibi said:
The point is I can't flash anything on any partition as phone is locked and can't be unlocked!
Click to expand...
Click to collapse
If you can access fastboot mode then you can definitely flash by other method

abhi0502 said:
If you can access fastboot mode then you can definitely flash by other method
Click to expand...
Click to collapse
you mean the 2nd method?

You said you lock the bootloader in 5th line, in order to flash any recovery you need to unlock bootloader again.
I also tried to lock bootloader last week and then my op3 got bricked with bootloop.
-First get into fastboot and unlock bootloader this will wipe your all data including you saved ROM files.
- after this flash TWRP or OnePlus recovery and sideload OOS ROM. Or transfer the ROM file using mtp in TWRP recovery.
- then you can easily do anything you want. Don't relock bootloader.

Those red things on your screen basically means your phone misses partitions, without these partitions it doesn't boot duhh.
If method 2 of the unbrick tool doesn't work, you can manually flash those files in Fastboot, the program has a folder that has all partitions like, cache.img, boot.img etc. I've been here as well nothing to worry about just keep us updated so we can help you

There's no mention in your post on which unbrick method you used. Was it first or second? By the looks of the end result, it was the first.
Just follow the same steps, but use method 2, that should leave you with a phone like out of the factory. Afterwards, you can simply set it up and let it update through OTA if you want to remain stock, or simply unlock bootloader, flash TWRP and flash whatever you want.

use the second method. the file you have to download contains all the raw room and when you follow the process, it would work. happened to me two times and i used this method

Just simply use fastboot oem unlock in fastboot mode then flash a recovery via fastboot flash recovery then go to recovery and once wipe all the partions and install a rom and then tried booting

Thank you all for your time and support. Method 2 saved my phone!

Bricked phone using adb, is the data salvagable?

I was trying to degoogle my phone with adb pm uninstall following some tutorial, when I think I uninstalled something crucial under com.google.android.#### because the system crashed and went into a boot loop.
Is there anyway to recover the data I still have on my phone? Is it salvageable?

PhoneUser2840 said:
I was trying to degoogle my phone with adb pm uninstall following some tutorial, when I think I uninstalled something crucial under com.google.android.#### because the system crashed and went into a boot loop.
Is there anyway to recover the data I still have on my phone? Is it salvageable?
Click to expand...
Click to collapse
Are you able to get to recovery, or get to fastboot and then flash a recovery?
I'd make a full backup in recovery, restore same version of whatever ROM you were using, and then restore backup.

SMcC2 said:
Are you able to get to recovery, or get to fastboot and then flash a recovery?
I'd make a full backup in recovery, restore same version of whatever ROM you were using, and then restore backup.
Click to expand...
Click to collapse
Hi thanks for the reply,
I'm in recovery mode now.
After downloading many different usb drivers (this one worked for me) and selecting the recovery mode option Apply update from ADB, I can now use adb devices.
The device is in sideload mode unfortunately and I can't use adb pull. Is there any other way to make a backup?

Are you able to get in to fastboot at all?
I was hoping you get TWRP or some kind of recovery working.

So thought I'd provide a quick update, after trying for ages to access any part of the filesystem, I was on the verge of giving up.
However by sheer luck, I found my phone was not too corrupted to launch safe mode, as a result I was then able to transfer all my files before resetting the phone.

Keep this on the dl before they get rid of adb to. I'm glad you fixed it, but is it deGoogled? Using adb I'm pretty sure a factory reset would fix just about anything. I had no Gapps for about 3 hours once, I found it very annoying, lol. Googles claws are sunk way to deep for me to live without.