Related
I wanted to start a discussion about one thing that I see as a drawback to Samsung development. I'd love to hear peoples thoughts about it and what their experience was on previous Galaxy devices.
I just got this incredible beast of a phone last Tuesday...and....I LOVE it.
This is my first Sammy device, coming from all HTC phones for the last several years. One major thing that has concerned me is the lack of cohesive development, simply due to the fact that Samsung releases so many variants of the GS4 (or do they?).
The one main thing HTC has going for them in regards to phones & development, is that there is usually only one main forum for all your needs. For instance, my old Sensation...all you have to do is SuperCID & have S-OFF and you can flash any ROM you want, regardless of carrier etc. Even though there were several varieties of the Sensation (XE etc), if you had SuperCID...your ROM options were endless. Look no further than the development forum for the One...quite frankly, it is incredible the amount of custom stuff that is available in that forum. Even before the phone was widely released, there were about 2 dozen of XDA's great devs, modders, themers, already pumping out ROM's & Kernels & Mods etc etc. All this with very little confusion or fuss on how to root and or what you can or can't flash etc.
I wish it were as simply as that for us. I can only imagine how amazing development would be for the S4, if it wasn't split up into 4-5 different forums.
Lastly...I would love to know if it will ever be possible to flash anything that's for the I9505 (for instance the ROM from Indie). If the GS4 can have SuperCID, or something similar...why would this not be possible?? Of course we've all heard that we should NEVER flash anything that's not specific to our Tmo GS4...and leaves me wondering just how involved development will be for the Tmo GS4. My question would be why is that not possible if the hardware is the same....regardless of carrier? What are the restrictions to flashing anything I9505 related...and will it ever be possible? Is there an actually hardware difference in the German Tmo I9505 and the US Tmo I9505??
I simply look at it from a perspective of less devs in one spot, means less development for each variant...and that kinda bums me out a bit.
Love to hear what you guys think about this...
Cheers! :good:
Blame the US carriers for split forums.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
Hoggles said:
Love to hear what you guys think about this...
Cheers! :good:
Click to expand...
Click to collapse
The T-Mobile version is not the i9505, it is he M919. The i9505 is subtly different and is the only model of the GS4 to contain an FM radio.
The fragmentation is due in part to what the previous poster noted; us carriers; and LTE. The Sensation was not ever released on CDMA networks, it was GSM only and all models had the same hardware, including the actual radios. This is why the development was in one section, because all the devices were the same hardware, with only slight software differences depending on region/carrier.
The i9500 is the technological dream of the masterminds at Samsung flexing their muscles as a super power. The vast majority of the components are made directly by them including the revolutionary CPU and screen. I cannot think of any other company that does this. The entry model on these units is rarely catered to the us market (think original GS2, GS3, original Note) and usually sees a second generation to add support for CDMA and or LTE (Think carrier branded GS2, GS3, Note).
The I9505 & Carrier branded versions utilize a different SoC to accommodate for global demand. Most qualcomm chips these days are being mass produced and have LTE/CDMA worked out in their design initially. I makes it easy for sammy to push out more units in a quicker amount of time.
Hoggles said:
I wanted to start a discussion about one thing that I see as a drawback to Samsung development. I'd love to hear peoples thoughts about it and what their experience was on previous Galaxy devices.
I just got this incredible beast of a phone last Tuesday...and....I LOVE it.
This is my first Sammy device, coming from all HTC phones for the last several years. One major thing that has concerned me is the lack of cohesive development, simply due to the fact that Samsung releases so many variants of the GS4 (or do they?).
The one main thing HTC has going for them in regards to phones & development, is that there is usually only one main forum for all your needs. For instance, my old Sensation...all you have to do is SuperCID & have S-OFF and you can flash any ROM you want, regardless of carrier etc. Even though there were several varieties of the Sensation (XE etc), if you had SuperCID...your ROM options were endless. Look no further than the development forum for the One...quite frankly, it is incredible the amount of custom stuff that is available in that forum. Even before the phone was widely released, there were about 2 dozen of XDA's great devs, modders, themers, already pumping out ROM's & Kernels & Mods etc etc. All this with very little confusion or fuss on how to root and or what you can or can't flash etc.
I wish it were as simply as that for us. I can only imagine how amazing development would be for the S4, if it wasn't split up into 4-5 different forums.
Lastly...I would love to know if it will ever be possible to flash anything that's for the I9505 (for instance the ROM from Indie). If the GS4 can have SuperCID, or something similar...why would this not be possible?? Of course we've all heard that we should NEVER flash anything that's not specific to our Tmo GS4...and leaves me wondering just how involved development will be for the Tmo GS4. My question would be why is that not possible if the hardware is the same....regardless of carrier? What are the restrictions to flashing anything I9505 related...and will it ever be possible? Is there an actually hardware difference in the German Tmo I9505 and the US Tmo I9505??
I simply look at it from a perspective of less devs in one spot, means less development for each variant...and that kinda bums me out a bit.
Love to hear what you guys think about this...
Cheers! :good:
Click to expand...
Click to collapse
You're spot on. I had the HTC Sensation as well. I currently have the HTC One. I can def say that HTC retains the crown when it comes to consumer development. They even launched a website to unlock your device in response to so many requests for it.
What has Samsung done? Well, most recently they pushed an update that locked out root at the kernel level. Boo!
From what I've seen thus far (and yes I know it's still early) there has been a very weak response in the dev department for the T-Mobile variant of this device. It has been out for a couple of weeks now and we still don't have a PIT file posted anywhere. So if anyone hit a worst case scenario, they would be unable to fully wipe their phone and use an ODIN tar to return to stock. On that note, we don't even have a virgin untouched tar of the stock firmware (MDL that has tweaked kernel) for ODIN. A couple of the deodexed and zip-aligned flashable packages that were posted have slight changes made to them - we NEED untouched flashable zips. Don't post something as "stock" if you have modified the firmware.
All in all, we have had a very rocky start on this T-Mobile variant. I'm contemplating buying the device for a couple of the old Team Whiskey guys and starting our own team for this. There is a lot of work to be done, yet. And this device has a lot of potential.
Some of you may be offended by this and some of you may be rolling your eyes. That's fine. But these are my two cents.
On a brighter note... I'm hoping for a massive response once source drops.
luckyduck69 said:
You're spot on. I had the HTC Sensation as well. I currently have the HTC One. I can def say that HTC retains the crown when it comes to consumer development. They even launched a website to unlock your device in response to so many requests for it.
What has Samsung done? Well, most recently they pushed an update that locked out root at the kernel level. Boo!
From what I've seen thus far (and yes I know it's still early) there has been a very weak response in the dev department for the T-Mobile variant of this device. It has been out for a couple of weeks now and we still don't have a PIT file posted anywhere. So if anyone hit a worst case scenario, they would be unable to fully wipe their phone and use an ODIN tar to return to stock. On that note, we don't even have a virgin untouched tar of the stock firmware (MDL that has tweaked kernel) for ODIN. A couple of the deodexed and zip-aligned flashable packages that were posted have slight changes made to them - we NEED untouched flashable zips. Don't post something as "stock" if you have modified the firmware.
All in all, we have had a very rocky start on this T-Mobile variant. I'm contemplating buying the device for a couple of the old Team Whiskey guys and starting our own team for this. There is a lot of work to be done, yet. And this device has a lot of potential.
Some of you may be offended by this and some of you may be rolling your eyes. That's fine. But these are my two cents.
On a brighter note... I'm hoping for a massive response once source drops.
Click to expand...
Click to collapse
Wrong. There is already stock ODIN files on here and sammible. You do not need a .pit to flash an MD5 and the T-Mo Note 2 didn't have one either in the dev sections. Yes Samsung has included a new revision in their kernel to lock out root access, big deal. We are a group of developers here dedicated to outsmarting the man and doing things our own way. The i9500 already has the newest kernel built from source with the 1 flag (yes, it's one flag) circumvented. HTC doen't even have an official RUU available yet, and their HTC dev site records your IMEI to refuse you warranty service lol. I would suggest you read up some more before offering up your two cents, because based on what you stated they are without warrant, and worthless.
Here's a link to the stock ODIN file since you missed it, http://www.hotfile.com/dl/213469534/9ff06bd/M919UVUAMDL_M919TMBAMDL_TMB.zip.html
KillaHurtz said:
Wrong. There is already stock ODIN files on here and sammible. You do not need a .pit to flash an MD5 and the T-Mo Note 2 didn't have one either in the dev sections. Yes Samsung has included a new revision in their kernel to lock out root access, big deal. We are a group of developers here dedicated to outsmarting the man and doing things our own way. The i9500 already has the newest kernel built from source with the 1 flag (yes, it's one flag) circumvented. HTC doen't even have an official RUU available yet, and their HTC dev site records your IMEI to refuse you warranty service lol. I would suggest you read up some more before offering up your two cents, because based on what you stated they are without warrant, and worthless.
Here's a link to the stock ODIN file since you missed it, http://www.hotfile.com/dl/213469534/9ff06bd/M919UVUAMDL_M919TMBAMDL_TMB.zip.html
Click to expand...
Click to collapse
No... I don't think you understand.
Of course you don't "need" a PIT file. But do you understand what that is used for? I encourage you to try this.
1. Run the latest update. The virgin, str8 from kies, MDL update. You'll have the root-block kernel and everything.
2. Now try to ODIN back to the previous firmware using THIS MDB tar file.
I think you will find you are unable to successfully return to the fully stock MDB firmware. That tar file alone will not wipe anything. It will seem to flash via ODIN. But once you reboot... you'll still have your MDL firmware installed (sorta). You might suggest installing CWM or TWRP Recovery here. Well... you can try. I did. You will run into some interesting issues. LIke not being able to get into ANY recovery until you perform a full reset from within the system settings menu. Then suddenly finding your way into the stock android recovery. At which point you'll do a factory reset/wipe from the stock android recovery. Then you WILL be able to install CWM Recovery and flash... oh wait. There is no completely stock flashable firmware package. Those we do have are found HERE and have had things removed.
I'll give you another example. Let's say you soft brick your phone. You need to do a restore via ODIN. But you also need to wipe it completely. What are you going to do? You can't get to recovery. Can't load the system. You need to do a full wipe and factory restore. How are you doing to do that without the Partition Information Table and ODIN?
As for warranty... technically we're all void of warranty so why does it matter? We all void the warranty as soon as we start flashing. That is why all the devs put that disclaimer in their OPs.
Furthermore, while its kinda cool that you went straight into defensive mode, I wasn't bashing anyone. I'm just saying we need to pick it up and get the right files out there for the ppl who don't know how to fix things on their own and so forth. If I need to I'll take one of my computers off of Folding and turn it into a dev box so I can help out.
Love, Peace, and Chicken Grease :good:
All you need is the ODIN file I provided (MDL). After that you can enter the stock recovery and wipe the data as needed.
If you are completely bricked (cannot enter download mode) Samsung will warranty the phone for a new one.
It's not defensive that I am being. I could careless if you brick your phone lol, I am only providing facts that you seemed to miss.
The .pit file is usually used if you have borked the phone from all recognition and need to tell the device what to flash where as it sets the maps for the partitions.
Your original post said nothing of having to wipe or anything else you just disclosed which is still incorrect to an extent.
We all know that stock ODIN files do not wipe data, but with the files I posted you will not need to go back to a lower firmware in the 1st place and will not be locked out of the system or recovery....
If you are concerned with a stock .pit file, make one from Heimdall. Or, are you one of the ones "who don't know how to fix things on their own" ?
KillaHurtz said:
All you need is the ODIN file I provided (MDL). After that you can enter the stock recovery and wipe the data as needed.
If you are completely bricked (cannot enter download mode) Samsung will warranty the phone for a new one.
It's not defensive that I am being. I could careless if you brick your phone lol, I am only providing facts that you seemed to miss.
The .pit file is usually used if you have borked the phone from all recognition and need to tell the device what to flash where as it sets the maps for the partitions.
Your original post said nothing of having to wipe or anything else you just disclosed which is still incorrect to an extent.
We all know that stock ODIN files do not wipe data, but with the files I posted you will not need to go back to a lower firmware in the 1st place and will not be locked out of the system or recovery....
If you are concerned with a stock .pit file, make one from Heimdall. Or, are you one of the ones "who don't know how to fix things on their own" ?
Click to expand...
Click to collapse
Nah. Benji was cleaning up the code last night. But he did tell me that Heimdall 1.4 will be officially released in a few hours. And that he confirmed it working on his Sprint S4. Previous versions wont detect our snapdragon device.
As for your MDL ODIN file, you're still missing the point. But im going to drop it.
Sent from my S4 using Tapatalk 2
Hello,
I've bought an HTC One M8 at ebay a few days ago.. the device was sold as a Google Edition one, although, after I bought it, I realized that it was an unlocked HTC One M8 with a Google Edition rom (description in english wasn't so complete as the german one ).. for me that wouldn't be a problem, although I would prefer to have the genuine firmware (I like the original HTC software)..therefore, I asked the user to change the firmware before sending the phone to me.
After receiving the phone, I've noticed that firmware version is "Android Revolution HD 8.1 by mike1986".. therefore,.. not the original rom from HTC.. besides this, there's also some "leftovers" of the google edition, as you can see in the image below (appears when I reboot the phone) .
The user told me that he has spent almost three hours to install that rom,.. and that he couldn't ger rid of the "Google" symbol whenever reboot the phone, as he had almost bricked the phone when he was trying.
What I would like to know is if there is the possibility to change the firmware to the original HTC firmware, exactly as if I was getting the phone from the store (with all the applications that comes with it) and that also allows me to benefit from HTC warranty?
If so, is there any step by step guide to safely do it?
I'm a novice in this area (never rooted or unrooted a phone).. and I just want to have the phone as if it was out of the box (do not need to have it unlocked to update roms or to delete any applications that comes with the phone, or something like that).
My HTC has a CID-HTC__102 (based on what I searched in the forum...it looks like an unlocked international version (German) device) and it has an IMEI SV 01 (I don't know if this info is needed, but I could not attach any more images, so I post this info here).
I will leave some info screen images as attachments so it becomes easier for you to help me.
Thank you in advance for your help.
Best regards,
SkElEtIkO
http://forum.xda-developers.com/showthread.php?t=2735235
you might not need to do all the steps, but this works 100%
confusion and more confusion in my head... :S
RossMacgill said:
http://forum.xda-developers.com/showthread.php?t=2735235
you might not need to do all the steps, but this works 100%
Click to expand...
Click to collapse
Hello Ross,
I've already read that post, however, for a noobie in this area, I believe that there's a lot of things that might not be so easy as they're for who flash firmware a lot of times.. for example.. "flash (...) ROM in TRWP"...I never flashed anything ..
I've roughly seached in the forum for "flash in TWRP"..and there's a lot of people with problems in flashing things with it (get stuck in some point)...
Besides this..EddyOS post mentions to use "odexed package provided by @Mike1986".. is that post only about applying that ROM or can I use another one? I already have a ROM by mike1986.. the one that I want to get rid off .. I want a completely original ROM as if the phone came from HTC... I was thinking on this..but even this one looks like was also provided by mike1986... (and probably has the same name that the one that I have).. isn't there any ROM by HTC without any modification???
I haven't got anything against ROMs made by mike or someone else.. I just want a manufacturer ROM which allows me to have full warranty and the functionalities that originally came with the phone. For example, with this firmware that I currently have, I cannot add my google account (says "cannot connect to google server") and I cannot see if there are new phone software updates (it keeps searching and searching)... and if I look into phone's software name.. it appears "Android Revolution HD 8.1 by mike1986"..well.. if I would take the phone to HTC under warranty.. they certainly wouldn't do anything with that software
Another thing, you told in your reply that I may not need to do all the steps.. Why not (?) and.. in that case, which steps shall I need to do?
My final question of this post...since the user that sold me the phone had already made a firmware update (google edition) before the current one, and now.. the phone has things from two firmware updates (the initial logo from google edition firmware, as you can see in the attached image, and the firmware from mike1986), don't you think, that it would be necessary to make another steps to clean all this mess?
Thank you in advance for your help.
Regards,
SkElEtIkO
skeletiko said:
Hello Ross,
I've already read that post, however, for a noobie in this area, I believe that there's a lot of things that might not be so easy as they're for who flash firmware a lot of times.. for example.. "flash (...) ROM in TRWP"...I never flashed anything ..
I've roughly seached in the forum for "flash in TWRP"..and there's a lot of people with problems in flashing things with it (get stuck in some point)...
Besides this..EddyOS post mentions to use "odexed package provided by @Mike1986".. is that post only about applying that ROM or can I use another one? I already have a ROM by mike1986.. the one that I want to get rid off .. I want a completely original ROM as if the phone came from HTC... I was thinking on this..but even this one looks like was also provided by mike1986... (and probably has the same name that the one that I have).. isn't there any ROM by HTC without any modification???
I haven't got anything against ROMs made by mike or someone else.. I just want a manufacturer ROM which allows me to have full warranty and the functionalities that originally came with the phone. For example, with this firmware that I currently have, I cannot add my google account (says "cannot connect to google server") and I cannot see if there are new phone software updates (it keeps searching and searching)... and if I look into phone's software name.. it appears "Android Revolution HD 8.1 by mike1986"..well.. if I would take the phone to HTC under warranty.. they certainly wouldn't do anything with that software
Another thing, you told in your reply that I may not need to do all the steps.. Why not (?) and.. in that case, which steps shall I need to do?
My final question of this post...since the user that sold me the phone had already made a firmware update (google edition) before the current one, and now.. the phone has things from two firmware updates (the initial logo from google edition firmware, as you can see in the attached image, and the firmware from mike1986), don't you think, that it would be necessary to make another steps to clean all this mess?
Thank you in advance for your help.
Regards,
SkElEtIkO
Click to expand...
Click to collapse
odexed package provided by @Mike19 and the system dump you linked to are the same stock, more than likely the very same file. You can use any rom, that is a stock dump and the correct version, but i would use mikes, or from the list of stock dumps thread on here.
Mike is a rom developer, he makes custom roms, but also has sources for his roms, which he then supplies for us to go back to stock.
with your google flash screen, i did read that if you flash 1.54.401.5 then reflash 1.54.401.10, it fixes that issue, not sure how true it is.
Please see solution in here
Thank you
Hello,
I've got a Galaxy Tab Pro 8.4 that I bought during the few months when it was the top of the line small tablet from Samsung (before the S series came out). Since it seems clear that Samsung has abandoned it and it won't get an Android update, I want to see what it'll take to upgrade to at least Lollipop. I'm pretty tech savy, but I've never tried to do anything like this with Android and I'm not at all sure where to start.
I've started to read the thread on rooting, but I quickly got a bit lost as I don't understand the terminology.
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking? If it is possible, can someone point me to a how to for complete newbies?
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
CafeKampuchia said:
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
Click to expand...
Click to collapse
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Ichijoe said:
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Click to expand...
Click to collapse
1) I read the OP. He said, "stock Lollipop or Marshmallow."
2) You don't have to root TouchWiz to install a custom ROM. All you have to do is install TWRP, but it doesn't matter because of #1 above.
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it. I read it that he has accepted the fact that Samsung have left us in the lurch concerning any future updates.
That's how I read it, so the question follows in how to install a Custom ROM. Granted it should be possible to install TWRP v. 3.0.1-0, though Odin, and then the Device appropriate ROM. It should go without saying that the T320, and T325 are not the same Device, even if they are both collectively known as Galaxy Tab Pro's 8.4. As such it would be upnto the owner to know which version he might need.
Ichijoe said:
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it.
Click to expand...
Click to collapse
The problem, is folks really need to stop using the word "stock" as it really doesn't mean jack. Or at the least, means so many different things to different people, as to be basically meaningless. I would take stock to mean, what belongs on the device per the manufacturer, so that would be Kitkat TouchWiz in this case. To others (and probably what the OP is getting at) is a "pure" unskinned Google experience like Nexus. But seeing as Nexus is limited to such a small number of devices, I don't personally feel you can consider that "stock". CM is AOSP based, and at one time considered by many to be close to a pure AOSP experience. But those days are long gone, and there are so many proprietary CM features and apps now, you can't even begin to consider this "stock" by any means.
---------- Post added at 03:36 PM ---------- Previous post was at 03:22 PM ----------
_salguod said:
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking?
Click to expand...
Click to collapse
What you are asking for is CM12 or CM13 (LP or MM) or one of the CM based ROMs. Those are really your only choice when it comes to anything past KK on this device. The CM ROMs are are very stable at this point. You might run into an obscure bug, but to be honest, its less laggy and overall a much better experience than the official Samsung TouchWiz ROM. And if you want to be free of Samsung bloat, CM definitely does that as well.
Tweak or maintain? You don't have to do anything after flashing the ROM, if you don't want to. You can decide to update to newer nightly CM builds from time to time, but that is completely optional. And to be honest, even CM13 is so stable at this point, that the nightly updates don't really change much of anything.
Go back? That's a breeze. Just do a backup in TWRP custom recovery before flashing a ROM, and you can restore to that backup (basically a snapshot of your existing configuration).
_salguod said:
If it is possible, can someone point me to a how to for complete newbies?
Click to expand...
Click to collapse
Honestly, just searching and reading are your best friend. You'll learn a lot more that way, than folk spoon-feeding you the info. The process isn't really all that hard. There may be a lot of esoteric lingo, but you can easily Google or use the XDA site search to find out what those terms mean. And once you've gone through the process, you'll likely be happy for the learning experience.
XDA is a wealth of information, for those willing to take the time to learn and search. All the answers you want are here in one form or other. Difficult to wade through at first, I'll agree with that. But all of us here had to go through the same thing at one time or other.
Its really hard to help someone when they say is "I'm a newb, tell me how to do this". Make a lot more sense for you to just dive in, then come back here with some specific questions, which we will gladly answer.
it would help to know what version OS you're running and the build #.
I rooted my tablet late last year (bought it in May 2015). Wasn't hard to do after some reading. Knox is still good too...1 yr warranty will be over soon.
Thanks all, I appreciate it. I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
I definitely appreciate the push to search and learn, but it can feel like drinking from a firehose. Most "how to" posts are written assuming the reader knows the terminology and every post I read means Googling a half a dozen terms to understand it. For example, I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
When I said "stock" I was referring to stock out of the box Android, not stock Samsung. Stock Samsung means staying with KitKat which I'd rather not do. My phone is a Motorola Droid Turbo, which I think is pretty close to stock Android Lollipop, so that I'm familiar with that.
However, I think I'm seeing that going stock Android isn't necessarily possible, or rather, other ROMs are easier to come by. Cyanogenmod seems to be the most popular and sounds very stable, I'll likely try that.
So, I don't need to root in order to flash a new ROM. What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back? Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Any other surprises that a guy who has never done this might want to know before going in?
Thanks again for your patience and help.
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Well you have a number of choices for your T320 (WiFi), Sadly nonmof those stock. Since Samsung has never seen fit to ever giving us one. For me the Samsung (e.g. Vender ROMs), were always the 'Stock' ROMs. 'Pure' ROMs (al-la Nexus), are clearly Custom ROMs.
The best, and quickest way to learn how to update from Stock to Custom would be to hit up YouTube for a few short Vids on the subject.
_salguod said:
I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
Click to expand...
Click to collapse
Those aren't bad general guides, to just introduce you to the basic concepts and terms. Just keep in mind that every different Android device has its nuances, which vary by manufacturer and over time (from one device to another - even from the same manufacturer). So you'll be referring back to Tab Pro 8.4 specific guides eventually.
_salguod said:
I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
Click to expand...
Click to collapse
Basically, if you don't know what the Knox flag is, then it probably doesn't matter.
The longer story, Knox is a enterprise mobile solution made by Samsung. If you company doesn't use Knox (and you don't use your device for work), you don't need it. The huge majority of folks will never need Knox or want it.
You're right, that if the warranty is expired, the warranty flag doesn't matter. And honestly, I rooted my device while it still had a valid warranty. I'd rather have a device that I can use how I wish, and install what software I want (especially if Samsung isn't going to support it with updates) and warranty is a secondary concern, at most.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
Once you install TWRP custom recovery, you can make a backup of the current Samsung TouchWiz KK ROM; and revert to that if needed or desired.
But honestly, you won't want to go back. CM runs faster and smoother, with no Samsung bloat. You won't want to go back to the crappy TouchWiz ROM, that is 2 generations (Android versions) obsolete.
But it is a good idea to have a backup, in case flashing CM doesn't go right the first time, and the device won't boot.
_salguod said:
Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Click to expand...
Click to collapse
You will absolute want to wipe user data when installing CM. Not doing so will likely cause major bugs and/or failure to boot. This is the general rule whenever flashing a new ROM. Although for similar ROMs (such as minor CM updates) you can try to keep user data. This is called a "dirty flash".
You can backup a lot of your data before flashing CM:
Apps: After root, you can use the app Titanium Backup (highly recommended) to backup apps and app data
Accounts: Titanium can backup a lot of this stuff, as well. Depends on what you are talking about, specifically.
Files: just move them to SD card or your computer. Or use a cloud solution (there are many)
You should always be backing up your data, anyway, if its important to you.
_salguod said:
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Click to expand...
Click to collapse
Same firmware as what I had prior to rooting it.
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
AndroidPrince1 said:
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Click to expand...
Click to collapse
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
AndroidPrince1 said:
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
Click to expand...
Click to collapse
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Thanks all, I plan on biting the bullet some time soon. Too much other stuff on my plate (like car repairs, etc.) so it'll have to wait for a bit. I'll check back in when I do. I'm looking forward to it.
redpoint73 said:
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Click to expand...
Click to collapse
Good to know on the sdcard thing...looks like I'll have to read up again on how to do.
Thanks for the note.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
CafeKampuchia said:
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
Click to expand...
Click to collapse
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
_salguod said:
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
Click to expand...
Click to collapse
Cellular South is the US firmware for some reason.
I'm trying to load the latest CM 13.0 nightly this morning and running into issues.
I'm following the install instructions on the CM website and the loading of a custom recovery is failing at step 7. I get the start of the blue bar on my tablet, but I get this error in the command prompt:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've tried twice with the the factory cable and a third time with an alternate cable same result.
How do I fix that?
I should mention that I'm working on a Windows 10 computer.
My wife and I have decided to hang onto our Note 7s, because why risk it with just one when you can play life in hard-mode? Sadly, she upgraded via the forced OTA, not knowing any better. Now that her battery is limited to 60%, she's extremely irritated by the popup notice she has to close every time the screen is turned on. I have tried searching, but cannot find instructions on resetting the phone back to stock (pre-OTA). Any help would be greatly appreciated. Thanks.
* Please spare this thread of the "omg you're crazy, return your bombs immediately" posts.
NarcissusV said:
My wife and I have decided to hang onto our Note 7s, because why risk it with just one when you can play life in hard-mode? Sadly, she upgraded via the forced OTA, not knowing any better. Now that her battery is limited to 60%, she's extremely irritated by the popup notice she has to close every time the screen is turned on. I have tried searching, but cannot find instructions on resetting the phone back to stock (pre-OTA). Any help would be greatly appreciated. Thanks.
* Please spare this thread of the "omg you're crazy, return your bombs immediately" posts.
Click to expand...
Click to collapse
Hi, well I won't say your crazy because I truly love my N7 and was very reluctant to do as requested and return and purchase a new phone. But I finally relented and bought the new Google Pixel Xl and have now been waiting over a month to receive it. Called Verizon last week they said I would have it Monday(yesterday), never did get it. Meanwhile I've managed to keep postponing this update I knew was the battery limiting ota for more than a week now. That is until tonight when I accidentally hit update. I am extremely pissed as I work for a government contractor and am constantly on my phone, and now must deal with only a 60% max battery to get me through a day when even a fully charged one couldn't. My only thought is maybe if I rooted the phone I would somehow be able to do something that way, perhaps by flashing the original factory software prior to the OTA. But I am just waiting on my new replacement and don' t really want to root for what could only be a day then un root to send back when my Pixel XL arrives. But it may be worth a shot on your wife's N7. Although I understand your decision to keep your N7's , as I really love mine, this deliberate hijacking of my personal property by Samsung and Verizon, has only streangthened my resolve to never purchase another Samsung phone again, I've owned every Note that has been made and as much as I love owning and using them, this will be the last time I allow them to take my money and reneder my phone useles. Samsung may not go under because of losing me as a customer, but they are definatally feeling the loss of the many who chose a different brand to replace their N7's. Good luck to you with your wife's N7. Please update if you try the root method so that others may also benefit.
Best wishes.
LvnInOC
Sadly, I believe it's impossible to revert back to 100% battery if you've already taken the update.
Get the PHE firmware from SamFirm, since SamMobile has removed all US Note 7 firmware, and use Odin to reflash it and then block the PK1 update (60% battery) with PDP or PDP+ (use manual mode to enter the package names) by disabling these 2 packages.
com.sec.android.soagent
com.samsung.sdm
Interpretation please
Woofa59 said:
Get the PHE firmware from SamFirm, since SamMobile has removed all US Note 7 firmware, and use Odin to reflash it and then block the PK1 update (60% battery) with PDP or PDP+ (use manual mode to enter the package names) by disabling these 2 packages.
com.sec.android.soagent
com.samsung.sdm
Click to expand...
Click to collapse
For those of us who have not yet learned the technical jargon, could someone help with more details about exactly how to do what you described. Is there a another thread or instructions somewhere that would detail this step-by-step for the novice? Better yet, if there is someone in the Tucson/Phoenix Arizona area who is in EXPERT at doing these and have been successful, I would be happy to pay a small success fee to have them do this for me..
garybiz said:
For those of us who have not yet learned the technical jargon, could someone help with more details about exactly how to do what you described. Is there a another thread or instructions somewhere that would detail this step-by-step for the novice? Better yet, if there is someone in the Tucson/Phoenix Arizona area who is in EXPERT at doing these and have been successful, I would be happy to pay a small success fee to have them do this for me..
Click to expand...
Click to collapse
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730
Verizon shut down service ?
chrisnosleep said:
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730
Click to expand...
Click to collapse
Thanks,
BUT, what is your opinion - will / can verizon stop service to all N7 phones eventually. Then all this is for nothing . What is the consensus on that one ???
chrisnosleep said:
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730
Click to expand...
Click to collapse
Using that link, next to the SM-N930V has a link to the PHE firmware, which is precisely what I don't want, correct? If I'm correct, I'm guessing the PH1 firmware is what I would want to flash, yes? Is it as simple.? Just...flashing back the stock PH1 firmware via ODIN? I see people having issues that try and root after accepting the PHE update, so why wouldn't they be able to just do this (flash PH1 and complete the root process)?
FYI: PH1 stock firmware here: http://forum.xda-developers.com/ver...-your-verizon-note-7-and-quick-guide-t3443994
Humble Request:
I have finally done the scary process of voiding the waranty of my samsung device. I did it for nethunter. But as always, there are some major road blocks to get nethunter to work on this device to full extent. Currently, my device works seemlessly but the only things not working are HID and WIFI Injections. (the exact 2 attacks for which i rooted my device in the first place).
I have read alot about this situation, all info regards to the issue being related to the kernal of my device which made me go down the dark rabbit hole of learning how to create a custom kernel for my device. sadly I cannot do anything RN.
If anyone has the right kernel with external wifi adapter support, Please redirect me. I will be very greatful.
I want to use Ralink RT3070 usb wirless adapter with my [SM-A325F/DS].
Link to the original request thread
Process of rooting the SM-A325F:
When i started to plan the Process, I read that many people were facing the IMEI problem with their A32s so I waited until a new baseband and firmware build was released. When i rooted my device luckily I did it correctly in the first try.
My Firmware Build was: A325FXXU2CVK3 Download [I used the "AP file to root"] [First check your Build no. If its differant then download your exact one. Don't blame me afterwards]
You can find the list of a firmwares for all A32 4G devices
After unlocking the bootloader, I followed this turtorial
Unlocking the bootloader was very easy compare to other devices. (For instance, I spent a Whole month tying to unlock Galaxy SCL24. I searched for the exact firmware so many times that i memorized the whole number.)
I used Latest magisk APK.
Afterwards, I downloaded This Root Explorer A/C to my knowledge, It is trusted. But Whose giving warranties.
I installed Nethunter By downloading form HERE Yon can find installation turtorial yourself.
After all this, I currently can't get my external wifi adapter to work yet. Any help will be highly appreciated.
Thank You.
Burhan A.
Waiting for custom recovery for a32
checksum.Burhan_Arif said:
Humble Request:
I have finally done the scary process of voiding the waranty of my samsung device. I did it for nethunter. But as always, there are some major road blocks to get nethunter to work on this device to full extent. Currently, my device works seemlessly but the only things not working are HID and WIFI Injections. (the exact 2 attacks for which i rooted my device in the first place).
I have read alot about this situation, all info regards to the issue being related to the kernal of my device which made me go down the dark rabbit hole of learning how to create a custom kernel for my device. sadly I cannot do anything RN.
If anyone has the right kernel with external wifi adapter support, Please redirect me. I will be very greatful.
I want to use Ralink RT3070 usb wirless adapter with my [SM-A325F/DS].
Link to the original request thread
Process of rooting the SM-A325F:
When i started to plan the Process, I read that many people were facing the IMEI problem with their A32s so I waited until a new baseband and firmware build was released. When i rooted my device luckily I did it correctly in the first try.
My Firmware Build was: A325FXXU2CVK3 Download [I used the "AP file to root"] [First check your Build no. If its differant then download your exact one. Don't blame me afterwards]
You can find the list of a firmwares for all A32 4G devices
After unlocking the bootloader, I followed this turtorial
Unlocking the bootloader was very easy compare to other devices. (For instance, I spent a Whole month tying to unlock Galaxy SCL24. I searched for the exact firmware so many times that i memorized the whole number.)
I used Latest magisk APK.
Afterwards, I downloaded This Root Explorer A/C to my knowledge, It is trusted. But Whose giving warranties.
I installed Nethunter By downloading form HERE Yon can find installation turtorial yourself.
After all this, I currently can't get my external wifi adapter to work yet. Any help will be highly appreciated.
Thank You.
Burhan A.
Click to expand...
Click to collapse
wooow, It works
CodeX1 said:
Waiting for custom recovery for a32
Click to expand...
Click to collapse
it already exists if you look at the forums. shrp and twrp both exist
Captain_cookie_200 said:
it already exists if you look at the forums. shrp and twrp both exist
Click to expand...
Click to collapse
wow thanks, is there also a custom rom for a32? And is there a telegram group for a32?