Hello so I'm trying to restore my LGV20 H910 from the original dump I made prior to rooting my phone.
Currently my phone is stuck in a TWRP loop after I tried to reflash the v10r rom from https://forum.xda-developers.com/v20/development/h910-return-to-stock-v10m-t3669956
I managed to reflash that ROM successfully once earlier, then realized I forgot to flash Magisk and went backwards to try again... then it said something like the ROM couldn't boot because of some encryption problem... and now it's just stuck on TWRP. I want to reverse everything and go back to unrooted stock as I've been having problems with my phone in terms of signal and also apps just randomly crashing or the entire phone freezing.
So the dump I have is missing the META-INF folder and also all the files have _COM11 at the end of them. What should I do to create a fully flashable ZIP? And if this doesn't end up working (i.e. still stuck in TWRP loop) what should my next steps be?
edit: don't need help with the twrp loop anymore, used the rom here https://forum.xda-developers.com/v20/development/h910-return-to-stock-v10m-t3669956 but i am still interested in being able to use my old dump
Related
Hello everyone and I apologize if there's been a solution to this before but I couldn't find it.
I was on Rooted stock V20F, and there was a new OTA update from LG (around 110 MBs). Before installing anything i made a backup from TWRP Recovery just in case anything went bad.
So after I download the official update, the phone reboots, and boots into TWRP recovery. From that moment, I can't get the phone to boot properly no matter what I do.
I tried restoring my backup, the phone will still boot into TWRP. Tried Factory Reset, Format Data, installing a new custom rom and nothing. It always brings me back to TWRP.
Also when i try to get into download mode so I can flash a KDZ file with flash tool, it boots into TWRP again.
Any ideas? Thanks a lot in advance.
edit: I actually found the solution here (it wasn't in the troubleshoot section and I didn't notice it..): http://forum.xda-developers.com/showthread.php?t=2451696
Is there any way to install official OTA updates without the phone freaking out?
Hello,
today I managed to brick my device and restore it to working state, and I wonder at what point I made an error.
So here's what I did:
Had stock lollipop 30b
Rooted using oneclick root+recovery
Installed twrp using autorec
Xposed etc. and used it for a while without problem
Decided to flash something new
AOSPA 5.1.1 seemed like a good choice
Flashed bootstack, that was mentioned in aospa thread, system and gapps
Wow, that was smooth, but I needed my apps next day so I decided to restore my stock backup
Restored backup and ended up with phone in 9006 mode
Later I did some stupid moves that made whole situation worse, but that's not the point.
I backed up and restored everything that twrp allowed me to, so not only system and data, but also boot, efs, modem, recovery, sns etc. Could this be the cause? I didn't change bootstack, because I thought, that I had the needed one (autorec puts kk bootstack, right? and aosp roms also require this).
What should I do to avoid such problems in the future? I'll probably flash a lot, trying to find best possible rom for me, so it's neccesary to now whatto avoid.
And tip for future newbies like I was: if you can enter download mode, then use it, flash tool won't wipe your device data when you're using normal flash. When you've got normal working system to begin with then you can tinker further.
(Also there seems to be no way to recover from demigod critical error, even though it says it enters recovery. Then it's only this method with shorting capacitors on motherboard (fix real hardbrick)).
Cheers,
Marmelada
You can flash the patch (go back to LP from Sombons), flash, reboot recovery, restore stock rom and reboot.
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:
One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.
I need help.
So I tried doing a clean flash, didn't work.
I was stuck at the loading screen when booting the phone.
I was previously on latest OOS 4.X.X with Magisk and TWRP.
Somehow, my OP5 was now back on stock recovery.
I just installed TWRP back again (blu's).
Everything is encrypted (in /sdcard/). I can't seem to transfer files to my cellphone, either through
HTML:
adb push
or manually dragging and dropping files from Windows 10.
TWRP doesn't ask me for my previous PIN, and I can't seem to tranfer files... any way I can gain access/install a rom again ?
At worst if I could find a way to push my TWRP backup and recover everything....
Can I flash a ROM that's on my PC without pushing it on the cellphone ?
Any help is greatly welcome and appreciated. Thanks for your help in advance guys.
EDIT: I've wiped everything and was able to tranfer and flash the latest ROM, then flashed TWRP again without rebooting.
Upon system boot, the welcome screen showed up, but android.com.phone kept crashing and after a while a factory reset happened.
I just pushed TWRP back again and I'm kind of wondering what to do now...
EDIT2: Flashed OOS 5.0.0, then realized 5.0.1 was out. I relocked the bootloader and did the OTA update since it was a clean, not rooted install. Working good... now I need to root it again.
I had OB3 installed with the unlocked bootloader and I wanted to try installing TWRP and going back to stock recovery.
So what I did was:
1. Install TWRP
2. Launch TWRP and confirm that it is working
3. Flashing boot.img from the OB3 stock dump from the related dev thread
4. The OS boots but it is stuck in "Android is starting". It seems that it cannot complete the process and starts from scratch for some reason
After this issue, I also tried to sideload OB3 OTA but no avail.
Do you have any idea what I might be doing wrong? Or is there a solution to this issue without reflashing the full rom?
If I recall when rooting my phone, after flashing the files in TWRP I had to select which partition to reboot to (A or B) and had this same problem before realizing I was booting into the wrong partition. New to Android so someone with more experience may have more useful info....