Database Users

If my SGS can go into 3 button recovery mode, is it un-brickable?

Can i still mess something up, or can i always just go into recovery and re-flash?

I think the SGS is almost unbrickable because of the 3 button download mode and such. Some people aren't as lucky though since their 3 button download mode was disabled for some reason when they got it.
As long as you don't go overboard with your flash attempts and in the process seriously damage something (I was told this was possible) then you're pretty safe as long as you know what you're doing.
Do a quick google search about the firmware you're attempting to use because at times they may be corrupted or have a corrupted file (for example: DXJG4 from samsung-fimrwares I was trying to flash was actually corrupted according to many who encountered the same problem. I tried flashing several times only to get stuck at the same part each time).
Also, make sure your phone has an ample amount of battery life. A phone with damaged firmware or something might not be able to charge and once it's fully drained you won't be able to get it to even turn on to access download or recovery mode.
I say these based on experience because just recently I had a horrible experience of thinking I permanently bricked my phone. I had been attempting to flash DXJG4 (not knowing yet it was corrupted) over and over, and for each time it got stuck I removed the battery to start over (people say this is a bad idea). After doing this for several times, for some reason my phone would no longer turn on or boot into download mode. It wouldn't charge in any way, it wasn't detected by my computer either...I thought it was dead and gone but the next morning the 3-button boot worked again though it wouldn't stay on at times... I still was able to keep it on long enough to flash to a working firmware. Once my device was up and running I saw it had an almost drained battery which I guess explains a lot.
To avoid the mess of a botched flash, follow flash procedure/instructions carefully, make sure the firmware you're going to use is really working and is the correct one, and make sure your phone has an ample amount of battery life.

Singhman said:
Can i still mess something up, or can i always just go into recovery and re-flash?
Click to expand...
Click to collapse
if the 3 button combo works, then yes you can always re-flash

i ****ed up my flashing right at start (its easy, use a long usb cable and it catches too many interferences for the flashing program which has no error correction)
phone went "?" and 3 button still worked and could flash

anoneemooz said:
As long as you don't go overboard with your flash attempts and in the process seriously damage something (I was told this was possible) then you're pretty safe as long as you know what you're doing.
Click to expand...
Click to collapse
To the best of my knowledge, probably not really.. Unless you flash millions of times maybe..

[Q] Got me some boot loops after using a specific font with Type Fresh.

Alright, so last night I was fooling around with "Type Fresh," which you guys have probably heard of. It was released here... It's a font changer...
Anyway, things were going good until I tried a font named, "Joystix," which replaced quite a few of my fonts. That caused my phone to go into a crazy bootloop.
So, at this point, I do not have Clockwork Recovery. I actually have the Stock Recovery. For some strange reason, my stock recovery just takes me to a screen with a red triangle, and factory reset just shows this hard drive and a loading bar that never goes anywhere before rebooting my phone into a boot loop.
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp

wauterboi said:
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
Click to expand...
Click to collapse
Well I've never personally used type fresh to change fonts, I've done it in other ways. Just a thought for ya, but I would recommend that if you can get adb to recognize your device (cmd: adb devices) try booting into hboot(volume down + power), and see if it recognizes it regularly that way, from there I recommend trying a program called Droid. It's a windows program that I used when I messed up re-rooting my replacement mt4g (tip: Don't try rooting when having been awake for 26 hours for no apparent reason ). It has a feature called Debug Console which fixed a bootloop, and constant force close that I somehow managed. I also suggest pulling your sdcard, getting a usb scard reader, and installing the stock recovery zip (Pdimg or something like that, I forget off hand).
That's all I can think of, hope it helps

...I finally looked at my SDCard via my brother's phone.
Every thing in my SD Card pretty much has "Font" in front of it in regards to the name.
I mean... Yahoo became FontsYahoo.
wat

Solved.
For those who were wondering, I found out that I had to rename the recovery file to the PBNASFASodhwhatever it was.

[Q] Cant Seem to Root EL30. Need help!

