Related
I'm sure this is covered here more than once but my searches are going nowhere.
I've got a RAZR MAXX HD with 4.4.2 182.46.15 (yes, one eight two, not three). A) how do I root it? B) Is there a pathway to 5.n.n? I need root (for TI and killing bloatware), I'd like Lollipop.
AFAIK, I'm SOL on unlocking the bootloader. How, then, can I move to CM? If at all?
I bought the phone, privately, as it is (no backups or older whatever). I do have the original USB cable (still in an unopened bag!).
So... how screwed am I?
BUMP. I get that this is probably a "we have answered this question too many times!" question, but the record is still fuzzy, at least for me, about whether or not all 4.4.2 installs are cursed or not. And whether my install is cursed, too.
91 looks and nobody has an answer???
Ok, first of all, you cannot get 5.0 on this device unless you are on 182.46.10 which the bootloader is unlockable but since you are on the latest firmware there is no way unlock the bootloader which means no cwm, which also means no custom rom, which also means no 5.0! You can use a tool called KingRoot but it doesnt support super SU. another method is hydrogen peroxide which you can google it.
I'm pretty well bleached out as it is, so worrying about roots with hydrogen peroxide doesn't take me very far. But, hey, nice bit of humor.
If SuperSU doesn't work with this scheme, where does that leave me with TI, Build Prop Editor, FX, etc.?
It looks as though rooting the MAXX HD is like pushing on a rope - not real productive.
What phone, comparable in size and specs, /is/ rootable, etc. Without resorting hydrogen peroxide?
You can root it cleanly with hydrogen peroxide, but before starting that process you must reflash to the 183.46.15 firmware. There's a couple of lines in the flashing file that must be commented out; it's all detailed carefully in the hydrogen peroxide thread. I did it, it worked properly the first time and each time after that (I was playing with some experimental stuff that put me in a bootloop a few times and had to reflash to recover.)
Then you can install Titanium Backup and whatever else; I like Nova Launcher and Xposed Framework with GravityBox.
I don't understand why everyone's so afraid of the hydrogen peroxide method. If you read carefully and follow the steps correctly it works. If you try to flash or root or unlock *any* phone using *any* method without reading carefully and following the steps correctly, it's probably going to fail and cause big problems; that's how stuff like this works.
Whoa! You weren't just messing with me about hydrogen peroxide! I tried googling on it and got lots of info about H²O² but zip about anything that could be flashed, etc. From what you're saying I should be searching inside XDA.
Point me at what I need to know to get back to 183.46.15. BTW, I thought it was .10 not . 15 that was easier to work with. Yes? No?
OK, I'll be quiet for a while. I think this is the thread you were pointing me at. It seems to answer all of my questions. I'll be back once I brick or root. [/hopeful grin]
http://forum.xda-developers.com/droid-razr-hd/general/root-droid-razr-hd-xt926-183-46-15-t3062040
OK, I lied. What is an FXZ? Looking at what I've seen so far, I guess I don't really care, but I am curious... Now I'll be quiet. For a while. Maybe. Sorta. I guess.
I rooted my XT926 using Hydrogen Peroxyde. Look at this link: http://forum.xda-developers.com/droid-razr-hd/general/index-motorola-droid-razr-hd-2015-t3167557
Yes, that is the post I used for instructions.
Start near the bottom, just after the screenshot, at the section "Flashing Firmware if Root fails" to get your device up to 183.x before you try and run the hydrogen peroxide stuff. There's a dead link there at "Using RSD Lite", it has moved to http://motofirmware.center/topic/22-how-to-restore-your-device-with-motorola-firmware-plus-unbrick/ instead, you'll need it.
You'll probably have to work through the section "Editing xml" as well, if RSD Lite returns an error during the flashing process. There's a script file with the firmware that has a couple of lines of instruction that causes problems for RSD Lite, you have to remove those lines and then it should work.
Once you're up and running on 183.46.15, then you can go to the top of the post and work through the rooting process.
If there's anything you don't understand, ask and I'll try and explain.
P.S. You shouldn't need any FXZ files for this process.
P.P.S. The x.10 firmware is preferred, because it has an exploit that will allow you to unlock the bootloader. But, since you're already at x.15, you're in a catch-22: The locked bootloader won't let you downgrade to older firmware for "security reasons", and you can't unlock the bootloader without using the older firmware. Nobody's found a method yet to bootstrap this process.
You da man!!! Thanks!
BTW, how do I bump up your thanks counter from here???
ROOT for Droid Razr HD XT926- 183.46.15 w/Kernel date after June 3, 2014 by sd_shadow
Went there, did that, like the t-shirt! [/GRIN]
I recently updated to marshmallow, and am currently trying everything to root it. I have done everything from trying to unlock bootloader in fastboot, to using apps such as kingroot and framaroot.... to no avail... can anyone help? It would be much appreciated!! Thanks!!!
I know you can't really do anything using MM, but can anyone help me flash stock firmware on my device? (I AM USING LINUX!!) I tried running the windows programs with wine.... Did not work...
Dropped my previous 6045O, Cricket variant on its screen on a bunch of gravel and cracked the screen. Since I am a klutz, I had taken out the insurance/phone replacement with Asurion. Received my replacement, and discovered it was loaded with MM, only, as others have noted, the fastboot commands are not there....
I've tried all the methods folks have offered, and, apparently Cricket is in collusion with Alcatel not to make it merely difficult to root and administer (worked entirely too many tech-support gigs... the uninformed tend to screw things up even with documentation), but to make it, seemingly at present, impossible. I'm stuck, and none of the previous methods have worked. (and, yes, I've read every applicable thread I see... at this point, nothing seems to work to root the beast. Since the ability's there by default to shove the apps that will allow themselves to be shoved to my 32GB SD.... that gets rid of my need for Link2SD, until the gentleman, Bulent Akpinar, gets around to recognizing that Marshmallow's been out a while. (paid for the Plus, and completely unusable, even as a widget, with the new Cricket variant of 6.0.1
I've tried the ROOT .rar, our other gentleman's Suite, and the various methods, and at this point, I'm just kinda lost.
pauljulian said:
Dropped my previous 6045O, Cricket variant on its screen on a bunch of gravel and cracked the screen. Since I am a klutz, I had taken out the insurance/phone replacement with Asurion. Received my replacement, and discovered it was loaded with MM, only, as others have noted, the fastboot commands are not there....
I've tried all the methods folks have offered, and, apparently Cricket is in collusion with Alcatel not to make it merely difficult to root and administer (worked entirely too many tech-support gigs... the uninformed tend to screw things up even with documentation), but to make it, seemingly at present, impossible. I'm stuck, and none of the previous methods have worked. (and, yes, I've read every applicable thread I see... at this point, nothing seems to work to root the beast. Since the ability's there by default to shove the apps that will allow themselves to be shoved to my 32GB SD.... that gets rid of my need for Link2SD, until the gentleman, Bulent Akpinar, gets around to recognizing that Marshmallow's been out a while. (paid for the Plus, and completely unusable, even as a widget, with the new Cricket variant of 6.0.1
I've tried the ROOT .rar, our other gentleman's Suite, and the various methods, and at this point, I'm just kinda lost.
Click to expand...
Click to collapse
Nobody searches the forums anymore ,it has been discussed in depth in many threads, you need to downgrade using eluga switch firmware to get back unlocked bootloader n fastboot, then install TWRP and then you can pick whatever rom you like... If you want stock MM with TWRP use the marionettes v1 MM rom, you loose LTE after using Eluga so you need to fix that also I have posted this link several times read all the threads attached and you will get there
http://forum.xda-developers.com/ido...de-mm-to-install-custom-t3475961/post69028659
kal250 said:
Nobody searches the forums anymore ,it has been discussed in depth in many threads, you need to downgrade using eluga switch firmware to get back unlocked bootloader n fastboot, then install TWRP and then you can pick whatever rom you like... If you want stock MM with TWRP use the marionettes v1 MM rom, you loose LTE after using Eluga so you need to fix that also I have posted this link several times read all the threads attached and you will get there
http://forum.xda-developers.com/ido...de-mm-to-install-custom-t3475961/post69028659
Click to expand...
Click to collapse
Actually I did search before posting my comment, and I have the Eluga executable... after expanding it and trying to do the deed, it doesn't see the phone... I've got the OEM unlocking enabled in the Dev. options on my device...
I admit, though, I may not be doing something correctly, and will try it again.
--- edit ---
Silly me... didn't remember I had to have the phone off... for that matter, since it was a while ago that I rooted the previous one, and that it was running Lollipop 5.0.2, I didn't have to jump through as many hoops as with 6.0.1... Alcatel and Cricket don't make it impossible to do with this phone, as Cricket seems to specify with the ZTE device, and the LG Stylo... Just difficult, but not impossible. Working on it as we speak, and will respond in a bit.
BTW... was a little snarky that no one reads the columns... I obviously missed a few things, but I have read... just sayin'...
pauljulian said:
Actually I did search before posting my comment, and I have the Eluga executable... after expanding it and trying to do the deed, it doesn't see the phone... I've got the OEM unlocking enabled in the Dev. options on my device...
I admit, though, I may not be doing something correctly, and will try it again.
Click to expand...
Click to collapse
Is the phone off? You must have phone off so it can go into download mode.
kal250 said:
Is the phone off? You must have phone off so it can go into download mode.
Click to expand...
Click to collapse
Been referring to Alek Dev's (and others') instructions, have booted into the Panasonic rom, in the process of erasing, and will flash the rest going forward.
Thanks for the links, and I admit a "Doh!" about how to go into download mode... a few devices I'm kinda maintaining around here, and each seems to have a different button process to get there.
Thanks again, and I think I've got it from this point (with multiple tabs up in my browser for reference, of course...)
pauljulian said:
BTW... was a little snarky that no one reads the columns... I obviously missed a few things, but I have read... just sayin'...
Click to expand...
Click to collapse
Sorry, if I seemed rude, been dealing with a few foster children, who want to push every button I have, lol teens.... was just in vent mode I guess....
No need to downgrade to LP, use Alcatel Flasher to flash twrp
Look at this: http://forum.xda-developers.com/idol-3/development/tool-sahara-firehose-test-alcatel-t3454855
install twrp and roo with supersu.zip. That all.
murigny64 said:
No need to downgrade to LP, use Alcatel Flasher to flash twrp
Look at this: http://forum.xda-developers.com/idol-3/development/tool-sahara-firehose-test-alcatel-t3454855
install twrp and roo with supersu.zip. That all.
Click to expand...
Click to collapse
Isn't that still in beta status as test only? The dev has discontinued development?? I have never tried it as I believed it was just still conceptual... I will look into it further..... Was flashing ever implemented??
kal250 said:
Isn't that still in beta status as test only? The dev has discontinued development?? I have never tried it as I believed it was just still conceptual... I will look into it further..... Was flashing ever implemented??
Click to expand...
Click to collapse
No, it's not a test, it work. You can read/write boot and recovery on 6039, 6045 and 6055 for all variants
Look at new howto made by decker.su: http://forum.xda-developers.com/idol-4s/help/howto-idol-4-6055-installing-twrp-t3486077
You Just have to choose "6045" in the app and twrp recovery for 6045
I used the Panasonic eluga software lol.... That program didn't work for me at all...
Mod Edit
So this is BS right? I've been out of the phone rooting game for a bit.
Sent from my SM-N920V using Tapatalk
Mod Edit
MrMike2182 said:
Why are you trying to get people to do this when it's not FULL ROOT?! You basically took the same exact console root eng kernel that is listed here https://forum.xda-developers.com/verizon-galaxy-note5/general/root-n920v-t3538192 and just renamed it..
Do not do this it's simply console root and nothing else!!
Click to expand...
Click to collapse
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
tylerlawhon said:
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
Click to expand...
Click to collapse
LOL there isn't even a CF auto root for the N920V!! He seriously just took the same one we already have for console root and renamed it! They're even the same exact size, haha. Besides, where does he think the SuperSU app is coming from? It sure ain't from the file he has posted because that's just the console root kernel and that doesn't install/ flash SuperSU it only flashes the boot.img..
tylerlawhon said:
..
Click to expand...
Click to collapse
There's to many inexperienced people claiming root and cluttering the hell out the forums!! Even on the easy-firmware website he posted this same exact thing and when a user asked him a question he didn't even know the answer and told the user to flash and report back with his findings.. This thread is totally not needed at all!!
Stuck in the boot interface
tylerlawhon said:
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
Click to expand...
Click to collapse
Well there goes 1 who didn't read first lol.
please remove this threade Please .
it's worng from inexperienced someone
I know this website, easy firm ware listed above, to be a scam site. I've seen a lot of different angles they've tried INCLUDING a download manager quote unquote that is supposed to help you finish downloading. But this is a trojan app. While I never fired it up I can tell you it doesn't look like something a windows user should execute on their system. I use linux.
(mods I promise I know this site is a scam site I've watched them work over the past couple months as I researched my studies)
Regards to root. If you are patched for dirtycow good luck getting root on this phone. (see below for dirtycow patch details) The AT&T / Verizon variants of the Note 5 are extremely well coded you can't get root on them without a powerful exploit. With dirtycow available the days are numbered for any phones not patched, of course not patching your phone in the meantime means you are very vulnerable to a nasty exploit.
So how long right? I dunno but it could be awhile.
Patch details:
Google says the fix is called CVE-2016-5195 patched 11-05-2016, however my security patch level is Nov 1st, 2016. The Samsung SVE-2016-7504 is stated to be included in November's patches and there are 14 patches in that set. AT&T N920AUCS4CPK1 has a note about 14 patches from Samsung, the exact number. (so I seem to be patched if I follow the logic even though Google responded on 11/05/2016 but I dunno how to confirm what's in this Nov 1 2016 security patch in the PK1 firmware.)
It doesn't really matter if they've patched it, you can still downgrade your firmware and security level - even on this variant. I used to go between Marshmallow and Lollipop, as it was required by the ps3 controller app.
Turbine1991 said:
It doesn't really matter if they've patched it, you can still downgrade your firmware and security level - even on this variant. I used to go between Marshmallow and Lollipop, as it was required by the ps3 controller app.
Click to expand...
Click to collapse
Which part are you saying you can downgrade? You can't take the Lollipop firmware and flash it if you're currently on the latest firmware update. It will just fall in odin.
That's just not true. The Verizon model can be flashed in Odin, I've done it a few times myself. Here's someone elses word: https://forum.xda-developers.com/verizon-galaxy-note5/general/downgrade-to-lollipop-5-1-1-verizon-t3368250
It's not impossible, you just need to use an official firmware and may need to downgrade the bootloader.
Turbine1991 said:
That's just not true. The Verizon model can be flashed in Odin, I've done it a few times myself. Here's someone elses word: https://forum.xda-developers.com/verizon-galaxy-note5/general/downgrade-to-lollipop-5-1-1-verizon-t3368250
It's not impossible, you just need to use an official firmware and may need to downgrade the bootloader.
Click to expand...
Click to collapse
Uh, Sir, the link you just posted.. *I* am the original poster of that and I'm telling you with official firmware you still CANNOT go from the latest firmware update of Marshmallow back to Lollipop! I even stated in my OP that it's not going to once you accept the BPI3 firmware update you're done and stuck on Marshmallow with no way to go back not even if you follow my original instructions it won't work!! The bootloader is no longer downgradeable thanks to Verizon!
Dirty cow or not is irrelevant. We can upgrade or downgrade and we're able to root this phone just like any other variant.
The only issue is the bootloader's signature checking.
so this is crap, thanks for the further investigation
There's a simply check for a value that they are calling a binary number. What is that? Certain versions will work together but past a certain point something changes. (most often the security storage binaries) .. So the bootloader checks to see if binary # >= current firmware binaries ... If you are on S3 binary and you attempt to flash S2 binaries the bootloader newly rejects this.
I can and have written a tool to over come this problem but there is one catch. system.img is too large for me to hack into place in this way. If I can't rewrite system.img then we are still stuck. ;*(
So what am I doing? I need root so I can just dd write system.img from /sdcard/ to the partition. that's it..
Stop listening to people who are not spending all their free time looking at the Note 5.. I already have too much access for the Note 5 to survive now.. It's going down, it is not the super secure device that will refuse to boot 'ever again' if you modify stuff that Samsung tried to claim.. that was lies and nonsense (don't hack BOTA0 or BOTA1 though)... I haven't tested changes to this partitions, all others have suffered a beating from me. (if you disable certain packages without disabling other packages it will refuse to boot, no wiping will help, reflash time)
droidvoider said:
There's a simply check for a value that they are calling a binary number. What is that? Certain versions will work together but past a certain point something changes. (most often the security storage binaries) .. So the bootloader checks to see if binary # >= current firmware binaries ... If you are on S3 binary and you attempt to flash S2 binaries the bootloader newly rejects this.
I can and have written a tool to over come this problem but there is one catch. system.img is too large for me to hack into place in this way. If I can't rewrite system.img then we are still stuck. ;*(
So what am I doing? I need root so I can just dd write system.img from /sdcard/ to the partition. that's it..
Stop listening to people who are not spending all their free time looking at the Note 5.. I already have too much access for the Note 5 to survive now.. It's going down, it is not the super secure device that will refuse to boot 'ever again' if you modify stuff that Samsung tried to claim.. that was lies and nonsense (don't hack BOTA0 or BOTA1 though)... I haven't tested changes to this partitions, all others have suffered a beating from me. (if you disable certain packages without disabling other packages it will refuse to boot, no wiping will help, reflash time)
Click to expand...
Click to collapse
I tried to tell everyone that this was straight up BS back when I was asking for help and no one wanted to risk it nor did they believe me.. Instead they chose to believe this instead of me..
http://www.idigitaltimes.com/samsung-galaxy-note-5-galaxy-s6-edge-specs-and-features-att-and-verizon-models-wont-468357
Would flashing the tar file in the OP give me the ability with ADB to delete, rename or change the bootsamsung.qmg and bootsamsungloop.qmg files? All I want to do is swap those out for another set. Would I then need to flash something else to bring it back to normal?
MrMike2182 said:
I tried to tell everyone that this was straight up BS back when I was asking for help and no one wanted to risk it nor did they believe me.. Instead they chose to believe this instead of me..
http://www.idigitaltimes.com/samsung-galaxy-note-5-galaxy-s6-edge-specs-and-features-att-and-verizon-models-wont-468357
Click to expand...
Click to collapse
You seem to have a good grasp on the situation and seem to talk sense, so I'll just ask a question. I'm only passing through because I needed some info, but got interested in the thread.
It seems you have the eng boot for the device, but not able to get system to mount rw? Strange because I have checked it and it is a bonafide eng boot.
Anyway I don't own this device, but I thought I'd just share some info that allowed others to get root on a few recent ATT devices with locked bootloaders on MM.
Using Kingroot on the said devices would not work, no matter how many times or which version was used. However flashing the eng boot from the combination firmware (so not even full eng boot as no root shell with adb) and then using Kingroot, Kingroot was able to successfully root these devices even though with some it took several tries. Kingroot was then used to convert to Supersu.
This may have been tried already, but I couldn't see it. Someone tried it with stock, but not using the eng binary.
The combination eng binary allows the device to boot in permissive mode with no dm-verity, but doesn't have a root shell or any write access with adb. The full eng boot you have should do the same obviously with the addition of adb root shell.
It's just for info and I'm not claiming it will work on Verizon devices, but it seems to be pretty successful on ATT and Tracfone devices.
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....
First of all I need to preface this by saying I know nothing about rooting.
I have a Nokia 3, Model TA-1020, Android version 8.0.0 (which apparently is Oreo, even though I got this phone as a Nougat) and Android Security patch level May 5, 2018.
From all the research I attempted to do regarding rooting a Nokia 3, most times it would be for a specific model (which apparently is important) but never TA-1020 (the one I have).
So it makes me wonder if I can root my phone. I don't want to do anything serious, just to basically give root access to a couple of apps (from what I understand).
Any guidance would be helpful if it is possible.
MainGoldDragon said:
First of all I need to preface this by saying I know nothing about rooting.
I have a Nokia 3, Model TA-1020, Android version 8.0.0 (which apparently is Oreo, even though I got this phone as a Nougat) and Android Security patch level May 5, 2018.
From all the research I attempted to do regarding rooting a Nokia 3, most times it would be for a specific model (which apparently is important) but never TA-1020 (the one I have).
So it makes me wonder if I can root my phone. I don't want to do anything serious, just to basically give root access to a couple of apps (from what I understand).
Any guidance would be helpful if it is possible.
Click to expand...
Click to collapse
There is already a thread and tutorial on XDA for rooting the nokia 3 (TA1020 and TA1032) on Nougat 7.1.1 and Oreo 8.0.0
Here is the link.
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
The important stuff......
You have received an android 8.0 update - so your device is an Oreo device.
It does not matter what was on the device when you purchased it - for future reference, just quote your current android version - Never quote previous versions or what was on the device when you brought it, as I can guarantee someone will see NOUGAT in your post and assume you have a Nougat device.
(Things like that cause all sorts of confusion and issues here that if you was to follow the incorrect instructions you would brick your device and render it unusable)
I'm also using a Nokia 3 TA1020 on Oreo (8.0.0)
After reading the rooting thread I've decided not to proceed with rooting my own Nokia 3.
As the procedure isn't very clear and it seems many users have had issues afterwards.
If you know NOTHING about rooting I suggest you also stay well clear of trying to root your nokia 3 - it's a very complicated process that even I'm not confident enough to try - and believe me Ive rooted many devices in the past!
With the Nokia, it's not a case of flashing a file in a custom recovery to gain root - there are several things you must do using a PC and complicated button combinations and perfect timing.
You get any of this wrong or miss a step you have a rather useless paperweight rather than a Nokia phone and trying to root will invalidate and void any remaining warranty your device may have left.
Ask yourself why you need root?
If you root your device, you have to keep the system recovery as if you flash a custom recovery you won't receive any system updates.
Also if you do keep your system recovery and receive a system updates you have to go through the process of rooting all over again and system updates can then fail, as confirmed by users in the other thread......
Newer android versions (8.1 and 9.0) will also block some of things users get round using substratum and xposed.
These apps will be almost useless in android 9.0 because Google is taking away the ability for rooted devices to change system UIs and draw over any apps.
Most xposed modules will be obsolete.
Obviously what you do is your own choice, I'm just saying it's not for me and I really don't want to try.
There isn't not any real benefit from having a rooted device these days, especially on this device which looks so difficult to get rooted.
Obviously you don't have to take my word for it, just look at all the posts in the thread I've linked to you above of users who tried the rooting process and missed a step or didn't follow correct instructions or even in one case followed instructions for the wrong android version and wrong device and have now bricked their device and rendered it unusable.
In my opinion it's just not worth it as the risks involved outweigh any real benefit gained.
Regards
@bubba1601 one slight modification to your post, rooting won't stop you from receiving system updates - as long as you still have your stock recovery. That said I agree with you on everything else especially the fact that it's a lot of hassle. Even after you have rooted your phone, once you install an update you have to go through the whole process of rooting over again. Half the time, my system update fails. If you're not familiar with the process it can really be daunting
redweaver said:
@bubba1601 one slight modification to your post, rooting won't stop you from receiving system updates - as long as you still have your stock recovery. That said I agree with you on everything else especially the fact that it's a lot of hassle. Even after you have rooted your phone, once you install an update you have to go through the whole process of rooting over again. Half the time, my system update fails. If you're not familiar with the process it can really be daunting
Click to expand...
Click to collapse
Thank you for correcting me @redweaver.
I've edited my comments accordingly!
After reading the linked post It really doesn't give me any confidence to try it and I personally see no benefit from doing it.
redweaver said:
@bubba1601If you're not familiar with the process it can really be daunting
Click to expand...
Click to collapse
bubba1601 said:
In my opinion it's just not worth it as the risks involved outweigh any real benefit gained.
Click to expand...
Click to collapse
Thanks you both for all the advice you've given me and I want to ask 1 more thing:
If I mess up something during the rooting process, is my phone forever a brick or can I fix it with a factory reset of some kind ?
Because even if I can't fix it, I am still willing to give it a try since:
I got this phone for free. (literally $0, not that someone gifted it to me).
This is my secondary phone (I have a Windows Phone as my main).
I have sent this phone for repairs at least 4 times and it took 3 weeks to get it back each time and the problems return every time.
I have factory reset it 5 times so one more isn't going to be a problem.
It still has problems.
I am not really a phone person and only use it when I am outside of my house (something that doesn't happen often) and only for games.
So my biggest concern is if it is possible to reset my phone after not following an instruction properly. But even that isn't really going to stop as long as it is possible to root my phone since I had the impression that only certain models could get rooted so far.
MainGoldDragon said:
Thanks you both for all the advice you've given me and I want to ask 1 more thing:
If I mess up something during the rooting process, is my phone forever a brick or can I fix it with a factory reset of some kind ?
Because even if I can't fix it, I am still willing to give it a try since:
I got this phone for free. (literally $0, not that someone gifted it to me).
This is my secondary phone (I have a Windows Phone as my main).
I have sent this phone for repairs at least 4 times and it took 3 weeks to get it back each time and the problems return every time.
I have factory reset it 5 times so one more isn't going to be a problem.
It still has problems.
I am not really a phone person and only use it when I am outside of my house (something that doesn't happen often) and only for games.
So my biggest concern is if it is possible to reset my phone after not following an instruction properly. But even that isn't really going to stop as long as it is possible to root my phone since I had the impression that only certain models could get rooted so far.
Click to expand...
Click to collapse
Yes it's possible to restore the phone if something goes wrong, but not via the traditional factory reset proceedure.
I understand resetting if flashing goes wrong involves using PC software called "SP flash tool" to flash some system files.
This isn't done inside android from the phone, it's done with your Nokia plugged into a PC in fastboot / download mode, again, I'm not sure of this part and that's
the bit I'm not really understanding and why I'm very reluctant to do it.
As I said, the choice is yours, but bear in mind the author of the rooting thread has now moved to another device so will not be supporting the Nokia 3 or the Nokia 3 rooting thread.
Is nokia 3 TA-1020 ROOTABLE