Related
Hello everybody,
As i don't have enough messages to answer on the development thread, i post a few information here.
On my Z bought on a xperia store (lock bootloader but unlockable, french version (I think it is a worldwide one...) ) i runned the exploit, and it do work!
But as some comment said, the NFC stopped to work (only bug so far...).
The error is simple: you can't 'check' the box in configuration.
The logcat is simple and say only a few information:
I/NfcService( 1102): Enabling NFC
E/NFCJNI ( 1102): phLibNfc_Mgt_ConfigureDriver() returned 0x0106[NFCSTATUS_INVALID_DEVICE]
W/NfcService( 1102): Error enabling NFC
I don't know if i can help. But here are the few informations i have =)
Hello, You can fix this problem by removing a directory named /data/usf.
Thanks !
goroh_kun said:
Hello, You can fix this problem by removing a directory named /data/usf.
Thanks !
Click to expand...
Click to collapse
Thanks for creating this root method.
Sent from my C6602 using xda premium
goroh_kun said:
Hello, You can fix this problem by removing a directory named /data/usf.
Thanks !
Click to expand...
Click to collapse
Hey goroh_kun, I messed around with some other scripts and lost root, and can't re-root using your method. Can you give me any pointers on what I can do?
robogo1982 said:
Hey goroh_kun, I messed around with some other scripts and lost root, and can't re-root using your method. Can you give me any pointers on what I can do?
Click to expand...
Click to collapse
Do you still have supersu??if no download it from playsrore.
You can always flash stock firmware and re-root again.
Sent from my C6602 using xda premium
goroh_kun said:
Hello, You can fix this problem by removing a directory named /data/usf.
Thanks !
Click to expand...
Click to collapse
please check p.m.!
gm007 said:
Do you still have supersu??if no download it from playsrore.
You can always flash stock firmware and re-root again.
Click to expand...
Click to collapse
SuperUser is there, just no apps have root access. None.
In process of flashing back to stock and going all over again.
EDIT: restored with SUS and rooted again with this method. All seems good so far.
Thanks for the tip, it works like before now.
And root is correctly working
Sent from my C6603 using xda app-developers app
Worked like a charm, and thanks for the tip to fix NFC! This is very valuable to me, my bootloader isn't unlockable (I'm hoping a carrier unlock will help there, but Vodafone Ireland claim they don't have the NUCs yet).
AW: About goroh_kun & huhka_com exploit on C6603 / 10.1.A.1.350
No, wont help. An unlock blocked bootloader is locked for good. No way around it and I judge from your post, you dont read other threads so you have no idea whats going on: Sony - as other manufacturers did and do - didnt compromise Qcoms security installments in place by poorly engineering the phone. Bootloader security barrier most likely wont ever be broken through.
How exactly do you remove a directory like that?
Use root explorer.. Worked like a charm
I didn't remove it I just renamed it to usf1 it worked! But there are a lot of files in that folder. Is it not important?
Sent from my Nexus 7 using Tapatalk HD
schaggo said:
No, wont help. An unlock blocked bootloader is locked for good. No way around it and I judge from your post, you dont read other threads so you have no idea whats going on: Sony - as other manufacturers did and do - didnt compromise Qcoms security installments in place by poorly engineering the phone. Bootloader security barrier most likely wont ever be broken through.
Click to expand...
Click to collapse
I take it your talking about official bootloader unlocking? Coz obviously a dev might work out how to unlock a bootloader using other ways which would mean a blocked bootloader can be unlocked.
Sent from my C6603 using xda premium
Hi everyone
I'm new at this root things so I would like to make a couple of questions if you don't mind...
I have a SIM Free UK Xperia Z, so I think my bootloader is unlockable. The thing is I don't want to do it (at least for now) because I will loose DRM keys, BE2, and my warranty...
1- Can I root using this method without unlocking the booloader?
2- If I root my phone with this method I mantain my DRM keys, BE2 and can restore it like when it came from factory?
Thanks in advance
1. Yes
2.Yes
nazrin313 said:
1. Yes
2.Yes
Click to expand...
Click to collapse
Thanks
One last question.
If Sony releases an update...Can I update it? I will loose root right?
AW: About goroh_kun & huhka_com exploit on C6603 / 10.1.A.1.350
jayman1986 said:
Coz obviously a dev might work out how to unlock a bootloader using other ways which would mean a blocked bootloader can be unlocked.
Click to expand...
Click to collapse
I covered this in my initial post: recognized elite Android god Entropy512 himself, stated repeadetly, that bootloader security on Qualcomm devices is very strong. If it gets broken (this is what you ask/hope for) then it's usually because the manufacturer ****ed up Qcomms security. Sony, so it seems, does not have done that so an "unofficial" unlock or "bootloader crack" is very unlikely on the current devices, such as the Xperia T and Xperia Z.
---------- Post added at 05:28 PM ---------- Previous post was at 05:25 PM ----------
JPWOA said:
If Sony releases an update...Can I update it? I will loose root right?
Click to expand...
Click to collapse
Most likely, yes. Or better: usually, yes, exemptions exempt. You will be able to update and keep root using the help and procedures which will be published in this forum.
hi all, i having the problem with nfc after root, and unable to find the data/usf.
my data folder is empty......
i533.photobucket.com/albums/ee333/ri1030/Other/rojak/Screenshot_2013-03-19-15-44-50_zps9dc2bef7.png
Sorry ubanle to post link
Make sure your file explorer is configured to access system directories (such as /data) in root mode. You may need to change a setting to enable root access.
/data is definitely not empty, it's filled with plenty of other stuff.
I recently got a GS4 in my hands. The details are mentioned below:
Model: GT-i9505
Android version: 4.2.2
Baseband: I9505DXUAME2
Build number: JDQ39.I9505DXUAME2
kernel: 3.4.0-526204
I pulled the source code for the same from the Samsung website. Compiled and deployed it without making any changes to the stock code (ensuring that the instructions are followed neatly...I have been doing it successfully on other Samsung models). My device boots fine but stops detecting the SIM card. I don't know what may be wrong here.
I am not sure if it has to do something with the code which I picked from the Samsung website. I tried using two different source codes but the result remained the same. I see in the kernel logs that exfat_fs and exfat_core drivers are not being loaded due to version mismatch. But I don't think it could be the reason behind my problem.
Any hints as in how can I debug this issue? What can I check in the kernel logs to get to the root cause of this issue?
epitoro said:
I recently got a GS4 in my hands. The details are mentioned below:
Model: GT-i9505
Android version: 4.2.2
Baseband: I9505DXUAME2
Build number: JDQ39.I9505DXUAME2
kernel: 3.4.0-526204
I pulled the source code for the same from the Samsung website. Compiled and deployed it without making any changes to the stock code (ensuring that the instructions are followed neatly...I have been doing it successfully on other Samsung models). My device boots fine but stops detecting the SIM card. I don't know what may be wrong here.
I am not sure if it has to do something with the code which I picked from the Samsung website. I tried using two different source codes but the result remained the same. I see in the kernel logs that exfat_fs and exfat_core drivers are not being loaded due to version mismatch. But I don't think it could be the reason behind my problem.
Any hints as in how can I debug this issue? What can I check in the kernel logs to get to the root cause of this issue?
Click to expand...
Click to collapse
Flash stock rom via odin.
I want to modify one of the drivers in the stock code and that is why I downloaded and compiled the kernel code. But before making my changes, I tried to do a sanity and ran into this problem. Going back to stock is not going to help me. So, essentially I have to find out the reason as in why it is not working with the stock code. Any clues for debugging this issue?
epitoro said:
I want to modify one of the drivers in the stock code and that is why I downloaded and compiled the kernel code. But before making my changes, I tried to do a sanity and ran into this problem. Going back to stock is not going to help me. So, essentially I have to find out the reason as in why it is not working with the stock code. Any clues for debugging this issue?
Click to expand...
Click to collapse
Oh understood. Unfortunately Im not good with that, but you can open thread here http://forum.xda-developers.com/forumdisplay.php?f=2321 Im sure devs will help you.
thanks!!
But I am not allowed to post in that forum as I am a new joinee and only experienced users may post. If that is the case, how can I reach out to the developers?
epitoro said:
thanks!!
But I am not allowed to post in that forum as I am a new joinee and only experienced users may post. If that is the case, how can I reach out to the developers?
Click to expand...
Click to collapse
Is type imei still there or is it corrupted?
Sent from my GT-I9505 using xda premium
sxi200 said:
Is type imei still there or is it corrupted?
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
good point
No. Settings menu doesn't show imei as well as the baseband version once i flash the compiled kernel. But both return as soon as i flash back the stock kernel. Shall i try to recover imei as it essentially doesn't get lost. I believe the real problem is somewhere else and loosing imei is just a side effect of that.
Sent from my GT-I9300 using xda app-developers app
I have verified that the contents of the efs folder don't change between the two kernels.
I mentioned in my first post that ext_fs drivers are not being loaded by the new kernel. Are these two things somehow correlated: efs and ext_fs. Namewise it seems that ext_fs driver reads efs folder. Its just a guess. Does it makes sense to someone else?
Sent from my GT-I9300 using xda app-developers app
Any comments please.
Sent from my GT-I9300 using xda app-developers app
epitoro said:
Any comments please.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I come from an i9000, where imei issues like these are always solved by flashing the stock rom again. Then you can make a backup of your efs folder and start your iterations again. Might also work this way for the s4.
Verstuurd van mijn GT-P5100 met Tapatalk
I was using a wrong config file for the kernel.
Sent from my GT-I9300 using xda app-developers app
One may use the following cmd to genrate the correct config:
make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig SELINUX_DEFCONFIG=jfselinux_defconfig ARCH=arm
Sent from my GT-I9300 using xda app-developers app
Hi im having this issue recently, im not very gppd when it comes to this sort of thing have u sorted out? & if so how did u resolve the issue?
Sent from my GT-I9505 using Tapatalk
eddie500_1 said:
Hi im having this issue recently, im not very gppd when it comes to this sort of thing have u sorted out? & if so how did u resolve the issue?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
You need to compile the source code available from Samsung Open Source with the attached config file. Steps will be:
1) Goto to the root of your kernel source tree and run this cmd:
make mrproper
2) Extract .config file from zip and place it in the root dir or your kernel source tree
2) Compile using gcc for ARM architecture (ARCH=arm) using the toolchain
This is for anyone who has root on 4.4.4 but also has write protection enabled. (Used SuperSU to keep root through the update).
This app will allow you to enable the native WiFi tether without modifying the system (Which we can't do anyways). I have been using this for about an hour with no issues.
Finally, I didn't make this, I'm just someone who's stuck between places and need WiFi tethering for my job and hate spending money. Use at your own risk of course.
http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
Sent from my XT1080 using Tapatalk
Yeah, I think this is how Topsnake's exploit works.
Its the same thing as the exploit I released in the dev section. Nice repost
Topsnake said:
Its the same thing as the exploit I released in the dev section. Nice repost
Click to expand...
Click to collapse
Link? I looked through both Dev sections and only saw exploits that require you to modify system files and build.prop. Sorry nonetheless if this has been posted before.
Sent from my XT1080 using Tapatalk
miketoasty said:
Link? I looked through both Dev sections and only saw exploits that require you to modify system files and build.prop. Sorry nonetheless if this has been posted before.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Yeah i just made the connection now. Forgot not everyone has unlocked BLs. In theory, if the app can make the change, you can too.
The app literally applies the same exact exploit as the one I've already released.
chrisc2u said:
Doesn't the exploit require write access? Shouldn't this as well? Just want to make sure before I update.Thanks in advance.
Click to expand...
Click to collapse
No it does not, it runs a command after the phone is booted that while requiring root to run does not make any actually changes to the system.
Again, I have a 1 for write protection (meaning its enabled) and SuperSU basically stuck in System and have no issues running the app, making WiFi hot spots, and having devices connected to it.
Make sure you have root survival set up as well, I'm not sure if the update would remove root without it but I don't think you would want to take that chance.
Sent from my XT1080 using Tapatalk
I dont know if anybody found that before but Im able to tether wifi without doing anything [emoji1], of course Im using my phone outside US with a gsm carrier.
miketoasty said:
No it does not, it runs a command after the phone is booted that while requiring root to run does not make any actually changes to the system.
Again, I have a 1 for write protection (meaning its enabled) and SuperSU basically stuck in System and have no issues running the app, making WiFi hot spots, and having devices connected to it.
Make sure you have root survival set up as well, I'm not sure if the update would remove root without it but I don't think you would want to take that chance.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
and just to confirm, you couldn't apply my exloit? Again this app does the same thing.
josuearisty said:
I dont know if anybody found that before but Im able to tether wifi without doing anything [emoji1], of course Im using my phone outside US with a gsm carrier.
Click to expand...
Click to collapse
That's because your on a different carrier
Topsnake said:
and just to confirm, you couldn't apply my exloit? Again this app does the same thing.
Click to expand...
Click to collapse
I attempted this exploit by you TopSnake ( http://bit.ly/1zz1JOE) and after rebooting my build.prop was deleted and all renamed files were restored to their original state. Was there another exploit you were talking about? This was the only one I could find in the dev section for the latest update.
I do know that you can run a simple command to do what this app does but this app can run on boot up which saves some time.
Sent from my XT1080 using Tapatalk
Topsnake said:
The app literally applies the same exact exploit as the one I've already released.
Click to expand...
Click to collapse
The OP stated he was write protected, so he can't copy the build.prop over the stock one. My app doesn't write to the system it runs the /system/bin/setprop command to set the property. The build.prop sets the property on boot but after the phone has booted the build.prop is never read again. So replacing it on write protected devices won't work.
Replied in pm
Thread cleaned
Keep this thread on topic and all other issues to PMs
Thank you for your cooperation
Friendly Neighborhood Senior-Mod
UPDATED:
Please jump to the following thread for information on root/lollipop:
http://forum.xda-developers.com/shield-tablet/help/qa-root-shield-tablet-2-0-lollipop-t2945163
garyd9 said:
There's some misinformation going around concerning lollipop (android 5.0), root, and the SHIELD tablet. I'm posting this (redundant) information to (hopefully) clear things up and prevent someone from causing themselves a headache after the tablet updates...
nvidia has stuck very close to AOSP in their tablet firmware updates, so it's a reasonable assumption (at this point) that the new firmware will also be very close to AOSP.
If that comes to be, then "rooting" the tablet will be more difficult than in previous firmware updates. Most of the gory details can be found in this G+ article by @Chainfire : https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP
(BTW, as always, a huge thanks to Chainfire for his efforts. If you haven't already, paying for the upgrade to "SuperSU Pro" is well worth the price if for no other reason than to encourage Chainfire to continue work on that project.)
If you don't understand the details of that post from chainfire, I'll try to summarize it: Even if you manage to get a copy of the "su" binary on your system partition (which is essentially the goal of all the older root exploits), it won't matter much in Android 5.0. In Android 5.0, we'll ALSO need a part of the kernel image changed (the ramdisk) so that a part of "superSU" can run at a more permissive context.
Updating the kernel ramdisk shouldn't be too difficult (if its compressed with the kernel in a normal way) once we have the image to play with. As well, in order to put the newly modified kernel image in place, a person would have to unlock their bootloader (which can void your warranty.)
Actually, it's possible (once the image is released by nvidia) that @Chainfire will stick the image on his server in one of his very easy to use "CF-Auto-Root" bundles. (Hopefully, all the @ references I've made will get him to look at this thread and confirm what I've said. The honest truth is that I'm NOT familiar with SELinux, so I'd have to do a bit of experimenting to get this working.)
Take care
Gary
Click to expand...
Click to collapse
Have you found any specifics on what will need to be modified in the ramdisk? I haven't really done anything with the boot.img itself but I'd be interested to see what is going on with this.
Keithn said:
Have you found any specifics on what will need to be modified in the ramdisk? I haven't really done anything with the boot.img itself but I'd be interested to see what is going on with this.
Click to expand...
Click to collapse
That Google plus post I linked to describes the needed change.
Sent from my SHIELD Tablet using Tapatalk
Okay, thanks. I guess I didn't catch that.
Sent from my One M8
Root successful!
I just successfully got root. If I can make it permanent I will post the necessary files/instructions in the update thread.
SuperPichu said:
I just successfully got root. If I can make it permanent I will post the necessary files/instructions in the update thread.
Click to expand...
Click to collapse
With a modified recovery or stock ?
matyas69 said:
With a modified recovery or stock ?
Click to expand...
Click to collapse
CWM. The instructions are up in the lollipop update thread
SuperPichu said:
CWM. The instructions are up in the lollipop update thread
Click to expand...
Click to collapse
Is this root sticking?
whoamanwtf said:
Is this root sticking?
Click to expand...
Click to collapse
It seems to be. Only problem I have run into is that FX file explorer root mode doesn't seem to work, but ES does so I think it's an app compatibility with 5.0 thing rather than a problem with root.
SuperPichu said:
CWM. The instructions are up in the lollipop update thread
Click to expand...
Click to collapse
I'll wait root without custom recovery
SuperPichu said:
It seems to be. Only problem I have run into is that FX file explorer root mode doesn't seem to work, but ES does so I think it's an app compatibility with 5.0 thing rather than a problem with root.
Click to expand...
Click to collapse
Are you able to use FolderMount with it? and Titanium? Those are the reason I need root, and if those both work then I will wipe and unlock to get LP rooted
whoamanwtf said:
Are you able to use FolderMount with it? and Titanium? Those are the reason I need root, and if those both work then I will wipe and unlock to get LP rooted
Click to expand...
Click to collapse
Testing right now. How should I test these? i.e. What do you use them for?
SuperPichu said:
Testing right now. How should I test these? i.e. What do you use them for?
Click to expand...
Click to collapse
Awesome, I use FolderMount to link my obb files from the sd card to the main so that my largest game files are all on my sd card. I actually have the premium version so I just link my whole obb folder and data folder but I would guess linking any obb and then seeing if the game would load would test it. As for Titanium a backup/delete/restore of any app would test all of the features. Thanks for checking that out
whoamanwtf said:
Awesome, I use FolderMount to link my obb files from the sd card to the main so that my largest game files are all on my sd card. I actually have the premium version so I just link my whole obb folder and data folder but I would guess linking any obb and then seeing if the game would load would test it. As for Titanium a backup/delete/restore of any app would test all of the features. Thanks for checking that out
Click to expand...
Click to collapse
No problem.
Results
Folder Mount - Made a link from internal to external and the link seemed to be working correctly (files put in one showed up in the other)
Titanium - Backed-up, uninstalled, and restored Netflix successfully with no errors
Here's a link to the root instructions. http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
Please post any questions there.
Works for both locked and unlocked bootloaders now.
SuperPichu said:
Here's a link to the root instructions. http://forum.xda-developers.com/showpost.php?p=56854633&postcount=77
Works for both locked and unlocked bootloaders now.
Click to expand...
Click to collapse
You beat me too it lol. I just got home pulled the ota and modified the boot.img before I saw this.
Keithn said:
You beat me too it lol. I just got home pulled the ota and modified the boot.img before I saw this.
Click to expand...
Click to collapse
I was starting to wonder how I was the only person (or at least the first) to have that idea.
So I already installed the update for lollipop. Although I was rooted using towelroot, I never installed CWM or unlocked my bootloader. Is it too late to follow the instructions to unlock my bootloader at this point? Do I need to just wait for another root method?
onduck said:
So I already installed the update for lollipop. Although I was rooted using towelroot, I never installed CWM or unlocked my bootloader. Is it too late to follow the instructions to unlock my bootloader at this point? Do I need to just wait for another root method?
Click to expand...
Click to collapse
No if you unlock your bootloader you can follow my unlocked instruuctions.
onduck said:
Is it too late to follow the instructions to unlock my bootloader at this point?
Click to expand...
Click to collapse
no. Not too late.
Sent from my HTC One_M8
Has anyone had any luck Rooting this phone. I need to get the tethering and mobile hot-spot option back but everything I've tried hasn't worked. Can someone point me In the right direction?
•Model number: SAMSUNG-SGH-I337Z
•Android version: 4.4.2
•Baseband version: I337ZTUUBOA1
•kernel version: 3.4.0-3238692 / [email protected] #1 / Wed Jan 14 18:33:42 KST 2015
•Build number: KOT49H.I337TUUBOA1
•SWE for Android Status: Enforcing / SE[F_SAMSUNG-SGH-I337Z_4.4.2_0033 / Wed Jan 14 18:33:42 2015
• Secure boot status: Type: Samsung
• Security software version: MDF v1.0 Release 2
I've been told to Downgrade my kernel and reuse towel root just not sure If It can be done or how. Can someone please point me In the right direction??? Can confirm that neither towelroot or kingo root works.
I'm facing this same problem. I recently switched from my old S4 to the new one (SGH-I377ZTUUBOA1) because Cricket is introducing a new network that isn't compatible with my old S4. I have searched the internet rigorously for a successful root method, but nobody seems to have been able to do it. Not to mention I could hardly find any information about this phone. I have tried kingoroot and towelroot with no success. I found this which will downgrade the kernel, but I'm afraid to try it because it is meant for the AT&T S4, and I don't want to impair my new phone. Anyone had any luck with this phone?
See this, http://forum.xda-developers.com/showthread.php?t=2442603&page=2
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
See this, http://forum.xda-developers.com/showthread.php?t=2442603&page=2
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks but I've tried both Kingo and Towelroot with no luck.
Nihilian said:
Thanks but I've tried both Kingo and Towelroot with no luck.
Click to expand...
Click to collapse
Does anyone know about SRSroot software? It claims to work for the new Cricket Samsung galaxy S4 build number.
I tried it and confirm it doesn't work. SRSroot is configured to auto tweet every time a new phone is used with their software regardless of whether it was successful or not.
I can confirm Kingroot works on this. Not Kingo, but Kingroot. It is a Chinese app that installs its own version of Superuser, which is kind of unfortunate. But it does provide you with root. After using this root method, there are threads to install TWRP or Safestrap. From there you can install a custom ROM like CM12 or something.
Not able to post links yet so I don't have one to Kingroot, but do a quick Google search and you shall receive.
Mobius 1 said:
I can confirm Kingroot works on this. Not Kingo, but Kingroot. It is a Chinese app that installs its own version of Superuser, which is kind of unfortunate. But it does provide you with root. After using this root method, there are threads to install TWRP or Safestrap. From there you can install a custom ROM like CM12 or something.
Not able to post links yet so I don't have one to Kingroot, but do a quick Google search and you shall receive.
Click to expand...
Click to collapse
Oh man thank you so much! I had given up all hope of ever rooting my phone until you swooped in out of nowhere! You fricken rock dude! Thank you!
Here's the link for anyone else facing the same problem: http://www.kingroot.net
And here's an easy way to replace the Chinese superuser app with SuperSU: http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/
Anyone know where I can find a recovery for this phone?
Nihilian said:
Oh man thank you so much! I had given up all hope of ever rooting my phone until you swooped in out of nowhere! You fricken rock dude! Thank you!
Here's the link for anyone else facing the same problem: http://www.kingroot.net
And here's an easy way to replace the Chinese superuser app with SuperSU: http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/
Anyone know where I can find a recovery for this phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55055768
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
http://forum.xda-developers.com/showthread.php?p=55055768
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you!