Related
Can anyone help me find an tutorial that will help me go back to stock ROM and unroot, so it is like i never modified phone? http://forum.xda-developers.com/showthread.php?t=1710613 i found this but dont know if it is outdated or not.
http://forum.xda-developers.com/showthread.php?t=1949687
Sent from my WICKED fast GSIII
How do you propose to reset the counter with the current issue with latest jb ? Its always stuck at one, so do you think I should flash stock kernel + recovery before doing anything?
pakakid said:
How do you propose to reset the counter with the current issue with latest jb ? Its always stuck at one, so do you think I should flash stock kernel + recovery before doing anything?
Click to expand...
Click to collapse
I use triangle away and it works fine.. Also I used mobile Odin to flash back to stock but you can do it however you want. You also have the option to flash stock pre rooted or not
Sent from my WICKED fast GSIII
RedJack117 said:
I use triangle away and it works fine.. Also I used mobile Odin to flash back to stock but you can do it however you want. You also have the option to flash stock pre rooted or not
Sent from my WICKED fast GSIII
Click to expand...
Click to collapse
Really no matter what, everytime i check download mode my count stays at one and i found out this is because of the kernel and recovery. My last question is do you know where I can find the latest kernel and recovery to flash separately? Ive been looking and no luck and still am but thank you for your help thus far
pakakid said:
Really no matter what, everytime i check download mode my count stays at one and i found out this is because of the kernel and recovery. My last question is do you know where I can find the latest kernel and recovery to flash separately? Ive been looking and no luck and still am but thank you for your help thus far
Click to expand...
Click to collapse
Yeah triangle away works pretty good never had a problem... And I'm not sure where to find just the stock kernel but it comes with the rom of course.. And cmw is also put on with the pre rooted stock rom.
Sent from my WICKED fast GSIII
Hi i am new to rooting and wind up loosing my stock backup, i had to flash a custom rom and used clean rom 2.0 se.
the data is very slow i went form have 20mbps down to 3mbps download speed. i have been doing some research and i think it may have something to do with my basband, apn settings, and so forth. the issue is clean rom blocks any modification to the settings.
if im on the right track im assuming i can flash a newer verion of my basband and possible my basband?
badsband is- LTE 1.4 or 1400
basband version is- I317UCALJ2
any help ill be greatful, i am a power user and paying 130 a month for the lte speed i need it.
http://forum.xda-developers.com/showthread.php?t=2004650
You need the UCAMA4 baseband and the associated RIL files as well.
Are you familiar with Odin ??
The best way back to stock and keeping root is to Odin flash the stock rom.
I'll get the thread for you. ..BRB. .g
Edit. ..
Thread is on top. .Just follow the instructions provided and you'll be stock and rooted in no time.
I used this method a few days ago and it was perfect.
The device will be restored to factory software with root so back up anything you wish to keep first.
You will even have the option to go full stock from here with a few more easy steps.
Read carefully and use the appropriate files. ..g
gregsarg said:
http://forum.xda-developers.com/showthread.php?t=2004650
You need the UCAMA4 baseband and the associated RIL files as well.
Are you familiar with Odin ??
The best way back to stock and keeping root is to Odin flash the stock rom.
I'll get the thread for you. ..BRB. .g
Edit. ..
Thread is on top. .Just follow the instructions provided and you'll be stock and rooted in no time.
I used this method a few days ago and it was perfect.
The device will be restored to factory software with root so back up anything you wish to keep first.
You will even have the option to go full stock from here with a few more easy steps.
Read carefully and use the appropriate files. ..g
Click to expand...
Click to collapse
thank you for your help but when i download the image odin does not recognize it, i also downloaded a 7z zip managers and it says zero files.
daze28nyc said:
thank you for your help but when i download the image odin does not recognize it, i also downloaded a 7z zip managers and it says zero files.
Click to expand...
Click to collapse
it verted back to stock but the basband version did not change speeds are even worst now... is there somthing i may have did wrong
First of all if you go to settings and about device and than to status and then under imei does your phone show a bunch of numbers?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Andrew149 said:
First of all if you go to settings and about device and than to status and then under imei does your phone show a bunch of numbers?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
i got it was still on 4.1.1, it was weird something with firefox would not download the image properly, 4.1.2 is harible stock i dnt know whyi went back. at least know i can properly back up my stock rom and flash back custom. thank you for all help i got it know.
im going to use odin to flash 4.1.2 image so i can get root then add custom recovery.
daze28nyc said:
i got it was still on 4.1.1, it was weird something with firefox would not download the image properly, 4.1.2 is harible stock i dnt know whyi went back. at least know i can properly back up my stock rom and flash back custom. thank you for all help i got it know.
im going to use odin to flash 4.1.2 image so i can get root then add custom recovery.
Click to expand...
Click to collapse
count says 3 on anyway to set that two zero?
Yes...
By using "triangle away" from the play store.
But you would also need a stock recovery to do this, otherwise the counter will stay at 1 until you restore a factory recovery. That is done by flashing CF auto root again to give you the stock recovery.
Honestly, if you are going to stay rooted I would not worry about the counter.
It can easily be set to zero if you need to go stock for a warranty or service....g
Can I flash sprint factory rom to my at&t note 2?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Do you need to use triangle away when you first root your phone? Or can you just use it when you need to return the phone back to stock? I want to root and if I need to return my phone for warranty I want to be able to put the phone back to stock with 0 flash counter.
later not needed right away
hold on but.....
dpshptl said:
Do you need to use triangle away when you first root your phone? Or can you just use it when you need to return the phone back to stock? I want to root and if I need to return my phone for warranty I want to be able to put the phone back to stock with 0 flash counter.
Click to expand...
Click to collapse
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:
Mr_Jay_jay said:
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:
Click to expand...
Click to collapse
This is not even close to the truth.
Aerowinder said:
This is not even close to the truth.
Click to expand...
Click to collapse
and u say this because? I mean I'm just talking on my experience with triangle away and JB It didn't work, I would use it and it would reset but once I restarted the counter would go back to "1" and honestly I'm not the only one, so please if u know the rite answer please explain, just calling me a liar is not helping anyone at all.
Mr_Jay_jay said:
and u say this because? I mean I'm just talking on my experience with triangle away and JB It didn't work, I would use it and it would reset but once I restarted the counter would go back to "1" and honestly I'm not the only one, so please if u know the rite answer please explain, just calling me a liar is not helping anyone at all.
Click to expand...
Click to collapse
I'm not calling you a liar. I simply stated that your post was not factually accurate. TriangleAway does indeed work as intended on even the new MD5.
Using a custom recovery will cause your flash counter to trip on newer JB builds. This may be what you meant, but the issue is not related to TA. It's a bootloader "feature". You can witness this yourself by resetting the flash counter, then rebooting into download mode. Count will be 0.
Aerowinder said:
I'm not calling you a liar. I simply stated that your post was not factually accurate. TriangleAway does indeed work as intended on even the new MD5.
Using a custom recovery will cause your flash counter to trip on newer JB builds. This may be what you meant, but the issue is not related to TA. It's a bootloader "feature". You can witness this yourself by resetting the flash counter, then rebooting into download mode. Count will be 0.
Click to expand...
Click to collapse
So what u're saying is that my custom recovery is to blamed? I can say that statement is partially true. Wait.. u think I havent tried to reset my counter while on JB before?? I'm telling it didn't work why don't you go head and try to reset your counter and show that it did work.
check it out.
http://www.youtube.com/watch?v=LxpL46-Zd0A&feature=youtu.be
Mr_Jay_jay said:
So what u're saying is that my custom recovery is to blamed? I can say that statement is partially true. Wait.. u think I havent tried to reset my counter while on JB before?? I'm telling it didn't work why don't you go head and try to reset your counter and show that it did work.
check it out.
http://www.youtube.com/watch?v=LxpL46-Zd0A&feature=youtu.be
Click to expand...
Click to collapse
He's correct. Having a custom recovery will always trip the flash counter to 1 after every subsequent reboot. If you use Ta and reboot, you'll see 0. But the next time you reboot and don't use Ta you will see 1. It doesn't matter what ROM you run or how you've rooted in the end, the custom binary (TWRP / CWM) will Always trip the counter.
That being said if you don't want to continously trip the counter you're going to need to go back to stock recovery.
Sent from my SGH-T999 using Tapatalk 2
TheLastSidekick said:
He's correct. Having a custom recovery will always trip the flash counter to 1 after every subsequent reboot. If you use Ta and reboot, you'll see 0. But the next time you reboot and don't use Ta you will see 1. It doesn't matter what ROM you run or how you've rooted in the end, the custom binary (TWRP / CWM) will Always trip the counter.
That being said if you don't want to continously trip the counter you're going to need to go back to stock recovery.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I do Agree with his statment, however while I was on any ICS rom even with custom recovery, TA would work even after a reboot, so my counter would stay at "0" it wasnt after I upgraded to JB when the TA would reset after reboot. I will upload a video of doing TA on ICS and everything just to prove I'm not just arguing just because. but it will have to wait til l8er tonite.
Mr_Jay_jay said:
I do Agree with his statment, however while I was on any ICS rom even with custom recovery, TA would work even after a reboot, so my counter would stay at "0" it wasnt after I upgraded to JB when the TA would reset after reboot. I will upload a video of doing TA on ICS and everything just to prove I'm not just arguing just because. but it will have to wait til l8er tonite.
Click to expand...
Click to collapse
There is no need for a video. I understand what you are saying, and I'm telling you, it's because of the bootloader. Not TriangleAway.
I am on 4.1.1 and TA 2.90 works FINE, the Counter shows "0" after a bunch of reboots, and "Allow tracker to run" is checked...
The ONLY time the counter trips is when/if I boot into the recovery or downloader modes.
I guess some structure of the setup makes a difference. I am using Root66 SGHT999 Build JR003L.T999UVDLJA with a T999UVDMD5 Baseband
bobolinko said:
I am on 4.1.1 and TA 2.90 works FINE, the Counter shows "0" after a bunch of reboots, and "Allow tracker to run" is checked...
The ONLY time the counter trips is when/if I boot into the recovery or downloader modes.
I guess some structure of the setup makes a difference. I am using Root66 SGHT999 Build JR003L.T999UVDLJA with a T999UVDMD5 Baseband
Click to expand...
Click to collapse
kool. maybe that's a good workaround. thanks. but in my case still won't work.. but then again i'm 4.1.2. thanks!
Mr_Jay_jay said:
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:
Click to expand...
Click to collapse
You can avoid using Odin and flash old firmware (excluding system / kernel) directly via heimdall or dd (which can be nicely bundled into an update.zip), avoiding the whole mess of needing Odin/Windows and having to backup+restore your system.
I think I'll make an update.zip just to flash the oldest firmware onto our phones -- I just made one that flashes the latest UVDMD5 firmware. The ROM shouldn't make a difference as far as trying to clear the flash counter really, it's the firmware that would be blocking that.
Also, flashing ROMs through CWM Recovery (and probably other custom ones) avoids tripping the flash counter. If you can root your ROM and dd the recovery directly to your eMMC, it avoids tripping the flash counter. Then you can use CWM Recovery to flash things without tripping the counter as well.
Remember, these are just computers with Linux + kernel modifications + custom Java VM running on them, essentially. It's good to become comfortable with UNIX commands like dd.
mnasledov said:
Also, flashing ROMs through CWM Recovery (and probably other custom ones) avoids tripping the flash counter. If you can root your ROM and dd the recovery directly to your eMMC, it avoids tripping the flash counter. Then you can use CWM Recovery to flash things without tripping the counter as well.
Remember, these are just computers with Linux + kernel modifications + custom Java VM running on them, essentially. It's good to become comfortable with UNIX commands like dd.
Click to expand...
Click to collapse
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1
bobolinko said:
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1
Click to expand...
Click to collapse
Really? I mean I'm no authority on this, so I could be wrong but I based this off my findings last night. I was in Download mode quite a few times and got to see my Flash Counter which was at 3. I've gone into recovery dozens if not hundreds of times by now on this device as well as flashed dozens and dozens of things ...
Even if it was just an 8-bit counter that overflowed, I'd need to have flashed over 256 things which I don't think I've reached yet and it would be totally silly if Samsung made the counter so easy to defeat that an 8-bit numeric overflow would bring it back to 0.
Can anyone else chime/weigh in? I'm curious now. I heard that using dd is supposed to avoid the flash counter. As a software engineer, I'd think there has to be some hook to trip that counter and that hook would belong to whatever firmware is on the phone for flashing (i.e. the stock recovery) and that if any other software gains control of the phone, all bets are off.
bobolinko said:
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1
Click to expand...
Click to collapse
I don't know who told you all of that or where you read it but you are wrong.
The only things that trip the flash counter is when you flash a custom rom or a custom kernel.
Simply booting into stock or custom recovery will not trip the flash counter at all.
Think about it, that's why it's called a FLASH counter, it counts the number of rom and kernel flashes. LOL
Misterjunky said:
I don't know who told you all of that or where you read it but you are wrong.
The only things that trip the flash counter is when you flash a custom rom or a custom kernel.
Simply booting into stock or custom recovery will not trip the flash counter at all.
Think about it, that's why it's called a FLASH counter, it counts the number of rom and kernel flashes. LOL
Click to expand...
Click to collapse
It trips whenever I boot into TWRP though. Maybe some phones are different?
Sent from my SGH-T999 using Tapatalk 2
re: unlocked?
TheLastSidekick said:
It trips whenever I boot into TWRP though. Maybe some phones are different?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Perhaps since I have an unlocked phone it might make a difference?
I have a Galaxy S3 AT&T I747 Unlocked phone and am using it with Tmobile service.
That makes sense actually lol as it says I have an SGH-T999 and mine isn't unlocked. Probably the model of the phone acts slightly differently with Ta and recoveries.
Sent from my SGH-T999 using Tapatalk 2
In my case My counter won't move from "1" no matter what I do, Restart to download or Recovery ( TWRP), or flash a new rom which I do alot, only way it goes from 1 to "2" is when I do something to my phone and I need to odin back to stock and re root(which I did for research) ... it's then it gets trigger again.
Hey guys I was wonderng if using this app will trip the counter to 1? Or are there other ways to install custom recovery that won't trip the counter?
far as i know any custom recovery. ie twrp, cwm, philz, will all trip counter. stock won't but any others will.
OvrDriVE said:
far as i know any custom recovery. ie twrp, cwm, philz, will all trip counter. stock won't but any others will.
Click to expand...
Click to collapse
what's stock recovery? oh crap, is stuck recovery available all the time? Like if you messsed up bad on a ROM flash, you can go into stock recovery and restore your system?
Or is that only possible through custom recovery?
the one that comes installed on the phone. i'm not sure if using the twrp app will trip it if you use it to install a custom rom but i do know if you install any recovery other then the stock recovery it will trip it
custom is required to fix a bad flash. it can't be done from stock recovery
OvrDriVE said:
the one that comes installed on the phone. i'm not sure if using the twrp app will trip it if you use it to install a custom rom but i do know if you install any recovery other then the stock recovery it will trip it
custom is required to fix a bad flash. it can't be done from stock recovery
Click to expand...
Click to collapse
even if that flash doesn't replace/affect original BL?
edo101 said:
even if that flash doesn't replace/affect original BL?
Click to expand...
Click to collapse
what is it exactly that your trying to do. i assume it's not pop your warrenty counter. i also assume your on 4.3. from my own personal experience installing a custom rom kind of requires a custom recovery as you will want to do a backup. i also suggest using an app called samsungtool v 2.0 to backup your efs partition just in case. instructions related to installing a custom rom can be found in any rom thread on here. for the most part it's the same for every rom with exception to a few. but again you do all this on your own. btw this will pop your warrenty counter but if your sure about what your doing and your warrenty is up. might as well pop it.
OvrDriVE said:
what is it exactly that your trying to do. i assume it's not pop your warrenty counter. i also assume your on 4.3. from my own personal experience installing a custom rom kind of requires a custom recovery as you will want to do a backup. i also suggest using an app called samsungtool v 2.0 to backup your efs partition just in case. instructions related to installing a custom rom can be found in any rom thread on here. for the most part it's the same for every rom with exception to a few. but again you do all this on your own. btw this will pop your warrenty counter but if your sure about what your doing and your warrenty is up. might as well pop it.
Click to expand...
Click to collapse
yeah I bought the phone used heavily on eBay, I guess I want to make it look like i never rooted it, in the future when I want to sell it or however much I can get it (phone is kinda beat up)
What I want to do is install Sky Note Air on my 4.1.2 BL without going to 4.3 BL (I hate that thing with all the stories I've heard). I wonder if I can flash Sky Air with TWRP or if I need Mobile Odin in order to do it without touching my BL?
edo101 said:
yeah I bought the phone used heavily on eBay, I guess I want to make it look like i never rooted it, in the future when I want to sell it or however much I can get it (phone is kinda beat up)
What I want to do is install Sky Note Air on my 4.1.2 BL without going to 4.3 BL (I hate that thing with all the stories I've heard). I wonder if I can flash Sky Air with TWRP or if I need Mobile Odin in order to do it without touching my BL?
Click to expand...
Click to collapse
as long as the rom your trying to flash isn't a 4.3 rom you should be good on the counter. flash counter can be reset with triangle away and the warrenty counter only gets poped on 4.3 roms. 4.1.2 and 4.1.1 are fine. flash a custom recovery and flash any older rom and you should be fine
OvrDriVE said:
as long as the rom your trying to flash isn't a 4.3 rom you should be good on the counter. flash counter can be reset with triangle away and the warrenty counter only gets poped on 4.3 roms. 4.1.2 and 4.1.1 are fine. flash a custom recovery and flash any older rom and you should be fine
Click to expand...
Click to collapse
OH yeah the Sky Note Air is a 4.3 ROM I just want to put it on a 4.1.2 BL
not sure that'll work then
OvrDriVE said:
what is it exactly that your trying to do. i assume it's not pop your warrenty counter. i also assume your on 4.3. from my own personal experience installing a custom rom kind of requires a custom recovery as you will want to do a backup. i also suggest using an app called samsungtool v 2.0 to backup your efs partition just in case. instructions related to installing a custom rom can be found in any rom thread on here. for the most part it's the same for every rom with exception to a few. but again you do all this on your own. btw this will pop your warrenty counter but if your sure about what your doing and your warrenty is up. might as well pop it.
Click to expand...
Click to collapse
what is the efs partition?
efs holds all your t-mobile settings. or at&t or whichever company you go through. backing it up is just a precautionary thing. you do it just in case it gets messed up so you can restore it
i found the program i mentioned works and can restore it from your backed up file so
Flashing almost any custom ROM will increment the flash counter on any GN2. If you have the Knox bootloader it will also pop the Knox warranty bit.
The flash counter can be reset by using triangle away. No biggie. Knox can't be reset at this time. I avoid doing anything that would install the 4.3 Knox enabled bootloader it at all possible. If I need to return to stock for whatever reason I simple flash MrRobinson's root66 ROM (stock plus root) and triangle away my flash counter clean then unroot my phone to stock. No way to tell I was not on official firmware with it.
TWRP is not an application. It is a custom recovery like CWM etc. It can functionally do anything the stock recovery can and more. You have to use a custom recovery to flash a custom ROM on the gn2 with very few exceptions.
Stock recovery can be restored via an Odin flash of root66 or the Sammy stock ROM. I usually do root66 so triangle away can clean up the counter and still have stock recovery so as to avoid incrementing the counter after clearing it.
Hastily spouted for your befuddlement
Coug76 said:
Flashing almost any custom ROM will increment the flash counter on any GN2. If you have the Knox bootloader it will also pop the Knox warranty bit.
The flash counter can be reset by using triangle away. No biggie. Knox can't be reset at this time. I avoid doing anything that would install the 4.3 Knox enabled bootloader it at all possible. If I need to return to stock for whatever reason I simple flash MrRobinson's root66 ROM (stock plus root) and triangle away my flash counter clean then unroot my phone to stock. No way to tell I was not on official firmware with it.
TWRP is not an application. It is a custom recovery like CWM etc. It can functionally do anything the stock recovery can and more. You have to use a custom recovery to flash a custom ROM on the gn2 with very few exceptions.
Stock recovery can be restored via an Odin flash of root66 or the Sammy stock ROM. I usually do root66 so triangle away can clean up the counter and still have stock recovery so as to avoid incrementing the counter after clearing it.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Any tips as to why my 4G Modem is not working with the Sky Note 4.3 based ROM. Everything else is working except for the modem. I'm still on 4.1.2 BL it looks like (not sure how to check) but my mobile stuff is in tact. It just says mobile network state (disconnected) but all my phone info is correct. It even still has my MetroPCS/Tmo as my Network
edo101 said:
Any tips as to why my 4G Modem is not working with the Sky Note 4.3 based ROM. Everything else is working except for the modem. I'm still on 4.1.2 BL it looks like (not sure how to check) but my mobile stuff is in tact. It just says mobile network state (disconnected) but all my phone info is correct. It even still has my MetroPCS/Tmo as my Network
Click to expand...
Click to collapse
Probably that your APN is wrong.
Hastily spouted for your befuddlement
Coug76 said:
Probably that your APN is wrong.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
You were right. I googled Metro APN and now its working. THANK YOU!!
Btw any chance you know how to change my phone to read as a Tmobile phone instead of AT&T?
edo101 said:
You were right. I googled Metro APN and now its working. THANK YOU!!
Btw any chance you know how to change my phone to read as a Tmobile phone instead of AT&T?
Click to expand...
Click to collapse
Build.prop edit. Do a nandroid backup first, if you make a mistake you can have problems. Reboot into android. Save a copy of the file as build.bak then edit the build.prop so that any reference to SGH-i317 is changed to SGH-T889. Also anything that shows t0lte or anything similar can be changed to t0ltetmo. There are editor apps in the play store.
If things go bad, simply restore back to your nandroid via recovery. No fuss, no muss.
Hastily spouted for your befuddlement
OvrDriVE said:
i also suggest using an app called samsungtool v 2.0 to backup your efs partition just in case.
Click to expand...
Click to collapse
Can you please give us a link to this tool, coz' it looks like a good tool to have.
Thanks.
Sent from my SGH-T889 using xda premium
premiatul said:
Can you please give us a link to this tool, coz' it looks like a good tool to have.
Thanks.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s3/development/tool-samsung-tool-1-0-t2602325
current version is 5.0
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
re: NF1 firmware
calderonr said:
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
Click to expand...
Click to collapse
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Misterjunky said:
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Click to expand...
Click to collapse
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
calderonr said:
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
Click to expand...
Click to collapse
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
---------- Post added at 11:27 AM ---------- Previous post was at 11:16 AM ----------
In case you can't see my sig due to being in xda app or tapatalk:
NF4 files and instructions: http://forum.xda-developers.com/showthread.php?t=2834398
Or if you're dead set on NF1, there's a link to that thread at the top of the NF4 post. The instructions in post 2 of the nf4 thread are valid for nf1 add well.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF4 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF4 there is no way to revert back to MI7?
3) Does your NF4 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
5) What about rooting? Is your firmware rooted or do I need to do it myself? If so, what do you recommend for rooting?
Thanks!!!
calderonr said:
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF1 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF1 there is no way to revert back to MI7?
3) Does your NF1 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
Thanks!!!
Click to expand...
Click to collapse
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
calderonr said:
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
Click to expand...
Click to collapse
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
calderonr said:
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
Click to expand...
Click to collapse
No it would not work. The reason, as stated in a previous post, is due to eFused bootloaders. Once the efuse is tripped, it cannot be reset, and the bootloader will fail if it's value is lower than the fused value. Otherwise just flashing the bootloader backwards would work. If you go the odin route you will be protected by odin mode. If you try via recovery of a nandroid that contains the bootloader, it'll either just not work, or (worse) brick your device.
The fuses are tripped in a sequential order. 0,1,2,3 etc. JB BL can only operate on fused value of 1 or lower. KK BL can only install and function (depending on current version) at 3 or lower.
NB4 will fuse to 2. NE6 through NF4 I believe will fuse to 3, thus preventing the JB BL from functioning.
Hope that helps.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Let me know how it goes. I have to update mine to.. I'm on NB4 with no issues but I should update anyways.
Sent from my SM-N900T using XDA Free mobile app