This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Disclaimer:
The Extreme Syndicate team and it's affiliates are not responsible for your actions or your device if any issues are to arise. You flash this and utilize these files at your own risk. You have been warned!
The Adventure!:
I will not get into any technical details here. Just know that this method has taken me ~1 year from start to finish. I also went through a number of devices during this time (at least 7 devices), even sold my original N9 then somehow ended up with another one before this root method was found. Some of us devs might be a bit burnt out so don't get upset if we are not in here all day every day answering everyones questions. We hope users will help eachother, that is what XDA is all about! Also, if you want more real time conversation/support then please join our Telegram group (link posted below) as this is easier for us to moderate and allows discussion to be had in real time. I don't always check XDA messages or PM's as it can be a lot and very tiresome so your best bet is Telegram!
Also, donations/money is not expected or required but if you feel obliged to share what you can then that would be greatly appreciated! Donations keep me on the grind and sometimes can even help me in acquiring other devices to work on. I had issues with Paypal a while back (SamPWND days) and do not have a Paypal account. I do however have a Venmo and Transferwise accounts that work in most situations.
Venmo - http://www.venmo.com/Thomas-Huntington-10
Transferwise - PM @elliwigy for info to donate using Transferwise.
Now Let's get into the files/method!
Notes:
- This does NOT trip KNOX so don't ask.
- Bootloader is of course still locked.
- This uses some partitions from combo firmware which means 80% battery.
- Each variant will have its own post in its own section. N9 in N9 section, S9 in S9 section, S9+ in S9+ section.. Make sure youre in the right one!
* Variants this should work on are: N960U/U1/W, G965U/U1/W, G960U/U1/W. If you do not have one of these variants then this forum is not for you!
- Initial files/method will leave you on Oreo stock root.
* Some users were successful in running Pie GSI but the initial posts will not include this. Others will do this and maybe down the road threads will be updated.
- It works on latest rev's from rev1 up to the most recent revs.
- As of the initial first release, all variants have an issue with MTP not working, we are working on it however.
- S9 and S9+ also might have some issues with the selfie cam. Also being looked into.
- There will be 3 threads created as this method works on 3 different variants. These groups will be facilitated by the following:
- Note 9 @elliwigy
- S9+ @klabit87
- S9 @jrkruse
- Telegram Support Group for All 3: https://t.me/joinchat/DxwvAlhtzHjg4EI9973BGQ
INSTRUCTIONS:
1. Downloads: https://www.androidfilehost.com/?fid=4349826312261714687
2. In odin folder flash the combo firmware
3. Once combo is booted up run the root bat. When done phone will reboot to download.
4. In odin flash the bootswap.tar.md5 file. What this does is swaps the boot and recovery images which allows system to be mounted rw.
5. Now when done flashing you need to hold the buttons to boot to recovery but since we swapped boot and recovery images it will boot system.
6. Now put your phone in airplane mode. This must be done whenever using Flashfire. Copy the system.img, vendor.img, and ODM zip files to your phone.
7. In Flashfire, choose zip and select the odm zip. Make sure you select the option to mount system. Then choose firmware and choose the system.img and the vendor.img. Then choose data wipe and wipe user and system data (the default choices). Make sure inject super su is NOT enabled. Disable it. Do not let flashfire inject root!!
8.. Now click flash. When finished you will have to hold buttons to reboot to recovery until you see boot animation. You must do this on every reboot. If you do not it will reboot to stock recovery. If it reboots to stock recovery just reboot system and hold buttons to reboot to recovery again.
9. When rom is booted up your computer will not recognize the phone for mtp file transfer. Adb does still work so you can transfer stuff that way (you need to switch to ptp transfer method in the dropdown) or use USB adapter and use a thumb drive.
10. Biometrics do not work so don’t try to setup fingerprint or face recognition.
Some GSI may work. YMMV
ShoutOuts:
@jrkruse - Helping me over the years and for all his contributions.
@klabit87 - Ditto
@me2151 - Ditto
@gsm-CHEN - Ditto
@mweinbach - For always posting my achievements on the XDA News portal as well as giving me someone to troll sometimes when bored.
@ShaDisNX255 - He was our best tester, give him credits for testing out GSI as well!
@everyone else I am forgetting!
ENJOY!
GSI discussion can be found here.
https://t.me/joinchat/CG3OjhX3C5QTnM1uaASHZA
Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Z Fold2 5G BL V1
Fold 5G BL V1-4
Fold BL V1-4
Z Flip 5G BL V1
Z Flip BL V1-3
Note series 20 BL V1
S20 series BL V1
S20 FE 5G BL V1-2
Note 10 series BL V1-5
S10 Lite BL V1-3
Note 10+ 5G N976U BL V1-4
Note 10+ 5G N976V BL V1-5
S10 5G BL V1-5
S10 series BL V1-4
Note 9 BL V1-7
S9 series BL V1-9
Tab S6 BL V1-3
Tab S7 BL V1
Tab S7+ BL V1
A71 5G BL V1-2
A51 BL V1-5
A51 5G BL V1-4
A50 A505W BL V1-A
A50 A505U BL V1-B
S21 BL V1
A32 5G BL V1-3
Tab Active Pro 10.1 BL V1-4
XCover Pro BL V1-7
Meow
Amazing work and I'm always happy to test your work. Take that, Samsung
Glad to see that root is actually possible on the S9+.
I'm not gonna try it just yet cause there are a few things I can't lose like the fingerprint and capped at 80% battery.
Good job on finding this method, I'll keep watching this and see what changes.
Litleck said:
Glad to see that root is actually possible on the S9+.
I'm not gonna try it just yet cause there are a few things I can't lose like the fingerprint and capped at 80% battery.
Good job on finding this method, I'll keep watching this and see what changes.
Click to expand...
Click to collapse
There's likely not going to be a fix for those restrictions (it's the signed kernel which is the key to this exploit), so instead of waiting you're better off getting the G965F version with unlocked bootloader, custom recovery, and no restrictions.
By the way, the flipping of the boot with recovery exploit is simply brilliant!
Why didn't I think of that?! lol
Nice! Good job yo
billa said:
There's likely not going to be a fix for those restrictions (it's the signed kernel which is the key to this exploit), so instead of waiting you're better off getting the G965F version with unlocked bootloader, custom recovery, and no restrictions.
By the way, the flipping of the boot with recovery is brilliant!
Click to expand...
Click to collapse
yea.
im surprised samsung is that sad when it comes to these vulns lol.. even sadder it took me so long before finding it..
hell i even gave up and sold my n9 before getting anpther then it happened within the day practically lol.. was prolly burnt out after a year and missed the obvious
elliwigy said:
yea.
I'm surprised samsung is that sad when it comes to these vulns lol.. even sadder it took me so long before finding it..
hell i even gave up and sold my n9 before getting anpther then it happened within the day practically lol.. was prolly burnt out after a year and missed the obvious
Click to expand...
Click to collapse
To some people, phones are like crack... but instead of smoking it, gotta crack it, not literally but the software.
On a different note, have you noticed how XDA has been more quiet lately than usual... not sure what's up with that. Hmm...
Thank you! Once I backup my stuff I will give it a try... :good:
billa said:
There's likely not going to be a fix for those restrictions (it's the signed kernel which is the key to this exploit), so instead of waiting you're better off getting the G965F version with unlocked bootloader, custom recovery, and no restrictions.
By the way, the flipping of the boot with recovery exploit is simply brilliant!
Why didn't I think of that?! lol
Click to expand...
Click to collapse
Wait, so the G965F would work? I'm currently on the SMG965U1 firmware.
Litleck said:
Wait, so the G965F would work? I'm currently on the SMG965U1 firmware.
Click to expand...
Click to collapse
No. He means the whole device not just the firmware.
Sent from my Pixel 2 XL using Tapatalk
Guys I posted a link up for my s8 battery fix for 80% of any one rooted wants to try
---------- Post added at 02:21 PM ---------- Previous post was at 02:21 PM ----------
elliwigy said:
yea.
im surprised samsung is that sad when it comes to these vulns lol.. even sadder it took me so long before finding it..
hell i even gave up and sold my n9 before getting anpther then it happened within the day practically lol.. was prolly burnt out after a year and missed the obvious
Click to expand...
Click to collapse
That's funny
---------- Post added at 02:45 PM ---------- Previous post was at 02:21 PM ----------
billa said:
To some people, phones are like crack... but instead of smoking it, gotta crack it, not literally but the software.
On a different note, have you noticed how XDA has been more quiet lately than usual... not sure what's up with that. Hmm...
Click to expand...
Click to collapse
Just here in sammy. All the good devices with unlockable bootloaders are hot hot hot ???
TheMadScientist said:
Guys I posted a link up for my s8 battery fix for 80% of any one rooted wants to try
Just here in sammy. All the good devices with unlockable bootloaders are hot hot hot
Click to expand...
Click to collapse
I like it at 80%, hell can you make one with a limit of just 50%? The battery life will last longer. xD jk!
I'll give it a try when I find some spare time.
But seriously what's up with all this quietness here on XDA (not just this thread but all over in general).... a root like this a year ago drew people in by droves... now it's like crickets... one can even hear the chirping. :/
billa said:
I like it at 80%, hell can you make one to limit it to just 50%? xD
I'll give it a try when I find some spare time.
But seriously what's up with all this quietness here on XDA.... a root like this a year ago drew people in by droves... now it's like crickets... one can even hear the chirping. :/
Click to expand...
Click to collapse
I'm sure the lurkers are watching. I am. Just seeing where this takes off, have no interest in trying it
Same here... 80% battery limit defeats the point of rooting. Running a GSI or Oreo is also a big miss...
Kudos to the team tho, for finding this vulnerability!
billa said:
I like it at 80%, hell can you make one with a limit of just 50%? The battery life will last longer. xD jk!
I'll give it a try when I find some spare time.
But seriously what's up with all this quietness here on XDA (not just this thread but all over in general).... a root like this a year ago drew people in by droves... now it's like crickets... one can even hear the chirping. :/
Click to expand...
Click to collapse
There are apps to limit charging all over. Yea. Either the super bowl or they all moved on. Dont know
---------- Post added at 08:19 AM ---------- Previous post was at 08:18 AM ----------
WuNgUn said:
Same here... 80% battery limit defeats the point of rooting. Running a GSI or Oreo is also a big miss...
Kudos to the team tho, for finding this vulnerability!
Click to expand...
Click to collapse
I was getting 8plus hours of sot on my s8 with 80% charge. When I was rooted.
Maybe it's time for me to upgrade finally. I'm still on my s8. 2 + years
They all move over from here to Discord or Slack or Telegram...
That's where all the action is.
The kernel along with the combination firmware itself is what is limiting it to 80%.
Someone with some time and motivation could possibly circumvent it with some crafty work.
Sent from my Pixel 2 XL using Tapatalk
Related
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
Hi,
I don't want to waste your time, but I think this is a proper time to ask a question.
This tablet(s) are 9 months on the market. Tons of ROMs came to see the daylight, every less important variant of this device got AOSP or CM builds for them, and that's awesome! And everybody enjoy their cool tablets, except ... the owners of the best and most important variant - 10.5 LTE. And there is even official T705 CM12 build! Why not for T805?
I feel sorry I don't have any knowledge in programming or porting, neither I have any pleasure in doing it. But there are a lot of great and talented chiefs who love to port and build good ROMs who make a good TW stuff, and a lot of guys who make AOSP for ... WiFi version. Noone is interested in LTE model, and there is a lot of T805 users out there waiting for AOSP release and asking on every Tx00 threads for builds for their devices.
I have a lot of respect for hard work everyone do here, and we all understand everyone of you - talented chiefs here - have limited time and possibilities. I am personally very grateful for your effort. And don't get my post wrong. All it is about is to ask: Why? Why there are CMs, AOSPs for T800, which I think is not so much different from LTE model,and there is NOTHING AOSP for T805....
I think there will be more than only me to greatly ask for attention from great developers of xda, to ask them for xda miracle for us. Please, make something AOSP for T805... please please please! Let us see this:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
We all would be so grateful for your help, to let us feel the Google Experience..
Thank you!
HUGE UPDATE
It looks like we got it! Finally, good working Lollipop with LTE on our amazing devices. Now the Tab S got a new life, with pure Google Experience! For everyone interested, check out our great developer who made a HUGE effort to make this happen (big cudos to AndyT12) and his website with updates and downloads:
http://goo.gl/ODCQ94
AAAND HERE WE GO!
Another AOSP from cool developer deadman96385:
http://forum.xda-developers.com/gal...m-liquidsmooth-v4-1-lollipop-sm-t700-t3092696
Unfortunately LTE still does not work here but they have just the initial build se let's be patient! Thank you!
UPDATE ON NEXT GREAT BUILDS
We are happy to see yet another great build with working LTE! This time it's amazing work from developer Nexorr who managed available sources from NVertigo and AndyT to build this ROM! Check the links below to download the stuff:
http://forum.xda-developers.com/showpost.php?p=61934130&postcount=78
http://forum.xda-developers.com/showpost.php?p=61940915&postcount=84
Thank you Nexorr for your huge effort!
Yes.. I'm interested this project... Available for Betatester on my Sm-t805.... Happy to see Android v5.1.1 full working on this device
T805 is alot different than T800. Nvertigo explained why a while back. One simply cannot build without having the device. In my guessing, more people probably have wifi ones vs lte models in which most devs have Idk. Nvertigo made a thread also on how to build/port. http://forum.xda-developers.com/showthread.php?t=3031278
It requires a ton of work so... yeah.
So there is no hope, I guess...
Btw I thought there are much more interested people in the AOSP. I was wrong, it seems. 248 visitors came across this thread without even a word, so let's say it: buy N9 or eat TW rubbish.
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
callum_88 said:
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
Click to expand...
Click to collapse
Bring him in.
callum_88 said:
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
Click to expand...
Click to collapse
Whoever read the cm12.1 for t800 thread knows about how much time I can spend on development untill November: it's hardly enough to keep up the development for t800.
So: no, I will not develop for a different device for now.
I said MANY times: there is a cm11 development for chagalllte and cm12.1 for klimtlte. Thats a good starting point.
nvertigo67 said:
Whoever read the cm12.1 for t800 thread knows about how much time I can spend on development untill November: it's hardly enough to keep up the development for t800.
So: no, I will not develop for a different device for now.
I said MANY times: there is a cm11 development for chagalllte and cm12.1 for klimtlte. Thats a good starting point.
Click to expand...
Click to collapse
And the questions from the first post still apply.
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
andyt12 said:
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
Click to expand...
Click to collapse
Hi Andrew! It is so great to hear! This is so cool! Thanks for the information. Are you willing to make xda thread also? Thanks!
PS. Is this build working or it is relatively experimental one? I am worried to lose my data or backups etc..
Hi, i have problems with download, it is so slow and then breaks the download fail. Any oher options to download ?
It was so great CM12.1 for the tab T805 LTE...... and great Job Thanks
One question, must i use your twrp or is it ok with the Original twrp i have 5.0.2 on my tab Iron Rom lollipop
Same here, download fail. But anyway, thank you for your effort! Would really like to try it.
Btw backing up efs, in twrp?
I could use a quick HOW-TO, @andyt12:
with both your provided Odin3.07, and my own Odin3.10, I could not graphically locate either your .md5sum file, nor the .zip ROM archive. At least I *could* enter the file/archive names at the Odin text-entry-box...
but that produced another pair of issues:
-although the suffix ".md5sum" isn't recognized, direct-entry of the filename indicates "binary corrupted" or similar
-entering the .zip archive directly results in Odin message-box saying "success 0/failed 1"
I am really, really excited at the prospect of CM12.1 for my tablet (matching my phone). But I seem to be sort of stuck at some basic point. BTW, I already had TWRP-2.8.6.0 installed on my T805, so I left that and did not try your provided version...
Thank-you for you efforts! I deeply appreciate the work you've put into this!
GordP
is this for t-805y or just t-805 ? since u seem from OZ the version i have is from telstra.
This is awesome. I'm so grateful someone is making a CM12 for t805. Will be trying it soon. Do we have a list of known issues/things that still need work?
andyt12 said:
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
Click to expand...
Click to collapse
Please put it in Xda it will be helpful to test and to make solutions to help you in this project
I've downloaded the latest build (as of May 30) and re-uploaded it to Mega (with an md5 file): https://mega.nz/#F!JhsSTahA!sEf03jOCUWHFbQXizOX_lA
DarkDvr said:
I've downloaded the latest build (as of May 30) and re-uploaded it to Mega (with an md5 file): https://mega.nz/#F!JhsSTahA!sEf03jOCUWHFbQXizOX_lA
Click to expand...
Click to collapse
There is any issue or bugs in this rom ?
Cuz there is no info about rom
So, here's what I did/got:
To repeat dev's words:
Make sure you use EFS backup tools (for example, there's one in Play store) to backup your EFS/IMEI partitions somewhere in a safe place (not just on a tablet).
1. Was not able to install Andrew's TWRP (Odin claims it's broken, redownloading the tar.md5 didn't help).
2. Used my own TWRP (latest, from XDA) to wipe system/data/caches, then install the CM12 zip Andrew has created.
3. Installed latest 5.1.x gapps (micro) from here: http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
4. Rebooted
ROM booted just fine, no errors or issues so far.
Bluetooth tested and works.
Wifi tested and works.
Mobile network and data tested and works.
Root, ADB work
USB works - able to see both device storage & SDcard
CPU: usage seems normal, with cores ranging from 200MHz to 1.9GHz. Although I don't see any cores disabling during no load. Not sure if this is normal.
Performance: subjective. To me, device seems a hell of a lot snappier. Transitions, scrolling, app switching - noticeably smoother than on Lollipop TW.
GPU test: tested in a game (hearthstone), performace is the same as on stock ROM, didn't see any difference.
Temperature: max 43C so far, seems the same.
Camera: both front and back cameras work
Battery: device is sleeping fine, no wakelocks. Battery usage completely flattens when it's sleeping, so, in a few days, I'm expecting a good battery life.
Charging: I think it's the same as on stock: around +500mA when device is ON and on a wall charger.
Bug: Samsung's stock docking keyboard: everything works, expect the app switch button.
Bug: In app switcher - there's an error loading the search widget. No big deal, but it's a thing.
Device info screen
Continuing to test other features, but so far, no issues encountered. Getting really freaking excited.
DarkDvr said:
So, here's what I did/got:
1. Was not able to install Andrew's TWRP (Odin claims it's broken, redownloading the tar.md5 didn't help).
2. Used my own TWRP (latest, from XDA) to wipe system/data/caches, then install the CM12 zip Andrew has created.
3. Installed latest 5.1.x gapps (micro) from here: http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
4. Rebooted
ROM booted just fine, no errors or issues so far.
Bluetooth tested and works.
Wifi tested and works.
Mobile network and data tested and works.
Continuing to test other features, but so far, no issues encountered. Getting really freaking excited.
Click to expand...
Click to collapse
Thank you for this info
What about battery and temperature of device ?
And if he used default kernel speed for cpu
Sorry for long questions
Finally what about speed and what is better TW or CM12.1 ?
All the answers before my post ? ??
http://www.theverge.com/2016/3/9/11185872/android-n-developer-preview-features-report
The first preview build of Android N will be released to the public today with new features including a native split-screen mode, according to a report from 9to5Google. Citing an article from Ars Technica that was pulled after publication, 9to5Google says that the preview version of Android N includes a redesigned notification panel (with notifications that span the full width of the screen, and an edit button for quick changes), and improvements to the operating system's Doze feature, which will reportedly save battery whenever the screen turns off.
THERE'S ALSO A 'PICTURE IN PICTURE' MODE REPORTEDLY COMING
The biggest addition though, seems to be a new split-screen mode for multitasking. This reportedly works on both phones and tablets, and, like other features included in the preview, will be given to developers to test before it's released to the public later this year. 9to5Google says that Ars Technica also reported the existence of a new "picture in picture" mode which sounds similar to that in iOS 9, letting users shrink windows to a corner of their screen while browsing other apps.
The original Ars story also reportedly said that the preview will be available for the Nexus 6P, Nexus 5X, Nexus 6, Pixel C, Nexus 9, Nexus Player, and the General Mobile 4G. Google is also said to be launching a new "Android Beta Program." All of this information is extremely provisional at the moment, but if the Ars Technica report is true, we can expect to hear more about Android N — and its new features — some time soon.
I would be surprised if it actually releases today, but one can hope!!
It's out! http://storage.googleapis.com/androiddevelopers/shareables/preview/shamu-npc56p-preview-54b13c67.tgz
Currently unlocked bootloader and running twrp 3.0
That being said how would I go about installing this image? The same way as the other images? Also, if I do this, will I be able to revert back?
Developer preview? It's still functional as a phone?
Awesome, thanks! I just downloaded the Shamu preview from http://developer.android.com/preview/download.html. Has anyone extracted and installed the images on their rooted 6.0.1? I'd rather not be the first, lol!
Official Release Page:
https://developer.android.com/preview/index.html
Having an OTA of the N preview is Awesome! I want to try it as soon as the site is availble, but I'm not sure how friendly the N preview will be for project fi this early. anyone else on Fi going to try the preview?
Flashable zip or it isn't true
matthew2926 said:
Flashable zip or it isn't true
Click to expand...
Click to collapse
give some time someone will make one
Cobra11Murderer said:
give some time someone will make one
Click to expand...
Click to collapse
Haha yea, I just wish I knew how to make one myself...oh well
I wasn't expecting that, well safe to say this will be last of the preview for us. Safe to say folks with the OG Nex5 won't get android N
---------- Post added at 08:11 PM ---------- Previous post was at 08:11 PM ----------
Any changes to the launcher?
This flashes just like a regular Nexus image right ? aka unzip, fastboot, etc, etc..............
md1008 said:
I wasn't expecting that, well safe to say this will be last of the preview for us. Safe to say folks with the OG Nex5 won't get android N
---------- Post added at 08:11 PM ---------- Previous post was at 08:11 PM ----------
Any changes to the launcher?
Click to expand...
Click to collapse
eh probably but it can be ported over just like any other rom
mikeprius said:
This flashes just like a regular Nexus image right ? aka unzip, fastboot, etc, etc..............
Click to expand...
Click to collapse
Yup, the usual img`s flashed in fastboot
mikeprius said:
This flashes just like a regular Nexus image right ? aka unzip, fastboot, etc, etc..............
Click to expand...
Click to collapse
In suggest wait for sometime and someone will surely give flashable zip... Then give a try.... Rest your own wish.....
Sent from my Nexus 6 using Tapatalk
Probably the coolest features, for me anyway, is built-in options to calibrate the display color (in System UI Tuner) AND change the DPI (in Display settings). I'm not sure if these will make it to the final build, but I really do hope so.
PS: you need to sign up for the android beta program to actually receive OTA updates https://g.co/androidbeta
as stated here: http://developer.android.com/preview/overview.html
deeplyyoung said:
In suggest wait for sometime and someone will surely give flashable zip... Then give a try.... Rest your own wish.....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I don't mind if I have to fastboot it vs. TWRP as a .zip, but I've been flashing out the yin-yang and I still have a few ROMs I want to try LOL. I'll get to this eventually....see how the feedback is first....plus I "need" root, not want...."need"...................LOL
mikeprius said:
I don't mind if I have to fastboot it vs. TWRP as a .zip, but I've been flashing out the yin-yang and I still have a few ROMs I want to try LOL. I'll get to this eventually....see how the feedback is first....plus I "need" root, not want...."need"...................LOL
Click to expand...
Click to collapse
mind that it will encrypt your device
The build.prop wifi tether method doesn't seem to work with the N preview at least in the traditional way. Has anyone managed to get it to work?
@jcadduono - http://forum.xda-developers.com/showpost.php?p=68223333&postcount=5
sources: https://github.com/jcadduono/android...e_zte_ailsa_ii
kernel: https://github.com/jcadduono/android...mmits/twrp-6.0
@Unjustified Dev
TWRP: https://github.com/TeamRegular/android_device_zte_ailsa_ii
A user on the Chinese ZTE forums has created a github with the Axon 7 kernel code in it based on the A2017U B18 kernel dump.
http://www.myzte.cn/thread-272111-1-2.html
https://github.com/snowwolf725/ZTE_Axon7
TeutonJon78 said:
A user on the Chinese ZTE forums has created a github with the Axon 7 kernel code in it. Seems based off of the A2017U kernel dump.
http://www.myzte.cn/thread-272111-1-2.html
https://github.com/snowwolf725/ZTE_Axon7
Click to expand...
Click to collapse
ZTE have the kernel uploaded. (been up for quiet a while now)
http://opensource.ztedevice.com/
Under smartphone - ZTE A2017U
DrakenFX said:
ZTE have the kernel uploaded. (been up for quiet a while now)
www.opensource.zte.com
Under smartphone - ZTE A2017U
Click to expand...
Click to collapse
Yes, I've had since then. However, this is all github'ed, compile tested, and ready for forking.
We also have @jcadduono device tree and kernel posted from his TWRP work: http://forum.xda-developers.com/showpost.php?p=68195475&postcount=17
anks329 said:
We also have @jcadduono device tree and kernel posted from his TWRP work: http://forum.xda-developers.com/showpost.php?p=68195475&postcount=17
Click to expand...
Click to collapse
Indeed, I recommend folks clone this:
https://github.com/jcadduono/android_kernel_zte_msm8996/commits/stock-6.0
It's merged into CAF and allows future CAF merges without any issues. I updated it just the other day. Very clean kernel from ZTE, I've been really impressed.
From my stock-6.0 branch you can just run ./build.sh to compile a Image.gz and ./dtbgen.sh is automatically run after build to create a dtb.img.
I dont recommend using Image.gz-dtb as dtb building was not correctly set up by ZTE and I haven't bothered fixing it. Separated dtb.img works great though.
DEFCONFIG=zte_defconfig
DEVICE_DEFCONFIG=device_ailsa_ii
Otherwise you can use opensource-caf branch which is pure ZTE with no build modifications or scripts from me.
As for flashing kernels you build, check out LazyFlasher installer at:
https://github.com/jcadduono/lazyflasher
It will dynamically replace kernel image and dtb, and has a folder to put patch shell scripts. dm verity and forced encryption disabling already included as an example. Supports LZ4, Gzip, Bzip2, and LZO so far. Readme has more info. Avoids the need to constantly update ramdisks, and other branches have examples of things like SuperSU policy mod.
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Thanks a lot for all the info!
@TeutonJon78 Maybe it would be beneficial to add these infos to the OP?
So...now we have two competing TWRP/device tree setups. @jcadduono and @Unjustified Dev it might make sense to keep them similar as make sure there aren't competing versions running around and making support harder.
Edit: I also updated the title of the thread to reference a more generic change -- just listing all known github resources.
grujildo said:
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Click to expand...
Click to collapse
Well first of all you need the cellphone but it is heavily back-ordered, you can pre-order it now and you might or might not get it on 09/09/16.
I pre-ordered a month ago so I'll get my Gray Axon 7 on monday 08/22/16 (already have the tracking number), I would be willing to sacrifice it (selling it to you) if you want it, for the full price of course ($400 plus shipping). No means to sell anything, I'm not here to sell phones BUT if it is for a developer I'll do it and sacrifice a couple more weeks of wait time. All for the team.
grujildo said:
Hey guys, I am a developer thinking of buying this great cell phone. I've never tried to develop kernels or ROMs but I would love to learn and contribute to this community.
How could be the easiest way to learn and to start working in things related with this phone?
Thanks.
Click to expand...
Click to collapse
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
This would be the best place to start learning Rom building.
Jose-MXL said:
Well first of all you need the cellphone but it is heavily back-ordered, you can pre-order it now and you might or might not get it on 09/09/16.
I pre-ordered a month ago so I'll get my Gray Axon 7 on monday 08/22/16 (already have the tracking number), I would be willing to sacrifice it (selling it to you) if you want it, for the full price of course ($400 plus shipping). No means to sell anything, I'm not here to sell phones BUT if it is for a developer I'll do it and sacrifice a couple more weeks of wait time. All for the team.
Click to expand...
Click to collapse
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Recon Freak said:
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
This would be the best place to start learning Rom building.
Click to expand...
Click to collapse
Hey thanks Recon Freak. Are you going to start developing for this phone? Who are the developers that want to be involved porting CM for the Axon 7.
It would be great to have a master dev on porting ROMs and lp him with the process. Otherwise are there any devs interested on porting CM to this phone?
Thanks.
grujildo said:
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
Hey thanks Recon Freak. Are you going to start developing for this phone? Who are the developers that want to be involved porting CM for the Axon 7.
It would be great to have a master dev on porting ROMs and lp him with the process. Otherwise are there any devs interested on porting CM to this phone?
Thanks.
Click to expand...
Click to collapse
I wish I had the time and skilz. I can build roms and tweak stuff, but that's it. I know the processes but time and knowledge are not on a 44 year old father of two's side. Tree development is best left to the young and knowledgable.
grujildo said:
Hey thanks bro, don't worry. I just checked in Amazon and they are announcing that they will have stock on the 22 August, so maybe I will buy it there.
Click to expand...
Click to collapse
I just ordered one yesterday and it will arrive 8/25, but seems that they are already out of stock by now... 1 to 2 months is the status now
Recon Freak said:
I wish I had the time and skilz. I can build roms and tweak stuff, but that's it. I know the processes but time and knowledge are not on a 44 year old father of two's side. Tree development is best left to the young and knowledgable.
Click to expand...
Click to collapse
Nice, If I managed to get the phone early I will tell you and we'll be able to port CM for sure
---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------
Gachmuret said:
I just ordered one yesterday and it will arrive 8/25, but seems that they are already out of stock by now... 1 to 2 months is the status now
Click to expand...
Click to collapse
Yes ****, I just saw. Anyone know another way to get the phone?
grujildo said:
Nice, If I managed to get the phone early I will tell you and we'll be able to port CM for sure
---------- Post added at 08:05 PM ---------- Previous post was at 08:05 PM ----------
Yes ****, I just saw. Anyone know another way to get the phone?
Click to expand...
Click to collapse
There is some on Ebay right at the $400 mark, that's how I planned to sell you mine in case you wanted it.
So, for those who know don't know already, a new zero-day (CVE-2019-2215) was recently found that applies to a majority of devices that run Oreo and higher, and a PoC application created by Grant Hernandez has been made to demonstrate the potential of this exploit when it comes to rooting. The code of this PoC application has been released onto GitHub and you can check it out in the links below, and maaaaaybe this means that the code can be customized to work on Snapdragon Samsung devices (no idea about Exynos) as this has been tested only on Pixel 2 devices, and in my own attempt in running the app, the process hangs after a few seconds. Sadly, there are a good amount of downsides with this PoC, mainly that Magisk is installed in core-only mode, and installed without a patched boot image. According to Grant, installing other Magisk environments and or updating it can possibly cause DM-Verity and you'd need to do a clean install.
I just wanted to share this with you guys, maybe we can utilize this for the greater good, and hopefully get some stuff going for Samsung devices with this as the base.
PS: The October security update patches this vulnerability, so if you already updated, yikes.
Related links
https://github.com/grant-h/qu1ckr00t
https://github.com/kangtastic/cve-2019-2215/blob/master/cve-2019-2215.c
The PoC of Hernandez manipulates kernel data structures, the user process credentials, that are protected by Samsung real time kernel protection (RKP). Normally, the PoC should therefore not work on Samsung devices, or am I wrong with that?
The original PoC was reported to work on S8 and S9. But i fear this was only due to the PoC did not trigger RKP. Will have a look at the original PoC, to assess that ...
i think the Samsung Knox version is decisive. This document states, RKP only protects kernel data structures on selected devices: (search for Real-time Kernel Protection (RKP))
In the 2018 version this comment is missing, indicating newer Knox versions protect kernel data structures on all devices: (Search for Knox Deep Dive: Real-time Kernel Protection (RKP))
In this case the PoC of Hernandez will not work.
Sorry this is pretty unrelated, but would it be possible to use this on a new lg g8 on september patches? Haven't had any luck asking in forums over there hoping this forum is a bit more active. Thanks
antintin said:
Sorry this is pretty unrelated, but would it be possible to use this on a new lg g8 on september patches? Haven't had any luck asking in forums over there hoping this forum is a bit more active. Thanks
Click to expand...
Click to collapse
It's kinda active here but I wouldn't hold my breath waiting for help with an LG in a Samsung note 9 forum tbh.