Went through DirtySanta, Accidentally updated, Phone Reboots into Recovery - LG V20 Questions & Answers

Hello All,
My v20 Arrived yesterday (Sprint ls997), and I immediately went through the DirtySanta guide and got it working. I wasn't paying attention, and accidentally selected to reboot and install an android update. The phone rebooted into recovery, and no matter what I try, it only boots into recovery.
I've tried:
Wiping Cache and Dalvik Cache
Wiping Caches and Data
Wiping System, Caches, and Data, then reflashing the stock file included in the thread
Wiping System, Data, Caches, and Internal Storage, and reflashing
Formatting Data and Reflashing
Wiping Everything and reflashing a custom rom
adb reboot system
fastboot reboot
Is there a method to fixing this, or did I brick my phone?
Thanks,
dfiel
EDIT:
I fixed it! Device booted into Android, just have to fix com.android.phone stopping every couple of seconds. What fixed this for me is:
While booted into TWRP, on your computer:
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=256 count=1 conv=notrunc
reboot
It then booted into bootloader mode. I ran step3.bat from the DirtySanta exploit, and it rebooted back into fastboot, I then flashed boot2.img using the command:
Code:
fastboot flash boot boot2.img
It then booted into android.
Hopefully this helps somebody else!

try this forum.xda-developers.com/v20/help/help-stuck-twrp-recovery-t3496631/page2 it works on mine device

ljm625 said:
try this forum.xda-developers.com/v20/help/help-stuck-twrp-recovery-t3496631/page2 it works on mine device
Click to expand...
Click to collapse
Just tried it 3 times, no dice.

dfiel said:
Hello All,
My v20 Arrived yesterday (Sprint ls997), and I immediately went through the DirtySanta guide and got it working. I wasn't paying attention, and accidentally selected to reboot and install an android update. The phone rebooted into recovery, and no matter what I try, it only boots into recovery.
I've tried:
Wiping Cache and Dalvik Cache
Wiping Caches and Data
Wiping System, Caches, and Data, then reflashing the stock file included in the thread
Wiping System, Data, Caches, and Internal Storage, and reflashing
Formatting Data and Reflashing
Wiping Everything and reflashing a custom rom
adb reboot system
fastboot reboot
Is there a method to fixing this, or did I brick my phone?
Thanks,
dfiel
EDIT:
I fixed it! Device booted into Android, just have to fix com.android.phone stopping every couple of seconds. What fixed this for me is:
While booted into TWRP, on your computer:
It then booted into bootloader mode. I ran step3.bat from the DirtySanta exploit, and it rebooted back into fastboot, I then flashed boot2.img using the command:
It then booted into android.
Hopefully this helps somebody else!
Click to expand...
Click to collapse
Did you get the com.android.phone file to quit crashing and is your device working smoothly? Id like to update to ZV5 but no one seems to have any advice on how to accomplish it succesfully.

bgibson72 said:
Did you get the com.android.phone file to quit crashing and is your device working smoothly? Id like to update to ZV5 but no one seems to have any advice on how to accomplish it succesfully.
Click to expand...
Click to collapse
I ended up flashing this rom. It's been working great, root works, and the only issue is the static on boot.

Related

Problem with Partition Table