Ill start this saying, yes, im a noob. I rarely post or visit unless i have problems.
But i do have experience rooting this specific phone before. But this time around its giving me a LOT of problems...
Ill start with:
Samsung Epic 4g (D700.0.5)
FM 2.3.6 (GB)
BB EL30
K 2.6.35.7
Now i will attempt to explain all the problems as well as what i have done to try to fix them and i will give as many links to the pages that i used for guidance as i can.
As i said, i have experience rooting this specific phone in the past. I ran a stock rooted ROM and everything was fine other then some glitches that i just learned to live with. But about 3 months ago i got a few more problems that have been driving me crazy so i desired to reroot.
When i power down the device, it will not turn back on just by pressing/holding the power button. Removing the battery, reinserting it, and holding the power also dose not work. I finally figured out that i have to remove the battery, replace the battery, then quickly (before the on-screen battery disappears) insert a charging cable thats connected to a power source. Then when the battery turns green (even with minimal power or full power) i can then power it on, but only when the on screen battery shows green. If i wait too long and it disappears it will not work and i have to start over from the beginning. (Removing Battery...) That was the 1st problem.
Soon after this happened (maybe 1-2 weeks) my phone started doing random shutdowns and not powering back on (i assume because it didnt have a power source connected). This would happen at anytime of the day or night, even when it was connected to a charger and actively charging. Yesterday i finally had the last of it and started researching this problem. I found that apparently some/all of the epics have this problem in time. From what i read the micro(or mini im not sure) USB port dosnt fit 100% snugly. So it causes heat. This heat causes corrosion and eventually leads to this problem. (I have never got this phone wet in the 1.5 years i have had it, i take very good care of my electronics.) Around the time this started my phone also would drain its self in about 2-3 hours, this was due to it constantly thinking i was plugging and unplugging it from a computer and requesting that i choose from the 3 options of mass storage.... Eventually the whole screen turning black with the android and the 3 buttons went away but the pop up on the notification bar continued, and as already said, it will drain the battery quickly.
NOW on to the rooting problems.
I dont remember what rom i was running originally, but following a few videos from QBKing77.
I odin'd back to EC05. This went fine no problems. (Useing odin 1.85)
I then tried to use the e4gtauto.zip file and running the "RUNFIRST.bat"
Used option A (install Root not EL13/newer)
Everything went though like it was suppose to. No errors or problems. Phone rebooted into recovery rather then to the lock screen.
Not remembering how to use recovery, i did some research, apparently the camera button is SUPPOSED to be the select button, but this did not work for me at all. After several manual reboots (pulling battery) this was the only thing i could get to (not even download mode to try to flash back to EC05 again). I did some research and found a post that said the "home" button on the front of the screen was his selector for some strange reason. This worked for me. I selected "reboot now" or something like that (the 1st option) and it rebooted into what i was thinking was a rooted rom, checked and there was no SU, or BusyBox (as said would happen in the e4gtauto).
I downloaded an su.zip and figured i would flash it with CWM (last time i installed CWM it was "purple" or 3.1.0.1)
Well it seems that my CWM is gone... i did the ever famous "3 finger salute" of Vol Down + Camera + Power and nothing except that i had to select "reboot phone" again from what i believe is stock recovery. Which booted me back into EC05.
By this time it was late at nite (2am or so) so i went to bed, over night apparently it updated and is now EL30. Thinking this was a good thing (and deff proving im not rooted) so today i tried rooting it as EL30.
Still do not have CWM seemingly.
Also would like to note, inorder for me to get to download mode, i have to take out my SD card, take out my battery, plug in the phone, and hold 1+power when the green power indicator comes on as stated above. This is the only way i can get into DownloadMode (if that helps at all)
If i could get any information on how to root from EL30 i would appreciate it greatly!!!
I will answer any questions as fast as possible, and i will provide as much information as you request when as soon as possible.
Thank you all in advance.
LATE:
Im not able to post links... so i cant give all the steps ive followed so far, I have attempted to take out all infomration already stated related to a link or video... Sorry.

I can do this for you remotely via teamviewer 7 google it and install it pm me the id and password and ill do it all for you
Oh and you used the epic touch one click root... not ours.. and el30 doesn't work on one click root.
Sent from my SPH-D700 using xda premium

As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.

YourLordAndMaster said:
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
Click to expand...
Click to collapse
You have the wrong recovery installed... you used the epic touch one click root... ... just go get teamviewer and ill fix it for you.
oh but now your on stock recovery because samsung has a script in the kernel to restore the stock recovery upon boot.

The rooting has been fixed.
I didnt install a CWM file apparently
and i also did a lot of bad things
Big thanks to "Big Goron" for the help he provided

[Dirty-Santa Root] Bricked Verizon LG V20 Please Help!!!

I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!

First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.

Did you get it fixed?

frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm

What roms can we use with dirty santa root?

me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...

TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.

I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.

Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.

Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...

Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into

For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.

Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir

Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.

yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you

Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.

So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery

Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...

can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.

Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.

Deleted Bootloader on LeEco S3 X626

A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.

can you at least get the phone to fastboot mode?

microMXL said:
can you at least get the phone to fastboot mode?
Click to expand...
Click to collapse
No I cannot, The screen is completely black and nothing comes on at all if I hold down the power button.

well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.

microMXL said:
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
Click to expand...
Click to collapse
I have already looked through that thread, and i have done everything up to the flashing process, and then I get a STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) Error. I looked it up but the only option I haven't tried to solve the issue is to remove the battery, which i cannot do currently because to remove the battery you need a heat gun to remove the screen to get to the rest of the phone. I think I've given up all hope on fixing this phone and may just begin saving for a new one.

Sgt.Collywobbles said:
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
Click to expand...
Click to collapse
Help, pls I got the exact same problem... Pls any solution to it... I have been at it for a month now no solution, help

same problem. after twrp flash x626 not boot