Good news everyone!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the lollipop update for the tab4 has just been confirmed to be in development. How long it will take before we can all get it is not known, but it will come out for all sizes of the tab4.
http://www.youmobile.org/blogs/entr...fficial-Android-5-0-2-Lollipop-In-Development
That would be good for getting updated blobs/vendor files but otherwise, Touchwiz can bite my shiny metal ass !
xD
m
TIL : moonbutt is Bender...
If a cell company is saying it is in the works I'm guessing for the non cellular folk it'll be here very soon.
Sent from my Amazon Tate using XDA Free mobile app
It sucks that I'll never get any updates cuz I choose the prepaid route. I haven't even gotten the last 4.4.2 update. No development, so no update option from a talented dev. Woe is me.
Wow, i was lucky because i was just wondering rooting my tab and install some custom roms but i've would lose alot apps and i'd had to go back stock like in 1 month because i want test lollipop
moonbutt74 said:
<Moonbutt is Bender. Behold the glorious revelation>
That would be good for getting updated blobs/vendor files but otherwise, Touchwiz can bite my shiny metal ass !
xD
m
Click to expand...
Click to collapse
You speak wisdom as always. I'm stuck with official touchwiz lollipop on my phone (GS4 Active) and it's just hideous. I mean you can always expect that from touchwiz, but now with all the white, and paler shades of blue and teal it honestly looks like girl colors/designed for a girl's phone. And sorry if that comes off sexist but that's just not the color theme I want at all. Plus G-D it I hate navigating Touchwiz's convoluted navigation, not to mention its stock apps options (file explorer, media players, office suite, etc.) are, as always, inferior in nearly every possible way to the many third-party options out there. Sorry to hijack this thread, but I just felt like someone had to mention the negative aspects of 5.0 touchwiz. AOSP remains as always the better choice for those who prefer real control over their devices.
T,
that's not sexist at all, the colors are abominable, it's a color theme that's suffering from estrogen poisoning. <----that is sexist ! :laugh:
the politically correct crowd can blow. m
xD
I have TW lollipop 5.0 on my Tab S. It's not the best in which I had to theme it myself. I wonder whose idea was to include these bubblegum colors xD
Ill keep my Xposed Framework on ol' 4.4. 5.0 is pointless for the 237p users/owners.
Hi,on samsung updates there is lollipop (5.0.2) for tab 4 10" LTE+WIFI (sm-t535) and only wifi (sm-t530),i have tab 4 8" LTE+WIFI (SM-T335) and i'm impatient for lollipop update!
Android2.1 said:
Hi,on samsung updates there is lollipop (5.0.2) for tab 4 10" LTE+WIFI (sm-t535) and only wifi (sm-t530),i have tab 4 8" LTE+WIFI (SM-T335) and i'm impatient for lollipop update!
Click to expand...
Click to collapse
Good eyes, thanks for that. @moonbutt74 @repey6 @sub77 I was not aware but it appears the official lollipop update is going live for the t535 and t530. Obviously I'm downloading the t530 file already. My reason for bothering you guys is I think someone is going to have to take the images, modem, etc. from the tar and make it into a zip that is flashable with FlashFire, in order to be able update while keeping root. We've done it for my locked-bootloader phone (AT&T S4 Active) so I assume it's doable here, as I assume towelroot can't root lollipop. If somebody more knowledgeable wants to weigh in now, please do...
Edit: User Android21 is referring to this page's info which leads me to believe LP actually is going out over the air....
Editt: @g_ding84 you're also very smart and very good at this crap, just wanted to make sure you see this too, I'm sure the 7.0 crowd will start clamoring for a keep-root update once your updates go live too.
Edittt: In case anyone cares the t530 LP build is region PHE (Spain) and the one for t535 is region NEE (Finland). Idk what effect if any that will have
Editttt: Now downloading both firmware builds (i.e. t530 and t535)
Editttt: I'll have these files shared with you guys most likely by around 8:00 PM (16:00) EDT (midnight, 0:00 GMT/UTC I guess), possibly sooner but no guarantees
They are unlocked boot loader devices unless bought by carrier.... We just need an Odin flashable recovery that suits lollipop from there we would attain root. I am unsure if the current one does or not. For the boot loader locked ones I believe you are quite correct in the use of flash fire.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
They are unlocked boot loader devices unless bought by carrier.... We just need an Odin flashable recovery that suits lollipop from there we would attain root. I am unsure if the current one does or not. For the boot loader locked ones I believe you are quite correct in the use of flash fire.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Sweet that's more or less what my line of thinking was, I just wanted to err on the side of safety (safety of course meaning rootable lol). No matter what, I'm downloading both files and uploading to AFH, that's a given. So what I'm thinking is for the carrier-branded devices, assuming they were able to root on KitKat, they'll need a FlashFire update.
For the unlocked bootloader devices, I'm guessing we keep doing the trick where we Odin flash an older kernel, run towelroot, and then flash the current kernel? I can tell you from actual personal experience this particular method will not work on a locked bootloader going from KK to LP (just so everyone is crystal clear). However with our unlocked bootloaders, my question is, will lollipop boot after flashing a kitkat kernel? I don't know enough about kernels to even know how stupid a question that is, if it is...
thisisapoorusernamechoice said:
Sweet that's more or less what my line of thinking was, I just wanted to err on the side of safety (safety of course meaning rootable lol). No matter what, I'm downloading both files and uploading to AFH, that's a given. So what I'm thinking is for the carrier-branded devices, assuming they were able to root on KitKat, they'll need a FlashFire update.
For the unlocked bootloader devices, I'm guessing we keep doing the trick where we Odin flash an older kernel, run towelroot, and then flash the current kernel? I can tell you from actual personal experience this particular method will not work on a locked bootloader going from KK to LP (just so everyone is crystal clear). However with our unlocked bootloaders, my question is, will lollipop boot after flashing a kitkat kernel? I don't know enough about kernels to even know how stupid a question that is, if it is...
Click to expand...
Click to collapse
Um. . If the devices that have bootloader unlocked already, you could simply flash twrp/cwm then flash supersu zip in twrp. Yeah it will trip Knox but that would be the only way. KK kernels and Lollipop kernels don't mix with each other.
For locked bootloader (att), they need FlashFire.
Sent from my SM-T800 using Tapatalk
Uh, they updated page from in developing to pending... any one have clue what it means?
DUHAsianSKILLZ said:
Um. . If the devices that have bootloader unlocked already, you could simply flash twrp/cwm then flash supersu zip in twrp. Yeah it will trip Knox but that would be the only way. KK kernels and Lollipop kernels don't mix with each other.
For locked bootloader (att), they need FlashFire.
Click to expand...
Click to collapse
This is what I suspected might be the situation. Thank you for letting me know. Files still on the way.
thisisapoorusernamechoice said:
Good eyes, thanks for that. @moonbutt74 @repey6 @sub77 I was not aware but it appears the official lollipop update is going live for the t535 and t530. Obviously I'm downloading the t530 file already. My reason for bothering you guys is I think someone is going to have to take the images, modem, etc. from the tar and make it into a zip that is flashable with FlashFire, in order to be able update while keeping root. We've done it for my locked-bootloader phone (AT&T S4 Active) so I assume it's doable here, as I assume towelroot can't root lollipop. If somebody more knowledgeable wants to weigh in now, please do...
Edit: User Android21 is referring to this page's info which leads me to believe LP actually is going out over the air....
Editt: @g_ding84 you're also very smart and very good at this crap, just wanted to make sure you see this too, I'm sure the 7.0 crowd will start clamoring for a keep-root update once your updates go live too.
Edittt: In case anyone cares the t530 LP build is region PHE (Spain) and the one for t535 is region NEE (Finland). Idk what effect if any that will have
Editttt: Now downloading both firmware builds (i.e. t530 and t535)
Editttt: I'll have these files shared with you guys most likely by around 8:00 PM (16:00) EDT (midnight, 0:00 GMT/UTC I guess), possibly sooner but no guarantees
Click to expand...
Click to collapse
http://metal-build.de/sub77/matissewifi/samsung/T530XXU1BOD8_T530OXA1BOD8_PHE.zip
@sub77
Is this compatible with the 530NU? I dont really care about whether or not the IR Blaster works.
Dudash said:
[MENTION=3132221]Is this compatible with the 530NU? I dont really care about whether or not the IR Blaster works.
Click to expand...
Click to collapse
530NU user here, I would not recommend it, it's always very dangerous flashing things for different models in Odin.
thisisapoorusernamechoice said:
530NU user here, I would not recommend it, it's always very dangerous flashing things for different models in Odin.
Click to expand...
Click to collapse
Yeah I realized it wasn't a ROM when it finished downloading and peaked inside. I saw .zip and assumed it was a ROM. It wouldn't let me flash the .tar in ODIN even if I tried.
Related
Details
User @donovanbrock has uploaded the COMPLETE dump for the GT-I9505G (Google Edition). The dump also includes original PIT, modems (UEUAMFD), and bootloader. This dump is different from the previously leaked dump that many roms were baked from.
Note: this is not yet flashable via ODIN
OP will be updated when new info arises
Download (Dump)
Original
Mirror 1
Mirror 2
Update
A flashable zip of this latest leak has recently became available.
Download (Flashable Zip) Thanks @Jah0n @Trev420
See here (at&t notes & download source) and here (t-mobile notes)
Don't forget to hit the
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
button
source
Thumbs way up. I was wondering when a CLEAN ge rom was going to hit. Everyone has their own version of the GE ROM with their own little "fixes" and signatures all over the meta data.
Now, with that said, will this actually make our AT&T GS4 phones exact replicas of GE? As in, OTA pushed from the settings menu?
mr_blanket said:
will this actually make our AT&T GS4 phones exact replicas of GE? As in, OTA pushed from the settings menu?
Click to expand...
Click to collapse
This has yet to be determined. Hopefully we'll find out very soon :good:
It'd be amazing if we could get a different boot loader like this with this new info! Assuming mf3 users aren't included.
Sent from my SGH-I337 using Tapatalk 2
mr_blanket said:
Now, with that said, will this actually make our AT&T GS4 phones exact replicas of GE? As in, OTA pushed from the settings menu?
Click to expand...
Click to collapse
I too am awaiting to convert my 32GB i337 into the GT-i9505G. As if purchased right from Google's little play ground.:cyclops:
I wish we had the availability of whatever the OEM uses when the phones are coming off the assembly line. Hardware is identical, and forks pretty much to be flashed in either direction, then they slap some identifying bar codes on them.
ERASE i337, and install i9505G, partitioned corrections and all.
It is flasheable on a i9505 ?
LOLWUT they completely removed se linux from the kernel
Might have to put linux back on this beast and see whats up
Scan I flash this to my I9505 with no problems ?
Sent from my GT-I9505 using Tapatalk 4 Beta
abdmid said:
Scan I flash this to my I9505 with no problems ?
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Not yet.. wait till further research from the knowledge devs.
Sent from my SGH-I337 using Tapatalk 2
I'm excited. I'm going to try flashing these bootloaders to the i337 once I get that JTAG box (still in transit - stuck in Germany now? -_-)
Definitely gonna give this a flash when its confirmed safe
Sent from my SGH-I337 using xda premium
come on devs, i want pure google not modified nexus roms +32gb storage
Fully flash-able with i337
Hello, just wondering if this is fully flash-able with the att i337? I know its probably a dumb question just want to make sure. I would like to thank all the devs for developing roms and kernels and such, I got into flashing roms when the evo came out and ever since then always had to have the top android phone out there. since the evo iv had the sensation, galaxy s 4g, galaxy s2, s3, note, note 2 and s4 the only reason im asking this question is because (htc set aside) this is the first galaxy that ive had that had locked bootloader (i believe) and every so often when flashing a rom i get a Kernel source error so i just end up flashing a Ktoonez kernel and 99% of the time fixes the problem. im using twrpr recovery and would like to use CWM but do wanna lose my back ups from previous roms, again, sorry for going on and on and really do appreciate all the devs work. Ive had an xda account for a while but didnt post much so sorry for having 2 questions in one also would appreciate it if someone could be so kind as to point me in the right direction where i could donate to the devs.
thanks
:good:
No one flash this unless you want a possible brick.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
this may be flashable via heimdall, though I'll wait for the devs to inform us first.
Interesting. AMFD modem. I wonder if the modem will be flashable since it seems a newer revision than AMF3 on regular SGH-I337's.
Hopefully the full dump will help in researching work arounds for the locked bootloader.
WoodburyMan said:
Interesting. AMFD modem. I wonder if the modem will be flashable since it seems a newer revision than AMF3 on regular SGH-I337's.
Hopefully the full dump will help in researching work arounds for the locked bootloader.
Click to expand...
Click to collapse
I thought the amf3 modem was the latest modem for 1337? Am I confusing myself here?
Capt said:
I thought the amf3 modem was the latest modem for 1337? Am I confusing myself here?
Click to expand...
Click to collapse
It is the latest for the i337 but with the leak there is a new leaked modem which I'm not sure is or will work for the 337 device.
Sent from my SGH-I337 using Tapatalk 2
Capt said:
I thought the amf3 modem was the latest modem for 1337? Am I confusing myself here?
Click to expand...
Click to collapse
Exactly. AMF3 is currently the latest official modem from AT&T/Samsung for I337. The Modem in this is AMFD, which by the numbering scheme seems newer. Compatible: No idea but newer it seems.
Hello my favorite Community!!!
The following very simple guide will guide you on how to create a 4.3 Based ROM (Official Android 4.3 Base or the earlier leaks) that will have have fully functional wifi and wifi-related functions. This Guide assumes that you are already in the process of cooking your 4.3 Custom Rom but you realize you dont have wifi, or wifi gets stuck all the time. However, it is also for users who want to experiement themselves because as you will see the changes are really simple. At the end of this Thread im providing a flashable. zip file that fixes the wifi issue on the 4.3 Roms...
UPDATE: As of 26 Oct 2013, unfortunately the following steps STILL NEED TO BE DONE in order for anyone to have fully functional wifi when they cook a custom ROM based on the Official Android 4.3 Base (or the earlier leaks):
Note 1: FOR THE EARLIER 4.3 UNOFFICIAL LEAKS YOU NEED BOTH STEPS 2A & 2B
Note 2: FOR THE OFFICIAL ANDROID 4.3 BASE YOU ONLY NEED TO IMPLEMENT STEP 2B
1. WHAT DO WE NEED
- The 4.3 Leak (either MI8 or the latest MJ3) or the Official Android 4.3 MJ5 Base
- A kernel compiled with the latest 4.3 sources (i.e. either ausdim or Kt kernel)
- A 4.3 GE ROM (I used mine http://forum.xda-developers.com/showthread.php?t=2369922)
- Notepad ++
2. PROCEDURE
A. FIRST CHANGE SOME OF THE BUILD.PROP VALUES (Note: With the official Android 4.3.MJ5 base you can skip this step)
. This way we "trick" the phone into thinking it is a 4.2.2. version. I used parts of the MGA build.prop. I chose MGA because it was the last one without the new bootloader. I tried with MI1 but i didnt get as satisfactory result. Below I show the procedure with pictures
I. ORIGINAL BUILD PROP:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
II. MODIFIED BUILD PROP
B. THEN WE NEED TO TAKE CARE OF SOME WIFI FILES
I. Exctract the 4.3 GE ROM and go to system/etc/wifi. Copy the whole wifi folder and paste it in the system/etc directory of your custom Rom of the 4.3 LEAK.
II. From the GE ROM we need 2 more files: From system/bin the "wlandutservice" and " wpa_supplicant" files. Again copy them to the system/bin directory of your custom Rom of the 4.3 LEAK.
C. THAT'S IT WE ARE FINISHED!!!!!
I trully hope this has been helpful!! This COMMUNITY has offered me so much. I feel like im giving something back. This is not a thread for Q+A and please respect that. I think everything I wrote is self-explanatory....:good::good::good:
If you will publish your 4.3 Roms, please give credits for the wifi fix.... No need to pm me or anything like that
LINK: The WIFI "Trick" in .zip form. Just flash via Recovery to make your 4.3 work http://d-h.st/fS2
Brilliant
Thanks
Sent from my GT-I9505 using XDA
...Yet simple. Good job Friedrich.
Enviado do meu GT-I9505 utilizando Tapatalk
The 4.2.2 wifi files also work on the wifi bug thing on 4.3 it's how i got mine fixed
Sent from my GT-I9505 using xda premium
Great job, thanks for it
And you are right, this forum offered a lot for me too so I help where I can every day too.
XDA and the Community are the Best
Sorry if it's a little bit off-topic but I need to say this
GT-I9505 ~ SlimBean
saywhatt said:
The 4.2.2 wifi files also work on the wifi bug thing on 4.3 it's how i got mine fixed
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Excellent partner
So, old bootloader, no knox (no counter, so no 0x0 or 0x1), new 4.3 Rom? This will be excellent...
Sent from my GT-I9505 using tapatalk 4
robertogl said:
So, old bootloader, no knox (no counter, so no 0x0 or 0x1), new 4.3 Rom? This will be excellent...
Sent from my GT-I9505 using tapatalk 4
Click to expand...
Click to collapse
yep yep yep
No bootloader, no modem, no knox
Yes 4.3
friedrich420 said:
yep yep yep
No bootloader, no modem, no knox
Yes 4.3
Click to expand...
Click to collapse
You are the man
Sent from my GT-I9505 using tapatalk 4
so users who have old bootloader can use the 4.3 if i'm correct,
well this is a awesome idea, but are they able to change it back to 4.3 in build prop so other apps only for 4.3 will be available? i don't think degrading the "build.prop" to 4.2.2 is the conclution but i might be wrong, so basically those who uses new bootloader can go back to older firmware? am i right?
Amazing. Thank you
Sent from my GT-I9505 now Free
I hate to have to be the one to do this, but because you did not change the modem or the kernel necessarily is any of this a step towards getting 4.3 on the at&t MF3 sgs4? Not enough people got stuck with this firmware for a real definitive answer to be obvious, or maybe it is and I just don't know enough, but any answer is appreciated.
xerythul said:
I hate to have to be the one to do this, but because you did not change the modem or the kernel necessarily is any of this a step towards getting 4.3 on the at&t MF3 sgs4? Not enough people got stuck with this firmware for a real definitive answer to be obvious, or maybe it is and I just don't know enough, but any answer is appreciated.
Click to expand...
Click to collapse
I cant be certain... Unfortunately i know very little about the other S4 variants...
Maybe if you asked this question in the ROM's thread,, you will get a response. Other users with other variants besides the International one have reported success...
Has anyone tested this with MJ5 yet?
Does it allow us to have fully functional root and Permissive SE Linux status? I want to use Titanium Backup and Wanam Xposed Framework to make Touchwiz slightly less vile.
donalgodon said:
Has anyone tested this with MJ5 yet?
Does it allow us to have fully functional root and Permissive SE Linux status? I want to use Titanium Backup and Wanam Xposed Framework to make Touchwiz slightly less vile.
Click to expand...
Click to collapse
On MJ3 yes...
On MJ5... We will know pretty pretty pretty soon (Larry David reference there)
I am testing this now with MJ5, should know something shortly.
Thanks sir for this, you are awesome...
Sorry, but is it possible to list specifically what the builprop changes are in detail (before and after), because I can't really read them well enough from the images, and I am trying to not make any mistakes.
donalgodon said:
Has anyone tested this with MJ5 yet?
Does it allow us to have fully functional root and Permissive SE Linux status? I want to use Titanium Backup and Wanam Xposed Framework to make Touchwiz slightly less vile.
Click to expand...
Click to collapse
TheAxman said:
I am testing this now with MJ5, should know something shortly.
Thanks sir for this, you are awesome...
Click to expand...
Click to collapse
donalgodon said:
Sorry, but is it possible to list specifically what the builprop changes are in detail (before and after), because I can't really read them well enough from the images, and I am trying to not make any mistakes.
Click to expand...
Click to collapse
SCORE WITH MJ5
About your request i need some time mate...
friedrich420 said:
SCORE WITH MJ5
About your request i need some time mate...
Click to expand...
Click to collapse
Sorry to bother you but I am trying to get a straight answer on some threads.
I have KNOX 0x1 and running MJ3 and its perfect.
I don't care about the KNOX thing because I am in the Netherlands and we can take our phones in for service even if knox is tripped.
I want to upgrade to MJ5 but don't want to mess around with Odin,
Is there a chance of making a Recovery flashable ZIP for MJ5?
I am using TWRP and rooted via CF-Autoroot, latest version.
Thanks in advance.
Daruka said:
Sorry to bother you but I am trying to get a straight answer on some threads.
I have KNOX 0x1 and running MJ3 and its perfect.
I don't care about the KNOX thing because I am in the Netherlands and we can take our phones in for service even if knox is tripped.
I want to upgrade to MJ5 but don't want to mess around with Odin,
Is there a chance of making a Recovery flashable ZIP for MJ5?
I am using TWRP and rooted via CF-Autoroot, latest version.
Thanks in advance.
Click to expand...
Click to collapse
If you are on the international variant go to my Rom's thread (Echoe ROm- check my signature) and soon you'll get a present
Hello everyone, I am in the process of development for the SM-T217A however, I require some information form members who have this device. (mostly for my verification). below is what information i will need so if you are able to provide it that would be much appreciated.
1. Are you rooted? If so what method (kingo, etc).
2. Screenshot of your "Settings- About".
3. Screenshot or picture of your device in "Download" mode. (For verification of some system information).
4. Whether or not you have flashed the official 4.2.2 image from Samsung using Odin.
If you can all bear with me on what may sound like simplistic questions this will go a long way towards some custom development for this device.
My development background is with HTC devices however I recently expanded into the Samsung market and have noticed the lack of development for the AT&T devices (Mostly do to no unlocked bootloaders).
I'm glad to see development for this device!
1. Not at the moment, purchased yesterday.
2. http://i6.photobucket.com/albums/y205/AzN_dM4/Screenshot_2014-03-24-14-02-08_zpsae0a8bdf.png
3. http://i6.photobucket.com/albums/y205/AzN_dM4/CameraZOOM-20140324140339973_zps7a9761c5.jpg
4. Currently running 4.2.2 stock
:good:
Rooted with kingo
Running 4.2.2, not from odin.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SGH-I747 using Tapatalk
good, this confirms we dont have the knox bootloader, at least not until 4.4 comes out
also even tho there are knox components we can remove those without ill effect
I am currently running the current configuration (and the device still shows as official)
Rooted (using kingo app)
init.d support added (not using any boot.img methods)
several init scripts for battery enhancement and performance
a few other various tweaks including xPosed modules
Samsung know applications and folders removed via script.
suggestions and recomendations would be welcome.
Finally! Thanks
Rooted With Klingo I think
Stock 4.2.2
Cstayton
Welcome to the Samsung side of things!
Im rooted using kingo unit came with 4.2.2. If you still need screen shots let me know and ill send some. Have tested for a number of devs doing Samsung roms on other devices. Let me know if you need help with anything you are developing.
Sent from my SAMSUNG-SM-T217A using XDA Premium 4 mobile app
oldbbman said:
Cstayton
Welcome to the Samsung side of things!
Im rooted using kingo unit came with 4.2.2. If you still need screen shots let me know and ill send some. Have tested for a number of devs doing Samsung roms on other devices. Let me know if you need help with anything you are developing.
Sent from my SAMSUNG-SM-T217A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check your PM's
Finally!!!
Thank you so much for devoting to the dev of this device.. please let me know if I can be of any assistance as I will be incredibly eager to help.
my device - sm-t217a on jb 4.2.2
kingo root
Kernal 3.4.0-1446028
Build # JDQ39.T217AUCUAMHC
SELinux status - permissive
boot status type - samsung
if you could get into the bootloader or get custom recovery that would be sweet
I rooted my wifes jflteATT s4 and flashed custom revovery using safestrap because like our t217a's the galaxy s4 out of ATT has locked bootloader... I was wondering If it is possible to create a safestrap or bootstrap type recovery for our tabs?
eddiemoney said:
Thank you so much for devoting to the dev of this device.. please let me know if I can be of any assistance as I will be incredibly eager to help.
my device - sm-t217a on jb 4.2.2
kingo root
Kernal 3.4.0-1446028
Build # JDQ39.T217AUCUAMHC
SELinux status - permissive
boot status type - samsung
if you could get into the bootloader or get custom recovery that would be sweet
I rooted my wifes jflteATT s4 and flashed custom revovery using safestrap because like our t217a's the galaxy s4 out of ATT has locked bootloader... I was wondering If it is possible to create a safestrap or bootstrap type recovery for our tabs?
Click to expand...
Click to collapse
unfortunately I'm not making any progress in this endeavor, ill continue to try different approaches but for now I'm pretty much back at square one.
Nothing wrong with square one! Now all you have to figure out is how to get to square two.
Everyone can wait until you get the right combination.
Sent from my Nexus 5 using XDA Premium 4 mobile app
just throwin this out there
I have an idea. Understand I am not a developer, nor a zip flashing custom recovery android guru by any means. Im a noob that just loves the topic, as you can see this is now only my second post so here it goes.
would there be a way to use the root access to partition the internal sd, then relocate system files apps and data to the primary, allowing you to wipe the secondary disk partition and side load/install the stock rom from the t217s? Kind of like creating a virtual nand and have a dual boot setup? Then we could flash and backup the recovery and take over bootloader?
this is just me daydreaming and feel free to flame as I have no knowledge if the above is possible or not.
I just hope this shows that I am willing and eager to assist the development process any way I can.
lastly I am scared to install xposed framework because with locked bootloader I cant flash recovery and backup. There is almost no information on user experience with xposed on our t217a devices, any feedback pertaining to kernel tweaking without custom recovery or backup would be nice.
thank you very much
eddiemoney said:
I have an idea. Understand I am not a developer, nor a zip flashing custom recovery android guru by any means. Im a noob that just loves the topic, as you can see this is now only my second post so here it goes.
would there be a way to use the root access to partition the internal sd, then relocate system files apps and data to the primary, allowing you to wipe the secondary disk partition and side load/install the stock rom from the t217s? Kind of like creating a virtual nand and have a dual boot setup? Then we could flash and backup the recovery and take over bootloader?
this is just me daydreaming and feel free to flame as I have no knowledge if the above is possible or not.
I just hope this shows that I am willing and eager to assist the development process any way I can.
lastly I am scared to install xposed framework because with locked bootloader I cant flash recovery and backup. There is almost no information on user experience with xposed on our t217a devices, any feedback pertaining to kernel tweaking without custom recovery or backup would be nice.
thank you very much
Click to expand...
Click to collapse
first, what you are proposing is actually capable via the safestrap application (our device is not supported as of yet and likely wont be) so basicaly the answer is no.
as far as xPosed goes, I have been rooted (with kingo app) and running exposed since the day I brought it home from the AT&T store with absolutely no issues what so ever. I have also managed to set this up with init.d support and tweak some battery and performance counters without the need for a insecure boot image.
there is much that this device can do and I have a few additional things to try and may have a test flash in a few days. (first try flashed for me but not for a tester next one hopefully will be more stable.
its just a bit tricky with odin I am used to HTC devices and unlocked bootloaders building an odin flashable tar.md5 with proper signatures in theory should be a simple straightforward process. however it has tripped me up as of today.
Oh Wow!
Thanks for the input on xPosed. As far as the init.d support goes, command line prompt and entry as well as scripting for some reason confuses me. ill need to do more research before I can understand the topic. Do we have an insecure boot.img on our kingo app roots? if not then can we only achieve true root access through init.d support until we can flash a touchable recovery?
Keep up the good work, im impressed that you've had a successful flash. my financials will be looking better here soon and when I can ill definitely donate to the cause. Im no developer by far but if me or my device can be of any assistance let me know.
sm-t217a
Good to see someone wanting to work on these tabs, if you need anything let me know. I can wipe my device and copy all the files, could probably extract the blobs also, I am downloading the cm source as I type this and was going to try and delevope a rom for my other tab 3 the sm-t210r and see if antthing would transfer over, I know the sm-t217a has a better processor with overclock im at 20,000 on antutu, I think if my memory serves me right best I got with the sm-t210r is like 12 or 13,000.
I am still new to dev. Pretty good at the rest of the stuff though, been using and getting familar with ubuntu lately
joestark1981 said:
Good to see someone wanting to work on these tabs, if you need anything let me know. I can wipe my device and copy all the files, could probably extract the blobs also, I am downloading the cm source as I type this and was going to try and delevope a rom for my other tab 3 the sm-t210r and see if antthing would transfer over, I know the sm-t217a has a better processor with overclock im at 20,000 on antutu, I think if my memory serves me right best I got with the sm-t210r is like 12 or 13,000.
I am still new to dev. Pretty good at the rest of the stuff though, been using and getting familar with ubuntu lately
Click to expand...
Click to collapse
as far as what can copy between the two devices, system apps (any non device specific apps may work but most of those will be common between the devices.
its slow going I am able to pull apart the official 4.2.2 rom and manipulate as needed just need to get past a couple of quirks with Odin and hopefully we will be good to go. once I get past the odin flash issues ill definetly be looking for more testers and help with this.
tester for sure
cstayton said:
as far as what can copy between the two devices, system apps (any non device specific apps may work but most of those will be common between the devices.
its slow going I am able to pull apart the official 4.2.2 rom and manipulate as needed just need to get past a couple of quirks with Odin and hopefully we will be good to go. once I get past the odin flash issues ill definetly be looking for more testers and help with this.
Click to expand...
Click to collapse
i am subscribed to this thread now so... Yea whatever you need let me know i am in, I am going to do some hardcore reading tonight and see what i can figure out about getting a custom recovery for these devices, another device that is identical from what i can come up with is the sprint version of the tab 3 sm-t217s.
Thread Closing
I have asked the Mods to close this thread, I will be opening a thread in the Tab3 7.0 Development section in the coming days with some modifications tweaks and some scripting changes. Unfortunately building a Odin Flashable ROM that is stable and usable at this point is not going to happen but i am able to implement several tweaks and cleanups etc thru scripting.
CAUTION with 5.1.1 UpdateG925PVPU2B0F7I've been spending some time reading T-mobiles issues with the update. This isn't a super new conversation, but is probably new to many Sprint users. The update appears have rollback protection, which effects both kernel and bootloader from what they are saying... Which I find slightly confusing since I didn't think that their was a locked bootloader on the US versions (maybe someone can assist with that)
Figured we could start the conversation early for Custom Root/Recovery/etc. users, so that we may save some of us some trouble with Soft/Hard brinks in the next week or so.
This is the thread I've been looking at.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
EDIT:
NO, the bootloader is not locked with the 5.1.1 update.
Rather, "Factory Reset Protection" (an Android thing - not a Samsung thing!) is now an option, which allows you to lock the bootloader yourself, protecting your device from someone installing a custom recovery, wiping your device and making it their own. It makes the device somewhat less valuable, and therefore (supposedly) less likely to be stolen.
The 5.1.1 upgrade looks to be a "permanent" upgrade, meaning we're not able to revert back to 5.0.2 kernels and recoveries.
So, I would suggest to sit tight with your current set up. In order to customize our devices we will need to wait for:
A) Root for 5.1.1
-Root has been achived: http://forum.xda-developers.com/spr...elopment/5-1-1-stock-of7-kernel-root-t3153396
B) Samsung to post the source code for the new kernel.
C) Custom Recovery
-Recovery has been achived:
Once we have the above, we can get back to modding our devices.
If I'm wrong, someone please correct me.
Interesting article, I remember several other older Samsung devices where you could not downgrade bootloaders and modems. IE Galaxy S3, note 3, s5. But there was still root, Roms and the ability to flash kernels. Hopefully there's no need to go back anyway. The kernel thing is something new so I may hold off on upgrading. Thanks for the info
Soooperstar said:
Interesting article, I remember several other older Samsung devices where you could not downgrade bootloaders and modems. IE Galaxy S3, note 3, s5. But there was still root, Roms and the ability to flash kernels. Hopefully there's no need to go back anyway. The kernel thing is something new so I may hold off on upgrading. Thanks for the info
Click to expand...
Click to collapse
This is my first Samsung, so the whole root recovery process was almost too smooth since I've been on the HTC side for 5 years. Unlocking bootloaders, S-off and requesting tokens to push.. Ugh, as must as I likes HTC and Sense, that sucked.
I think I'm holding off as well, untill Sac23/ Ram9200 might have spare time to look over the update first and make sense of it all and could at least get it to where V.2 is right now. But it sounds like the Kernel could be our hold up, without Hybridmax's current support.
wildjeep said:
This is my first Samsung, so the whole root recovery process was almost too smooth since I've been on the HTC side for 5 years. Unlocking bootloaders, S-off and requesting tokens to push.. Ugh, as must as I likes HTC and Sense, that sucked.
I think I'm holding off as well, untill Sac23/ Ram9200 might have spare time to look over the update first and make sense of it all and could at least get it to where V.2 is right now. But it sounds like the Kernel could be our hold up, without Hybridmax's current support.
Click to expand...
Click to collapse
Yea but based off of my years of experience and having Samsung devices, I'm pretty sure that someone will find a way moving forward, but going back probably won't happen. I too had an HTC evo years back lol and I couldn't stand the root process. I feel your pain. But yea it may be wise just to wait for a while on the update
Root added
wildjeep said:
Root added
Click to expand...
Click to collapse
I've been keeping up with the thread. Looks like T-Mobile got it worked out and looks like it didn't affect the international variant. US cellular just got it. Let's see what happens with them
Soooperstar said:
I've been keeping up with the thread. Looks like T-Mobile got it worked out and looks like it didn't affect the international variant. US cellular just got it. Let's see what happens with them
Click to expand...
Click to collapse
I agree. Definitely a step in the right direction.
Any Sprint rep on here that can tell us when the update is going live?? Someone has to know something ..
just heard 6/30.
Sent from my SM-G925P using XDA Free mobile app
Got it today
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G925P using Tapatalk
Poxie said:
Got it todayView attachment 3384936
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
Thank you for the update. Were you rooted before updating?
wildjeep said:
Thank you for the update. Were you rooted before updating?
Click to expand...
Click to collapse
No
Sent from my SM-G925P using Tapatalk
Poxie said:
No
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
That makes sense. Thank you for the confirmation. 5.1.1 is only a stock update for the time being
http://forum.xda-developers.com/showthread.php?t=3083442
International got twrp working for their phones. We will see if someone gets something working for us
Sent from my SM-G925P using Tapatalk
xadidas4lifex said:
http://forum.xda-developers.com/showthread.php?t=3083442
International got twrp working for their phones. We will see if someone gets something working for us
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
Thanks for the update, I'll add that Link to the OP
Q&A for Galaxy Core Prime SM-G360T1 Root?
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Galaxy Core Prime SM-G360T1 Root?. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
root for SM-G360T1
There is a developer option to allow for the bootloader to be unlocked. Would that help get this phone rooted? I desperately need a root for this phone.
yeay me too! any updates?
jgammon1979 said:
There is a developer option to allow for the bootloader to be unlocked. Would that help get this phone rooted? I desperately need a root for this phone.
Click to expand...
Click to collapse
I think that option's only there for the Samsung engineers to update the bootloader and for those who already have root unfortunately, as any changes made to the bootloader without root result in an unbootable device. :/
Sent from my SM-G360T1 using Tapatalk
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002 @bogarty here is some info that will help with making a rooted kernel for the Galaxy core prime the engineer bootloader will only help to not trip knox. The kernel still needs to be selinux permissive and a few other variables in the kernel have to be worked around like the other samsung galaxy phones with lollipop 5.1.1
---------- Post added at 12:50 AM ---------- Previous post was at 12:33 AM ----------
And yes I know the S6 has a exynos possessor and are core prime are qualcomm they are still both Linux base kernels. I'm start looking at other qualcomm base galaxy phones running lollipop 5.1.1 like the note4 and g360 variants compile some info since I won't have my pc for a couple more days but we will have root and custom recovery before Friday who cares if we void the warranty by tripping the knox counter
bremos812 said:
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002 @bogarty here is some info that will help with making a rooted kernel for the Galaxy core prime the engineer bootloader will only help to not trip knox. The kernel still needs to be selinux permissive and a few other variables in the kernel have to be worked around like the other samsung galaxy phones with lollipop 5.1.1
---------- Post added at 12:50 AM ---------- Previous post was at 12:33 AM ----------
And yes I know the S6 has a exynos possessor and are core prime are qualcomm they are still both Linux base kernels. I'm start looking at other qualcomm base galaxy phones running lollipop 5.1.1 like the note4 and g360 variants compile some info since I won't have my pc for a couple more days but we will have root and custom recovery before Friday who cares if we void the warranty by tripping the knox counter
Click to expand...
Click to collapse
I would think the engineer bootloader would be unlocked so you could flash anything, not that it really matters I guess though as we'll likely never see one. I did already make an selinux permissive kernel with superuser and edited init file too that I think should've rooted the device. I even tried packing it into an ODIN file and also a flashable zip, but it doesn't let you boot into Android after flashing a custom anything from recovery or ODIN. I'm with you on the "who cares if we void the warranty" thing for sure. Guess I just wanted to make sure I could still carrier unlock it later with a tripped KNOX, as Samsung said I have to wait 90 days before I can do this. Also, I'm sure you already know that there is an official TWRP for the CORE PRIME already: https://twrp.me/devices/samsunggalaxycoreprimequalcomm.html I've been looking into how to port it though specifically for the SM-G360T1 lately, as pretty much everyone has reported it as non-functional. I figure if I can get a working custom recovery then, in theory, testing should be a breeze.
Well samsung of course gives Lil support for there low end phones no lollipop 5.1.1 source codes for any of the variants while custom recovery will be great I think without a custom kernel will cause boot loop
Sent from my SM-G360T1 using XDA Free mobile app
bremos812 said:
Well samsung of course gives Lil support for there low end phones no lollipop 5.1.1 source codes for any of the variants while custom recovery will be great I think without a custom kernel will cause boot loop
Sent from my SM-G360T1 using XDA Free mobile app
Click to expand...
Click to collapse
I hear ya. Bootloop's not really a big deal anymore though, which is good news for testing. If you get caught in a bootloop just flash my ODIN boot file...or, of course, if you were flashing a recovery when it happened, then just flash the ODIN recovery file. Works like a charm!
http://forum.xda-developers.com/showpost.php?p=62457159&postcount=42
Ok I'm going and getting a new laptop today to being work on a metropcs stock root kernel I'm ready to trim the fat off this phone @bogarty I was reading last night and seen a guy on xda made a tmo kernel for the S5 following Aou and unibase github making changes were need be how is work on the twrp recovery going
Sent from my SM-G360T1 using XDA Free mobile app
Well I figured out why the other TWRP file isn't working for people. Looks like someone just compiled it directly from the generic source for all Core Prime phones without really making any changes. Also looks like they didn't add touch screen support, which is why you can't do anything with it. Made some changes to customize it a bit and add touch, but looks like there may be quite a bit more to be done. Have to start from scratch and work from source as the other TWRP is no good. Have to go out of town though today, so can't do it right now.
Sent from my SM-G360T1 using Tapatalk
Samsung finally released the source code o yeah
Sent from my SM-G360T1 using XDA Free mobile app
Now that Samsung has released the source code will we be seeing a root soon?
Yes, a rooted custom kernel is in the works stay tuned
Sent from my SM-G360T1 using XDA Free mobile app
I cannot wait!
Sent from my SM-G360T1 using XDA Free mobile app
I'll be watching this thread.
ROOT HAS BEEN ACHIEVED courtesy of @ShinySide!!!
Be sure to send him your thanks/donations/etc.
ROOT THREAD IS HERE: http://forum.xda-developers.com/galaxy-core/development/kernel-root-root-sm-g360t1-5-1-1-t3203522
Yes! Finally achieved root and my first time (successfully I might add) that I have ever used odin! Now hopefully some custom roms will come our way (pac-rom....hint-hint!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G360T1 using XDA Free mobile app
mcrue69 said:
Yes! Finally achieved root and my first time (successfully I might add) that I have ever used odin! Now hopefully some custom roms will come our way (pac-rom....hint-hint!)View attachment 3476215
Sent from my SM-G360T1 using XDA Free mobile app
Click to expand...
Click to collapse
Awesome! Yes. We really need a custom "deodexed" rom to be made actually, as Samsung phones require this in order to run the Xposed framework.
Is there any way to remove the Security Warning that continues to pop up after root?
Sent from my SM-G360T1 using XDA Free mobile app
mcrue69 said:
Is there any way to remove the Security Warning that continues to pop up after root?
Click to expand...
Click to collapse
Yes. That was the first question I had too. If you haven't already after root, download SuperSU from the play store and open it at least once. Then, download a root browser and use it to go to the "/system/app" folder. Delete the entire folder in there called "SecurityLogAgent". Make sure to give the browser root permission whenever SuperSU prompts you. After that the security message will not appear.
Sent from my SM-G360T1 using Tapatalk