i tried to flash the PIE US99830b TWRP zip (was on OREO h) via TWRP. Got stuck at V30 boot logo. OREO was correctly flashed last year and havent had any issues.
Attempted to factory wipe via power+vol down and it goes back to boot screen. I also cannot power down the phone. I was able to get to download mode by usb+vol up after the factory wipe screen. I've tried 2 different versions of the patched LGUP. One being the pie version and the other, the original version i used to flash OREO. Both say no handset connected. I see no device in device manager on my pc. I know my usb cable is working because the device will show up when i plug the usb in during the boot logo hang.
Download screen shows:
Unknown B35
Unknown / E /L / RQ
is my device hard bricked?
Related
Hi!
I'm so stupid. I wanted to install cm12.1. So I rooted phone, unlocked BL. Then, I had first problem - when executing adb oem-unlock BL has unlocked and phone go to fastboot. But my comp couldn't recognize it (heard plugging in and out sound repeatedly). And here comes my "stupidity". I installed flashify and flashed CWM by it, got to CWM, installed cm12.1 zip. Of course wiped all data. Because I didn't flashed boot.img cm12.1 was freezing on fist setting up screen (nothing was working, just power button - pushing 10s turned off phone).
I wanted to flash boot.img by fastboot. But I still had problems with drivers(omap4boot didn't work). So I tried to recovery system by LG Mobile Support Tool. Everything got fine, but then phone stuck on the LG logo.
S/W Uprgade mode works of course, but I can't get to recovery now.
I'm using Windows 8.1
Any ideas?
Edit.
Ok, so I tried to install omap again. I did it, but the phone is still repeatedly conecting and disconnecting and in device manager I cought omap4430 driver whith waring mark for a while. Any ideas now?
Is it the non-animated LG logo?
This should work:
http://forum.xda-developers.com/showthread.php?t=2748384
The download links for the firmware are probably not up to date. Use this to download: http://forum.xda-developers.com/showthread.php?t=2287573
If your phone still goes beyond the non-animated logo, there might be easier solutions.
It was after animation.
Anyway, I have finally solved this problem by installing new system using Bride's solution with full wipe.
I'd appropriate it, if anyone would be willing to help me out with my issue.
I have a LG G2 D801, 32GB.
Had it ROOTED, TWRP Recovery, and Lineage OS 14.1 running perfectly just fine. Until I recently tried to Flash Lineage OS 15.1, which then caused my phone to completely go into a black screen with a dead Android Robot having a exclamation point in a red triangle coming out of it's belly.
Yes, I'm able to get into: Android System Recovery <3e> LRXX22G
- Tried, Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Tried, Wipe Cache Partition, then Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Tried, Wipe Data/Factory Reset, then Wipe Cache Partition, then Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Last but not least, leaving me with the only real option I have left to help fix my phone is the, Apply Update From ADB. (Yes, I tried that one too) Which is why I need your help!
Here's a quick scenario of what happens after trying that last option. (Apply Update From ADB)
-Basically my phone then asks me to ADB Sideload files.
-I connect my phone to my PC. (Windows 7, x64)
-Check my Device Manager to see if it's fully connected, but my D801 connects each time under SAMSUNG Android Phone - AndroidNet Sooner Single ADB Interface. (which I know has to be wrong)
-I go into my CMD Prompt, to access my installed ADB Shell, to search for attached ADB Devices. (Yes, it sees my phone as: LGD801cb55c4e4 sideload)
-I proceed to try to sideload a ROM and after about 30% Signature Verification, Fails causing my D801 to Abort Installation. (no matter what I throw at it, IMG/KDZ/TOT files fail as well.)
Now when it comes to trying the methods listed in: https://forum.xda-developers.com/showthread.php?t=2432476 to Flash Stock Firmware, I simply can't because my D801 doesn't connect to my PC in Device Manager under Ports or QHSUSB_BULK. (it connects each time under SAMSUNG Android Phone - AndroidNet Sooner Single ADB Interface.
I've also tried SRKtool_2.1_droidth which ends up leaving me at another dead end.
If you have the time please help, and or point me in the right direction.
I've already installed the needed drivers:
qualcomm-driver
adb-setup-1.4.3
LGMobileDriver_WHQL_Ver_4.2.0
Downloaded all the corresponding files to my PC for my D801:
Firmware Files (KDZ & TOT also Extracted)
LG Flash Tool 2014 & 2015
SRKtool_2.1_droidth
Megalock DLL File
D801 DLL File
LGUP
Silly suggestion perhaps, but after freaking out for about an hour when this happened to me I ended up realizing I could reboot to TWRP using the hard keys. Honestly, I only mention it because I was trying everything else too. If you didn't already try it (I didn't see it in your description) I think it's the power key and volume down key while it's off and as soon as you see the splash screen, release them both and immediately repress and hold them both until you see TWRP. Just a thought.
I loved that phone!
Sent from my [device_name] using XDA-Developers Legacy app
Just tried your technique @C-Tec. Thank you. But that only brings up the Factory Data Reset Screen (to Erase all user data & Restore default settings) instead of the TWRP Recovery screen. (so that's a dead end)
Because, after selecting Yes, Erasing data and Restoring default settings, my phone reboots in to the same loop I started from, as if I never did anything to remedy the situation.
Update on my progress:
-So I was able to get in to Download Mode. (holding the VOLUME UP button, while the phone is off)
-Followed by the Firmware Update Screen after plugging my phone in to my PC via USB. (which then read my phone as - LG Mobile USB Serial Port. (COM8) under Ports in Device Manger)
-I then Flashed the D801 Stock Lollipop KDZ. (by using the LG Flash Tool 2014)
-Waited for the progress bar to completely fill to 100% and BOOM! I fixed my problem.
-Android Lollipop running like NEW. (that's 2014 NEW :crying
-Now to retry Lineage OS 15.1.
Here's a helpful Video Clip, to understand how to use the Flash Tool. -
Just search for: LG G2 - Fix LG Logo Stuck/ Boot Loop Fix / Flash Firmware - EASY METHOD in YouTube.
Being that I'm low ranked I cant post any links just yet, sorry.
I even went out of my way and ordered a LG V20 off of Swappa, which arrives tomorrow. Due to this issue.
I flashed TWRP to the device successfully, and proceeded to try to install Magisk 19.3 zip. It would begin to do a recovery bootloop. I fixed it using TWRP, and tried using the patched boot img from magisk manager instead. This is where things go wrong. After flashing boot.img, the phone refuses to boot, and asks me to do a factory reset. I did this twice, and the phone continued not to boot. I then tried installing the latest android Q factory image. The flash failed, and the phone stopped showing up when I do fastboot devices or adb devices. It is stuck in the bootloader telling me slot b is not bootable. I have tried different ports, but adb and fastboot are no longer responding.
Take out the battery for 10 sec or more replace, see if you can get back into recovery. Recovery should be TWRP.
You may need to uninstall and reinstall the driver on your computer. IF it is a Win computer should show up in device manager at the top under Android.
https://www.xda-developers.com/how-to-install-custom-rom-android/
or you can do a factory reset which is also a button.
I fixed it by holding down the power and vol up buttons, which allowed me to use fastboot again and fixed everything. Thanks for the help tho>
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
why did you u
Insomnium_D said:
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
Click to expand...
Click to collapse
why did you OTA update the rooted phone
it is clearly written that your phone might brick.
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
I didn't, because I get (as always, this is not my first rooted phone) the message, that the system has been changed. OTA is not working and I read that uninstall magisk, update the phone and BEFORE reboot install magisk again on partition B. But I accidentaly pressed the second option in magisk, complete uninstall or how its name is. Didn't expected, that its start instantly without a "Caution" message.
Uninstalling Magisk should not bring my phone into a bootloop anyway, even if I wipe the cache. Or am I wrong?
raja0408 said:
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
Click to expand...
Click to collapse
That is the problem how do I do that, when everything with odin stops imediately or odin crashes.
Does Odin give you any error messages? Are you patching all of the files for the firmware AP BL CP & CSC? Are you making sure to use the non home CSC? Have you tried using Samsung Smart Switch to recover your phone?
Smart Switch didn't recognize the phone. The only error on Odin was "succeed 0 / failed 1).
It worked with Windows 10 notebook and the USB C Port. However it didn't worked on Win 7 and regular USB Ports. Very strange. Well, but now I have the original firmware and again lots of bloatware. TWRP doesn't work, impossible to boot with it. How can I root the A52 with Magisk that way, to deactivate it - if needed - for firmware updates? The phone doesn't has A/B partition.
Same happened to me.
So, I have an A52 Indian version and want to flash the Canadian firmware. I downloaded different versions of the Canadian firmware and used Odin to flash. I followed the instructions on downloading the files, loading them into Odin,hit Start and it kept failing. It was giving an error message regarding a repartitioning error. Could this be due to having to tick "OEM Unlocking" in developer options which I hadn't done?
Hey, is your phone still stuck ?
SHAREit​
Hi guys been spending all night trying to figure out but seems nothing is working. HELP! I know i can get it to work.
So tried to root my A2017G previously but saw all the horror brick stories so ended up just doing the multiple OTA updates via SDCARD upgrade.zip and finally ended up with OREO BO3 version. running fine except for ridiculous battery meter levels playing up but just kept it charged most of the time.
1) at first I tried to check bootloader unlock status from fastboot. But somehow unable to as fastboot is not there! So i thought maybe fastboot is corrupt (stock recovery options ok / also power plus down gets stuck in FTM mode (easy to reboot with adb command) So unable to check bootloader (i am thinking its probably still locked)
2) so got latest version of TWRP 3.3 something and flashed it --> result in phone black screen but detectable (I assume in EDL mode.) '
3) Tried to flash Nougat B10 EDL with EDL tool (working now but after everything is ready to flash it says"" 13:02:38: {ERROR: WritePort:5164 Could not write to '\\.\COM8', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times""
4) MiFlash unable to read hello packet. But i tried pressing power and connecting quickly and suddenly starts flashing B10 nougat EDL ROM but doesnt complete with a "function: sahara_rx_data:237, unable to read packet header" error. Should I be using a stock rom with Meta-INF folder rather than the EDL version? Also should i be flashing OREO stock rom rather than nougat with MiFlash? or it doesnt matter?
5) tried the DFU tool initially qualcomm and com8 detected but says disconnected. (so its in EDL probably but somehow still disconnected?
So currently
1) trying to let the phone battery run out, though i doubt its any use as i probably bricked it installing twrp without unlock bootloader on OREO.
2) Also downloading Oreo stock rom to try and flash with miflash.
Any help or point to some discussion i missed would be helpful thanks. Just wanna get root and GPS tools running so I can let the kids catch some Pokemon without GOing outside.
Seems like the battery had to run out first. Then it started recharging . After about 5 mins I just pressed power button without up or down. Phone rebooted nicely back into Oreo. PhEW... Then i used a stock 2017g EDL for nougat B10 (7.1.1) and flashed with Miflash by going into proper EDL (used ADB reboot EDL command)
Ok some more small hiccups along the way but being able to access EDl i managed to flash TWRP 3.2.1 and then load it up and flash SuperSU for root.
Now to read the threads on how to get rid of the bootloader unlock screen as well as load in the battery saving scripts.