Related
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Im having the same issue too
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Try this? http://forum.xda-developers.com/showthread.php?t=2451696
I finally solved the issue, miraculously, nothing was working so I just left the phone to continuing formatting for an hour so, came back, and it seemed to have done it, I installed Custom ROM, and it booted up normally, I'm not sure what triggered the phone to accept the system mount, but I am sure as hell happy it did. I was worried I was going to have a bricked device on my hands.
Hold strong, just allow the phone to continue doing what it needs to do I guess. Leave TWRP in all STOCK settings, I tried to modify multiple settings based on Devs saying to get a faster formatting to enable RM-F but I have no clue why and what didn't work.
Anyhow, problem resolved!
On another note, I would never use the recommended method from Droid_<3er as they would completely brick your phone unless you're specifically in the situation listed in that thread. As you would put your phone into a state where you lose both access to Recovery and ROM access, rendering your phone to a piece of plastic and metal. But it's definitely worth mentioning, I just had to do some research on the method cause I had the same thinking as well.
I can confirm by using normal make_ext4fs while formatting /system is the best way to avoid this. Was afraid of having a 5.2 inch brick, but thankfully, disabling the quick way to format has fixed it and allowed /system to be remounted.
I think (<-- that's the disclaimer) that it's OK to use the fast formatting method for Dalvik Cache and Cache, but not for System.
in my opinion it's best to use rm -rf /system aka delete_recursive("/system"); than formatting
I'm having the same issue, and I'd be willing to try this one. How would I do this?
I have the same issue with CWM and now got over to twrp with the same outcome.
Right here I see solutions that worked so far, but it seems like this was rather accidentially.
I want to try some of these, but in the thread posted above
"Try this? http://forum.xda-developers.com/show....php?t=2451696"
it says "Do it the wrong way and your phone might get nuked"
unfortunately it doesn't say what the commands in there mean...
Can anybody be of assistence which method will properly work without nuking the phone?
I have the MOTO G 2014 (2nd Gen)
It is an updated bootloader
i got the latest twrp
and some titan roms.
only stock rom will work so far,
custom roms will result in a bootloop.
Due to the fact that the N6/9 cannot oem unlock until after initial setup (which also means a forced ota), it may be impossible to dump the initial rom on it, info: PSA: OEM Unlock On The Nexus 6 And 9 Requires Checking A Box In Developer Options
What can be done however is finding a little information, specifically the bootloader/baseband (for devices that have them) and initial rom version.
How to check:
Enter fastboot mode
Make note of baseband and bootloader versions
Enter Recovery mode
Press and hold Volume up, and then press power until the UI appears
Make note of rom build in title
I would like to request someone that has not done first setup to make note of what build is preinstalled.
Is it not possible to go through initial setup without Internet connectivity?
dualityim said:
Is it not possible to go through initial setup without Internet connectivity?
Click to expand...
Click to collapse
It depends on the device, most recent ones now simply cannot finish setup without first checking in with gservices. They force you to connect to wifi to continue, and if you connect to a wifi point that cannot reach the internet, it will simply sit there waiting to connect.
This is what happened with my NP at least, and it was roughly the same with the 2013 N7.
I think all the quick hands on unboxing videos show people skipping all the setup steps, including adding wifi and logging in. There may be cell connection, but the OTA doesn't install itself, it just starts downloading and tells you when it's done, right? That's what my Moto X 2013 did when I cracked it open.
All nexii in recent history have forced otas during setup, there is no way to bypass it short of doing something that would normally break the ota check.
Most reviews have devices from before the ota, or had no ota available at all.
reminder: now that the N6 is starting to ship out, please make note of what the initial rom is.
Update: the N6 does not seem to have a forced update at least.
If you have a N6 and are willing to hold off on updating for a few days/weeks (until CWM or the like is ported), I would like to request a dump of the initial rom.
Due to the fact the N6 is likely a secure /system device, the only usable dumps require DD, nandroids or manually pulling the files are of minimal help.
YOU MUST DO THIS FROM A RECOVERY, IF YOU ROOT YOUR ROM YOU WILL NO LONGER BE ABLE TO RECIEVE OTAS/THE DUMP WILL BE NO GOOD
Here's how to do it:
boot into a custom recovery
open an adb shell
mount data: mount /data
dump bootloader:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/aboot.mbn
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/data/local/rpm.mbn
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/data/local/sbl1.mbn
dd if=/dev/block/platform/msm_sdcc.1/by-name/sdi of=/data/local/sdi.mbn
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/data/local/tz.mbn
dump baseband: dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/data/local/radio.img
dump boot: dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/data/local/boot.img
dump recovery: dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/data/local/recovery.img
dump system: dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/data/local/system.img
dump logo: dd if=dev/block/platform/msm_sdcc.1/by-name/logo of=/data/local/logo.bin
dump versions: dd if=/dev/block/platform/msm_sdcc.1/by-name/versions of=/data/local/versions.bin
What about dumping Att OEM? Since it is memblck0p39, does it matter? For the people that nuked the OEM partition and have to send it in for warrenty, it might make a big difference.
Well,I didn't take the ota,but I rooted it. what you trying to get done?
TheManii said:
All nexii in recent history have forced otas during setup, there is no way to bypass it short of doing something that would normally break the ota check.
Most reviews have devices from before the ota, or had no ota available at all.
reminder: now that the N6 is starting to ship out, please make note of what the initial rom is.
Click to expand...
Click to collapse
not true.
i got my ota a day after i got my n6, i didnt take the ota. the option hung for another day, but it was my choice not to ota. instead, i flashed the most recent aosp. otas are never forced upon anyone who owns a nexus.
edit.. ok, i read your next post.
This thread has been a lifesaver, I have a friend with a pre-order Att Nexus 6 that I was able to get the OEM partition from. I deleted something and I still do not have any sensors, and my logcat shows a ton of errors trying to get the sensors to work. I tried to fix-permissions with TWRP but it always fails. Anyone have any suggestions?
simms22 said:
not true.
i got my ota a day after i got my n6, i didnt take the ota. the option hung for another day, but it was my choice not to ota. instead, i flashed the most recent aosp. otas are never forced upon anyone who owns a nexus.
edit.. ok, i read your next post.
Click to expand...
Click to collapse
same here, I got my ota update probably 3 or 4 hours after setting my device up, but I just hit remind me later and never accepted it and wasn't forced to accept anything
Hi everyone!
I was using Resurrection Remix ROM on my 6P, no custom kernel and TWRP 3.0.2-2 installed. I installed the ROM by going back to stock, reflashing the recovery, and installing ROM + GAPPS - I like my ROM installs squeaky clean, never had an issue. I set up my phone and moved in completley. I went on with my day until around 11 last night where I was rebooting into recovery to do a TWRP backup the phone just never booted. I rebooted bootloader and tried again but I kept getting the Google logo and the device rebooting. Then again Google logo and reboot. Never showed the TWRP splash screen.
I then went ahead and tried returning the phone back to stock. I downloaded the firmware from Google (latest Nougat), put the phone in bootloader, and began the installation (using flash-all from the zip file). Everything seemed like it installed fine (no errors) and the phone reboots. Same issue, Google logo and a reboot. I tried going into the stock recovery, but no dice - Google logo, reboot. I reflashed TWRP to see if maybe that'll work but it didn't (Google logo, Reboot, rinse and repeat).
I relocked the bootloader and for a split second I saw the "Erasing" with the colourful hoops then a reboot to the Google logo - never booting into the fresh install.
Fastboot responds and detects my phone, I have opened the phone and the power button isn't stuck, I have tried going back to MM stock (installs but no boot).
Is there anything else I can do before going out and buying a new phone?
Thank you!
xxxrichievxxx said:
Hi everyone!
I was using Resurrection Remix ROM on my 6P, no custom kernel and TWRP 3.0.2-2 installed. I installed the ROM by going back to stock, reflashing the recovery, and installing ROM + GAPPS - I like my ROM installs squeaky clean, never had an issue. I set up my phone and moved in completley. I went on with my day until around 11 last night where I was rebooting into recovery to do a TWRP backup the phone just never booted. I rebooted bootloader and tried again but I kept getting the Google logo and the device rebooting. Then again Google logo and reboot. Never showed the TWRP splash screen.
I then went ahead and tried returning the phone back to stock. I downloaded the firmware from Google (latest Nougat), put the phone in bootloader, and began the installation (using flash-all from the zip file). Everything seemed like it installed fine (no errors) and the phone reboots. Same issue, Google logo and a reboot. I tried going into the stock recovery, but no dice - Google logo, reboot. I reflashed TWRP to see if maybe that'll work but it didn't (Google logo, Reboot, rinse and repeat).
I relocked the bootloader and for a split second I saw the "Erasing" with the colourful hoops then a reboot to the Google logo - never booting into the fresh install.
Fastboot responds and detects my phone, I have opened the phone and the power button isn't stuck, I have tried going back to MM stock (installs but no boot).
Is there anything else I can do before going out and buying a new phone?
Thank you!
Click to expand...
Click to collapse
It's been an ongoing thing with the 6P's and 5X devices. Here's a thread that might be able to help you. I myself fell victim to this and nothing i did brought it back to life. Wound up doing an RMA with Huawei..
Check your warranty status http://consumer.huawei.com/us/support/warranty-query/index.htm
Thread: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page41
One more Guide: http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Hope this helps..
BIGSAMDA1ST said:
It's been an ongoing thing with the 6P's and 5X devices. Here's a thread that might be able to help you. I myself fell victim to this and nothing i did brought it back to life. Wound up doing an RMA with Huawei..
Check your warranty status http://consumer.huawei.com/us/support/warranty-query/index.htm
Thread: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page41
One more Guide: http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Hope this helps..
Click to expand...
Click to collapse
THANK YOU for shining some light on this issue! Looks like my phone is under warranty till 05/2017. But my next question is would the warranty be voided because I opened up the phone to make sure the power button wasn't the cause of the issue? :| I hope not!
Thanks again!
xxxrichievxxx said:
THANK YOU for shining some light on this issue! Looks like my phone is under warranty till 05/2017. But my next question is would the warranty be voided because I opened up the phone to make sure the power button wasn't the cause of the issue? :| I hope not!
Thanks again!
Click to expand...
Click to collapse
Absolutely, yes. Your warranty is void. That's always going to be the case on just about any electronic product. The only exceptions I know of are upgrading the hard drive in your PlayStation or Xbox, since you don't actually have to dismantle the entire system. They make the hard drives easily accessible without having to open anything else. As far as phones go, opening them will always void the warranty. They can tell as well, so you can't get a warranty replacement. Hopefully those links provided can help solve your issue so you don't need to pay out of pocket for a new phone. Good luck.
I had this problem when nougat previews first started. This is what worked to get me back up. I guess it erases the efs partitions and forces the phone to rebuild them. I tried fastboot flashing stock, etc, nothing worked, then I ran these two commands and it booted right up.
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Sent from my Pixel XL using Tapatalk
how did you get adb to work? The phone does not go into recovery mode, always bootloop.
shiftr182 said:
I had this problem when nougat previews first started. This is what worked to get me back up. I guess it erases the efs partitions and forces the phone to rebuild them. I tried fastboot flashing stock, etc, nothing worked, then I ran these two commands and it booted right up.
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
guys have the same problem and Huawei does not help me and are under warranty, I have tried google but to no avail what can I do?
wonderdroid87 said:
guys have the same problem and Huawei does not help me and are under warranty, I have tried google but to no avail what can I do?
Click to expand...
Click to collapse
Where did you purchase the device from? Try Huawei again, maybe you'll get a different rep.
Amazon
I had a very similar problem. In the end, I used WugFresh's Nexus root toolkit to flash stock Nougat, with 'current status' set to 'soft-bricked'. That worked fine, and I'm back to normal...
jozomali said:
I had a very similar problem. In the end, I used WugFresh's Nexus root toolkit to flash stock Nougat, with 'current status' set to 'soft-bricked'. That worked fine, and I'm back to normal...
Click to expand...
Click to collapse
I'm a try but not work
I spoke with Huawei and as soon as I told them about the issue they right away were going to give me an RMA. I told them that the phone received an update from "google" and when I restarted the phone, the phone started to bootloop and never booting back to the home screen. But before we proceeded with the RMA I had to tell them the bad news - that my phone was opened because I was suggested to check if the power button wasn't the cause. She said that that voided the warranty and that my phone wont be covered for any repairs. I asked if I can pay them to fix it and they said no.
All in all I have a very pretty paperweight sitting, waiting to see if someone can come up with a fix. For now I'm using a Blackberry Passport with my android apps installed.
If not I'll either be moving to a OnePlus 3 or OnePlus 3T.
P.S. the toolkit "Soft-brick" option did not work for me either.
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
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.