Related
ok so i got my replacement thunderbolt and tried to use the 3 step root tool on here and i think something went wrong. i made it to step 3, it says s off and seemed ok. i rebooted, tried to fix permissions to test and it failed. now all i get is the HTC white boot screen and thats it. i can go into bootloader (the screen with hboot, recovery, etc) and i can load up recovery but when i try to do a restore (backup from the old phone) i get an error and it fails. is it screwed? what can i do to correct this? thanks guys!
[email protected]|ice said:
ok so i got my replacement thunderbolt and tried to use the 3 step root tool on here and i think something went wrong. i made it to step 3, it says s off and seemed ok. i rebooted, tried to fix permissions to test and it failed. now all i get is the HTC white boot screen and thats it. i can go into bootloader (the screen with hboot, recovery, etc) and i can load up recovery but when i try to do a restore (backup from the old phone) i get an error and it fails. is it screwed? what can i do to correct this? thanks guys!
Click to expand...
Click to collapse
If you can get into recovery, wipe EVERYTHING (data/cache/dalvik). Then mount USB and put a rom on your SD. Flash that. If you tried to fix permissions BEFORE you installed a ROM, then you kinda skipped a step mate.
DO NOT RERUN THE ROOT METHOD. IF you have S-OFF, jut flash a ROM
cj2566 said:
If you can get into recovery, wipe EVERYTHING (data/cache/dalvik). Then mount USB and put a rom on your SD. Flash that. If you tried to fix permissions BEFORE you installed a ROM, then you kinda skipped a step mate.
DO NOT RERUN THE ROOT METHOD. IF you have S-OFF, jut flash a ROM
Click to expand...
Click to collapse
thank you for the quick reply! so there is some hope for this thing then, woohoo!
yes i have wiped everything you mentioned. how does one mount usb from that menu? from within recovery? i saw a usb option on that (is it called bootloader?) is that what your speaking of?
now as a rom i DO have the gingerjane rom from jcase on there somewhere, is that safe to flash on there to fix this? thanks again!
If you have access to recovery (as you said you do) just load it, wipe, and flash any Thunderbolt rom you put on your sdcard (or already have in your case). Whether the rom you flash will fully works or not depends on whether it is compatible with your current radio.
But as long as you have access to recovery, you are set.
it booted! thank you both.
now im positive the root failed but it says s-off and superuser does show in the app drawer. im gonna try to d/l rom manager since its not on here anymore and see if it works.
if root failed am i safe to do the three step process again?
just don't flash roms with Rom Manager. It's known to cause problems with the Thunderbolt..
[email protected]|ice said:
it booted! thank you both.
now im positive the root failed but it says s-off and superuser does show in the app drawer. im gonna try to d/l rom manager since its not on here anymore and see if it works.
if root failed am i safe to do the three step process again?
Click to expand...
Click to collapse
Not sure what "3 step process" you are referring to but I'm gonna say no.
You have recovery. You can clearly flash roms. The roms contain Superuser.apk and su binaries which means THEY are rooted. Flash a good copy of a rooted rom from recovery and you will have working SU.
If that means you have to download another copy of a rom and put it on your sdcard then do it. Point is, roms are "rooted" not the phone. You can't "root" something that doesn't have an OS. Common misconception but I'm leaving it at that.
Everything is working great now, thank you all for your guidance and support. Love my android community. Can't thank you enough.
Ive tried flashing both following EillonCross directions using the same twrp as he did but it still failed. im trying it with 2.6.3.7 and having unable to mount usbstorage. with 2.6.3.2 i was unable to load anything from my external sdcard. If someone has a way to flash the m15 rom could you please let me know if there is a small detail im missing or something. Baseband says m13 still and software does as well. :/ btw im installing both the firmware update and rom.
onemanruler said:
Ive tried flashing both following EillonCross directions using the same twrp as he did but it still failed. im trying it with 2.6.3.7 and having unable to mount usbstorage. with 2.6.3.2 i was unable to load anything from my external sdcard. If someone has a way to flash the m15 rom could you please let me know if there is a small detail im missing or something. Baseband says m13 still and software does as well. :/ btw im installing both the firmware update and rom.
Click to expand...
Click to collapse
Haven't experienced the TWRP issue but I was able to make a nandroid backup with TWRP and it mounted external SD (haven't tried to restore), but regarding your issue. I installed Wanam Xposed to fake my status from Custom to Official and did an OTA update from M13 to M15. I lost root and used chainfire again to fix it (I originally updated to get the native hotspot working since it's for M15 only). Hope that helps!
Tavo_7 said:
Haven't experienced the TWRP issue but I was able to make a nandroid backup with TWRP and it mounted external SD (haven't tried to restore), but regarding your issue. I installed Wanam Xposed to fake my status from Custom to Official and did an OTA update from M13 to M15. I lost root and used chainfire again to fix it (I originally updated to get the native hotspot working since it's for M15 only). Hope that helps!
Click to expand...
Click to collapse
could you share how you did it step by step thanks
viettt said:
could you share how you did it step by step thanks
Click to expand...
Click to collapse
which part?
Im trying to use xposed to set it back to official but it will not change ive tried it serveral times now.
onemanruler said:
Im trying to use xposed to set it back to official but it will not change ive tried it serveral times now.
Click to expand...
Click to collapse
Make sure you install the exposed framework, the link is in the description on the play store. Once installed, make sure to update it under framework settings, then activate the xposed module under module settings. Now you'll have access to flag it as official
Did both those steps and it is still not sticking I'm confused like no other at this point lol. I do appreciate the replys. Still trying to figure it out so if you think of something I'll be watching this thread.
Sent from my SM-N900P using xda app-developers app
I can only guess that your SU is not working properly, are you getting the prompts to gain root access? worst case, reinstall superuser.
Yea su is working. Prompts for su access when I open root apps.
Sent from my SM-N900P using xda app-developers app
I can't recall where I saw on these forums but....
The Xperia Ultra rom exploits all seem to use vroot. However vroot had been found ti be sending IMEI numbers back to China. Nice
But given that hamdogg. Et.Al have used vroot in ROMS they have released, who feels worried?
Is there another root exploit you are using?
vroot is not working any more.
avetny said:
vroot is not working any more.
Click to expand...
Click to collapse
Not quite what I was asking
keratos said:
Not quite what I was asking
Click to expand...
Click to collapse
You are safe with a custom ROM. They don't use any tool... don't need to.
- With a rooted ROM, it flashes the superuser or superSU app, and applies the appropriate binaries and permissions directly to the ROM system.
But... to get a recovery flashed onto your system, you'll need to use vROOT or a similar tool, as it will need root access to apply the recovery script, and flash recovery. So.. you must have already used such a tool to originally root your device...
Two Important Points here:
- The app/s only "MAY" have your IMEI numbers stored. I say may, because all we currently know is that the IMEI numbers were read, we don't know for sure if they have been stored anywhere.
- If the app/s continues to send information [we currently don't know this yet] then it would be better to have a custom ROM. As it will clear your device of all app data and have ROOT access. This is only if you want to have a rooted device.
Hope that clears things.
hamdogg said:
You are safe with a custom ROM. They don't use any tool... don't need to.
- With a rooted ROM, it flashes the superuser or superSU app, and applies the appropriate binaries and permissions directly to the ROM system.
But... to get a recovery flashed onto your system, you'll need to use vROOT or a similar tool, as it will need root access to apply the recovery script, and flash recovery. So.. you must have already used such a tool to originally root your device...
Two Important Points here:
- The app/s only "MAY" have your IMEI numbers stored. I say may, because all we currently know is that the IMEI numbers were read, we don't know for sure if they have been stored anywhere.
- If the app/s continues to send information [we currently don't know this yet] then it would be better to have a custom ROM. As it will clear your device of all app data and have ROOT access. This is only if you want to have a rooted device.
Hope that clears things.
Click to expand...
Click to collapse
You don't need root access to flash a custom recovery. You can just flash from fastboot. You can use the original recovery found here. http://forum.xda-developers.com/showthread.php?t=2426736
You need an unlocked bootloader though. Also you need to remember to flash your normal kernel back afterwards, although that will be done automatically if you flash a custom rom from recovery,
baileyjr said:
You don't need root access to flash a custom recovery. You can just flash from fastboot. You can use the original recovery found here. http://forum.xda-developers.com/showthread.php?t=2426736
You need an unlocked bootloader though. Also you need to remember to flash your normal kernel back afterwards, although that will be done automatically if you flash a custom rom from recovery,
Click to expand...
Click to collapse
Urm... You need to be rooted to unlock boot loader don't you?
Sent from my C6833 using XDA Premium 4 mobile app
SpyderTracks said:
Urm... You need to be rooted to unlock boot loader don't you?
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I want to say no?
LordManhattan said:
I want to say no?
Click to expand...
Click to collapse
****, I'm getting everything wrong at the moment, my brains gone weird.
Sent from my C6833 using XDA Premium 4 mobile app
SpyderTracks said:
Urm... You need to be rooted to unlock boot loader don't you?
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, but you do need to be rooted to backup your TA Partition.
Thats the trade off. If you unlock without first having root you can't restore TA and the DRM at a later date.
I rooted with Vroot and backed up mine, but I would have unlocked the bootloader regardless if I had too. Not missed any off the DRM tools at all.
UPDATE 05/28/15 This works fine without doing the xposed part on Lollipop. No speed issues. It may be totally unnecessary now but I am not going to retry it to see. It may once again become necessary to follow these instructions when we get xposed for lollipop.
There are a number of threads about these two topics, I am going to consolidate my findings here.
First off root works great on the Sprint variant, secondly so does Xposed with S-Health and private mode. You just have to be careful how you set them up. There have been a lot of posts about freezing S-health and Private mode then clearing data but from my experience that is hit or miss. There are four basic steps to getting everything working and it should be done from a factory reinstall of software. The files you will need are in the following threads/links
Chainfire Autoroot - http://autoroot.chainfire.eu/
Chainfire File Link - http://download.chainfire.eu/617/CF-Root/CF-Auto-Root/CF-Auto-Root-tbltespr-tbltespr-smn915p.zip
Xposed - http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Xsecure - http://forum.xda-developers.com/xposed/modules/app-xshealth-bypass-secure-storage-t2878708
Teamwin Recovery - http://www.techerrata.com/browse/twrp2/trltespr
Root using Chainfire autoroot for Sprint it will fail just pull the battery and boot to download to install the teamwin recovery (buttons HOME, VOLUME DOWN, AND POWER) boot to recovery then install supersu. Before leaving recovery set the screen timeout off and lower the brightness to 10.
Skip past Google and Samsung setup. You can fill out the first and last name screen (only opportunity to name phone, first boot).
Download and install Xposed (not Wanam) download and install XSecure Health module install Xposed framework reboot
Activate Xsecure Health module reboot
Clear Data for Health Service and S-Health reboot
Run Private mode and set up, run S-Health and setup.
Setup your Google and Samsung accounts
If you do these steps exactly without doing anything else I can promise you will have a rooted Sprint version with Xposed, Shealth, and private mode working. When I say exactly I am serious there are a lot of things that can/will mess you up like
Signing into google or samsung on reboot after installing factory software
Starting private mode before setting up xposed
Shortcutting by doing a factory reset instead of a factory software reinstall
Restoring your data Nandroid backup (Use Titanium etc for a program by program reinstall of apps)
BTW the problem here is a little bit deeper than uninstall xposed everything works. There is a something that is changed in the software with either xposed or wanam that can permanently kill private mode until you do a factory install. At the moment I am doing Nandroids before any change I make in Xposed.
worked like a charm. Thank you very much.
blackinjun said:
Root using Chainfire autoroot for Sprint it will fail just pull the battery and boot to download to install the teamwin recovery
Click to expand...
Click to collapse
Is it absolutely necessary to install the custom recovery to achieve root? I only ask because I prefer to leave the stock recovery
Sent from my SM-N915P using XDA Free mobile app
metal666fukhead said:
Is it absolutely necessary to install the custom recovery to achieve root? I only ask because I prefer to leave the stock recovery
Sent from my SM-N915P using XDA Free mobile app
Click to expand...
Click to collapse
Sorry it is because the SU has to be installed outside of the system. There may be a way to then use TWRP or CWM to reinstall the stock recovery but I have not researched that.
Thanks blackinjun for this, I just got a Sprint variant of the Note Edge. I believe that I'm on NK1, it's been a while since I rooted a device, last one was about 2 years ago on my Galaxy S4. Will try it this weekend.
blackinjun said:
Sorry it is because the SU has to be installed outside of the system. There may be a way to then use TWRP or CWM to reinstall the stock recovery but I have not researched that.
Click to expand...
Click to collapse
@metal i now think it may be better to keep the custom recovery. Ive found that when su says it needs an update it asks to reboot ro twrp or cwm to update. I have twrm and it worked flawlessly.
Sent from my SM-N915P using Tapatalk
@Hired no prob
Sent from my SM-N915P using Tapatalk
worked for me as well just like you said..one problem im seeing though..well not sure if it matters..but while makeing my back of stock system,i see in red letters cant mount cace several times,but it completes the back up,and says sussefull..im backing up to my external sd card..i flashed the super user zip first before back up,flashed latest zip,hope this diddnt matter,did you mean to let twrp install it?..or ok to flash the zip?..anyhow,should i worry about the red letters 'cant mount cacge'??...i dont like it when i see any red letters while in recovery,just looks bad to me,like something is wroung...
blackinjun said:
@metal i now think it may be better to keep the custom recovery. Ive found that when su says it needs an update it asks to reboot ro twrp or cwm to update. I have twrm and it worked flawlessly.
Sent from my SM-N915P using Tapatalk
Click to expand...
Click to collapse
I have a client that I rooted their Note Edge but they really want Stock Recovery. Do you know how to put stock recovery back on there?
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
sand1303 said:
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
Click to expand...
Click to collapse
Download the zip file not the IMG.tar
Is it possible to do this. If my phone is already rooted?
I randomly found a YouTube video they walked me through rooting my phone before I knew shealth would have not work. This was a couple months ago I guess. So I'd like to get it back. Though doing factory reset isn't something that I'd prefer to do. But if it comes to it.
I'd assume just follow the rest of the steps in your tutorial?
sand1303 said:
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
Click to expand...
Click to collapse
You didn't unzip it right? Make sure you download the one with the .tar extension
ya thats what i was doing. i downloaded the .tar and unzipped it. flashing it without unzipping it worked fine
DevXen said:
Is it possible to do this. If my phone is already rooted?
I randomly found a YouTube video they walked me through rooting my phone before I knew shealth would have not work. This was a couple months ago I guess. So I'd like to get it back. Though doing factory reset isn't something that I'd prefer to do. But if it comes to it.
I'd assume just follow the rest of the steps in your tutorial?
Click to expand...
Click to collapse
this trick will work if your already rooted. Clear your D. Cache and cache and start from the download/install xposed portion of the instructions. This is what I ended up doing and haven't had any issues at all.
For those who have moved to lollipop has anyone tried this method
Sent from my SM-N915P using Tapatalk
+1, Would like to know how to root now that I have Lollipop............links, instructions, etc.
Same process as rooting kk i had no probl3ms with s health or private mode
Sent from my SM-N915P
Which method in Post #1 did you use?
Root using chainfire odin twrp ,xposed does not work on lolipop,so no other steps.
Sent from my SM-N915P
Below you will find my procedure to root the SM-J727P Galaxy J7 Perx / MSM8953
This procedure has only been tested on J727PVPU1AQB9 firmware. It may work for future releases or it may not.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
This took some doing and was a tough nut to crack. I don't own this device and much thanks goes to those that stuck with it in the testing phase, without whom it would not have even been possible. Credits below.
To see how we got here and before asking any questions click this link: https://forum.xda-developers.com/galaxy-j7/help/root-sm-j727p-galaxy-j7-perx-galaxy-j7-t3598117
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the files below:
J727P-SuperSU-v2.79-SR3_rooted_boot_AQB9
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to RECOVERY mode then select FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA. (This procedure is required to remove encryption or your device won't boot)
◘ 4. From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY OR YOUR DEVICE WILL RE-ENCRYPT)
◘ 5. Run ODIN and place the J727P_SuperSU-v2.79-SR3_rooted_boot_AQB9.tar file as is in the AP slot. Don't change any options and hit START.
◘ 6. Wait for the device to flash and reboot.
◘ 7. Install the SuperSU apk from Play store and you should be rooted.
◘ 8. Have fun!
Credits: ME, @Borams @Project89Odin @Chainfire and special thanks to @RS.85243
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
scbcskin said:
I got the encryption error on reboot. I then did the reset it required and rebooted. I installed supersu just to see what it would say. It says root not properly installed in root checker, so I guess that means its there but I guess its a binary issue? Is there something that I didnt do correctly or a step I missed?
Click to expand...
Click to collapse
Whoops glad you pointed that out, forgot to include that step!
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
scbcskin said:
I factory reset, booted directly to download mode, flashed tar, phone rebooted. I installed Supersu but still not rooted.
Click to expand...
Click to collapse
When you open the SuperSU app does it complain about no binary installed?
ashyx said:
When you open the SuperSU app does it complain about no binary installed?
Click to expand...
Click to collapse
It sure does!!
scbcskin said:
It sure does!!
Click to expand...
Click to collapse
Strange, it works perfectly on Marshmallow. Looks like we're going back to the old method of manually pushing su.img to data!
Will update shortly.
Have you tried rebooting again to see if works after that?
Just did a reboot and same deal.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Project89Odin said:
If you grant root permission before opening supersu apk but after downloading it, it does not ask to update binary with first op build
Click to expand...
Click to collapse
Say again. Can you explain in more details, not sure I understand?
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Project89Odin said:
After process in op, after downloading supersu do not open it, download something that requires root and grant it. It will grant without ever opening supersu. I granted flashfire and flashed sr3 just to make sure. After reboot i opened the supersu app and it asks for no update. Although disabling knox did not work for me.
Click to expand...
Click to collapse
OK I see. Can you do me a favour and test the updated version?
First delete su.img from /data or just unroot from SuperSU settings then reboot to download mode and install the new version. Your device should auto re-root.
https://www.androidfilehost.com/?fid=961840155545567256
ashyx said:
I think I've just found the issue. Try this version instead, no need to format, just install with ODIN.
https://www.androidfilehost.com/?fid=961840155545567256
.
Click to expand...
Click to collapse
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
After deleting su in /data andfull unroot, flashed newer build and supersu reports no binary, not even one to update, no root
scbcskin said:
Root has been achieved my friend. At first a flashed it and when it booted I got the encryption error. I just pulled the battery and then tried to boot into recovery. Instead of going in recovery it booted like normal. I installed Supersu and it got stuck attempting to disable Knox. Well after about 2 minutes or so of watching that I just went to root checker and there it was. I think I can speak for everyone when I say job well done!!!:good:
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Quick question, must you have custom recovery in order to install Xposed or is it just a suggestion?
Click to expand...
Click to collapse
Thanks for confirming. OP updated.
You can use Flashfire to install Xposed.
ashyx thank you for your efforts. Thanks to everyone else that helped as well. Guess what I just ordered. Can't wait to get my new phone and root, install viper4android. Both are a must for me and I never own a phone I can't have both on.
scbcskin said:
Just did a reboot and same deal.
Click to expand...
Click to collapse
When the reboot is repeated,
please flash the original firmware to odin
and try again from the beginning.
from CIAO7
after unrooting, repeating format is required to reroot. Works flawless. Thankyou again. Looking forward to a fully functional twrp now!!
Project89Odin said:
Thankyou again. Looking forward to a fully functional twrp now!!
Click to expand...
Click to collapse
It's next on my hit list. Just need to figure out why the source built kernel doesn't boot.
Now that root is achieved there's more chance of finding out what's going on, so I'll be calling on you guys again at some point for logs.