Like all of you who purchased this product since it's release in Spring 2012, I/we have all been awaiting an update from ICS 4.0.4 to JB. And up till now it hasn't happened.
Over the last 8 months I have been in contact regularly with AU's tech support to find out when it will be released and which version of JB it will be. The answer has always been;" we are working on it"; "we don't want to make any mistakes, since an update on another phone was a poor release", etc.
Well today I was browsing through Joshin and saw the spects of the new Galaxay Note 3 KDDI AU has just release. It's OS? JB 4.3. Yahoo I thought, we're going to get our update.
So I go to my local AU shop, where I bought my phone and showed them a copy of the new Note 3 specs and asked when will the update roll out for the Galaxay S3 SCL21 Progre? Answer direct from a Technical Services Manager: "We have never had any intention to release an OS update beyond ICS 4.0.4, because by the time your contracts run out you'll be wanting the Galaxy S4".
WTF! They have never had any intention and just thought that we would roll over and take it up the arse and just by the next version.
Well I'll tell you what I'm going to do, and I told the Service Rep the same.
When my contract runs out I'm going to DOCOMO. Their customer service is way better than AU's, the range of their XI LTE is much broader and faster than Au's (ever had no bars next to a DOCOMO user with full bars?), and they give their android users rapid, regular updates.
KDDI AU needs to be taught a lesson in company ethics. If every KDDI AU Galaxy S3 user changed over to DOCOMO at the end of their contract, they would get the message. DON'T SCREW YOUR CUSTOMER BASE!
***************************************************
On a side issue, since we are not going to get our update, I've been researching possibilities for a custom stock ROM to bring us at least up to JB 4.2.2 is to use Verizon's current stock ROM since it has the same ROM structure and specs as the Progre. I'm a complete novice but if there is anyone willing to assist I have the Stock ROM, which seems to have been removed from SamMobile for some reason.
Confused what is the question .
There is no question.
This is an announcement. And information sharing post.
firechild said:
There is no question.
This is an announcement. And information sharing post.
Click to expand...
Click to collapse
is it for GT-i9300/i9305 ?
This is for the KDDI AU SCL21 also known as the Progre.
After a lot of searching I found it has exactly the same specs as the Verizon SGH-1535.
That is a Qualcomm MSM8960 Snapdragon 1.5GHz Dual-core with the Adreno 225 GPU.
Therefore the JB4.2
2 for the Verizon should be compatible with the KDDI AU Progre, with a little tweaking.
firechild said:
This is for the KDDI AU SCL21 also known as the Progre.
Click to expand...
Click to collapse
This forum is not for this device....
firechild said:
Verizon SGH-1535.
Click to expand...
Click to collapse
Nor is it for this. This is the GT-i9300 forum which has no specs the same as the verizon S3.
Also Q&A is for questions and answers, not announcements.
Suggest using the report /!\ button to request a moderator review your post and move it to wherever is correct
rootSU said:
This forum is not for this device....
Nor is it for this. This is the GT-i9300 forum which has no specs the same as the verizon S3.
Also Q&A is for questions and answers, not announcements.
Suggest using the report /!\ button to request a moderator review your post and move it to wherever is correct
Click to expand...
Click to collapse
Wrong... This is the sch-i535 forum bud.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
tylerlawhon said:
Wrong... This is the sch-i535 forum bud.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
This thread was moved to our forums.
Sent from my SCH-I535 using Tapatalk 4
Thanks to the moderator
Thank you for the help in giving this announcement a proper home.
Since I haven't used the forums since we were doing the translations for the Softbank HTC X01HT Windows phone way back in the early 2000's, the forum has become a lot more diverse.
So I sincerely apologize for the original incorrect placement.
Thank you you again.
Creating a KDDI AU Galaxy S3 SCL21 (Progre) JB 4.2.2 ROM
If there are any developers that would like to assist in modding the Verizon SGH-1535 JB 4.2.2 ROM to suit the KDDI AU Galaxy S3 SCL21 (Progre), any assistance or pointers would be appreciated.
My initial thoughts are to take the I535VRBMF1_I535VZWBMF1_VZW.zip extract the files;
aboot.mbn
boot.img
cache.img.ext4
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
system.img.ext4
And replace NON-HLOS.bin and recovery.img from the current KDDI AU Galaxy S3 SCL21 (Progre) ROM (SCL21KDALJD_SCL21KDIALJD_KDI).
Now as I've said previously I am a complete novice to ROM cooking. So would this be a viable solution, or would it need to be done differently?
Our MF1 ROM is only 4.1.2 by the way.
Oh I was under the impression that it was 4.2.2.
4.1.2 is better than 4
0.4.
tylerlawhon said:
Wrong... This is the sch-i535 forum bud.
Click to expand...
Click to collapse
Not when I wrote it, it wasn't
firechild said:
If there are any developers that would like to assist in modding the Verizon SGH-1535 JB 4.2.2 ROM to suit the KDDI AU Galaxy S3 SCL21 (Progre), any assistance or pointers would be appreciated.
My initial thoughts are to take the I535VRBMF1_I535VZWBMF1_VZW.zip extract the files;
aboot.mbn
boot.img
cache.img.ext4
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
system.img.ext4
And replace NON-HLOS.bin and recovery.img from the current KDDI AU Galaxy S3 SCL21 (Progre) ROM (SCL21KDALJD_SCL21KDIALJD_KDI).
Now as I've said previously I am a complete novice to ROM cooking. So would this be a viable solution, or would it need to be done differently?
Click to expand...
Click to collapse
Interesting, I had the same idea, but never followed up b/c it seemed troublesome. I had asked about how to extract files from ROMs on android stackexchange but never got a reply. If you have an idea of how to do it, I could give it a shot.
Extracting Files from a ROM
filmost said:
Interesting, I had the same idea, but never followed up b/c it seemed troublesome. I had asked about how to extract files from ROMs on android stackexchange but never got a reply. If you have an idea of how to do it, I could give it a shot.
Click to expand...
Click to collapse
It's fairly simple really to extract the individual files from a ROM. If you're using Windows based OS you can extract with WinRAR (Google it if you don't already have it)
When you first open the zip file with WinRAR you will see 2 files, the .dll file is unimportant it's the I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 file you'll be using.
Double click on this and after a while another WinRAR windows opens, again with the file I535VRBMF1_1152558_REV09_user_low_ship.tar.md5, but when you double click this you will see the ROM file structure.
IF YOU DON'T HAVE A COPY OF THE SGH-I535 (4.1.2) ROM YOU CAN DOWNLOAD FROM HERE:
http://www.androidfilehost.com/?fid=23125694133305576 (Thanks to Senior Member, DarkMenace for providing a download link)
IF YOU DOWNLOAD FROM HERE PLEASE GIVE DarkMenace SOME THANKS!
Of course if you're running Unbuntu or similar the extraction is just as easy using either a terminal or Gnome GUI.
Then I guess filmost it's just a matter of replacing the recovery.img and NON-HLOS.bin from the KDDI AU Galaxy S3 SCL21 Progre ROM into the Verizon ROM.
Does That help you in any way?
Adding to the above Post
To view the contents of each file is easily done using Unbuntu. But if you're using Windows;
Read this thread by Forum moderator rwilco12:
http://forum.xda-developers.com/showthread.php?t=2138885
And remember to give thanks.
firechild said:
It's fairly simple really to extract the individual files from a ROM. If you're using Windows based OS you can extract with WinRAR (Google it if you don't already have it)
When you first open the zip file with WinRAR you will see 2 files, the .dll file is unimportant it's the I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 file you'll be using.
Double click on this and after a while another WinRAR windows opens, again with the file I535VRBMF1_1152558_REV09_user_low_ship.tar.md5, but when you double click this you will see the ROM file structure.
IF YOU DON'T HAVE A COPY OF THE SGH-I535 (4.1.2) ROM YOU CAN DOWNLOAD FROM HERE:
http://www.androidfilehost.com/?fid=23125694133305576 (Thanks to Senior Member, DarkMenace for providing a download link)
IF YOU DOWNLOAD FROM HERE PLEASE GIVE DarkMenace SOME THANKS!
Of course if you're running Unbuntu or similar the extraction is just as easy using either a terminal or Gnome GUI.
Then I guess filmost it's just a matter of replacing the recovery.img and NON-HLOS.bin from the KDDI AU Galaxy S3 SCL21 Progre ROM into the Verizon ROM.
Does That help you in any way?
Click to expand...
Click to collapse
I'm on Linux actually, and I should probably clarify. I was trying to figure out how to extract APKs. The img files are no problem. Also, instead of porting to Stock Verizon, I am thinking to port to a Cyanogenmod rom for the Verizon SCH-I535.
Today I figured out how to create a deodexed version of the SCL21 stock rom downloaded from sammobile. I have created several CWM compatible images, but got a status 0 during flashing. It took me awhile to track down the cause. Hopefully this last image I created will flash properly, but I won't be able to tell until later tonight. If it's successful, then I'll look at porting to Cyanogenmod.
filmost said:
I'm on Linux actually, and I should probably clarify. I was trying to figure out how to extract APKs. The img files are no problem. Also, instead of porting to Stock Verizon, I am thinking to port to a Cyanogenmod rom for the Verizon SCH-I535.
Today I figured out how to create a deodexed version of the SCL21 stock rom downloaded from sammobile. I have created several CWM compatible images, but got a status 0 during flashing. It took me awhile to track down the cause. Hopefully this last image I created will flash properly, but I won't be able to tell until later tonight. If it's successful, then I'll look at porting to Cyanogenmod.
Click to expand...
Click to collapse
You're status 0 could be due to CWM issue: I found this post http://forum.xda-developers.com/showthread.php?t=2154762 to create odin flashabale ROMS (I used this to create a backup of SCL21's recovery.img.tar.md5 compatible with Odin and had no problems. Prior I had the status O issue . Perharps that thread will help
You're a lot further along cooking than I am. So have you been able to created a 4.1.2 ROM (or greater than) for the SCL21?
And with porting to Cygenmod, what's the idea behind that?
Extracting the APKs doesn't Titanium backup deal with that?
firechild said:
You're status 0 could be due to CWM issue: I found this post http://forum.xda-developers.com/showthread.php?t=2154762 to create odin flashabale ROMS (I used this to create a backup of SCL21's recovery.img.tar.md5 compatible with Odin and had no problems. Prior I had the status O issue . Perharps that thread will help
You're a lot further along cooking than I am. So have you been able to created a 4.1.2 ROM (or greater than) for the SCL21?
And with porting to Cygenmod, what's the idea behind that?
Extracting the APKs doesn't Titanium backup deal with that?
Click to expand...
Click to collapse
Yeah I have created packages for use with Heimdall (too lazy to VM windows just to use Odin). And actually I think Heimdall is way easier and safer to use.
Anyway, no I haven't worked with anything other than the stock rom. If I can get this to work, then I'll think about other things.
The idea behind porting a Cyanogenmod rom is that its lighter and easier to port (at least from the looks of it). Most custom roms come deodexed (single file apks) so if we have a working deodexed stock rom, we could try copy pasting relevant files, and deleting unnecessary bloat.
Technically we could still try simply replacing certain image files from the verizon stock rom, but I the way I have been going about it is safer and allows for more fine tuned control. Besides, even if the SCL21 and SCH-I535 are basically the same spec, if its as easy swapping certain images files out, someone should have made it by now. For the record though, the SCH-I535 and SCL21 are not only very similar hardware wise, their partition layout from what I have noticed is basically the same.
See what you mean.
filmost said:
Yeah I have created packages for use with Heimdall (too lazy to VM windows just to use Odin). And actually I think Heimdall is way easier and safer to use.
Anyway, no I haven't worked with anything other than the stock rom. If I can get this to work, then I'll think about other things.
The idea behind porting a Cyanogenmod rom is that its lighter and easier to port (at least from the looks of it). Most custom roms come deodexed (single file apks) so if we have a working deodexed stock rom, we could try copy pasting relevant files, and deleting unnecessary bloat.
Technically we could still try simply replacing certain image files from the verizon stock rom, but I the way I have been going about it is safer and allows for more fine tuned control. Besides, even if the SCL21 and SCH-I535 are basically the same spec, if its as easy swapping certain images files out, someone should have made it by now. For the record though, the SCH-I535 and SCL21 are not only very similar hardware wise, their partition layout from what I have noticed is basically the same.
Click to expand...
Click to collapse
filmost - you are a hell of a lot more knowledgeable than me in this. For one thing I wouldn't even know how to compare the partition layout.
As you may have guessed I'm more knowledgeable about windows based, so haven't tried hemdal. As for someone else already have done it, I think it's due to to the smaller user base with the SCL21 than the DOCOMO variations
which are based on the international version.( It seems only KKDI AU, Verizon and Sprint went with the Qualcomm Chip ,whilst the others went with the Exynos chip)
Back to ROMS, have you looked at Android Kitchen?
http://forum.xda-developers.com/showthread.php?t=633246
I just haven't had the time as a house dad with a chronic pain syndrome (can't sit in front of the PC for long periods)
Perhaps this will allow the more fine tuning your looking for.
I actually been looking at SlimROM http://www.slimroms.net/ as an ulternative down the road for a lighter ROM. Have you had a look at them?
Related
dsixda's Android Kitchen - Now for Samsung Galaxy SII Skyrocket
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S2 Qualcomm MSM8660-based (non-Exynos) custom ROMs. This also applies to the following devices:
AT&T Skyrocket
T-Mobile SGH-T989
Telus Galaxy SII X
Rogers Galaxy SII LTE
Bell Galaxy SII HD LTE SGH-I757M
Galaxy Note SGH-I717
IMPORTANT: If you have the original Galaxy SII GT-I9100 or its variants such as the Galaxy Note SGH-N7000, then click here to follow this other thread instead.
This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.181, you can now create your own Galaxy S2 Skyrocket ROMs with the kitchen.
I'd like to thank twopumpchump (who owns an AT&T Skyrocket) and -Mr. X- (Telus Galaxy S2 X) for helping me out, as well as for testing on their devices and providing feedback. I only have a Bell Galaxy S2 I9100 so their assistance was greatly appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S2 Skyrocket or equivalent with a ClockworkMod custom recovery.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT: To verify your variant of the Galaxy S2 Skyrocket works in the kitchen, open your device's /system/build.prop file and check the ro.product.device value. If the value doesn't exist under the kitchen's tools/samsung_files/sgs2x_variants/ folder then just create a blank file there with same file name as your device's ro.product.device value.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S2 Skyrocket, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
system.img.ext4, tomb.img.ext4 (if it exists) and boot.img (and optionally: cache.img.ext4)
TAR file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4) NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
ZIP file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
Custom ROM:
ZIP file created only by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a system.img.ext4 but then didn't include the cache.img.ext4, then you have the option to add a cache.img.ext4 later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss Samsung Galaxy S2 Skyrocket or equivalent SGS2 LTE devices in this thread!
Most of all, have patience, take your time and enjoy!!
Reserved...
Reserved ...
Nice work guys. Enjoyed cooking rims fir my g2 and mt4g with this. I know what I'm gonna be doing soon
Sent from my SGH-I727 using Tapatalk
now we should have roms popping up everywhere
Sent from my SAMSUNG-SGH-I727 using xda premium
Nice job on the guide I'm gonna sticky this, hopefully alot of people will learn how to cook their own roms for Skyrocket!
A must use for new people who wants to get their feet wet with deving
Sent from my SGH-I727 using xda premium
I will be playing w this during the weekend.
Thanks!
Oh yes, I will be having fun with this! As a non-dev this will be a great way for me to get my feet wet. Thank you!
saweeeeet!!
Thanks again for getting this set up.
I was about to post this last night but dozed off. Great stuff...!
Awesome! Much appreciated! Thought you were done updating this...nice surprise!
Cboss said:
Awesome! Much appreciated! Thought you were done updating this...nice surprise!
Click to expand...
Click to collapse
Yes I was done but felt I needed to put a stop to those persistent tweets/questions from the original SGS2 thread.
thanks so much!
Awesome, great to see this for SkyRocket. Now if we can cook from ICS sources, that had be amazing! I guess we will haev to wait till atleast Galaxy S2 gets ICS officially. Nexus S got it today, jealous!
kornklown69 said:
now we should have roms popping up everywhere
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
yeah, can't wait for those "roms"
Is there currently a way to develop on top of a vanilla android rom? I personally don't like touchwiz or the carrier branded roms whatsoever. New to the development for this device so i am not exactly sure what's available.
Seannoxious said:
Is there currently a way to develop on top of a vanilla android rom? I personally don't like touchwiz or the carrier branded roms whatsoever. New to the development for this device so i am not exactly sure what's available.
Click to expand...
Click to collapse
Well, creating a custom ROM with the kitchen is not really development. You would need to compile the AOSP source code or a Cyanogen source to develop a vanilla ROM. The kitchen could be used afterwards to add other things to it like deodexing, root etc.
I have had limited success using the kitchen with a Samsung Galaxy S2 Cyanogen ROM, it depends on how complex the updater-script is. It did work fine on other devices like the Nexus S.
dsixda said:
Well, creating a custom ROM with the kitchen is not really development. You would need to compile the AOSP source code or a Cyanogen source to develop a vanilla ROM. The kitchen could be used afterwards to add other things to it like deodexing, root etc.
I have had limited success using the kitchen with a Samsung Galaxy S2 Cyanogen ROM, it depends on how complex the updater-script is. It did work fine on other devices like the Nexus S.
Click to expand...
Click to collapse
Understood i read some things on the cyanogen forums stating that they dont have plans to send out a skyrocket rom. They said that the att gs 2 is so similar to the international and the skyroxket using different chips for the blazay blazay blazay highly unlikely to develop a from for the skyrocket.
If he ports of a cyanogen are flakey and cm has no plans to support the phone BC of little demand or whatever do you know of anybody trying to pursue compiling a source code for the gs2 sr? I have Dev experience and would like to see more options for rooms. Not to discount the work that has already been done atall. I just personally love that vanilla feel. I also like launched pro and works much better in that environment from my experience.
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
thanks for the warning for the less experienced users, here's to making a rom kitchen to move roms between devices
I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482
incubus26jc said:
I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482
Click to expand...
Click to collapse
Such greatness!
I appreciate the warning. I came close to flashing another ROM. Kind of we had our own forum not a subforum.
I would also like to add, do not use ES Note Editor (part of ES File Explorer) to edit build.prop. I made one tiny change and rebooted and the phone wouldn't go past the boot logo. The fix was easy enough, but I wish I took the time to edit it properly.
Are the root methods carrier specific? Sorry for the noob question. So I'd be able to root using a Heimdall method for the i9300 - I'm on a Mac.
xjedi said:
Are the root methods carrier specific? Sorry for the noob question. So I'd be able to root using a Heimdall method for the i9300 - I'm on a Mac.
Click to expand...
Click to collapse
Yes, methods are carrier specific, don't use the i9300 methods. As far as I'm aware, Heimdall doesn't work. If you know how to use adb then you can try this method:
http://forum.xda-developers.com/showpost.php?p=29175988&postcount=1
Otherwise you'll have to use bootcamp or some other method to get to windows.
s197 said:
Yes, methods are carrier specific, don't use the i9300 methods. As far as I'm aware, Heimdall doesn't work. If you know how to use adb then you can try this method:
http://forum.xda-developers.com/showpost.php?p=29175988&postcount=1
Otherwise you'll have to use bootcamp or some other method to get to windows.
Click to expand...
Click to collapse
Thanks. Yeah, it looks like Heimdall only works for i9300 not the VZW version. I'll probably just wait til I can borrow a PC laptop or someone comes up with a VZW Mac rooting method that's proven to work.
And while in the subject of being on the right development section...
Archangel, what's the difference between "Verizon S3 and android development" and "Verizon S3 ORIGINAL Android development"?
... I read the first one most of the time but why 2 sections?
The Archangel said:
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
Click to expand...
Click to collapse
aqhilles said:
And while in the subject of being on the right development section...
Archangel, what's the difference between "Verizon S3 and android development" and "Verizon S3 ORIGINAL Android development"?
... I read the first one most of the time but why 2 sections?
Click to expand...
Click to collapse
Read my sticky in original development. XDA is trying to separate users that unzip a rom, toss in a few apps, then release it. Original development is for source built roms, cutting edge features(sense on Samsung S3, custom done ui. Etc) so users who want the best possible roms ASAP, without wasting time. It also helps shed light on those original roms
Hi all
Not really a noon, but seem to be either drawing a blank and getting conflicting comments and information!
So, in brief, I'm running stock Samsung jelly bean 4.1.1( Taiwan version). And it works fine.
I want to root so i can get cm 10.1 for that aosp feel.
I know that Macs use heimdall (got that) and i also understand i need to be on cwm recovery, but I'm struggling to find instructions as to how to actually root!
Which files do i need ( being on stock jelly bean), to use for heimdall in order to be able to flash cm10.1?
I do not have access to a windows computer, so unfortunately can't use Odin,
If anyone can point me in the right direction, id be very grateful.
I like to contribute comments for those in need on the forums.... and i now cone cap in hand asking for assistance
Many thanks all and a happy new year to you all
If you already in how how to use Heimdall, you can find the files in my guide (link in signature) ... just use CWM-SuperSU-0.96.zip.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
If you already in how how to use Heimdall, you can find the files in my guide (link in signature) ... just use CWM-SuperSU-0.96.zip.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
many thanks indeed
I have the note 10.1 and I hear its fast enough to run kitkat, how do I get kitkat on my n8013?
This doesnt belong in the general thread but in the Q and A. Btw you can find tuturiols here in general or search one.
Guntert said:
I have the note 10.1 and I hear its fast enough to run kitkat, how do I get kitkat on my n8013?
Click to expand...
Click to collapse
You CANT Officially.. Samsung Decided that those of us who bought the n8013 did not spend enough money to Deserve the update..
You can Load a Custom VERSION Thou. Read READ READ .. ITS on on here
Sorry for putting this in wrong place... I have read a few posts but understand them. Tried you tube and they were for other models, I did root already but it was like so easy it was just one click.
Guntert said:
Sorry for putting this in wrong place... I have read a few posts but understand them. Tried you tube and they were for other models, I did root already but it was like so easy it was just one click.
Click to expand...
Click to collapse
If you do not care for Samnusmg stock, then I would suggest that you flash the Carbon ROM KitKat 4.4.2. This ROM is AOSP but is like cream cheese - smooooth and bug free. I have a N8013. Samsung based KitKat is a really poor effort from Samsung. It is quite average...
If you are bent on having Sam stock, try Gnabo ROM. Actually, try carl1961's method here first to get an idea of KK on the device.
http://forum.xda-developers.com/showthread.php?t=2770009 .
It is a very good starting point. Be careful what recovery you flash. For all I have suggested, Philz advanced CWM recovery works smoothly.....Flash this first then theROM.
Good luck!
chappatti said:
If you do not care for Samnusmg stock, then I would suggest that you flash the Carbon ROM KitKat 4.4.2. This ROM is AOSP but is like cream cheese - smooooth and bug free. I have a N8013. Samsung based KitKat is a really poor effort from Samsung. It is quite average...
If you are bent on having Sam stock, try Gnabo ROM. Actually, try carl1961's method here first to get an idea of KK on the device.
http://forum.xda-developers.com/showthread.php?t=2770009 .
It is a very good starting point. Be careful what recovery you flash. For all I have suggested, Philz advanced CWM recovery works smoothly.....Flash this first then theROM.
Good luck!
Click to expand...
Click to collapse
Hello
Were can i download carbon rom for the samsung n8103 ? I'm running omni rom right now but i would like to run something different on it since i really don't have to many options for this tablet . i looked around for carbon and found nothing .
Cisco408ca said:
Hello
Were can i download carbon rom for the samsung n8103 ? I'm running omni rom right now but i would like to run something different on it since i really don't have to many options for this tablet . i looked around for carbon and found nothing .
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2784870
HueyT said:
http://forum.xda-developers.com/showthread.php?t=2784870
Click to expand...
Click to collapse
Thanks Friend.
Thank u, I went and got a tab s
KitKat wanna be on my N8013
Guntert said:
I have the note 10.1 and I hear its fast enough to run kitkat, how do I get kitkat on my n8013?
Click to expand...
Click to collapse
My device has become very slow but I am a downloading fool. What programs (many I have are duplicates with slightly differing features,) from file managers, to apk's utilized by most are the power hoarders?
Where can I find a copy of KitKat that is working, and AOSP as I am assuming I have to install that instead of the aroma installer I have used.
I look forward to all your help. A sort of perplexed person in Philadelphia.
I am running kit kat on my 8013 and it works great. Find "Gnabo rom" thread on xda.
http://forum.xda-developers.com/showthread.php?t=2762418
Sent from my GT-N8013
Galaxy Note GT - N8013 unlock software is not listed the N8000 is; will it work?
I am begging for information to let me restore my tablet to its factory default state. As you can tell from below, I have used two 64 gig mem cards, and have only 2 gig of the 16 gig of internal storage left as I am an electronic tidbit hoarder. I want to upgrade my tablet and have a buyer if I restore the tablet to its pre purchase state. Please help as this device is not listed on GalaxyUnlocker. The closest device is the samsung N8000 ..... Any advices, opinions, hints, or feelings will all be tried.
Please help the hoarder in Philadelphia
Thank you
My device has become very slow but I am a downloading fool. What programs (many I have are duplicates with slightly differing features,) from file managers, to apk's utilized by most are the power hoarders?
Where can I find a copy of KitKat that is working, and AOSP as I am assuming I have to install that instead of the aroma installer I have used.
I look forward to all your help. A sort of perplexed person in Philadelphia.[/QUOTE]
joanno said:
I am begging for information to let me restore my tablet to its factory default state. As you can tell from below, I have used two 64 gig mem cards, and have only 2 gig of the 16 gig of internal storage left as I am an electronic tidbit hoarder. I want to upgrade my tablet and have a buyer if I restore the tablet to its pre purchase state. Please help as this device is not listed on GalaxyUnlocker. The closest device is the samsung N8000 ..... Any advices, opinions, hints, or feelings will all be tried.
Please help the hoarder in Philadelphia
Thank you
My device has become very slow but I am a downloading fool. What programs (many I have are duplicates with slightly differing features,) from file managers, to apk's utilized by most are the power hoarders?
Where can I find a copy of KitKat that is working, and AOSP as I am assuming I have to install that instead of the aroma installer I have used.
I look forward to all your help. A sort of perplexed person in Philadelphia.
Click to expand...
Click to collapse
[/QUOTE]
Get stock firmware from Samsung or Sammobile.com . and flash with ODIN.
Unfortunately Samsung will not be releasing any updates past 4.1.2 for the gt-n8013. They have come to the conclusion that anyone in north america does not deserve an update and will never release the update for the tablet even though they had an official press release stating we would get the update.
They don't care that you paid a premium and promised updates for this tablet. They expect you to buy a new tablet every year to get any android updates!
Two words! LEAVE SAMSUNG!
custom roms
So i rooted my gt n8013 using key root master i used root checker it said it was rooted. Now i did this with no pc just my tab .so what custom recovery should i install next that installs without a pc ? And once that is done is there a way to flash a custom rom for kit kit onto the device without a pc ? And which one do you recommend? Sorry for all the questions new to all this
---------- Post added at 10:07 PM ---------- Previous post was at 10:02 PM ----------
johna2u said:
I am running kit kat on my 8013 and it works great. Find "Gnabo rom" thread on xda.
http://forum.xda-developers.com/showthread.php?t=2762418
Sent from my GT-N8013
Click to expand...
Click to collapse
So can this be installed without a pc
Pretty sure you need a pc to get the custom recovery installed.
Really then what does the cwm recovery app do?
---------- Post added at 12:50 AM ---------- Previous post was at 12:27 AM ----------
Really then what does the cwm recovery app do?
Any custom recovery needs to be designed to Work for your specific device. It may be possible to install a custom recovery with an app but you should definately do lots of reading before you attempt it.
Sent from my SM-T320
No "Development" in Settings
I'm pretty new to this, so have patience with me.
Just installed KitKat 4.4.2 on my GT-N8013. I wanted to tick the USB Debugging" checkbox, but there is no development section in the settings.
Am I missing something ?
Yes you are. In order activate the developer section you have to tap on build number about 7 or so times. That will make it appear.
Sent from my Nexus 9 using Tapatalk
[Q&A] UPDATED 9/30 [ROM][P900][P900UEU1BNI2] Original Stock and Debloated Stock Vari
Q&A for UPDATED 9/30 [ROM][P900][P900UEU1BNI2] Original Stock and Debloated Stock Variants
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 UPDATED 9/30 [ROM][P900][P900UEU1BNI2] Original Stock and Debloated Stock Variants. 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!
will it work on SM-P901 ?
i really like to try the debloated version,
my stock rom is a bit laggy for me
will it work on SM-P901 version?
i really hope it work
16person said:
i really like to try the debloated version,
my stock rom is a bit laggy for me
will it work on SM-P901 version?
i really hope it work
Click to expand...
Click to collapse
I do not feel completely confident it would work , not enough to tell you to take that risk.
Although they do appear to have the exact same hardware chip wise (the cpu/gpu are identical) I would need someone who is rooted on the 901 to check that the partition tables are identical to the sm-p900. The biggest one being that /boot is still mmcblk0p9. If /boot was set to the wrong block because they are slightly different you would end up with a bricked tablet, which would be awful. There is also the unknown of different parts in the firmware to account for the sm-p901 having 3g support while the sm-p900 is only wifi.
16person said:
i really like to try the debloated version,
my stock rom is a bit laggy for me
will it work on SM-P901 version?
i really hope it work
Click to expand...
Click to collapse
I think it will work, but you need to replace kernel (boot.img file) from your tab
edit: possibly not. I didnt find any libs with 3g support in p900 rom...
bonuzzz said:
I think it will work, but you need to replace kernel (boot.img file) from your tab
edit: possibly not. I didnt find any libs with 3g support in p900 rom...
Click to expand...
Click to collapse
That was my other fear. It may flash onto it fine if the /boot is the same, but I have not seen any support for the 3g service part of it.
Will any firmware updates coming soon to this wonderful rom?
Can you add widgets to the lockscreen?
OTA and new kernal - Gatsrom's ROM
I have been using the debloated stock variation of Gatsrom's rom and love it. I also use Xposed framework. When Samsung pushes a new OTA I don't want it to screw up the Rom. Will the new OTA be blocked or is there something I need to do to block the OTA? Second question: there is discussion in the original thread about changing kernels. What is the benefit for a non-developer or non-heavy tweaker for changing kernels.
Great ROM!
Keith
Really need some help guys ive followed the install details and install twrp with odin.
Tired both roms and on reboot it just sits on the Samsung logo screen.
Can anyone help me?
Thanks, you saved me!
Gat, I rooted my None Pro 12.2 P-900. Then got Twerp up and running and put Cm 12 on. Did not like it and it was buggy. My Samsung tablet mouse and Samsung Blue tooth keyboard lost some functionality. Could not unmount flash drive which I use anew OTG cable to read the drive... leta just say I was not in a good place. Found your thread here on XDA and decided to download your Ron and flash. Had trouble the first few times, but finally am up and running thanks to you. The Cm 12 fried my 120gb micro sd, but that versus the thought of bricking this device is a small price to pay. I am out an sd but still have a functioning note pro. Cm 12 was an awful experience for a first time rooter and rom flasher. You saved me and I would like to personally thank you.
Sincerely,
Mr. Kelley aka Zenistao