I apologize in advance if this question has already been asked but I was just wondering if it were possible to completely wipe the gs4 to stock like it come straight from Samsung and load your own kernels and roms. Or even load a dev edition or Google play edition load out so that the phone could be customizable. I mean isn't that all vzw does anyway is take the Samsung and Google packages add there own twist and apps to it and lock it down.? Sorry if this seems like a waist of time but it's just a question I keep asking myself but don't have the know how to test it for myself. Any input or further ideas would be appreciated.
cnall09 said:
I apologize in advance if this question has already been asked but I was just wondering if it were possible to completely wipe the gs4 to stock like it come straight from Samsung and load your own kernels and roms. Or even load a dev edition or Google play edition load out so that the phone could be customizable. I mean isn't that all vzw does anyway is take the Samsung and Google packages add there own twist and apps to it and lock it down.? Sorry if this seems like a waist of time but it's just a question I keep asking myself but don't have the know how to test it for myself. Any input or further ideas would be appreciated.
Click to expand...
Click to collapse
Here.. http://forum.xda-developers.com/showthread.php?t=2606501
Take some time and read through what's on that thread.
To answer your question though, unless your S4 is an MDK build or a Developer Edition you aren't going to be able to have a true custom recovery that allows for AOSP ROMs or custom kernels.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Here.. http://forum.xda-developers.com/showthread.php?t=2606501
Take some time and read through what's on that thread.
To answer your question though, unless your S4 is an MDK build or a Developer Edition you aren't going to be able to have a true custom recovery that allows for AOSP ROMs or custom kernels.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
cnall09 said:
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
Click to expand...
Click to collapse
Ohh OK gotcha! Hey to me that sounds like a great plan lol just I'm in way over my head when it comes to fully understanding what's needed to make something like that really happen.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Ohh OK gotcha! Hey to me that sounds like a great plan lol just I'm in way over my head when it comes to fully understanding what's needed to make something like that really happen.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
You and me both buddy. But hopefully someone with the know how will see this and give it a try. Who knows it could be the answer we have all been waiting for.
cnall09 said:
I have read through many many forums hoping someone has found away to bypass the bootloader and nothing so far. Im not asking if i can revert it to an early kernel. I merely suggested to take the s4 and revert it to basically it's shell and find the packages that come for the dev edition or google play edition and load it up. That doesn't sound to crazy does it?
Click to expand...
Click to collapse
You can't just revert to the original Google-supplied Android files as that operating system shell doesn't have drivers for the specific hardware devices in your phone - it has to be modified to add drivers for the screen, radio, cameras, touchpad, and so forth. That's files provided in the Kernel, so in the end you're asking to revert to an earlier kernel.
You can't install a Google Edition ROM image without customizing it for the specific phone, which is what some people have done. That is, to take the stock ROM and replace bits with those from the GE phone to try to get closer to the original; however, you can't go very far with this without having to change the kernel to make it compatible with GE, so you're stuck.
It's not a horrible situation as we can still use Safestrap to boot a custom ROM as long as it's compatible with the touchwiz kernel. If we could replace that kernel, we'd be able to run a lot more ROMs, but since the locked bootloader will reject a non-Samsung kernel, we're stuck.
k1mu said:
You can't just revert to the original Google-supplied Android files as that operating sysm shell doesn't have drivers for the specific hardware devices in your phone - it has to be modified to add drivers for the screen, radio, cameras, touchpad, and so forth. That's files provided in the Kernel, so in the end you're asking to revert to an earlier kernel.
You can't install a Google Edition ROM image without customizing it for the specific phone, which is what some people have done. That is, to take the stock ROM and replace bits with those from the GE phone to try to get closer to the original; however, you can't go very far with this without having to change the kernel to make it compatible with GE, so you're stuck.
It's not a horrible situation as we can still use Safestrap to boot a custom ROM as long as it's compatible with the touchwiz kernel. If we could replace that kernel, we'd be able to run a lot more ROMs, but since the locked bootloader will reject a non-Samsung kernel, we're stuck.
Click to expand...
Click to collapse
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
Short answer - no, you can't do that...it doesn't work that way. Depending on the bootloader your phone came with you cannot downgrade. You can try erasing everything and starting over but that's one thing you cannot change.....your stuck.
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
Feel free to do what you want...but you may end up with a $600 door stop. ..
Sent from my SCH-I545 using XDA Premium 4 mobile app
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
You can totally do this, you can replace the kernel and everything. The phone won't boot, and you'd have a hard brick though. The problem isn't replacing the kernel, the problem is getting the phone to boot after doing so. Download mode operates through aboot, aboot has protections and conditions set that regulate what kernel and recovery partitions you can boot. If these are replaced with a "non-allowed" version the phone simply won't boot, in other words it would be hard-bricked at this point.
Sent from my SCH-I545 using XDA Premium 4 mobile app
cnall09 said:
I understand all of that. I am currently running hyper drive installed through safestrap but it still feels governed apposed to a Google rom. We are still stuck on 4.3 and everywhere else has a later version. I still don't understand why you can't completely erase the internals to reload with a different loadout. Isn't it the same phone regardless of where you get it rather it be samsung or verizon or google?whenever we download updates it installs new cameras and radios I'm not talking about reverting I'm talking about completely shipping the phone down to nothing but download mode and install new kernels drivers and software. Just like the developers at any of the companies do except we won't have to do any testing or development
Click to expand...
Click to collapse
"Shipping the phone down to nothing but download mode" - yes, you can wipe the internal ROM and strip it down to download mode.
Then you have a brick which runs just the downloader. OK, it's not quite dead, because you can flash stuff. But what can you flash?
OK, so you want to "install new kernels drivers and software". That's not always possible. You flash kernels and and software using the bootloader, but the bootloader won't allow you to flash a kernel that's not pre-approved by Samsung. If you're rooted, the rest of the phone storage can be overwritten with whatever custom software you want, but there's a hitch. You can install whatever software you want EXCEPT for the kernel. (If not rooted, you can't even do that without a custom recovery, which the bootloader won't allow.)
The software that you flash depends on the kernel to drive the hardware, so you can't flash base software that requires services that the stock kernel doesn't provide. This is why only certain ROMs are available for Safestrap - you can't flash CyanogenMod on a Safestrapped i545 because CM isn't compatible with the Touchwiz kernel. It's theoretically possible to modify CM to make it work with a TW kernel, but nobody has done that (unsurprising, as it would be a lot of work that would have to be repeated each CM release.)
The bootloader chain is the way Samsung enforces the restrictions on what you can and can't do with your phone. With a locked bootloader (like ours), you're very limited. Until the bootloader protections are breached, what you propose can't be done.
decaturbob said:
Feel free to do what you want...but you may end up with a $600 door stop. ..
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well thank you so much for your permission to do what I want I was so afraid you wouldn't approve. and I have geek squad protection with unlimited replacements and no deductable so it doesn't hurt my feelings in the least bit if things don't go as planned. I know i ain't as seasoned as some of yall on here but thats how things get done by asking questions and trial/error.
k1mu said:
"Shipping the phone down to nothing but download mode" - yes, you can wipe the internal ROM and strip it down to download mode.
Then you have a brick which runs just the downloader. OK, it's not quite dead, because you can flash stuff. But what can you flash?
OK, so you want to "install new kernels drivers and software". That's not always possible. You flash kernels and and software using the bootloader, but the bootloader won't allow you to flash a kernel that's not pre-approved by Samsung. If you're rooted, the rest of the phone storage can be overwritten with whatever custom software you want, but there's a hitch. You can install whatever software you want EXCEPT for the kernel. (If not rooted, you can't even do that without a custom recovery, which the bootloader won't allow.)
The software that you flash depends on the kernel to drive the hardware, so you can't flash base software that requires services that the stock kernel doesn't provide. This is why only certain ROMs are available for Safestrap - you can't flash CyanogenMod on a Safestrapped i545 because CM isn't compatible with the Touchwiz kernel. It's theoretically possible to modify CM to make it work with a TW kernel, but nobody has done that (unsurprising, as it would be a lot of work that would have to be repeated each CM release.)
The bootloader chain is the way Samsung enforces the restrictions on what you can and can't do with your phone. With a locked bootloader (like ours), you're very limited. Until the bootloader protections are breached, what you propose can't be done.
Click to expand...
Click to collapse
yes sir i did mean stripped down. sorry for the typo. and ok im not talking about stripping it down just to boot a custom rom or kernel. i want authentic samsung/google software and kernels. so the samsung wouldn't even accept its on software. I apologize for seeming argumentative thats not my intent at all. im just trying to get a good idea and handle on how some of this works. i appreciate your input and help on this matter and your patience.
cnall09 said:
yes sir i did mean stripped down. sorry for the typo. and ok im not talking about stripping it down just to boot a custom rom or kernel. i want authentic samsung/google software and kernels. so the samsung wouldn't even accept its on software. I apologize for seeming argumentative thats not my intent at all. im just trying to get a good idea and handle on how some of this works. i appreciate your input and help on this matter and your patience.
Click to expand...
Click to collapse
Yeah it's a good idea for someone like yourself who seems fairly new to this stuff, because what you're proposing is kind of what were trying to do to unlock the boot loader. The problem basically is that the very base software contains checks to make sure you're using Samsung approved software.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
joshm.1219 said:
Yeah it's a good idea for someone like yourself who seems fairly new to this stuff, because what you're proposing is kind of what were trying to do to unlock the boot loader. The problem basically is that the very base software contains checks to make sure you're using Samsung approved software.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i know how to permanently unlock it without bricking it. Hit it with a hammer smoke a whole lot n watch in amazement as the bootloader flies out of this phone, able to be replaced of course. Just kidding dont do that, although ive been tempted
cnall09 said:
well thank you so much for your permission to do what I want I was so afraid you wouldn't approve. and I have geek squad protection with unlimited replacements and no deductable so it doesn't hurt my feelings in the least bit if things don't go as planned. I know i ain't as seasoned as some of yall on here but thats how things get done by asking questions and trial/error.
Click to expand...
Click to collapse
reading helps too my friend....also I wouldn't jump to the conclusion that geek squad warranty coverage applies to the the misuse or negligent use of a product....you best read the fine print again.
any way good luck
Dear Friends,
I am a US consumer. About to buy a Verizon LG G3. My number # 1 priority in a phone is, more of less development support for a phone. Number of ROMs being developed, how many choices, mods, frequent updates, and etc.
Clearly, the International version D855 is the King. Number 2 is probably D851, the T-Mobile US Variant with the Unlocked bootloader. International versions are expensive and hard to find in America and it's more or less the same for the T-Mobile version.
I browsed the Development section for all G3 variants on XDA, and surprisingly, the number 3 variant is the Verizon, US Model! Which is fine by me, because it can be unlocked and used on AT&T and I am moving to Verizon soon, for the better coverage and LTE speeds.
I am lined up to pull the trigger on buying the Verizon G3, as we speak, but I need some help confirmation from you guys:
1. Is it true, that with the BUMP'd/TWRP recovery, the Verizon G3 is as good as the Unlocked bootloader models, like D851 and D855? If not, what is the difference, disadvantage?
2. How would you rate the Development support for the Verizon variant of the LG G3?
Thank you for your help! I have the seller lined up, please respond as soon as you can, I would really appreciate it!
ProFragger said:
Dear Friends,
I am a US consumer. About to buy a Verizon LG G3. My number # 1 priority in a phone is, more of less development support for a phone. Number of ROMs being developed, how many choices, mods, frequent updates, and etc.
Clearly, the International version D855 is the King. Number 2 is probably D851, the T-Mobile US Variant with the Unlocked bootloader. International versions are expensive and hard to find in America and it's more or less the same for the T-Mobile version.
I browsed the Development section for all G3 variants on XDA, and surprisingly, the number 3 variant is the Verizon, US Model! Which is fine by me, because it can be unlocked and used on AT&T and I am moving to Verizon soon, for the better coverage and LTE speeds.
I am lined up to pull the trigger on buying the Verizon G3, as we speak, but I need some help confirmation from you guys:
1. Is it true, that with the BUMP'd/TWRP recovery, the Verizon G3 is as good as the Unlocked bootloader models, like D851 and D855? If not, what is the difference, disadvantage?
2. How would you rate the Development support for the Verizon variant of the LG G3?
Thank you for your help! I have the seller lined up, please respond as soon as you can, I would really appreciate it!
Click to expand...
Click to collapse
Having the bump'd twrp is basically the same thing. No matter which way you get to a custom recovery it's all the same. In my opinion its a great phone to have and pretty hard to screw something up. Sky Dragon and Jasmine are my personal favorites as far as Stock roms go. Unless you want to wait for the G4 i would go ahead and pull the trigger. You won't be disappointed.
Edde3d said:
Having the bump'd twrp is basically the same thing. No matter which way you get to a custom recovery it's all the same. In my opinion its a great phone to have and pretty hard to screw something up. Sky Dragon and Jasmine are my personal favorites as far as Stock roms go. Unless you want to wait for the G4 i would go ahead and pull the trigger. You won't be disappointed.
Click to expand...
Click to collapse
This is excellent news bud, thank you! What tripped me up was the fact that the T-Mobile version is so much more expensive... Why exactly ?
One question for you, how would you rate the development support for the Verizon variant? And yes, I'm more interested in CM12 kind of ROMs.
Lastly, if the seller has OTA'd to Lollipop, can I somehow bring it back to the KK firmware in I want that?
Thanks so much for your help again!
ProFragger said:
This is excellent news bud, thank you! What tripped me up was the fact that the T-Mobile version is so much more expensive... Why exactly ?
Click to expand...
Click to collapse
Must be that Qi charging antenna sticker... The VZW comes with only the NFC installed, but it is easy and cheap to upgrade.
ProFragger said:
One question for you, how would you rate the development support for the Verizon variant? And yes, I'm more interested in CM12 kind of ROMs.
Click to expand...
Click to collapse
I have to say that it is pretty excellent. Lots of support just for the VZW variant on the AOSP side and many of the goodies from the main LG G3 thread are also applicable. I find the best phones for hacking up are the ones available on most of the US carriers.
ProFragger said:
Lastly, if the seller has OTA'd to Lollipop, can I somehow bring it back to the KK firmware in I want that?
Click to expand...
Click to collapse
Easiest way would be to flash a KK stock-based ROM. That way, you go bloat-free, get fixes, and stop the OTA if you're freezing on KK.
epidenimus said:
Must be that Qi charging antenna sticker... The VZW comes with only the NFC installed, but it is easy and cheap to upgrade.
I have to say that it is pretty excellent. Lots of support just for the VZW variant on the AOSP side and many of the goodies from the main LG G3 thread are also applicable. I find the best phones for hacking up are the ones available on most of the US carriers.
Easiest way would be to flash a KK stock-based ROM. That way, you go bloat-free, get fixes, and stop the OTA if you're freezing on KK.
Click to expand...
Click to collapse
Thanks for the response, bud. Wireless charging really hasn't been a factor me, so far, so it's a non-issue. Good to hear of the VZW Dev support, although I'd have to say it's probably because someone found a way to "bump" or install Custom Recovery on a locked Bootloader, which is every phone on Verizon ! Too bad, because these LTE phones are factory unlocked for Global use, but so crippled, thanks to the bootloader non-sense. I wish the exploit extended to the Note lines or even HTC phones.
This is one reason why we see most of the T-Mobile variants selling like hot cakes, even though Sprint has that as well, the supported GSM functionality and bands are just not there.
I assume doing a simple Stock ROM flash via the LG Flash Tools, or "KDZ" is the way to get back to KK, if wanted? No downgrade issues like Notes, correct? Apparently, you can't downgrade the bootloader on those once moved to LP ...
ProFragger said:
Thanks for the response, bud. Wireless charging really hasn't been a factor me, so far, so it's a non-issue. Good to hear of the VZW Dev support, although I'd have to say it's probably because someone found a way to "bump" or install Custom Recovery on a locked Bootloader, which is every phone on Verizon ! Too bad, because these LTE phones are factory unlocked for Global use, but so crippled, thanks to the bootloader non-sense. I wish the exploit extended to the Note lines or even HTC phones.
This is one reason why we see most of the T-Mobile variants selling like hot cakes, even though Sprint has that as well, the supported GSM functionality and bands are just not there.
I assume doing a simple Stock ROM flash via the LG Flash Tools, or "KDZ" is the way to get back to KK, if wanted? No downgrade issues like Notes, correct? Apparently, you can't downgrade the bootloader on those once moved to LP ...
Click to expand...
Click to collapse
Yes, you can either use the "kdz", or " tot" methods of restoring back to software version 10B (the initial stock software that is easily rootable/unlockable using stump and bump). I personally prefer the tot method, but that probably because I've got a Win 7 computer ( Win 8 has apparently caused some issues for some using the tot method), and its the first method that came out that I used so just stuck with it, but either would work great. And no, no downgrade nonsense or risk of bricks, regardless of firmware it comes on (at least as of this writing lol)
ohlin5 said:
Yes, you can either use the "kdz", or " tot" methods of restoring back to software version 10B (the initial stock software that is easily rootable/unlockable using stump and bump). I personally prefer the tot method, but that probably because I've got a Win 7 computer ( Win 8 has apparently caused some issues for some using the tot method), and its the first method that came out that I used so just stuck with it, but either would work great. And no, no downgrade nonsense or risk of bricks, regardless of firmware it comes on (at least as of this writing lol)
Click to expand...
Click to collapse
This is excellent news and response, bud, thanks! Although, from a little bit of reading around here, I have heard of at least a few instances of people restoring stock firmware and in the process, somehow magically clearing out their IMEI to 0 !!! Is this actually true and a common occurrence? I heard their is a process to correct is via QPST, but it is arduous.
I wish someone did a video of Root + TWRP from starting to end for the LG G3 (Verizon version). Seeing how this will be my first LG phone, terms still confuse me, like Root method names, what exactly does "stump" or "bump" mean, and yeah, getting TWRP on there.
There is also a one-click TWRP installer for the VZW G3 on the Playstore? Is that true? Is that the same as having Bumped TWRP? Thanks!
ProFragger said:
This is excellent news and response, bud, thanks! Although, from a little bit of reading around here, I have heard of at least a few instances of people restoring stock firmware and in the process, somehow magically clearing out their IMEI to 0 !!! Is this actually true and a common occurrence? I heard their is a process to correct is via QPST, but it is arduous.
I wish someone did a video of Root + TWRP from starting to end for the LG G3 (Verizon version). Seeing how this will be my first LG phone, terms still confuse me, like Root method names, what exactly does "stump" or "bump" mean, and yeah, getting TWRP on there.
There is also a one-click TWRP installer for the VZW G3 on the Playstore? Is that true? Is that the same as having Bumped TWRP? Thanks!
Click to expand...
Click to collapse
I can't speak to the IMEI clearing as being a "common" issue....I've restored at least 5 different phones using the tot method, several multiple times and never once had an issue. I do, however, maintain a backup in the cloud of the EFS partition (same basic thing I think? I just know it's an important partition lol) for every phone I oversee and have messed with.
As for your question about stump/bump/etc., there are several different root methods out now...."Stump root" was just the name of the first - and so it's what I've always stuck with. "Bump", on the other hand, is the method for "unlocking" the bootloader and flashing TWRP.
As for the play store 'auto' app, I hadn't even heard of it until you said something and I searched. I'm assuming you're talking about this. All I can say is that I've never used it so I have no idea. Below I've laid out the steps that I, personally, follow each and every time I've gotten a new device or restored one. I realize there may be simpler ways out there now, but I've been in this specific community since the very beginning, and so I've just stuck with the "tried and true" stuff that came out first.
As for the one click TWRP installer on the play store, again I don't know. However, flashing the "bumped" TWRP via flashify is probably the easiest way to do it (it is not officially stated by the devs to work, but countless people including myself numerous times have confirmed it does).
So, TLDR:
If I were to get a brand new, VS985 today, here is the exact set of steps I would follow (I just got another one 2 weeks ago and these are what I did, and have always done):
1). Use the tot method, found here to restore (downgrade) back to the initial stock release software (version 10B_03). Alternatively, you can use the "kdz" method found here, but on my Windows 7 PC the tot method has always worked like a charm and the one time I used the kdz method it seemed a bit sketchier, but to each their own. I think the main "push" for the kdz method was that some people were having trouble getting the tot method to work on computers w/ Windows 8/8.1.
2). Once that's done, reboot and do minimal setup, then use stump root (found here) to root. Follow the directions exactly, and as long as you're on 10B it will still work - it's just been patched in newer software versions. After rooting and rebooting, then install superSU from the play store, open that, update the binary via "normal" method and then reboot once more. After that reboot, uninstall the stump app, you don't need it anymore.
3). Then, install Flashify from the play store. To be safe, I usually open it and make sure I've granted root, then close it and open superSU and make sure it's got the green mark next to it signifying it has full root access (again, just to be sure). Then, download the "bumped" TWRP image from here, and put it somewhere you can find it on your INTERNAL storage (not sure if this is vital, but again, just being safe). Also, for later, download the zip of TWRP 2.8.6.1 from here
4). Use the Flashify file browser to flash that recovery image you just downloaded to the your internal storage. Let it do it's thing, then reboot when it prompts you.
5). You should now boot up into TWRP. Use the install function to update from the TWRP you just flashed (2.8.0.0) to the 2.8.6.1 zip you just downloaded. Then use reboot>recovery to confirm it took.
6). That's pretty much it. With that you're fully rooted + unlocked. Only other thing I would highly recommend at this point is following the guide here to back up your EFS partition, and then store it to your Google drive or dropbox or other cloud storage or somewhere safe lol. If you're gonna stay stock I'd freeze the system update apps, or better use just flash skydragon or jasmine roms as they're great stock-based roms.
Any other questions just let me know.
ohlin5 said:
I can't speak to the IMEI clearing as being a "common" issue....I've restored at least 5 different phones using the tot method, several multiple times and never once had an issue. I do, however, maintain a backup in the cloud of the EFS partition (same basic thing I think? I just know it's an important partition lol) for every phone I oversee and have messed with.
As for your question about stump/bump/etc., there are several different root methods out now...."Stump root" was just the name of the first - and so it's what I've always stuck with. "Bump", on the other hand, is the method for "unlocking" the bootloader and flashing TWRP.
As for the play store 'auto' app, I hadn't even heard of it until you said something and I searched. I'm assuming you're talking about this. All I can say is that I've never used it so I have no idea. Below I've laid out the steps that I, personally, follow each and every time I've gotten a new device or restored one. I realize there may be simpler ways out there now, but I've been in this specific community since the very beginning, and so I've just stuck with the "tried and true" stuff that came out first.
As for the one click TWRP installer on the play store, again I don't know. However, flashing the "bumped" TWRP via flashify is probably the easiest way to do it (it is not officially stated by the devs to work, but countless people including myself numerous times have confirmed it does).
So, TLDR:
If I were to get a brand new, VS985 today, here is the exact set of steps I would follow (I just got another one 2 weeks ago and these are what I did, and have always done):
1). Use the tot method, found here to restore (downgrade) back to the initial stock release software (version 10B_03). Alternatively, you can use the "kdz" method found here, but on my Windows 7 PC the tot method has always worked like a charm and the one time I used the kdz method it seemed a bit sketchier, but to each their own. I think the main "push" for the kdz method was that some people were having trouble getting the tot method to work on computers w/ Windows 8/8.1.
2). Once that's done, reboot and do minimal setup, then use stump root (found here) to root. Follow the directions exactly, and as long as you're on 10B it will still work - it's just been patched in newer software versions. After rooting and rebooting, then install superSU from the play store, open that, update the binary via "normal" method and then reboot once more. After that reboot, uninstall the stump app, you don't need it anymore.
3). Then, install Flashify from the play store. To be safe, I usually open it and make sure I've granted root, then close it and open superSU and make sure it's got the green mark next to it signifying it has full root access (again, just to be sure). Then, download the "bumped" TWRP image from here, and put it somewhere you can find it on your INTERNAL storage (not sure if this is vital, but again, just being safe). Also, for later, download the zip of TWRP 2.8.6.1 from here
4). Use the Flashify file browser to flash that recovery image you just downloaded to the your internal storage. Let it do it's thing, then reboot when it prompts you.
5). You should now boot up into TWRP. Use the install function to update from the TWRP you just flashed (2.8.0.0) to the 2.8.6.1 zip you just downloaded. Then use reboot>recovery to confirm it took.
6). That's pretty much it. With that you're fully rooted + unlocked. Only other thing I would highly recommend at this point is following the guide here to back up your EFS partition, and then store it to your Google drive or dropbox or other cloud storage or somewhere safe lol. If you're gonna stay stock I'd freeze the system update apps, or better use just flash skydragon or jasmine roms as they're great stock-based roms.
Any other questions just let me know.
Click to expand...
Click to collapse
Hey bud,
This is probably the BEST post I have EVER been a recipient of at XDA. And trust me, I have been here since almost 2008! So please accept my deepest gratitude, so detailed, and so patient, really excellent job and excellent member of the community!
I ordered my phone, it is used, so not sure what build it will have, but if it took the OTA, then likely, it's LP and I would have to downgrade to 10b, like you said and then use Stump to Root. Problem is, since we can't backup EFS without Root, or TWRP, rather, it is making me nervous to use the TOT method first, which as I mentioned earlier, I have read, people blowing their IMEIs like that before ...
With that said, I think you have laid everything out nicely for me, just a matter of getting the phone, sitting down, and getting through the process . What would make it easier, is a Rooting method without the downgrade, but that's just me being really nit picky .
The other thought lingering in my head... since this my first LG, do I enjoy a Optimus UI ROM for a bit or go straight for the no nonsense CM12 or 12.1? Do you guys have the non working NFC on CM ROMs as well or other bugs that are common like that? I heard the LG G3 stock ROM got super laggy and heats the phone up!
ProFragger said:
Hey bud,
This is probably the BEST post I have EVER been a recipient of at XDA. And trust me, I have been here since almost 2008! So please accept my deepest gratitude, so detailed, and so patient, really excellent job and excellent member of the community!
I ordered my phone, it is used, so not sure what build it will have, but if it took the OTA, then likely, it's LP and I would have to downgrade to 10b, like you said and then use Stump to Root. Problem is, since we can't backup EFS without Root, or TWRP, rather, it is making me nervous to use the TOT method first, which as I mentioned earlier, I have read, people blowing their IMEIs like that before ...
With that said, I think you have laid everything out nicely for me, just a matter of getting the phone, sitting down, and getting through the process . What would make it easier, is a Rooting method without the downgrade, but that's just me being really nit picky .
The other thought lingering in my head... since this my first LG, do I enjoy a Optimus UI ROM for a bit or go straight for the no nonsense CM12 or 12.1? Do you guys have the non working NFC on CM ROMs as well or other bugs that are common like that? I heard the LG G3 stock ROM got super laggy and heats the phone up!
Click to expand...
Click to collapse
Thanks for the compliment What can I say, I've just seen too many crap-tastic tutorials
I understand your concern about the whole imei thing, I'd be the same way had I not done it so many times. Could you link the places where you've seen people wiping out their imeis supposedly? Also, if you're willing to do a little reading, something along these lines MIGHT work just to obtain root while still on STOCK LP (which I'd what I'm assuming it would come on:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
If you do go this route and try to root while still on stock and before downgrading so that you can backup the efs partition, then be sure to NOT install twrp unless you do a bunch of reading beforehand as I believe it is the aboot that changed on LP and if you try to flash the twrp images I posted while on stock LP you'll get secure boot errors and have a heck of a mess. IMHO, better to either bite the bullet and do the downgrade straight (as I haven't seen these imei wipes you're noting and I've done several myself with zero issues), OR try and root stock LP, then backup the EFS partition, and THEN downgrade through the steps I posted.
Either way, with the Roms, its pretty much same as normal. I never recommend full stock, as if you're gonna root and unlock, you might as well use it IMHO. Stock is good if your most important things are stability and (at least currently and in my experience) battery life, while aosp based is better if you like the cleaner look, and most customizability. Either way you'll be OK. If you go for stock LG, I'd recommend either jasmine ROM or skydragon ROM. I've used skydragon ROM for a bit and its great if you love stock. I'm more of an aosp guy and so I currently use CM 12.1 and its easily DD stable for me, but not without it's quirks - sometimes the screen double tap to wake doesn't work or screen doesn't come on post-call, sometimes the battery life ain't great, sometimes it runs hot, etc. but all typically good enough for reasonable DD stability. I've started using 777kernel on top of the CM 12.1 flash and the device seems to run a bit cooler.
ohlin5 said:
Thanks for the compliment What can I say, I've just seen too many crap-tastic tutorials
I understand your concern about the whole imei thing, I'd be the same way had I not done it so many times. Could you link the places where you've seen people wiping out their imeis supposedly? Also, if you're willing to do a little reading, something along these lines MIGHT work just to obtain root while still on STOCK LP (which I'd what I'm assuming it would come on:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
If you do go this route and try to root while still on stock and before downgrading so that you can backup the efs partition, then be sure to NOT install twrp unless you do a bunch of reading beforehand as I believe it is the aboot that changed on LP and if you try to flash the twrp images I posted while on stock LP you'll get secure boot errors and have a heck of a mess. IMHO, better to either bite the bullet and do the downgrade straight (as I haven't seen these imei wipes you're noting and I've done several myself with zero issues), OR try and root stock LP, then backup the EFS partition, and THEN downgrade through the steps I posted.
Either way, with the Roms, its pretty much same as normal. I never recommend full stock, as if you're gonna root and unlock, you might as well use it IMHO. Stock is good if your most important things are stability and (at least currently and in my experience) battery life, while aosp based is better if you like the cleaner look, and most customizability. Either way you'll be OK. If you go for stock LG, I'd recommend either jasmine ROM or skydragon ROM. I've used skydragon ROM for a bit and its great if you love stock. I'm more of an aosp guy and so I currently use CM 12.1 and its easily DD stable for me, but not without it's quirks - sometimes the screen double tap to wake doesn't work or screen doesn't come on post-call, sometimes the battery life ain't great, sometimes it runs hot, etc. but all typically good enough for reasonable DD stability. I've started using 777kernel on top of the CM 12.1 flash and the device seems to run a bit cooler.
Click to expand...
Click to collapse
Forgive the late response bud, the compliments are well deserved, trust me !
Here's an example of a gentleman losing his IMEI via TOT: http://forum.xda-developers.com/verizon-lg-g3/help/restore-via-tot-wipe-imei-t3033445
Let's hope it's the abnormal and not so normal .
I think let me get the phone I will keep, and will figure it out how to Root and Bump it. This phone I have to return, the item was not as described, but incidentally, came with Android 4.4.2! I imagine a simple Stump and Bump would have worked like a charm here?
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about.. like the Phone Muting and Speaker options in the Notification bar, while on a call. Can you believe, I couldn't even find a replacement app/dialer that could do that on AOSP ROM !?
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Thanks again bud!
ProFragger said:
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about..
Click to expand...
Click to collapse
The stock camera is surely missed, but the screen clarity is still amazing, the removable battery is sizeable, the sound is decent (no boom sound though), and you can slap an external SD card in it for more fun. The real appeal of this is that the hardware setup is pretty awesome for running and testing custom software. The LG stock ROM is really lackluster; a good AOSP ROM makes far better use of it.
ProFragger said:
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Click to expand...
Click to collapse
Yes, all of this works fine in the 12.1 ROMs I have tested out. You get knock-on and knock-off at the status bar. Quick Remote has been ported and works great. Most things that you might use Xposed to do are integrated in a good AOSP/CM based ROM already. I have not seen a need to install it on AOSP, just stock.
ProFragger said:
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Click to expand...
Click to collapse
If the dev baked the feature in, the kernel that comes with it should work.
Just my two cents. I hope it helps!
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
ProFragger said:
Forgive the late response bud, the compliments are well deserved, trust me !
Here's an example of a gentleman losing his IMEI via TOT: http://forum.xda-developers.com/verizon-lg-g3/help/restore-via-tot-wipe-imei-t3033445
Let's hope it's the abnormal and not so normal .
I think let me get the phone I will keep, and will figure it out how to Root and Bump it. This phone I have to return, the item was not as described, but incidentally, came with Android 4.4.2! I imagine a simple Stump and Bump would have worked like a charm here?
In the end, playing with Optimus UI/LG UI, I couldn't find anything really that would make me stay with it. Outside of the camera app, 4K recording, and some minor features which I love, but no one else cares about.. like the Phone Muting and Speaker options in the Notification bar, while on a call. Can you believe, I couldn't even find a replacement app/dialer that could do that on AOSP ROM !?
Since you are a CM12.1 user, can I ask you what works on it and doesn't? NFC? Bluetooth? Knock-on, but NOT Knock Code, correct? IR Blaster? And have you had much luck with Xposed?
Please let me know your thoughts and input? Also, for CM12/12.1, do I need a special kernel for Knock on (and Knock Code) to work? If so, which one?
Thanks again bud!
Click to expand...
Click to collapse
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
ohlin5 said:
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
Click to expand...
Click to collapse
That would be me.
Yup, the second time around it worked just fine when I flashed back to 10b so I could then take the LP OTA. Of course, now we know that you can use the 12b image to flash back to official KK to take the OTA, or you can now flash the official 23C image that's out there and one-click root it.
Glad my post has been of use. I definitely wanted to share my experience so that others who experience the same issue can then get it rectified.
epidenimus said:
The stock camera is surely missed, but the screen clarity is still amazing, the removable battery is sizeable, the sound is decent (no boom sound though), and you can slap an external SD card in it for more fun. The real appeal of this is that the hardware setup is pretty awesome for running and testing custom software. The LG stock ROM is really lackluster; a good AOSP ROM makes far better use of it.
Yes, all of this works fine in the 12.1 ROMs I have tested out. You get knock-on and knock-off at the status bar. Quick Remote has been ported and works great. Most things that you might use Xposed to do are integrated in a good AOSP/CM based ROM already. I have not seen a need to install it on AOSP, just stock.
If the dev baked the feature in, the kernel that comes with it should work.
Just my two cents. I hope it helps!
Click to expand...
Click to collapse
ohlin5 said:
Pretty much what he said ^^^
---------- Post added at 01:02 AM ---------- Previous post was at 12:58 AM ----------
See the other guys post, does a pretty fair overview. And thanks for that link....I mean it does show it can happen I guess, although I did also note the OP said in his last response that the 2nd time he toted he didn't have the issue, so he thinks maybe he screwed something up the first time....who knows lol
Click to expand...
Click to collapse
iBolski said:
That would be me.
Yup, the second time around it worked just fine when I flashed back to 10b so I could then take the LP OTA. Of course, now we know that you can use the 12b image to flash back to official KK to take the OTA, or you can now flash the official 23C image that's out there and one-click root it.
Glad my post has been of use. I definitely wanted to share my experience so that others who experience the same issue can then get it rectified.
Click to expand...
Click to collapse
Guys,
I wanted to follow up/close the loop on this thread and thank you guys once again for all your help! I received 12B on my phone, was downloading materials to TOT down to 10B to root with stump, till I found this:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Worked like a charm, and can save others an hour or two, downloading the stock firmware and etc.
Now I am Rooted, TWRP'd 2.6.8.1, is it?, and efs backedup as well!
This is my first LG ever, so I will use stock ROM on it for a few weeks. It is unbelievable how LITTLE stock ROM support is, compared to the CM stuff, across the board for the G3. Maybe your experience is different, but that is what I have found. For every 5 aosp builds there is one stock ROM. And the Verizon variant is no different, only Jasmin and skydragon available. Please do correct me if I am wrong, and there are more ROMs out there to try? I still can't believe the lack of stock ROMs considering how crucial the camera is on this phone!
Between the sd and Jasmine, I think I will start out sd. Yes Jasmine is smaller and also updated later?, but also a little too complicated to install with separate Zips and stuff. What o you guys think?
Finally, if I go the aosp route, which likely I will in a few weeks, which one do you recommend for best features, updates, and performance/battery life?
Lastly, and possibly the most important question... What camera are you using on your CM ROMs ? I found that Lenovo was the best on my Note 3, best features and quality. Although a battery drain, no 4K, or HDR, and Panorama ... What do you guys think?
Thank you again guys for ALL your help!
ProFragger said:
Guys,
I wanted to follow up/close the loop on this thread and thank you guys once again for all your help! I received 12B on my phone, was downloading materials to TOT down to 10B to root with stump, till I found this:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Worked like a charm, and can save others an hour or two, downloading the stock firmware and etc.
Now I am Rooted, TWRP'd 2.6.8.1, is it?, and efs backedup as well!
This is my first LG ever, so I will use stock ROM on it for a few weeks. It is unbelievable how LITTLE stock ROM support is, compared to the CM stuff, across the board for the G3. Maybe your experience is different, but that is what I have found. For every 5 aosp builds there is one stock ROM. And the Verizon variant is no different, only Jasmin and skydragon available. Please do correct me if I am wrong, and there are more ROMs out there to try? I still can't believe the lack of stock ROMs considering how crucial the camera is on this phone!
Between the sd and Jasmine, I think I will start out sd. Yes Jasmine is smaller and also updated later?, but also a little too complicated to install with separate Zips and stuff. What o you guys think?
Finally, if I go the aosp route, which likely I will in a few weeks, which one do you recommend for best features, updates, and performance/battery life?
Lastly, and possibly the most important question... What camera are you using on your CM ROMs ? I found that Lenovo was the best on my Note 3, best features and quality. Although a battery drain, no 4K, or HDR, and Panorama ... What do you guys think?
Thank you again guys for ALL your help!
Click to expand...
Click to collapse
Nope, no other main stock based Roms for the G3....SD and Jasmine. If I were running stock I'd go SD with the custom kernel packaged with it. As for AOSP, people may disagree with me here, but I just sitck with CM. I like the idea of nightlies and being able to easily find updates from their websites and keep tabs on the progress updates merged, but that's just me. Recently I've been running CM with the 777 kernel, but only because the stock kernel seemed to be running very warm and draining battery a fair bit faster than usual. As for the camera, I again just stick with stock, as I find its good enough for me. I flashed several motorola, lenovo, etc. camera mods but it seemed like all too often it'd either be glitchy beyond measure or would break FFC in certain apps I knew to be otherwise working, etc. So I just started sticking with stock.
Random info:
I like focal (altho deprecated) it's in the play store. Lots of camera options.
If you do end up on some non stock roms, and have a dual band router, turn the channel on it to 11. It doesn't fix the wifi problems 100% but it may help.
Also there's plenty of g4 stuff floating around if you look for it.
Also you shouldn't have more than 0.25-0.5%/hr idle drain. If you do then somethings wrong. I'd install better battery stats right away and charge up to full and unplug before bed.
Amplify and greenify help but really the display is your battery culprit. I like cf lumen to help adjust the display from day to night usage.
ohlin5 said:
Nope, no other main stock based Roms for the G3....SD and Jasmine. If I were running stock I'd go SD with the custom kernel packaged with it. As for AOSP, people may disagree with me here, but I just sitck with CM. I like the idea of nightlies and being able to easily find updates from their websites and keep tabs on the progress updates merged, but that's just me. Recently I've been running CM with the 777 kernel, but only because the stock kernel seemed to be running very warm and draining battery a fair bit faster than usual. As for the camera, I again just stick with stock, as I find its good enough for me. I flashed several motorola, lenovo, etc. camera mods but it seemed like all too often it'd either be glitchy beyond measure or would break FFC in certain apps I knew to be otherwise working, etc. So I just started sticking with stock.
Click to expand...
Click to collapse
jfriend33 said:
Random info:
I like focal (altho deprecated) it's in the play store. Lots of camera options.
If you do end up on some non stock roms, and have a dual band router, turn the channel on it to 11. It doesn't fix the wifi problems 100% but it may help.
Also there's plenty of g4 stuff floating around if you look for it.
Also you shouldn't have more than 0.25-0.5%/hr idle drain. If you do then somethings wrong. I'd install better battery stats right away and charge up to full and unplug before bed.
Amplify and greenify help but really the display is your battery culprit. I like cf lumen to help adjust the display from day to night usage.
Click to expand...
Click to collapse
Guys, horrible day of flashing.
GPS issues with both SD and Jasmine. Tried both stock and SD kernels, as well as 12B and 23C radios, no dice :'(!
Resurrection Remix, not enough options for me and zero GPS locks :'(!
BlissPop came the closest. Bluetooth worked, Xposed, had the options I wanted, but GPS is still not strong enough indoors, and there is an issue WiFi not autoconnecting on each boot :'(!
Long story short, I think I need to head back to 12B somehow. Can anyone please tell me how? I will TOT to 10B, but then, how do I get to 12B? I can't find the image for it anywhere! Please do help, I need a reliable
working phone tomorrow, porting my number into a new carrier...
Thanks in advance!
Some people have to tot back to get gps working. For me, flashing sky always did the trick. Sometimes it takes longer or a reboot, and even setting gps to gps only (strange huh)?
Didn't u make a TWRP backup of working firmware?
I would seriously try flashing skydragon again. Why do u need gps indoors anyway?
Not sure about the tot but I think u can just take updates. Once u get to 10b please make a TWRP backup if you haven't already.
jfriend33 said:
Some people have to tot back to get gps working. For me, flashing sky always did the trick. Sometimes it takes longer or a reboot, and even setting gps to gps only (strange huh)?
Didn't u make a TWRP backup of working firmware?
I would seriously try flashing skydragon again. Why do u need gps indoors anyway?
Not sure about the tot but I think u can just take updates. Once u get to 10b please make a TWRP backup if you haven't already.
Click to expand...
Click to collapse
Thanks for the quick response bud. I will try SD again, maybe, but for now, I liked how Stock felt out of the box which was 12B. I feel like with rooting, manual debloating, and maybe the CPU thermals mods, I would have a snappy 4.2 device.
I'm stupid, I did not Nandroid the 12B I had . Thought it would be like Samsung, each firmware easily available for download on the Internet to flash via the LG Flash Tools.
I will TOT to 10B tomorrow, but then question is, how do I upgrade or OTA to 12B? Would it give me options on which update to take? Or will it take me to the latest, which is 23C?
Appreciate your help or if anyone can! Thank you!
Ok so at first it wouldn't let me in until I plugged it into a computer or a fancy USB outlet. And it wouldn't let me go T the home screen. Now it wont let me on at all, after the home screen suddenly swooped in and ate this post on my Apollo, thus ****ing it. So now I can't get in at all. And I just rooted after I suddenly got this update, the newish one, and I renamed ota and ota contracts on accident. Is that a problem? Please help me...
Leafen said:
Ok so at first it wouldn't let me in until I plugged it into a computer or a fancy USB outlet. And it wouldn't let me go T the home screen. Now it wont let me on at all, after the home screen suddenly swooped in and ate this post on my Apollo, thus ****ing it. So now I can't get in at all. And I just rooted after I suddenly got this update, the newish one, and I renamed ota and ota contracts on accident. Is that a problem? Please help me...
Click to expand...
Click to collapse
Renaming OTA contracts is a problem! Given device is rooted it may be fixable via ADB. Also possible you can go further and unlock bootloader which yields complete control to repair/replace FireOS. I am travelling today and can not immediately help with details. Will check back later (24 hours) to see if help is still needed.
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Leafen said:
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Click to expand...
Click to collapse
Bootloop further complicates matters. How much time passes before the device restarts? Does it ever make it to the login screen?
While there is still a glimmer of hope the situation is dire. Pretty good chance the device can not be recovered. I say that not to be negative but rather recognizing Apollo is not a cheap gadget. Amazon crippled native recovery capabilities making simple fixes impossible to apply. Akin to making tires a non replaceable item (brilliant). Just want to prepare you for an unpleasant outcome...
Davey126 said:
Bootloop further complicates matters. How much time passes before the device restarts? Does it ever make it to the login screen?
While there is still a glimmer of hope the situation is dire. Pretty good chance the device can not be recovered. I say that not to be negative but rather recognizing Apollo is not a cheap gadget. Amazon crippled native recovery capabilities making simple fixes impossible to apply. Akin to making tires a non replaceable item (brilliant). Just want to prepare you for an unpleasant outcome...
Click to expand...
Click to collapse
Oi. Uh. It's normal procedure up to the colored Kindle logo. Goes off the same amount of time as usual. And it never makes it to the put in your password screen. Not yet anyways.
Scratch that I'm in. Changing Ota contracts back
It worked. I'm able to get back in the home screen. But now I need safestrap again for the ROM I already have partitioned on this device.
Leafen said:
It worked. I'm able to get back in the home screen. But now I need safestrap again for the ROM I already have partitioned on this device.
Click to expand...
Click to collapse
Great! Assuming a factory reset did the trick (I didn't immediately suggest that course of action as it can sometimes make things worse; other things to try first).
If you install Safestrap v4 choice of ROMs is limited to Fire Nexus and CM11 - both KitKat based. Unlocking the bootloader opens the door to a wider selection of Lollipop and Marshmallow based ROMs. Unlocking is not risky but does require a bit of technical knowledge and some patience. An unlocked device is also easier to recover in the event of a ROM crash or bootloop.
Assuming you want to proceed with Safestrap download the app from here. Make sure you get the build appropriate for your device. Install/launch the app and then select the option that installs Safestrap recovery. Please note this is not a true recovery environment and has none of the special powers associated with TWRP. Its singular purpose it to support the two custom ROMs noted above on a locked device. Unlocked devices do not need to use Safestrap.
Once Safestrap recovery is installed reboot your device. After the grey Amazon logo you will be presented with a 'robot' screen where you can choose to continue booting into FireOS or enter Safestrap recovery mode. Choose the latter. After a few moments device will enter Safestrap recovery which emulates TWRP.
Do you know what to do from here?
Warning: Once Safestrap v4 recovery is installed you should NEVER perform a factory reset via the stock recovery menu. Doing so will brick the device.
Oh! Well. Id like to know about unlocking my boot whatever. Now Marshmallow and lollipop are Android 4. S.omething right? Oh um. Do you mind telling me how to do it, especially since I got jammed into the new update, breaking my safestrap I already had and leaving the slot out to dry? That would be appreciated!
Leafen said:
Oh! Well. Id like to know about unlocking my boot whatever. Now Marshmallow and lollipop are Android 4. S.omething right? Oh um. Do you mind telling me how to do it, especially since I got jammed into the new update, breaking my safestrap I already had and leaving the slot out to dry? That would be appreciated!
Click to expand...
Click to collapse
Well you got "jammed" into a FireOS update because Safestrap was improperly configured. Details matter. Suggest proceeding with reinstalling Safestrap and forget about unlocking the bootloader thingy. Do not create or attempt to use a secondary slot. Custom ROM overwrites FireOS in the stock slot. Lots of posts outlining Safestrap best practices that apparently were not read or ignored.
Bootloader unlock thread: http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
No the reason I was booted out was because i was having to be stuck on the FireOS because I have to have it for well.. Showing reasons. Don't worry about that. But Safestrap was done perfect, I had it going on for A long while. I successfully used two or more ROMs with perfect functionality.
Leafen said:
I successfully used two or more ROMs with perfect functionality.
Click to expand...
Click to collapse
If using multiple/secondary slots worked well enough for you, great!
Full functionality can not be achieved in secondary slots with Safestrap v4 which is an adaptation specific to this device and was never intended to support dual boot capability. Issues impacting ROMs operating in secondary slots:
- restricted BT/WiFi radio functionality (less of an issue w/CM11)
- only 2 of 4 CPU cores available (other two disabled)
- the two active cores run at 100% regardless of load
- device will not enter deep sleep when secondary slot is active
- poor performance and lousy battery life resulting from above
If you only use the secondary slot on occasion and radios work then it's obviously a personal call if the limitations are problematic.
Davey126 said:
If using multiple/secondary slots worked well enough for you, great!
Full functionality can not be achieved in secondary slots with Safestrap v4 which is an adaptation specific to this device and was never intended to support dual boot capability. Issues impacting ROMs operating in secondary slots:
- restricted BT/WiFi radio functionality (less of an issue w/CM11)
- only 2 of 4 CPU cores available (other two disabled)
- the two active cores run at 100% regardless of load
- device will not enter deep sleep when secondary slot is active
- poor performance and lousy battery life resulting from above
If you only use the secondary slot on occasion and radios work then it's obviously a personal call if the limitations are problematic.
Click to expand...
Click to collapse
I only had the battery thing. Otherwise I used my secondary rom pretty much all the time.
Leafen said:
I only had the battery thing. Otherwise I used my secondary rom pretty much all the time.
Click to expand...
Click to collapse
And ½ the CPUs disabled. So why not install the custom rom in the stock slot?
Davey126 said:
And ½ the CPUs disabled. So why not install the custom rom in the stock slot?
Click to expand...
Click to collapse
I have o keep up appearances pretty much. The reason why I dont really need to tell you. But its for appearences sake
Leafen said:
I have o keep up appearances pretty much. The reason why I dont really need to tell you. But its for appearences sake
Click to expand...
Click to collapse
Yep - I get it. Not specifics (obviously) but understand optics. As an aside unlocking the bootloader offers no significant benefit given your situation. Enjoy.
Davey126 said:
Yep - I get it. Not specifics (obviously) but understand optics. As an aside unlocking the bootloader offers no significant benefit given your situation. Enjoy.
Click to expand...
Click to collapse
Crap. Safestrap isnt working for this update. Dang. Gotta wait for ggow or someone to make it.
Leafen said:
Crap. Safestrap isnt working for this update. Dang. Gotta wait for ggow or someone to make it.
Click to expand...
Click to collapse
Must be on FireOS 4.5.2.0 or 4.5.5.1 to run Safestrap v4. Rollback/upgrade options are available but ugly. Pretty sure Safestrap won't be receiving any further updates now that the HDX bootloader can be unlocked on any rooted 3rd gen device.
Stock Pixel/Pixel XL Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.111
Suitable for build(s): August 2019
Suitable for devices(s): Pixel XL (marlin) | Pixel (sailfish)
I compiled the stock kernel for the Pixel/Pixel XL and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post. Older versions can be found HERE.
(shamelessly copied from Sakete's kernel for the Pixel/Pixel XL, which is no longer being maintained. Thanks for the inspiration, Sakete!)
Wow. I literally just compiled the patched kernel myself just now. What a ninja! While I'll be running my own, thanks for posting this so I didn't have to
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
iissmart said:
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
Click to expand...
Click to collapse
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Cardflip said:
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
Click to expand...
Click to collapse
Good catch, I didn't look that closely before recompiling but they are indeed the same. Oh well! Maybe I'll start going off of tag names instead of branches...
ipeedalil said:
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Click to expand...
Click to collapse
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
iissmart said:
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
Click to expand...
Click to collapse
I think he's asking for the patch itself to be a flashable zip so he can patch the boot image while it's already compiled and on the phone. Which AFAIK is impossible
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I was thinking the same thing, That K is for the Verizon model. good to know.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I'll look into it tomorrow!
Thank you.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I believe the kernel would still work.
It looks like the same kernel is used among NHG47K, N2G47J, and N2G47E, so my patched one should work for all of them. I'll update the post.
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
bobby janow said:
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
Click to expand...
Click to collapse
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
iissmart said:
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
Click to expand...
Click to collapse
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
bobby janow said:
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
Click to expand...
Click to collapse
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
iissmart said:
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
Click to expand...
Click to collapse
I've seen the term 2FA bandied about. I presume that's what you're talking about regarding the lockout. So to clarify, if you don't have an unlocked bootloader you can't sell the device? That seems weird. How do you get your account off? If I gave the phone to my wife she can't add her account?
I've never lost a device either although I have smashed one of them disastrously. But now I have a lot more stuff on the device including some personal pics and videos, password files, banking app and of course AP. I actually think my reasoning was more of like there is so much hacking and theft going on that rather than take a chance let me see what it's like being locked like normal people. It's hasn't been bad at all so far as I'm sure you know since you're not really modded either. I get the OTA on another slot and while it's updating I can use the device and a simple reboot updates it. But the bigger reason is that I got a Verizon model (Pixel 32gb) for $240 and not the $650 the Google one would have cost. I'm not sorry although I will revisit that once the Pixel 2 is released. Black Friday is your friend. I would even have bought the Google Pixel for $350 if they had a deal but they didn't. With a fully functioning 5X I just couldn't justify the full price.
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
coldconfession13 said:
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
Click to expand...
Click to collapse
After extracting the file I just renamed it to sailfish-image and used that in the command fastboot flash kernel sailfish-image. Flashed fine.
Sent from my Pixel using XDA-Developers Legacy app