Related
So today I bought a new Note 2 (SGH-i317M) on Bell Mobility Canada, as I was having issues with my first one. The first one had been rooted, and had a couple different roms on it. The last week or so my reception has been atrocious and constantly in "emergency calls only" mode, so I said "forget it" get a new one, send in the old one and sell it to my buddy when it gets back.
I managed to get a stock recovery and a stock rom on the old Note 2 using Samsung Galaxy Note2 Toolkit. Now, this is where it goes wonky and not sure what happened.
Upon initially getting the stock rom (4.1.1) on it, I noticed another update in the notification tray. At this point my SIM card has been pulled and I am using only wifi on it. I jumped on the update thinking cool my device isn't "modified" anymore, so I will take this update ( to 4.1.2)
After doing that update, I looked in my app drawer and it has 6 or 7 Roger's bloat apps in it, and the kernel version was different. Otherwise baseband, build and Android version are the same Not sure if it happened when I installed the stock rom from the Toolkit process or if the Roger's apps came with the OTA update to 4.1.2.
The problem is, this makes it hard to take a phone back to Bell for repairs with Roger's system apps in it. I've tried flashing the stock rom from the Toolkit via Odin again but there is still Roger's bloat there.
I have no idea what to do now. I pretty much used up all my brain power today getting this far. Could someone point me in the right direction, I would appreciate it greatly.
Thanks ahead of time for any responses, I've been at this most of the day now and I am just out of ideas now. :silly:
If you are getting rogers apps in a fresh flash via Odin...then you likely have the wrong rom being flashed....(it happens)
Look in the "Everything thread" in the development section for the stock bell firmware. this is the bell stock firmware from the thread...I pulled it for you...http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
That rom is the link from the everything thread...
You are the second user this week that has flashed a mis-labeled rom from the kit...
Once bell is flashed, your rogers apps will go away...
Remember to wipe all data and caches in the stock recovery before booting the new rom....g
U need to change ur csc, all stock Canadian fw is the same... it will show bell bloat till u enter the proper csc.
Hopfully this helps http://forum.xda-developers.com/showthread.php?t=1988202
And this http://forum.xda-developers.com/showthread.php?t=2004029
twanskys204 said:
U need to change ur csc, all stock Canadian fw is the same... it will show bell bloat till u enter the proper csc.
Hopfully this helps http://forum.xda-developers.com/showthread.php?t=1988202
And this http://forum.xda-developers.com/showthread.php?t=2004029
Click to expand...
Click to collapse
+1 csc will give you right firmware i always use Samsung Galaxy S csc from pstore. Just choose your carrier and no need to flash firmware again.
https://play.google.com/store/apps/details?id=com.manniakk.cscselector
Sent from my SGH-I317M
gregsarg said:
If you are getting rogers apps in a fresh flash via Odin...then you likely have the wrong rom being flashed....(it happens)
Look in the "Everything thread" in the development section for the stock bell firmware. this is the bell stock firmware from the thread...I pulled it for you...http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
That rom is the link from the everything thread...
You are the second user this week that has flashed a mis-labeled rom from the kit...
Once bell is flashed, your rogers apps will go away...
Remember to wipe all data and caches in the stock recovery before booting the new rom....g
Click to expand...
Click to collapse
Thanks so much. I wish found that earlier.
As well as this.........
twanskys204 said:
U need to change ur csc, all stock Canadian fw is the same... it will show bell bloat till u enter the proper csc.
Hopfully this helps http://forum.xda-developers.com/showthread.php?t=1988202
And this http://forum.xda-developers.com/showthread.php?t=2004029
Click to expand...
Click to collapse
Which may have lead to this......
jon3sh said:
+1 csc will give you right firmware i always use Samsung Galaxy S csc from pstore. Just choose your carrier and no need to flash firmware again.
https://play.google.com/store/apps/details?id=com.manniakk.cscselector
Sent from my SGH-I317M
Click to expand...
Click to collapse
Thanks so much guys. This experience has really stumped me.
I did however manage to get this sorted in the mean time. I installed a custom recovery back in, did a full system wipe the put in a rom that supports Canadian variants (tell ya the truth can't even remember it's name) and in that install process it had an aroma installer. One of the options was to adjust CSC for your desired carrier. After I set it up, I started the intitial process of wiping, and flashing and such over and voila I had all Bell apps and no Rogers apps.
But, in the meantime, the wifi decided to do its hanging thing again and for the last 3 hours or so I have been trying to get Triangle Away running on it. The app requires more data to work with my phone, but as this phone doesn't have a registered SIM and the wifi wont start now I have to manage a way to get it working, reset my binary count, unroot and verify and be done with it.
I greatly appreciate your guys input and will be reading as much as possible. Generally I can go flash crazy with custom roms but Odin messes me up.
I hope others see this thread and don't do what I did, and learn about CSC before they get hung up. Thanks again guys.
p.s. my brain hurts
OK. I officially give up. This 5 month old phone is going in the garbage. If it isn't one thing, it's another. Managed to get the wifi (and BT which I didn't know at first wasnt working) by inserting my new phones SIM. Blam, both worked. Great, now I can install Triangle Away, do my thing, reflash the stock firmware and I'm good.
And now.............the Toolkit won't recognize ADB enabled. I have been at this for over 24 hours now and it's been one roadblock after another.
I am officially McGyver'ed out :crying:
Idk what ur doing wrong but, doing a freash install should fix ur issues..
twanskys204 said:
Idk what ur doing wrong but, doing a freash install should fix ur issues..
Click to expand...
Click to collapse
Right on. Ya I kinda gathered my thoughts and buckled down and started over. So, now I have what appears be the proper firmware on my older Note 2.
Version: 4.1.1
baseband: i317MVLAJ2
kernel: 3.0.31-262790 / [email protected] #1 / SMP PREEMPT wed Oct 3 ........2012
build: JRO03C.I317MVLAJ2
Device Status: Normal
It seems like the exact same software as when I first cracked my new one out the box. After I updated it, the newer one now has:
Version: 4.1.2
baseband: I317MVLBMA3
kernel: 3.0.31-262790 / [email protected] #1 / SMP PREEMPT wed Oct 3..........2012
build: JZ054K.I317MVLBMA3
Pretty sure I got all the numbers right lol.
Still trying to figure out what to do now for Triangle Away, and making this phone seem like it's never been touched. Thanks for your help so far.
Root with cf root ,,run triangle away then do what u just did
twanskys204 said:
Root with cf root ,,run triangle away then do what u just did
Click to expand...
Click to collapse
CF Root. OK I will check it out. Thank you ! I will let ya know how it goes. I appreciate this as it just seems like there is just way too much Note 2 info out there. Thanks for the filter lol !
Update. Well that did it. In the "Download" screen it is saying;
-Custom binary download: No
-Current Binary: Samsung Official
-System Status: Official
In Settings, the device status is Normal
As far as my research has gotten me, my understanding is that I should now be able to send it in with out any warranty issues. My wifi and BT are acting hinky again but I may try my SIM swap again and see if that helps, before I send it away.
Thank you so much for your help. That suggestion of CF Auto-Root helped big time!!!!!
No problem. . Get some rest and hit it up in the morning. .
Valkillmore said:
Update. Well that did it. In the "Download" screen it is saying;
-Custom binary download: No
-Current Binary: Samsung Official
-System Status: Official
In Settings, the device status is Normal
As far as my research has gotten me, my understanding is that I should now be able to send it in with out any warranty issues. My wifi and BT are acting hinky again but I may try my SIM swap again and see if that helps, before I send it away.
Thank you so much for your help. That suggestion of CF Auto-Root helped big time!!!!!
Click to expand...
Click to collapse
Next time you are flashing stock rom for your phone just use rom from link below so you dont need to worry about rooting after. Roms are root injected already and good to go.
http://forum.xda-developers.com/showthread.php?t=2004650
Sent from my SGH-I317M
jon3sh said:
Next time you are flashing stock rom for your phone just use rom from link below so you dont need to worry about rooting after. Roms are root injected already and good to go.
http://forum.xda-developers.com/showthread.php?t=2004650
Sent from my SGH-I317M
Click to expand...
Click to collapse
Nice ! Ya I found the same root injected bell rom but unfortunately it was after I wanted to uninstall and unroot. I will be taking this approach from now on. Thank you good sir!!
I appreciate everyone's patience because I was certainly runnIngl out of it . Going to get the old Note 2 packed up and shipped off sometime today. Again all help greatly appreciated guys .
To add to my ordeal going on now, I did notice that my first Note 2 was made in China, and feels sloppy. Like the battery is slightly loose, and like the assembly just doesn't feel tight. I had to slip a piece of folded paper in behind the battery as the phone always rebooted even just gently dropping it on the table.
My brand new Note 2 I noticed was made in Korea. The battery is seated much, much better, and the phone itself feels like it was put together in a factory, not a car garage.
I am wondering if this is what is going on, because today after messing with the old one (which is now OTA'd to 4.1.2 *thanks again guys!*), and having the same persistent wifi hanging issue (not turning on and not really turning off, just suspended) and BT not wanting to turn on, alongside its original problem of poor cell reception......I thought I wonder if something is just hinky/loose or whatever. So I picked the phone up, dropped it flat on its back (in a case lol) from about 8 inches in the air, onto my coffee table. Opened the notification tray, and tapped the wifi toggle and it instantly turn on, bright lime and I was able to see available networks. The BT turned on immediately after pressing it too. Can't speak on cell signal, and it may well just be coincidence, but after several wipe/flash processes and BT and wifi acting hinky across several factory resets etc, then immediately working after the drop.......strange indeed.
More convinced now than ever that I have had somewhat of a lemon the whole time as I have had weird issues with reception for a long time from in the house to out in the world. The phone has never been seriously dropped and anytime it did slip it was in an Urban Armor Gear case, screen is near mint (didnt have protector first week) , and should be absolutely zero water damage.
Valkillmore said:
To add to my ordeal going on now, I did notice that my first Note 2 was made in China, and feels sloppy. Like the battery is slightly loose, and like the assembly just doesn't feel tight. I had to slip a piece of folded paper in behind the battery as the phone always rebooted even just gently dropping it on the table.
My brand new Note 2 I noticed was made in Korea. The battery is seated much, much better, and the phone itself feels like it was put together in a factory, not a car garage.
I am wondering if this is what is going on, because today after messing with the old one (which is now OTA'd to 4.1.2 *thanks again guys!*), and having the same persistent wifi hanging issue (not turning on and not really turning off, just suspended) and BT not wanting to turn on, alongside its original problem of poor cell reception......I thought I wonder if something is just hinky/loose or whatever. So I picked the phone up, dropped it flat on its back (in a case lol) from about 8 inches in the air, onto my coffee table. Opened the notification tray, and tapped the wifi toggle and it instantly turn on, bright lime and I was able to see available networks. The BT turned on immediately after pressing it too. Can't speak on cell signal, and it may well just be coincidence, but after several wipe/flash processes and BT and wifi acting hinky across several factory resets etc, then immediately working after the drop.......strange indeed.
More convinced now than ever that I have had somewhat of a lemon the whole time as I have had weird issues with reception for a long time from in the house to out in the world. The phone has never been seriously dropped and anytime it did slip it was in an Urban Armor Gear case, screen is near mint (didnt have protector first week) , and should be absolutely zero water damage.
Click to expand...
Click to collapse
Flash away now
Sent from my SGH-I317M
jon3sh said:
Flash away now
Sent from my SGH-I317M
Click to expand...
Click to collapse
Well, I was thinking that, but seeing it's under warranty, I am going to see what happens at Samsung. Hopefully they don't have some new way of seeing its been customed *face palm* lol and just replace it, even if its with a working factory rebuild or whatever. As I had to purchase both devices out right, and I live in Canada, I may be able to buy a car with the money.......holy crap its expensive up here.
Nearly $800 for each one. Ridiculous lol
EDIT: It would be a crappy car, but a car none the less
Ya , im up in canada also.. mine was 840 when it first came out. I payed it right out and unlocked it.
Mind u my build quality is excellent, maybe except for the sqeeky back.
But no problems none the less.:thumbup:
Sent from my SGH-I317 using Tapatalk 2
twanskys204 said:
Ya , im up in canada also.. mine was 840 when it first came out. I payed it right out and unlocked it.
Mind u my build quality is excellent, maybe except for the sqeeky back.
But no problems none the less.:thumbup:
Sent from my SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Ya it is just ridiculous the costs up here, and I live up in northern BC so everything is just a little more than everywher else as expensive at it is already, UGH !
I wonder if there is a new batch shipped because like I said, the one I bought 5 months ago was made in China, and like you say "squeeky". Loose. And big difference in at least mobile data / cell radio performance between my two devices.
This new one made in Korea, even the older battery slides in nice and tight. No squeaky back. Just feels tighter, even the S-Pen. It was always kind of loose on the older Note and even tossing the phone onto the table sometimes dislodged it. Even my camera lense on my older one seemed like it was mounted weird. I'd prefer stuff domestic if possible but I sure notice a difference between the Korean manufactured and the Chinese manufactured.
But I have a feeling I may be sending it back right away if service is as useless as it is everywhere else nowadays. I noticed after getting home on the work order it says
Wifi not connecting
BT not connecting
etc
Well, it was not that BT or wifi wouldn't connect. They connect to my devces/network immediately, BUT if and only if they actually turn on. The toggle stays half lit, and the wifi would say "turning on" then simply shut off a minute later. And the BT just wouldn't turn on at all, UNTIL I "dropped fixed" them this morning.
She also forgot to add that the S-Pen is totally haywire. I think that may be simply a sensitivy calibration issue I could maybe fix myself from YouTube vids I've seen. Just never got to it with other issues. I just hope the tech that checks it isnt as useless as I am picturing them in my mind and they show initiative and actually check the whole phone. Dream on I'm thinking HA !
Valkillmore said:
Ya it is just ridiculous the costs up here, and I live up in northern BC so everything is just a little more than everywher else as expensive at it is already, UGH !!
Click to expand...
Click to collapse
I have to agree Valkillmore, northern BC has horrible pricing. I have had mine since January on Telus and also had strange problems with the radios.
My wireless randomly drops my home wifi signal, regardless of which frequency it uses. This started just the other day and I actually hadn't done any flashing or updates in a few days. Seems strange that it would start now.
Any AT&T SM-T217A users here successfully obtain root via Srsroot on their tabs? They dropped a tweet a month ago that it was supported @ 4.4.2, but it's not sticking for me..
geokhentix said:
Any AT&T SM-T217A users here successfully obtain root via Srsroot on their tabs? They dropped a tweet a month ago that it was supported @ 4.4.2, but it's not sticking for me..
Click to expand...
Click to collapse
Nope. I tried that one out as soon as it posted. Here is the thread discussing http://forum.xda-developers.com/galaxy-tab-3/help/root-sma-4-4-2-t2902677
bigdawg6183 said:
Nope. I tried that one out as soon as it posted. Here is the thread discussing http://forum.xda-developers.com/galaxy-tab-3/help/root-sma-4-4-2-t2902677
Click to expand...
Click to collapse
These T217As I bought are turning out to be the worst experience I have ever had with a decent device. The specs and the battery life are great, but AT&T (or samsung?) has lost their mind. Out of my two tabs (both set up identical) Only one was ever eligible for the 4.4.2 upgrade. The second says no upgrade when I check for one.
The one I did upgrade was so bad on 4.4.2 that I ended up trying to flash back to 4.2.2 before I realized I couldn't and bricked the tab.
2 months later, still no upgrade available for my second tab (probably a good thing except I wanted to try an app that says it can catch the firmware update to use on my bricked tab). Still no 4.4.2 firmware to be found on the internet to download for this device.
The worst part is it doesn't even seem to be available from kies. Kies 3 doesn't even recognize it as a 4.4.2 device anymore after the attempted downgrade and the other kies versions only offer 4.2.2 which the device won't let me flash.
rmntruexjr said:
These T217As I bought are turning out to be the worst experience I have ever had with a decent device. The specs and the battery life are great, but AT&T (or samsung?) has lost their mind. Out of my two tabs (both set up identical) Only one was ever eligible for the 4.4.2 upgrade. The second says no upgrade when I check for one.
The one I did upgrade was so bad on 4.4.2 that I ended up trying to flash back to 4.2.2 before I realized I couldn't and bricked the tab.
2 months later, still no upgrade available for my second tab (probably a good thing except I wanted to try an app that says it can catch the firmware update to use on my bricked tab). Still no 4.4.2 firmware to be found on the internet to download for this device.
The worst part is it doesn't even seem to be available from kies. Kies 3 doesn't even recognize it as a 4.4.2 device anymore after the attempted downgrade and the other kies versions only offer 4.2.2 which the device won't let me flash.
Click to expand...
Click to collapse
I totally agree rmn, the experience with this tablet has been sub par. I know when I first heard about the update being released I was checking around online to see if I could find a dl for it, none existed. I did finally go through the process of updating OTA after having to remove root from my 4.2 firmware. Since the update my tablet appears to operate the same except for the lag has returned. I believe that is because I now no longer have my tweaks setup on the device since I have no root. My real peeve with AT&T with this tab is the locked bootloader, come on man, I want to load up different roms and get rid of all this bloatware. We cant even get root access with this new 4.4!
Could I get a screenshot of your about screen on the tab that is not updating?
bigdawg6183 said:
I totally agree rmn, the experience with this tablet has been sub par. I know when I first heard about the update being released I was checking around online to see if I could find a dl for it, none existed. I did finally go through the process of updating OTA after having to remove root from my 4.2 firmware. Since the update my tablet appears to operate the same except for the lag has returned. I believe that is because I now no longer have my tweaks setup on the device since I have no root. My real peeve with AT&T with this tab is the locked bootloader, come on man, I want to load up different roms and get rid of all this bloatware. We cant even get root access with this new 4.4!
Could I get a screenshot of your about screen on the tab that is not updating?
Click to expand...
Click to collapse
If it's in warranty, take it to the AT&T store. Tell them you did OTA and it 'got all screwy'. don't use terms like "bricked". Feign ignorance on all the workings of rooting and roms and stuff. Don't even use the term "Rom", use "operating system". Assuming you have the same boot error message I did, something to the effect of "there was a problem updating", apparently it's common enough that they'll get you to Samsung. Samsung will email you a shipping label, and in about a week to a week in a half, I had mine back functional again. Granted they put it on 4.4.2, which is a bummer, but at least it works. No questions asked. they didn't ask me about rooting or anything, I just told them I did the update, rebooted, it rebooted once, and then I had to reboot again and it had the error. First I took it so Samsung rep at best buy, he couldn't do anything, then I took it to the AT&T store. AT&T doesn't deal with tablet warranties, so that's why they put me on the phone with Samsung. On amazon, they have refurbished t217a's for $144.00, and on the description it says they're on 4.1.2 (rootable, and upgradable to 4.2.2 w/odin, which is also rootable. 4.2.2 firmware was a gigantic pain in the ass to get a hold of, but it's out there. I know it's not the answer you want, but hope it helps at least return the tablet into working state. I don't think we'll ever see a root for t217a on 4.4.2, nor any way to downgrade back to 4.2.2. Just not enough interest from the guys with the time and know-how. It was Samsung's bottom-end tablet, and the Tab S is just better for almost everyone. I use the Tab3 7.0 for work mainly because of it's size. I'm a pilot and I strap the tablet to my leg for approach plates and maps and stuff, and the size of the 7.0 is just right. The 8.0 and 8.3(?) is just a bit to big for that purpose. Anyway, I just hope (but not holding my breath) that Samsung + AT&T well at the very LEAST update the thing to lollipop so we can at least get full external SD card function again, because aviation maps and references and the sort take up a LOT of memory after a while..
DSTG said:
If it's in warranty, take it to the AT&T store. Tell them you did OTA and it 'got all screwy'. don't use terms like "bricked". Feign ignorance on all the workings of rooting and roms and stuff. Don't even use the term "Rom", use "operating system". Assuming you have the same boot error message I did, something to the effect of "there was a problem updating", apparently it's common enough that they'll get you to Samsung. Samsung will email you a shipping label, and in about a week to a week in a half, I had mine back functional again. Granted they put it on 4.4.2, which is a bummer, but at least it works. No questions asked. they didn't ask me about rooting or anything, I just told them I did the update, rebooted, it rebooted once, and then I had to reboot again and it had the error. First I took it so Samsung rep at best buy, he couldn't do anything, then I took it to the AT&T store. AT&T doesn't deal with tablet warranties, so that's why they put me on the phone with Samsung. On amazon, they have refurbished t217a's for $144.00, and on the description it says they're on 4.1.2 (rootable, and upgradable to 4.2.2 w/odin, which is also rootable. 4.2.2 firmware was a gigantic pain in the ass to get a hold of, but it's out there. I know it's not the answer you want, but hope it helps at least return the tablet into working state. I don't think we'll ever see a root for t217a on 4.4.2, nor any way to downgrade back to 4.2.2. Just not enough interest from the guys with the time and know-how. It was Samsung's bottom-end tablet, and the Tab S is just better for almost everyone. I use the Tab3 7.0 for work mainly because of it's size. I'm a pilot and I strap the tablet to my leg for approach plates and maps and stuff, and the size of the 7.0 is just right. The 8.0 and 8.3(?) is just a bit to big for that purpose. Anyway, I just hope (but not holding my breath) that Samsung + AT&T well at the very LEAST update the thing to lollipop so we can at least get full external SD card function again, because aviation maps and references and the sort take up a LOT of memory after a while..
Click to expand...
Click to collapse
bigdawg6183 said:
I totally agree rmn, the experience with this tablet has been sub par. I know when I first heard about the update being released I was checking around online to see if I could find a dl for it, none existed. I did finally go through the process of updating OTA after having to remove root from my 4.2 firmware. Since the update my tablet appears to operate the same except for the lag has returned. I believe that is because I now no longer have my tweaks setup on the device since I have no root. My real peeve with AT&T with this tab is the locked bootloader, come on man, I want to load up different roms and get rid of all this bloatware. We cant even get root access with this new 4.4!
Could I get a screenshot of your about screen on the tab that is not updating?
Click to expand...
Click to collapse
I just now saw your post. When I get back home I'll take a screenshot. It's set up identical to the one I upgraded and bricked. Rooted with kingo, installed the tweaks for this tab from development (KoolKit) and using a few xposed modules to change some notification/statusbar icons..Not much else you can do to these things, and if I had to guess, the only difference between the two would maybe be different versions of the KoolKit tweaks.
---------- Post added at 01:10 PM ---------- Previous post was at 01:08 PM ----------
DSTG said:
If it's in warranty, take it to the AT&T store. Tell them you did OTA and it 'got all screwy'. don't use terms like "bricked". Feign ignorance on all the workings of rooting and roms and stuff. Don't even use the term "Rom", use "operating system". Assuming you have the same boot error message I did, something to the effect of "there was a problem updating", apparently it's common enough that they'll get you to Samsung. Samsung will email you a shipping label, and in about a week to a week in a half, I had mine back functional again. Granted they put it on 4.4.2, which is a bummer, but at least it works. No questions asked. they didn't ask me about rooting or anything, I just told them I did the update, rebooted, it rebooted once, and then I had to reboot again and it had the error. First I took it so Samsung rep at best buy, he couldn't do anything, then I took it to the AT&T store. AT&T doesn't deal with tablet warranties, so that's why they put me on the phone with Samsung. On amazon, they have refurbished t217a's for $144.00, and on the description it says they're on 4.1.2 (rootable, and upgradable to 4.2.2 w/odin, which is also rootable. 4.2.2 firmware was a gigantic pain in the ass to get a hold of, but it's out there. I know it's not the answer you want, but hope it helps at least return the tablet into working state. I don't think we'll ever see a root for t217a on 4.4.2, nor any way to downgrade back to 4.2.2. Just not enough interest from the guys with the time and know-how. It was Samsung's bottom-end tablet, and the Tab S is just better for almost everyone. I use the Tab3 7.0 for work mainly because of it's size. I'm a pilot and I strap the tablet to my leg for approach plates and maps and stuff, and the size of the 7.0 is just right. The 8.0 and 8.3(?) is just a bit to big for that purpose. Anyway, I just hope (but not holding my breath) that Samsung + AT&T well at the very LEAST update the thing to lollipop so we can at least get full external SD card function again, because aviation maps and references and the sort take up a LOT of memory after a while..
Click to expand...
Click to collapse
I wish it was that easy, but I ditched AT&T years ago and went to straight talk. These tabs I purchased second hand.
rmntruexjr said:
I just now saw your post. When I get back home I'll take a screenshot. It's set up identical to the one I upgraded and bricked. Rooted with kingo, installed the tweaks for this tab from development (KoolKit) and using a few xposed modules to change some notification/statusbar icons..Not much else you can do to these things, and if I had to guess, the only difference between the two would maybe be different versions of the KoolKit tweaks.
Click to expand...
Click to collapse
No worries mate. Hmmm, if it was root that was stopping the update from showing it should have been the case on both tabs. Plus, mine was originally rooted when I searched for the update and it found it fine. You do definitely have to remove root to successfully update to 4.4, which totally blows, but with the SD card changes that came out in 4.4 I had to do it.
My LG G4 is dead and i need a good substitute ASAP on a tight budget ($200-$250 max). This pretty much limits me to 2015 era phones. Not getting another LG, Samsungs are too expensive and S6 has no microSD slot anyway. Narrowed it down to either an HTC One M9 and Moto X Force. Moto's limited development as well as an alarming number of nightmarish defective OLED displays has scared me off of it (shame as I love OLEDs).
So i'm about settled on an HTC One M9. I did my best to research any deal breaking hardware defects, any problems seem far less severe or common compared to G4 or Moto. Assuming I haven't missed anything...
So that said my question now turns to the software side- are there any carriers/variants of the M9 I should try to avoid buying? As the title says, I wish to unlock the bootloader, root, and eventually install custom roms etc. I'm prepared to pay for Sunshine if necessary provided all M9 variants are supported. I've done my best to read through as many threads and pages as I could before asking this. It SEEMS like i'd be safe buying pretty much any M9 and still be able to unlock bootloader, root and s off. Even Verizon models if i'm not mistaken? Am I correct in this assumption? I wanted to ask just to ensure I didn't miss any important caveats before buying.
I messed up buying an LG, many suffer from a motherboard defect causing unfixable bootlooping and mine finally succumbed the other day. Mine was also a region that didn't allow bootloader unlocking. I could root with some effort if I didn't mind being stuck forever on lollipop, but no custom roms and other annoying limitations.
I don't wish to repeat the same mistakes if I can avoid it, so any information regarding my query would be greatly appreciated. Any other advice or things to look out for regarding the M9 would be helpful too. Thanks very much in advance.
By the way, the version i'm looking at buying is listed as an AT&T model. From what I have seen, this variant seems to be pretty much perfect for doing all I want. But I still wanted to ask this in case I either get a different variant, or if the seller is listing the wrong version of the product. If all M9s are basically equal at this point, then I don't need to worry which kind I get.
Try to buy a worldwide edition. It's the sim unlocked from factory with region 401 ie x.xx.401.xx firmware version.
M9 is a solid phone. The camera isn't the greatest but it does take good shots. It can get a bit hot if charging and playing games at the same time and it is more than capable of draining the battery in an hour or two if you use resource intensive games or apps. The sound is very clear and boomsound is a major player in the satisfaction this phone gives, making the speakers significantly bassier than other devices on the market. The speakers 'can' be a little quiet at full but they ALWAYS stay crystal clear with no distortion at all.
You MUST get a protector case for this device as the front of the actual phone can crack if you apply pressure, by the front camera lens is cracked on mine. Tech21 make a good sturdy case for this device but it is a tad expensive at £30 GBP.
I Don't recommend using custom roms with this device as not only is the risk of a brick significantly higher it is also going to result in a slightly slower phone than stock rooted.
The different variants of this device are essentially the same but carrier locked versions can be a prick to find software to fix stuff.
In all you've made the right choice of phone if you plan on keeping it stock but the wrong one if you plan on modding it.
Beamed in by telepathy.
Sorry, but I have to disagree with some points of the post above this one.
If you live in the US then choosing either the unlocked/dev variant or the version of your carrier is the best choice. SKU 401 is optimized for the EU (in regard to supported frequencies and some GPS configurations). And it's important that you choose the correct hardware version for your carrier's technology (Verizon & Sprint: CDMA - all other variants: GSM). The firmware of CDMA devices and GSM devices isn't interchangeable. You can't even flash Sprint firmware on a Verizon device (or vice versa) without damaging it. However, you can change from one GSM firmware to a different one if you want to (S-OFF required).
Just for having it mentioned (I know that you don't need this information but who knows who else is going to read this): The Verizon version's bootloader cannot get unlocked via HTCdev (unlike the bootloader of all other versions). You need S-OFF for unlocking the bootloader of that version. Since sunshine needs root on the latest firmware version the only way to unlock the Verizon variant on the latest firmware is an xtc clip/java card. (This may change with a future update of sunshine.) Or you try to get a pre-Nougat Verizon M9 and use the temp-root of the sunshine app.
In addition, HTC provides RUUs for its US devices. Therefore, getting back to stock is easier with one of them than with all other non-US variants.
And in regard to custom roms: They don't hardbrick your device. The worst thing that can happen is a soft-brick/bootloop and that will only happen if you try to flash a custom rom whose base is newer than your phone's firmware (and some nougat roms are even compatible with the marshmallow firmware so this happens quite rarely in the recent time).
Aside from that, my phone is as fast while I use Viper 6.1 as it has been while I was playing around with the stock rom. If there really is a difference then you need laboratory equipment for being able to detect it. And I'm pretty sure that you get the same performance on other (sense-based) custom roms, as well.
The only thing that you need to be aware of is that there are more and more reports of dying memory chips. These nand deaths happen on stock phones and on modified phones. As far as I read, no one has been able to repair such a dead device except for HTC itself. I don't know what's the cause of the problem since I know enough people whose M9's are still working fine without any issues.
Sent from my HTC One M9 using XDA Labs
Thanks for the reply from both of you. I'm surprised and happy a mod actually replied too!
My LG was locked out from installing custom roms and such, but I have experience installing some on a first gen Galaxy S (currently using it as backup in fact). I'm sure things have changed somewhat, but I am aware of the potential risks in flashing custom roms. I've bootlooped and soft bricked my device doing so more than once. I'm not a programmer, but I was able to fix them all with patience, research and the right tools/software. I assume there are also methods to deal with soft bricks and bootloops on HTC One M9 if you consider it less of a threat than a hardware brick (which my LG G4 got even without flashing anything). I appreciate the warning and advice either way.
I'm not concerned with the carrier compatibility that much. I don't have service with anyone at the moment and can use whatever. Seller says the device is a GSM unlocked AT&T device, if accurate then i'm perfectly content with using GSM networks. Listing says "new AT&T carrier overstock item", which I hope means the device is okay. It's being advertised as running 5.0 Lollipop, which I assume means the stock rom it came with when first released and also hope is an okay starting point for doing whatever rooting and customization I want.
I hope the NAND issue doesn't crop up on the one I get though, that doesn't sound good. HTC attracted me because i've seen fewer people complaining about widespread hardware defects compared to many other phones. It's difficult to find phones that are a good value, are reasonably free of serious problems and include features I deem important (microSD card support for instance, and having reasonably fast processors). My options are limited.
I'm not sure if i'll need s off. I'm new to that term and don't know much about it besides it being some sort of HTC security. Not sure what doors would open up by having s off, still researching. Assuming the model I buy is accurately listed as AT&T, it sounds like I should be able to unlock the bootloader, root, flash TWRP and even get custom roms without having s off. Am I correct? Not even sure if it's required to flash kernels such as ElementalX.
That can happen if you post in the forum of a device that's owned by a mod. Don't forget that we're normal members, as well, if we don't moderate.
If you face a soft-brick you only need to keep both volume buttons and the power button pressed until the phone reboots to its bootloader. From there on you can boot to TWRP and only need to flash a working rom or to restore a backup of a working (stock) rom and the problem should be fixed. Hard-bricks only happen if you flash a CDMA firmware on a GSM device (or vice versa) or a Sprint firmware on a Verizon device (or vice versa). The phone will still be booting but from what I observed here on xda your SIM card won't be detected, anymore, even if you re-flash your phone's original firmware. Aside from that you can "kill" this phone if you're impatient while it's installing an update and power it down during the process (there was a time when that happened quite often). Therefore, I suggest you to just let it do it's thing after you started the update process. Depending on which update you want to install it might take up to approximately half an hour and the phone might reboot (and therefore vibrate) several times.
Correct, for flashing custom recoveries/roms/kernels you don't need S-OFF on this phone (as long as it's not the Verizon variant). Take a look at the further reading section of the ReadMe thread. There's an article linked that explains S-OFF. And Sneakyghost's firmware thread in the development section should contain an explanation, as well. If I remember correctly it should be located in the 5th post. Be aware that you don't need to (re-)lock this phones bootloader like you needed to do on older HTC devices if you want to flash a RUU with S-ON as long as you use the SD card method. That's the recommended method, btw.
I personally don't use a custom kernel. They had a huge impact on my last device (the HTC One S - released in 2012) but HTC seems to be learning at least from some of its "mistakes" since the battery optimizations are much better on the M9. Therefore, I haven't been using a custom kernel since one of the early versions of ElementalX. On the other hand, that means that I can't tell you whether the current version got optimized that much that it actually has an impact, again.
In regard to the nand issue: Don't forget that 95% of the posts here get made by people who face problems with their phones whereas most people don't post if everything is working fine. That might cause that an issue seems to be more common than it actually is. And as said in my last post, I haven't seen such a dead nand in real life, yet, and I know a lot of people who own this phone.
And last but not least a little tip: Find out your phone's firmware as soon as you get it. If it's a pre-4.x version (everything before android n) then try to find the latest 3.x RUU for your SKU*. If you install that one you will save some time that would otherwise be needed for installing a huge amount of OTA updates. (A RUU only needs around 5 minutes if you use the SD card method.) You can't directly install a 4.x RUU since HTC changed the encryption keys between firmware 3.x and 4.x. Therefore, you need to install the 4.x update via the software update function of the phone since OTAs aren't encrypted. More information, some useful files and instructions can be found in the ReadMe thread. (It's a big wall-of-text but reading and understanding it is worth the time that you need for doing so.)
Edit: * = Here's a download link for the latest 3.x AT&T M9 RUU (directly from HTC's server). However, now that I think about it I actually can't tell you whether the AT&T variant already received android n...
Sent from my HTC One M9 using XDA Labs
Hi!
I've had my G4 for about 1,5 years. I think it launched with android5, and it currently has 6.0.
The last few months it has become super slow, apps takes very long to start and such. I was starting to think that the newer OS would have slowed it down, so I tried a factory reset.
Now, the phone is still 6.0 after reset, and I'm a bit confused since I thought it was going to be an older version. But the phone now feels like a new phone, it's super responsive and fast. And now that it is a clean phone just like it was when I bought it, I was wondering if it would be possible to root this phone with this OS, and version
My phone is:
H815 European (bought in Norway)
droid v 6.0
software version V20g-EUR-XX
My question is can this be rooted, or do I have to downgrade to an older anroid OS? if so, could someone point me in the right direction? =)
wondering the same things - a current response would be amazing!
ElevateMusic said:
wondering the same things - a current response would be amazing!
Click to expand...
Click to collapse
I've heard about some "one click roots", but some say they cost money. also have no idea if they are scams or not. I wouldnt mind paying a small fee if it actually works. I dont dare to try any old rooting method from 3 years ago :/
Title says most of it, but i'll put the specifics.
The samsung j250-n is a J2 model made specifically for students in south korea.
It's a dumb phone, with no internet capabilities to help people focus on studies.
I got one in order to curb some internet addiction without having to rock a flip phone, and I like it except for the samsung bloat.
There are plenty of custom ROMs on here that I'd love to try, but none have the sm-j250n model number listed specifcally.
I haven't tried flashing any of these yet because this phones are hard to get in the west and I don't want to brick it.
Is flashing a ROM for different model a bad idea? Will I have to build my own ROM?
Thanks for reading, sorry I know it's an old phone and no one cares lol
If you do happen to have the answer though I will be forever grateful
Edit: build number is NMF26X.J250NKOU1ARL1 btw
you can try
LR7875 said:
you can try
Click to expand...
Click to collapse
I did, I put ressurction remix on it, and it was actually crazy.
The ROM worked, and it straight up gave the phone the ability to connect to wifi.
I guess since it has the physical antenna the software is the only thing preventing it.
Anyways, the whole point was no wifi so I just went back to stock ,where ill have to stay : P