Database Users

[Q] Soft brick after trying to flash resurrection

I have a G2 from Verizon (VS980).
It was running KitKat 4.4.2 stock rooted.
I run a Nandroid backup using TWRP.
I flashed the Resurrection Remix ROM.
On restart I entered a boot loop.
Turned off, rebooted into TWRP recovery, did a complete swipe (system, cache, dalvik and data).
Tried restoring from Nandroid backup and could not find any backup files (perhaps I don't know where to look but all folders appear empty).
Tried rebooting into download mode and got stuck at installing some drivers (could take 10 minutes) with nothing happening.
Screen says Rooted and I am guessing that could be the issue. I don't know how to proceed.
Can someone help please?

Download another 4.4.2 based ROM. I'm assuming you are attempting to flash a lollipop 5.0.2 ROM. Is that the case?

untamed1 said:
I have a G2 from Verizon (VS980).
It was running KitKat 4.4.2 stock rooted.
I run a Nandroid backup using TWRP.
I flashed the Resurrection Remix ROM.
On restart I entered a boot loop.
Turned off, rebooted into TWRP recovery, did a complete swipe (system, cache, dalvik and data).
Tried restoring from Nandroid backup and could not find any backup files (perhaps I don't know where to look but all folders appear empty).
Tried rebooting into download mode and got stuck at installing some drivers (could take 10 minutes) with nothing happening.
Screen says Rooted and I am guessing that could be the issue. I don't know how to proceed.
Can someone help please?
Click to expand...
Click to collapse
I ran in to that problem when trying to go from a G3 rom to Lollipop. My solution was this:
1. Boot in to TWRP
2. Plug phone in to computer (pc should recognize it; sometimes it wouldn't and I had to mount then unmount /system partition from TWRP
3. Drag and drop a Kit Kat based rom (and GAAPS if need be) from your computer on to the root of your device
4. Flash from there
Let me know if you have any issues with that. I did manage to lose everything saved on my device which led me to a valuable lesson learned, that being: once you back up the device in TWRP, be sure to transfer that backup to your PC in case you mistakenly wipe the device clean later.

RETRObruzzin said:
I ran in to that problem when trying to go from a G3 rom to Lollipop. My solution was this:
1. Boot in to TWRP
2. Plug phone in to computer (pc should recognize it; sometimes it wouldn't and I had to mount then unmount /system partition from TWRP
3. Drag and drop a Kit Kat based rom (and GAAPS if need be) from your computer on to the root of your device
4. Flash from there
Let me know if you have any issues with that. I did manage to lose everything saved on my device which led me to a valuable lesson learned, that being: once you back up the device in TWRP, be sure to transfer that backup to your PC in case you mistakenly wipe the device clean later.
Click to expand...
Click to collapse
Retobuzzing, thank you for the quick response. Thanks also for your last recommendation, gotta do that too next time.
I have actually found my solution reading in a post that I should try entering download mode by pressing both volume keys together while you connect the micro usb connector. That worked even though the screen gives you no feedback except for the led turning red (kind of scary at first :fingers-crossed.
After doing that I was able to follow the directions in the article titled: "How to unbrick LG G2 with stock firmware" at the Androidcure.com site.
The phone was restored to the original stock conditions and later I was able to update it to software version 26A.
Note to Forum Moderators: You can close this tread if desired. Thanks.

Yes I am!
Snuzzo said:
Download another 4.4.2 based ROM. I'm assuming you are attempting to flash a lollipop 5.0.2 ROM. Is that the case?
Click to expand...
Click to collapse
Your assumption is right on the money.:good:
Do you have a suggestion on a better lollipop ROM for the G2?
Any idea on could have caused the boot loop after flashing Resurrection remix?

untamed1 said:
Your assumption is right on the money.:good:
Do you have a suggestion on a better lollipop ROM for the G2?
Any idea on could have caused the boot loop after flashing Resurrection remix?
Click to expand...
Click to collapse
Only 1 assumption. Didnt downdate back to 12b bootloader/modem.

A6000 rom and Gapps problems

Hey folks I'm new here and I recently rooted my phone and flashed a z5 rom from the XDA rom thread. Link below
http://forum.xda-developers.com/len.../rom-xperia-z5-rom-lenovo-a6000-plus-t3393251
And flashed this nano pack of this gapps Link below
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
So it all went fine but now I'm incurring some problems.
Firstly I didn't notice that the Gapps is closed for updates I don't know if that affected the issue but the Google play is not working and some other Google stuff as well.
And I thought I'll flash new Gapps which are being kept up to date but my phone won't connect with the PC with the usb now so I don't know how do I flash the Gapps now.
I have re Rooted my phone using the Kingo app but it still won't reconnect.
So any help on these issues would be really helpful!
One last question that if I do find a way to flash the Gapps will I have to reflash the rom again?
Thanks

Parvarsingh said:
Hey folks I'm new here and I recently rooted my phone and flashed a z5 rom from the XDA rom thread. Link below
http://forum.xda-developers.com/len.../rom-xperia-z5-rom-lenovo-a6000-plus-t3393251
And flashed this nano pack of this gapps Link below
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
So it all went fine but now I'm incurring some problems.
Firstly I didn't notice that the Gapps is closed for updates I don't know if that affected the issue but the Google play is not working and some other Google stuff as well.
And I thought I'll flash new Gapps which are being kept up to date but my phone won't connect with the PC with the usb now so I don't know how do I flash the Gapps now.
I have re Rooted my phone using the Kingo app but it still won't reconnect.
So any help on these issues would be really helpful!
One last question that if I do find a way to flash the Gapps will I have to reflash the rom again?
Thanks
Click to expand...
Click to collapse
First dowload the gapps from opengapps.org. Go here choose ARM>>5.1.1>>nano/pico.
Then, boot into recovery, wipe system, data, cache, dalvik and then flash the ROM again and the gapps. All done...!!!

sasukay said:
First dowload the gapps from opengapps.org. Go here choose ARM>>5.1.1>>nano/pico.
Then, boot into recovery, wipe system, data, cache, dalvik and then flash the ROM again and the gapps. All done...!!!
Click to expand...
Click to collapse
That's the prob right. I cant reach the custom bootloader I don't know why. Do you think its because of the new rom ill have to use some different recovery? I am usin twrp right now and even I used it to flash this rom. Please help

Parvarsingh said:
That's the prob right. I cant reach the custom bootloader I don't know why. Do you think its because of the new rom ill have to use some different recovery? I am usin twrp right now and even I used it to flash this rom. Please help
Click to expand...
Click to collapse
""usin twrp right now"" -- can you boot into it..??
You press vol up + vol down along with power key and release the power key once the lenovo logo shows up, to boot into twrp

sasukay said:
""usin twrp right now"" -- can you boot into it..??
You press vol up + vol down along with power key and release the power key once the lenovo logo shows up, to boot into twrp
Click to expand...
Click to collapse
no cant boot into it.
I go into the fast boot mode enter recovery commands in the command window. Then try to boot into recovery but it doesn't go into recovery. The Lenovo screen stays there or it boots straight into the phone
This method worked before like I used this way to flash the rom but now its not working.
Any help?

Parvarsingh said:
no cant boot into it.
I go into the fast boot mode enter recovery commands in the command window. Then try to boot into recovery but it doesn't go into recovery. The Lenovo screen stays there or it boots straight into the phone
Click to expand...
Click to collapse
Brother, you have made it really confusing for me. Earlier you said that you can't boot into bootloader, but now you can boot into fastboot..!!
Also, your phone, instead going to recovery, boots directly to system. That means your phone is in working condition(Is it..?), which you didn't told me earlier.
So, if you can boot into system (normal boot). Download Rashr from play store (or from any other source) and flash this TWRP 3.0.2. (First extract this zip and then choose recovery from storage option in Rashr to flash).

Please help, possible bricked phone???

Hey guys so my phone appears to me to be bricked. I have a rooted angler on stock 7.0.0 (NBD90X, Oct 2016). I have ElementalX kernal.
A few weeks ago I was looking in to putting on MultiROM. After I flashed the custom TWRP recovery for MultiROM, the recovery wouldn't work. It just goes to the TWRP blue startup screen and freezes. I have been procrastinating on flashing a functioning recovery ever since. I know, I'm an idiot. Lesson learned. Well the November security update was pushed to my phone a few days ago. I ignored it. Last night I wanted to see if the update included 7.1 or if it was just security update, so I tapped on the update notification and it automatically downloaded the updates without prompt (which I did not want to do.)
Well an hour later my phone died. When I plugged in to the charger, it immediatly started up by itself and booted to the non-functioning recovery and froze. It does this every time I try to boot the device now. I booted in to the bootloader and tried plugging in to my PC to flash a working recovery, but the device will not get picked up by the PC anymore. I don't believe it's a driver issue I use adb all the time with this same device and pc.
Also want to add, factory reset from bootloader went to google startup animation, but then just shut off as soon as it was done. Also, when I select shutdown from bootloader with it plugged in to charger, it will turn off and stay off but does not appear to be charging in any way.
Well that's the backstory. Any help you all can provide is very much appreciated. Turns out the battery in my backup phone is only good for a couple hours anymore. You all know how helpless we are without our phones, ha! Please help! Is it bricked?

I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.

RoyJ said:
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
Click to expand...
Click to collapse
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?

Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Edit: If you can boot to bootloader your device should be read with 'fastboot devices' - if it isn't, delete any Android / Nexus / Google drivers. **Reboot your PC** and install them again. After you install them again reboot your PC one more time and try again.

RoyJ said:
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Click to expand...
Click to collapse
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.

Nebul0us said:
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Click to expand...
Click to collapse
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.

RoyJ said:
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
Click to expand...
Click to collapse
Okay so I left the phone on the charger with the frozen screen in twrp multirom edition. After that rebooted in to the bootloader. I then selected the factory option. If loaded the google animation like before, but this time actually booted up the system. The notification bar had two diagnostic tools that said tap to run...one was called sims i think? Anyways I held power button and did a hard reboot. It booted up fine. I then used twrp manager to install 3.0.2.2....then i used fastboot to flash 3.0.2.3 that i had a copy of. Things seem to be working fine now. Close call. I'm not sure what the factory option is in the bootloader, but it's not factory reset and it was the only way I could boot. I think the phone was trying to boot to recovery to install the latest updates and I had to boot to factory to get it out of "update mode," if you will...
Does anyone know what the factory option is in the bootloader?
Thanks for your help RoyJ

Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Factory options is meant to restart the system with some manufacturers apps available just so you can test certain functions of the phone, mostly to see if all sensors and hardware are working properly.

Need Help; My LG G6 (H870) keeps booting in TWRP and I can't install stock ROM

Hi,
I unlocked the bootloader of my H870, installed TWRP 3.1.1.0 and SUPERSU. Everything was working great untill I decided to restore my system defaults to make a fresh start with my G6. After choosing the option to restore system defaults, my phone rebooted and it booted into TWRP. I rebooted my phone and it kept doing this all the time.
I decided to look for a stock ROM and flash that ROM.
I succesfully flashed the "LG-H87010f-Flashable.COMPLETE.zip" ROM (from autoprime's post) trough TWRP. But this did not work. I even wiped all the data from my phone (even system) and flashed the ROM again; still nothing.
Before having this issue, I had the same Baseband version, Kernel version, Build number. Only the dates and the Software Version are different.
I had the V10b-EUR-XX Software Version installed on my phone. I see this is the 10f version. I guess this should not be a problem right?
After this I took these steps solve this issue:
1. Downloaded new LG Mobile Drivers (LGMobileDriver_WHQL_Ver_4.2.0)
2. Downloaded and installed LGUP. LGUP doesnt recognize my phone as a LG G6 and this method did not work for that reason.
Fastboot mode is working on my phone; I can reboot my phone trough the commandline on my PC and things like that . However, my PC is not recognizing my phone as a LG G6 device in Fastboot mode.
My PC recognices my phone as a H870 when in TWRP. In Fastboot mode it recognices my phone as Android Device.
3. Installed LG Bridge for more drivers; did not work either
4. Downloaded Uppercut, but it doenst work without LGUP.
4. Looked all over the internet to find a Stock ROM in .zip or .img format; found nothing
5. Downloaded WindowsLGFirmwareExtract-1.2.6.1 and tried to extract the H87010d_00_OPEN_EU_OP_0327.kdz file. I extracted it into .bin files, but they were not usable. After that, I combined these .bin files into a system.img file. But that .img file was bigger then 5 GB and for that reason it was not usable to flash trough Fastboot or TWRP.
7. Looked for other methods to obtain a H870 Stock Rom, including another extraction method, but I cant figure out how to do this.
I have spend countless hours on this problem, but I cant find an usable H870 stock rom to flash my phone with.
Is there someone that can help me out with this problem? Im willing to donate some € if someone helps me to get my phone working again.
Really hoping for a kind person to help me out and provide me solution for this issue.
Thanks in advance

Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.

autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?

RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.

RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.

Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:

autoprime said:
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
Click to expand...
Click to collapse
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:

RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
RoyalD said:
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
Click to expand...
Click to collapse
Probably because you already did all the flashing prior to. Glad it worked. This happened when I first got my V20 and was stoned not thinking. I reset using the in phone option and it caused twrp bootloop. I too learned the hard way.

Had the same issue, fixed it, thanks.

My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.

matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash a firmware trough LGUp, or flash again the last TWRP available trough fastboot.

RoyalD said:
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
Click to expand...
Click to collapse
Please help, i have the same problem and nothing, what exactly is a boot to the hard side? I ve tried to power off the phone, press vol down and power, realase power 1 sec, press again...but nothing...still boot on twrp...
Well, I finally solved it with lgup and uppercut... what a nightmare.

matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash stocl .kdz with uppercut and lg up

Saved my G6!
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Great tip @Swizzle82! It allowed me to restore my LG G6 after bootloop. It had not been detected by PC, and this hardware reset helped!

Hi, all
If I understand, and to sum up :
I rooted my LG-G6 few weeks ago, and intall TWRP. When OTA wants to install official update, the reboot stops in TWRP mod, so ... failed :-/
Is the solution to flash through Uppercut/LGUP with a .kdz file, without risk of brick the phone ?
Thx

HELP! SM -G901F, TWRP can't find storage partition to mount

Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:

Pobi123 said:
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Click to expand...
Click to collapse
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?

BlueCyclone said:
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
Click to expand...
Click to collapse
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping

Pobi123 said:
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Click to expand...
Click to collapse
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.

BlueCyclone said:
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
Click to expand...
Click to collapse
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!

Pobi123 said:
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Click to expand...
Click to collapse
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again

BlueCyclone said:
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
Click to expand...
Click to collapse
Good News! Phone is back in full working order after flashing stock firmware. It was kinda scary though, I had to fix an error in Odin and then the phone wouldn't even boot up! Left it over night, booted it again and it worked fine Thanks a lot for your help, I'll try not to soft brick my device again