Related
Hey all,
I recently sold my phone running CM 10 on eBay and the buyer said the phone is for her son, so she didn't know what software he wants on it....I figure I would be best off just sending it to them stock (stock firmware, unrooted, locked bootloader).
Is there anyway I can do this besides using Odin? I'm currently using a Mac, so anything method that I can use on OS X would be great, but if not, I can just get hold of a PC and do it via Odin if necessary
Heimdall would be your solution. It's a cross platform Odin alternative and there are native versions for PC, Mac, and Linux. The XDA thread is here:
http://forum.xda-developers.com/showthread.php?t=755265
It uses the same tar files that Odin would. As far as the software, I would run a stock unrooted TW for the kid personally. That way his mom can't come back and harass you about something he did because you left him with dangerous software. If he roots it and then breaks it, it's his own fault. Just tell her you left it on a stock version with no inherent risk involved, but just incase he needs to know (have her not tell the kid) the bootloader is already unlocked.
I would do stock rooted. Rooted is always a plus and may get you a few more dollars for it. Then people could choose their own ROM if they so desire. I know I desire just being stock rooted
shredder47 said:
Hey all,
I recently sold my phone running CM 10 on eBay and the buyer said the phone is for her son, so she didn't know what software he wants on it....I figure I would be best off just sending it to them stock (stock firmware, unrooted, locked bootloader).
Is there anyway I can do this besides using Odin? I'm currently using a Mac, so anything method that I can use on OS X would be great, but if not, I can just get hold of a PC and do it via Odin if necessary
Click to expand...
Click to collapse
Make it Stock, locked! incase they dont like the way the phone run, they can always blame you for modding and make you take it back! and it acts as a negative point in Dispute even though you mention it!
I ended up just Odin'ing it back to stock! Thanks guys
shredder47 said:
I ended up just Odin'ing it back to stock! Thanks guys
Click to expand...
Click to collapse
Definitely a good call... I do that with every phone I sell.
The way I see it is that if they're not intelligent / motivated / tech savvy enough to root and load something custom on their own then they'll probably have a hell of a time navigating the random problems you'd encounter running anything other than stock.
Hello XDA Developers,
Okay so here is my unusual situation...
I have two phones. I have one Verizon (d2vzw) SGS3 that I run CM 11 on with CWM Touch installed on that phone. On my second phone which is also a Verizon (d2vzw) SGS3 i was running stock 4.1.2 ROM which was rooted with CWM recovery manager. The stock SGS3 was the baseband version that supported multi windows.
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3. I knew there had been an update available for some time but I never decided to update my phone because i figured with it being rooted and with CWM recovery manager installed there was no way that the OTA update would work...
So like an idiot i went ahead and tried the update. I figured what is the worst that could happen? I figured that at the worst it was just going to tell me that the update failed and i would just be stuck with Android 4.1.2 which isn't the end of the world. I really like the multi windows setup. Moving on...i downloaded the update and I hit the install update button. My phone booted into recovery manager and it installed the update. When the phone rebooted I saw the message "Android is upgrading" and i thought whoa! no way!. After android finished upgrading which i believe was the dalvik rebuilding I saw a message in notifications saying "upgrade installation failed", however when i went into settings it now told me that i was running Android 4.3. So to me it looked like the upgrade took but I think the problem was that when it asked me to flash the stock recovery there was an option in CWM to say no and i choose that to keep CWM recovery manager instead of the stock recovery manager. Maybe i should have let the update install the stock recovery manager...
Now i knew ahead of time that if this update worked I was going to loose root but again I didn't think it was that big of a deal since I could just re-root my phone and I would be on a newer Android version. I looked around for the best rooting option and I wanted to use Chainfire's CF-AutoRoot exploit but I know that if you do not have the bootloader unlocked that there is a chance of bricking your phone. So after some research (which i should have done before i updated my phone!) i saw that there was an exploit out called "saferoot.zip" and that you could root your phone running a windows.bat file or a shell script if you are in Linux. Even though the program is for SGS4 many users on XDA with SGS3 phones reported success with "saferoot". So i tried saferoot 2 times with no luck. Finally on the third attempt (3rd times a charm!) i was able to root my phone and SuperSU was able to "disable KNOX".
So i now had my Verizon SGS3 updated from Android 4.1.2 to Android 4.3 and I had successfully re-rooted my phone. I was feeling good...
Until I wanted to make sure that CWM Recovery Manager was still on my phone. I opened up the app "quickboot" and choose to boot into Recovery Manager this is where the trouble began...
When my phone booted into recovery mode i saw a big Yellow Triangle. Under this very scary yellow triangle it said that "Verizon has detected unauthorized software on this phone. Please turn off the phone and take it into your nearest verizon store". Other something along those lines...
I thought I was in big trouble...
I could not get the phone out of recovery mode. I tried pulling the battery but every time my phone rebooted it just kept going back into recovery mode. The trick to get out recovery mode was to hold down Volume Down + Home for a few seconds then press the power button. This brought me to a new menu and i was able to hit "cancel" on installing a new OS and it rebooted my phone back to its normal state.
So finally here is my questions...
Question 1: I know i need to unlock my bootloader again. After you apply an OTA update it re-locks your bootloader right? Does anyone know of a method of unlocking the bootloader with the Verizon (d2vzw) SGS3 baseband version I535VRUCML1 running on Android 4.3?
Before when my phone was running 4.1.2 I unlocked the bootloader with Odin and the app EZ-UNLOCK but i don't think EZ-UNLOCK is going to work with Android 4.3
Question 2: Is there a way to get rid of that message about Verizon has detected unauthorized software on this phone? Now I know that ChainFire has a Yellow Triangle Away app on the Google Play store and I will happily buy it but I know that in order for it to work you first must have your bootloader unlocked right? If i try to use that app with my bootloader in a locked state i could brick my phone permanently right?
Is there possibly any file or exploit i can flash with either Odin or the app "Flashify" so that I can unlock my bootloader. Has anyone here tried unlocking their bootloader on their SGS3 running 4.3 with the app "EZ-UNLOCK" ?
I am very concerned about damaging my phone which is a company work phone so if i mess it up i will be in deep trouble...
Oh, one last question...
Question 3: Since i got that yellow triangle message about unauthorized software when i tried to boot into recovery mode could it have possible been because CWM recovery was somehow deleted with the OTA update? After i was able to get out of recovery mode I used the app "ROM Manager" to install CWM Recovery Again hoping that I might have a recovery manager... Now ROM Manager says that CWM Touch was installed successfully but I am not sure since I am kind of scared to boot into recovery mode again until I unlock this bootloader.
If my recovery manager is being blocked until I get my bootloader unlocked could i use the app "flashify" if i need to flash any files?
I know my situation might be a bit unusual but I am really going to need some help on this and someones expertise advice.
I hope to hear from someone soon...
XDA Members, have a great New Years and make 2014 count!
I thank you all for your time and assistance.
-droidshadow
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, debloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
well that stinks...
podspi said:
After accepting the 4.3 OTA, your bootloader is locked and there is no way to unlock it. My suggestion to you would be to grab the 4.3 ODIN file, reflash to 100% stock, root using saferoot, unbloat as wanted, and hope for the best.
Probably not what you wanted to hear, but there is no way to unlock the bootloader once taking the 4.3 OTA. Attempting to do so will brick the phone.
Click to expand...
Click to collapse
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
droidshadow said:
The only reason that I even attempted the upgrade is because next week I am going to purchasing the smart watch from the Samsung Galaxy Gear. For that watch (you can make calls from the watch) you need the upgrade to pair my SGS3 with my smartwatch when I get it next week.
Now this OTA update is quite new so that means that there still might be a chance to unlock the bootloader eventually when someone works it out right?
Big question:
Is it still possible to have CWM or TWRP with this 4.3 OTA update?
Thanks for the reply.
-droidshadow
Click to expand...
Click to collapse
To bad you took the ota. There is a twrp flashable rom for stock 4.3. And no you can not have custom recovery.
droidshadow said:
Okay so today i decided to go ahead and check for an OTA update on my stock (rooted) SGS3...
Click to expand...
Click to collapse
There's no need to read any further than that.... Sorry to be another bearer of bad news, but if a phone is rooted and you want it to stay that way, "OTA" should be a term that you never, ever, ever even think about !
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
so what entails for the future of samsung phones?
landshark68 said:
The S4 boot loader has been locked down with Knox longer than the S3 has, and no one has cracked it yet. I'd say the chances of this boot loader being cracked wide open are slim to none. If unlocking this boot loader were as simple as using EZ unlock 1.2, it would have been written about all over these and all forums.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Will KitKat + SELinux + Knox no longer allow us to enjoy the true beauty of Android? I think that is major BS.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones? I love Samsung phones and I love having the options of flashing custom roms or reverting back to stock and I really really love CWM recovery or TWRP recovery.
These phones are our property...
I understand that the software and the code is Samsung's or Verizon's yet we should be able to do what we want to our property. Could you imagine if Toyota or Chevy said that after you purchased one of their cars you could never paint it a different color or add custom rims + wheels! That would be ridiculous... It is the same concept here really.
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Difference is though, if you were to somehow screw up your car by customizing it you wouldn't try to take it back to the dealership and get a new car under a warranty claim. I would have to think at least part of the reason phone manufacturers and mobile carriers are locking down phones is all the "warranty" claims people are submitting after screwing up while rooting and flashing their phones. Warranty claims are for inherent manufacturer defects, not a hard brick from flashing the wrong software. If more people took responsibility for their mistakes and bought a new phone instead of making the carriers or manufacturers pay for their mistakes, perhaps this wouldn't be happening. I'm not saying absolutely, just perhaps. OK, I'll get off my soapbox now. Happy New Year everyone.
Different animal. You own the hardware, but the providers have the right to control the firmware since it can change how the phone interacts with the network.
Just like the firmware in your cars computer. The manufacturer and the federal government have control over what went in. Modifying it can be done, but it is a violation of EPA emission laws.
Modifying the paint, tires, rims etc is like putting a different case, bling etc on your phone
Your phone needs to have the 4.3 odin tar installed to clean the recovery.
Sent from my SCH-I535 using xda app-developers app
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
These phones are our property...
It is really sad that Samsung and Mobile carriers such as Verizon have resorted to this...
-droidshadow
Click to expand...
Click to collapse
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using xda app-developers app
DigitalMD said:
Its really Verizon, They have had many Moto and HTC phones with locked bootloaders , unless Verizon unlocks it, it won't be cracked.
Click to expand...
Click to collapse
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Insurance companies make big bucks by all the people who never file a claim...but i won't get into that.
Many of you have made excellent points and i respect that. I especially liked the comparison of car rims to phone cases i thought that was great!
Hopefully someone will work it out soon or some how an unlocked bootloader will get leaked.
Come one Verizon developers! Leak it! We wont tell!
I was planning on getting the NOTE 3 but i doubt that phone comes with an unlocked bootloader so this d2vzw (sgs3) will most likely be my last samsung phone that I ever buy. I guess i will have to stick with the Nexus phones... I am going to miss micro sdcards!
-droidshadow
droidshadow said:
I know but still i think it should be our choice! While there are millions of us out there that love to customize the software on our phone's by adding new recovery managers or custom rom's we are a small population to the rest of the stock phone using world...
Click to expand...
Click to collapse
Having that debate at this site is kinda silly.... Fact is, "we" will lose the fight against the carriers and/or manufacturers as it stands. The only way to really impact them is to STOP giving them our money, but you know what ? The number of people who "hack" their phones is a tiny percentage in the grand scheme. We'd probably get a "good riddance" response from them anyway.
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct and.... read on.
So what are our options now? Are we going to simply have to choose different phones like future Google Nexus phones?
Click to expand...
Click to collapse
That could be the only solution. I believe the success that Samsung/Verizon have had with locking down their phones will soon result in ALL phones on ALL carriers being locked down with little or no possibility of rooting or flashing.
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
It would be a shame....
xs11e said:
I suspect we've seen the end of modifying any phone on any network. I sure hope I'm wrong....
Click to expand...
Click to collapse
I just rooted and got into CM in the last month. Got rid of all the bloat and installed some neat little apps. And now, just when I get hooked, it's possible that my drug of choice may be going away.
hey there guys, i know this post is a little old, but i just wanted to share my story real quickly with you and to reiterate that messing with the boot loader on an sch-i535 running 4.3 is a HORRIBLE idea.
this is the first phone i have ever tried to root. i successfully rooted the phone, immediately i tried to run cwm recovery. HARDBRICK. i was so proud for all of five minutes that i rooted a phone on my first try. The phone would not power on in ANY mode. i could only get a red light to come on by plugging my phone into my computer with the battery out of the phone. after three days and alot of reading and some help from xda i managed to (amazingly) debrick my phone. I am now very VERY cautious of what i do with my rooted sch-i535 with its HORRIBLE 4.3 crap.
If you are truly hardbricked, im told that jigs (despite what is all over the internet) will not work. (maybe they do but a shop in texas told me a hardbrick will not revive by jig).
JTAG is the most dependable repair.
I revived my phone via debrick image on an sd card.
Bottom line, do everything you can to avoid the situation in the first place.
Never take updates. I unlocked boot loader on 4.3 with ez-unlock app booted into recovery and hard bricked my phone... The fun is over after 4.3...Had to send it to Tampa fl. To get JTAG and it worked.
droidshadow said:
So what is the going to happen to the future of Samsung Phones? Are we no longer going to be able to put custom ROM's and custom Recovery Managers on Samsung Phones?
Click to expand...
Click to collapse
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
xs11e said:
That's correct, given the amount of time the Devs have had to find a way to unlock the bootloader on the S3 and S4 w/o success, I believe it's hopeless.
Worse, I believe Samsung will share their technology and ALL cell phones will eventually have locked boot loaders and be un-rootable, un-flashable and, to me, at least, un-desirable!
I sincerely hope I'm wrong but I believe in a year or two any cellphone will be locked down to whatever software is installed at time of purchase.
Click to expand...
Click to collapse
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
An0nYm0u5.bat said:
How's the fun over??? Haha I've seen this same junk many times... I'm running 4.3 rooted. Safestrapped (cwmis garbage) alliance 23 build ROM CSC & build prop tweaks on sch-i535v on straightalk att side. Knox removed manually by me. All bands open except domestic 3g. (Working on it now).
So the funs over? I'm confused.. And how is that? Lol take your time. Research. Learn. Adapt. Achieve. If it can be locked. It can be unlocked. I've yet to run across a phone that I couldn't bring back from the supposed "hard brick" but I did find one I COULDNT brick on purpose. And I threw everything at it. Huwaei m8665 I think it was. I tried for two days to brick that little piece of junk, and not even wrong roots etc could. Lol
Click to expand...
Click to collapse
I agree with you if there is a way to lock it there is a way to unlock it.
is just a matter of time some smart brain will figure it out how to and share LOL
Hello,
I am very new to the rooting community, I am above average as a computer user, but mobile programming/rooting is an uncharted territory for me-please forgive the simple nature of this post.
I have a Huawei H892L Raven LTE phone.
I got this phone for cheap, so I didnt mind experimenting with rooting (as a novice) with it because if i bricked it I could just go back to my S4 or note 3.
anyways I have looked all around, looked at other threads, watched videos and most of what I saw was kind of vague. i have grasped the basic concept (i think..) of rooting but some areas are still unclear.
1. I rooted my phone and now I want to make sure I have a backup of it before i proceed with doing much else with it. I have downloaded CWM recovery and some other recovery tools in hope to make a backup of my device. But most of them require premium accounts to make backup from what i can gather.
Using an app called ROM tool box lite > Rom Installer >I see the options to Backup current ROM, Backup Recovery, and Backup Kernel..
Now do I want to make a "backup of my current Rom"? Would this option backup the stock H89RL Raven LTE image that is currently on the phone? or is this feature mean it is used to backup a custom rom that say i downloaded, used on my phone, maybe tweeked a little bit and wanted to back up?"
or when I am backing up my Raven H892L stock image should i use the "Backup recovery" and "backup kernel" options? I used both of these, but I am not sure if those options will suffice as properly and safely giving me reassurance that if i mess up anything i can recover the original format of the phone.
sooo.. what exactly do I need to use and what steps do i need to take to reassure I can play with new root and be able to fix it should i mess up? what file format are proper backups of my phones current settings... .img? and what steps would I take to recovery the old image of the phone?
2. I also need some clarification about SuperUser and SuperSU apps. I used kingoroot and it installed kingo superuser on my phone. Which is the preferred superuser app I should use? if i delete the kingo superuser app will it take away my ability to easily unroot my phone via pc the same way i rooted it? (there is an option on kingoroot when i plug my phone into my computer to unroot) the only reason i kept Kingoroots superuse over superuserSU is because I wanted to make sure I could unroot. what exaclty is the purpose of these apps? to delegate permissions? or is there other uses for them?
3. custom roms- I want to put a custom rom on my phone. i do not see any custom roms for my specific mobile device, (obviously because many people do not have this device, i really didnt expect there to be) Is there, for a lack of better words a "universal," or a custom rom I could use that would be compatible with my device? Are most ROMS used for android not device specific. (Im really sorry if thats a really stupid question.) I dont really understand this. is there a custom rom you would suggest me using?
4. What are some useful tools or cool things that I can do with my newly rooted device? any suggestions? what are your favorite things to do with a rooted device? Am i kind of out of luck because of the specific device I have not being so popular? I'm being a huge newb here but I thought I would give this forum a try.
I really really appreciate you taking the time to read all that if you did!
Hello,
Welcome to XDA.
Ok, first, as far as I know you cannot make a backup without custom recovery. I have searched for a custom recovery for you but I did not find one anywhere in XDA or Google.
You will have to find a custom recovery(CWM or TWRP) for Huawei H892L if it exists anywhere and install it however the guide you find it in says to install it, the method used will depend on what file format your recovery file is, the method also varies from device brand to device brand. Recoveries are very specific things, the recovery for one device brand/model number does not work on another device brand/model number, sometimes recoveries can be shared by devices that are virtually identical in hardware/software but more than most of the time trying a recovery for one device on another results in a bricked device similar to flashing the wrong BIOS on a PC.
As for the superuser, superSU and kinguser, if you have Kinguser I recommend you use the supersume app from the playstore to switch to superSU, it does it for you. If at some point you choose to unroot, there is an option in the superSU app settings that lets you unroot and uninstall superSU and root is completely gone.
Custom ROMs are flashed in custom recovery, for copyright and trademark reasons most custom ROMs have to be flashed along with a compatible Google apps package, referred to as Gapps. They both come in .zip format. The Android version of your ROM and Gapps have to match, 4.4/4.4, 5.0/5.0, 5.1/5.1 etc.. The custom ROMs are also device brand/model specific and also can't be shared. No, there is no "universal" android ROM. You are correct that your device is not popular so you most likely won't find anything as far as custom ROMs and recoveries. You would have been better off rooting and customizing your S4(depending on your model number) or your Note 3, there is plenty available and they are actually much easier devices to work with, I love my Samsung devices, they are easily rooted and usually easy to fix if a modification goes wrong, the device you have will easily get messed up and would likely be almost impossible to fix.
Root gives you control over everything about the device, you can modify any and every part of your systems software to look and function how you choose it to do, you can even modify the apps you install or even add features that it didn't have before as long as your hardware supports it, for example my Straight talk S3 supports Hotspot and tether even though it didn't come with it, and that's just the least of the mods my device has.
For more answers to your questions you can post in the thread linked below, there are many knowledgeable members in that thread, including myself.
http://forum.xda-developers.com/showthread.php?t=2257421
Good luck in your journey, if you choose to customize one of your Samsung devices(which i personally recommend for someone new to this because they are easy to repair), they are virtually impossible to brick beyond repair unless you just completely lose your head and use something meant for another device and 95% of the time even that is fixable.
thank you so
Droidriven said:
Hello,
Welcome to XDA.
Ok, first, as far as I know you cannot make a backup without custom recovery. I have searched for a custom recovery for you but I did not find one anywhere in XDA or Google.
You will have to find a custom recovery(CWM or TWRP) for Huawei H892L if it exists anywhere and install it however the guide you find it in says to install it, the method used will depend on what file format your recovery file is, the method also varies from device brand to device brand. Recoveries are very specific things, the recovery for one device brand/model number does not work on another device brand/model number, sometimes recoveries can be shared by devices that are virtually identical in hardware/software but more than most of the time trying a recovery for one device on another results in a bricked device similar to flashing the wrong BIOS on a PC.
As for the superuser, superSU and kinguser, if you have Kinguser I recommend you use the supersume app from the playstore to switch to superSU, it does it for you. If at some point you choose to unroot, there is an option in the superSU app settings that lets you unroot and uninstall superSU and root is completely gone.
Custom ROMs are flashed in custom recovery, for copyright and trademark reasons most custom ROMs have to be flashed along with a compatible Google apps package, referred to as Gapps. They both come in .zip format. The Android version of your ROM and Gapps have to match, 4.4/4.4, 5.0/5.0, 5.1/5.1 etc.. The custom ROMs are also device brand/model specific and also can't be shared. No, there is no "universal" android ROM. You are correct that your device is not popular so you most likely won't find anything as far as custom ROMs and recoveries. You would have been better off rooting and customizing your S4(depending on your model number) or your Note 3, there is plenty available and they are actually much easier devices to work with, I love my Samsung devices, they are easily rooted and usually easy to fix if a modification goes wrong, the device you have will easily get messed up and would likely be almost impossible to fix.
Root gives you control over everything about the device, you can modify any and every part of your systems software to look and function how you choose it to do, you can even modify the apps you install or even add features that it didn't have before as long as your hardware supports it, for example my Straight talk S3 supports Hotspot and tether even though it didn't come with it, and that's just the least of the mods my device has.
For more answers to your questions you can post in the thread linked below, there are many knowledgeable members in that thread, including myself.
http://forum.xda-developers.com/showthread.php?t=2257421
Good luck in your journey, if you choose to customize one of your Samsung devices(which i personally recommend for someone new to this because they are easy to repair), they are virtually impossible to brick beyond repair unless you just completely lose your head and use something meant for another device and 95% of the time even that is fixable.
Click to expand...
Click to collapse
I really appreciate you taking the time to reply to my questions, and so thoroughly too! And that sounds like a good idea, I am going to just root my S4 and use that for a beginners root device. Nice to know it will be hard to mess that up. so i will download supersume and switch over to superSU automatically.. I also have straight talk, is it really possible to make my s4 a hotspot?? i heard something about that, but also heard something about straight talk being fussy about it? is there a way they would even know, by analyzing data intake maybe? idk where i heard that from. but Anyways. thanks for all the info. I think I will stick around in these forums and gather information and maybe ask for help if I need it.
Have a good night
k
kwotkwot said:
I really appreciate you taking the time to reply to my questions, and so thoroughly too! And that sounds like a good idea, I am going to just root my S4 and use that for a beginners root device. Nice to know it will be hard to mess that up. so i will download supersume and switch over to superSU automatically.. I also have straight talk, is it really possible to make my s4 a hotspot?? i heard something about that, but also heard something about straight talk being fussy about it? is there a way they would even know, by analyzing data intake maybe? idk where i heard that from. but Anyways. thanks for all the info. I think I will stick around in these forums and gather information and maybe ask for help if I need it.
Have a good night
k
Click to expand...
Click to collapse
As long as your S4 doesn't have a locked bootloader you should be fine, if its locked then you'll likely brick it trying anything, post me your model numbers for both the S4 and the Note 3 and I'll see what is out there before you do anything.
Sent from my SCH-I535 using Tapatalk
The note is in my storage two hours away. it also has a crack on the screen so will hold off on that.
But the s4 model number is SCH-I545
Sent from my HUAWEI H892L using XDA Free mobile app
kwotkwot said:
The note is in my storage two hours away. it also has a crack on the screen so will hold off on that.
But the s4 model number is SCH-I545
Sent from my HUAWEI H892L using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, the i545 is one that is a pain, what firmware version does it have? Is it easy to get to? If it's one of the versions with locked bootloader you can root it possibly but custom recovery and custom ROMs is absolutely out of the question. With locked bootloader you'll be stuck with using Safestrap and modified stock ROMs.
Sent from my SCH-I535 using Tapatalk
Android version 5.0.2
Secure boot status says type; samsung
How exactly do you check the firmware, I was under the impression that is was Android version.
Sent from my HUAWEI H892L using XDA Free mobile app
I also have a Motorola droid razr Android version 4.1.2 may be worth considering. I'll do some investigating on whether I can root it. Thanks for conversing with me, I am starting my second degree in the spring. I will be taking computer programming, and i Can't wait to get to the mobile side of the curriculum. Hopefully I will be ahead of the game by then XD
Sent from my HUAWEI H892L using XDA Free mobile app
kwotkwot said:
Android version 5.0.2
Secure boot status says type; samsung
How exactly do you check the firmware, I was under the impression that is was Android version.
Sent from my HUAWEI H892L using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure this isn't 5.0.1? i'm finding i545 root for 5.0.1 but no 5.0.2.
The thread below is root for 5.0.2
http://forum.xda-developers.com/galaxy-s4-verizon/general/rooted-galaxy-s4-t3158098
you"ll have to ask about the bootloader and whether or not you have to use custom recovery(CWM, TWRP) or Safestrap in the i545 forum linked below.
http://forum.xda-developers.com/galaxy-s4-verizon/help
Be careful, I have tried to repair an i545 that had been flashed with TWRP over the locked bootloader, there is no saving it if this is done, be certain of what you have before you do anything, either way isn't too difficult you just have to be sure of which way you have to go.
Exactly which razr model number do you have?
It is 5.0.1 my fault! I was looking right at it too. So the secure boot status=Samsung means the boot loader is definately locked?
On The Razr i have I can't read the model number its scratched on the back..any way to tell via the settings? Maybe xt912? Its not the RAZR max...idk I can't make it out. In the settings it says
Mod number= Droid Razr
Android version = 4.1.2
Baseband version CDMA_N_05.21.00RLTEDC_U_09_.1D.00
Build number 9.8.20-72_VZW-16
Sorry for the questions.
I think this phone is rootable. Def needs a new screen. BTW I'm in NC too. Kitty Hawk NC on the beach
Sent from my HUAWEI H892L using XDA Free mobile app
correction it is 5.0.1
okay MOTXT912W is the model number. i just ordered a replacement screen for it, maybe ill make this badboy my new phone if a root is possible.
Im stressed out thinking about my note 3.. i really hope its in storage, the more i think about it the more I wonder if it got thrown out by my gf bc the screen was trashed.
sure hope not i miss that thing. but im going back to my storage unit maybe this week ill rummage through and see if i can find it.
surely one of my many phones can accept custom roms!
kwotkwot said:
It is 5.0.1 my fault! I was looking right at it too. So the secure boot status=Samsung means the boot loader is definately locked?
On The Razr i have I can't read the model number its scratched on the back..any way to tell via the settings? Maybe xt912? Its not the RAZR max...idk I can't make it out. In the settings it says
Mod number= Droid Razr
Android version = 4.1.2
Baseband version CDMA_N_05.21.00RLTEDC_U_09_.1D.00
Build number 9.8.20-72_VZW-16
Sorry for the questions.
I think this phone is rootable. Def needs a new screen. BTW I'm in NC too. Kitty Hawk NC on the beach
Sent from my HUAWEI H892L using XDA Free mobile app
Click to expand...
Click to collapse
OK, I'll check the moto out by the specs you listed.
I've never been to Kitty Hawk. I always wanted to go and see where flight was born.
Sent from my SCH-I535 using Tapatalk
The ordered a new digitizer\glass\blackframe and an eb20 battery too for the xt912 Razr.. But I'm thinking about doing the RAZR maxx conversion and putting an Eb40 battery on it. I know someone named wando Did it on these forums, exciting stuff.
Sent from my HUAWEI H892L using XDA Free mobile app
Yeah I actually went to first flight highschool. You should visit its nice even in the winter!
Sent from my HUAWEI H892L using XDA Free mobile app
kwotkwot said:
The ordered a new digitizer\glass\blackframe and an eb20 battery too for the xt912 Razr.. But I'm thinking about doing the RAZR maxx conversion and putting an Eb40 battery on it. I know someone named wando Did it on these forums, exciting stuff.
Sent from my HUAWEI H892L using XDA Free mobile app
Click to expand...
Click to collapse
I've never had a RAZR, never heard of that mod.
Sent from my SCH-I535 using Tapatalk
Basically taking the RAZR Maxx battery (3300 mAh, eb40) and replacing the regular RAZR xt912 battery (1900 mAh eb20) with it. Making it essentially a RAZR max
Sent from my HUAWEI H892L using XDA Free mobile app
Hi,
I know this is a NooB question, I know HOW to root my S4, and have a RIFF box, but I need an honest opinion.
I just bought a new mobo to replace my old one with the dead eMMC. It came with Android 4.3, Knox, and firmware version M919UVUEMK2. T-Mobile is offering me an OTA update to M919UVSFQA1 every 24 hours. I want to root my device, simply so they cannot take that ability away from me. I'm too busy really to develop my own apps now, but I don't think it's fair to tell me how I can and can't use MY phone.
If I accept the update, from what I read, it's most likely I will be able to root it, using CF Auto Root, but RegionLockAway (my phone is already unlocked from T-Mobile giving me the code - do I still need this?) may not work. Is M919UVSFQA1 still rootable? I know it will trip the KNOX bit, that's OK. If I root my M919UVUEMK2 the way it is, will it trip the KNOX bit?
Also, what are these "Security Policy Updates" offered by Google they are asking me to accept? Security policy for malware, or security policy against me?
I guess I want my cake and eat it too. I want the stability and security against malware, and the latest baseband, but I don't a security update against myself. If I root my phone the way it is (M919UVUEMK2), will it trip the KNOX bit anyway?
All I am asking is, have I got anything to lose by accepting the OTA update? Will I lose rooting / bootloader options, or is my bootloader already locked on MK2, and it will still trip the KNOX bit. If so, and nothing's different, I will accept the OTA update first so my phone is the latest OFFICIAL version, then I can be sure my new rooted phone is most stable, as I doubt T-Mobile will support a rooted phone.
My S4 employs E-Fuses (a.k.a. the "Knox" bit) and once they're blown, that's it. If you want them un-blown, you need to buy a new CPU hence a new mobo. This is why I'm wary of ANY update, especially security. (Google eFuse if you're interested in the technology). eFuse was a brilliant idea from IBM, but was abused like most other technology.
Thanks,
-Rob
filter4ever said:
Hi,
I know this is a NooB question, I know HOW to root my S4, and have a RIFF box, but I need an honest opinion.
I just bought a new mobo to replace my old one with the dead eMMC. It came with Android 4.3, Knox, and firmware version M919UVUEMK2. T-Mobile is offering me an OTA update to M919UVSFQA1 every 24 hours. I want to root my device, simply so they cannot take that ability away from me. I'm too busy really to develop my own apps now, but I don't think it's fair to tell me how I can and can't use MY phone.
If I accept the update, from what I read, it's most likely I will be able to root it, using CF Auto Root, but RegionLockAway (my phone is already unlocked from T-Mobile giving me the code - do I still need this?) may not work. Is M919UVSFQA1 still rootable? I know it will trip the KNOX bit, that's OK. If I root my M919UVUEMK2 the way it is, will it trip the KNOX bit?
Also, what are these "Security Policy Updates" offered by Google they are asking me to accept? Security policy for malware, or security policy against me?
I guess I want my cake and eat it too. I want the stability and security against malware, and the latest baseband, but I don't a security update against myself. If I root my phone the way it is (M919UVUEMK2), will it trip the KNOX bit anyway?
All I am asking is, have I got anything to lose by accepting the OTA update? Will I lose rooting / bootloader options, or is my bootloader already locked on MK2, and it will still trip the KNOX bit. If so, and nothing's different, I will accept the OTA update first so my phone is the latest OFFICIAL version, then I can be sure my new rooted phone is most stable, as I doubt T-Mobile will support a rooted phone.
My S4 employs E-Fuses (a.k.a. the "Knox" bit) and once they're blown, that's it. If you want them un-blown, you need to buy a new CPU hence a new mobo. This is why I'm wary of ANY update, especially security. (Google eFuse if you're interested in the technology). eFuse was a brilliant idea from IBM, but was abused like most other technology.
Thanks,
-Rob
Click to expand...
Click to collapse
There are several threads covering most of your questions or at least have answers somewhere in them in the Tmobile S4 forum if you take the time to search and read. I don't have Tmobile S4 so I don't know the details.
And it's called qfuse in Samsung devices, not e-fuse.
Sent from my SM-S903VL using Tapatalk
Thanks
Thanks. I've had a lot of homework so I haven't had the time to search very deep. I found a Knox less NH7 update and installed it, guess I'm just going to have to wait for the OTA to become available.
qFuse
Droidriven said:
There are several threads covering most of your questions or at least have answers somewhere in them in the Tmobile S4 forum if you take the time to search and read. I don't have Tmobile S4 so I don't know the details.
And it's called qfuse in Samsung devices, not e-fuse.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks. If you're interested, I found the code that burns qfuses. Bootloader.rollback(blowFuse) at 0x00004000 (I think). Has only to do with bootloader upgrades.
Qfuse, for Qualcomm, duh. Still the same thing though. It makes me sick that they would go THAT FAR to prevent even the advanced nerds from doing with... I guess I'll say Samsung 'so phone now, I won't buy an S7 if I don't own it fully. It's the principal, I can understand if it is their network they are worried about security, but I don't see how that is an issue. if I buy it, it's mine. If I fixed it from the garbage, it's REALLY mine. Just who do they think finds these bugs and security flaws? The average user? If phones get bricked, wouldn't they want to hire someone who learned what they're doing? Using to pirate apps, OK, I can see that it not right. Running your own software and being able to repair the firmware? If I can run it over with my car and break it, I should be allowed to do anything in between.
Anyways, thats my rant about qfuses, efues, any permenent harfware changes being used this way.
filter4ever said:
Thanks. If you're interested, I found the code that burns qfuses. Bootloader.rollback(blowFuse) at 0x00004000 (I think). Has only to do with bootloader upgrades.
Qfuse, for Qualcomm, duh. Still the same thing though. It makes me sick that they would go THAT FAR to prevent even the advanced nerds from doing with... I guess I'll say Samsung 'so phone now, I won't buy an S7 if I don't own it fully. It's the principal, I can understand if it is their network they are worried about security, but I don't see how that is an issue. if I buy it, it's mine. If I fixed it from the garbage, it's REALLY mine. Just who do they think finds these bugs and security flaws? The average user? If phones get bricked, wouldn't they want to hire someone who learned what they're doing? Using to pirate apps, OK, I can see that it not right. Running your own software and being able to repair the firmware? If I can run it over with my car and break it, I should be allowed to do anything in between.
Anyways, thats my rant about qfuses, efues, any permenent harfware changes being used this way.
Click to expand...
Click to collapse
I'll check out that qfuse code just for curiosity.
The main reason they work so hard to prevent even advanced users from altering the devices is because they got tired of losing money replacing devices under warranty that had been bricked, technically the warranty is voided when a device is modified but when fully bricked they can't tell that their was any attempt to modify it.
I agree, when you buy something it is yours to do with as you wish but most devices on plan aren't owned, technically they are considered mortgaged property, these devices that are advertised as free with a plan aren't free, it's being paid for in your monthly bill. This means it's just like financing a car, you have to have full collision insurance coverage to protect their investment. That is, in effect, the thing that gives Samsung or your carrier the right to do what they've done to protect their investment.
It would be a logistical nightmare if they had it so that people that actually own the devices didn't have to worry about qfuse but at the same time have it so that customers still paying for the device do have to worry about qfuse, so they just have them all like that across the board.
Sent from my SM-S903VL using Tapatalk
It's in the partition "SBL3" at offset 0x31160. I have a dump of my phone if interested, but I would like to remove specifics (make sure I'm not signed in, did factory wipe, imei, etc)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It appears to be C code (compiled possibly encrypted) before or after the file name. Please don't let this fall into the wrong hands :0
I bought an app, "MobileODIN", that seemed a bit iffy, but I thought I'd give it a try. T-Mobile has the OTA update, they want me to use Kies (yeah, right) so I am using that stupid RapidGator thing (oh well, at least they dont ask for my credit card, I mean, WTF?, who would do such a thing)? Anyways, EverRoot - Part of the PRO version I bought as I wanted to try Loli but KitKat is the latest. T-Mo just released M919UVSFQA1 on 2/8, if I can do things like EverRoot, do you think it would successfully castrate that code? Even if it can preserve root, if I lost it, I may not be able to get it back. Right now I'm running the M919UVUFNH7 Stock Rooted, Permissive NH7, and NH7 non-hlos and it works good. Read a couple posts on mobile ODIN and it did say it would root firmware, keeping it from being lost, BUT - not a full stock image (which possibly has boot.img - just what that nasty little firebug code is looking for in SBL3). I will post in mobile ODIN, but have you heard of an unlocked boot.img, one that doesn't have this nasty little line of code?
Just took upgrade.
Well i just flashed the ota with odin and even with supersu pro 2.79 runing survival mode it took root from me. Now. I know this may be a shot in the dark here but what about doing something similar of the i337 and flashing a previous kernal rooting locking in survival and then reflashing kernal? I have thr ota file saved on my laptop if you would need it to break it down and see what is possible. I will toy around with it as i have time to. Having 4 youngins gets a little difficult to have a whole lot of time to invest myself to most of this stuff anymore. Eventually it will work right? Lol GL And let me know if we want to give this a shot or not
xXxCyanidexXx
Been playing around the with the new upgrade trying to find some sort of root method for it. I was able to run king root and got it to suscessfully get root access, after running it like 4 or 5 times in a row. However I didn't really care much for king root itself. Just the extra unnecessary garbage it has. So I tried to swap root management over to super su.... so far i have not had any luck with that part yet.... ain't giving up on it though, so as soon as I find something successfully able to get root aside from kingroot I will let you guys know.
xXxCyanide87xXx said:
Been playing around the with the new upgrade trying to find some sort of root method for it. I was able to run king root and got it to suscessfully get root access, after running it like 4 or 5 times in a row. However I didn't really care much for king root itself. Just the extra unnecessary garbage it has. So I tried to swap root management over to super su.... so far i have not had any luck with that part yet.... ain't giving up on it though, so as soon as I find something successfully able to get root aside from kingroot I will let you guys know.
Click to expand...
Click to collapse
Did you try the Supersume app? Did you try normal SuperSU or did you try systemless SuperSU?
Just make sure you get rid of everything else that came along with Kingroot, it's malware.
Sent from my SM-S903VL using Tapatalk
Switched around some...
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.
xXxCyanide87xXx said:
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.
Click to expand...
Click to collapse
Ok, try SuperSU in systemless mode, it'll probably work for you. Good luck.
Sent from my SM-S903VL using Tapatalk
Just got home gonna get twrp .tar for Odin and the systemless zip and see what I don't break lol
New firmware successfully rooted using Kingo Root to initially access root then flashing TWRP 3.1.0-0 using Mobile Odin Pro then flashed SuperSU 2.79 with TWRP after recovery was flashed. Rebooted no problems, then froze Kingo and removed it...
Yes I'm sure there a far easier way to do this but I am patting myself on the back for not screwing up the phone considering I have still yet to back anything up >. < So thanks for starting this post and giving me something to amuse myself with these past couple of days (-:
xXxCyanide87xXx said:
New firmware successfully rooted using Kingo Root to initially access root then flashing TWRP 3.1.0-0 using Mobile Odin Pro then flashed SuperSU 2.79 with TWRP after recovery was flashed. Rebooted no problems, then froze Kingo and removed it...
Yes I'm sure there a far easier way to do this but I am patting myself on the back for not screwing up the phone considering I have still yet to back anything up >. < So thanks for starting this post and giving me something to amuse myself with these past couple of days (-:
Click to expand...
Click to collapse
Good to go. Actually, the method you used is about the easiest, it's commonly the go-to method if Supersume doesn't work. You did good.
Sent from my SM-S903VL using Tapatalk
Thanks for the update!
So you flashed OTA at first, then re-rooted using KingoRoot? I used CF Auto Root, and CF RegionLockAway before upgrading to NH7, but I haven't tried this yet.
Here's the firmware for all who want to flash the old fashioned way using ODIN (not OTA or Kies).
Rapidgator Mirror: http://rapidgator.net/file/cc090b9fd3b077b9041ff1b6df3bf889
AltaFile Mirror: https://alfafile.net/file/vbGh
If these links don't work (I had a hell of a time), PM me or post below, I can send you a direct link.
Did you originally try to flash using Mobile Odin, regular Odin, or the OTA stock update? I don't know if mobile ODIN works yet - I'm not really into nightly builds yet. The only reason I bought mobile ODIN was because if it already HAS root, it can "castrate" the code like this:
I found in SBL3. My "new" mobo that came with M919UVUFMK2 (WITH knox ). Jellybean 4.3, I asked for a 4.2.2, but they didn't have any in stock. I disabled KNOX, but I think this is still in here.
Thank you for letting me know, I finally rooted the MK2 using CF Auto Root, T-Mo gave me the unlock code (since my previous mobo was already unlocked and IMEI changed), but I used CF Region Lock Away before upgrading. (Works GREAT, but not sure on the new firmware). I ended using this stock M919UVUFNH7, Non SE Enforcing (Permissive) Kernel, and NON-HLOS modem found here:
https://forum.xda-developers.com/ga...stock-base-4-4-4-nh7-rooted-deodexed-t2873695
If any of you developers make a modded version of this stock firmware QA1 (like NH7 above), let me know.
I just heard on the radio that Samsung (as well as other manufacturers) are desperately trying to improve the security of their devices, as they are paranoid of the govt getting in (like the story about their smart TVs), so I wouldn't be surprised of them (at least trying to) take rooting capability away soon.
SuperSU
xXxCyanide87xXx said:
Well I got tired of the king root app really didnt want to do the bloat removal so I switched to kingo root which so far seems to be doing OK. Still no luck on SuperSu. I tried just normal SuperSu & SuperSu Pro.. also tried 2 different apk fIles for SuperSu Me one just kept saying License Verified (no app just black screen flash then that) the other one loaded the actual app and when I clicked the blue bubble thing it said please wait whIle environment is loaded & load bar went maybe 1/20 of the way then just sets there going no further. Going to mess with it some more here later on. Have a little St. Patrick's day baby girl to prepair a 1st birthday party for. I'll keep you posted when I find out more.
Click to expand...
Click to collapse
I'm a NooB but the only thing I can think of is that CF may have not updated SuperSU for this kernel version. Can you post your details ("Settings" > "More" > "About Device")? I still haven't updated, NH7 works OK.
Rooting without SuperSU is scary. I make sure to turn off "Auto MMS download" as I once thought I got an MMS virus with rooted firmware and just about had to change my shorts.
Here is a screenshot of my phones info... kernel build ect. Let me know if you need anything else. Or just need help in general with your phone.
filter4ever said:
Thanks for the update!
So you flashed OTA at first, then re-rooted using KingoRoot? I used CF Auto Root, and CF RegionLockAway before upgrading to NH7, but I haven't tried this yet.
Here's the firmware for all who want to flash the old fashioned way using ODIN (not OTA or Kies).
Rapidgator Mirror: http://rapidgator.net/file/cc090b9fd3b077b9041ff1b6df3bf889
AltaFile Mirror: https://alfafile.net/file/vbGh
If these links don't work (I had a hell of a time), PM me or post below, I can send you a direct link.
Did you originally try to flash using Mobile Odin, regular Odin, or the OTA stock update? I don't know if mobile ODIN works yet - I'm not really into nightly builds yet. The only reason I bought mobile ODIN was because if it already HAS root, it can "castrate" the code like this:
I found in SBL3. My "new" mobo that came with M919UVUFMK2 (WITH knox ). Jellybean 4.3, I asked for a 4.2.2, but they didn't have any in stock. I disabled KNOX, but I think this is still in here.
Thank you for letting me know, I finally rooted the MK2 using CF Auto Root, T-Mo gave me the unlock code (since my previous mobo was already unlocked and IMEI changed), but I used CF Region Lock Away before upgrading. (Works GREAT, but not sure on the new firmware). I ended using this stock M919UVUFNH7, Non SE Enforcing (Permissive) Kernel, and NON-HLOS modem found here:
https://forum.xda-developers.com/ga...stock-base-4-4-4-nh7-rooted-deodexed-t2873695
If any of you developers make a modded version of this stock firmware QA1 (like NH7 above), let me know.
I just heard on the radio that Samsung (as well as other manufacturers) are desperately trying to improve the security of their devices, as they are paranoid of the govt getting in (like the story about their smart TVs), so I wouldn't be surprised of them (at least trying to) take rooting capability away soon.
Click to expand...
Click to collapse
Yes I flashed it first.
This is the order I did it all
1 - downloaded firmware ( rom https://samsung-firmware.org )
2 - Flashed update using Odin PC version (search forums there are links everywhere.
3- downloaded Kingo root from https://www.kingoapp.com and ran root process (may take a couple times... if it fails immediately run it again
4 - after root was successful I then downloaded Mobile Odin (lite or pro your choice. I used Mobile Odin Pro. Check forums for links to download.
5- Download Twrp 3.1.0-0 follow
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976 follow steps to retrieve .tar file. MAKE SURE IT IS CORRECT FILE FOR INSTALLATION.
Don't flash yet
6- down load SuperSu 2.79 SR3 .zip from
h1ttps://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Now we flash.
7 run Mobile Odin and click recovery. Place Twrp there. Then scroll down to after flash and click. Set it for reboot recovery. Run.
8- After TWRP loads click on Flash .Find SuperSu 2.79 select and flash. Reboot to System (I went ahead and wiped just the regular cache partition then rebooted)
9- Run SuperSu (if prompted by Kingo for root then allow.
10- Using something abe to freeze/Remorvebe (Root Essentials, Lucky Patcher, something of that sort) then proceed to freeze and remove all the kingo junk and bloat.
11- Reboot phone and enjoy.
Now I will warn you the Samsung-firmware is slow for download. So if need be and I am allowed to. I have the firmware file I can upload on here for everyone.
I take no responsibility for any damage that can &/or may happen to your device this method worked for me. Doesn't guarantee that this method will work for you. GL and happy rooting ^__^
qFuse Code
Droidriven said:
I'll check out that qfuse code just for curiosity.
The main reason they work so hard to prevent even advanced users from altering the devices is because they got tired of losing money replacing devices under warranty that had been bricked, technically the warranty is voided when a device is modified but when fully bricked they can't tell that their was any attempt to modify it.
I agree, when you buy something it is yours to do with as you wish but most devices on plan aren't owned, technically they are considered mortgaged property, these devices that are advertised as free with a plan aren't free, it's being paid for in your monthly bill. This means it's just like financing a car, you have to have full collision insurance coverage to protect their investment. That is, in effect, the thing that gives Samsung or your carrier the right to do what they've done to protect their investment.
It would be a logistical nightmare if they had it so that people that actually own the devices didn't have to worry about qfuse but at the same time have it so that customers still paying for the device do have to worry about qfuse, so they just have them all like that across the board.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I agree, and I don't have a problem with the qFuse "Warranty Bit" for that reason... when it says "This Will Void Your Warranty" it means exactly that. Like I said, when I buy something it's mine (including, Samsung doesn't have to support it if I screw it up).
Are there any custom variations with permissive kernel of this firmware yet? Tried looking around here and searching, none yet... this post of mine appears to be my latest. If you would like this firmware I'll provide the link.
Now that I have SuperSU Pro and Mobile ODIN pro, do I still have to worry about that bootloader qFuse code (my guess is they flashed the locked bootloader and it's already been executed) I just don't want this new update to screw me, and didn't worry about it for a year, but now my phone is acting funky.... showing ads when I open the "Lock Screen" etc. I got Super SU Pro specifically because... an Android virus... with ROOT privileges = anyone's WORST nightmare. Just look at the /dev folder, not to mention "ps -l -C", or "pidstat -l -C" (and other commands I'm not familiar with yet). Listen to you, take pictures of you, steal your data, your passwords, do something illegal and blame it on you (Use your phone as a PSTN and Internet proxy).... you name it. (also it being mine applies to they don't have to support security updates as well - caveat to all rooters that's the 'Catch 22').
LOL, thats more than my Brain Can Handle
I have the same phone.. samsung s4 with the m919uvsfqa1 . It was from Tmobile, i bought the phone in canada and have it locked to Fido in Ontario , Canada. The fact the phone is Canadian, is likely irrelevant. As the Revision is the same as the phone ASHLEY has rooted.
I want to Multitask Apps, and the Samsung Apps that are Preinstalled do not offer the ones i want.
So I read, that if i Root the Phone then any app can be Multi-Window.
As I see Ashleys , rooting was quite difficult. I ask is it Possible to Root this Phone. For someone that really dont know what they are doing. I would need, a very detailed plan that i could follow but am not able to Follow Ashleys plan. Is there a New Method since your THREAD was POSTED?
I doubt any Local Tech would ROOT THIS for a Price, in Sault Ste Marie Ontario... as the stores wont void warranty and i dont know any Techs.
I need to get something done, so that i can access the Calendar app to add Information while talking on the Phone. So far i have to hang up the phone to enter information to the Calendar. That doesn't seem like a Smartphone....
Can I still root the latest build number NRD90M.N920TUVU4EQG3 for the T-Mobile Note 5?
My overall goal in rooting is to revert back to MM. Honestly I hate Nougat and the battery life has dropped significantly so I'd like to flash a MM ROM. I'm sorry if this is in the wrong section or has been asked before. Just looking for some help. The research I did only showed how to root Nougat but didn't specify the particular build number. I forgot to ask also if Odin is the ONLY method I have to root? I've run into issues before with Odin. Just curious if there's another method for rooting.
tech15 said:
Can I still root the latest build number NRD90M.N920TUVU4EQG3 for the T-Mobile Note 5?
My overall goal in rooting is to revert back to MM. Honestly I hate Nougat and the battery life has dropped significantly so I'd like to flash a MM ROM. I'm sorry if this is in the wrong section or has been asked before. Just looking for some help. The research I did only showed how to root Nougat but didn't specify the particular build number. I forgot to ask also if Odin is the ONLY method I have to root? I've run into issues before with Odin. Just curious if there's another method for rooting.
Click to expand...
Click to collapse
You don't have to root to revert. What I did was put the phone into download mode and flashed the MM Rom from QC2, I believe, or whatever the version was from samfirm which is deprecated now. Just remember to have the OEM unlock enabled and USB debugging enabled in developer. You should be able to then use Odin to revert. If it doesn't work then you can try and root the phone using the root QE1 method from the posts in the T-Mobile note 5 thread and follow the guide. I can't say for certain if you can downgrade straight from an unrooted 7.0 rom to an earlier 6.0.1 MM rom in Odin. But what I do know is this. I came from the Khongloi v11 rom and decide to do something stupid.
"After unwittingly turning off OEM unlock and USB debugging and rebooting phone. I lost all my data. Stupid me. I got so used to quick rebooting and all of sudden decided to do a hard reboot, *sigh. Oh well, you live you learn. Just remember if you do root. Leave those options on. Never, ever, ever, ever disable OEM unlock. EVER."
Anyways, try downgrading in Odin 3.10.7 or if you have trouble with any newer Odin versions. If you have trouble with the newer versions, use an older version. If you can't downgrade directly from that rom, might have to try another way.
Thanks for the reply and advice! But just making sure though for general root purposes: I'm able to root the latest build number?
Try and see. I'm actually on the same firmware and haven't tried yet. I'm still considering if I should root again. I miss using game guardian, especially for LDoE: Survival.
I'd do it but I'm nervous I'm gonna mess up my phone. I was hoping someone will chime in and let me know it's good to go lol
No worries. You can't, because Odin will give you an error message if the firmware doesn't allow it. Kinda how it was in previous revisions. I've tried on purpose to brick my device. The only real way to brick a device is to do something super, super stupid. Try, the only thing that can result is you get an error in Odin and it fails.
The reason I say this is because I tried to use Odin to flash Nougat onto my Verizon S7 and I honestly don't know what the hell I did but it continually bootlooped to the point where I couldn't get it in recovery or anything. It was messed up. Had to send it in for another S7 which I sold and got a Note 5 lol. Needless to say I'm a bit nervous to use Odin.
tech15 said:
The reason I say this is because I tried to use Odin to flash Nougat onto my Verizon S7 and I honestly don't know what the hell I did but it continually bootlooped to the point where I couldn't get it in recovery or anything. It was messed up. Had to send it in for another S7 which I sold and got a Note 5 lol. Needless to say I'm a bit nervous to use Odin.
Click to expand...
Click to collapse
Honestly, bootloops can be fixed. Either thru the recovery or by download mode. It must have been something else you flashed. But if you decide to try and root and Odin doesn't take, then you haven't done anything to jeopardize your phone.