Related
Sorry for the duplicated post. I just noticed the other one i posted is in the wrong section and this is the one for the AT&T phones so here it is again.
Hi Guys. Today i rooted my phone for the first time (LG Optimus G e970)
Everything went well, then i uninstalled the bloatware from AT&T and a few of the google apps that i do not use like books or music, and on the next reboot i got my phone bricked with the LG loop and "Security Error" message.
I found some great info on these forums on getting the phone in working condition with the help of this: http://forum.xda-developers.com/show....php?t=2388440
However, before i go ahead and restore the phone's original firmware, i would like to know if there is anyway to recover some of the files. I have some important notes i wish to recover, everything else is on google and the external SD card so im not all lost.
I am able to put the phone in download mode by holding the up and down volume keys and then powering on the phone with the usb cable connected to the PC, but it is not showing as an external disk on the computer. I do have the LG drivers installed tho, the same ones i used to root the phone.
Any ideas?. thanks a lot.
What recovery do you have ? You may be able to mount internal and sd card in recovery and access them on your computer ?
optimusv45 said:
What recovery do you have ? You may be able to mount internal and sd card in recovery and access them on your computer ?
Click to expand...
Click to collapse
Hi thank for the help.
I have no clue about what recovery i have. I never played with the phone before the rooting and removal of the apps, so i believe it should be the "stock" recovery if you wanna call it like that.
axopro said:
Hi thank for the help.
I have no clue about what recovery i have. I never played with the phone before the rooting and removal of the apps, so i believe it should be the "stock" recovery if you wanna call it like that.
Click to expand...
Click to collapse
I don't know what guide you followed to get the root. If you followed this
http://forum.xda-developers.com/showthread.php?t=2450258
You should have twrp. Stock recovery may not be able to mount storages for uses on PCs.
Also I haven't seen the post you included , maybe that's an older post. A lot of people use this to recover their "bricked" phones
http://forum.xda-developers.com/showthread.php?t=2230994
I personally have followed this too.
As long as you have download mode you don't have to worry. However you need to read carefully before processing with teenybins because its something that can actually brick your phone if used wrong.
optimusv45 said:
I don't know what guide you followed to get the root. If you followed this
http://forum.xda-developers.com/showthread.php?t=2450258
You should have twrp. Stock recovery may not be able to mount storages for uses on PCs.
Also I haven't seen the post you included , maybe that's an older post. A lot of people use this to recover their "bricked" phones
http://forum.xda-developers.com/showthread.php?t=2230994
I personally have followed this too.
As long as you have download mode you don't have to worry. However you need to read carefully before processing with teenybins because its something that can actually brick your phone if used wrong.
Click to expand...
Click to collapse
Ok so when i did the rooting i followed that same guide you linked to, but i only did it to the root part. Not the "UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-"
I just wanted the permissions to remove the apps.
So now with the TeenyBin guide.... will that erase the current settings and information on the phone or is it just an attempt to fix the firmware loop?
will the process attempt to restore the google apps missing?
axopro said:
Ok so when i did the rooting i followed that same guide you linked to, but i only did it to the root part. Not the "UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-"
I just wanted the permissions to remove the apps.
So now with the TeenyBin guide.... will that erase the current settings and information on the phone or is it just an attempt to fix the firmware loop?
will the process attempt to restore the google apps missing?
Click to expand...
Click to collapse
There are different kind of teenybins. They do different things, one giving you a working recovery and updating RPM/TZ, one restoring your phone to complete factory state. You will have to read it to know what I'm saying here. The one that give you twrp and update your partitions may let your data alone but you will most likely still have the existing bootloop. The gapps missing ? The ones you deleted ? If you use the bin that recovers phones to factory state then you will have all the stock apps again.
Quick update.
I was able to recover the phone and the data in it. :good:
I installed the new boot loader with the teenybin instructions and was able to backup the data partition to an SD card.
Anyway, after that i went for a recovery using the stock firmware and LGNPST and now i lost the boot loader with all the neat options, but got the phone working again, and to my surprise, everything was back there including data and applications,. i dont get it but oh well... im back alive.
Ill backup all the important stuff from now on, and then i will keep messing with the phone again LOL. i learned quite a few things today... ill read more from now on before doing more things.
Thanks for all the help.!!
Good nite
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
ipsmaxes said:
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
Click to expand...
Click to collapse
First step: Don't panic!
Second step: Tell us which version of the G2 you have (carrier) and which update you had on before things went south, and also which version of TWRP you have.
Third step: Please explain what you mean by it not turning on but plugging it into the PC shows odd things.
Does that mean you CAN still get into recovery? Can you get to download mode? But either way, just stay calm. I just helped my buddy with the ATT version fix his phone from a similar issue a couple of days ago and I have also played with the Sprint version quite a bit and am familiar with LGs in general. Lemme know these things and I can help get you back on the right track.
Can you get into recovery mode?
If you can, try the factory reset and reboot your device.
Does your phone connect to adb?
If so i guess you could flash a fresh rom from there.
Correct me if i'm wrong, i am a new user with slight experience.
Same Thing Happened to Me
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
alferdjeffers said:
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
Click to expand...
Click to collapse
Probably would be best to start your own thread. However, what update were you on? I'm hoping that you do have the Verizon version of the G2? What error is on the screen? But generally speaking, you should be able to boot to the software update mode and re-install the stock OS with the kdz file, for most G2 things. I haven't worked on a VZW one though, only Sprint and T-Mobile ones and they're all a bit different.
so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Ilikecheese said:
so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Click to expand...
Click to collapse
you could try putting the sd in your pc to put the rom back on it, then back and try flashing. if that fails, sounds like its toast.
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Ilikecheese said:
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Click to expand...
Click to collapse
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Jewveeski said:
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Click to expand...
Click to collapse
thank you so much for the help (; ill let you know if i succeed
I think you will be okay, maybe try LG Flashtool and usb flash back to stock if those don't work.
I got it. Put the Rom in sd and it worked perfect. Whooo
Whew!..congrats.:good:
For some reason I can't flash from recovery menu..failed to mount sd/card, unknown error 150...
Maybe your SD is formatted in a file system twrp doesn't recognize? I had to reformat my 64gb to fat. I used twrp's built-in advanced wipe function to change external SD file system to fat, others have used a pc-based tool from ridgecomp.
You end up with the couple GB maximum individual file size limit, but I just copied my 11c 2.8gb system.img onto it without any trouble.
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
richsapf said:
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
Click to expand...
Click to collapse
You might be on the 11C update. Try downgrading (there's a thread in here somewhere) to 10b and you should be solid. I don't know if those numbers are correct, but check your build number.
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
B-Nice_88 said:
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
And this check this for blocking an OTA: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
richsapf said:
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
Click to expand...
Click to collapse
Never ever take an OTA if you're rooted. In the future, just get rid of the notification, and then come here. Better yet - after you root, disable updates entirely.
Also, another reason to not take an OTA is because often times there are anti-rollback code in them, just like there is almost always a root patch. The regular "usb back to stock" and all the current root methods don't work on 11C for that very reason, and you have to use the KDZ method instead. If you jump on an OTA too early and find out there isn't a way to get back to the previous version... you're stuck. That happened to tons of people on one of the Galaxys I heard, and it so happened that the patch was a very good one. I've heard that the people who took that OTA are still stuck with it.
For 11C, there were early reports of those that rooted, but did not Bump or edit the system, got lucky and sometimes kept root after the OTA. Have you used a root checker to confirm you don't have root? None of the root methods are going to work on 11C, but you might still have it. If you don't, or something else is messed up, you'll need to get back to 10B to fix it.
Edit: Also, you're going to want THIS thread, not the other two I posted!
I did unroot before ota.. the only way I could at that time, via simple root. I just wanted to get the OTA out of the way(dont know why)
I used root checker, says no root.. If I go back to 10B I will try KDZ; or can I use the LG flashtool and try again with that using port 41, the 10B .dll, and 10B TOT?
For now I will follow your link and do as instructed..
Thank you laura
richsapf said:
I did unroot before ota.. the only way I could at that time.
Click to expand...
Click to collapse
Did you do anything else when you had root? Change anything in the system at all?
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
richsapf said:
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
Click to expand...
Click to collapse
Awesome! And yes, the sd card needs to be reformatted as fat32 for TWRP to see it.
Now that you're back on 10B, you can get the 11C update again if you want using this. The 11C OTA already has a rooted, deodexed flashable zip.
I do have that exact Rom/zip on both internal and ext card. Is there a program in particular to format, or just any, and should I format via pc(hook up usb with Windows 7), or is there a good .apk app.
Also, is 64gigs in any way too much.
Could I go up to 128gigs provided I use fat32.
Should the allocation just stay default? It looks like I can go up to around 4 mbs. Is that a cache type thing.
Sorry I am bombarding all these questions. I love learning this stuff. Need a break from studying for comptia 801/802.
Last, where is the thank u button?
Hello everyone this is my fist guide so be kind with the formatting, i will get better as I post more. I am writing this guide, because like you, the reader, I had installed lineageOS 14.1 and set up the phone and realized there was encryption on it, and with that tried to wipe it in twrp just to find out that it only wiped the encryption key, but not the encryption itself. Don't panic, it isn't all your fault, XD. Stay calm, the last thing you need is to be freaking out, flashing random zips in hopes of fixing it. I will give credit to all of the developers whose tools i am linking at the bottom.
Now that the introductions are out of the way, time for the complimentary dose of warning.
WARNING: Doing this won't guarantee that this will fix it, as every situation can vary. I am not responsible for any bricked devices, thermal reactors coming from your phone after this, or modding before it was cool.
Assuming you can still get into fastboot first you need to gather these files if you don't have them yet.
- Minimal adb and fastboot on windows after installing just drag to desktop to add files to it
- Qualcomm fastboot drivers for axon7tool.exe and for fastboot and adb
- TWRP 3.0.4-1 official for Axon 7
- B29 rollback modded zip on the second tab
- Nougat modem and bootstack
- Tenfar's axon7root.exe (just in case you can't use fastboot. that's what i used because i don't know how to use axon7tool.exe)
- Fastboot image to get fastboot working again flash it in twrp after getting twrp installed again through axon7root.exe
- Some time because this will likely take an hour of your time, assuming you have the drivers and files already downloaded, longer if not and slow internet.
- LineageOS 14.1
- GAPPS 7.1.1 ARM 64
- almost forgot, you also need a microsd card to store the files because we will be wiping your entire internal with this, so back up your lovely dank memes or forever hold the loss.
Step 0.5. if you don't have fastboot working flash the bootloader unlock file by drakenfx to get it working again. if you don't have twrp for whatever reason go to the guide for axon7root.exe linked above and reboot to edl mode by holding all buttons down and have your phone connected to computer to know you are there. there won't be a vibration to let you know, just your computer telling you it has a connected device. now flash twrp, by first renaming the recovery to recovery.img and putting it in the adb folder along with the the root exe and do 'axon7root.exe -p (insert your com number listed in device manager) -r' (without the ' obviously) and it should send the recovery. if it doesn't see your device. make sure you have the drivers installed and make sure you have put down your com number where i left the () at
Step 1. assuming your device boots to this beautiful screen. you need to go back to twrp and drag the B29 zip from your computer to your external sd card from mtp and go to mount and mount system read-only this is very important.
Step 2. flash the B29 modded and let it go through. this will take a few minutes. if the progress bar automatically jumps to the end, you didn't go read only.
Step 3. after it finishes reboot into system and let it set up your system, you can skip through because we will be resetting again anyhow.
Step 4. reboot back to recovery. you can do this by using that pesky bl unlocked message by pressing up on volume as soon as it shows and selecting recovery. there you can see you have stock recovery, don't panic this is what we need. select wipe data factory reset and let it do it
Step 5. go back and skip set up again and reboot to bootloader where you can now 'fastboot flash recovery recovery.img' to get back twrp.
Step 6. flash the nougat bootstack and modem i had you download. after flashing that, go to wipe: Advanced wipe. Select Dalvik, system, data, cache and swipe to wipe. this will format it as ext4 which is what is required to get to lineageOS
Step 7. flash lineageos 14.1 and your gapps category and wait to let it finish. Note, you don't have to flash the modem more than once after flashing lineageos, even for updating. just after leaving B29
Step 8. reboot to make sure your encryption problem is not there
Step 9. set up phone and profit.
If you have done everything right, you shouldn't have bricked and should be back to lineageos 14.1 with no further problems. If you skipped around and got yourself bricked, congratulations because i am not the best at fixing problems, and i can try to help, but you will be at the mercy of the Best devs this community has to offer.
Now to the part where I thank all the Devs who, without their tireless time and effort, would not have made this guide possible and development into this phone in the first place. @Unjustified Dev for the lineageOS build i use as my daily driver for now; you rock dude. ^^
@DrakenFX oh god where do i begin. for the bl unlock zip, B29 modded ota, inspiration to the rest of the community, etc.
@tenfar for the axon7root.exe tool used
@sixohtew for his constant help and advice with not only this guide, but with teaching me to build android. if you are interest in learning how to compile android for any device, he can probably help. he has a very fair deal and is amazing at what he does.
Thank you all for your copious hours of time spent in the building of each great tool and to the community as a whole. Everyone, these guys are amazing, even if i have only talked to one of them. Be sure to stop by and donate.
If i have left anyone's name out, please hit me up and i will add you to the credits, and to that i apologize.
Happy flashing!
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
gpz1100 said:
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
Click to expand...
Click to collapse
Sorry for delayed response, it gets removed when you do the factory reset in stock recovery. For some reason TWRP can't remove it from /data in nougat but stock recovery can in B29.
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
QuantumFluxx said:
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
Click to expand...
Click to collapse
I did try it. It doesn't wipe it because there is a bug with TWRP for our phone. I would wipe and even format data and it wouldn't work. If you go to the official TWRP thread it even warns you that if you have encryption to not wipe. We had a dev who wiped and it got rid of the encryption key and not the encryption, like what happened to me. I tried to wipe so many times and had to revert. Long process but I got my phone to work again
Rip me
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
navsterama said:
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
Click to expand...
Click to collapse
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
twilighttony said:
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
Click to expand...
Click to collapse
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
try this.
twilighttony said:
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
Click to expand...
Click to collapse
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
twilighttony said:
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
Click to expand...
Click to collapse
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
twilighttony said:
try this.
Click to expand...
Click to collapse
This is posted in the dev section. No need for external linkage.
navsterama said:
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
Click to expand...
Click to collapse
glad that worked. perhaps i will edit the guide to where fastboot is added at the end as an extra. seems that if we at least have twrp we can go from there. do you still have an unlocked bl?
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
will remember for future reference. thanks
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
gpz1100 said:
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
Click to expand...
Click to collapse
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
twilighttony said:
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
Click to expand...
Click to collapse
Right, I understand that, but the person reading your blog won't, and thus the confusion.
This guide really needs to be stickied or higher up. Restarted my phone yesterday and it randomly got encrypted upon booting. Was locked out of everything and no keyboard was popping up to be able to put in a PIN or Password. This guide saved me. Thank you.
Help!
I've had a verizon V30 I unlocked and rooted via the frankenstein method a few years ago.
I was running out of space recently and did some cursory research about 'my verizon' app and it was pretty large, so I made a titanium backup and then deleted it. Also did this for the basic 'messages' app built in.
Noticed the phone was a little laggy and having some hang issues after that so I rebooted. It's stuck on a Verizon splash screen with a few colorful dots.. seems stuck there.
I've tried clearing the cache and booting into safe mode all with the same result. I really do not want to do a factory reset.
What are my next steps for troubleshooting this or trying to restore that program? Any help is appreciated--I've tried to search a bit but not finding a good first step towards trying to resolve this.
Thanks!
water- said:
Help!
I've had a verizon V30 I unlocked and rooted via the frankenstein method a few years ago.
I was running out of space recently and did some cursory research about 'my verizon' app and it was pretty large, so I made a titanium backup and then deleted it. Also did this for the basic 'messages' app built in.
Noticed the phone was a little laggy and having some hang issues after that so I rebooted. It's stuck on a Verizon splash screen with a few colorful dots.. seems stuck there.
I've tried clearing the cache and booting into safe mode all with the same result. I really do not want to do a factory reset.
What are my next steps for troubleshooting this or trying to restore that program? Any help is appreciated--I've tried to search a bit but not finding a good first step towards trying to resolve this.
Thanks!
Click to expand...
Click to collapse
Early on with the verizon V30 roms I found that uninstalling some of the bloatware caused boot loops. From then on I just froze them; doesnt help your space situatuon though...
If no other suggestions, you could try a dirty flash of the ROM you were running (assuming you flashed TWRP zip).
I believe you'll need MyVerizon anyway, as this is what enables VOLTE and VOWIFI on Verizon (for me, at least). So I would not recommend removing it anyway.
Granted, you're past that. I would think that dirty-flashing the ROM should restore it, potentially? That could be one way to get back to running. Another way might be to reload the APK somehow. You might need to use TWRP to do that, unless there's another way to do it from a TiBu backup? If I can help in some way (I'm on VS996) I'm happy to try.
Unless you actually deleted the apps from System, it's almost certain that a Factory Reset will solve it. But I can understand your reluctance.
I'm not sure a dirty flash will help, since the problem is your data partition. You already tried deleting cache (I presume in TWRP).
And I agree that if you could somehow reload the apk, that might do it. Does ADB install work in TWRP, despite no OS? If so, that's worth trying. First pull the apks you removed from System to your computer, then run adb install apk-filename.
But FIRST make a full TWRP data backup of what you have now!
If you have to Factory Reset, you can use TiBu to restore your user apps from that backup. I haven't tried that in years, but I assume TiBu still has this feature.
Fingers crossed for you :fingers-crossed:
And for others who see this: Careful, selective debloating IS possible, but it always starts with a full backup: TWRP if rooted, otherwise LG Backup, (which saves app data and most OS settings).
Thanks all for responses, appreciated so much. In a bit of a pinch as I needed my phone for a backpacking trip last weekend, I just moved forward as best I could on Friday. Generally I tweak my phone enough to unlock/root then let it be. I guess I got greedy/complacent try trying to de-verizonify it and clear some space as much as possible.
Two things
1) Immediate solution, and still seeking some advice:
I used LGUP to flash the Android 9 kdz as an upgrade I think to the phone. Because I had TWRP as my recovery that ran into an encryption error (I subsequently saw this caveat/warning further down in one of ChazzMatt's posts), and due to that was required to wipe/clear everything.
So now I have 'benefits' of Android 9 but no root. However my bootloader is still unlocked.. so I am still seeking advice how I can get Android 9 root. Please don't tell me I have to go back to 8 and do some stuff before going back to 9 with root. I didn't actually see in any guide how to root on 9. But it is possible I missed it/just need to apply same sequence as shown as on the guide for doing so on 8.
I'm on 30c version of PIE and keep getting bugged to install a system update which I keep putting off because I'm leery of that..but I can't freeze the process without root.
Also because I flashed the stock OS, that means I lost the custom recovery, I don't have TWRP anymore (this seems so, but looking for confirmation), right?
2) retrospect, and a question for future reference
After all this I realized like an idiot I had a TWRP backup made in 2018 after I first unlocked and rooted it. Just hanging out on my SD card, which I could have accessed via TWRP before I flashed the KDZ. If I would have restored that it would have re-installed the OS and retained my data. Is that considered a dirty flash though, like it might not have worked or had subsequent problems?
And secondly on the SD card, I found all the 'dank memes' and other downloads I was worried I'd lost, so most of the data loss tragedy :silly: was averted (main pics backup to cloud, learned that lesson after lg g4 hardware bootloop pain).
water- said:
1) Immediate solution, and still seeking some advice:
I used LGUP to flash the Android 9 kdz as an upgrade I think to the phone. Because I had TWRP as my recovery that ran into an encryption error (I subsequently saw this caveat/warning further down in one of ChazzMatt's posts), and due to that was required to wipe/clear everything.
So now I have 'benefits' of Android 9 but no root. However my bootloader is still unlocked.. so I am still seeking advice how I can get Android 9 root. Please don't tell me I have to go back to 8 and do some stuff before going back to 9 with root. I didn't actually see in any guide how to root on 9. But it is possible I missed it/just need to apply same sequence as shown as on the guide for doing so on 8.
Click to expand...
Click to collapse
With unlocked bootloader on Pie, here's how you reinstall TWRP (IF you are on firmware with fastboot flash commands). Yes, I made a standalone post for this -- but if you read it it's basically just Section 6 of WTF Instructions. However, I had to make a standalone post because too many people kept thinking they had to downgrade back to Oreo, etc.
So, you can reinstall TWRP on Pie if you have unlocked bootloader. The problem is you need to fastboot flash commands to do that. VS996 firmware does not have that, which is why VS996 owners have to TEMPORARILY convert to US998 in the first place to unlock bootloader, install TWRP and root. Yes, your bootloader is already unlocked, but on VS996 you don't have the necessary fastboot flash commands to reinstall TWRP.
Thus, you will need to go back to US998 firmware (flashing KDZ via Dev Patched LGUP) to get fastboot flash commands. You can do it the hard way (US998 Pie KDZ) or you can do it the easy way (US998 Oreo KDZ). With already unlocked bootloader, you don't need to go back early Oreo, you can go to last Oreo. I don't recommend flashing US998 Pie for this, as there's too many people who have trouble with US998 Pie (stuck on LG logo, etc). You just need to temporarily get fastboot flash commands, and get TWRP reinstalled.
That post I have linked in the first sentence is for unlocked Bootloader with fastboot flash commands, on any stock firmware (Pie, Oreo, even Nougat if you wanted that for some reason).
Once you reinstall TWRP, then you can go back to VS996 Pie firmware via TWRP flashable zip.
Thanks for your response, now and two years ago.. super appreciated
I only need to get to the point to put the phone in debug mode (with access to fastboot) to get TWRP installed after flashing the recent oreo kdz. After TWRP installed follow your instructions (thanks!) to flash TWRP pie..
I'll probably give it a go this weekend or tomorrow evening, but do you have a recommended link to US998 Oreo kdz? https://androidfilehost.com/?fid=1395089523397933445 is fine?
Whereafter I'll follow your instructions for installing it (using LGUP patched) at: https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
In the ROM section, go to ChazzMatt's US998 Pie KDZ thread. It also has instructions for rolling back to Oreo. Follow them to the t.
Make sure to use the Pie-compatible LGUP version in there when you roll back, and install it exactly as described in that thread.
His US998 Oreo thread will have a download link for Oreo 20h (the latest Oreo). Otherwise it's easy to find on lg-firmwares.com.
Good luck to you
Ok really that was pretty easy and not bad once I got everything lined up, did it in maybe 30 minutes or less. I'm in Pie with root now and TWRP recovery. Thank you for the help!
Two points:
1) after flashing TWRP, I got some issues when wiping, I was able to flash the VS996 ROM but kept seeing some red "twrp can't mount system" or something like this. It would be a hassle but do I need to go back and reformat/reflash? or do it dirty at least?
2) maybe related to the above, maybe (probably not) not.. and I realize magisk and other avenues might cover it these days but I'm trying to debloat the TWRP flashed VS996 ROM with Titanium Backup.. stuff like NFL and slacker radio, google music.. like I did on Oreo. But Titanium keeps giving me an error about 'can't find the apk' -- Ti says I have root. I have read a bit that Android 10 really packages the apps in there so it's not like you can just remove the ones you want. is this the case for 9 too?
suggestions for alternative tool if Titanium is kind of a dinosaur in that regard?
Thanks
Well done!
1) It's best to use Format Data in TWRP to avoid that mounting error. Unless you are certain you have no mounting problems, I would recommend doing that before spending more time setting up the OS.
2) Before trying to freeze apps with TiBu, see if they can be Disabled in the regular Apps menu. Most of the "optional" bloatware can. Of course make a TWRP backup before freezing anything with TWRP!
Water-, there is already a debloated Verizon 99630c rom out there somewhere, if you would like to try it. I'm on it now.
Sorry, I can't link it. It was made by micromod777. So do a search for him.
I also use tibu, but there is another app (?) out there called migrate that backs everything up. You might look for it and try it. (I did use it a month or so ago myself just to try it - - worked for me).
water- said:
Ok really that was pretty easy and not bad once I got everything lined up, did it in maybe 30 minutes or less. I'm in Pie with root now and TWRP recovery. Thank you for the help!
Two points:
1) after flashing TWRP, I got some issues when wiping, I was able to flash the VS996 ROM but kept seeing some red "twrp can't mount system" or something like this. It would be a hassle but do I need to go back and reformat/reflash? or do it dirty at least?
Click to expand...
Click to collapse
You're welcome!
See points "f" and "g" of the screenshot. When you were installing TWRP I think you missed the "format data" part... And/or possibly the "reboot recovery" step immediately after.
If you were reading in an app (XDA or Tapatalk) instead of web browser, it's possible that section was truncated and you didn't see it.
ChazzMatt said:
You're welcome!
See points "f" and "g" of the screenshot. When you were installing TWRP I think you missed the "format data" part... And/or possibly the "reboot recovery" step immediately after.
If you were reading in an app (XDA or Tapatalk) instead of web browser, it's possible that section was truncated and you didn't see it.
Click to expand...
Click to collapse
hmmm
it's possible.. ..i definitely gave formatting a shot (hence the red errors.) and believe I rebooted to recovery.
Where I'm at now, OS booting/operating flawless (bloat aside) and root verified, can boot back into TWRP no problem...
recommended course of action?
water- said:
hmmm
it's possible.. ..i definitely gave formatting a shot (hence the red errors.) and believe I rebooted to recovery.
Where I'm at now, OS booting/operating flawless (bloat aside) and root verified, can boot back into TWRP no problem...
recommended course of action?
Click to expand...
Click to collapse
Sorry, I'm in another hemisphere for several weeks on leave of absence for family matters. Didn't see this until now. Hope you got it worked out.
ChazzMatt said:
Sorry, I'm in another hemisphere for several weeks on leave of absence for family matters. Didn't see this until now. Hope you got it worked out.
Click to expand...
Click to collapse
Not a problem at all! Maybe you mistook this post for another, as you'd fairly promptly replied to me through here over the last two weeks! much to my appreciation.
Basically I'm saying when I was doing some of the wipe functions in TWRP before flashing the new OS, and while flashing it, I saw some red mount system error messages.
However my phone is fully functional, I can reboot into TWRP recovery, I'm not noticing any functional issues with it right now.
Can I ignore because functional phone and recovery access = functioning fully! or is there some check I should do or whatnot. I mean I could clear data and start over again but It's been a week+ of customizing and getting it how I like it, kind of a hassle if it's not needed/necessary.
Thanks
water- said:
Not a problem at all! Maybe you mistook this post for another, as you'd fairly promptly replied to me through here over the last two weeks! much to my appreciation.
Basically I'm saying when I was doing some of the wipe functions in TWRP before flashing the new OS, and while flashing it, I saw some red mount system error messages.
However my phone is fully functional, I can reboot into TWRP recovery, I'm not noticing any functional issues with it right now.
Can I ignore because functional phone and recovery access = functioning fully! or is there some check I should do or whatnot. I mean I could clear data and start over again but It's been a week+ of customizing and getting it how I like it, kind of a hassle if it's not needed/necessary.
Thanks
Click to expand...
Click to collapse
Do you have encryption on? TWRP will show a mount error upon start, and prior to the passcode being entered.