Hi guys,
I'm experiencing a very big problem with a friend of mine's nexus 4. I've done the same thing in the same order with my phone (nexus 4 too) five minutes before and it worked.
We installed 4.4 stock rom downloaded from official google website via fastboot and all went well on my device. The problem was that we repeated the same identical procedure on my friend's nexus 4 and it went well except for the fact that the phone only had 5gbs available after the flash, so we red on the internet that we had to repeat the procedure using "fastboot -w update" instead of flashing every single file contained in the zip folder.
So it's now that borns the real problem. We've erased all partitions (fastboot erase cache, userdata, system, bla bla) and reflashed all. But from this point it stucks on android 4.4 loading logo.
We've tryied to repeat the operation and we've noticed that "fastboot erase bootloader" command answers with "Failed (remote: bootloader partition does not exist)". So we tryied to install cwm recovery and flash from sideload, it works and loads cyanogenmod logo but stucks on it again, tryied to flash everything possible and it works but after don't start.
The strange thing is that the bootloader appears to not exist but if i do the command: fastboot flash bootloader C:\...\bootloader.img it works and says "writing... OK" so i really don't know what could be the problem.
Please guys help us, my friend is on the point to sell his phone but we both are SURE that if it still can enter on recovery and on bootloader it could be restored!!! But we don't know why! Tryied every possible solution on the web, and nothing worked for now...
Thanks to all in advance!
Install the latest twrp recovery, enter it and go to the wipe menu, chose the format data option. Then give a rom a try.
meangreenie said:
Install the latest twrp recovery, enter it and go to the wipe menu, chose the format data option. Then give a rom a try.
Click to expand...
Click to collapse
Hi, thanks for the answer. Fortunately i've just resolved the problem. It worked after I wiped data from the STOCK recovery (it was the first thing i've done with the cwm several times but unsuccessfully). Now it works perfectly. Thanks again :victory:
fdm91xda said:
Hi, thanks for the answer. Fortunately i've just resolved the problem. It worked after I wiped data from the STOCK recovery (it was the first thing i've done with the cwm several times but unsuccessfully). Now it works perfectly. Thanks again :victory:
Click to expand...
Click to collapse
For future references. Most likely the reason why your phone didn't boot up is because you 'erase' a partition and left it unformatted. The 'erase' command wipe out the partition so no data is there and it can't access it. If you erase userdata, then there would be no accessible internal storage and the phone cannot boot.
Which is why after you erase it, you need to either flash something over it or format the partition to make it blank: fastboot format userdata (this is what Format DATA option in TWRP is).

[SOLVED]A500 Stuck on OS Load

