So I admit I may not be completely up to date on the latest "little things" with this 35B ota...
I sort of just took it, updated, stayed on my roms and went with it.
Well, I think that's gotten me two hard bricked G3s. My first one I thought was done so I went and bought another G3 for cheap because I like this phone... got to setting it up and it wasn't long and that one was hard-bricked too.
What is it that we're doing to cause these phones to hard brick? I'm confused, honestly. I'm not sure what it is that I am doing to cause it to hard brick. I found one thing I know I did that's possible - wiping all the partitions before flashing the 35b bootstack... so I know now not to do that again.
What do you guys think?
I would strongly suggest trying the hard brick recovery tutorial posted. I thought I truly bricked my phone but I was able to get it back. My screen wouldn't even turn on... Only reason I knew it was trying to power on was the vibration at start up. Now it's perfect. It does require you to take apart the phone though, but it really is pretty easy.
One common cause of what's actually a soft brick is flashing the 35B bootstack before flashing either JasmineROM or SkyDragon because both of those have some older partitions which will conflict with the bootstack's 35B partitions. Flashing the 35B bootstack after its fine.
Even when it appears it's turning on but the screen stays black doesn't mean it's not on. Many people on here who soft bricked their G3 this way we still able to put it in Download mode and use LG Flash Tool 2014 to flash a KDZ, even though the screen stayed black. Flashing the KDZ restores it all back to normal.
CaptainElwood said:
I would strongly suggest trying the hard brick recovery tutorial posted. I thought I truly bricked my phone but I was able to get it back. My screen wouldn't even turn on... Only reason I knew it was trying to power on was the vibration at start up. Now it's perfect. It does require you to take apart the phone though, but it really is pretty easy.
Click to expand...
Click to collapse
I have now done this tutorial four or five times now. I'm trying to investigate certain causes of these hard bricks. So I am now an expert at hard brick recovery for this device! Haha.
roirraW "edor" ehT said:
One common cause of what's actually a soft brick is flashing the 35B bootstack before flashing either JasmineROM or SkyDragon because both of those have some older partitions which will conflict with the bootstack's 35B partitions. Flashing the 35B bootstack after its fine.
Even when it appears it's turning on but the screen stays black doesn't mean it's not on. Many people on here who soft bricked their G3 this way we still able to put it in Download mode and use LG Flash Tool 2014 to flash a KDZ, even though the screen stayed black. Flashing the KDZ restores it all back to normal.
Click to expand...
Click to collapse
I was thinking it had a lot to do with the bootstack actually. I was flashing the bootstack before flashing JasmineROM. However I was flashing it after I had wiped data, cache, and system partitions. But no system installed. I know that can't be right, obviously.
droidian1441 said:
I was thinking it had a lot to do with the bootstack actually. I was flashing the bootstack before flashing JasmineROM. However I was flashing it after I had wiped data, cache, and system partitions. But no system installed. I know that can't be right, obviously.
Click to expand...
Click to collapse
The bootstack isn't the problem, just to be clear. The problem is the conflicting older partitions in JasmineROM and SkyDragon. That's why you need to flash the 35B bootstack AFTER flashing either ROM. You can flash it before just as long as you would flash it again after, but obviously, there's no reason to flash it before if you're going to flash it after.
Wiping isn't the problem either. I always wipe Data, Cache, Dalvik and System.
What exactly are you saying can't be right? Flashing a ROM flashes System, that's where the ROM goes.
Related
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click "format data" under the "wipe" section this will wipe EVERYTHING so make sure you have the latest twrp then on your computer save a rom. Wipe the phone via twrp and then plug the phone it and wait for either Adb sideload or mtp. Personally I feel that mtp is the best just because you can move anything to your phone. Then just move the rom you want to the root of the sdcard (Every folder will be gone). Then flash it and hope that fixes it but if it dosent you may need to use the lg flash tool (windows) and flash the zv4 files. This will make you back on zv4 meaning restump root reflash twrp. The whole nine yards, just try the twrp thing first and if that dosen't work then do the flash tool. I am not responsible if you listen to me and your device breaks
bucketachicken said:
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/lg-...trying-ota-t2907508/post56061720#post56061720
Thanks, I did get it working. I have no idea how, but my data was all still there, despite wiping several times....but the recovery fix is what worked. I also got that lg flash tool setup so hopefully that will be helpful if I run into future problems. I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again!
I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again![/QUOTE]
Here is a cm12 rom that is almost perfic: http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197
It's the one I use everyday and I have seen almost no bugs
Long story not-so-short.
Due to upgrading to G5 I decideed to sell my G3.
I was running CM13 (one of the latest nightlies), 21C modem and TWRP 2.8.6, so it seemed like a good idea to go back to stock-ish firmware.
To do so, I installed stock ROM using this method with 21A modem.
Everything worked fine. I had a working LG ROM.
Then I had this great idea of mine to install even 'stocker' firmware with LG UP. (I couldn't do that while running CM13 - LG UP didn't recognize the phone)
And that was the moment when everything fell apart.
It took a few minutes for LGUP to 'install' the new firmware. Qhen phone finally rebooted, I got stuck in TWRP. There was no chance to boot a system.
I tried this fix and it didn't help.
I also tried to restore my nandroid backup (i made it on clean CM13) and it didn't work either.
Then, as an idiot I thought "How hard can it be?" and went crazy: wiping, formatting, trying to flash new modem (this tme 30B hybrid), boot, sytem and doing probably all the things I shouldn't do.
So the conclusion is: I have a nice gold brick with working TWRP, adb and LG's download mode, but nothing more than that.
No chance to boot to system and I guess with a pretty messed up system partition.
Also, I think there's some problem with flashing anything, as I don't see any lines while installing, just a few seconds and info about succeeded flashing.
Is there anyone who could help me?
Verizon LG G3 with 24b firmware. Yesterday it started lagging massively, refusing to open most apps that weren't google, random reboots where it gets stuck on the red Verizon splash page that either resolve after 10 minutes or I pull the battery. Wiped the cache and did a factory reset. The phone is in the process of restoring stuff but now NOVA launcher freezes/quits. Any idea what this is?
I'm probably just going to attempt to upgrade until 46a or whatever is the most current since factory reset did not help and erased all my data already anyway.
Flash the 10B TOT after you move stuff you want to keep from your internal storage (if you have anything). TOTs flash more partitions than KDZs and can fix problems that nothing else can.
I had a weird problem months ago and no wiping, KDZ or ROM I flashed helped. The TOT did and after talking to @xdabbeb, that's when I found out there's a reason TOTs can help when nothing else does.
Then root with the Stump app on XDA, use TWRP Manager from the Play Store to flash TWRP, wipe Cache, Dalvik /ART and Data, flash the ROM that you want and appropriate Bootstack.
35B and 47A ROMs like both of @xdabbeb 's work great, and better than 24B and 23C.
I went ahead and upgraded to 6.0 on 47a with the instructions you gave me in another threat a while back, since I have everything backed up. Now if I can get Xposed to work..
APeter001 said:
I went ahead and upgraded to 6.0 on 47a with the instructions you gave me in another threat a while back, since I have everything backed up. Now if I can get Xposed to work..
Click to expand...
Click to collapse
Great! Shouldn't be too hard with Xposed these days, they've taken care of incompatibilities with LG weather apps, etc.
Hey folks. I'm stuck at the lollipop loading screen and can't get my ROM loaded, nor can I get into recovery.
I was on SkyDragon 6.x with the 35 bootstack. I wanted to load the stock 47A by xdabbeb, and all was good. I got into 47A, loaded things and then realized that I didn't have my Nova Launcher settings saved. I went back into recovery, wiped, flashed my most recent working backup, and then rebooted. Now I'm stuck at the ROM's loading screen (the four weird rotating artworks). It won't go past that even after leaving it for 30 minutes. It's possible the cause for my error was not wiping dalvik/cache after restoring, but regardless, my problem is now that I CAN'T FIND A WAY TO GET BACK INTO RECOVERY!!!
I tried the power+volume down, release at logo, then power+volume down like 20 times, but to no avail.
I tried adb in download mode, but my device isn't found in the list (maybe because the rom is not setup properly??)
What options do I have to get into recovery? I haven't backed up my photos in a while and it would be a TERRIBLE loss to have those photos go missing.
PLEASE HELP (at 3 AM!!!)!!!
Attempting adb again. My phone shows in Device Manager under USB as "LGE Mobile for VZW USB Composite Device" as well as under Portable Devices as "LGE Android MTP Device", but it won't list as an adb device when typing "adb devices"
Argghhh.
Mother plucker. I wasn't holding the buttons down long enough!!! Rebooting to recovery is working.
I should lose all of my rep for this thread.
Glad you solved it! For what it's worth I use the Mega app to automatically upload any photos and videos I take to Mega (free 50 GB cloud) whenever I'm on WIFI. You can have it do it on mobile data too if you wish. I know this sounds like an advert. OneDrive, Google Drive and DropBox all do the same thing but don't give as much space for free so I like to keep those available for other things.
By the way, the cause of the issue is mainly that TWRP doesn't do a backup of all the necessary Bootstack partitions, and also SkyDragon 6.x (and JasmineROM 9.x) only contain a partial 24B Bootstack. By themselves they're fine, but if you either are on the 35B Bootstack before you flash those ROMs or restore a backup of them, or you don't flash the 35B Bootstack after flashing either ROM or restoring a backup, you get what you experienced.
You should get in the habit of always flashing the appropriate Bootstack after flashing any ROM or restoring any backup, even if you think you were already on the necessary Bootstack.
Thanks for responding and not making me feel like the full moron that I am. Also for providing some suggestions on backing up photos. I know I'm supposed to do it. I just don't for some reason. Too trusting, I guess.
So coming from 47A and going to SD6, I should flash 24B boostack and then restore ROM from backup? Even if 35B was installed when the SD nandroid was taken? I just assumed that since my SD ROM was running on 35B bootstack, that restoring SD while still on 35B would have been sufficient. Is that incorrect?
roirraW "edor" ehT said:
Glad you solved it! For what it's worth I use the Mega app to automatically upload any photos and videos I take to Mega (free 50 GB cloud) whenever I'm on WIFI. You can have it do it on mobile data too if you wish. I know this sounds like an advert. OneDrive, Google Drive and DropBox all do the same thing but don't give as much space for free so I like to keep those available for other things.
By the way, the cause of the issue is mainly that TWRP doesn't do a backup of all the necessary Bootstack partitions, and also SkyDragon 6.x (and JasmineROM 9.x) only contain a partial 24B Bootstack. By themselves they're fine, but if you either are on the 35B Bootstack before you flash those ROMs or restore a backup of them, or you don't flash the 35B Bootstack after flashing either ROM or restoring a backup, you get what you experienced.
You should get in the habit of always flashing the appropriate Bootstack after flashing any ROM or restoring any backup, even if you think you were already on the necessary Bootstack.
Click to expand...
Click to collapse
my.ads0 said:
Thanks for responding and not making me feel like the full moron that I am. Also for providing some suggestions on backing up photos. I know I'm supposed to do it. I just don't for some reason. Too trusting, I guess.
So coming from 47A and going to SD6, I should flash 24B boostack and then restore ROM from backup? Even if 35B was installed when the SD nandroid was taken? I just assumed that since my SD ROM was running on 35B bootstack, that restoring SD while still on 35B would have been sufficient. Is that incorrect?
Click to expand...
Click to collapse
LOL, you're welcome! Restore a backup or flash a ROM and then flash the Bootstack after the flash or restore. For SD6, you can flash either the 24B or 35B Bootstack although 35B might be preferable. I believe encryption and Advanced/HD Calling on 35B ROMs don't work with the 24B Bootstack but do with the 35B Bootstack.
Just get used to flashing the appropriate Bootstack after and you don't have to bother thinking about when you can get away without doing it.
I can still boot up the phone into cm13. It is a vs985. Have an issue with data on cm13 and tried to factory reset from the phones settings instead of twrp. It restarted into a boot loop where only the TWRP screen keeps looping. If i boot it normal it boots up fine.
I dont even remember how i rooted and installed twrp originally, it was a while ago. Im going to look into it now but before i start experimenting and trying things like flashify i wanted to make sure this wasnt a known issue with certain mistakes to avoid.
I'd flash the 10B TOT, reroot with the Stump app, put TWRP on with TWRP Manager from the Play Store and start fresh.
roirraW "edor" ehT said:
I'd flash the 10B TOT, reroot with the Stump app, put TWRP on with TWRP Manager from the Play Store and start fresh.
Click to expand...
Click to collapse
Before I saw this I got impatient and just used flashify. Got the newer TWRP 3.0 and it went through no problem. Is this a known issue that you can't factory reset from within cm or is it just a bug that i encountered?
cory733 said:
Before I saw this I got impatient and just used flashify. Got the newer TWRP 3.0 and it went through no problem. Is this a known issue that you can't factory reset from within cm or is it just a bug that i encountered?
Click to expand...
Click to collapse
Glad you solved it. I knew that was possibly the solution but since I didn't know for sure what exactly CM did when you tried it's factory reset, I didn't know for sure it would be that simple. I don't play with non-Stock anymore, so I don't know the answer to your question. If no one answers this here, I'd suggest asking in the VS985 CM13 thread. Non-stock in general is always too buggy for me.