Develop Bugs

[Q] No ROMs taking, keep getting no MD5 message, phone close to bricked.

I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.

gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient

MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?

I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.

theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.

spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?

gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.

theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?

gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).

theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.

No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.

gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.

flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?

[Q] (Help: Can't boot) Lollipop + eager urge for Xposed

I'm going to be away soon and won't have easy access to a non-professional PC (meaning any computer I may have access to - I won't have admin rights with). I didn't want to wait for a root+TWRP dev package for Lollipop to be released. I wanted to just get it done, (I was having bad problems with KitKat on some select apps because of LG's 4.4 coding, long story, but I won't even go there...)
I saw that I can go to the LG support site via a link from Android Central and manually upgrade to Lollipop way before the OTA rollout even begins. I had heard rumors of people having problems, read posts, and learned how to avoid it all. I reset everything before upgrading. I did many factory resets after getting Lollipop, (I know, a lot). I got rooted and set mostly everything up.
I wanted to get Xposed loaded, BADLY. I looked it up for Lollipop and realized that I'd have to flash a custom recovery. I expected as much. When I looked that up, I realized that I would have to either use a downgrade-upgrade method (which I didn't feel like going through) or a mandatory requirement of factory reset though a process. I had already set up all of the system stuff and restored from Titanium backup most of my apps. There was no way I would factory reset because I hate resetting-up the system stuff. - - - - - BIG MISTAKE 1
So I found a thread for the D850 (AT&T) version (no I didn't flash a bad radio or anything, I thought I knew what I was doing because I was only flashing recovery stuff for Lollipop, not an AT&T rom or radio.) This was to install TWRP without downgrading or resetting. The instructions said to copy files from an aboot.img and other boot images and such (to replace the recovery) on to the internal memory and use a terminal to type in code. I did it and rebooted it.
I made a horrible mistake.
When I held the power button on the phone, nothing happened. I found out that when plugging it in to the PC, it seems to be in download mode. It was fully charged. When using the restore/brick recovery software, I have tried different cables, different computers, checking to see if anything is corrupt, different USB ports, etc. with the files... Nothing will work. I keep getting an error with a red box about the model or something. "Model Information Check Fail"
So basically I have broken boot images on my device. I need to fix these.
Where do I go from here? All because I wanted Xposed on Lollipop without resetting.
Click to expand...
Click to collapse
I have this situation. I messed up with laf.img and aboot.img too (from D850, thinking it was harmless since trying to install custom recovery only) and device won't turn on but PC recognizes as download mode but can't flash. Please read above. I'm bricked and all restore methods have failed so far.
Source from u/nicksteron on reddit.

I'm having this issue now too. It seems the thing I downloaded and tried broke my boot images.
Have you been able to fix this?
I'm trying the LG Flash Tool but it stops me at the model check fail as well. Gonna try a kdz method next.
EDIT: I tried the KDZ method with LG Flash Tool 2014 using both a KitKat and Lollipop based ROMs and I get an error. The S/W Upgrade progress gets to 4% and then the error shows up. I need my phone. Help?!

[Solved] Issues activating SGS3 SPH-L710 on Sprint with Custom ROM + lots of problems

Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.

This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.

I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.

Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!

afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good

twrp error after update

Hey guys, i've been loving bringing new life to my s2, but i went to put the latest PA on today and it said "make sure you have the latest TWRP". So i hit up the twrp site and it listed a new 2.8.7.0 version. I did note that most threads showed the 2.8.6 rev but i figured since it was on the official site it would be safe. I booted into my current TWRP, i think it was ancient, like 2.7.x, and i loaded the img, no problem and it flashed fine. I rebooted into recovery and say the 2.7.8 at the top and thought "ok great". but when i went to install my new rom, i don't have the SD card accessible. It only shows me the main system, which is also odd because if i go to factory reset or wipe cache or anything, it tells me "no os installed". If i go to reboot it also tells me "no os installed", and i relaunched in a bunch of times and i can't get it to read my SD card to flash down or anything.
Any help / ideas would be greatly appreciated.
*i should note, it still boots into my old system, so it's still there, but sadly I can't get pas the sim card screen so i can't use the os to circumvent the above error..

no ideas eh? man i hope i'm not screwed. luckily it's a secondary device but still..
*edit. after going through a ton of things i figured out i might still be able to odin over a new recovery. So i'm messing with CWM mod now and going to see if i have better luck there. I can't belie i didn't think to just odin out after the last go, but admittedly i was pretty frustrated at the time.

update
ended up using the CM13 guide and flashing between the TWRP versions listed in the guide and getting the re-partition on the phone for larger systems. After that i was able to get all kinds of stuff going that was giving me hell before. currently (and happily) running cm13 after a brief flash to PA. Can't believe how well the community has a marshmellow based rom on this ol geezer.

I ran into the same problem too when I did my first recovery installation so basically we can't use the TWRP from the official site. The one we can use is from our forum. I used the one from Paranoid 5.1.1 or CM13. Thanks to the community, S2 is still alive.

G3 won't boot @all anymore [Resolved]

So I've bricked my phone. And I can't make it work. Yesterday I finally had some time to thinker with the phone and decided to install Fulmics Rom 6.0. I had already downloaded it a while ago but first now had the time to install it. I made a post in the Fulmic's thread but with their new 6.5 fulmics just out, so my post got berried so quickly so I got no replies.
I started in TWRP with doing a backup, then a wipe and then started the install.
It seemed install was going fine, I even got the Fulmic's GUI midways and selected appropriate model, D855. I tried to keep things as vanilla as possible and chose to not uninstall anything and keep stock temperature throttle back.
But when the install completed I got one error: set_metadata_recursive: some changes failed
Phone wouldn't boot. I had however made a backup before I started and I was able to restore from backup from within TWRP.
Then phone booted and it seemed all was fine. But as I had my mind set on the Fulmics ROM I had one more go, just ti be sure I didn't mess up and chose something bad in the Fulmic install GUI. Also I did a wipe first, then I wiped the cache/dalvik as I once read that could make install easier. And result same as before. set_metadata_recursive: some changes failed.
Tried to reboot but I get flash screen with LG loge and powered by android on the bottom, and then when screen changes to only LG logo it gets stuck'd. No matter how long I wait, and I tried to wait for hours remembering wiping dalvik/cache makes boot take longer time. Stucked on the boot load. Notification light changes from green to blue. And the Lg logo is there.
Worst part is that now I can't even restore it to my backup from yesterday.
Here is my phone:
Lg G3 D855 16 GB 2 GB RAM
Android 6.0 stock LG update.
TWRP 3
Rooted
For now I would settle for a working phone. That is my main priority. Truth be told I got scared now and I don't know if I will take my chances putting a custom ROM onto the phone. After all my android 6 was working nicely, phone was rooted and adaway was working nicely. I guess I got greedy and wanted more

It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.

joppy said:
It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.
Click to expand...
Click to collapse
Downgrade to twrp 2.8 and flash again hope you are good too to go....

For me , if i have problem.
Replace sdcard , format data on twrp and flash .kdz (not after 30x.0426.kdz) , usually LGup can made download mode it self.
If can booting , make temporary root and get twrp.

Ok I had TWRP v2.8.7.0 laying around. I've used it before with success, so I know it works with my Lg G3.
But still not possible to boot.
I will try to read up on the .kdz as I never even heard of that before. Maybe if I am lucky that will save the day.

Hehe what do you know. TWRP v2.8.7.0 worked!
I dismissed it too fast, turned out it didn't get stuck'd on boot, boot just took a while because I had wiped everything.
Now I can see android is upgrading apps, and also when I think back to the first reboot with twrp v2.8 it was fulmics logo on the bottom part of the screen not android I guess my mind did not pay any attention as I was truly expecting to be stuck in boot loop this time too
Fingers crossed it is working now, I guess I didn't pay much attention when I tested twrp v2.8 and pointed to the fulmics ROM 6.0 and it seems it will work whoha

Finally I've got a working phone, and I also got Fulmics 6.0 as I sat out to get.
Don't know what went wrong or what caused the boot loop, but twrp v2.8 seemed to be the working solution.

IT seems everything works except I lost root. Which is fine for now, I will root another day.
Now I just need to use the dang phone

Deleted for your own safety

Btw, as the phone must be rooted to install custom ROM's it does seems strange that phone after installing Fulmics 6.0 appears to NOT have root, according to RootChecker. Could it be that the custom ROM is confusing RootChecker or did root somehow get revoked?
Is there a manual way I can check to see if phone is rooted? Cos there is, terminal
I took the chance tp get the latest KingRoot v4.9.6 over my previous v4.5.6. And run the APK.
Seems there must have been some issues with SuperSU, I had v2.54 and BETA v2.65. None of them kept root after install.
Found the latest stable that was superSU v2.78 and that fixed my issues.

TWRP ver 3.x messed my phone up too. Thought I had a good EFS backup, but when I needed to restore it, it didn't work. I will not be using ver 3.x again for a long time. Ended up losing my IMEI because of it.