Related
Ok, so there seems to be some issues with installing the recent 4.2.1 OTA update with custom recoveries (ie: CWM or TWRP). I ran into this issue myself, and I've seen many other posts with similar problems. I've found the solution and explained it in multiple threads, but due to the nature of the issue, I thought it deserved it's own thread to make sure everyone is aware of the problem and the workaround.
Details:
The 4.2.1 OTA update comes in two flavors - nakasi and nakasig. The former is for WiFi devices (8, 16, 32), and the latter is for 3G devices. In turn, they each have their own device types - grouper and talapia, respectively. While the hardware differences between the WiFi and 3G models is negligible, and most things are interchangeable (ie: kernels, recoveries, etc.), the updates are NOT, and you need to pick the correct one for your platform. For the 3G models, this means the 'nakasig' version.
However, the first thing the OTA update does is validate the integrity of the system. In addition to checking about 200 files in the /system partition, it also looks at the device itself. Specifically:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2/JOP40C/527662:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2.1/JOP40D/533553:user/release-keys");
assert(getprop("ro.product.device") == "talapia" ||
getprop("ro.build.product") == "talapia");
While the first part checks the build.prop file to see what the "ro.build.fingerprint" has defined, the latter (bolded) assert examines what the RECOVERY says the system is. This is where the problem lies. AFAIK, there are no 'talipia' versions of CWM or TWRP. All 3G users running custom recoveries are using the 'grouper' (ie: Wi-Fi only) version. And this is fine 99% of the time. But this is the 1% of the time when they are not compatible. As a result, when the updater script checks recovery, and is told that the system is 'grouper', it aborts the update.
I ran into this issue on both the latest versions of TWRP and CWM. I wasn't sure why, since I thought it just looked at build.prop which was OK. After speaking with oldblue910, he explained that it is getting that information not from build.prop, but from the custom recovery, which is why the update was failing (thanks to oldblue910 for the info!).
SO, I was left with one of two options. I could either restore the stock talipia recovery or modify the update zip to ignore this information. I chose the latter. I'm not sure why Google decided to even but this redundant check in place, since the build.prop fingerprint check should suffice to validate the hardware. Not to mention that the next part of the update is to assert check the majority of files in 'system' anyway, which would fail if it wasn't a 3G device. In any case, by removing the above bolded lines out of the updater-script, my tablet was able to be successfully updated to 4.2.1.
Since many other XDA users run custom recoveries, it is safe to say many other users will run into this issue as well. So I put my custom update online for anyone else to use.
You can download it here:
http://core.routed.com/CUSTOM_RECOVERY-65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
MD5SUM: b0adff6a04ca2ca6234a9678476d329e
A couple notes:
1) This update zip is completely identical to the Google version, outside of the talipia check removed.
2) This update should ONLY BE USED ON 3G NEXUS 7 MODELS. It will NOT work on Wi-Fi only versions.
3) All the other asserts are left in-tact, as they should be. So your 'system' needs to be mostly stock. It checks and patches about 200 files, and if any of them are modified, removed, frozen, etc., the update will fail.
4) The OTA update does NOT check or update the bootloader or kernel, so modifications or non-4.2-stock versions in those areas are fine. However, as stated in #3, mostly everything else should be stock.
5) If the update fails on a specific assert, it will explain what the problem is (ie: the specific apk or odex file). You will need to fix that before proceeding. If you run into an issue and require assistance, you will need to explain the exact error message.
6) As this is almost completely stock OTA update, you WILL lose root/custom recovery unless you take precautions to prevent them from being overwritten. To preserve root, you can use RootKeeper or a similar app to back it up. The latest version of CWM also will warn you if root is lost and apparently restore it for you. For the recovery side of things, the update puts that recovery-recovery file on the system. You can either manually remove it via adb shell (BEFORE REBOOTING AFTER THE UPDATE), or in CWM (and possibly TWRP's case), it should warn you that you might lose custom recovery after the update and ask if you want it to fix it for you (say yes).
Hopefully this helps others who ran into the same error as me. Enjoy!
phonic said:
Ok, so there seems to be some issues with installing the recent 4.2.1 OTA update with custom recoveries (ie: CWM or TWRP). I ran into this issue myself, and I've seen many other posts with similar problems. I've found the solution and explained it in multiple threads, but due to the nature of the issue, I thought it deserved it's own thread to make sure everyone is aware of the problem and the workaround.
Details:
The 4.2.1 OTA update comes in two flavors - nakasi and nakasig. The former is for WiFi devices (8, 16, 32), and the latter is for 3G devices. In turn, they each have their own device types - grouper and talapia, respectively. While the hardware differences between the WiFi and 3G models is negligible, and most things are interchangeable (ie: kernels, recoveries, etc.), the updates are NOT, and you need to pick the correct one for your platform. For the 3G models, this means the 'nakasig' version.
However, the first thing the OTA update does is validate the integrity of the system. In addition to checking about 200 files in the /system partition, it also looks at the device itself. Specifically:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2/JOP40C/527662:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/nakasig/tilapia:4.2.1/JOP40D/533553:user/release-keys");
assert(getprop("ro.product.device") == "talapia" ||
getprop("ro.build.product") == "talapia");
While the first part checks the build.prop file to see what the "ro.build.fingerprint" has defined, the latter (bolded) assert examines what the RECOVERY says the system is. This is where the problem lies. AFAIK, there are no 'talipia' versions of CWM or TWRP. All 3G users running custom recoveries are using the 'grouper' (ie: Wi-Fi only) version. And this is fine 99% of the time. But this is the 1% of the time when they are not compatible. As a result, when the updater script checks recovery, and is told that the system is 'grouper', it aborts the update.
I ran into this issue on both the latest versions of TWRP and CWM. I wasn't sure why, since I thought it just looked at build.prop which was OK. After speaking with oldblue910, he explained that it is getting that information not from build.prop, but from the custom recovery, which is why the update was failing (thanks to oldblue910 for the info!).
SO, I was left with one of two options. I could either restore the stock talipia recovery or modify the update zip to ignore this information. I chose the latter. I'm not sure why Google decided to even but this redundant check in place, since the build.prop fingerprint check should suffice to validate the hardware. Not to mention that the next part of the update is to assert check the majority of files in 'system' anyway, which would fail if it wasn't a 3G device. In any case, by removing the above bolded lines out of the updater-script, my tablet was able to be successfully updated to 4.2.1.
Since many other XDA users run custom recoveries, it is safe to say many other users will run into this issue as well. So I put my custom update online for anyone else to use.
You can download it here:
http://core.routed.com/CUSTOM_RECOVERY-65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
MD5SUM: b0adff6a04ca2ca6234a9678476d329e
A couple notes:
1) This update zip is completely identical to the Google version, outside of the talipia check removed.
2) This update should ONLY BE USED ON 3G NEXUS 7 MODELS. It will NOT work on Wi-Fi only versions.
3) All the other asserts are left in-tact, as they should be. So your 'system' needs to be mostly stock. It checks and patches about 200 files, and if any of them are modified, removed, frozen, etc., the update will fail.
4) The OTA update does NOT check or update the bootloader or kernel, so modifications or non-4.2-stock versions in those areas are fine. However, as stated in #3, mostly everything else should be stock.
5) If the update fails on a specific assert, it will explain what the problem is (ie: the specific apk or odex file). You will need to fix that before proceeding. If you run into an issue and require assistance, you will need to explain the exact error message.
6) As this is almost completely stock OTA update, you WILL lose root/custom recovery unless you take precautions to prevent them from being overwritten. To preserve root, you can use RootKeeper or a similar app to back it up. The latest version of CWM also will warn you if root is lost and apparently restore it for you. For the recovery side of things, the update puts that recovery-recovery file on the system. You can either manually remove it via adb shell (BEFORE REBOOTING AFTER THE UPDATE), or in CWM (and possibly TWRP's case), it should warn you that you might lose custom recovery after the update and ask if you want it to fix it for you (say yes).
Hopefully this helps others who ran into the same error as me. Enjoy!
Click to expand...
Click to collapse
I compiled a CWM image for tilapia, so now users can flash updates and roms for their device without trying to by-pass the safety checks. With everyone recommending flashing grouper recovery, people are going to keep flashing grouper roms and wonder why things aren't working correctly.
The two devices differ in more respects than a simple assert check, including having different recovery.fstab files, which are used to make and configure recovery.
Better to have proper recovery for our (unique) device instead of a grouper port. The CWM image is not touch, the touch sources are not open source and koush's online builder is not producing a working image at this time. I ported one by hand, but it is too buggy to release.
I'll add twrp to the post sometime later.
mateorod said:
I compiled a CWM image for tilapia, so now users can flash updates and roms for their device without trying to by-pass the safety checks. With everyone recommending flashing grouper recovery, people are going to keep flashing grouper roms and wonder why things aren't working correctly.
Better to have proper recovery for our (unique) device instead of a grouper port. The CWM image is not touch, the touch sources are not open source and koush's online builder is not producing a working image at this time. I ported one by hand, but it is too buggy to release.
I'll add twrp to the post sometime later.
Click to expand...
Click to collapse
Thanks, that's definitely a better solution versus a work around.
Though the safety check bypassed in the OP wouldn't cause any issues since it was redundant and unnecessary. The OTA update already checks build.prop for the model info and all the apks/odexes it updates, so it would be impossible to flash it on a non-compatible device. But you raise a very valid point about incorrect ROMs and other things. The 3G unit probably needs it's own forum.
Did you have to make any real modifications to CWM outside of changing grouper to talapia?
The 3G unit probably needs it's own forum.
Click to expand...
Click to collapse
Its already done here; http://forum.xda-developers.com/forumdisplay.php?f=2022
Ather said:
Its already done here; http://forum.xda-developers.com/forumdisplay.php?f=2022
Click to expand...
Click to collapse
Woohoo! Thanks.
I had some issues when I did the update. It gave me some errors, and aborted, but then I found a link that had the update and I got it to update. This happened on my n4 and n73g. Well, for some reason, the recoveries got deleted so I had to reinstall them. I was able to use the goo manager to restore TWRP on my N4, but it wasn't working on my N7 so I had to side load it. After this, I noticed that google now wasn't working on my n4, and the volume rocker on my n7 had some issues. I went in and wiped the cache and dalvik cache and rebooted. Google now works on my N4, and while the volume gets adjusted on my N7, it won't make the beep every time I push up or down on the rocker indicating the volume level. I haven't noticed any other issues, but I haven't really delved into my devices. I may try to do a factory wipe and return everything to stock just to see what went wrong in the first place and to see if I can do anything different I still can't figure out how to get ADB running on my computer, so yes I used one of the tool kits to load everything. I know the OP's position on tool kits, but I just can't figure out how to get ADB running manually, AND it takes so long to download and install everything unless I am installing things I don't even need.
Nexus 7 takju firmware update
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Do you have the Galaxy Nexus or Nexus 7? If Galaxy Nexus, you of course would want to check those forums. As for the updates, you should normally see a notification alerting you of the update, but you can also check for it in settings/about phone/system updates. Otherwise the appropriate forum for your device will have links to the update files. Good luck!
lil help please
I updated to 4.2.1 with the OTA zip file using TWRP and voodoo root keeper installed. It flashed just fine. Rebooted with update. My root access is funky though. SuperSU is still there and I can access root file threw root explorer but I can't mount it as writable and when I install a new app that needs root access it never asks for it. Does superSU need to be updated? There is no update available for it.
Vlad7777 said:
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Click to expand...
Click to collapse
Is your device rooted? Is this your first android device? You will get a little notification in the notification bar at the top saying your deivce has an update.. If you have not rooted, you will receive the first OTA in a day or two that will go from JVP15S to JOP40C. Then later, you will receive the update for JOP40D. Some people have had success at forcing the update by going to settings, apps, all, google framework services, and selecting force stop then clearing the data. You then go back into settings, about device, check for updates and check for update.
Vlad7777 said:
Hi, while this is a very detailed description, I am still in need of help.
I just got a Google Nexus 7 from Google play store and it came with JVP15S firmware.
I understand that this is takju version of th edevice - I would like to upgrade it with the latest firmware but going through all the posts, I am totally lost.
I see upgrade files to upgrade from JOP40C to JOP40D - and see al ldifferent update combinations - but cannot fined one for JVP15S to JOP40D.
Also, all the updates are for different version "tilapia" and other fishes -- but none for takju (whatever that means)
Can someone direct me to right place to get the right updates/
Also I see a lot of posts and articles stating that Google is "pushing" the 4.2.1 Firmware JOP40D to Nexus 7 devices - how is this "pushing" manifest itself? What is the procedure for OTA update? Do I need to go to a place on Google to get it? Is it supposed to be downloaded automatically?
Hope someone can help.
Click to expand...
Click to collapse
The N73G ships with an interim 4.2 build, which is JVP15S. There are some significant differences between this and JOP40C, which is the first update you will get out of the box. I imagine 4.2 wasn't fully finalized prior to hardware production, and they didn't want to hold it up until they were ready (wise choise!). In my case, within an hour after opening my N73G and turning it on, I had the 40C update notification. I applied this prior to rooting/modding/etc. ONLY after you are on 40C can you get the upgrade to 40D (4.2.1). Google pushes out incremental patch updates, so you can't skip a version.
So you have two options:
1) Apply update #1 and wait for #2 and then root/etc.
2) If you don't want to wait, and your device is still basically brand new and not setup (too much), AND assuming you want to root, customize, etc., just download the 4.2.1 system image from Google and fastboot flash it. You'll need to unlock the bootloader anyway, which will wipe your system, so now's a perfectly good time to do everything at once. Unlock bootloader, flash 4.2.1 stock (40D FULL IMAGE), flash custom recovery, install su zip, install any other mods (which is limited really to basic stuff and a custom kernel right now), enjoy.
Andoid 4.2.1 update
adamhlj said:
Is your device rooted? Is this your first android device? You will get a little notification in the notification bar at the top saying your deivce has an update.. If you have not rooted, you will receive the first OTA in a day or two that will go from JVP15S to JOP40C. Then later, you will receive the update for JOP40D. Some people have had success at forcing the update by going to settings, apps, all, google framework services, and selecting force stop then clearing the data. You then go back into settings, about device, check for updates and check for update.
Click to expand...
Click to collapse
Thanks!
It is my first Android device.
I am trying to root it (unsuccessfully).
I was able to get the FASTBOOT unlock - but cannot root because of the drivers interface...
I did update the firmware by forcing via framework system. Had to do in two steps as it only upgrades one generation at a time.
By the way - I had the "takju" - now it is "tilapia" after "official OTA update.
I hope to get the rooting problem resolved - all instructions on the net are for older ROMs and I already screwed up my work laptop installing obsolete PDANET drivers which replaced the original drivers - so my device manager which originally saw my Nexus 7 as "Nexus 7" now sees it as "Android Phone Device". I do not know how to recvert back.
So now I am going to try my other laptop for rooting.
Hopefully I could find just a "professional step by step procedure - unlike many that I found on the net. Many people just happy to get on YouTube to show themselves off but the advice is half ass.
Thanks again for your help though I am half way through.
Best regards
Vlad7777 said:
Thanks!
It is my first Android device.
I am trying to root it (unsuccessfully).
I was able to get the FASTBOOT unlock - but cannot root because of the drivers interface...
I did update the firmware by forcing via framework system. Had to do in two steps as it only upgrades one generation at a time.
By the way - I had the "takju" - now it is "tilapia" after "official OTA update.
I hope to get the rooting problem resolved - all instructions on the net are for older ROMs and I already screwed up my work laptop installing obsolete PDANET drivers which replaced the original drivers - so my device manager which originally saw my Nexus 7 as "Nexus 7" now sees it as "Android Phone Device". I do not know how to recvert back.
So now I am going to try my other laptop for rooting.
Hopefully I could find just a "professional step by step procedure - unlike many that I found on the net. Many people just happy to get on YouTube to show themselves off but the advice is half ass.
Thanks again for your help though I am half way through.
Best regards
Click to expand...
Click to collapse
I think you are either looking at really bad guides or simply making the rooting process much harder on yourself.
While some Android devices have more complicated unlocking/rooting/etc. requirements, that is not the case with Nexus devices - certainly not the Nexus7. The process couldn't be more simple. If you've already unlocked the bootloader, you are 1/3 of the way there. All you need to do is copy over a compatible "su" app zip to the device, install or run a custom recovery, install the su zip and voila - rooted.
If you already have fastboot running, that's the only tool you need. Download a custom recovery (CWM or TWRP) from a thread in this forum that is compatible, reboot into bootloader mode and install it:
fastboot flash recovery <recovery.img>
Then reboot into recovery mode (you can do this from bootloader), and you should be in CWM/TWRP. Then you simply install the SU zip using the menu on the screen.
It's a very simple process and does not require a special toolkit or anything like that.
phonic said:
I think you are either looking at really bad guides or simply making the rooting process much harder on yourself.
While some Android devices have more complicated unlocking/rooting/etc. requirements, that is not the case with Nexus devices - certainly not the Nexus7. The process couldn't be more simple. If you've already unlocked the bootloader, you are 1/3 of the way there. All you need to do is copy over a compatible "su" app zip to the device, install or run a custom recovery, install the su zip and voila - rooted.
If you already have fastboot running, that's the only tool you need. Download a custom recovery (CWM or TWRP) from a thread in this forum that is compatible, reboot into bootloader mode and install it:
fastboot flash recovery <recovery.img>
Then reboot into recovery mode (you can do this from bootloader), and you should be in CWM/TWRP. Then you simply install the SU zip using the menu on the screen.
It's a very simple process and does not require a special toolkit or anything like that.
Click to expand...
Click to collapse
Thank you for your reply and advice.
How do I place the "su zip" in the device and into which directory - I can try download directly to Nexus but needs to know where to place it.
Also what are "CWM" or "TWRP" And where do I place them for custom recovery procedure.
I apologize for my ignorance but Android is a complete new experience for me.
Vlad7777 said:
Thank you for your reply and advice.
How do I place the "su zip" in the device and into which directory - I can try download directly to Nexus but needs to know where to place it.
Also what are "CWM" or "TWRP" And where do I place them for custom recovery procedure.
I apologize for my ignorance but Android is a complete new experience for me.
Click to expand...
Click to collapse
You can place the "su zip" anywhere you like on the internal storage. When you get into custom recovery (CWM or TWRP), you can select "Install ZIP" (or something along those lines) and it will bring up a file system explorer that will let you select the one you want to install.
CWM and TWRP are both custom recoveries. They replace the stock, and very useless, recovery and give you many more advanced features. Things like flashing zip files, making nandroid backups, etc. You need to flash them to your "recovery" partition. It's a very easy process, but will require some specialized software. There are many guides and toolkits (if that's what you want to use) online. Just make sure you use the Talipia recovery (which exists now in the 3G forum).
... to the latest nightly 02/12, it has a broken kernel / recovery mode!!
If you did, flashing via Odin will be necessary.
;( can u help me? i've flashing via Odin but it doesn't start boot loop
I tried the version of today : 20140213 and also that one seems to fail.
Was this via OpenDelta, or a complete ZIP downloaded from dl.omnirom.org?
None of the developers can reproduce issues with locally-build ZIPs, and I think xplodwild flashed a nightly ZIP with no issues too.
My 20140212 got flashed via opendelta
Entropy512 said:
Was this via OpenDelta, or a complete ZIP downloaded from dl.omnirom.org?
None of the developers can reproduce issues with locally-build ZIPs, and I think xplodwild flashed a nightly ZIP with no issues too.
Click to expand...
Click to collapse
It came with OpenDelta.
my post here can help :
http://forum.xda-developers.com/showthread.php?t=2647218
Entropy, I can make test with my spare i9100 if it can help ! Just tell me what do you need
Entropy512 said:
Was this via OpenDelta, or a complete ZIP downloaded from dl.omnirom.org?
None of the developers can reproduce issues with locally-build ZIPs, and I think xplodwild flashed a nightly ZIP with no issues too.
Click to expand...
Click to collapse
I had the issue with a locally build zip. And also with an OpenDelta update.
It gets fixed (the bootloop that is, there are other issues) by just replacing the kernel. Between the previous nightly and the broken one, there's only one commit in the kernel project: https://gerrit.omnirom.org/#/c/5019/.
But here's the mystery: most people, including me, seem to be able to solve the problem by installing the latest gustavo's kernel. But that one also seems to have that code... However, even though I saw no one reporting problems with the latest gustavo's, I did in one of my many trials have issues with it dumping back into TWRP instead of booting. I never had issues with older omni or gustavo's kernels and the 0212 rom.
Because of the other issues (Settings.apk not being loaded starting from 0212) I'm still on pre-0212 and experimenting...
Update: build a current zip, with 5019 reverted to its PS2, which I think didn't have trouble yet. However, it still bootloops. (Of course I may be doing something wrong however; I'm not very experienced with this sort of thing).
Update 2: build a zip with 5019 fully reverted: no boot loop! I am currently verifying whether including 5019 again will break stuff again.
Update 3: yes, it does. I took great care to follow the exact same install procedure. So this confirms https://gerrit.omnirom.org/#/c/5019/ as the culprit.
The 2014-02-12 update for OpenDelta has also caused my i9100 to boot loop.
Hoping the post by -Furion- will fix it.
will test after work.
Edit:
Works fine when done with odin ver3.04
GidiK said:
I had the issue with a locally build zip. And also with an OpenDelta update.
It gets fixed (the bootloop that is, there are other issues) by just replacing the kernel. Between the previous nightly and the broken one, there's only one commit in the kernel project: https://gerrit.omnirom.org/#/c/5019/.
But here's the mystery: most people, including me, seem to be able to solve the problem by installing the latest gustavo's kernel. But that one also seems to have that code... However, even though I saw no one reporting problems with the latest gustavo's, I did in one of my many trials have issues with it dumping back into TWRP instead of booting. I never had issues with older omni or gustavo's kernels and the 0212 rom.
Because of the other issues (Settings.apk not being loaded starting from 0212) I'm still on pre-0212 and experimenting...
Update: build a current zip, with 5019 reverted to its PS2, which I think didn't have trouble yet. However, it still bootloops. (Of course I may be doing something wrong however; I'm not very experienced with this sort of thing).
Update 2: build a zip with 5019 fully reverted: no boot loop! I am currently verifying whether including 5019 again will break stuff again.
Update 3: yes, it does. I took great care to follow the exact same install procedure. So this confirms https://gerrit.omnirom.org/#/c/5019/ as the culprit.
Click to expand...
Click to collapse
OK this is really weird. I9100 and I777 have 100% identical displays (the only differences between these two devices are the touchkeys, call audio, and NFC. In fact I9100 kernels will boot on i777 although the above items will not work correctly of course...) and my i777 is booting fine even with that patch.
wtf?
Entropy512 said:
OK this is really weird. I9100 and I777 have 100% identical displays (the only differences between these two devices are the touchkeys, call audio, and NFC. In fact I9100 kernels will boot on i777 although the above items will not work correctly of course...) and my i777 is booting fine even with that patch.
wtf?
Click to expand...
Click to collapse
We're definitely in the land of weirdness here. Judging by the SII I9100 thread, some people with i9100 also have no problem...
I don't know what I'm talking about, but could it be an issue unrelated to the code? The way it's build? The resulting kernel size? Maybe any other change would also have caused problems?
GidiK said:
We're definitely in the land of weirdness here. Judging by the SII I9100 thread, some people with i9100 also have no problem...
I don't know what I'm talking about, but could it be an issue unrelated to the code? The way it's build? The resulting kernel size? Maybe any other change would also have caused problems?
Click to expand...
Click to collapse
OK that's REALLY weird if not all I9100 users have problems. Great. I'll check when I get home if xplodwild has tried this on his device, hopefully he can reproduce the problem.
stupid unified kernel/recovery approach, makes it damn near impossible to get a last_kmsg of a failure.
OK, here's a question: Can one person who is having issues with the newer kernels and one person who isn't please run the following command and put the output here, including whether or not you're having problems with the newer kernels on your device. (People who are having issues with the new kernels need to flash an older kernel to do this, people who are not having issues can get this from a newer kernel.)
Code:
cat /proc/cmdline
Please only post this information if you have results that differ from results already posted, specifically:
Look at the lcdtype variable (if present) or (if present) the ld9040.get_lcdtype variable
If you have the same lcdtype as someone who has already posted results AND you are getting the same results, don't post your results as they are unnecessary
If you have the same lcdtype as someone who has already posted results AND you have different results with new kernels, quote the other person and post that you're getting different results
Issues: yes. ld9040.get_lcdtype=0x0.
Not exactly from an older kernel, but with the patch reverted so effectively the same; I hope that isn't a problem. Redacted the serialno just in case:
Code:
console=ttySAC2,115200 consoleblank=0 androidboot.selinux=permissive loglevel=4 console=ram androidboot.serialno=*** sec_debug.enable=0 sec_debug.enable_user=0 c1_watchdog.sec_pet=5 [email protected] s3cfb.bootloaderfb=0x5ec00000 ld9040.get_lcdtype=0x0 consoleblank=0 lpj=3981312 vmalloc=144m
Issues: no. ld9040.get_lcdtype=0x2
running 20140212 nightly
GidiK said:
Issues: yes. ld9040.get_lcdtype=0x0.
Not exactly from an older kernel, but with the patch reverted so effectively the same; I hope that isn't a problem. Redacted the serialno just in case:
Code:
console=ttySAC2,115200 consoleblank=0 androidboot.selinux=permissive loglevel=4 console=ram androidboot.serialno=*** sec_debug.enable=0 sec_debug.enable_user=0 c1_watchdog.sec_pet=5 [email protected] s3cfb.bootloaderfb=0x5ec00000 ld9040.get_lcdtype=0x0 consoleblank=0 lpj=3981312 vmalloc=144m
Click to expand...
Click to collapse
Not a problem. I pretty much meant "any working kernel"
_mikey_ said:
Issues: no. ld9040.get_lcdtype=0x2
running 20140212 nightly
Click to expand...
Click to collapse
Thanks.
So, so far:
People with 0x0 have failures
People with 0x2 do not have failures
No need to post results if you have results that match the above.
Entropy512 said:
So, so far:
People with 0x0 have failures
People with 0x2 do not have failures
No need to post results if you have results that match the above.
Click to expand...
Click to collapse
I don't pretend to understand anything about the code, but the patch moves initialization code from one file to another, and this initializes equally for lcdtypes 1 and 2, but differently for lcdtype 0. Was "&u1_panel_data", is now "&s2plus_panel_data" for lcdtype "LCDTYPE_SM2_A1", i.e. 0. No idea what this means, but I don't have an S2plus.
GidiK said:
I don't pretend to understand anything about the code, but the patch moves initialization code from one file to another, and this initializes equally for lcdtypes 1 and 2, but differently for lcdtype 0. Was "&u1_panel_data", is now "&s2plus_panel_data" for lcdtype "LCDTYPE_SM2_A1", i.e. 0. No idea what this means, but I don't have an S2plus.
Click to expand...
Click to collapse
Yup, got it, found the same thing. Also, s2plus_panel_data was an uninitialized struct.
https://gerrit.omnirom.org/5569
I've had no issues, and my results matches those posted.
Works on 20140215 NIGHTLY
Thank you,
The issue was resolved for me with nightly build 20140215
For me, too! Thx for tracking this down!!
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Hardley97 said:
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Click to expand...
Click to collapse
Here's my advice, go back to stock again,the LG flash tool. When that completes, use Freedom Tools (its in Development) and use ioroot25 (link is in the aforementioned thread) to root device. Then use Freedom Tool to install twrp. I've used it many times and never had a problem. Re-download cm rom (perhaps bad download) and flash in twrp. I would suggest using a more current twrp (start with 2.7, DL newest twrp, flash, reboot recovery) then flash cm. Let me know how it goes!
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Hardley97 said:
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Click to expand...
Click to collapse
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
njstein said:
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
Click to expand...
Click to collapse
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Hardley97 said:
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Click to expand...
Click to collapse
Dude, I'm sorry for not reading closer to begin with, but ya, you're trying to flash a JB rom with a KK recovery. 2.7 and up are for kk only. I'm so sorry...
Did you flash a gapps zip with Beanstalk? Did you do a completely clean install?
If you still want to flash a 10.2 cm you're going to have to find the appropriate recovery, and there I'm of no use since I entered this phone on kk and don't know anything about its jb history. Also don't know about the USB tether part either (I don't use it) so you're probably going to have to do some searching, flashing, and experimentation.
But bright side is we've figured out why you couldn't flash the cm rom. Either stay on kk or above, or start scrolling through the dev section looking for jb recovery...
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Hardley97 said:
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Click to expand...
Click to collapse
So glad it worked for you and you're up and running!
Nah, bro, I'm good. Give it to the devs, they deserve it. Giving knowledge through experience is what xda is all about, pass it on when you can. Thank you, though!
Hello XDA community, I am a 100% new noob who is interested in getting started with rooting. I am going to get right to the point with what I am working with, what I have done, and what I need some help with. May my journey with lovely pictures be a helpful guide for all those who follow me (I find it is easier to understand things with lots of images).
Used this thread to begin my journey on rooting an old Nook HD tablet.
Started with a factory reset but it automatically updated according to my settings page, so one of my question is; does it matter what software version my device is running before I root it?
Followed instructions in PeteInSequim guide and created an 8 GB Micro SD Card with all the files.
Green = CM-12.1_Installation_20150925 Instructions PDF
Light Blue = Files from NookHD-bootable-CWM-6046-for-emmc-BOOTFILES-rev0-(07.13.14)
Red = CyanogenMod 12.1 (No official release on their website)
Orange = ClockworkMod_Recovery (Couldn't find website for other versions)
Yellow = TWRP Recovery (They may have a newer version)
Purple = TK-GAPPS (Which I downloaded the STOCK package, and am not sure if that is compatible)
This is what I have done so far, and would like advise on what I should do before I advance, specifically around the TWRP VS. CWM with relation to the GAPPS packages. In the tutorial (PDF), I believe they use the CWM to install TWRP, I think TWRP is better and is the only of the two who will support my GAPPS package, but would like someone to help clarify so I don't make a permanent mistake. Also, should I use newer versions of anything? Should I even be attempting CM-12.1 if it is not officially supported? I don't want to have to keep making changes and not changing backgrounds or settings... should I go for the more stable CM-11, if so would I have to completely change my process?
Thanks for the help,
Buckaroo9
I'm a bit lazy when it comes to installing incremental releases, so I prefer to do simple "dirty installs". This means re-flashing without wiping the old installation, which can be done in seconds with no consequences.
But a dirty install will probably fail if you have made user-interface changes, even if you try to reverse out those changes before flashing. You can still install revisions any time you wish, but you must do the wipes first. This means you will have to go through the set-up procedure all over again, which takes a lot longer than a dirty install.
CM-12.1 for our Nooks should eventually be offered among the official nightly releases, and hopefully a milestone release now and then. I might consider UI tweaks after installing one of these, then settle down for a long quite period of no more updates.
If a stable CM-12.1 ever happens, we'll all be installing CM-13 by then.
Click to expand...
Click to collapse
PeteInSequim
Could you please explain this concept slightly more to me? How much would I be able to change and what would the consequences be? If I make changes would I always have to do a clean wipe, would that mean I would have to not make changes and constantly wait for updates? This uncertainty is kind of pushing me away from rooting...
Buckaroo9 said:
...
This is what I have done so far, and would like advise on what I should do before I advance, specifically around the TWRP VS. CWM with relation to the GAPPS packages. In the tutorial (PDF), I believe they use the CWM to install TWRP, I think TWRP is better and is the only of the two who will support my GAPPS package, but would like someone to help clarify so I don't make a permanent mistake.
Click to expand...
Click to collapse
The files you got look right, although I'd recommend using the smaller micro or even nano GApps packages as you can always add more apps later on.
Just use CWM to flash TWRP first, then boot to TWRP to wipe /data and flash CWM and GApps.
Also, should I use newer versions of anything? Should I even be attempting CM-12.1 if it is not officially supported? I don't want to have to keep making changes and not changing backgrounds or settings... should I go for the more stable CM-11, if so would I have to completely change my process?
...
Click to expand...
Click to collapse
CM12.1 for the HD/HD+ is not officially supported and, more importantly, is no longer enhanced/maintained (its original developer has recently moved onto CM13). I've been using CM12.1 for about a month now: the apps' performance can be noticeably more snappy but not consistently so, on the downside couple of apps/features that used to work on CM11 no longer work.
If you're looking for a reasonably newer but stable CM version, I'd suggest you try CM11 (either M12 snapshot or one of the recent "nightly" releases).
digixmax said:
Just use CWM to flash TWRP first, then boot to TWRP to wipe /data and flash CWM and GApps.
Click to expand...
Click to collapse
Is there any reason TWRP can't flash itself?
digixmax said:
I'd recommend using the smaller micro or even nano GApps packages as you can always add more apps later on.
Click to expand...
Click to collapse
Is there any downside to using a larger GApps, and if I can always add more, does that mean I can mix and match, are the essentially just packages of Apps that I am side-loading?
digixmax said:
If you're looking for a reasonably newer but stable CM version, I'd suggest you try CM11 (either M12 snapshot or one of the recent "nightly" releases).
Click to expand...
Click to collapse
I am definably leaning towards more stable, but in your opinion, what features would I loose from CM12 (Android 5.0 Lollipop)? Someone made a good point that, the most advanced, newest, and coolest software will always be unstable. You have to trade off the cutting edge for reliability and support.
As a new member to rooting, I think I may start with more stable things, and then work my way up.
Buckaroo9 said:
Is there any reason TWRP can't flash itself?
Click to expand...
Click to collapse
The TWRP flashable zip file you have contains a TWRP image that is compiled for internal EMMC. Once installed, it can be used to flash CM, GApps, or another version of CWM or TWRP to replace itself.
To flash from SD you need to find and use a TWRP recovery image that is compiled for SD.
Is there any downside to using a larger GApps, and if I can always add more, does that mean I can mix and match, are the essentially just packages of Apps that I am side-loading?
Click to expand...
Click to collapse
You can use a Zip archive program like 7-zip to open up and browse the content of these GApps zip packages to see and compare their particular mixes of apps.
I am definably leaning towards more stable, but in your opinion, what features would I loose from CM12 (Android 5.0 Lollipop)?
Click to expand...
Click to collapse
This depends on your particular use and choice of apps for the tablet, but as examples, the Hulu app and USB Host feature which work on CM11 don't work on CM12.1.
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Shplad said:
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Click to expand...
Click to collapse
see the index for correct safestrap version, 3.75 is latest, but you need the Droid 4 one
[INDEX] Development Motorola Droid 4
GApps are android version specific, opengapps.org are good
I haven't used the Droid 4 much since cm11, it's likely still a good option
sd_shadow's How-To Videos for Droid 4
Sent from my XT1254 using XDA Labs
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
The link for safe strap is not dead there are two versions. One from stargo and the other is a modified safe strap for unused partitions redone by some one else. You need to look in the correct posts and thread. Here is the download: http://www.internauta37.altervista....afestrap-maserati-v3.75-unused-partitions.apk
As far as for gsm keep looking you'll probully find something. I can't help you with that because I never needed to use but it shouldn't be to hard to do or figure out.
As far as wich rom you want to use just try a few different ones and see wich one you prefer to use as a daily driver.
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
moodroid said:
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
Click to expand...
Click to collapse
Shplad said:
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
Click to expand...
Click to collapse
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
moodroid said:
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Click to expand...
Click to collapse
Shplad said:
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
Click to expand...
Click to collapse
As far as I understand it (which could be totally wrong), 11 and 12 are no longer being developed and will only receive security updates, so from that point of view, I guess they will be more stable. But 13 and 14 will work, but there may be the odd issue here and there (particularly with 14 which is still quite new). You'd have to have a quick scan through the comments to see if there's anything that's like to be a problem for you.
With reagrds to GSM, I should just try it and see if it works to begin with. If it doesn't, then download the patch, reboot, go into safestrap, install the zip then reboot.
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provides superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Wow, this is a lot to take in. Thanks. So, I don't quite understand the repercussions. Once I root, does that mean any ROM OS that boots is somewhat more vulnerable, cause it's like being logged on as root in Linux, or does it depend which ROM I'm using or something else?
Bobcus Leper said:
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provided superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Click to expand...
Click to collapse
Okay, I figured out after my last post that root status depends on which ROM you are running, and of course installing a ROM without root status would put you back to unrooted status.
I downloaded Lineage OS 13 and verified the MD5SUM. I rooted the phone using Shadow's video.
Now I want to make an image of my NAND or have some other method of restoring the stock ROM before I install a new ROM. At what stage in the process do I do that and what is the safest tool / method to do that? RSDLite? Adding another ROM slot and using Nandroid backup?
Awaiting anxiously...
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Shplad said:
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Click to expand...
Click to collapse
As far as I understand it, and again, this could be wrong, using RSDLite is usually a last resort in the unlikely event that you've completely messed up your phone. You will lose everything, and your phone will back to how it was when you bought it. I've never needed to use RSDLite myself, but from what I've read, it's a pretty reliable way to get your phone working again. As long as you follow all the instructions, and install CM (LOS) 13 into another slot, it's very unlikely that you'll damage your original stock rom and you'll still be able to boot into if ever you need to. Hopefully, someone who knows more about it will comment also...
I got Safestrap 3.75 special version for unused partitions installed. I didn't realize it allows you to make TWRP ROM backups.
I made a backup of the stock ROM. The first time I did that, I got an error stating it couldn't find or access /boot.
Strangely, the second time I tried, it seemed to work fine.
I copied the folder with the stock ROM backup to my PC, just in case. I managed to flash with Lineage OS 13. It booted fine, but I forgot to select the Gapps zip as well. It does not appear to be rooted after bootup.
1. Do I need to reinstall Lineage 13 or is there way to install the apps without reinstalling Lineage?
2. What is the normal state of this ROM? I'm not sure if I have to root Lineage 13. If I don't enable root, will I be unable to run TWRP recovery and add the Gapps zip file and reinstall? I don't want to be stuck with a successful Lineage install and no apps. I'd find another way to install the apps, but I'm guessing you can't without the apps themselves, no?
Help!
Okay, I figured out how to install just gapps 5.1-2015-05-23-24 . However, during configuration, I cannot get the phone to connect to gmail via WiFi (I don't have a data plan).
"Validating Server Settings...
Couldn't open connection to server."
I see other people had this in other version of Android. Is this a particular problem in Lineage 13? Any solutions known?
...AAAANDDD Google Play Services has closed.
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
EDIT:
I tried these suggestions, just in case.
https://productforums.google.com/forum/#!topic/gmail/ACSvDiQoufI
Now, I'm getting the error:
"Problem with account setup
Username or password is incorrect"
Google Play Services keeps closing. Should I uninstall the gapps and install a more compatible one? I think network connectivity is not stable.
Shplad said:
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
Click to expand...
Click to collapse
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
moodroid said:
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
Click to expand...
Click to collapse
Shplad said:
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
Click to expand...
Click to collapse
I meant on this website. In the 'Droid 4 Android Development' section (https://forum.xda-developers.com/droid-4/development), there a thread for each of the roms. The one for CM (LOS) 13 is https://forum.xda-developers.com/droid-4/development/cm13-0-marshmallow-unofficial-builds-t3270938
moo:
Thanks for that. I didn't post there earlier because I thought it was only for developer reports of bugs, and my coding skills are exactly zero. Should I wait to see what happens in that other thread and not post back here until I hear something from there?