Related
Good Morning,
I've searched through the forums and so far haven't had any luck. I apologize if this is a topic that's been covered to death, which it likely has, but I haven't found a solution to my particular problem.
Galaxy Tab Pro 10.1.
I was having problems with TouchWiz crashing, usually 2 to 3 times per day. Sometimes it would lock up the unit, requiring me to reboot. Sometimes it would just come back after 5 or so minutes. Whatever the case, I decided, since I was already interested, that I would try to root the device, clear up some memory, maybe even flash a new ROM to take care of the issue.
First, I successfully rooted the device, no problem. Surprisingly easy, actually, following steps from this website.
I loaded SuperSU, Titanium Backup, Greenify - but still had (more rare) instances of TouchWiz crashing, and even the entire unit rebooting itself occasionally. So, I decided to take a stab at Cyanogenmod 11.
After attempting to load Cyanogenmod using Heimdall and Odin, and having issues I'll add, I finally realized that (theoretically) I could just use ROM Manager to load the file. Cool! So I loaded the zip file for CM11 onto the top level of my SD Card, created a recovery, and attempted to load the new ROM. The first problem I had was that the unit wouldn't just load the ROM like I expected, but it put me into recovery mode. I suspect that's not right, but I attempted to go ahead and use the menu picks to load the ROM anyway. I wiped data/factory reset, them wiped cache partition. Then, I selected "apply update from external storage". I selected the zip file for CM11, which was right where I left it, hit select, and had the following problem.
I got the following errors, two times, in red text (with other yellow text messages surrounding);
E:footer is wrong
E:signature verification failed
So...what do I need to do here, folks? Worst case scenario, obviously, I just keep using TouchWiz, as I haven't managed to brick my device yet, and I would still be able to utilize root access apps. But I have to be close, aren't I? Does anyone have the patience to help out a guy who only knows enough to be dangerous?
You need to use custom recovery to flash custom ROMs. It sounds like you are trying to use stock recovery.
redpoint73 said:
You need to use custom recovery to flash custom ROMs. It sounds like you are trying to use stock recovery.
Click to expand...
Click to collapse
Thanks for the reply. I'm not sure what I did wrong, but I decided to give TWRP recovery a shot, and was getting an error on the CM11 zip file. I re-copied over the zip file, tried again, and that did the trick. I guess I either had a bad zip file, the wrong recovery, or both.
Thanks!
Robb
Sometimes I had problems flashing zips from external storage, appeared as corrupted, never a problem when zip was in internal storage . Did you try that?
thdervenis said:
Sometimes I had problems flashing zips from external storage, appeared as corrupted, never a problem when zip was in internal storage . Did you try that?
Click to expand...
Click to collapse
No, I did not try that, as simply recopying the zip file onto the SD card did the trick.
I spent all evening playing with the settings, trying out themes, setting up my apps - and my unit didn't crash one time. Pretty slick!
Now I just need to learn how to use Titanium Backup to store settings so I can play with different ROM's.
Hi there, I'm desperately hoping someone can help me with this issue as I have trawled through Google for solutions to no avail
I've followed the tutorials from all the lovely people on these forums to get quite far into installing a custom rom for my HTC One X (XenonHD). Unfortunately I've been greeted with the "Decryption unsuccessful" error which I have discovered to be a very persistent error - where many people have many different solutions for it (none have worked for me ) I'm greeted with a password box, and no matter what I type into the box over 4 characters long it says:
Code:
Decryption unsuccessful.
The password you entered is correct**, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
<Reset Phone>
** - It says this regardless of what I type into the password box.
There was no important data on the phone (it's an old phone) so I'm more interested in just getting this custom rom up and running, it doesn't matter to me if I have to wipe data.
Here are the approximate steps I took to reach this position:
Set up bootloader/fastboot
Installed twrp
Wiped the device (cleared every cache etc.)
Copied XenonHD zip and gapps zip on to sd card
Flashed boot.img to the device
Rebooted - XenonHD spinning logo appears, then after about 30 seconds it asks me to enter the password, and I get the Decryption Unsuccessful error.
If you need any more information from me please just ask!
I am so appreciative of how helpful this forum has been to me so far, so I have really high hopes you guys can help me
Just a quick update: I actually managed to install a different rom using the exact same method that I did for Xenon - no signs of the decryption error whatsoever. I'm a noob at this stuff so I'm not really sure of the relevance of this but it sounds like it could be helpful in pointing towards a solution?
Ollie1700 said:
Just a quick update: I actually managed to install a different rom using the exact same method that I did for Xenon - no signs of the decryption error whatsoever. I'm a noob at this stuff so I'm not really sure of the relevance of this but it sounds like it could be helpful in pointing towards a solution?
Click to expand...
Click to collapse
Wich rom you install? The answare will help
I said in my original post which rom I was installing (XenonHD) - but I've actually managed to fix it!
To anyone else who stumbles upon this thread, if you are getting the decryption unsuccessful error you have to format your phone. In my case, it was a case of updating to the latest TWRP which includes a Format option on the wipe screen. This got rid of the encryption on my phone and I was able to use the rom!
Ollie1700 said:
I said in my original post which rom I was installing (XenonHD) - but I've actually managed to fix it!
To anyone else who stumbles upon this thread, if you are getting the decryption unsuccessful error you have to format your phone. In my case, it was a case of updating to the latest TWRP which includes a Format option on the wipe screen. This got rid of the encryption on my phone and I was able to use the rom!
Click to expand...
Click to collapse
Yes offcorce you migrate from old layout to the new leyout the roms for this two layouts are different
Warning: This post is long, and probably full of grammatical errors due to my writing it late at night. a TL;DR is included at the bottom, but to fully understand my problem, I encourage you to read the whole post.
Hello, xdadevelopers community. I really need your help. So, recently I learned how to install custom ROMs myself and the experience has been really informative but also very struggling. To make a rather long story short, I bought a used G3 from my friend, had him root it, put a custom ROM on it, and everything was working fine. Only, that ROM was on Android 5.1.1, which was contemporary to when it was flashed. I wanted 6.0.1, so I went about getting it. I eventually got that up and running with Resurrection Remix, but the battery life was completely awful. Idle is okay, but using the device results in completely intolerable battery life. I asked Reddit what to do, and someone recommend crDroid for it's great battery life. I attempted to install that, and that's where I got the problems discussed in this post.
Post where I got the ROM and GApps from
Specific ROM and GApps I got:
- crdroid-6.0.1-20160118-vs985
- So I go the one for Android 6.0.1, and the most recent one at that, last updated on the 18th of January, for my G3 model the vs985
- for GApps, I selected "ARM", "6.0", and "Stock" from the menu
Could another problem be that the ROM is 6.0.1, and the GApps are 6.0? If so, open GApps version exists of 6.0.1.
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally. I navigated to the ROM folder it was located it, selected it, and swiped to flash the ROM. I got the following in response:
Installing '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Checking for BASEBAND version 35B
ERROR: It appears you are running an unsupported baseband. assert failed: h3.verify_baseband("35B:MPSS.DI.2.0.1.c1.13.4-00005") == "1"
E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Error flashing zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
So basically it failed to flash, apparently because of both an unsupported baseband version and a failure to execute a certain binary. Well, if you know how to fix the executing issue, that'd be great, although that's now what I'm focusing on here. I'm focusing on the baseband, because I believe that may be causing the failure to execute (although, as a newbie, I'm not sure if that's actually true). Apparently it was looking for version 35B, and that's not what I was running. When I set up my current ROM again just to be able to use the device, and checked for the baseband verion, it simply says "Unknown". Also, if you check out that link to the post above, it says:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
. Well, I never installed a custom kernel, but I assume my friend did, because when looking at the kernel version on my phone it says:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
.
I'm assuming if it was a non-custom kernel it would just have multiple numbers separated by periods, not have all that info, and it specifically says "CM" in there, so I assume that should work, but am not for certain.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
So that's it. I realize this post is incredibly long but feel like if it was shorter, potentially important information would be nixed. I have a TL;DR below for your convenience, but as I just said, to get all the important information, read everything above, please.
TL;DR:
Tried to install a new ROM
Failed
Failing apparently due to unsuppported baseband version
I can't determine my baseband version b/c my settings app returns "Unknown""
If baseband is unsupported, how do I know which are?
Also apparently "E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip' " is a thing. Caused by unsupported baseband version or entirely different problem all together?
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Please read the whole post to get all the detail needed.
NeatAndClean,
Thank you for providing the detailed information in this thread, so let's get to business.
First thing I want to straighten out is that you said your Baseband Version says "Unknown", i think you should check your IMEI information, if your IMEI is "null" then there is another problem to fix first.
If you have tried restoring from a backup after the "Baseband Unkown" issue and the Baseband Version still says "Unknown", then something happened whilst, or after you tried flashing CrDroid. At this moment I am not so knowledgeable about how to fix the Unkown Baseband issue, but it is a well known problem and usually coincides with the IMEI "null" issue. If you still are having that problem, I will try to find out how to fix it.
However, I will provide you with my full answer so this can hopefully get fixed at your preferred pace.
To start out, my questions are:
1. What ROM/Version of that ROM are you running right now? (I assume it is Resurrection Remix 6.0.1?)
2. Do you have a backup before trying to flash CrDroid? If so, I would suggest restoring from your backup to fix your "Settings Unkown" issue.
Once your Baseband "Unknown" problem is fixed, you can continue on to flash CrDroid (This time, it should work). Now I just downloaded the CrDroid zip file, that you used, on my PC. And just from opening it I can already tell that it is deeply based on CyanogenMod, but with some tweaks to make it CrDroid. Reason I mention this is because of this quote:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
I'm not super knowledgeable on downloading Custom Kernels, but i do know that your Kernel:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
is (I'm 99%sure) a CyanogenMod Custom Kernel, which comes when you flash a CM ROM.
Mine is:
3.4.0-CM-gc6520f1
[email protected] #1
Click to expand...
Click to collapse
and I'm running CyanogenMod 13, 6.0.1 on my vs985. Point is, you should be all set to flash CrDroid based on your Kernel.
Now, the "Unsupported Baseband" issue when flashing, at least CM based ROMs, is a known error recently. (In the past year I'd say) So the very common way to get around this, without having any issues, is to:
1. Go into your downloaded ROM zip, the zip you wish to flash, in your case it's crdroid-6.0.1-20160118-vs985.zip.
2. Extract the files into a folder (I'd recommend naming the folder the name of the .zip file, for ease in the end)
3. Open the extracted files folder
4. Open "META-INF" ==> "com" ==> "google" ==> "android"
5. Within that "android" folder, open "updater-script" file with Notepad, or a similar text editor.
6. Delete this line of code:
assert(getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "vs985" || getprop("ro.build.product") == "vs985" || abort("This package is for device: g3,vs985; this device is " + getprop("ro.product.device") + ".");
assert(g3.verify_baseband("35B:MPSS.DI.2.0.1.C1.13.4-00005") == "1");
Click to expand...
Click to collapse
7. You should be left with "ui_print("Target: lge/g3_vzw....." in your case.
8. Overwrite the edited "updater-script" back to it's directory (the android folder)
9. (Make sure you don't save it as a .txt file, it should still be a "File" (no extension))
10. Now go back to the "crdroid-6.0.1-20160118-vs985" folder after editing and saving "updater-script"
11. Select all the files/folders within, and add them to a .zip archive (Recommended by using WinRar)
12. You should end up with a .zip file visually identical to the original crdroid-6.0.1-20160118-vs985.zip, except this one has the edited "updater-script"
13. The edited one^ is the only one you need now, and is the one you will be flashing
14. Also, if you're curious I have done this many times with CyanogenMod, on vs985, and can assure you nothing bad will come of this... I assume the same is with CrDroid as it is deeply based on CM. (As long as you're "Unknown Baseband" problem has been fixed.
This procedure essentially gets rid of the Baseband/Model Check, ensuring a successful flash. Also as you can see in the code, it checks for the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Baseband/Modem version, I believe "xdabbed" makes a flashable version of the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Modem, which should eliminate the need to edit the updater-script. However, I strongly recommend to do the "updater-script" fix rather than trying to flash a different Baseband, as I have heard flashing a new Baseband can easily brick your phone, and you really do not need to do it.
I have Baseband: MPSS.DI.2.0.1.c1.13-00008, which does not match the "Baseband Check" and my ROM still works like a charm after the updater-script fix.
However, before you flash the edited crdroid-6.0.1-20160118-vs985.zip with your TWRP seperately, with the Marshmallow (6.x) ROMs right now, if you plan on using GApps you need to flash the ROM AND the GApps file at the same time in your custom recovery. Otherwise you will most likely get errors and you will need to re-flash the ROM and GApps.
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Click to expand...
Click to collapse
To answer this, no it is not a problem, you were correct.
1. The LG G3 is an ARM device
2. GApps only uses the first two digits in the OS version (i.e. 5.0.x or 6.0.x) (<==That "x" variable is the third digit in the OS version, and does not matter in GApps
3. All in all you have the correct version of GApps, no you just need to flash it at the same time as your edited ROM.
The procedure you did to flash the ROM was all good:
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally
Click to expand...
Click to collapse
This is great, again the reason it didn't work was because of the mismatch in the Baseband Check, which shouldn't persist after following the instructions in the "updater-script" fix.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
Click to expand...
Click to collapse
1. The Baseband Version is not supposed to state "Unknown", as i said in the beginning, this is a problem that happens sometimes, I am not sure why, or exactly how to fix it, but if you do some research I'm sure you will find something, I will also do some research so I can try to help you with that if it is not fixed by a Factory Reset or a Restore from Backup
2. The Baseband Version that a specific ROM calls for will be in that "updater-script" I was talking about, at least that's how it is for CyanogenMod based ROMs. I think your stock Baseband Version will work with any custom ROM, as long as it is a ROM made for your specific phone. That being said, I do think that the latest Baseband Version for your specific phone does improve Network, Cellular and GPS Connectivity, but again I do not recommend venturing there yet, until you have alot of background on it and can do it safely.
3. If the ROM you intend to flash doesn't support your Baseband, chances are the ROM is not made for your phone or you somehow have a Custom Baseband that is not made for your phone. I say that because even though you get that Baseband error when flashing CM based ROM, it is still supported, it's just that you do not have the "latest" Baseband Version I believe.
I do believe I have answered all of your questions, at least I hope so. I'm sorry that some things I could not answer in great detail, but I tried my best so that you could continue on enjoying your device. I also have the VS985 so I'm familiar with the device.
Summary:
1. Before anything try to Restore from Backup to fix the Baseband "Unknown" issue, as fixing this is priority. If that does not work I will try to find a fix online, or you can try to beat me to it.
2. Once that is fixed^ you can carry on with the "updater-script" fix i included.
3. Then flash the edited ROM and your 6.0, ARM OpenGApps at the same time (one right after another, without a Reboot in between)
4. Then you should honestly be all set
5. Your Kernel is all set for CrDroid
6. The GApps you said you downloaded is all good for the CrDroid version you downloaded
7. You could also try to flash back to vs985 stock (10B) this will hopefully give you your Baseband back if you still need it after Restoring from Backup
7. You should get no errors now! Yay. Now you can enjoy a Battery Optimized beautiful Marshmallow ROM
Click to expand...
Click to collapse
Please let me know if you have any confusion, I would be happy to provide you with clarification, screenshots etc.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Edit: I'm not sure if Fastboot is actually working. I can't get it to do anything. It just hangs on whatever command I give it, and it continues to hang until I unplug USB, then fails.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Click to expand...
Click to collapse
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: forum.xda-developers.com/showthread.php?t=2785089 - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Edit: Sorry, I didn't reach 10 posts yet, so you gotta drag 'n drop the links
Williquah said:
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot http://forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
http://http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: http://lgflashtool.net/index.php/tot-method/ - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Click to expand...
Click to collapse
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
---------- Post added at 09:09 AM ---------- Previous post was at 08:37 AM ----------
Knux Kitsune said:
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Knux Kitsune said:
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Click to expand...
Click to collapse
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Williquah said:
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Click to expand...
Click to collapse
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
*Solution*
Knux Kitsune said:
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
Click to expand...
Click to collapse
Awesome, well that's good that you eventually reached your goal. I can't say for sure why your connection was unstable on the Stock Kit Kat, but the 35B baseband is for 35B (5.1.1) Lollipop. The TOT method flashes back Stock Firmware, which is 10B (I believe 4.2.2) - KitKat so you would then need the Stock Modem IMG: (10B Modem File) but you are past that.. which is great. The Phone Service not responding is, I'm sure, a result of the incompatible 35B Modem mixing with 10B (4.2.2) Software Version. That's why flashing XDABBEB's Stock ROM fixed it (at least the second time around), because it includes all the stock IMGs, including the stock Baseband Version (10B).
But I'm so glad that you re-flashed and wiped again, because you have literally managed to return it to complete stock. Your baseband is official, and seems to me.. completely fixed!
Just confused with this:
It seems to run faster on Marshmallow than it did on Lollipop.
Click to expand...
Click to collapse
Are you running Marshmallow now? Or Kit Kat? I think I just lost you at some point haha.
But congrats on fully flipping your situation around! And in fact, because you fixed your Baseband issue, this thread is now completely answered! :good:
The TOT Method does wonders, doesn't it :victory:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Knux Kitsune said:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Click to expand...
Click to collapse
Ohhh, I see. I totally agree with you, it really makes no sense... the phone was built a certain way, it was meant to be used like that. Why the providers "nerf" them, I don't know. Even with the FM radio, they disable the receiver on the phones, I assume so that we are forced to stream instead, and they make more money. It's absolute sh**. But yeah, alright well that's cool, I might have to flash that myself actually, Marshmallow is lookin' really nice, as long as the battery life ain't too bad I'm gonna test it out myself!
Excuse me, first i´m sorry for my bad english language. I have same problem the unsupported baseband, but till now i just feel confused. I flash the Resurrection Remix Nougat on twrp and says unsupported baseband error. What should i do first? Flash the new baseband? If it yes, which baseband version is suitable for my device. Im using LG d855 and running android 6. Or i must unlock bootloader before flashing the new ROM? Thankyou, hope anyone will answer my stupid question.
I am using micromax q372 smartphone, had an android 5.0 stock ROM, and now i have installed resurrection remix 5.5.9, and my DEVICE OFFICIALY DOESN'T SUPPORT, and I garbed all of my luck and installed it, and now I have a fully working custom ROM on a unsupported device, the only problem I had was with the data connection, and I sorted it out, now everything is working, .............now I want to install resurrection remix 5.9.X , and my device doesn't is not on the support list, so ....can I do it , without any bugs? .......plz advice me
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message "android.process.media has stopped".
I've used the following installation procedure:
1. Starting with the stock Samsung Android v4.4.2, I used Odin v3.1.2, to root the device, by installing
CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md
2. I used Odin to install picassowifi TWRP v2.8.7.0. I didn't use the latest v3.1.1-0, because it reboots the
device while making Nandroid backups. Available here
https://eu.dl.twrp.me/picassowifi/
3. I copied several versions of Lineage OS amd Gapps (see below) to the device's SD card
4. I used TWRP to wipe the cache/dalvic/data/system each time, using the Wipe->Advanced option
5. I used TWRP to install the Lineage OS amd Gapps as an atomic operation on the device
6. After installation, I rebooted from TWRP:
- without rooting: I get the message "Google Services Framework keeps stopping"
- with rooting, by installing SuperSU: The device enters into a boot loop, displaying the sliding Lineage logo
I followed the same procedure to update my Samsung Galaxy S4 Mini, and it worked flawlessly.
I tried the following Lineage OS versions, available here:
https://download.exynos5420.com/LineageOS-14.1/n2awifi/
lineage-14.1-20170506-UNOFFICIAL-n2awifi.zip
lineage-14.1-20170715-UNOFFICIAL-n2awifi.zip
I also tried the folowing Lineage OS versions, available here:
https://download.lineageos.org/n2awifi
lineage-14.1-20170608-nightly-n2awifi-signed.zip
lineage-14.1-20170713-nightly-n2awifi-signed.zip
I tried the following versions of Gapps, available here (32-bit arm, Android v7.1, stock variant):
http://opengapps.org/?api=7.1&variant=stock
open_gapps-arm-7.1-stock-20170505.ziip
open_gapps-arm-7.1-stock-20170711
I tried several combinations of these 2 packages. With all the combinations I tried, I got the results summarised above.
This post suggests installing Lineage OS alone without Gapps, and then install Webview Implementation, if not installed:
http://www.lineageosrom.com/2017/02/how-to-fix-google-play-services-error.html
When I tried this and reboot, I get the messages "android.process.media" has stopped, followed by the message "clock has stopped". When I click away these messages, and click on next on the Lineage OS screen, the device enters into a boot loop displaying the sliding Lineage logo. This agrees with the Lineage recommendation, that both packages need to be installed at the same time:
https://wiki.lineageos.org/devices/n2awifi/install
Can anyone please help? I really don't want to go back to Android v4.4.2 on my SM-T520.
Hello so to get rid of the error I would suggest downloading samsung kies 1 not 2 or 3 and flashing completely back to stock then try rooting and flashing rom should get rid of system errors and force closes. Kies will ask you for model and serial number. Serial is found on back of the tablet. As another suggestion I would try resurrection remix by cosmox. It is very stable everything works. I just posted a link in that thread with a link to download samsung kies for a 64 bit windows and other relevant files if you need. Let me know if you need any other help. Also closer inspection of your links. I think for sm-t520 u should be using twrp Picassowifi, not n2awifi so idk if that will work or not. Not sure about that part though because they may have made it work on Picasso.
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
paintball,
I've found a solution, that I thought I'd post here in case anyone else has the same problem.
I wiped the cache/dalvic after each step of the installation:
Wipe-> Advanced -> wipe cache / data / dalvic / system
Install -> flash Lineage -> wipe cache/dalvic
Install -> flash Gapps -> wipe cache/dalvic
Reboot -> don't install SuRoot
I got a Music closed error during the first boot, which hasn't appeared since.
Afterwards, I used Odin to install CF-Auto-Root. The device rebooted twice after this step, but now appears to be OK.
A final problem I had was that it couldn't find my wifi SSID. I solved this by setting wifi region to Europe.
ppmoore said:
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
Click to expand...
Click to collapse
I suggested using Samsung kies which I'm positive works, not Odin, but I'm glad you got it fixed.
ppmoore said:
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message
<snip>
Click to expand...
Click to collapse
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
I have tried several permutations of Lineage OS nightlies along with various flavors of OpenGApps, with and without root, wiping cache/dalvik/data/system, wiping only some, wiping none.
I also cannot restore the backup of the running LOS that I had up (I did take a backup before going back to the original setup). When I try, I get the same results as above--as if I had backed-up an un-instantiated setup.
Any thoughts?
eckster said:
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
Any thoughts?
Click to expand...
Click to collapse
Hi Eckster,
I have exactly the same problem on a LG G2 with LOS 14.1. It ran July version perfectly but I didn't make a backup and now I'm stuck. Did you ever manage to fix this?
Thanks,
Kevin
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
how did you format the partitions? I can only find "format data".. thx
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
:thumbsup: I was on lineage 14, all was well. I tried an old stock rom NK2, that was fine. I tried to restore lineage backup via twrp, got this problem with the framework crashing. No amount of re-flashing twrp nor lineage, gapps, modem, bootloader, etc nothing worked; always crashed right after boot to lock screen. Finally twrp "format data" - yes. Now lineage boots to welcome, no crash; restore backup - after copying it back to internal - and all is good.
I'm glad it works but why is it needed in this case to remake the filesystem on data - does it work by removing some bad file or does it work by rebuilding the ext4 and security context? this is with latest twrp twrp-3.2.1-0-klte.
Hi,
don't know if you solved it eventually, or maybe helpful for other people with the same problem. I had the same problem, spent 6 days digging around on the internet why the framework keeps stopping and crashing.
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Say whatever you need to whatever deity you prefer and wait for the tablet to boot.
I hope to be of some help to other people having the same problem
Code:
Sent from my SM-S920L using Tapatalk
grammar
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
Was going crazy trying to figure out why LineageOS was encountering so many ANRs. The first time I flashed Lineage it worked beautifully but every time after that it just went nuts. This fixed it for me, thanks dude!
Note to others who may end up here, after formating data I had to install a stock ROM, then wipe and install Lineage. Lineage wouldn't install due to Updater process ended with ERROR: 7 which was because there was some bit of information that was on the data partition that showed the install script that the phone was actually a Note II. Formating data blows that info away but installing stock puts it back on.
LievenVanh said:
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Click to expand...
Click to collapse
Coming into this thread after a few hours of struggle with an old GS4 I can say that this method instantly worked for me as well.
Thanks!
Thanks for the help to resolve my issue of installation. Do you have a solution for Zoom , where my audio (cannot hear other speakers) and video is missing. Did enable access for Mic, Camera etc in App permission.
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
hamudistan said:
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
Click to expand...
Click to collapse
That solution didn't work. My Zoom audio still not working.