Develop Bugs

[Q] Stuck In a Broken ROM and cant get back into CWM recovery mode(Error Message)

Hi,
i found a simliar thread that was talking about a similar subject, but didn't answer my question. i have lost it and cant find that same thread for help.
rooted -flashed bad rom - everything keeps closing(apps, Google sync)--- cant get int to recovery mode because of error
****I unlocked bootloader and rooted my GalaxyNex. then installed ROM maneger. i flashed CWM,then backed up my ROM. i tested it by flashing my backed up ROM, after i had messed around and my phone went back to normal. i was feeling safe. i noticed that i was having trouble getting into the recovery mode because of the belly open with exclamation Point. i read that it is because CWM was losing permission? i found that i just had to re-flash CWM every time right before i go into recover mode. i flashed a ROM from ROM maneger and everything worked until i turned the phone on. i cant sync Google account, and basically all apps close immediately (no key board too). I cant get into recovery mode and i cant down load ROM maneger to try to re-flash CMW to restore from older ROM.
I am sorry if this is already been answered i have try to find my situation but i couldn't.

I tried to re-flash the clock work recover image through the terminal of my mac but it says permission denied... i guessing i need to find a way to re flash to stock from fastboot is this possible ?

Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium

joshnichols189 said:
Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks I got really lucky i was able to re flash Clock work recovery in fast boot with the command
./fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
then i was able to get into the proper recovery mode and re flash my backed up image.
if i wanted to re flash a original image would the terminal command look like this
./fastboot flash recovery "Imagename" ? i might have just got lucky but i am guessing thats how you re-flash something to your phone?
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again

Glad your good! Hate to see these threads but we all go through it sooner or later
Sent from my Galaxy Nexus using xda premium

billycurtis said:
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again
Click to expand...
Click to collapse
After you fastboot flash the CWM image, use ADB, a terminal, or a file explore to remove or rename the file /system/recovery-from-boot.p

Stuck at boot

Hi hoping someone can help, I accidentally wrote the wrong file to my system partition and am stuck at smartwatch 3 logo.
i tried pc companion and it tells be there "no software available for my device" all i can get to is fastboot mode stock recovery is gone too
I wrote twrp to it but as of yet have not been able to launch it. its running 5.1.1 os and i cant remember build number other than it began with an L
Please help
ZR1

if you read this and know i have no hope please let me know that too please
seems like if i had stock partitions images i could flash using adb i"d be good yes?? no?

I do not have time to help right now, but since you can get to fastboot, you are probably fine. Find the stock 5.1.1 recovery and boot to it. Then sideload the latest update. You will be good to go.
The command in a terminal window is...
Code:
Fastboot boot <stock recovery.img>
Alternatively, you can boot to twrp and install a twrp flushable zip.
Good luck.

Lekofraggle thank you for your help.
I did what you said with img file from this thread http://forum.xda-developers.com/sma...50-version-t2988087/post62897403#post62897403
it wrote the img file but still just hangs at boot image, and i still cant get twrp to work after holding power button and choosing recovery option screen goes blank and then starts to boot and hangs at smartwatch 3 image
all the things i"ve rooted before in my life i"ve never screwed up this bad.

zr1 said:
Lekofraggle thank you for your help.
I did what you said with img file from this thread http://forum.xda-developers.com/sma...50-version-t2988087/post62897403#post62897403
it wrote the img file but still just hangs at boot image, and i still cant get twrp to work after holding power button and choosing recovery option screen goes blank and then starts to boot and hangs at smartwatch 3 image
all the things i"ve rooted before in my life i"ve never screwed up this bad.
Click to expand...
Click to collapse
Have you tried Sony Companion to repair your watch?
If you were running 5.1.1, then the recovery you mention is for 5.0.1, so that might be the reason why you can not boot into it. See if you can find the stock recovery for 5.1.1
I have used the following method a couple of times now to get me out of trouble after playing around with my SW3
http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
You can then use the stock recovery you already have and update via OTA files to get it back to the latest firmware or via Sony Companion.

