Related
Like I'm sure this topic hasn't come up before, but I've searched for hours and I'm probably just making things worse. I also just accidentally deleted this post halfway through. It's too late and I'm too tired and I have no working phone.
Bought an SGH-I747 on E-Bay. Got a Straight Talk SIM card kit, activated it, so far so good.
Rooted it with CF-Auto-Root. Worked pretty well, took a lot of reboots, upgraded the SU from the Play Store and it got rid of Knox. So far so good. Got everything all set up the way I like it. Happy.
It was running 4.4.2. I'm assuming it was the release prior to the November 12th OTA release, but I can't say for sure.
Phone downloaded and installed an upgrade automatically. Now, it won't boot. I get the SAMSUNG logo, then the Samsung Galaxy S III logo then nothing.
I retried the CF-Auto-Root, no change.
I booted into recovery (volume up, home and power on), did factory reset, no change.
Started looking around for a way to return it to stock. Found an upgrade43.zip file somewhere (I'm sorry I can't find where I got that now). Put it on the sdcard card and tried installing it with the recovery and it fails part way through.
At this point, I think I probably need to completely overwrite everything with something stock. I just don't know how to do that. I see posts on such subjects but they all have warnings that make me think I'm going to totally brick the phone, so I'm hoping someone can point me the right way. I'm not all that Android savvy, as you can tell.
Help.
Since your phone was running 4.4.2, do not attempt to flash any ROMs using that attempt to downgrade your bootloader to anything prior to 4.4.2.
Try this to get your phone up and running:
download the latest CM11 for the d2lte and save it to an external SD card: https://download.cyanogenmod.org/?device=d2lte
dowload the latest tar.md5 version of Philz Touch for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
boot phone in download mode, open Odin 3.07, do not check anything except f.reset.time, flash Philz via PDA box, remove USB cable when you see the word Reset appear in the status window, remove battery, replace battery, boot into recovery, format system, Dalvik, data, and cache, flash cm11, and reboot.
Thank you for your reply. There are a few things in there I don't quite understand, but I think I can figure it out.
I was going to attempt this...
http://forum.xda-developers.com/showthread.php?t=2658486
In fact, I did attempt it with TWRP last night after I posted here and new I still wasn't going to sleep. I kept getting an error about a bad ZIP file.
Is that stock restore a bad idea?
Do not attempt to flash an older bootloader. The mjb bootloader is from 4.3 and attempting to flash it could hard brick your phone.
I suggest doing what I suggested so you can confirm the bootloader and modem installed on your phone.
OK. Thanks. Probably a good thing I couldn't get it to work then.
Thank you so much. I have a working phone again. Now I just have to get it all set back up the way I like it.
I have to say, and it's probably words straight from the devils mouth, that I kind of wish I could have restored the Samsung stock software. It's just what I'm used to. But I will take what I can get.
A few questions. I like having root. But root is what got me in trouble in the first place. Is this going to be rooted now, or will I have to do that or am I better off just leaving it alone.
Second, I'm probably going to have questions since this is so different than what I'm used to (like I already can't find the Play store). Where is the best place to ask?
If you want root, one of the easiest ways to get it is to flash supersu from your custom recovery. Most ROMs are pre-rooted.
Many custom ROMs do not include Gapps. Just download and install the Gapps version for your ROM.
If you like the TW look, flash a TW-based ROM. Check out the development threads for different ROMs.
here is a thread for Q's that has some pretty good/friendly helpers on it if you need.
http://forum.xda-developers.com/showthread.php?t=2257421
"all i can really do , is stay out of my own way and let the will of heaven be done"
How to save in to external SD card
How do you save the file into the external SD card? I am having the same brick issue with my GS3.
To save a file to an external SD card, just put the card into a card reader and save the ROM to the SD card.
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
I've had this tab for awhile now and the lack of updates wasn't an issue for me while my Nexus 7 was still my workhorse. USB port and charging issues has forced me to use the Pro almost exclusively now and it's frustrating. I'm thinking CyanogenMod 13 because it's available and the latest version of android. But I have a couple questions. Please help. I've searched and will continue but a little help would be appreciated.
Internal storage is at the top of my list right now and I believe Cm allows the ability to use SD card as internal storage. It's available in CM12 but apparently not CM13 as it sits as a nightly. Is this still true? I'm going to flash this tab today. Would rather go with 13 but I'll flash a stable 12 because I need this ability.
This isn't really that important but would help with dealing with all my remote controls. Does Cm now have the ability to take advantage of the RF sensor for remote control? In the past it was always blamed on closed source drivers. Still an issue or no?
Thanks for your input. After being away from the scene for awhile I've answered most of my questions. These are the last two.
I have the CM13 version from about a week ago, and it has the option for using the SD card as internal storage. As for the IR blaster, there are a couple of apps on the play-store that worked with CM12, so I assume they will also work with CM13.
Sicron said:
I have the CM13 version from about a week ago, and it has the option for using the SD card as internal storage. As for the IR blaster, there are a couple of apps on the play-store that worked with CM12, so I assume they will also work with CM13.
Click to expand...
Click to collapse
Thank you! Guess I'll grab a 13 nightly and get to work :good:
Hey guys. The install went smooth but I'm getting parsing error when trying to install apps from unknown sources. In particular right now I'm trying to get PS Remote Play setup but the only remote app I can get to install needs updating. Every single other download I've tried has failed due to parsing error.
Edit: Now I'm stuck. Cm13 is running fine. Rooting was smooth, flashing Twrp 3.0.0-2 was smooth. But then I started installing my apps from unknown sources. Parsing errors even though it's set to allows unknown sources. Hours of searches, tons of articles dealing with parsing errors and everyone recommends check the unknown sources box. Nice!
During this process I've booted into recovery and even though it worked fine before now it freezes in different areas. The menu will sometimes freeze right away or wait till I try and reboot into recovery, OS, download it doesn't matter. Reinstall Twrp and no change. I originally used Flashify but also tried Twrp manager which was worthless. Shocker.
At this point I want to just start over but I have zero confidence in Twrp. Or is maybe because of flashify? I'm lost. Is clockworkmod available? Most likely regardless of my thinking I'm missing something here. I just need a fresh start. How should I start. I need a recovery first.
IFLATLINEI said:
flashing Twrp 3.0.0-2 was smooth.
During this process I've booted into recovery and even though it worked fine before now it freezes in different areas. The menu will sometimes freeze right away or wait till I try and reboot into recovery, OS, download it doesn't matter. Reinstall Twrp and no change. I originally used Flashify but also tried Twrp manager which was worthless. Shocker.
At this point I want to just start over but I have zero confidence in Twrp. Or is maybe because of flashify? I'm lost. Is clockworkmod available?
Click to expand...
Click to collapse
Are you flashing TWRP 3.0.0.2 every time? I wasn't even aware they had a 3.0.0.2 build. And once in a while, they release a build with some problems. If you haven't already, try 3.0.0.0. I'm still back on 2.8.5.0 and no issues like you describe.
redpoint73 said:
Are you flashing TWRP 3.0.0.2 every time? I wasn't even aware they had a 3.0.0.2 build. And once in a while, they release a build with some problems. If you haven't already, try 3.0.0.0. I'm still back on 2.8.5.0 and no issues like you describe.
Click to expand...
Click to collapse
Yeah but its 3.0.0-2. https://dl.twrp.me/mondrianwifiue/
Somehow I got it all worked out. Starting over from scratch. The problem now is how to update to more recent nightlies. TWRP doesn't see any files anymore.
IFLATLINEI said:
Yeah but its 3.0.0-2. https://dl.twrp.me/mondrianwifiue/
.
Click to expand...
Click to collapse
I don't know why they just switched from the last digit in the version number being -1, -2, etc, instead of .1, .2 (dash instead of dot) which they used for years.
But that misses the point. If you are having trouble on a brand new TWRP version, try a previous, known good one.
redpoint73 said:
I don't know why they just switched from the last digit in the version number being -1, -2, etc, instead of .1, .2 (dash instead of dot) which they used for years.
But that misses the point. If you are having trouble on a brand new TWRP version, try a previous, known good one.
Click to expand...
Click to collapse
Yeah I got ya. I may try another one. Problem is I couldn't begin to guess which one is a "known good one". I know I've used a few starting with a 2.8 something up to the one I'm using now. None of these were even able to get me this far. But thanks
IFLATLINEI said:
The problem now is how to update to more recent nightlies. TWRP doesn't see any files anymore.
Click to expand...
Click to collapse
You have the right location selected, correct (internal storage vs. SD card)? A number of times, I've switched the location in TWRP, then forgot to change it back and scratched my head wondering where the files went.
redpoint73 said:
You have the right location selected, correct (internal storage vs. SD card)? A number of times, I've switched the location in TWRP, then forgot to change it back and scratched my head wondering where the files went.
Click to expand...
Click to collapse
Yeah I ran into that as well. I can assure you now its set correctly but I did experiment with placing the zip file in folders on both.
I got fed up last night and just started over. I flashed back to stock, Rooted, and flashed TWRP 3.0.0.0 this time and it worked! Installed CMs latest nightly and im up and running. Havent tested yet to see if zip files now show up in TWRP. Ill be looking after lunch
IFLATLINEI said:
I got fed up last night and just started over. I flashed back to stock, Rooted, and flashed TWRP 3.0.0.0 this time and it worked! Installed CMs latest nightly and im up and running. Havent tested yet to see if zip files now show up in TWRP. Ill be looking after lunch
Click to expand...
Click to collapse
If you don't know if zip files show up in TWRP, how did you flash CM? Did you sideload?
To be clear, when you were having trouble seeing zip files in TWRP before, it was using the "Install" function in TWRP? Or were you trying to "Restore"?
redpoint73 said:
If you don't know if zip files show up in TWRP, how did you flash CM? Did you sideload?
To be clear, when you were having trouble seeing zip files in TWRP before, it was using the "Install" function in TWRP? Or were you trying to "Restore"?
Click to expand...
Click to collapse
Because adopted storage wasn't setup till after CM13 was installed. Adopted Storage is the key in this whole mess. Unfortunately for me its also the one key component I need to make this tab last me another year. What I was trying to do was flash the latest nightly with TWRP. That's when I realized TWRP couldn't see any of the files in any folder.
But get this. I forgot to repost after lunch. Seeing as though this time I successfully used 3.0.0.0 to flash CM I thought my chances of it seeing a zip file were pretty good. And it did! But then it freezes. Multiple reboots and all attempts to select a file or folder resulted in TWRP freezing. But at least 3.0.0.0 seen the files as you would expect. Maybe I should give 3.0.0.0-1 a shot again.
Depends do you have the T320, or the T325? AFAK the newer version of TWRP is ONLY for the T320. Having installed it to my T325 I lost my Recovery. thankfully I was able enough to recover it by flashing 2.7.8.x though Odin again in Download Mode. Not sure what was so special about the T320 that it needed a point realese fix for, that the T325 never got.
Ichijoe said:
Depends do you have the T320, or the T325? AFAK the newer version of TWRP is ONLY for the T320. Having installed it to my T325 I lost my Recovery. thankfully I was able enough to recover it by flashing 2.7.8.x though Odin again in Download Mode. Not sure what was so special about the T320 that it needed a point realese fix for, that the T325 never got.
Click to expand...
Click to collapse
I have the T320
At the risk of adding confusion to this Thread, it seems that the T325 version of TWRP was also recently updated to v3.0.1.0 recently.
Since that's the version I'm running,
FYI:
mondrianWIFI = T320
mondrianLTE = T325
The trick here is to google mondrian<INSERT DEVICE> TWRP, which should take you to the direct download page.
To flash from rooted stock you'll need a *.img.tar File, with which to flash from Odin. In my case that would apply to v2.8.7.0 (IIRC).
Once that's been installed you can just use *.zip Files from within TWRP to update it.
Ichijoe said:
At the risk of adding confusion to this Thread, it seems that the T325 version of TWRP was also recently updated to v3.0.1.0 recently.
Since that's the version I'm running,
FYI:
mondrianWIFI = T320
mondrianLTE = T325
The trick here is to google mondrian<INSERT DEVICE> TWRP, which should take you to the direct download page.
To flash from rooted stock you'll need a *.img.tar File, with which to flash from Odin. In my case that would apply to v2.8.7.0 (IIRC).
Once that's been installed you can just use *.zip Files from within TWRP to update it.
Click to expand...
Click to collapse
Just to be clear. There was no problem flashing CM13 from stock with TWRP. Its not till the flash is all done and I selected to adopt SD card as internal storage. Then regardless of TWRP version it either won't see any files or and I've only been able to get 3.0.0.0 to see files but it freezes.
Here's the question. Are you using adopted storage?
IFLATLINEI said:
Just to be clear. There was no problem flashing CM13 from stock with TWRP. Its not till the flash is all done and I selected to adopt SD card as internal storage. Then regardless of TWRP version it either won't see any files or and I've only been able to get 3.0.0.0 to see files but it freezes.
Here's the question. Are you using adopted storage?
Click to expand...
Click to collapse
no not yet, I'm still kinda stuck on a 32GB card that I've had since my S1 days. I'm kinda hoping to pick up a 64GB MicroSD for that purpose soonish though.
But, just outta interest, you wouldn't have happened to have Device encryption enabled, would you? As for myself I managed to figure out that if you encrypt the Device early enough (i.e. before you root it), the GSM \ Data Connections still work. Where as if you do it post root, it would kill those functions. (Not that a T320 User should care though).
But, the other side effect of encryption (of the /data Partition), is the loss of said /data Partition under TWRP. Which can no longer 'see', what it thinks should be a valid /data Partition. So reports back to you a 0kb free (e.g. not found).
Now like I have stated I have not used any features which would marry my MicroSD to the Device, yet... But if I had then as I understand how Google implemented Adapted Storage to work. then it would be reasonable to assume that it would become part of the /data Partition.
So to get to the punch line... is your Device encrypted? If so that's your problem right there.
No I haven't encrypted it. Its on my list of things though. I just didn't want to overcomplicate things at this point. I felt as though I was already pushing pretty hard with the CM13 nightlies and adopted storage. I'll tell you this much though. I said it before and I'll say it again. This thing has never ran so well. Also for the first time since I've had it storage is not an issue.
I'd seriously recommend the Samsung Evo+ micro SD card. I haven't noticed any issues with lag when loading or using any app. Since I've installed this setup a few times now though I noticed that when you do select to adopt storage and it tests your card, pay zero attention to what it says. Same card and twice it said the card was too slow and twice it said nothing. There's a flaw there I think. It alternated. First time the card was too slow but the second time there wasn't a problem and so on. Then again maybe not. Could be the SD card that's causing that. Ahhhhhh who knows. Lol
Hi Folks:
I had been running CM12 and deciding to upgrade to CM13 last night as the several issues seemed to have been addressed most recently in the most recent string of Nightly's.
I followed the instructions from RootJunky dude and all went just fine.
HOWEVER
I lost my root in the process. Not pleased about that.
Any way to get it back now that I'm on CM13, or do I have to roll it all back via a recovery?
Thanks for your assistance
whitehawk66 said:
Hi Folks:
I had been running CM12 and deciding to upgrade to CM13 last night as the several issues seemed to have been addressed most recently in the most recent string of Nightly's.
I followed the instructions from RootJunky dude and all went just fine.
HOWEVER
I lost my root in the process. Not pleased about that.
Any way to get it back now that I'm on CM13, or do I have to roll it all back via a recovery?
Thanks for your assistance
Click to expand...
Click to collapse
Settings - > About Tablet -> click the build number a few times to enable "Developer options" then Click the back arrow or back button -> Developer options -> Root acess - Click Apps and ADB
now apps that need root will prompt you
No OS installed. I have twrp installed. So literally when i turn it on it goes directly into recovery menu. Apparently I have no back up or restore point. This is a Sprint galaxy note 4. Does anyone have any suggestions. I have been looking for a factory reset firmware somewhere online cant find one. Funny thing is my wife has the same exact phone. I thought making a back up and restore point for her phone would work on mine, but it didnt lol. Please I would be very grateful for help.
Hello, you could get the official software and use odin to get it back all the way to stock, or you can also just flash a custom rom since you already have twrp. To install a custom rom, all you need to do is download the rom and place it on a micro sd card, boot into twrp, and flash the rom from the micro sd.
Thank you for your reply how ever my trouble is finding an OS that works for my note 4 sprint device. I have downloaded dozens and dozens of different roms and so called " factory firmware" but seem to have no lucks. i have the recovery software installed twrp. when i go into there and try to load rom i still get error that says no os installed..
Thanks for the input i will close this thread now. my problem was not being patient at the bootload screen. I automatically assumed that something was wrong because it was stuck at the sprint spark yellow screen how ever little did i know a little bit of patients would have saved me numerous amounts of hours of research. Lost sleep, called off of work, and canceled weekend plans due to a little lack of patience. Well you live and you learn i really appreciate you taking time out to reply.
I was needing a new phone and saw a Linus Tech Tips video where he took an LG G3 and put LineageOS on it. So I thought I'd try it out for myself following his guidelines at https://linustechtips.com/main/topic/1058206-lg-g3-lineageos-tutorial/
I bought an LG G3 D851 (T-Mobile version) off EBay for this. It's my first Android phone (yes, experimenting on my first Android Phone), I've always used Windows phones. This is what I've done to the LG G3 so far:
I reverted back to KitKat. Everything seemed to have gone just fine.
Then I downloaded the the Full Purple Drake Root and ran that after I figured out that .gz files are a compressed file and that can be decompressed. Everything seemed to have worked fine.
Then I downloaded the TWRP app on the phone and tried to backup the recovery via the TWRP app, which I'm not sure if it worked correctly. But anyhow.
Now that I'm writing this I see I missed this step:
number seven: Select the TWRP file we copied over earlier in the app, flash it to recovery, and then reboot to recovery
Click to expand...
Click to collapse
I guess I just didn't understand what was meant by flashing it over and has just copied it to the phone's memory which I later wiped.
Well then I went into TWRP recovery and tried to do a recovery backup, which it seemed to do just fine. I rebooted and tried copying it over to the computer, which seems to not have worked. I just have an empty folder on my computer as we speak.
Then back in the TWRP recovery, I selected Wipe>Advanced Wipe, and select Dalvik, Cache, Data, Internal Storage, and System – then swipe to wipe.
Then I downloaded the latest version and nightly of LineageOS zip file and the Opengapps zip file but then had a hard time figuring how to get them to the phone.
I figured out that I could stick them on an SD card and slip it into the LG G3 that I'm working on and could see the files from the TWRP recovery menu.
So I tried to install the LIneageOS zip file several times and it didn't work. I'm guessing it's because I forgot to flash a certain file to TWRP recovery and am not sure how to do that, especially now with the phone only booting into recovery mode with the TWRP menu since it's wiped clean and will just display the LG logo and turn the LED different colors if I try to normal boot the phone.
Well I still want to try to fix the phone and go for LineageOS. I spent nearly all night working on it so I may give it a rest for a few days. But any help or pointers would be greatly appreciated.
Now that I think about it, I didn't do what I mentioned ok #4 above about flashing the TWRP recovery because TWRP recovery was installed with the full Purple Drake root. However, the Linus Tech Tips instructions point to them rooting the phone with the lite version of Purple Drake (root only) and then flashing the newest version of TWRP recovery. So I wonder if my problem has to do with my having the latest version of TWRP recovery on my phone.
Ok. So I think I'm making progress, although that's just a feeling I have since I'm not suite what I'm really doing.
Anyhow the error code was something like "Unknown Error, Error Executing Updater Binary in Zip, Zip is for LG G3 D851, this phone is...(blank)". So I found an article in DroidThunder.com talking about this very problem. It suggested unzipping the rom on my computer and looking for the updater-script file and erasing some lines that apparently only have to do with verification. Then re-zip and retry.
Now I'm getting a "No MD5 file" message followed by an "Error flashing zip" message.
Edit: After reading this I take it I have an older version of TWRP, that is, v2.7.1.0, whereas the newet versio (for this phone?) is apparently 3.3.1-0. That seems to have an effect on this. I wonder if it's possibly to flash a newer version of TWRP onto this bricked phone. Anyhow, I'll have to look into that later. It's time to call it a day.
So recently I've been focusing on these two threads:
[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851! by Omar-Avelar
And:
[GUIDE][FIX][DISCUSSION] LG G3 Hard Brick Recovery by l33tlinuxh4x0r
But I can't get either of them to work. I guess the only other thing would be to try to find a ROM, preferably the original KitKat that came with the phone, and hope and pray that I can get TWRP recovery v2.7 to install it.
I have the original as a tot file. But as far as I understand, I need a zip file that's set up for TWRP recovery.
Anyhow, trying to get this phone running hasn't been easy and has made other problems. Now every time I turn on my Surface 3 I have to go through BitLocker authentication. Hopefully turning bcd Test Signing off will stop that. But I'm getting to the point that I'm feeling like giving up.
Well that's it. Last night I found a zip file for the original Marshmallow ROM for my G3. I got it onto the SD card, went into TWRP recovery, saw it install, restarted and...
Now it's hard bricked. I cannot even get into TWRP recovery. The screen won't show a thing. I tried several times to get it into any mode possible, normal boot, TWRP recovery boot, download mode, and that jumping the pins trick, and I can't get it to where I can do something with the phone.
So I'm giving up on all this rooting, custom recoveries and custom ROM stuff. It all seems like a good idea, and I'd love to be a part of it all. But I take it this isn't for me. So I give up.
Thanks to all who have worked on this and have made the helpful forums about these phones! Maybe if I were more competent I would have figured it out.
Well, I said I was giving up. But maybe not. I did give up trying to recover the phone from being bricked and sent it out to a JTAG shop. For about $40 the phone is supposedly fixed and on it's way back.
But when it's back, do I just leave it alone this time, or should I try to get Lineage OS back on it again? Well, this is something that I haven't made my mind up yet. I see where I had made several mistakes when I first tried to get LineageOS on it. Maybe I know enough now that it won't happen again. But at the same time there's no guarantee that I won't me it up again, and have to pay some $40 again to have it unbricked.
SUCCESS!!!
So I got my phone back with stock Marshmallow working. Then I carefully went through every step on the Linus Tech Tips site, including installing the latest version of TWRP, and the next thing I know I'm running LineageOS 16 on my phone!
This is great! It's my first Android Phone and I've got it setup just about perfect! The only thing I kind of miss is Wi-Fi calling. But that didn't work so well on the Alcatel Window's phones I had anyway. But I got all the apps and most of the music I need installed and am ready to go! I also have two batteries, and the original isn't too bad, so I might carry that around as a backup until I'm sure how much battery I'll be using.
I'll be coming back and thanking all the ones who's posts and work have helped me individually. But if you read this and are one of those who have worked on TWRP, LineageOS and anything else that has helped me, Thank You!