Missing data partition boot loop - T-Mobile LG G4

I was following the instruction in http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227 to install TWRP using adb and fastboot and I'm pretty sure I messed up because once I installed a ROM(AOKP) through TWRP and rebooted I get the attached error in a boot loop. As far as I can tell it seems I'm missing the /data partition and that is causing a crash which it tries to recover from by rebooting. Before I started I was on 6.0 official with no root or TWRP.
I'd appreciate in help in figuring out if this is fixable and if so how.
Thank you.

Use LG UP to Refurbish and flash a 10n or 20i Stock .kdz.

Related

[Q] Can't Install TWRP

LG G2 VS98024A
Rooted with Ioroot
Tried AutoRec, result: gets stuck in fastboot, have to reflash partition files
Tried GooManager, result: secure boot error
Tried flashing loki and recovery via ADB, result: secure boot error
Tried Flashify, result: gets stuck in fastboot, have to reflash partition files
Thank you in advance.
tyrell22 said:
LG G2 VS98024A
Rooted with Ioroot
Tried AutoRec, result: gets stuck in fastboot, have to reflash partition files
Tried GooManager, result: secure boot error
Tried flashing loki and recovery via ADB, result: secure boot error
Tried Flashify, result: gets stuck in fastboot, have to reflash partition files
Thank you in advance.
Click to expand...
Click to collapse
Autorec, make sure it's the proper version for your phone and your baseband is at 24A also. Otherwise follow steps 5-9 here - http://forum.xda-developers.com/showthread.php?t=2702958
mjones73 said:
Autorec, make sure it's the proper version for your phone and your baseband is at 24A also. Otherwise follow steps 5-9 here - http://forum.xda-developers.com/showthread.php?t=2702958
Click to expand...
Click to collapse
I followed the instructions on the linked post.
It Worked! Thank you!

Bricked bricked bricked!!!!

HELP! So I posted a thread earlier of my personal root method but it's buggy but the closest I can get to a successful root on Android M for Lgh81110N running software 20i android M
I was toying with methods of mounting the system as RW manually and stupidly changed the permissions of /system to 0666 via chmod in a terminal emulator! All I get now is the splash boot logo with the flashing boot LED and it will restart, I can access download mode and factory reset mode but that's it and I tried to flash stock firmware for my device but it's android L and I can't find stock for h811 for android M.
KDZ method DOESN'T work and all It says is that there is an error and stops the update! Someone please help me to either make this damn flash tool work or figure out a way I can flash my device with defualt /system!
Bootloader is unlocked and mostly rooted, never fully successfully flashed twrp but managed to boot it a few times with adb commands! Any other information you may need I can answer!
have you tried using fastboot to flash your system partition?

Stuck in recovery after 4.0.1 OTA

Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.

Stucked in Encryption Unsuccesful help!

I need help, I was trying to root my Oneplus 3T, with stock OOS 4.0.2. After following all the steps, I flashed the dm-verity to keep with the steps, and that worked. But after formatting data, as it was suggested, it gave me an error. It showed like everything was encrypted which shouldn't due to the flash of the dm-verity and now I'm stucked in not a bootloop because the phone actually boots but I cant do anything because the encryption error takes me back to the recovery, which shows an error etc. Is there any tutorial to fully recover the phone from this point? Thank you very much in advance.
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Anova's Origin said:
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Click to expand...
Click to collapse
Now I'm stuck in a bootloop after reflashing stock recovery. If i reflash the boot.img via fastboot from the .zip of the official OOS 4.0.1, will it work? Thank you very much
Not sure why flashing recovery would cause a bootloop. Might be safer just to sideload a fresh ROM. If you're worried about losing files, you can use adb to pull whatever you need first from sdcard prior to flashing.
What I did in a similar situation was to reflash the stock recovery first using the unbrick-toolkit. When booting into recovery then, there is an option "forget password" when it asks you to enter the password. If you select that, it will simply wipe your phone completely and you can start over again.

Stuck in Recovery Mode Boot Loop w/ dm-verity error. Tried all I can think of.

Hello everyone,
I am not completely new to customizing but I've run into a problem and I have tried everything I knew to try and everything I have searched for online so far.
What I have:
Galaxy Note 5
SM-N920T
Baseband: N920TUVS5ERF2
I installed twrp to perform a full system backup in preparation for a full factory reset. The backup was successful, no problem there. I did the factory reset from twrp, now all the phone will do is reboot into the recovery menu and now it says "dm-verity error... failed code: 0x02)
I flashed it back to full stock with ODIN with the latest firmware, which said successful, but boots into recovery.
I flashed 4 of the older official firmware, boots into recovery.
I reflashed twrp and restored the backup, boots into recovery.
I flashed a custom rom, recovery.
Had twrp reload the filesystem with EXT4...
Used ADB to disable verity checks...
Used ADB to pull, push and rebuild permissions for the build.prop edited to disable verity checks...
Nothing has worked and I am out of ideas.
Hopefully, someone reading this will have the key to getting this fixed. It's a good phone, well cared for and I don't want to replace it.
Thanks in advance for any and all help. :fingers-crossed:
flash no-verity-opt-encrypt zip file?
topgunpilott said:
Hello everyone,
I am not completely new to customizing but I've run into a problem and I have tried everything I knew to try and everything I have searched for online so far.
What I have:
Galaxy Note 5
SM-N920T
Baseband: N920TUVS5ERF2
I installed twrp to perform a full system backup in preparation for a full factory reset. The backup was successful, no problem there. I did the factory reset from twrp, now all the phone will do is reboot into the recovery menu and now it says "dm-verity error... failed code: 0x02)
I flashed it back to full stock with ODIN with the latest firmware, which said successful, but boots into recovery.
I flashed 4 of the older official firmware, boots into recovery.
I reflashed twrp and restored the backup, boots into recovery.
I flashed a custom rom, recovery.
Had twrp reload the filesystem with EXT4...
Used ADB to disable verity checks...
Used ADB to pull, push and rebuild permissions for the build.prop edited to disable verity checks...
Nothing has worked and I am out of ideas.
Hopefully, someone reading this will have the key to getting this fixed. It's a good phone, well cared for and I don't want to replace it.
Thanks in advance for any and all help. :fingers-crossed:
Click to expand...
Click to collapse
Contact me on [email protected]
I will help you

Categories

Resources