I had the exact same issue after I did fastboot flash using corrupt system.img (which wasn't a snapshot that could be flashed but rather a tarball). Since you have TWRP installed you can confirm this by trying to mount system partition in recovery mode. After it fails, connect to recovery via adb and view latest kernel messages (dmesg). It should show something like "failed to locate ext4 filesystem".
If this is your case, you can use TWRP restore function to restore system from your TWRP backup. It will then erase the partition, mkfs.ext4 and write the files from tarball. This did the trick for me.
(If you don't have backup, try looking for downloads in other threads here)
Edit: Re-read your post. Since your TWRP is broken, try hotbooting it using fastboot boot new_boot.img (you can take it here)

ebones thank you thank you thank you
I had downloaded new_boot img already so im not sure what i was doing wrong but i did what you said and she booted right into TWRP i now have to sideload the right update.zip file and run it in twrp correct?
edit; having trouble sideloading wear-supersu.zip what is the correct command?

GOT IT!!! I installed stock rom from this thread http://forum.xda-developers.com/sma...rom-repacked-stock-rom-swr50-version-t2988087 through TWRP and it works cant thank you guys enough
Thanks ZR1

[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

Soft brick, restore from fastboot?

I erased the laf partition Download Mode in order to use fastboot, rooted, and installed cm-13.
Then I ended up wiping all partitions using TWRP recovery, soft bricking my phone, if I understand right.
Now I need to restore something starting from fastboot to get the phone working again. I would like to get back to rooted phone with cm-13.
To do this, posts recommend using fastboot to flash the laf partition to restore LG's Download Mode, but I'm worried if I put Download Mode back and it doesn't work, I won't even be able to get back to fastboot, an then I'm more stuck. Is this a good worry?
Also I don't want to go all the way back to stock, unless I have to.
Also, I'm on Linux, but I do have Windows I could use.
Can I just flash a bunch of partitions in fastboot, enough to get me back to being able to install cm-13? Which ones and which img files?
If not, am I on the right track with the Download Mode fix? I just don't want to brick my phone more than it is.

colinw1 said:
I erased the laf partition Download Mode in order to use fastboot, rooted, and installed cm-13.
Then I ended up wiping all partitions using TWRP recovery, soft bricking my phone, if I understand right.
Now I need to restore something starting from fastboot to get the phone working again. I would like to get back to rooted phone with cm-13.
To do this, posts recommend using fastboot to flash the laf partition to restore LG's Download Mode, but I'm worried if I put Download Mode back and it doesn't work, I won't even be able to get back to fastboot, an then I'm more stuck. Is this a good worry?
Also I don't want to go all the way back to stock, unless I have to.
Also, I'm on Linux, but I do have Windows I could use.
Can I just flash a bunch of partitions in fastboot, enough to get me back to being able to install cm-13? Which ones and which img files?
If not, am I on the right track with the Download Mode fix? I just don't want to brick my phone more than it is.
Click to expand...
Click to collapse
Also, does it matter which version I restore - I found all these online:
20E Jun-09-15
10R Mar-30-15
10C Oct-31-14
20B Apr-12-15
10M Mar-31-15

colinw1 said:
Also, does it matter which version I restore - I found all these online:
20E Jun-09-15
10R Mar-30-15
10C Oct-31-14
20B Apr-12-15
10M Mar-31-15
Click to expand...
Click to collapse
PS I will be happy if anyone can answer any of these questions like just is it right thing to use fastboot to flash laf.img. ONly thing is I've got these five different laf.img's I could download - any one is okay? Most recent? Do I still have options if this doesn't work, like getting back to fastboot and trying something else?

colinw1 said:
PS I will be happy if anyone can answer any of these questions like just is it right thing to use fastboot to flash laf.img. ONly thing is I've got these five different laf.img's I could download - any one is okay? Most recent? Do I still have options if this doesn't work, like getting back to fastboot and trying something else?
Click to expand...
Click to collapse
Got it working! I ended up flashing version 10C of download mode (laf.img) to the laf partition using fasboot flash laf laf.img. I got the problem people have with download mode only showing up for a second and then going back to fastboot.
Then I tried the latest version of laf.img from here, version 10M:
http://downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions
and that got me a working download mode.
Next went to Windows machine and followed this guide:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
including downloading lg drivers so phone gets recognized, lg setup tool, and downloading large lg stock recovery file and dll.
Once back in stock, I was able to re-root, install TWRP recovery and install cm-13 and google apps. This time I installed cm-13 and google apps in the same TWRP session and didn't have the problems I was having before which led me to wiping everything and accidentally soft-bricking.

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