My V30+ was fine until I flashed a new ROM (LineageOS 16.0) and then it started booting slow, now taking like 2-3 minutes. I reset everything in TWRP recovery and flashed back to Lineage 15.1 but it still occurs. Is there something I could have messed up? Has anyone else had this issue?
Averie said:
My V30+ was fine until I flashed a new ROM (LineageOS 16.0) and then it started booting slow, now taking like 2-3 minutes. I reset everything in TWRP recovery and flashed back to Lineage 15.1 but it still occurs. Is there something I could have messed up? Has anyone else had this issue?
Click to expand...
Click to collapse
Flash the stock rom what's so bad in stock rom?
trouble. said:
Flash the stock rom what's so bad in stock rom?
Click to expand...
Click to collapse
I did flash stock, same thing. I hate it as well.
Averie said:
I did flash stock, same thing. I hate it as well.
Click to expand...
Click to collapse
You're saying on stock your phone takes 3 minutes to boot?
On rooted stock firmware, from the time I hit "Power off and restart" through bootloader unlock warning, LG boot animation and back to my wallpaper is 56 seconds.
ChazzMatt said:
You're saying on stock your phone takes 3 minutes to boot?
On rooted stock firmware, from the time I hit "Power off and restart" through bootloader unlock warning, LG boot animation and back to my wallpaper is 56 seconds.
Click to expand...
Click to collapse
Exactly
Averie said:
I did flash stock, same thing. I hate it as well.
Click to expand...
Click to collapse
were you able to fix it? having the same problem
same problem here, even after flash KZD from LGUP Dual Mode - 2-3 minutes to boot :/
Postmanpl said:
same problem here, even after flash KZD from LGUP Dual Mode - 2-3 minutes to boot :/
Click to expand...
Click to collapse
Have you tried flashing an Oreo KDZ? I'm not sure, but you may need to do that if coming from a Pie ROM like LOS 16. You can then try flashing the Pie KDZ afterward.
Osprey00 said:
Have you tried flashing an Oreo KDZ? I'm not sure, but you may need to do that if coming from a Pie ROM like LOS 16. You can then try flashing the Pie KDZ afterward.
Click to expand...
Click to collapse
I tried Resurrection Remix 17, and then I flashed stock Pie - that was a problem.
In download mode I saw, that something is wrong with partitions - some notice in red. So I go back to Oreo - flashed KZD Oreo in LGUP, and then again KZD Pie. Now boot time is normal. Thanks for tip
Related
So i had a hardricked phone(i thought) but than it worked again. So i flashed pacrom and it went in a hardbrick like state again (using twrp btw)I flashed it with nano gaps and the b330 package so you could get the fingerprint scanner. Than after an hour or so it worked again. Than i started running my battery low on purpose so i knew if it was just stuck or if it was something else. When my phone dies it will reboot again and work. And then i flashed rr with the nano gapps and the b330 package and it did this again, I thought it might have something to do with the b330 package so i flashed it without and it still did this. Then i thought it might have something to do with my twrp because i was still running on version 3.0.0 so i flashed the newer version through fastboot and it did this again!!
I dont know what is going on but my phone is acting really strange.
Does someone know of this problem or has ever heard of it or is my phone just strange?
jimandroidnerd said:
So i had a hardricked phone(i thought) but than it worked again. So i flashed pacrom and it went in a hardbrick like state again (using twrp btw)I flashed it with nano gaps and the b330 package so you could get the fingerprint scanner. Than after an hour or so it worked again. Than i started running my battery low on purpose so i knew if it was just stuck or if it was something else. When my phone dies it will reboot again and work. And then i flashed rr with the nano gapps and the b330 package and it did this again, I thought it might have something to do with the b330 package so i flashed it without and it still did this. Then i thought it might have something to do with my twrp because i was still running on version 3.0.0 so i flashed the newer version through fastboot and it did this again!!
I dont know what is going on but my phone is acting really strange.
Does someone know of this problem or has ever heard of it or is my phone just strange?
Click to expand...
Click to collapse
I have no idea why you keep flashing the firmware b330 it only needs done one time
clsA said:
I have no idea why you keep flashing the firmware b330 it only needs done one time
Click to expand...
Click to collapse
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
jimandroidnerd said:
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
Click to expand...
Click to collapse
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
jimandroidnerd said:
i didnt know that. so is that whats causing my issue and can it be fixed?
ps: now its doing it again cuz i flashed the newest twrp through fastboot
Click to expand...
Click to collapse
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
clsA said:
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
Click to expand...
Click to collapse
Demian3112 said:
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
Click to expand...
Click to collapse
I will do that. thanks for the help everyone
clsA said:
you need to consider putting your phone back to stock using the dload / update.app for your version nd leave it their until you figure out if your phone is broken or not. flashing roms is just confusing the situation.
Click to expand...
Click to collapse
Demian3112 said:
Hi Jim, Indeed you need to fully revert back and see if it works.. i will provide you some links since we are from the same region/country.
1. Flash the stock recovery
2. Download this file and put the update.app in a file named 'dload' on the root of your sdcard.
3. Shutdown the phone hold Volume Up+Down and Hit the power button it should start booting and applying the update. Just leave it for like 30 minutes and u should be back at B130 firmware. Then you should receive a update for B140 and once you are on B140 u can upgrade back to B330.
Report back if it worked or you encountered any other issues!
Click to expand...
Click to collapse
Ok so i have gone back to stock, everything is working again as far as i can tell. Just done it 10 minutes ago. I will test for a week to see if erverything is working properly. Is it safe to flash custom roms / recovery after i have confirmed everything is working properly? Thank you guys so much for the help btw, i really appreciate it!:good:
jimandroidnerd said:
Ok so i have gone back to stock, everything is working again as far as i can tell. Just done it 10 minutes ago. I will test for a week to see if erverything is working properly. Is it safe to flash custom roms / recovery after i have confirmed everything is working properly? Thank you guys so much for the help btw, i really appreciate it!:good:
Click to expand...
Click to collapse
did you take all the updates to b330 ? if so you can pretty safely go to CM13 + gapps nano without any worries.
use one of the newest versions of TWRP
Do a factory reset and flash only CM13 and gapps
reboot let it fully load .. reboot to recovery / backup your fresh install to ext-sd
boot back to the OS and setup your new device.
So recently, my phone went into bootloop for no reason. I was using stock firmware, no root or modifications of any sort.
I'm not able to access recovery mode, boot the phone(in safe mode as well). The only screen I was able to get to was download mode.
However, I don't want to flash custom firmware on it because that would make me lose my data.
Help of any kind to help me backup my files or fix the problem would be appreciated.
UPDATE: I was able to install TWRP onto the phone, but it freezes after the first of seconds of boot.
Is there any important data on the phone? If not, did u factory reset it?
Akshat2100 said:
Is there any important data on the phone? If not, did u factory reset it?
Click to expand...
Click to collapse
There's a lot of important data on the phone. I can't possibly lose it.
aryan.arora180 said:
There's a lot of important data on the phone. I can't possibly lose it.
Click to expand...
Click to collapse
Did you flash the correct version of twrp?
callumbr1 said:
Did you flash the correct version of twrp?
Click to expand...
Click to collapse
Yeah, I even tried multiple versions of TWRP. I tried arter97's TWRP recovery as well and it didn't freeze but it wasn't performing any opeartions(factory reset, installing ROMs, MTP)
aryan.arora180 said:
Yeah, I even tried multiple versions of TWRP. I tried arter97's TWRP recovery as well and it didn't freeze but it wasn't performing any opeartions(factory reset, installing ROMs, MTP)
Click to expand...
Click to collapse
V 3.1.1-0 is the correct version.
Have you tried flashing stock firmware?
callumbr1 said:
V 3.1.1-0 is the correct version.
Have you tried flashing stock firmware?
Click to expand...
Click to collapse
I tried flashing stock firmware as well. It ends up in a bootloop only.
aryan.arora180 said:
I tried flashing stock firmware as well. It ends up in a bootloop only.
Click to expand...
Click to collapse
Sounds like your flashing the wrong firmware. What's your model? G925? And Android version and region?
callumbr1 said:
Sounds like your flashing the wrong firmware. What's your model? G925? And Android version and region?
Click to expand...
Click to collapse
It's the G925I - the international variant. I bought the phone in India and it was latest on nougat.
Should I restore the Marshamllow version instead?
aryan.arora180 said:
It's the G925I - the international variant. I bought the phone in India and it was latest on nougat.
Should I restore the Marshamllow version instead?
Click to expand...
Click to collapse
http://updato.com/firmware-archive-select-model?record=304ED2348A3811E7963AFA163EE8F90B
Try this one first mate
callumbr1 said:
http://updato.com/firmware-archive-select-model?record=304ED2348A3811E7963AFA163EE8F90B
Try this one first mate
Click to expand...
Click to collapse
Sure, I'll try it out.
callumbr1 said:
http://updato.com/firmware-archive-select-model?record=304ED2348A3811E7963AFA163EE8F90B
Try this one first mate
Click to expand...
Click to collapse
Hey sorry for the late reply... I had to travel and bought the OP5 in a hurry.
Tried flashing the firmware you gave, but it had the same result - bootloop.
Any luck? Mine just did the same thing this morning. To be a little more clear, my ph-1 (USA, Sprint purchased) ran the battery out last night. When I plugged it in, it bootlooped. I entered boot loader and shut it down. Fast forward - charged all night, no difference. Bootloader is locked and there is no recovery (phone hasn't been modified at all, unless you count Holy Diver as a ring tone
CtDMonet said:
Any luck? Mine just did the same thing this morning. To be a little more clear, my ph-1 (USA, Sprint purchased) ran the battery out last night. When I plugged it in, it bootlooped. I entered boot loader and shut it down. Fast forward - charged all night, no difference. Bootloader is locked and there is no recovery (phone hasn't been modified at all, unless you count Holy Diver as a ring tone
Click to expand...
Click to collapse
Sorry for the late reply.
I gave it to a service center. They simply replaced the battery and it was working fine for a day. The next day the same things started happening again, and I sent it back to them.
I upgraded to nitrogen os 8.0 few weeks back. all going ok but flashed firmware update few days back and continually getting signal drops. the signal does not hold for longer than few minutes then disappears and comes back while later. Every rom I have tried since suffers from the same issue.
I have tried to flash miui 8 and miui 9 but although they eventually flash they stay on bootscreen (poweredby android screen) and never load. I left it overnight on that screen and never loaded?
Any help greatly appreciated. any help of any kind :crying:
irishchris2014 said:
I upgraded to nitrogen os 8.0 few weeks back. all going ok but flashed firmware update few days back and continually getting signal drops. the signal does not hold for longer than few minutes then disappears and comes back while later. Every rom I have tried since suffers from the same issue.
I have tried to flash miui 8 and miui 9 but although they eventually flash they stay on bootscreen (poweredby android screen) and never load. I left it overnight on that screen and never loaded?
Any help greatly appreciated. any help of any kind :crying:
Click to expand...
Click to collapse
just download lazyflasher for miui flash it after you flashed miui rom.
irishchris2014 said:
I upgraded to nitrogen os 8.0 few weeks back. all going ok but flashed firmware update few days back and continually getting signal drops. the signal does not hold for longer than few minutes then disappears and comes back while later. Every rom I have tried since suffers from the same issue.
I have tried to flash miui 8 and miui 9 but although they eventually flash they stay on bootscreen (poweredby android screen) and never load. I left it overnight on that screen and never loaded?
Any help greatly appreciated. any help of any kind :crying:
Click to expand...
Click to collapse
U should flash miui using Mi flash tool or if u wanna stay on nitrogen oreo or any custom rom u should first flash the latest firmware available before flashing any rom
I have done that but unfortunately it gets stuck on boot screen. Cheers
irishchris2014 said:
I have done that but unfortunately it gets stuck on boot screen. Cheers
Click to expand...
Click to collapse
Have u tried flashing miui using flash tool?
If yes for how much time u had waited on that boot screen bcs it takes more then 15-20 minutes before it boots up
And remember to take backup of ur data before flashing
Criston said:
U should flash miui using Mi flash tool or if u wanna stay on nitrogen oreo or any custom rom u should first flash the latest firmware available before flashing any rom
Click to expand...
Click to collapse
Criston said:
Have u tried flashing miui using flash tool?
If yes for how much time u had waited on that boot screen bcs it takes more then 15-20 minutes before it boots up
And remember to take backup of ur data before flashing
Click to expand...
Click to collapse
Yes it only worked once through my flash tool. Fails now when I try. The time it did flash, I left it plugged in overnight and on boot screen but never got past the mi powered by android bootscreen
irishchris2014 said:
Yes it only worked once through my flash tool. Fails now when I try. The time it did flash, I left it plugged in overnight and on boot screen but never got past the mi powered by android bootscreen
Click to expand...
Click to collapse
I think u r not properly flashing u have to choose clean all option in Mi flash tool otherwise it won't work and before that u should backup all the important data and files from ur internal storage
Criston said:
I think u r not properly flashing u have to choose clean all option in Mi flash tool otherwise it won't work and before that u should backup all the important data and files from ur internal storage
Click to expand...
Click to collapse
I did click that option but fails on flash nearly straight away, thanks
irishchris2014 said:
I upgraded to nitrogen os 8.0 few weeks back. all going ok but flashed firmware update few days back and continually getting signal drops. the signal does not hold for longer than few minutes then disappears and comes back while later. Every rom I have tried since suffers from the same issue.
I have tried to flash miui 8 and miui 9 but although they eventually flash they stay on bootscreen (poweredby android screen) and never load. I left it overnight on that screen and never loaded?
Any help greatly appreciated. any help of any kind :crying:
Click to expand...
Click to collapse
Having the same problem of signal drops in evry single rom. Its really bad to see developers not doing anything about it. And regarding that flashing, if u flash official miui by official twrp, then it will not boot. U have to use modified twrp to flash the official firmwares.
pritamdutt said:
Having the same problem of signal drops in evry single rom. Its really bad to see developers not doing anything about it. And regarding that flashing, if u flash official miui by official twrp, then it will not boot. U have to use modified twrp to flash the official firmwares.
Click to expand...
Click to collapse
Good to see it's not just me having this issue! Have you found any solution yet? What version of twrp do you suggest? I have been using red wolf recovery
pritamdutt said:
Having the same problem of signal drops in evry single rom. Its really bad to see developers not doing anything about it. And regarding that flashing, if u flash official miui by official twrp, then it will not boot. U have to use modified twrp to flash the official firmwares.
Click to expand...
Click to collapse
Developers have nothing to do with network drops, its Xiaomi sources.
irishchris2014 said:
Good to see it's not just me having this issue! Have you found any solution yet? What version of twrp do you suggest? I have been using red wolf recovery
Click to expand...
Click to collapse
No solution till now. Getting frequent internet disconnects. The only thing which is keeping me in the custom rom is the adoptable storage , cause m using the standard variant 16gb and its internal storage sucks.
For twrp, refer here:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
same issues here, running LOS official with default kernel, had the same problem always. I thought it might be antenna related as I had to order a new usb daughterboard due to poor microphone, (had reception issues with a note1 in the past due to a fake usb board lacking gsm antenna) but I think this is not the case here. Always updating the latest firmware hoping that can help but so far not.
Hello friends:
seeking help with a soft brick V30+
Story: I've been running stock VS996 20i on a converted LS998. Now TWRP gets stuck on splash screen(TWRP-3.2.3-7-IntSD.img) after trying to dirty flash VS996_20j on an encrypted device. Mistake??? I think so, cause now phone wont boot to OS or to Recovery.
In download mode connected to LGUP+V30DLL_PATCHED; phone shows the VS996 20j.
Question: How do I get recovery back? Can it be done via download mode? Do I need to downgrade back to Nougat or can I reflash recovery from LGUP?
Thanks all!!!
20j TWRP has been having some issues. Take a look at that thread for help on how to get it back. You may just have to KDZ back to a working version. I hear the KDZ works fine, just the TWRP is failing. It's a work in progress still.
When I got stuck with 20j only way out was to lgup us998 N then to us998 O.. That was with DL partition tho.
neocyke said:
When I got stuck with 20j only way out was to lgup us998 N then to us998 O.. That was with DL partition tho.
Click to expand...
Click to collapse
So you basically Frankenstein'ed again, but your bootloader was already unlocked.
I'm sorry but has no one tried flashing 20i again................... Because that literally worked dozens of times for all the debugging I did for john.
TotallyAnxious said:
I'm sorry but has no one tried flashing 20i again................... Because that literally worked dozens of times for all the debugging I did for john.
Click to expand...
Click to collapse
The first guy said he lost TWRP, so he couldn't flash the 20i zip again. And flashing full KDZ 20i in LGUP would just give stock VS996 with no fastboot flash commands to reinstall TWRP. Unless I'm misunderstanding your suggestion.
steevo23 said:
Story: I've been running stock VS996 20i on a converted LS998. Now TWRP gets stuck on splash screen(TWRP-3.2.3-7-IntSD.img) after trying to dirty flash VS996_20j on an encrypted device. Mistake??? I think so, cause now phone wont boot to OS or to Recovery.
In download mode connected to LGUP+V30DLL_PATCHED; phone shows the VS996 20j.
Question: How do I get recovery back? Can it be done via download mode? Do I need to downgrade back to Nougat or can I reflash recovery from LGUP?
Thanks all!!!
Click to expand...
Click to collapse
ChazzMatt said:
The first guy said he lost TWRP, so he couldn't flash the 20i zip again. And flashing full KDZ 20i in LGUP would just give stock VS996 with no fastboot flash commands to reinstall TWRP. Unless I'm misunderstanding your suggestion.
Click to expand...
Click to collapse
The zip wouldn't have gotten rid of twrp. It does nothing to the recovery partition. It just doesn't work that way.
TotallyAnxious said:
The zip wouldn't have gotten rid of twrp. It does nothing to the recovery partition. It just doesn't work that way.
Click to expand...
Click to collapse
Well not get rid of TWRP but still lost the ability to successfully boot into TWRP. He said it was stuck on TWRP splash screen.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Well not get rid of TWRP but still lost the ability to successfully boot into TWRP. He said it was stuck on TWRP splash screen.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
That's completely different lol
TotallyAnxious said:
That's completely different lol
Click to expand...
Click to collapse
And I don't know about the others...
Sent via open market LG US998 V30/V30+
Let me add a quick query here or start new thread, idk. Us998, messed up recovery, laptop says unauthorized device in adb. No boot either, what are my options?
Been out-of-town for a bit, so just wanted to thank everyone who contributed remarks.
As described before...after the dirty flash of 20j, phone could/would not boot back into recovery. It either boot-looped or got stuck on the splash screen. So I decided the easiest way to get working was to use LGUP to downgrade back to N. Essentially, repeating the Frankenstein process. Now I'm back to 20i again.
I'm just wondering if it was the encryption which caused the issue to begin with. Perhaps there is a conflict with dirty flashing ROMs on an encrypted OS?
IIRC, flashing over encrypted Data partition almost always ends up with bootloops, no boot or in worst cases a brick. But then that's in twrp. I don't think lgup flashing does that since it repartitions everything if you go with DL..
I tried restoring from a twrp backup when I got stuck in a bootloop. the phone boots up into lock screen then after a couple seconds restarts.
I have tried flashing different a kdz on lgup and the master reset as well.
vlowbot said:
I tried restoring from a twrp backup when I got stuck in a bootloop. the phone boots up into lock screen then after a couple seconds restarts.
I have tried flashing different a kdz on lgup and the master reset as well.
Click to expand...
Click to collapse
What variant do you have, what KDZ are you flashing? Did you try Refurbish mode?
Sent via open market LG US998 V30/V30+
ChazzMatt said:
What variant do you have, what KDZ are you flashing? Did you try Refurbish mode?
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I have the H931 converted to a US998. I have been using UD99820b kdz I will try refurbish right now,
Edit: tried refurb still having the same problem
vlowbot said:
I have the H931 converted to a US998. I have been using UD99820b kdz I will try refurbish right now,
Edit: tried refurb still having the same problem
Click to expand...
Click to collapse
get back to Nougat via refurbish, do a hard reset right after , then refurbished back to Oreo
vlowbot said:
I have the H931 converted to a US998. I have been using UD99820b kdz I will try refurbish right now,
Edit: tried refurb still having the same problem
Click to expand...
Click to collapse
Mrxyzl said:
get back to Nougat via refurbish, do a hard reset right after , then refurbished back to Oreo
Click to expand...
Click to collapse
Also, after you go back to US998 Nougat with Refurbish, then do the Master Reset, and when you refurbish back to Oreo go ahead and go to 20H KDZ.
Your bootloader should still be unlocked, I would think. (However, if you don't see the bootloader unlock warning after Nougat and Master Reset, then go to 20b)
From 20H, then you can reinstall TWRP, and flash the three root files again (no encryption, root check disable, and Magisk).
ChazzMatt said:
Also, after you go back to US998 Nougat with Refurbish, then do the Master Reset, and when you refurbish back to Oreo go ahead and go to 20H KDZ.
Your bootloader should still be unlocked, I would think. (However, if you don't see the bootloader unlock warning after Nougat and Master Reset, then go to 20b)
From 20H, then you can reinstall TWRP, and flash the three root files again (no encryption, root check disable, and Magisk).
Click to expand...
Click to collapse
Mrxyzl said:
get back to Nougat via refurbish, do a hard reset right after , then refurbished back to Oreo
Click to expand...
Click to collapse
I am still just restarting a couple of seconds after getting to lock screen. It kind of looks like the phone doesn't actually complete the reset it goes the deleting screen for about 2 seconds before rebooting.
vlowbot said:
I am still just restarting a couple of seconds after getting to lock screen. It kind of looks like the phone doesn't actually complete the reset it goes the deleting screen for about 2 seconds before rebooting.
Click to expand...
Click to collapse
it is a symptom of not following the Frankeinstein method correctly. Did yo ugo back to Nougat and do a Master reset>?
Mrxyzl said:
it is a symptom of not following the Frankeinstein method correctly. Did yo ugo back to Nougat and do a Master reset>?
Click to expand...
Click to collapse
I am still just rebooting at lock screen
steps I have done:
refurb to 20b
master reset
refurb to 20h
am I missing something am I supposed to let it boot to android before I do the master reset?
vlowbot said:
I am still just rebooting at lock screen
steps I have done:
refurb to 20b
master reset
refurb to 20h
am I missing something am I supposed to let it boot to android before I do the master reset?
Click to expand...
Click to collapse
I don't see that you first flashed Nougat, then did Master Reset before going to Oreo.
Nougat would be 10c or 10d (your choice).
Oreo starts in the 20's.
Frankenstein Instructions say to flash Nougat, then Master Reset, then go to Oreo. There's a reason for each step I don't have time to explain here.
Something about your phone is messed up and doing Frankenstein over (Nougat, Master Reset, then Oreo) should fix it.
ChazzMatt said:
I don't see that you first flashed Nougat, then did Master Reset before going to Oreo.
Nougat would be 10c or 10d (your choice).
Oreo starts in the 20's.
Frankenstein Instructions say to flash Nougat, then Master Reset, then go to Oreo. There's a reason for each step I don't have time to explain here.
Something about your phone is messed up and doing Frankenstein over (Nougat, Master Reset, then Oreo) should fix it.
Click to expand...
Click to collapse
thanks that did it <3 . I got a little confused on my kdz
vlowbot said:
thanks that did it <3 . I got a little confused on my kdz
Click to expand...
Click to collapse
Don't flash Magisk 19.4 for root in TWRP yet. Try Magisk 18.1 first and then update once rom is setup and stable.
vlowbot said:
I tried restoring from a twrp backup when I got stuck in a bootloop. the phone boots up into lock screen then after a couple seconds restarts.
I have tried flashing different a kdz on lgup and the master reset as well.
Click to expand...
Click to collapse
Help! How do I get out of bootlop? I already tried the master reset but it doesn't work
JavierC53 said:
Help! How do I get out of bootlop? I already tried the master reset but it doesn't work
Click to expand...
Click to collapse
It DOES work if you flashed the right firmware.
If you have a constant bootloop and Master Reset doesn't fix it, it means you usually have flashed the wrong firmware.
I'm betting that you tried to flash Oreo first instead of Nougat.
What letter/number US998 Nougat did you flash? Did you use Partition DL mode?
Please read Frankenstein Instructions again. You should be asking in that thread if you are trying to convert one North American variant to another.
ChazzMatt said:
It DOES work if you flashed the right firmware.
If you have a constant bootloop and Master Reset doesn't fix it, it means you usually have flashed the wrong firmware.
I'm betting that you tried to flash Oreo first instead of Nougat.
What letter/number US998 Nougat did you flash? Did you use Partition DL mode?
Please read Frankenstein Instructions again. You should be asking in that thread if you are trying to convert one North American variant to another.
Click to expand...
Click to collapse
help me, my v30+ us998 stuck on bootloop logo screen and can`t force power off, i tried to hard reset but not work, i tried flash to Nougat use US99810c_03_1216.kdz ,it stuck again after erasing and back again to logo and stuck.
Greyzu said:
help me, my v30+ us998 stuck on bootloop logo screen and can`t force power off, i tried to hard reset but not work, i tried flash to Nougat use US99810c_03_1216.kdz ,it stuck again after erasing and back again to logo and stuck.
Click to expand...
Click to collapse
If you already have US998 V30+, why are you flashing US998 Nougat? What are you trying to achieve?
You don't need that for bootloader unlock -- you need early Oreo 20a or 20b. The only reason to flash Nougat are for North American variants who have to convert to US998, before flashing US998 Oreo 20a or 20b. Most can't flash directly to Oreo 20a/20b, they have to first flash Nougat, and do Master Reset, then flash early Oreo.
Were you using Partition DL or Refurbish? Read the Master Reset directions again.
ChazzMatt said:
If you already have US998 V30+, why are you flashing US998 Nougat? What are you trying to achieve?
You don't need that for bootloader unlock -- you need early Oreo 20a or 20b. The only reason to flash Nougat are for North American variants who have to convert to US998, before flashing US998 Oreo 20a or 20b. Most can't flash directly to Oreo 20a/20b, they have to first flash Nougat, and do Master Reset, then flash early Oreo.
Were you using Partition DL or Refurbish? Read the Master Reset directions again.
Click to expand...
Click to collapse
I want to try using US99820b_03_0524.kdz, and choose to refurbish, any other suggestions??
Greyzu said:
I want to try using US99820b_03_0524.kdz, and choose to refurbish, any other suggestions??
Click to expand...
Click to collapse
Read the Master Reset directions again?
If you press the buttons long enough, hopefully it will reboot.
Still didn't answer why you were flashing Nougat, when you already had USS98 firmware? You only needed to flash USS98 20b.
I'm afraid you unneccessarily flashed it because you didn't read instructions carefully, so I don't know what else you didn't read carefully...
Hope you get it working again!