Related
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
toby1978 said:
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
Click to expand...
Click to collapse
I've got the same question. I know I'm an idiot that shouldn't have installed Gapps without having a clue, but unfortunately I did. I used the Victoria Antonio youtube video that says it does not root but does install Gapps about 4 months ago--May 2013. I'm now trying to figure out how to get the OTA update to 2.1, but I'm just lost, since it's been a while. I tried fooling around in TWRP, but again, didn't have any luck. Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
abbienormal said:
Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
Click to expand...
Click to collapse
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Thanks and sorry!
aicjofs said:
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Click to expand...
Click to collapse
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
abbienormal said:
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
Click to expand...
Click to collapse
If you followed any of the guides out there then you likely have gapps on your tablet(Google Play Store). If that is the case then it has modified/removed some system files. When the Nabi OTA does its thing in the "Android guy" screen(aka stock recovery) it finds files missing or modified and halts the OTA.
You have 2 options. 1) Use a modified OTA(that ignores those files), or
2) restore your backup you made during the Victoria video that has unmodified/removed files then do the OTA.
There is a caveat. The new 2.1.27 OTA uses up almost all the room on the system partition. Without removing something you cannot have a tablet with full gapps package and full Nabi 2.1.27 something will have to be deleted.
Start reading from post #1597 http://forum.xda-developers.com/showthread.php?t=1905674&highlight=nabi&page=160 it will make some more sense.
Update Nabi 2
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
rozibaby84 said:
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
Click to expand...
Click to collapse
Assuming you are on 2.0 right now?(2.0.5)? I'm going to base my description on that, if it's 1.9.37 or less there would be other steps.
If so you have a couple of options. I don't know which method you used to get playstore so it's a bit harder. There are 2 questions that you need to answer for yourself. Do you want Wings or the Playstore? Because as of right now it's difficult to fit them both on, and while we kind of have a method using symlinks it's not perfect yet.
So if you want to update and keep the playstore the first thing you need to do is figure out if you have TWRP installed(probably best to have version 2.6.1.0). WIth tablet powered off press and hold the vol+ and power key, navigate with the vol- key to recovery kernel and vol+ to select. If it boots to TWRP you can go on, if it boots to an Android guy you need to install TWRP. Once you have TWRP. MAKE A BACKUP! You can delete it later if you choose but make one now so you can get back to where you are if something goes wrong. I would use external SD for all of this because these are some big files.
After you have done that you can try to do this:
Download these
https://docs.google.com/file/d/0B024tOntNFbbaFJHcFRBRjVMUXc/edit?usp=sharing
http://home.comcast.net/~aicjofs/205to210libfix.zip
Copy them to the Nabi.
Boot in to TWRP and "install" both of these. You should be at 2.1 with Playstore and no Wings(You will still have one Wings app)
OR
You can restore a stock 2.1 if the above doesn't work
Download this:
https://docs.google.com/file/d/0B024tOntNFbbX1liUGN5eVU4UU0/edit?usp=sharing
Extract boot.emmc.win, system.ext4.win from the zip in to the TWRP folder on the device to internal storage(may not have room)
TWRP/BACKUPS/%serial%/2127
Or external SDcard
TWRP/BACKUPS/%serial%/2127
you will have to create the 2127 folder, and possibly the others(if you made a backup some of this will exist already) %serial% = whatever your device serial number is it's different for everyone.
Then boot to TWRP and "restore" checking boot and system only. Don't select data(it shouldn't be an option if you didn't copy data.ext4.win from the zip anyway)
This would leave you at 2.1.27 with Wings but no playstore. You can root it at that point but not install the Playstore unless you then deleted Wings.
The Product Version on the Nabi 2 tablet is 1.9.37. I am assuming that is what you were referring to when you asked if I was on 2.0 right now. I don't really care if I have the Play store or not anymore. At this point, I just want to be able to get the Nabi update and see if it addresses some of the other issues that I am having. I think that I made a huge mistake in doing all of this since I do not actually know what I am doing. I think the only reason why I got the Play store was for one specific game and I don't even remember what that game was anymore, so she will be ok without it.
I do not really understand what TWRP or anything like that is. Is there an easy way to just get rid of everything and pretty much start from scratch so that I can get the updates like normal? I know that the factory reset doesn't get rid of the rooting, unfortunately.
I am really grateful for your help! Thank you!
Error in /external_sdcard/...
I am not sure why I am getting his but I have tried every version of the Nabi2 ROM stock and custom 2.0.5 and above. It seems that I can only install previous versions to 2.0.5.
I have TWRP v2.3.3.0 installed and I am trying to get the latest 2127OTA build installed. If I revert back to stock ROM it boots fine but there a few odd going ons. One it always defaults to Mommy Mode even though I select Daddy Mode. WiFi never works even with WiFi fix. Tap sound does not turn off even though I selected to turn it off.
At this point I am fine going back to a full working stock mode as long as I will be able to get the latest OTA of the web or a working 2127OTA build.
Please advise,
Niles
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
marcusbaw said:
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
Click to expand...
Click to collapse
I have upgraded to the latest TWRP, 2.7, on my Nabi2 and was able to upgrade to 2.05, but I am still not able to upgrade to 2.10. Same error. Obviously some one was successful or they would not post the 2.10 file. Please advise.
Not sure if it will work for everyone, but....
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
How to Restore Backup?
78cherokeechief said:
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
Click to expand...
Click to collapse
How do I locate the backup file to restore it? I am hoping that I saved everything on my computer at home. I really just want to get rid of everything that I did to get access to the Google Play Store. I regret ever messing with it to begin with. I am trying to update my daughter's tablet, but it won't let me bc of whatever I did to get the Google Play Store about a year ago. I am almost 100% sure that I used the video by Victoria Antonio to root the tablet originally. If you are able to explain this process to me to fix it, I would greatly appreciate it. I like to think of myself as being pretty computer intelligent, but this was a big mistake!
So following Davey126's advice, I started looking into doing a rollback on my apollo 3.2.5. I managed to get the play store up and running after some work, and grabbed the latest prop editor following the instructions in http://forum.xda-developers.com/showthread.php?t=2782159 So far so good. I then edited the four lines in question, and allowed the device to reboot.
The changes didn't seem to take. After the reboot I ended up on the same version as where I started, and the four lines I changed were back to their unedited versions. Since I have run into a problem with r/w permissions before, I suspect I'm missing them here as well - but I haven't seen the thread/entry on how to change those. Any help would be appreciated.
If, those aren't the issue, then I'm lost again.
begalund said:
So following Davey126's advice, I started looking into doing a rollback on my apollo 3.2.5. I managed to get the play store up and running after some work, and grabbed the latest prop editor following the instructions in http://forum.xda-developers.com/showthread.php?t=2782159 So far so good. I then edited the four lines in question, and allowed the device to reboot.
The changes didn't seem to take. After the reboot I ended up on the same version as where I started, and the four lines I changed were back to their unedited versions. Since I have run into a problem with r/w permissions before, I suspect I'm missing them here as well - but I haven't seen the thread/entry on how to change those. Any help would be appreciated.
If, those aren't the issue, then I'm lost again.
Click to expand...
Click to collapse
Stop!! You are following the wrong procedure and could brick your device! Don't reboot again. I will post further info shortly (on a call at the moment...).
EDIT: Sorry for the earlier drama; you were headed for a cliff ...
Recheck the guide (post #1) from the thread you linked. Note there are two sections: One for devices below 3.2.5 and a second for 3.2.5-3.26. You want the second section. There is no need to mess with build prop. You should immediately restore that file to its previous state (hopefully you have/made a backup). Then follow the rest of the instructions. Again, sorry for sounding like an alarmist worry wort. A quick check of the forums will surface many hdx carcases in the sad hands of those who didn't follow instructions or made simple mistakes (we all make mistakes).
Davey126 said:
Stop!! You are following the wrong procedure and could brick your device! Don't reboot again. I will post further info shortly (on a call at the moment...).
EDIT: Sorry for the earlier drama; you were headed for a cliff ...
Recheck the guide (post #1) from the thread you linked. Note there are two sections: One for devices below 3.2.5 and a second for 3.2.5-3.26. You want the second section. There is no need to mess with build prop. You should immediately restore that file to its previous state (hopefully you have/made a backup). Then follow the rest of the instructions. Again, sorry for sounding like an alarmist worry wort. A quick check of the forums will surface many hdx carcases in the sad hands of those who didn't follow instructions or made simple mistakes (we all make mistakes).
Click to expand...
Click to collapse
No worries!
1. Yes, I had a backup.
2. Nothing got broken, so everything is peachy.
3. The way that post is written, there is absolutely no easy way to tell (for the average user) that you still don't edit the file with build prop. All it appears is that you need a different roll back file for 3.2.5 and 3.2.6 variants instead of the earlier versions.
Someone should likely edit that post - or at least add something to it to make it more clear. I know I read every entry in that thread and I never caught anything that told me "hey, you are on one of these two versions. Skip the build prop step and just push the update. it'll work fine from there."
However, I thank you for the added information. I'll give it a whirl and see if that works. It would be nice to get beyond at least point C so I can get to the steps I want to do. I keep getting stuck at the point just before where things get nice.
begalund said:
No worries!
Nothing got broken, so everything is peachy.
Click to expand...
Click to collapse
Glad nothing got busted!
begalund said:
Someone should likely edit that post - or at least add something to it to make it more clear. I know I read every entry in that thread and I never caught anything that told me "hey, you are on one of these two versions. Skip the build prop step and just push the update. it'll work fine from there."
Click to expand...
Click to collapse
It's an old post created before 3.2.5+ was released. I do not know if the OP is still around. As many others have commented the hdx forums are generally a mess (with a few notable exceptions) as the landscape is continually changing. No one has the time/energy to create and validate step-by-step guides given the number of permutations/combinations and high risk of bad outcomes given a touchy device with limited recovery options...especially for those who can't install twrp and/or unlock their bootloader.
Note to newbies: Many tinkerers come to these forums thinking all the cautions are the byproduct of excessive hand wringers blowing smoke out of a certain orifice. Hey, if I create a brick I'll just whip out my magical fastboot cable, arsenal of fastboot commands and make everything right again. Err, no. Fastboot cables don't work on the HDX nor to most other recovery techniques. Tread carefully...respect the kindle. Rewards will come soon enough.
Hey, already pushed the thank you, for all of your help, but I've got one more fundamental question that might seem kind of stupid, but what exactly does this mean?
"4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
. . . . .
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage."
I skipped steps 5 and 6, because they make sense to me. But step 4 loses me. which "same" folder? None of the previous steps mention anything about a folder where anything is being stored. Likely this is referring back to that same previous post you referenced above.
I have no trouble with step 7 - that makes sense - but I'm suddenly worried about this mysterious step 4, especially since "SAME" is in all caps.
begalund said:
Hey, already pushed the thank you, for all of your help, but I've got one more fundamental question that might seem kind of stupid, but what exactly does this mean?
"4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
. . . . .
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage."
I skipped steps 5 and 6, because they make sense to me. But step 4 loses me. which "same" folder? None of the previous steps mention anything about a folder where anything is being stored. Likely this is referring back to that same previous post you referenced above.
I have no trouble with step 7 - that makes sense - but I'm suddenly worried about this mysterious step 4, especially since "SAME" is in all caps.
Click to expand...
Click to collapse
Tanks for the thanks. As a new comer I struggled a bit and got help from some kind souls in these forums. Giving back ...
It is a tethered operation as you probably gathered. Step 4 means you need to put the .bin file in the same folder on Windows where install.bat lives. If you edit the batch file you'll see it generates a signed flashable image from the bin file and then issues a bunch of adb commands on your behalf. For Step 7 copy the bin file to root (not sdcard) on your hdx. Then reboot.
Footnotes:
- when you download the batch file be sure to use the blue "download now" button. Filename should be "rollback.zip" .The orange button yields an executable called "rollback.zip.exe". Probably fine but since I can't see into it can't tell for sure. Also, make sure to download the file appropriate for your device (7"/Thor or 8.9"/Apollo).
- be sure to immediately disable wifi after performing the update; otherwise Amazon may push a nasty update of their own. As a precaution I would advise deleting all existing wifi profiles and make sure you are not within range of an open hotspot. Don't want the Kindle to auto connect and update while you are sleeping.
- I would strongly recommend flashing twrp immediately after, test and backup of you stock rom from within twrp. Leave the image on your kindle if you have room.
- Once everything is working to your satisfaction flash the nexus rom (v2.0.5) and optionally the 3.2.3 bootloader update as described in earlier posts. Read up on any caveats.
- (optional) Unlock your bootloader. This not necessary to run Nexus and CM11 but is for some CM12 builds. An unlocked bootloader also opens additional recovery options should you loose twrp. That said, unlocking the bootloader is not for the faint of heart and carries its own set of risks.
Davey126 said:
For Step 7 copy the bin file to root (not sdcard) on your hdx. Then reboot.
- be sure to immediately disable wifi after performing the update; otherwise Amazon may push a nasty update of their own. As a precaution I would advise deleting all existing wifi profiles and make sure you are not within range of an open hotspot. Don't want the Kindle to auto connect and update while you are sleeping.
Click to expand...
Click to collapse
Okay. New headaches.
First part of the rollback happened. I'm now on 14.3.0.0. That worked okay. I grabbed the 14.3.1.0 update and loaded it on but then nothing happened. No further updates.
At this point I figure 1 of 3 things happened. Either:
A. I put it in the wrong place - I stuck it in Internal Storage (/storage/emulated/0), I would move it to either / or /root, but I can't - "no space available" error when I attempt to move it via es file explorer
B. I could keep turning OTA off and on and hope it eventually takes, but how many times exactly?
or C. I'm missing something with wireless needing to be on (or off but in some weird mode) or whatever. I'm just worried about having an automatic update to another newer version that I can't fix.
So what am I missing?
begalund said:
Okay. New headaches.
First part of the rollback happened. I'm now on 14.3.0.0. That worked okay. I grabbed the 14.3.1.0 update and loaded it on but then nothing happened. No further updates.
At this point I figure 1 of 3 things happened. Either:
A. I put it in the wrong place - I stuck it in Internal Storage (/storage/emulated/0), I would move it to either / or /root, but I can't - "no space available" error when I attempt to move it via es file explorer
B. I could keep turning OTA off and on and hope it eventually takes, but how many times exactly?
or C. I'm missing something with wireless needing to be on (or off but in some weird mode) or whatever. I'm just worried about having an automatic update to another newer version that I can't fix.
So what am I missing?
Click to expand...
Click to collapse
Hum. Everything seems ok. Bin file is in the correct location (/storage/emulated/0). Make sure OTA is enabled using the same tool/technique you originally used to disable (there are several methods) and reboot. Some posters claim they had to toggle it on/off a few times. While my device recognized the update fairly quickly (minutes) others mentioned it took a while. Keep checking settings->device->system updates. Some say the update did not take until WiFi was disabled. Might want to try that first. I recall seeing something about airplane mode but can't immediately find the post.
btw, you can mitigate the automatic update risk by making sure there are NO WiFi profiles on your device and you are not in range of any open hotspots (if possible).
Well, still no dice.
I've reset OTA (cycled off then on) and rebooted about 10 times now. I've also attempted various options of wifi on, off, and in airplane mode. The only thing I haven't done is connected to an actual network and pushed the check now button (I'm not quite that dumb). The lovely device just keeps taunting me with 14.3.0.0 and refusing to do anything else.
Very frustrating.
I'm gonna head for bed and look at it fresh sometime tomorrow. Maybe it will miraculously fix itself while I ignore it (but I really doubt that will be the case).
begalund said:
Well, still no dice.
I've reset OTA (cycled off then on) and rebooted about 10 times now. I've also attempted various options of wifi on, off, and in airplane mode. The only thing I haven't done is connected to an actual network and pushed the check now button (I'm not quite that dumb). The lovely device just keeps taunting me with 14.3.0.0 and refusing to do anything else.
Very frustrating.
I'm gonna head for bed and look at it fresh sometime tomorrow. Maybe it will miraculously fix itself while I ignore it (but I really doubt that will be the case).
Click to expand...
Click to collapse
Sorry for your troubles. One or more of the following are likely culprits:
- OTA capability not fully restored (try HDX Toolkit if you haven't already)
- ensure the .bin file name matches exactly and is located in the proper folder
- Verify .bin MD5 on the device (use a tool like hash droid) MD5=0F2BC5278C057E7A6B4823B0F68D0727
- use notepad to view the batch file; make sure all the files made it to respective directories on your HDX
- repeat the preliminary steps with your device tethered
If everything checks out then the real fun begins. You'll need to comb threads for others who have experienced a similar problem. You are looking for some morsel that may provide a path forward. Frustrating - yes! One reason there are not step-by-step tutorials as everyone's device seems to respond differently; too many uncontrolled variables. Not sure anyone really knows what all those variables are.
Remain calm and don't do anything crazy. Be wary of fixes that involve manually modifying build.prop or flashing via adb. Both are legitimate tools/techniques in skilled hands. Used incorrectly they can (and usually do) yield a brick.
So I was attempting to write a nice long message about how I was using the right toolkit, and how to check on OTA messages to verify whether it was performing correctly, when all of a sudden I look down at my device and it suddenly stopped being obstinate.
No idea what I did. It just started playing nice.
14.3.1.0 now installed. I'm going to go get a drink.
begalund said:
So I was attempting to write a nice long message about how I was using the right toolkit, and how to check on OTA messages to verify whether it was performing correctly, when all of a sudden I look down at my device and it suddenly stopped being obstinate.
No idea what I did. It just started playing nice.
14.3.1.0 now installed. I'm going to go get a drink.
Click to expand...
Click to collapse
Funny how some devices take their time processing update files. Would love to know the criteria for checking and if processing can be manually triggered. Don't forget to disable OTA or keep WiFi off as long as there is a version of stock os in the system partition. One you load nexus or some other rom OTA worries will be history.
Edit: Enjoy that drink; you earned it
So I thought I would just report back with a final update as of 20 minutes ago:
Finally got the device rolled forward to 14.3.2.4
Re-rooted
Re-safestrapped
Backedup
Partitioned
And Nexus 4.2.2 running perfectly fine in Rom slot 1.
I'll go add a few apps later to personalize and make it wife-friendly. Thanks to everyone here and especially Davey126 for the patient assistance. I'll probably be back at some point in the near future to figure out the next step, but for now I'm gonna go enjoy an ad-free device for awhile.
begalund said:
So I thought I would just report back with a final update as of 20 minutes ago:
Finally got the device rolled forward to 14.3.2.4
Re-rooted
Re-safestrapped
Backedup
Partitioned
And Nexus 4.2.2 running perfectly fine in Rom slot 1.
I'll go add a few apps later to personalize and make it wife-friendly. Thanks to everyone here and especially Davey126 for the patient assistance. I'll probably be back at some point in the near future to figure out the next step, but for now I'm gonna go enjoy an ad-free device for awhile.
Click to expand...
Click to collapse
Glad to hear you are back in business! An interesting choice to upgrade to 3.2.4 vs 3.2.3. Native twrp requires 3.2.3 or lower so no CM11/12 or bootloader unlock. I do not believe there are meaningful differences between Nexus v1.0.1 (safestrap edition) and v2.0.5 (native) so nothing lost at this point. Plus you still have access to stock with a simple reboot which can be an advantage. But it is unlikely other roms will be adapted to run under safestrap. Btw, downgrading from 3.2.4 is a bit tricker than 3.2.5/3.2.6. You many need to upgrade first.
Don't forget to reblock OTA if you haven't already. Enjoy your 'new' device
Davey126 said:
Glad to hear you are back in business! An interesting choice to upgrade to 3.2.4 vs 3.2.3. Native twrp requires 3.2.3 or lower so no CM11/12 or bootloader unlock. I do not believe there are meaningful differences between Nexus v1.0.1 (safestrap edition) and v2.0.5 (native) so nothing lost at this point. Plus you still have access to stock with a simple reboot which can be an advantage. But it is unlikely other roms will be adapted to run under safestrap. Btw, downgrading from 3.2.4 is a bit tricker than 3.2.5/3.2.6. You many need to upgrade first.
Click to expand...
Click to collapse
So it turns out I may have done myself a big favor by going the safe route. I'm not positive of course since I haven't tried the "non-safe route", but I'm guessing I'm right. I recently obtained a bluetooth KB to use with the fixed device - specifically the bear motion KB/case - cause I figured if I only spent $40 on the tablet, I'm not going to spend more than that on the KB. Since one of the purposes for this is to allow me to use it for remote work options, I wanted a better KB than pulling up the native one - especially if I'm running teamviewer, the screen is small enough as it is.
In any event, the Nexus SS edition has troubles pairing up with the KB (already logged a bug report on it), so I'm probably going to have to swap over to a different rom. Since I've already been through the process, and I've seen your updated posts in another thread, I'll just upgrade, rollback, and follow the twrp, cm11/12 route instead.
I just need to check and see if anyone has used this combination of hardware with another rom and made them work out.
begalund said:
So it turns out I may have done myself a big favor by going the safe route. I'm not positive of course since I haven't tried the "non-safe route", but I'm guessing I'm right. I recently obtained a bluetooth KB to use with the fixed device - specifically the bear motion KB/case - cause I figured if I only spent $40 on the tablet, I'm not going to spend more than that on the KB. Since one of the purposes for this is to allow me to use it for remote work options, I wanted a better KB than pulling up the native one - especially if I'm running teamviewer, the screen is small enough as it is.
In any event, the Nexus SS edition has troubles pairing up with the KB (already logged a bug report on it), so I'm probably going to have to swap over to a different rom. Since I've already been through the process, and I've seen your updated posts in another thread, I'll just upgrade, rollback, and follow the twrp, cm11/12 route instead.
I just need to check and see if anyone has used this combination of hardware with another rom and made them work out.
Click to expand...
Click to collapse
Have you tried stock Fire OS yet? Should be an easy test given you are on Safestrap with (presumably) stock in the base slot. That would help rule out any native compatibility issues.
If you opt for a different rom might try the native version of Nexus first (v2.0.5) after you get twrp loaded as it's an easy test. Possible (albeit unlikely) Safestrap is interfering. Of the two CM varients CM11 would see the better choice today as the latest CM12 build still seems to have some issues with BT. As always, watch the forums for updates.
Davey126 said:
Have you tried stock Fire OS yet? Should be an easy test given you are on Safestrap with (presumably) stock in the base slot. That would help rule out any native compatibility issues.
If you opt for a different rom might try the native version of Nexus first (v2.0.5) after you get twrp loaded as it's an easy test. Possible (albeit unlikely) Safestrap is interfering. Of the two CM varients CM11 would see the better choice today as the latest CM12 build still seems to have some issues with BT. As always, watch the forums for updates.
Click to expand...
Click to collapse
Second thing I did. Rebooted into the stock rom and retested. KB works fine on that slot. So it doesn't appear to be a safestrap issue - more than likely a problem with the SS version of Nexus - else it might be a Nexus compatibility issue with the KB itself.
I haven't had time to do any more playing with the tablet - Wife's birthday, but I'll retest once I know more. Should probably make a new thread however....
begalund said:
So it doesn't appear to be a safestrap issue - more than likely a problem with the SS version of Nexus - else it might be a Nexus compatibility issue with the KB itself.
Click to expand...
Click to collapse
Well, that's verified. :good: Although on the plus side, I did have a completely problem free rollback to 14.3.1.0, got twrp installed, and then cycled through a couple of the roms available looking for one that worked with the KB. Again, much thanks for all the assistance - including the assistance you lent to another user in the main thread - it helped immensely with getting twrp working on the first attempt. :victory:
Native Nexus - no go. It had the same issue. Eventually found it, but never recognized any key strokes. :crying:
Swapped to CM11 and at first it appeared to not work either (more on this), as the rom never got past the boot stage, so I bootloaded and realized I made an error (forgot to mount). Then the rom loaded but everything crashed on opening (rebooted again, wiped and reinstalled) now everything worked but the KB - I'll come back to this one.
Was about to try magic beans when I read something about the KB being "finicky" - so I swapped back to native nexus and played with the BT a bit. after 20 minutes of trying it never synced up, so I went back to CM11.
Turns out it does actually recognize it. You need to turn the KB on, then press its BT pair button, and then have the system search for new BT devices (in that order). It still has an issue where certain apps like titanium backup (or anything else that makes root calls) cause the system's BT to drop the KB - but it does find it and it works just fine 90% of the time. And when it does drop, it can be reset pretty easily in settings by removing the pairing and going through those steps again. You'll also have to do this every time the system is first turned on and you want to use it. A bit aggravating, but better than not having it any functionality or needing to swap back to FireOS.
Plus it appears that CM11 works just slightly better than nexus for the apps I tend to use anyway - so that's another bonus.
begalund said:
Plus it appears that CM11 works just slightly better than nexus for the apps I tend to use anyway - so that's another bonus.
Click to expand...
Click to collapse
Thanks for posting your BT findings with various HDX roms (below). Helpful to others who may be experiencing similar issues. I agree Nexus (based on Jellybean) is getting a bit long in the tooth. I stick with it given overall stability for the apps and and devices that I use including a AmazonBasics keyboard which pairs fine. I have been monitoring the HDX CM11/12 threads and will likely move there as the few remaining issues of concern to me are hammered out. Been running CM11 on another device (HD) for 15+ months; great rom that brought new life to an aging device.
Hi, I am new here, but have recently gotten into rooting phones etc, but my knowledge base is still Novice at best. I have an AT&T Optimus G that was rooted and had CWM, Free G and Kitkat. Long story short, a co-worker who claimed to know what they were doing has reset my phone, wiped my external sd card and totally factory reset my phone. When I turn it on now ClockworkMod Recovery comes on, but all of my back ups etc have been wiped. I am assuming that it is now just a machine with no info on it. What do I do now? I'm sure that the answer to this will be very involved so if anyone could possibly suggest a thread to read or somewhere to start I would greatly appreciate it. I'm sorry for the inconvenience guys...
The google account that this was linked to is my current one so no issues with reset protection once it gets running or what not. Any info I can provide on my end if need be feel free to let me know. I know one of the specifics to the device was: geefhd???
Here is the current update: Android 4.4.2 KitKat
The details
Release date: September 29, 2015
Android version: 4.4.2
Baseband version: APQ8064/MDM9x15M
Kernel version: 3.4.0
Build number: KOT49I.E98020i
File size: 9.47MB
Software version: E98020i
EMT803 said:
Hi, I am new here, but have recently gotten into rooting phones etc, but my knowledge base is still Novice at best. I have an AT&T Optimus G that was rooted and had CWM, Free G and Kitkat. Long story short, a co-worker who claimed to know what they were doing has reset my phone, wiped my external sd card and totally factory reset my phone. When I turn it on now ClockworkMod Recovery comes on, but all of my back ups etc have been wiped. I am assuming that it is now just a machine with no info on it. What do I do now? I'm sure that the answer to this will be very involved so if anyone could possibly suggest a thread to read or somewhere to start I would greatly appreciate it. I'm sorry for the inconvenience guys...
The google account that this was linked to is my current one so no issues with reset protection once it gets running or what not. Any info I can provide on my end if need be feel free to let me know. I know one of the specifics to the device was: geefhd???
Click to expand...
Click to collapse
Since your phone has been wiped, you are going to have to re-install your ROM either via LGNPST, which will return your phone to stock, or you will need to install your favorite custom ROM via adb sideload.
If going back to stock via LGNPST refer to FAQ Number 3 here http://forum.xda-developers.com/showthread.php?t=2006946
If installing custom rom via ADB Sideload refer here http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
Kilogrm said:
Since your phone has been wiped, you are going to have to re-install your ROM either via LGNPST, which will return your phone to stock, or you will need to install your favorite custom ROM via adb sideload.
If going back to stock via LGNPST refer to FAQ Number 3 here http://forum.xda-developers.com/showthread.php?t=2006946
If installing custom rom via ADB Sideload refer here http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
Click to expand...
Click to collapse
I was able to fix the problem late the night of this post, but I REALLY DO APPRECIATE the advice.
I had to reinstall the firmware ultimately. I did learn the commands and process for the sideload, so that was cool, and the program zips did show as downloading from 0-100% and attempted to install, but the 4g part of "this device is geef4g" was an error that I was unable to surmount. I attempted to install the madmack version of TWRP to no avail. I am lucky I figured out the tool ONLY by accidentally stumbling over the advice referencing turning back the clock on the pc.
Moving Forward...
Ok... Had to at least stop in and say thank you for the response and post the conclusion to the handful of people that stopped and looked at the thread and at the least not be one of the members that pops on to fix their device and lurks around until they need help to post again. I wouldn't be back to stock with my Optimus if others did that. I do apologize that I was able to find onsite and unable to do it at the time of the threads origin. I wont re-post links, FlashTool the fix was figuring out the right order to go in with the drivers and eventually flashing the stock AT&T firmware with the LG FlashTool. I kept on getting an error when placing the dll file and the tot in to the Tool and it was total mental error on my part when "organizing" everything beforehand. It did require me to wipe my pc back down to Windows 8.1 simply because this is all new to me and I had files EVERYWHERE from rooting every thing I can get my hands on recently. I'm having fun, but this Optimus is my heart for some reason. Originally I had her rooted with Towelroot (I believe), it could of been the LG one click flash thing that I grabbed from here, and I remember Freegee and KitKat recovery being part of the process, but I attempted to install TWRP (personal preference for me from messing with a Kindle Fire for weeks installing CM) but during reboot always went back to CWM 6.0.2.1 (or similiar). Ultimately CM was the goal on this device but was never possible, for me at least, due to my device being "geef4g" yada yada. I think I have read the fix for this in another post, so I will re study up on all that again if need by, but I wanted to pose this question simply because the "Mystique" of successfully installing CM has passed, and while I love the interface and style of that ROM, I kinda liked AndroidArea51 Rom and another ROM whose name escapes me at the moment that I put on some OLD LG phones that I practiced on in the beginning. So this is my goal. I would love it if one or two of you guys would take the time to look at what I want to accomplish and point me in the right direction as far as the procedure and order I should install these modifications to this device and if you have preferences I would love to hear them. I will look up the threads on how to do everything, so I'm not asking for an easy way out of hitting the search box, but I am WAY behind you guys as far as skill set and knowledge base is concerned and trial and error is not the method I wanted to use on this particular machine. If I need to begin a new thread or if a MOD wants/requires me to rename this thread or move it I understand. Stand by for what my goal is ultimately......
OBJECTIVE
AT&T Optimus Pro G (will HOPEFULLY be accepted by StraightTalk and used on their network or whatnot)
I ran the IMEI through their BYOD tool and it was accepted initially a week or so ago while "rooted", so I am assuming that since it is mine from another network they wont sweat me. HOWEVER, if they are going to send any code or require me to allow them modifications during the activation process that is going to in anyway alter my device down to the castrated ST standard they sell, I will have to weigh finances and options again. I realize that Tethering will be frowned upon, traceable, and grounds for termination in either case, but the subject of Mobile Hotspots is what brought me to you guys here in the first place. It irks me.
In my original "build" of this phone I attempted to dabble in "Over-Clocking" with Kernel Booster and Kernel Auditor. I didn't have a f******* clue what any of that $hiT meant. If the app's pretty much optimized it I did so for SPEED rather than battery. I don't know why, I want this thing to FLY in a noticeable fashion for performance and so that I can whip it out and show my family and friends just what the hell it is that I am accomplishing.
1. Optimize it for speed, but I would like the eventual permanent ROM to be stable PERIOD. Whether I customize the Kernel and then place the ROM, or build the ROM and then mess with the Kernel is a hurdle that I don't understand how to approach really, so when you guys talk about it I just think it sounds cool. I am assuming that "Xposed" is something I should maybe begin studying? Build props through ES File Explorer has peaked my interest as well. Long story short, if CM is what you guys suggest I install, I dont want to Optimize the hell out of the stock only to have all of it be replaced when the custom ROM is flashed. I hope that makes sense.
2. I want to optimize the range on my WIFI and every other manner of device communication without losing security. I have numerous friends that are very generous with their personal accounts that allow me to randomly log in to strangers spots (EX. Xfinity accouts), in order to truly connect to it, I have to sit outside in the yard like a weirdo at 3am with my phone in my backyard, much to the disgust of every dog in the neighborhood. I dont want to be that guy. Honestly, I am really curious in learning how to access the internet and/or any other data networks that are out there with out using these major carriers at all. I feel like there is a lot more out there than the average person is aware of. Maybe they are super low key because they are owned by the upper rich 1% or the military etc etc, but if other networks exist that facilitate the same communications that us peasants pay $100/month to access I want in on it.
3. Optimize the picture, color and clarity of the screen for any and everything being shown on it, optimize the Audio with a good "Music Player"(currently what I use) which I generally heard through head phones and when in the car pushed to that system via FM signal. I currently have over 1000 tracks, discovering a cost efficient way of adding to that Library would be wonderful (ie: spend $0), but I have been out of the music file sharing game for a while so I dont know if this is realistic. Optimizing my camera to take the best shots possible on this phone. I generally shoot nature shots, sunsets, sunrises.... unsuspecting women in doggy, the usual... I will not be loading movies and super large files. I am a NAZI with my storage. If I could expand upon the internal or external factory specs that would be great. In other words, real life applications... I haven't been a gamer for decades so nothing crazy, but this device's beautiful picture is what I fell in love with.
4. A kick ass ROM UI that is eye catching and user friendly... sorry so long winded. Got to go run calls at work now....
DEPRECATED
This firmware is old and deprecated.
See the below link for new firmware and a better root method.
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
You can just flash the BL_ tarball if you don't want to install a new system
but want the better screen and modem drivers.
PART 2: FIRMWARE RELOADED
I have done extensive research into the issues reported by those of you who are still experiencing screen issues.
I was unable to reproduce the screen issue on my then-current firmware with this update.
Not being content to leave people with buggy screens, I learned as much as I could about the s8 firmware.
This is what I did with that information.
Flashable Custom Firmware Package For ALL SM-G950U/U1 ON US CARRIERS
If you have a non-us G950U and want to install this pm me or ask in the thread and ill make one. Its very simple but I wanted to get this out to everyone else ASAP
​
NOTICE!
This an UPDATE (and More) to the Green/Garbled Screen Issue firmware.
There is NEW firmware to download below, and everyone who is rooted should read on, even if you installed the previous version.
Background
At the core of the issue with the garbled screen, modem panics, and sd card issues are two central themes: Bugs, and Incompatibilities. The S8 family of phones was fraught with issues early in its release, including the infamous "Red Tint', Fingerprint scanner malfunctions, mysteriously poor battery life, and surely a bunch of smaller others. Many of these bugs were caused by issues in the device's underlying firmware. Like most devices, Samsung has worked to fix these bugs and improve device performance throughout the phones lifetime for sale in public.
Root Bugs
The problem was unfortunately worse for users of one of the rooting methods for the S8. The biggest reason for this is that in order to relax security constraints enough to make rooting possible, a "non-user oriented", "factory" combination firmware was used. This firmware, being designed apparently for configuration/repair processes inside a factory, was not tuned to the normal level as the public firmware, likely did not go through the same testing, and ultimately any bugs unique to this "Combination" firmware that did not directly affect basic functionality or also stock were probably largely initially ignored.
This is where most of the issues that you all have had come from.
Finding a Solution
As I was unable to reproduce the issue on my device without resorting to the original firmware shipped out with the root method I used, I decided to think about what made my device different than the other devices reporting these issues. While sure we may have slightly varying hardware and that may contribute to these issues as well. What I am absolutely certain of is that most of us have different releases of software from each other. Not only have people essentially ad-hoc upgraded from the original firmware they rooted with until now, many have not upgraded at all or, only partially upgraded (such as with the pervious version of this).
While I could have simply packaged up my firmware/bootloader flashfire backup, I decided to take it a step further.
THE GOODS
Without further ado, I present to you:
S8Root Improved: A SM-G950U1 Custom Firmware Package for Root Users
This package contains a custom mix of the latest AQH3 STOCK (not combination) firmware used wherever possible with the Necessary boot/kernel images from the combination firmware necessary to keep root working with permissive SELinux. It contains all of the improvements from the previous version, and many more.
RESULTS
I can only speak for myself, but the results I experienced were amazing:
- Better UI Responsiveness.
Things surprise me how they move
- Sharper/brighter screen colors
I thought it couldn't get better than the last version but it has! Everything just looks crisper and are super bright without being oversaturated like with the Adaptie Mode.
- POSSIBLY Improved LTE network connectivity.
Note I said POSSIBLY. I personally regularly experienced 8-10Mb/s download bumps and 2-3Mb/s upload bumps in LTE while moving back and forth from this new firmware. I have my LTE radio locked to a specific channel (there are two i pick up at my place and one is terrible) and I carefully measured -107 to -112 dBm RSRP and -13 to -14 dB RSRQ prior to each measurement. I almost left this out but I figured it would be better to give you the information with no conclusion either way. It ABSOLUTELY could be Atmospheric changes, Traffic level changes, or any other of a million thins. YMMV
- Could POTENTIALLY still any remaining fix long-standing SDCard issues
I did not experience this, but had a few reports from users that did. The same pieces used in that version that would touch SDcard usage are used here, so that fix/improvement will carry over.
DISCLAIMER
Unfortunately proving beyond any shadow of a doubt that this package fixes the issue was impossible . I have TRIED AND TRIED AND TRIED to trigger the screen issues, including tweaking on and off every setting (auto brightness, multiple DPIs, different graphs modes, etc) I could get my hands on and it just was not happening. I used every software/systems trick I could think of to break this again, and I was completely unable to tickle the bug on this firmware, despite being able to reliably trigger it almost on command using my previous firmware.
The only thing left to do is either:
- Get the source from samsung, fix the bug myself, and get them to sign my new kernel image with their key so our locked bootloaders would allow it (HAHA I DOUBT IT)
- Acquire a large fleet of S8s (and S8+s) to run distributed integration testing (like the kind Android use at Google). Well if someone wants to buy me a few dozen s8s and s8+s (each) sure I'll take a month off work and squash this, but otherwise not gonna happen either.
If it STILL happens for you, I'm sorry.
I have done everything I can think of, and if it happens to you and you have suggestions, I'm all ears.
BUT HEY, but this is XDA right? Land of mods like Xposed which will brick one persons device and work flawlessly on the identical one next to it. And we love Xposed don't we?
Despite absolutely hilarious comments to the contrary, this package absolutely meets the (aka "BugFix") as well as just about any android update ever does, given the wide variety of environments, usecases and software configurations out there. I surely hope that this works for you.
Instructions
1) Download the package from the link above.
- Here it is Again for good measure.
2) Reboot into download mode and flash using Comsy Odin
Thats it! I packaged this in a way to make the process as smooth as possible.
There is NO reinstall, NO wipe of any kind, nor ANY further work on your part needed to install and use this.
The file size is small so the download is fast, and again, there is NO WIPE or config change needed.
if (for some inexplicable reason) you want to roll back, or go to 100% stock sans root, that process should not be made any more difficult as well.
Legacy Information
If you were here before and either looked at or downloaded the previous version, AND YOU HAVE NO QUESTIONS you can skip this part.
If you have questions, please read through to the end of the post before asking them, as I tried to answer as many as I could before hand and all of this information still applies.
WHAT IT IS NOT:
I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN ENTIRELY UPGRADED OS.
There is no full stock AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE but ME
Since the moment I installed this I have not had ONE SINGLE screen issue, where previously I would have them several times throughout the day (at least 3 sometimes upwards of 6). For the case of ME and MY device, I am confident in declaring that this boot ROM does not have the same kernel bug that was causing the issue on the boot.img provided as part of your traditional root method.
NOTE: This is for the s8 G950 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere but my phone as I dont have any other s8s nor do I have access to any locally. I hope it works for you as well as it has for me.
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: Go Download the New Hotness
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and accidentally click factory reset instead, please tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I wi;; be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: A s8+ thread is coming too, as I sprung for purchasing both downloads to be an equal opportunity XDAer (at least with US flagship Samsung devices lol) but since I have an s8 and thus had the files locally already I made this one first
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, all of the tons of you who have made so many aewesome mods, themes, apps, what have you that I use every day and that make me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
Here is the restof the s8 combo firm if you are interested, but don't just flash this as its not a full OS:
EDIT: DOWNLOAD THE NEW ONE ABOVE
Can I Get The Link To The S8+ Boot im willing to try it
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Coming very soon I promise! 10m max
Ok thanks
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Its up now! https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673815
whats the bootloader verison? it can be found by booting into download mode manually.
Cameron581 said:
whats the bootloader verison? it can be found by booting into download mode manually.
Click to expand...
Click to collapse
This isn't a bootloader change, it's boot.img which is the kernel and root filesystem essentially
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
mweinbach said:
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
Click to expand...
Click to collapse
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
wildermjs8 said:
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
Click to expand...
Click to collapse
i mean legally a warranty can not be void through software modifications unless it causes physical damage to the device. Since the efuse was not tripped no physical damage has been caused and no warranties have legally been void.
I had the green screen/graphics corruption after flashing this still...
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
wildermjs8 said:
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
Click to expand...
Click to collapse
I have auto brightness off and still get it here and there.
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
wildermjs8 said:
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
Click to expand...
Click to collapse
We flash the tar in the AP slot correct?
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
Yep
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Seems to be running better to me. Thanks bro
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
It actually does not matter, as Odin will do the right thing no matter what.
Sorry I should have made that clear. I will update the op to make that clear
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
Nope, only need the tar file bud. The old boot.img file is just basically the previous version of this.
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
The old image is actually part of the new tar, do you will have it anyway . I packaged it in Odin this time because there are some pieces of firmware FF either can't or warns against using it for. Plus one clean simple tar seemed easier, no?
Do you see the boot.img in the op? I thought I nixed all the instances of the link but I may have missed one.
I almost rewrote all the old text to reflect now but it felt like editing history so I tried to preserve what made the most sense still. It sounds like it's still a little confusing sobrskr another crack at it shortly.
Please let me know if you have any trouble! I'll be here to help all evening
Important notice! : iLLNiSS made me aware of a serious risk!
If you play with the firmwares manually and not with the flash all bat then DO NOT flash the blobs!
These are the actual bootloader files and stuffing up here will cause a hard brick!
I have to stress this out as it is serious thanks to not having working APX drivers a flshing programs for the Shield!
For starters, I uploaded a copy of the 7.2 developer firmware here:
7.2 developer ZIP on Dropbox
It is the full 1.1Gb update and not the 422mb block based one.
I have done some extensive tests since the first block based update wrecked my rooted Shield.
Some of it will end up in this post as info for everyone.
But lets start with what seems to be the problem for a lot of users right now who run a rooted Shield : Fixing the problem
A downgrade is officially not supported by Nvidia but my tests showed it works just fine if you only go back to the 7.1.
So far my tests showed differen sources for a Shield no longer working after the OTA.
1. The device had an unlocked bootloader and you got the 422mb block update.
This would have stuffed your bootloader and the Shield won't go past 1/4 on the progress bar for the update.
You are in luck as just flashing the 7.1 bootloader will fix it.
After that just dismiss the update and change the settings to manual updates.https://forum.xda-developers.com/editpost.php?do=editpost&p=78466377
2. Your device was already fully rooted and you got the full update that resulted in your Shield doing all sorts of thing but nothing properly anymore.
As long as your apps are still there and the Shield is still somhow usable you are lucky again.
A downgrade to 7.1 will fix it, I will explain the steps required further down.
3. You made bid mods, used Magisk or other rooting tools and now your Shield complains that your system is corrupt.
Bad luck if your bootloader is locked as you loose it all.
Lucky if the bootloader is unlocked as you might be able to keep most if not all during the downgrade.
General words of warning:
Even if your bootloader was unlocked from day one I can not garantee that the downgrade will keep all settings, apps, databases and so on.
For me it works fine as I kept all vital databases on external storage.
The procedures are all based on the developer firmware, on the stock firmware some things can still be done but then again you should not have more than software problems.
On the stock firmware the bootloader is locked by default and you can use some things required to owngrade due to the restrictions of a stock system.
General downgrade procedure for the developer firmware to get back to 7.1 :
If the update did get stuck on the progess bar early on and a reboot won't fix it so you can dismiss the update you just follow the steps.
If you can reboot into the 7.1 then just dismiss the update.
Trust issues or curruption warnings at boot but an otherwise working shield on 7.1 require to flash the 7.1 bootloader again.
In some cases it is possible to skip the corruption warning with a connected controller.
A reboot once you got to the homescreen will determine how bad it is.
Reboot goes fine: You are good.
Reboot keeps nagging with warnings other than the unlocked bootloader: Downgrade.
The downgrade is only required if you have problems or the Shield already runs on the 7.2!
In almost all other cases just flashing the 7.1 bootloader is sufficient.
Fixing a stuffed Shield by sideloading the 7.1 firmware while keping all apps and things:
Enable USB debugging and allow the connections for the computer if you still have access to the settings.
Otherwise you need to flash the 7.1 fresh and might loose vital things that need to install again.
Reboot into the stock recovery, if you use TWRP flashed on the Shield already then please flash the recovery from the 7.1 firmware first.
Hook up the controller and pressing A or B should get you into the normal recover screen past the dead droid.
ADB sideload XXX - where the xxx stands for the filename you have for the developer ZIP.
After the rebbot you should be back on your 7.1 homescreen and can dismiss the 7.2 update.
Also change the update settings while at it
Fixing a fully stuffed Shield and then downgrading to the 7.1 firmware:
If all went down south then you tried a few things and realised there is no way to get your data back and even less to prevent the 7.2 update.
Installing the 7.1 from scratch forces the setup wizard and before you can get anywhere you need to update to 7.2
So much easier to use the linked 7.2 update from above until Nvidia provides it on their download servers.
A vital thing to do is to keep the bootloader locked!!
Same for NOT having TWRP installed on the Shield!
If in doubt flash the 7.1 boot and recovery partitions first then go back into the stock recovery and wipe the cache.
Coming from a stock developer firmware with just an unlocked bootloader you are good to go.
Sideload the 7.2 update.
Unplug when the reboot starts and go into fastboot to lock the bootloader: Fastboot oem lock.
This is a vital step as the new kernel otherwise could ruin the completion of the install.
Ignore the double hassles and go through the wizard so you can enter the settings again to enable the developer mode and USB debugging.
Unlock the bootloader so you can do it all again Last time I promise!
Once you have both the bootloader unlocked AND the Shield in a usable condition past the setup wizard:
Reboot into the recovery to sideload the 7.1 firmware.
After the next reboot you are back on the 7.1 homescreen drirectly and can dismiss the update.
Possible tricks that can help you to prevent the installation of the 7.2 update if you come from a fresh 7.1 install instead:
Don't allow the reboot and instead use ADB to reboot into the recovery.
Wipe the cache - this will remove the scripts required to start the update after the reboot.
The next reboot should bring you back to the homescreen where you can stop the new download of the update and change the update settings.
TWRP, full root and new security measures in 7.2:
The 4.9 kernel used also makes use of a Fstab configuration that no longer includes the system partition.
This and other restrictions currently make the normal use of Magisk impossible.
With no system partition available to Magisk the changes in the boot process come to a stop and the Shield gets stuck during boot.
The added restrictions also make it very, very hard to manually add SU and busybox.
At least without getting the currupt system popup on every boot and finding out that a lot of things still don't work properly.
A final 7.2 firmware is said to be available on the download servers today.
If this final is no different from the current OTA then it will not be of any use for users requiring a fully rooted devices.
With the stock recovery still using the old kernel all attempts to use recovery functions to alter the system for rooting fail as well.
Can't blame the company as all this is part of Google revamp og security and closing backdoors and loopholes for possible attackers.
Personally I think it is Googles way of keeping control over devices they don't actually own.
Anyways I did make some little progress:
Plans for the near future:
Security is good but I like to know what my Android devices are doing and especially what Google likes to collect if I can not find ways to stop it.
So I will not try to use any backdoors or secrurity vulnerablilites in the new kernel to allow a full root on my Shield.
I will go the route I know best: Manual labour
The bootloader is already fixed to allow what we are used to from previous developer firmwares.
As SU and busybox can not be manually entered at this stage I will try to include them directly in the stock 7.1 firmware while renaming the OTA updater to have it a bit easier.
Assuming that works as expected I will do the same on the 7.2 firmware and compare the corresponding scripts and so on.
If the standard SU still works on an "unlocked" 7.2 I should be able to adjust the Magisk ZIP accordingly to implement it into the bootloader.
Only need to figure out if Magisk then has enough rights to work and the system is still happy to accept the changes.
I noly have the 16Gb 2017 model to work with but since the bootloader seems to be same for all Shield models I think if it works then it should do so for all models.
In the meantime I hope the infos here will help some pople to get their shield back without the need to sent it in.
Update 25/12/18: I got TWRP working on 7.2
This is only true for the 2017 model though as I have only this for testing.
Currently creating a backup to the internal storage.
If the restore works then I will upload the new TWRP - for the said model only!
Give me a day or two to fix it for the other models too.
There is progress on the rooting front as well.
Created new scripts for my kitchen to be able to handle the new file_context thing.
A fully pre-rooted and totally unsecure (in terms of ABD, DM-verity and such) is already cooked, just did not dare yet to try it out as I have a real life job too.
As for the pre-rooted firmware:
Things have changed quite a bit with the new kernel in terms of "just adding SU or Magisk".
Magisk might see an update for this problem soon, SU however seems to tally fail on two levels.
So far I was unable to do a full install of the modded firmware.
Flashed all at once and the boot just hangs.
Bootloader, reboot, then the rest seems to work.
At least for the basic install of the system.
If I add SU and busybox the system still ends up with a corrup notice during boot and then it fails.
Tune in over the next few days for progress updates at the end of the thread.
Major developments will be added right here.
Just a matter of finding the last restrictions.
Once that is done Magisk should be possible as well.
Ok, TWRP boot fine, does a backup but fails to restore the system to a bootable state.
Will now check if at least installing a zip works.
Well, it did not, so TWRP has to wait a few more days
I edited post 3 with instructions on how to "unbrick" and go back to 7.1.
Update 27/12/18: A friend of mine found some intersting stuff.
A 7.2 firmware offering a pure Android without any TV stuff but also a full root possible.
I hope he will share his finding here soon or allow me post it all in his name.
For now lets just say: It really works if done the rght way!
Full write rights, installing Magisk modules and all.
All thanks to an undocumented flaw in the device security structures, so even without any hidden backdoors or such LOL
Update: Whiteak was so kind to provide a working root solution in post 36, please check it.
I can confirm it is working as promised.
So the credits for this one go to Whiteak and the credits for the idea and use of the DTB file to Zulu99 - great idea!
To prevent any problems I advise to perform a factory wipe after the install and before the first boot.
Switch to the stock recovery to do this then boot as normal an enjoy.
A complete firmware with the required mods is sitting on my PC just waiting for idiot behing the keyboard to figure out how to pack it properly for flashing.
Once that problem is sorted and also TWRP working again things will get a lot easier.
Annoying update:
I was not able to confirm my web findings on the 7.2 firmwares bootloader but it seems other devices running the same type of kernel and bootloader and a bit lost now.
AVB is fully implemented on the latest level.
(Again I am working on confirming or denying these findings!)
This means any alteration to vital parts of the system will fail with a corruption warning or worse.
Custom recovery access is limited if not fully restricted.
But even if it works you still need a firmware to flash that either is able to disable all this crap, hoping the bootloader alone will allow it, or
to hope Nvidia will provide a future bootloader update with these restrictions removed.
We can not downgrade the bootloader and even if there is some old one out there that would actually be flashable the risk is high to end with a brick anyway.
The DTB, at least in my tests gives us the required system wide write access but I have no information about the AVM verfified boot other than that Zulu99's firmware works.
But if it was compiled with the NVidia developer suite then it will be signed accordingly so the bootloader accepts it.
Could not find any info on how his firmware was actually created.
It gives me the hope though that once I have a fully working TWRP again that my modded 7.2 will work as expected and with no restrictions anymore.
Thanks for the info.
Edit: Will use this post to list options to recover the Shield is all seems lost.
As a result of far too much rom cooking and mods I needed a 100% working way to recover the Shield in case things turn very ugly.
So lets sum up what I define as very ugly when playing with firmwares:
1. Firmware installed but the Shield just hangs on the logo.
2. Firmware installed and now the system is corrupt and even it is boots it takes forever to get around the nag screens.
3. Firmware downgrade attempted but now the Shield won't even boot anymore.
4. Anything that would qualify for a soft brick.
My worst case when I only got a flashing white screen after trying to restore a TWRP backup under 7.2.
There any many way that work for a variety of boot problems but it takes too long to list all cases I encountered with a list of fixes that work or a comment that only the below way works.
So just to be clear here: This is not for any recovery purpose other than fixing what can't be fixed through a factory reset or fresh flashing of the firmware!
1. Get the Shield into Fastboot mode: Connect wired controller and male to male USB cable.
2. Power the Shield up while holding A and B on the controller.
Keep holding until you see the fastboot menu on the screen.
3. Install the 7.1 recovery firmware for your Shield type after unpacking it.
With Fastboot connection working type: flash-all.bat and hit enter.
4. Keep an eye on the progess!
5. Once the Shield is finnished and reboots, hold the A and B buttons on the controller again to enter fastboot mode!
Do not let the Shield boot up other than into the fastboot mode!
6. Lock the bootloader! Fastboot oem lock
Confirm with the controller, then go down and select the recovery kernel.
7. Once the dead droid is on the screen press B on the controller to enter the real recovery.
If B does not work try A
8. Select the factory reset option to wipe all!
9. Once the wipe is done you can boot into 7.1 as normal again.
10. With a bit of chance you might even get directly to the homescreen if the previous setup was completed.
If you need the full seup wizard again and are forced to update to 7.2 then at least the update will work fine this time around.
In case you desire to go back to the 7.1:
If you just finnished the above only to end with the 7.2 then set it up and flash the 7.1 - you won't get the setup wizard again and can skip the update.
If you are on a working 7.2 that was update the OTA way but want to go back:
1. Install the 7.1 firmware.
2. Lock the bootloader.
3. Boot and then skip the update to 7.2.
Any idea what to do if the Shield sticks at the NVidia logo when you select Recovery from Fastboot? I reflashed boot and got the same result.
psycho_asylum said:
Any idea what to do if the Shield sticks at the NVidia logo when you select Recovery from Fastboot? I reflashed boot and got the same result.
Click to expand...
Click to collapse
It won't work from fastboot.
Fastboot operates on a different level and calling the recovery from there lets it end up in nowhere with no access to the system.
You need to boot into recovery through ADB as (for the new model) without a power button and usable hardware buttons we can't get into it otherwise.
Having said that, the fastboot way should still work with an unmodified bootloader.
When the dead droid is on the screen the recovery should be available after pressing the A button on the wired up controller.
But during my tests on 7.2 it did not always work, so you might have to try a few times and also try the B button.
Downunder35m said:
It won't work from fastboot.
Fastboot operates on a different level and calling the recovery from there lets it end up in nowhere with no access to the system.
You need to boot into recovery through ADB as (for the new model) without a power button and usable hardware buttons we can't get into it otherwise.
Having said that, the fastboot way should still work with an unmodified bootloader.
When the dead droid is on the screen the recovery should be available after pressing the A button on the wired up controller.
But during my tests on 7.2 it did not always work, so you might have to try a few times and also try the B button.
Click to expand...
Click to collapse
I have not been able to get to the dead droid screen.
Downunder35m said:
For starters, I uploaded a copy of the 7.2 developer firmware here:
7.2 developer ZIP on Dropbox
It is the full 1.1Gb update and not the 422mb block based one.
(snip)
Click to expand...
Click to collapse
Thanks for posting this, but please note that this firmware is only for the 2017 16GB model and cannot be used with a 2015 or Pro model.
I just got a 7.2.1 update that forced me to update. Wouldn't give me an option to skip it... As soon as I turned on my Shield, it said something about the 7.2.1 update and then rebooted and installed.
I was holding off on updating too so I didn't lose root. Now I'm unrooted and am unable to get Magisk working again until I can get my hands on a 7.2.1 bootloader... Bleh.
Weird, I am not getting the 7.2.1 at all here.
And since yesterday the OTA only tries the block based but not the full image.
AthieN said:
I just got a 7.2.1 update that forced me to update. Wouldn't give me an option to skip it... As soon as I turned on my Shield, it said something about the 7.2.1 update and then rebooted and installed.
I was holding off on updating too so I didn't lose root. Now I'm unrooted and am unable to get Magisk working again until I can get my hands on a 7.2.1 bootloader... Bleh.
Click to expand...
Click to collapse
I was able to downgrade using the 7.2 image after setting up the device on 7.2.1 OTA just make sure you disable automatic updates
Thanks downunder this kind of in-depth info is always appriciated man........i like to learn these kind of things, having bits here and bits there gives a better picture of the whole, while also giving us upto date current info.
Thanks for taking the time to write this :good:
---------- Post added at 07:35 AM ---------- Previous post was at 07:27 AM ----------
Edit
Hi downunder, could you confirm i have this correctly
With no access to fastboot thus no twrp or root, are you implying, assuming your able to inject root into stock firmware, that, i'd be able to flash this stock+root rom in STOCK recovery, which i do have access to?
Edit: im under the impression that stock firmware zips are checked by stock recoveries, so modifying a stock firmware zip tends to fail this check and thus wont install/flash.......which makes me think im misunderstanding here......or just hoping im not
If so, im interested
Edit
i just read your second post which near enought answers my curiousity, so that'll teach me to read beyond the first post before asking answered questions ........even if the post excites me............ahhh, who am i kidding, ill probabably do it again........the equivelancy of a mental post boner........not controllable
Sorry for the disgusting analogy
SyberHexen said:
I was able to downgrade using the 7.2 image after setting up the device on 7.2.1 OTA just make sure you disable automatic updates
Click to expand...
Click to collapse
Did I understand it correctly? You successfully downgraded from 7.2.1 to 7.2?
ErAzOr2k said:
Did I understand it correctly? You successfully downgraded from 7.2.1 to 7.2?
Click to expand...
Click to collapse
Yes,
Just ran flash all from the bootloader. For the newly released 7.2 developer_rooted factory image.
As long as we don't jump to Android 9 we should always be able to downgrade through a full factory firmware.
Once Android 9 comes this might not work anymore due to the massive changes involved for the boot and system checks.
@banderos101: Unless you really did something bad you should always be able to enter the fastboot mode to flash a full firmware.
If I have some time after xmas I will have another look on the options of signing the zip properly or simply to fake it.
Biggest problem will be to generate the corret SHA checksums ince all is installed so I can use the same checksums in the check files.
The bootloader needs them to identify the system and vendor as genuine.
The system needs them to confirm all is actually unmodified as otherwise all fails to boot at some stage.
Modding a proper userdebug firmware is not really that hard, but converting a release version that also is a true and secure user release...
Lets just say that it won't be an easy task.
As it looks like the kernel is a keeper I might have to figure something out unless TopJohnWu won't enjoy a break after his exams and works on a way to get Magisk working with out kernel.
At least I figured out why the recovery trick isn't working for me.
The system partition is not mounted for the sideload mode.
To apply an update the stuff is written directly onto the partition, so no file level access left to play with and break things
In comparison you could say the shield is now like a modern car with keyless operation only.
You know you can start it with ease, if you only could the remote that you left in the drivers seat when you locked the door
SyberHexen said:
Yes,
Just ran flash all from the bootloader. For the newly released 7.2 developer_rooted factory image.
Click to expand...
Click to collapse
Just wondering what is achieved by going back to 7.2?
What do you mean "going back"?
Right now the 7.2 is the official and latest firmware.
I was unable to get my hands in the 7.2.1 but guess it might have been a testversion for certain models only.
I wasted a few hours trying to fix the system image.
First stage was only to get the basic "features" back, like full ADB support, enabling the support to use SU and busybox....
Just what is required to actually allow these nice apps we like to gain root to work.
This backfired badly as right after the start the bootloader complained about the system being corrup and no override to get past this worked.
So of course I then removed the known restrictions from the bootloader...
As you guessed it the damn thing then did not even boot at all, just jumped right into the (locked) recovery mode.
A half decent comparision with my last manual root on a tv box that was a success showed I still did the right things...
If anyone wondered why we needed a new bootloader for the support of smart helpers an some codes stuff:
We didn't as all this could have been done with the 7.1 bootloader as well.
Since my root attempts so far all ended either in disaster or in a root access that failed shortly after/corrupted the system, I took a look of the general kernel changes that were published for other devices.
Before I could find anything meaningful I realised the 4.9 kernel is actually a requirement for Android Pie!
With that info sorted I started digging inti the new "security" features Pie can offer.
I will try to keep it simple and to the stuff that actually concerns us for rooting purposes:
The new boot process with Pie is aimed at being secure from the hardware level up and all the way into the system partion once the boot is completed.
So the hardware checks if the bootloader is actually usable - we had that for a long time, nothing new.
Once the bootloader starts and reaches the point of actually getting somewhere, all partitions required will be checks by either a hash check or a trusted certificate gererated at boot time that is compared to the previous certificate.
Only if that is fine the bootloader will call upon the system and vendor partitions.
The handover of control from bootloader to the system is made far more secure as well.
SELinux is called early on to ensure that only trusted apps and tasks can work but also to all a new control level.
System related apps no longer run as root or with special permissions.
Instead every single app and service runs as its own user!
And under SELinux conditions this means nothing can access anything that it is not entitled to unless included as a user for the other app.
And with that sorted the vendor stuff is called to ensure all hardware and vendor related stuff is still genuine - this include the required certs but also the recovery and bootloader hash codes and certs.
So if something is fishy either SELinux will stop us or the vendor stuff will just overwrite it all.
Once we finally reach the system stage the recovery is checked if called from within the system, if fully implemented it could mean that using an official update on a modded firmware will delete all data as the encryption from the old system is declared invalid.
Sadly it does not stop there because even with full rigths (faked or otherwise) to access the system partition with write access we still can not just change things.
If something belongs to a user (a secure app) than a change will corrupt the system.
To overcome all this without using vulnerabilities that so far no one has found, a compatible userdebug release has to be created from the official user firmware.
DM-Verity needs to be disabled as well as all partition encryption stuff.
The bootloader needs to be adjusted to reflect these changes and the required turst certificates generated and included in both system and boot images.
The only problem here is that the kernel won't allow these changes unless it itself is a userdebug kernel.
After that it is only the little efford to go through about 60 different scripts to remove or redirect the calls for all boot and system security related things.
If then by some chance all this actually boots up and goes all the way into a usable homescreen the entire stuff needs to be secured again.
This time so that the final system has a correct cert and checksum that matches those we need to include in the bootloader.
Anyone knows how to gain full access to the trusted keystore on the 4.9 kernel? LOL
For the moment I don't really care about all the stuff above.
I would be happy to figue out what to make out of these new fstab configurations without the vital partitions listed.
The real aprtitions used have not changed but it is impossible include them in the fastab, doing so causes the bootloader to fail.
Presumably because the kernel realised we try to get around the verification process.
This and some other minor things are also the reason TWRP fails so badly, same for the stock recovery by the way.
Since TWRP is toy a lot us like:
TWRP and 7.2....
Without a system partion in the bootloader fastab TWRP can not mount it.
Same for all other things TWRP needs to mount as it simply does not have the right to access these areas.
To make things worse, we need system access to even start TWRP through fastboot.
So, now matter if we flash or start it through fastboot: The bootloader and system will realise our recovery does not match the checksum.
What does al this now mean in terms a lot more people are able to understand?
Let me try...
Imagine the 7.2 in a running version would be just some encrypted file with a lot of folders in it.
And like PGP or other encryptions software we know there is a private and a public key.
With the public key you can see a lot and use most the encrypted file - but only to a level that is required, nothing above your low level clearance.
For every attempt to write into this file or to make changes we need the private key.
If you follow so far then lets just say the recovery (stock) and Fastboot can be, to some extent, used for this access.
But since every folder in the encrypted file also uses private and public keys it is like tracing a tree.
Although it is getting too long, let me give you the example of just adding SU to the sytem partition:
Adding SU into the system image is no big deal.
Singing this image to get a usable key and including this key into the keystore is.
Assume we would just be able to do it....
SU needs to be called quite early in the boot process.
It then elevates the access level for certain things and also intercepts all root related requests from apps and services.
Except of course those that already had these rights by default.
Problem here is that adding the scripts we need plus changing some others means violating the tree of trust on the device and we get locked out.
Finding a spot to add the required rights for SU might be still possible.
On the other hand it will be impossible to give SU any rights or access to "trusted user" owned parts, files, folders, partitions....
The entire concept of SU just fails.
I will have to check how much of the new features are active in the 7.2 kernel that hinder us.
If I find enough it might be possible it enough to call for a Magisk update.
But I guess it is of little use for just one set of devices, so maybe once more devices on the 4.9 kernel fail to work with Magisk it will be easier to spot a usable pattern.
In case someone else if already working ona mdified system: Please let me know how you made it boot after the changes
Shield Tv 16 2017 - OTA update 7.2.1 Ready for updating
Im on 7.1. I have been waiting for 7.2 developer image, which is now out and just noticed 7.2.1 is available OTA. I'm really confused what to do. I want to keep root without bricking my Shield. Should I Stay with what I have as it is running well.
I am not even sure if it is safe trying to update to dev 7.2 image (or if I would want to) by hooking to computer and using ADB Fastboot tools.
Is there any good reason to update to 7.2 or 7.21? and if so how would I go about doing it? Which program is good for flashing developer images or OTA updates. I used to use flash-fire, which seems to be obsolete now and have heard TWRP is incompatible rooting with SU with OREO updates????
Should I play it safe and stay with what I have rather than experiment and end up with a brick? (wouldn't be the first time)
Anyone know if 7.21 is some-kind of bug fix?
Alot of questions but hope someone has some answers.
Thanks for any info.
"You know you can start it with ease, if you only could the remote that you left in the drivers seat when you locked the door "
My fastboot issue
Yeah, i think i busted the microusb somehow with a faulty usb hub, whenever i plug the usb to my raspberrypi/windows box(for adb/fastboot) now, it turns off all usb ports on the pi aswell as the windows box, even when the shield is unplugged, some sort of earth problem maybe
......all i have is adb over network, adb reboot bootloader simply reboots back to system, adb reboot recovery works though.
ive read that fastboot over tcp(ethernet) had been introduced a couple of android versions ago, but i dont think its been implemented in our shields
infact heres a link
https://www.androidpolice.com/2016/...-capabilities-wireless-flashing-isnt-far-off/
Looks like it needs to be specifically added onto a build
As far as you making a stock root build, if you can, that would awesome, more then awesome, but if it becomes more work then you thought dont worry about it, its not like their making it easy
Also, sounds like 4.9/future android is gonna be a nightmare for root......... having the ability to root so that the option is there to see whats going on in the background of these devices, these devices posessing cameras/microphones/old+latest sensors/personal files/personal info, which reside on our personal beings or in our homes........is just one reason why i dont want to see root go away
So what is the purpose of the developer image of 7.2?
Rather, I know the stated purpose of the developer image, but if it is locked in the way described it sounds like the benefit is negated for typical developers.
(e.g. sometimes I debug an application without permissions in order to benchmark or debug a problem).
For casual users of the shield, using ad blockers and whatnot, is there any benefit to derive from installing the developer rom over stock? Does "adb root" still work?
What is left as the difference. It doesn't sound like they produced a userdebug build of the OS.
Thanks
The 2 new updates are horrible. I have gone back to 7.1. They have crippled my shield. I'll wait for a new update.