Tired, Frustrated and Helpless I am at the moment.
My A500 was running OK with a Jelly Bean Rom( I forgot which one) with Skrilax_CZ's bootloader V8 and CWM v5.5.0.4.
I decided to try a different Jelly Bean Rom. Forgot to keep a CWM backup and my misery started.
Any rom and gaps will install fine. But after reboot it will be stuck on Cyogenmod or Android LOGO. I have tried several ROM. Exact same result.
This happened a few months back and after trying numerous times I gave up for that time.
But I need to get the tablet back to working.
So, since yesterday I have been trying my best to get this one to work.
Started with "[A500 & A501] Android 4.4.4 (OmniROM unofficial)".
According the installation note for that rom, I installed CWM 6.0.4.5 on secboot following the "[Recovery]CWM 6.0.4.5[UPDATED WITH INSTRUCTIONS][25/12/2013]" process.
Same exact situation. ROM will install then after reboot it will be stuck on OS load.
Tried with a few other older rom such as CM10-FLEX_V6Supercharged_Rev3.4. Same issue.
I even, Installed TWRP recovery openrecovery-twrp-2.6.3.0-a500 on secboot. Same Issue.
Then, Updated Skrilax_CZ's bootloader V8 to Skrilax_CZ's bootloader V9. Same Issue.
Weird thing is now when I go to "CWM 6.0.4.5" from "Skrilax_CZ's bootloader V9", CWM doesn't really let me do any task. Any menu I enter on CWM 6.0.4.5 it freezes and then reboots the tablet. But initially when I first installed CWM 6.0.4.5 on secboot it worked for the first few times.
I am a noob in this. I do not want to try anything else myself as I think I will eventually brick the device and there will be no coming back.
I have searched on XDA for this issue. Many other people have similar issue with a500 but I couldn't find any situation same as mine.
Need help from you awesome people.
I do not want to give up on this tablet. But without your HELP I am lost.
Please HELP.
Need help on this please.
iamtapu said:
Need help on this please.
Click to expand...
Click to collapse
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
HenrikE said:
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
Click to expand...
Click to collapse
tried that. same issue.
it keeps circling on cyanogenMOD logo.
Apologies for reply late. I was not well and could not attend to you reply.
anything else i can try?
Please help.
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Same here
I have had exactly the same issue and haven't yet found a decent solution.
Mine was stuck on the Acer logo with the stock ICS ROM.
I found my CPUID and SBK, the linux way.
I tried everything you tried, managed to have bootloader V9 installed, TWRP as a recovery (Thor's version), CWM as secboot.
I was able to wipe and flash with no errors, but it would always stuck on the Acer logo. No custom ROM would ever boot.
I will definitely try Unimatrix-zero's solution and tell you guys if it worked for me.
So far, the only thing that worked for me was to use an EUUs package (GEN1) to get back to stock HC 3.01.
As you may guess, there are no more OTA updates via wifi in 2014.
So I downloaded several update packages and so far I only managed to update to HC 3.2. I haven't yet found a working package for stock ICS.
Anyway, if Unimatrix-zero's workaround actually works, a custom ICS ROM will do the trick for me.
Unimatrix-zero said:
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Click to expand...
Click to collapse
Significant result but did not resolve the issue.
As you have mentioned, I have wiped off everything that i can find in the recovery menu.
rebooted after that to recovery and for the first time I could go to TWRP 2.7.
tried to install a custom rom. but same issue. Either it reboots when I tried omni rom 4.4.4 on the "booting from primary" menu or the CM blue circle going on forever, when I tried with a CM 10.1 rom.
and just now after trying the cm 10.1 rom it went back to the way it was before. now the TWRP 2.7 will just keep on blinking on the screen .
Help bro...help....
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Unimatrix-zero said:
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Click to expand...
Click to collapse
you are a GOD SEND for me.:highfive::highfive::highfive::victory::victory::victory::victory::victory:
Did the following as you mentioned.
Code:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
boot recovery TWRP 2.7.
Installed OMNI 4.4 rom.
Installed GAPS.
NOW its booting to OMNI rom...
awesomeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

[ZE551KL] Stuck in bootloop, need complete rebuild. Help!

OK, 3 days ago I rebooted my ZE551KL and it went into a bootloop. I was completely 100% stock. No root. Locked bootloader. Spent the better part of the weekend trying to troubleshoot it, and I have made almost zero progress.
I've tried a bunch of things, but here is my current status.
Can get into fastboot mode no problem.
POWER + DOWN VOL gets me into stock recovery, but at some point I flashed an older version. I tried flashing TWRP, but after install could never seem to get into it (is that because I'm unrooted and locked?)
Current recovery version: Android system recovery <3e> LRX22G.WW_user_1.16.40.763_20151201
I've tried flashing to a couple different firmware versions from the ASUS website both via ADB and via the SD Card.
Current firmware: UL-z00T-WW-1.17.40.1531-user.zip
Still in bootloop.
Any advice on rebuilding this thing from scratch? I dont care whether I just get stock back, or if I need to root/unlock, install TWRP and a custom ROM. Dont care, just want a functioing phone!
Thanks in advance.
ACFH said:
I dont get it. Did you factory reset your phone? With stock rom, factory work most of the time.
You said that you tried flashing TWRP. If you see successfull message after flash, type "fastboot reboot" and hold volume down button right after hit Enter. If you did right, you can get into twrp, then choses Wipe > format, it more powerfull than factory reset.
Click to expand...
Click to collapse
1. Factory reset from within the phone's OS? No, I cant get that far. Just constant bootloop on ASUS logo.
2. I've used the fastboot erase command to wipe everything, and used the wipe data/factory reset option in the stock recovery. Still bootloop.
3. I've tried flashing TWRP 3.0.0.0 and the newest version of TWRP. I hold down the VOL DOWN key before hitting enter on "fastboot reboot"; it just goes into a faster bootloop, like every half-second. When I release the VOL DOWN key, it goes into the same, slower original bootloop.
ACFH said:
Ok. You can format through fastboot
Code:
fastboot format userdata
fastboot format cache
If it still stuck in bootloop, try reflash boot and recovery, fastboot wipe system. Then copy update.zip to sdcard. Boot into recovery > install update from external sd.
Click to expand...
Click to collapse
Awesome. I'll give that a try and report the results.
I just downloaded the .img with the same date as my recovery version from here. https://asus.kremowka.xyz/categories/show/2
Its been hung at "Verifying update package...." for about 10 mins now. Once this is finished (and probably fails ); I'll give your format commands a try.
ACFH said:
Ok. You can format through fastboot
Code:
fastboot format userdata
fastboot format cache
If it still stuck in bootloop, try reflash boot and recovery, fastboot wipe system. Then copy update.zip to sdcard. Boot into recovery > install update from external sd.
Click to expand...
Click to collapse
Ugh. Didn't work. Here is what I did:
fastboot format userdata
fastboot format cache
fastboot erase system
fastboot format system
Reboot to recovery
install UL-z00T-WW-1.17.40.1531-user.zip from SD card.''
Installation successful.
Reboot.
In a bootloop that shows ASUS logo for 10-15 seconds, flashes a blue screen really quick, then reboots.
What can I try next?

Help me fix my bootlooping N6P

While I was on vacation my N6P (Android 6.01 MTC20L) decided it was time to give me the bootloop of death - talk about timing!
I have a recent backup I made via Flashfire saved on my PC but I need to get my phone booted - at least temporarily.
As I said my phone is on 6.01, but the fix offered by @XCnathan32 (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) is for Nougat and above. So what are my options?
- Should I use fastboot to upgrade to Nougat or Oreo then apply the fix?
- How do I dirty flash N or O without losing my data?
- Any ideas on the heating notion? Some people have had their phones working using a blow/hair dryer..is it dangerous to heat the phone? Will any parts get damaged?
Any response would be useful to me, thanks!
boeder9 said:
While I was on vacation my N6P (Android 6.01 MTC20L) decided it was time to give me the bootloop of death - talk about timing!
I have a recent backup I made via Flashfire saved on my PC but I need to get my phone booted - at least temporarily.
As I said my phone is on 6.01, but the fix offered by @XCnathan32 (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) is for Nougat and above. So what are my options?
- Should I use fastboot to upgrade to Nougat or Oreo then apply the fix?
- How do I dirty flash N or O without losing my data?
- Any ideas on the heating notion? Some people have had their phones working using a blow/hair dryer..is it dangerous to heat the phone? Will any parts get damaged? Any response would be useful to me, thanks!
Click to expand...
Click to collapse
More information would be useful to determine whether you really have BLOD or just bootlooping. What were you doing when it bootlooped? Was it just spontaneous? Are you able to access stock recovery or TWRP? Do you have a stable fastboot mode? If so, two options to try would be to use ADB to update using a newer version full OTA (eg. 7.0.0 (NRD90T)) or flash a full image (not OTA) with flash-all.bat, removing the -w (wipe) switch. Both of these methods will leave your data intact. If you don't have access to recovery mode (bootloops on selecting) or an unstable fastboot mode, then you are pretty much left with the hairdryer.
v12xke said:
More information would be useful to determine whether you really have BLOD or just bootlooping. What were you doing when it bootlooped? Was it just spontaneous? Are you able to access stock recovery or TWRP? Do you have a stable fastboot mode? If so, two options to try would be to use ADB to update using a newer version full OTA (eg. 7.0.0 (NRD90T)) or flash a full image (not OTA) with flash-all.bat, removing the -w (wipe) switch. Both of these methods will leave your data intact. If you don't have access to recovery mode (bootloops on selecting) or an unstable fastboot mode, then you are pretty much left with the hairdryer.
Click to expand...
Click to collapse
Thanks for the response.
- Phone was idle for a few moments thats when the bootlooping started.
- I was rooted (bootloader unlocked) with TWRP, I am unable to access it, takes me to the bootloop again
- What do you mean by stable fastboot. I can get to the fastboot mode by power button, volume down, remains there (if that's what you mean?)
boeder9 said:
Thanks for the response.
- Phone was idle for a few moments thats when the bootlooping started.
- I was rooted (bootloader unlocked) with TWRP, I am unable to access it, takes me to the bootloop again
- What do you mean by stable fastboot. I can get to the fastboot mode by power button, volume down, remains there (if that's what you mean?)
Click to expand...
Click to collapse
No access to Recovery mode is one hallmark of the BLOD. Without Recovery you have no ADB, even if it was enabled previously. Stable fastboot mode means you can actually flash something successfully and it completes before bootlooping again. Many people who are unlocked can start flashing, but it won't finish -or- flashing completes successfully, but the phone never boots up. Try the following: fastboot format your system, userdata, and cache and observe for errors. Do these 3 complete successfully? Next, fastboot FLASH the latest TWRP to your recovery partition.... errors? Try fastboot BOOT the same in an effort to get a working Recovery where you have some additional tools. If these fail, you are looking at either RMA if eligible or replacing the phone.
fastboot format system
fastboot format userdata
fastboot format cache
v12xke said:
No access to Recovery mode is one hallmark of the BLOD. Without Recovery you have no ADB, even if it was enabled previously. Stable fastboot mode means you can actually flash something successfully and it completes before bootlooping again. Many people who are unlocked can start flashing, but it won't finish -or- flashing completes successfully, but the phone never boots up. Try the following: fastboot format your system, userdata, and cache and observe for errors. Do these 3 complete successfully? Next, fastboot FLASH the latest TWRP to your recovery partition.... errors? Try fastboot BOOT the same in an effort to get a working Recovery where you have some additional tools. If these fail, you are looking at either RMA if eligible or replacing the phone.
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
Do these commands (espec system and userdata) erase my data and app data/personal files?
Ill try these and get back
boeder9 said:
Do these commands (espec system and userdata) erase my data and app data/personal files? Ill try these and get back
Click to expand...
Click to collapse
Formatting userdata will, but you won't be saving anything if you can't access recovery. If you like, try formatting system and cache first. Look for errors. Then try fastboot flashing or fastboot booting TWRP. The action of formatting each partition will tell you if there is a problem with the internal memory, and correct it (if possible).
v12xke said:
Formatting userdata will, but you won't be saving anything if you can't access recovery. If you like, try formatting system and cache first. Look for errors. Then try fastboot flashing or fastboot booting TWRP. The action of formatting each partition will tell you if there is a problem with the internal memory, and correct it (if possible).
Click to expand...
Click to collapse
OK so I did fastboot format cache, finished fine (see attached)
Haven't done format system, is it safe? what will the system formatting erase?
As for TWRP do you mean fastboot flash recovery twrp.img?
EDIT: after the cache format I'm getting 1-2 red LED flashes before each bootloop, is this the battery being down? If I turn off the device, hook up the charger it shows a full battery with electricity charge sign and phone boots again to bootloop.
boeder9 said:
OK so I did fastboot format cache, finished fine (see attached)
Haven't done format system, is it safe? what will the system formatting erase?
As for TWRP do you mean fastboot flash recovery twrp.img?
EDIT: after the cache format I'm getting 1-2 red LED flashes before each bootloop, is this the battery being down? If I turn off the device, hook up the charger it shows a full battery with electricity charge sign and phone boots again to bootloop.
Click to expand...
Click to collapse
System is a read only partition. Formatting it will not cause any data loss of yours, but will temporarily render the phone not bootable... BUT It can easily be restored via fastboot from any factory image. You just extract and flash the system image back to the system partition. Userdata is your personal data. When you format that partition your personal data will be gone. You did mention you had a FF backup so I'm guessing that was on the backup.
Yes on flashing TWRP. If after FLASHING twrp you cannot access Recovery, then try BOOTING recovery- fastboot boot recovery twrp.img
If you get to a point where nothing is working and you decide to format system and userdata and they complete successfully, you can flash a full Google image using flash-all.bat
Not sure about the LED's but just make sure your battery is close to fully charged. You didn't ever mention an battery issue, so there shouldn't be one. If in doubt hook the charger up and let it sit before proceeding.
@v12xke
Thank you for all your help. I left the phone on charge and let it bootloop for a good period of time and went out, came back and it was booted. I disabled the big clusters as suggested by @nicotinic in ElementalX and the device appears to be working fine aside from a little lag. I can live with that
Currently doing a little ADB pull, then will clear some space for a full nandroid backup!
Thanks a bunch to you both.

LineageOS on LG G3 keeps booting back into TWRP

I'm trying to install LineageOS on an LG G3 I bought, so I rooted the phone successfully on its stock firmware, then installed a terminal emulator, them copied over the TWRP image and ran these commands in the terminal on the phone:
Code:
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-3.3.1-0-d855.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I then rebooted the phone and booted into TWRP 3.3.1-0 successfully. I downloaded a recent LineageOS nightly (lineage-15.1-20190724-nightly-d855-signed.zip) and copied it to the phone. Then I booted into TWRP again, selected Install, selected the image, and it claimed to install it. But now when I reboot the phone, it shows the LineageOS opening screen animation for maybe 2 minutes, then reboots the phone again and shows TWRP. What's going wrong?
OK I managed to fix it by first going to wipe, and wiping Data, Cache, and Dalvik. Installed after that and it booted OK.

Categories

Resources