Hey guys I'm about to attempt to root/flash my G2 with the cyanogen (spelling?) ROM. This is my first time ever so before I begin I wanted to know if their was a guide with the basics? (rooting, nandroid (still clueless as to what this is) , how to back up what I have now)
Also is their any advantage to rooting? I heard it gives big speed increases, I'm a little worried though because 2.3 should be coming out soon? and I'm stuck between waiting for the original 2.3 or updating from a Cyanogen mod
Kasaki said:
Hey guys I'm about to attempt to root/flash my G2 with the cyanogen (spelling?) ROM. This is my first time ever so before I begin I wanted to know if their was a guide with the basics? (rooting, nandroid (still clueless as to what this is) , how to back up what I have now)
Also is their any advantage to rooting? I heard it gives big speed increases, I'm a little worried though because 2.3 should be coming out soon? and I'm stuck between waiting for the original 2.3 or updating from a Cyanogen mod
Click to expand...
Click to collapse
Yes there are advantages with rooting and also risks, but if your only worried about the gingerbread update, there is already an unofficial Cyanogen CM7.0 rc0 and GingerVillian beta versions of Gingerbread for the HTC Vision out right now.
As far as a guide for rooting, nandriod etc. there are a few ways of rooting, Rage, Visionary and gfree. My suggestion would be if you know how to use ADB, to root(Rage)+gfree which can be found here:
Starting in the sub-section: Rooting the Vision (G2/DZ) and DHD
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Next way No adb needed.
If your not familiar with ADB, you can always root with Visionary. The following links will help walk you thru rooting your phone using visionary r14. I have not had any problems with it, many people have rooted this way. If something goes wrong it is usually operator error. This method is for after the OTA. All needed files and links are in the video instructions.
Visionary has bricked phones before when not properly used, the videos show how to use it properly, use all the settings in the videos.
This is the visionary method, but works perfectly when done correctly..
Follow the videos to a "T", remove visionary and superusers from you phone if you already have them installed from a previous temp root before following the videos, start fresh, follow the videos starting with temp root then onto perm root then onto flashing a rom. Do everything just like the videos start to finish and you should have no problems.
Temp-root first:
http://theunlockr.com/2010/10/20/how-to-root-the-t-mobile-g2-htc-vision-visionary-method/
Perm-root second:
http://theunlockr.com/2010/11/30/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-g2-htc-vision/
Nandriod and flashing a rom last:
http://theunlockr.com/2010/11/30/how-to-load-a-custom-rom-on-the-t-mobile-g2-htc-vision/
Remember don't assume you know how to temp root properly, follow all three videos start to finish and you should have no problems
The cerdit for the videos goes to Daivd Cogen from the unlockr.
As far as nandriod once you flash ClockWorkMod recovery you will be able to back up your existing rom, the last video link I gave you shows you how to do this.
I recommend using the guide found in the Wiki, which is the most up-to-date. See http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Although a lot of people have used Visionary successfully, another lot of people have ended up semi-bricking their phone when it somehow went wrong. You will find plenty of threads about this. Whereas with the method in the Wiki, if something goes wrong then you will just get an error message and/or the root won't stick, but your phone will still work fine.
It's easy to get adb working on your PC, which is needed for the Wiki procedure, if you follow this guide - http://forum.xda-developers.com/showthread.php?t=865685
"nandroid" is the term for a backup/restore done via ClockworkMod, a custom recovery which can be installed via the ROM Manager app (or even flashed separately). However, you will need to have S-OFF to flash a custom recovery, so that's not going to help you for backing up stuff before you do root. Although rooting won't lose any data/settings. Once you have root/S-OFF then you can do a nandroid backup, and you should definitely do one before you flash any custom ROM like Cyanogen.
You can sync contacts/calendar etc to Google to back those up. If you want to backup texts, then you will need to do that separately - e.g. I use the "SMS Backup" app to send my texts to my Google Mail account, though that app won't restore them (but that doesn't bother me).
Rooting won't change anything noticeable about how your phone works, but combined with S-OFF (security off), it unlocks your phone so there are more things you can modify on it - e.g. overclocking, root-only apps. One of the main advantages if you S-OFF is that you can then flash custom ROMs. Though I have root/S-OFF and am still running a stock ROM. You can stay with a stock ROM and overclock once you have root, or flash a new custom ROM which also has overclocking potential plus other features.
Thanks alot , I'll most likely use the gfree method as it seems easiest. When I flash a new rom I don't need to wipe my phone completely? but it's recpmended
Kasaki said:
Thanks alot , I'll most likely use the gfree method as it seems easiest. When I flash a new rom I don't need to wipe my phone completely? but it's recpmended
Click to expand...
Click to collapse
Full Data and cache wipe when flashing between different ROMS, and not needed when flashing the same ROM or updates.
joemm said:
Full Data and cache wipe when flashing between different ROMS, and not needed when flashing the same ROM or updates.
Click to expand...
Click to collapse
Just out of curiousty, Is their a guide to wipe the phone? or is that done form the recovery window? I'm about to start the rooting process now. Currently backing stuff up
Kasaki said:
Just out of curiousty, Is their a guide to wipe the phone? or is that done form the recovery window? I'm about to start the rooting process now. Currently backing stuff up
Click to expand...
Click to collapse
Once you have ClockworkMod Recovery Flashed and you boot into recovery there is an option to wipe Data and option to wipe cache from recovery. The picture below is what it looks like from recovery, note this is not the current recovery version for the HTC G2 but it looks exactly the same. The current recovery is v.2.5.1.3 for the G2
{
"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"
}
To root go to unlockr. Com which shows it very easily and then pocketnowvideo on you tube has full walkthroughs of rom manager which makes everything very easy
Sent from my HTC Vision using XDA App
When i get to the cmd on my pc what do I type out
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse
Thanks everyone just successfully flashed cyanogen !!!
theunlockr.com was the most helpful website ever!!
This seemed like an excellent place to ask my question:
There is a very new OTA update for the Desire Z (1.72 ROM) which prevents current methods of rooting.
See: Rooting/S-OFF with the new 1.72 Desire Z ROMs - currently not possible
I live in the US and I am looking to purchase the T-mobile G2 and then root it.
So I was wondering if I buy a completely new G2 within one week, if it will be the old rootable version instead the new unrootable one on the Desire Z.
thecarbine said:
This seemed like an excellent place to ask my question:
There is a very new OTA update for the Desire Z (1.72 ROM) which prevents current methods of rooting.
See: Rooting/S-OFF with the new 1.72 Desire Z ROMs - currently not possible
I live in the US and I am looking to purchase the T-mobile G2 and then root it.
So I was wondering if I buy a completely new G2 within one week, if it will be the old rootable version instead the new unrootable one on the Desire Z.
Click to expand...
Click to collapse
The G2 and the Desire Z have diffrent updates, so to awnser your question the G2's are still rootable even with the G2 OTA, which is not the Desire Z 1.72 OTA.
joemm said:
The G2 and the Desire Z have diffrent updates, so to awnser your question the G2's are still rootable even with the G2 OTA, which is not the Desire Z 1.72 OTA.
Click to expand...
Click to collapse
Excellent.
I will be receiving my T-mo G2 within the coming weeks. It'll be rootable for at least this long, presumably? (like the Desire Z update won't migrate or anything?)
Cheers, pal
thecarbine said:
I will be receiving my T-mo G2 within the coming weeks. It'll be rootable for at least this long, presumably? (like the Desire Z update won't migrate or anything?)
Click to expand...
Click to collapse
I imagine it will be ok, but I would be very suprised if the extra security in the 1.72 DZ OTA doesn't find its way to the G2 via an OTA at some point. Though hopefully by that point it will have been cracked anyway.
Related
/Update: Rooting went fine. Updated this thread - maybe it helps if somebody wants to root his/her 2.3.3 DZ and is being overwhelmed by guides etc.
Hi there!
I finally decided to root my Stock 2.3.3 Desire Z - I've read a lot, but I'm still confused when it comes to certain steps of rooting. I just wanted to get "green light" by someone who certainly has more experience in rooting etc.
First I read this ADB guide to get familiar with it. I certainly didn't understand everything about it, but the basic stuff should be clear.
Next step is downgrading my phone. I want to use this guide as mentioned in the HTC Vision wiki.
Which raises the first question: What's with that post, which Desire Z users should read. I don't really see the connection to the guide I want to use - it's stated that one should replace psneuter with fre3vo in step 4. But which step 4? Little confused.
So which step is different to execute for me?
No step is different, the guide is up to date and can be used with every device stated in its headline.
Next steps should be clear.
So after downgrading I planned on sticking with the Vision wiki - seems that every step is described clearly, even for an ADB dummy.
If everything went well, I planned to flash the Virtuous Sense v2.0.0 which requires a "full wipe".
So it's nonsense to save application settings via titanium backup in the first place, because I want to set Virous 2.0.0 as backup-rom anyway? Are there files I should backup - besides contact info etc.?
Application settings can be restored if you stick to the downgrade guide, only system settings/stuff should not be restored.
And am I missing anything important? Are there other (better) ways of rooting my device?
No
Tiny, rather unimportant last question - is there a way to save my savegames to just load them later if needed? Since the "full wipe" wipes everything (?), I don't see how I could save them.
See above.
Looking forward to be enlightened!
Greetings!
Kueber said:
Hi there!
I finally decided to root my Stock 2.3.3 Desire Z - I've read a lot, but I'm still confused when it comes to certain steps of rooting. I just wanted to get "green light" by someone who certainly has more experience in rooting etc.
First I read this ADB guide to get familiar with it. I certainly didn't understand everything about it, but the basic stuff should be clear.
Next step is downgrading my phone. I want to use this guide as mentioned in the HTC Vision wiki.
Which raises the first question: What's with that post, which Desire Z users should read. I don't really see the connection to the guide I wan't to use - it's stated that one should replace psneuter with fre3vo in step 4. But which step 4? Little confused.
So which step is different to execute for me?
Next steps should be clear.
So after downgrading I planned on sticking with the Vision wiki - seems that every step is described clearly, even for an ADB dummy.
If everything went well, I planned to flash the Virtuous Sense v2.0.0 which requires a "full wipe".
So it's nonsense to save application settings via titanium backup in the first place, because I want to set Virous 2.0.0 as backup-rom anyway? Are there files I should backup - besides contact info etc.?
And am I missing anything important? Are there other (better) ways of rooting my device?
Tiny, rather unimportant last question - is there a way to save my savegames to just load them later if needed? Since the "full wipe" wipes everything (?), I don't see how I could save them.
Looking forward to be enlightened!
Greetings!
Click to expand...
Click to collapse
I followed the downgrading guide you linked to in order to downgrade from 2.3.3 and it worked perfectly for me (and many others, it seems). The guide uses fre3vo so I think you are safe to just follow the steps described in it.
I used SMS Backup & Restore and Angry Birds Backup free, both worked a treat. Other than that I restored everything from scratch.
It's probably a good idea to do a nandroid backup after rooting the stock froyo ROM but before flashing something else. Just in case.
Good luck
Yeah, and you probably should have posted this in Q&A
Eventually it would have been better, yup, but then I considered this thread more like a list of steps you want to go through to root your Desire Z 2.3.3 successfully - maybe it helps someone.
Anyway, thanks for your answer. I'll try that SMS Backup app.
Now I have to gather some informations about that "nandroid" backup - I've read it several times, but still I don't know what exactly it does / its benefits are.
If anyone would like to give a brief explanation, feel free!
Greetings
/edit: Well, a nandroid backup can be done with clockwork recovery, which installation is kinda part of the rooting process. There's one thing I don't understand yet - how to load that backup if it's needed?
Kueber said:
Now I have to gather some informations about that "nandroid" backup - I've read it several times, but still I don't know what exactly it does / its benefits are.
If anyone would like to give a brief explanation, feel free!
Greetings
/edit: Well, a nandroid backup can be done with clockwork recovery, which installation is kinda part of the rooting process. There's one thing I don't understand yet - how to load that backup if it's needed?
Click to expand...
Click to collapse
Part of the rooting process gives you a better recovery partition that you can boot into, where you can flash roms, backup/restore ROMs and has some other tools,this is independent of the ROM you flash and is a safety net when messing with your phone.
bombadier said:
Part of the rooting process gives you a better recovery partition that you can boot into, where you can flash roms, backup/restore ROMs and has some other tools,this is independent of the ROM you flash and is a safety net when messing with your phone.
Click to expand...
Click to collapse
So, essentially, as you already mentioned, that means I got safety tools that work independent. For example - if everything goes wrong and I have a copy of that nandroid backup somewhere, I could easily adb push that onto my sd card and flash it? Or has this backup to be on my sd card all the time, because in certain cases the sd-card is not mountable?
Just want to make sure that I understand what I'm doing..
Kueber said:
So, essentially, as you already mentioned, that means I got safety tools that work independent. For example - if everything goes wrong and I have a copy of that nandroid backup somewhere, I could easily adb push that onto my sd card and flash it? Or has this backup to be on my sd card all the time, because in certain cases the sd-card is not mountable?
Just want to make sure that I understand what I'm doing..
Click to expand...
Click to collapse
You don't have to have the nandroid backup on your SD card at all times. You can do a backup, copy it to your computer and keep it there if you need the space on your SD card for daily use. There is also the possibility to keep multiple backups of different ROMs if you wish to change UI more often.
Whatever your needs, you should at least keep one backup from a stable setup. If anything goes wrong you can copy it back to your SD card (if it is not already there), boot into recovery (volume down + power) and choose backup/restore and restore your backup. Everything will be exactly as it was when backing up - very convenient
Everything went fine, updated thread - maybe it helps someone.
Thanks again!
Good to hear it went well
Got full root access and all the way to step 5 on the Wiki and go to verify that it worked and I get the...
secu_flag = 1
CID = T-MOB010
SIMLOCK = 01
Please disregard.
For my DZ:
secu_flag = 0
CID = 11111111
SIMLOCK = 00
Sent from my HTC Vision using XDA App
which method do i follow to just root my Desire z.
I dont want to update h-boot, or install clockwork recovery.
My device has S-off with stock htc sense rom...i just want root
sandipbarik said:
which method do i follow to just root my Desire z.
I dont want to update h-boot, or install clockwork recovery.
My device has S-off with stock htc sense rom...i just want root
Click to expand...
Click to collapse
Just follow the xda Vision wiki.. read it attentively.
You'll see that you can just skip these steps.
Im using that method & rooted my DZ.
Sent from my HTC Vision using XDA App
look, I don't want to downgrade my system.
I want to root 2.3.3. is this possible ?
artur-x said:
look, I don't want to downgrade my system.
I want to root 2.3.3. is this possible ?
Click to expand...
Click to collapse
You can't root 2.3.3 directly. In order to root you need to first downgrade to 2.2 and then root. Afterwards you can choose to install a rooted 2.3.3 stock ROM, a custom ROM with 2.3.5 or 2.3.7 depending on what you choose. Or you can try out one of the ICS alphas.
Sendt fra min HTC Vision med Tapatalk
I have factory 2.3.3 in my desire z , is it possible to root it (downgrade and change to something new ) and not to lose my data and installed applications?
Zocca: You have to downgrade, but the downgrade guide contains a section to get Titanium Backup running, so you can backup your apps and data.
-Nipqer
TD;DR Since I already have the bootloder unlocked, would re-rooting my N7 wipe it?
I know it's a noobish question, I've already rooted my device once, but it was fresh out of the box, I had nothing important on it.
I accidentally updated to 4.2.2 and it screwed up my Bluetooth.
I rooted on 4.2.2 and rolled back to 4.1.2.
Decided that Bluetooth wasn't such a huge deal (got tired of carrying around a Wiimote and Nunchuck everywhere,) so I updated back to 4.2.2, which made me lose my root.
(I even used a root protecting app, didn't work :/ )
So yeah, It's unlocked, I can get to the bootloader and all that jazz.
So does Rooting wipe the N7, or is it just when you first unlock it?
Exact same happened to me I would appreciate an answer too.
Sent from my Nexus 7 using XDA Premium HD app
blahman179 said:
TD;DR Since I already have the bootloder unlocked, would re-rooting my N7 wipe it?
I know it's a noobish question, I've already rooted my device once, but it was fresh out of the box, I had nothing important on it.
I accidentally updated to 4.2.2 and it screwed up my Bluetooth.
I rooted on 4.2.2 and rolled back to 4.1.2.
Decided that Bluetooth wasn't such a huge deal (got tired of carrying around a Wiimote and Nunchuck everywhere,) so I updated back to 4.2.2, which made me lose my root.
(I even used a root protecting app, didn't work :/ )
So yeah, It's unlocked, I can get to the bootloader and all that jazz.
So does Rooting wipe the N7, or is it just when you first unlock it?
Click to expand...
Click to collapse
javajava14 said:
Exact same happened to me I would appreciate an answer too.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Rooting wipes data, its best you make a nandroid backup or backup to PC......correct if I'm wrong hope this helps
I don't think so.
The unlocking generally wipes it.
I've rooted many a device (that weren't locked) and they weren't wiped.
Now, installing a ROM generally calls for a wipe unless you're updating the same....
If you use a root method that calls for an unlocked bootloader, unlocking the bootloader wipes. Any root method that does not require an unlocked bootloader will not wipe the device.
Sent from my SPH-D710 using xda premium
graydiggy said:
If you use a root method that calls for an unlocked bootloader, unlocking the bootloader wipes. Any root method that does not require an unlocked bootloader will not wipe the device.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This is very correct that's why I just throw in the.......correct me if I'm wrong!
Unlocking bootloader wipes data, not rooting....
dalanik said:
Unlocking bootloader wipes data, not rooting....
Click to expand...
Click to collapse
Yep. Agreed.
Rooting and Unlocking the Bootloader have seemingly become synonymous with each other, and confusion has crept in. Because the 'traditional' method of Rooting the Nexus 7 necessitates an unlocked Bootloader (in order to run the required Fastboot commands).
Unlocking the Bootloader (which for security reasons wipes the device) and Rooting are two completely different procedures (but the success of one, is contingent upon the success of the other).
And of course you can now Root the N7 without unlocking the Bootloader at all (and thus no wipe), with this 'exploit'...
http://forum.xda-developers.com/showthread.php?t=2233852
Rgrds,
Ged.
although if you want to install a different rom, a wipe is highly suggested for stability. not 100% required, but much better if you wipe. i highly suggest Helium (also known as Carbon) to back everything up, along with a nandroid just in case. enjoy ur n7!
You certainly should be wiping between ROM flashes, but keep in mind that OP's bootloader is already unlocked. At this point, more or less any root exploit will work without OP losing data, since they can skip unlocking the bootloader.
All you should have to do, OP, is download a custom recovery and root zip, put your device into fastboot, and then run fastboot flash recovery <path-to-recovery-img>, then flash your root zip.
Rirere said:
You certainly should be wiping between ROM flashes, but keep in mind that OP's bootloader is already unlocked. At this point, more or less any root exploit will work without OP losing data, since they can skip unlocking the bootloader.
All you should have to do, OP, is download a custom recovery and root zip, put your device into fastboot, and then run fastboot flash recovery <path-to-recovery-img>, then flash your root zip.
Click to expand...
Click to collapse
Edit: Tried that one-click root that was referenced earlier, didn't work.
It hung up on "daemon started successfully," for like, 10 minutes before I stopped.
It can't be that it doesn't see my tablet, so.
I'm trying it again right now, but I doubt it'll do anything.
Drivers.
Sent from my Nexus 7 using xda premium
graydiggy said:
Drivers.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
NOPE.
No root access, Superuser fails to gain it to update it's binary...
BUT.
I go into the Terminal Emulator, type "su," and it sends back a #, which signifies that I have this thing Rooted, as shown here:
{
"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"
}
Edit: Left the Checker running, and it says, after all this BS, that I don't have proper root access...
{
"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"
}
(Credits to @Disturbed™ for the awesome picture!)
I saw this on another part of the forum, so I thought I might as well expand it here! Credits to @malybru for inspiration and help!
Useful links will be in the 2nd post.
Personal recommendations will be in the 3rd post.
BEFORE POSTING ANYTHING, PLEASE READ THIS:
BEGINNER'S GUIDE AND FORUM RULES
YOU ARE FREE TO ASK ANY QUESTIONS ON THIS THREAD! I WILL TRY TO PROVIDE AN ANSWER OR I WILL DO MY BEST TO PUT YOU ON THE RIGHT TRACK! THERE IS NO ABUSE OR FLAMING TO NOOBS/NEWBS HERE!
Always remember to search before posting! There most likely is SOMEONE out there with a similar problem to yours!Make sure that you have a SPRINT SAMSUNG GALAXY S4. If you do not, you are in the wrong section of the forum! Try out this link and see which model you have and add it to your signature - Useful Signatures
There are other variants of the Galaxy S4 here:
International GS4 (Help Thread)
T-Mobile GS4 (Help Thread)
Verizon GS4
AT&T GS4
South Korean Help Thread
Please hit the Thanks button if I (or anyone else) helped you out!
Also, I don't take credit for ANY of the links I have posted! They are all from the helpful developers of XDA and the moderators!
MY STORY:
So I was also a newb at one point (weren't we all), and I really didn't know who to go too. XDA came into my life and I was so happy. The problem, however, is that sometimes the terminology and that "new person" feeling was making me feel on edge. That, however, was a while ago. I know a lot more, but I wanted to make this thread to try and help out some of the newer people who are entering the Android world.
[NOOB FRIENDLY] SPH-L720 Questions Thread - ALL Are Welcome!
Quick update guys...
09/09/2013
So as many of you know, school has started and I've hit the books. I barely get any time for XDA (which I am very, very sorry for!), so I won't be updating as often. I will try to update as much as I can, but with a pretty rough schedule this year, I'll see what I can do.
[NOOB FRIENDLY] SPH-L720 Questions Thread - ALL Are Welcome!
Here are some quick useful links that you can use!
Link to Galaxy S4 root - Galaxy S4 Root HOW TO
Stock Firmware - Stock Firmwares
Directory of *almost* every mod, tweak, ROM and Kernel for Sprint Galaxy S4 - Roms/Kernels/Recoveries/Mods/Themes/Games/Apps
WiFi Hotspot Mod - Hotspot Mod
Consumer Guide - Sprint S4 User Guide
*Will add more as things continue to develop!*
I have a question about kernels I want to get a new kernel but if I don't like the new one how would I go back to the old one
Sent from my SPH-L720 using xda app-developers app
Glad to see someone had the guts to start this thread.
I too, for one, get tired of the condescending attitude of people who forget that they were once noobs.
Congrats!
danzelcool said:
I have a question about kernels I want to get a new kernel but if I don't like the new one how would I go back to the old one
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Easiest way is to do a backup before flashing any kernel, rom, or mod. Then you can always revert should there be an issue or problem.
Sent from my SPH-L720 using Tapatalk 4 Beta
MF9 hotspot mod issues
I was running rooted MDL on my sprint gs4 but wanted to update to MF9 so i unrooted then updated to stock MF9 i then used cfautoroot to root the stock MF9 which worked just fine.... i attempted the hotspot mod using the odexed MF9 "system.jar" and "system.odex" files then did a reboot.....the replaced files soft bricked my phone....it was stuck on the sprint splash screen it would not go any further....i had to re-flash back to stock MDL to get my phone booted up again....I'm not sure what the issue is with the MF9 hotspot mod because the MDL hotspot mod works like a charm. If anyone has any insight into this problem all help would be greatly appreciated....because i would much rather be updated to the latest software but i still need my hotspot feature to work
twisclone said:
I was running rooted MDL on my sprint gs4 but wanted to update to MF9 so i unrooted then updated to stock MF9 i then used cfautoroot to root the stock MF9 which worked just fine.... i attempted the hotspot mod using the odexed MF9 "system.jar" and "system.odex" files then did a reboot.....the replaced files soft bricked my phone....it was stuck on the sprint splash screen it would not go any further....i had to re-flash back to stock MDL to get my phone booted up again....I'm not sure what the issue is with the MF9 hotspot mod because the MDL hotspot mod works like a charm. If anyone has any insight into this problem all help would be greatly appreciated....because i would much rather be updated to the latest software but i still need my hotspot feature to work
Click to expand...
Click to collapse
I would suggest you to take a look here: MF9 Hotspot Mod
I have a question too, actually.
Flashing to a new kernel is the same way as flashing a ROM, right? I heard that you need to fix permissions, but some say you shouldn't...
So after flashing to a new kernel, is fixing permissions required?
twisclone said:
I was running rooted MDL on my sprint gs4 but wanted to update to MF9 so i unrooted then updated to stock MF9 i then used cfautoroot to root the stock MF9 which worked just fine.... i attempted the hotspot mod using the odexed MF9 "system.jar" and "system.odex" files then did a reboot.....the replaced files soft bricked my phone....it was stuck on the sprint splash screen it would not go any further....i had to re-flash back to stock MDL to get my phone booted up again....I'm not sure what the issue is with the MF9 hotspot mod because the MDL hotspot mod works like a charm. If anyone has any insight into this problem all help would be greatly appreciated....because i would much rather be updated to the latest software but i still need my hotspot feature to work
Click to expand...
Click to collapse
I did the exact same thing, but it worked perfectly the only thing. I'm not sure what mod caused it xposed,prl enabler, probably one of these that made my phome so slow to boot. It takes twice as long as before. Anyway, I'm guessing you probably downloaded the incorrect file.
I've heard several cases where the new mf9 update reduces boot speed.
Sent from my SPH-L720
Alright, here goes:
I am rooted (TWRP Recovery which I boot to through Goo Manager), SuperSU, Rom Toolbox, Adblock Plus, Hotspot Mod.
I achieved root via CF-Autoroot a while back, pre-MF9 update. As such, I am still running on MDL.
Now, let's assume I wanted to update to MF9 and then install an MF9-based ROM.
I'm a bit confused as to the steps. I think they go something like:
1) Uninstall any Root only apps (or move them somewhere? freeze? something else?)(And I can't very well remove SuperSu or TWRP Recovery can I?)
2) Boot into recovery and do a factory wipe?
3) Move the OTA update file back from SD card to /cache.
4) Unroot (no idea how to safely do this)
5) Install OTA update.
6) Re-root (does the method change with MF9? If so, what do I need to do?)
7) Flash Rom via recovery (which installs as part of the rooting process, right?)
8) If necessary, install any SU apps not otherwise baked into my newly selected rom.
Is that about right? And can you clarify the specific execution of some of the above steps, as inquired about parenthetically?
I appreciate your help in advance (though I certainly understand, given that I am asking a bunch of questions, thus requiring a fairly substantial reply) if you don't wind up answering.
ok first of all i have a t mobile s4, i got a used s4 for my girl but she has sprint how do i deleted the info from the other person in the setting/more/about devise/ status/user name and phone number ,i rooted format all ,data cache ,dalvik put 3 different roms ,and it keeps showing the other person info and number is there other thing im missing?
walliester said:
ok first of all i have a t mobile s4, i got a used s4 for my girl but she has sprint how do i deleted the info from the other person in the setting/more/about devise/ status/user name and phone number ,i rooted format all ,data cache ,dalvik put 3 different roms ,and it keeps showing the other person info and number is there other thing im missing?
Click to expand...
Click to collapse
Sounds like the phone was never activated in your girls name and it is still under the previous owners info. You can't wipe that away. You need to switch the user info by calling Sprint, sounds like you were scammed and you are going to have a phone with a bad ESN that cannot be used. Good luck.
Sent from my Sprint Galaxy S4 using Tapatalk 2
---------- Post added at 08:33 PM ---------- Previous post was at 08:32 PM ----------
GiantJay said:
Sounds like the phone was never activated in your girls name and it is still under the previous owners info. You can't wipe that away. You need to switch the user info by calling Sprint or getting a hold of the previous owner to deactivate it in their name. Sounds like you were scammed and you are going to have a phone with a bad ESN that cannot be used. Good luck.
Sent from my Sprint Galaxy S4 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my Sprint Galaxy S4 using Tapatalk 2
beerindex said:
Alright, here goes:
I am rooted (TWRP Recovery which I boot to through Goo Manager), SuperSU, Rom Toolbox, Adblock Plus, Hotspot Mod.
I achieved root via CF-Autoroot a while back, pre-MF9 update. As such, I am still running on MDL.
Now, let's assume I wanted to update to MF9 and then install an MF9-based ROM.
I'm a bit confused as to the steps. I think they go something like:
1) Uninstall any Root only apps (or move them somewhere? freeze? something else?)(And I can't very well remove SuperSu or TWRP Recovery can I?)
2) Boot into recovery and do a factory wipe?
3) Move the OTA update file back from SD card to /cache.
4) Unroot (no idea how to safely do this)
5) Install OTA update.
6) Re-root (does the method change with MF9? If so, what do I need to do?)
7) Flash Rom via recovery (which installs as part of the rooting process, right?)
8) If necessary, install any SU apps not otherwise baked into my newly selected rom.
Is that about right? And can you clarify the specific execution of some of the above steps, as inquired about parenthetically?
I appreciate your help in advance (though I certainly understand, given that I am asking a bunch of questions, thus requiring a fairly substantial reply) if you don't wind up answering.
Click to expand...
Click to collapse
For 1&4:
Also, you can remove root access if you would like too! In superSU, there is an option to unroot the phone in the settings area. As for recovery, I would NOT remove TWRP if I were you. If anything were to happen to your phone, you could use TWRP to restore it. Speaking of that, MAKE SURE you back up your data! Must people recommend nandroid, but I find TWRP back up to be just as good.
For 2:
TWRP gives you an option to wipe your data. When you but recovery, just go into wipe. A screen will pop up and will ask you to slide the slider to confirm the back up. You will lose your data, but it will get any updating/ROM issues resolved.
For 5&6:
I would recommend reading this! http://forum.xda-developers.com/showthread.php?t=2277480
For 7:
You don't need to flash any ROM if you're running on stock (stock means you're running the ROM that came with the device)
For 8:
Make sure you double check with the compatibility of everything you install! Some things are not ready for mf9, so be cautious!
Just hit the thanks if I helped at all!
Sent from my SPH-L720
beerindex said:
Alright, here goes:
I am rooted (TWRP Recovery which I boot to through Goo Manager), SuperSU, Rom Toolbox, Adblock Plus, Hotspot Mod.
I achieved root via CF-Autoroot a while back, pre-MF9 update. As such, I am still running on MDL.
Now, let's assume I wanted to update to MF9 and then install an MF9-based ROM.
I'm a bit confused as to the steps. I think they go something like:
1) Uninstall any Root only apps (or move them somewhere? freeze? something else?)(And I can't very well remove SuperSu or TWRP Recovery can I?)
2) Boot into recovery and do a factory wipe?
3) Move the OTA update file back from SD card to /cache.
4) Unroot (no idea how to safely do this)
5) Install OTA update.
6) Re-root (does the method change with MF9? If so, what do I need to do?)
7) Flash Rom via recovery (which installs as part of the rooting process, right?)
8) If necessary, install any SU apps not otherwise baked into my newly selected rom.
Is that about right? And can you clarify the specific execution of some of the above steps, as inquired about parenthetically?
I appreciate your help in advance (though I certainly understand, given that I am asking a bunch of questions, thus requiring a fairly substantial reply) if you don't wind up answering.
Click to expand...
Click to collapse
You don't have to Unroot to update to MF9. Follow this: http://forum.xda-developers.com/showthread.php?t=2357471
Its a little complicated but you will learn a ton and everything after will be easy
With ROMs like blue Kuban that have a hacked hotspot, do you have to install a third party hotspot app or can you just use the toggle they provide to turn on hotspot without being charged from Sprint?
FlyHighCrue said:
With ROMs like blue Kuban that have a hacked hotspot, do you have to install a third party hotspot app or can you just use the toggle they provide to turn on hotspot without being charged from Sprint?
Click to expand...
Click to collapse
Not sure about Blue Kuban but, the normal hack doesn't require a 3rd party app.
You do want to be careful about not over doing it on your data plan.
Salil999 said:
I have a question too, actually.
Flashing to a new kernel is the same way as flashing a ROM, right? I heard that you need to fix permissions, but some say you shouldn't...
So after flashing to a new kernel, is fixing permissions required?
Click to expand...
Click to collapse
Fixing permissions never hurts anything...
ObrienDave said:
Not sure about Blue Kuban but, the normal hack doesn't require a 3rd party app.
You do want to be careful about not over doing it on your data plan.
Click to expand...
Click to collapse
Well I have unlimited data I just don't have a plan for hotspot.
Hi guys this method works with any version. Very easy to follow.
I have done the following:
1) Unlock bootloader (first make a backup).
2) Download SuperSu.zip and copy in memory. (Last version http://download.chainfire.eu/supersu)
3) Download fastboot.rar and extract. (fastboot.rar inlcudes boot.img (doomkernel) for flash).
4) Place fastboot folder in C:
5) Open cmd (from start) and go to C:/fastboot
6) Plug phone in fastboot mode (shoutdown and press Vol + and plug usb).
7) In cmd write "fastboot flash boot boot.img" at the end "fastboot reboot".
8) Enter in recovery pressing vol + or vol - when phone booting and led is coloured.
9) Flash supersu.zip. Unplug usb.
10) After go in advanced and shoutdown phone (NOT RESTART).
11) Flash ONLY stock kernel of your firmware with flashtool. Reboot.
12) Relock bootloader.
Fastboot.rar
https://mega.co.nz/#!U5pkQQ6T!5YAVu3VOwpTSg-WH5aE6djJOKF3ilfg_R-JEBoJ25cM
Sorry for my bad english.
I did everything in less than 10 minutes.
This is a guide made by me. Then tested and working also with last 4.3 10.4.1.B.0.101.
Useful, but somebody already made a very similar guide -
http://forum.xda-developers.com/showthread.php?t=2590781
Sent from my C6603 using Tapatalk
you forget to put backup TA step I think. Because without restoring TA, the low-light camera quality will be reduced.
Somehow between step 10 and 11 my phone automatically rebooted while I getting ready to flash the stock kernel. Maybe I wasn't in the right mode and plugged / unplugged the USB cable. Either way, my phone restarted when I didn't intend it to. I believe when this happened my phone was reset to like-new.
I did lose all data / settings / etc. The backup and restore functionality of the Sony PC Companion seems to be crap in this situation and I'm not sure just what might be useful about it.
Just an FYI to others who might try this.
colacin said:
Somehow between step 10 and 11 my phone automatically rebooted while I getting ready to flash the stock kernel. Maybe I wasn't in the right mode and plugged / unplugged the USB cable. Either way, my phone restarted when I didn't intend it to. I believe when this happened my phone was reset to like-new.
I did lose all data / settings / etc. The backup and restore functionality of the Sony PC Companion seems to be crap in this situation and I'm not sure just what might be useful about it.
Just an FYI to others who might try this.
Click to expand...
Click to collapse
AFAIK unlocking the bootloader factory-resets the phone. making and restoring a backup, including TA, should be step 0 and 13
colacin said:
Somehow between step 10 and 11 my phone automatically rebooted while I getting ready to flash the stock kernel. Maybe I wasn't in the right mode and plugged / unplugged the USB cable. Either way, my phone restarted when I didn't intend it to. I believe when this happened my phone was reset to like-new.
I did lose all data / settings / etc. The backup and restore functionality of the Sony PC Companion seems to be crap in this situation and I'm not sure just what might be useful about it.
Just an FYI to others who might try this.
Click to expand...
Click to collapse
Unplug USB and when you flashed supersu.zip you had to turn off the phone from recovery.
Then go to step 11
Coirpre said:
AFAIK unlocking the bootloader factory-resets the phone. making and restoring a backup, including TA, should be step 0 and 13
Click to expand...
Click to collapse
I unlock bootloader with flashtool and I do not lose anything.
When restores TA partition is not made no wipe.
kingvortex said:
Useful, but somebody already made a very similar guide -
http://forum.xda-developers.com/showthread.php?t=2590781
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Similar not equal.
Please stop this unlocked bootloader root posts, they are useless.
If you got unlocked bootloader you can root when ever you want, that is not a talent.
If you got any solution for locked bootloader, then speak, or remain your silence...
Sent from my C6603 using Tapatalk
eryen said:
Please stop this unlocked bootloader root posts, they are useless.
If you got unlocked bootloader you can root when ever you want, that is not a talent.
If you got any solution for locked bootloader, then speak, or remain your silence...
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
I don't think the OP was claiming any particular talent - this is simply a step-by-step guide - and there are countless other posts of this sort for various other purposes. Sure, he could have put UNLOCKED BOOTLOADER in the title and that way you wouldn't have read it.
eryen said:
Please stop this unlocked bootloader root posts, they are useless.
If you got unlocked bootloader you can root when ever you want, that is not a talent.
If you got any solution for locked bootloader, then speak, or remain your silence...
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
If you want to follow the guide, good. Then nothing. I have done some work to help the forum. If you unlock the bootloader after you relock. It took me 10 minutes to do all this. For unlock andrelock takes 2 minutes.
I do this to also help users to root their phone.
At the end of unlocking the bootloader will not void your warranty if you re-lock at the end of the guide.
I could agree with you if you were a moderator.
Are you a home user who wants to increase their own posts on the forum.
Please do not offend people who want to help the forum. Thank you.
colacin said:
I don't think the OP was claiming any particular talent - this is simply a step-by-step guide - and there are countless other posts of this sort for various other purposes. Sure, he could have put UNLOCKED BOOTLOADER in the title and that way you wouldn't have read it.
Click to expand...
Click to collapse
Thanks.
First, nobody needs to be a moderator to comment on a thread/post. This is the second time I've seen someone say this in 24 hours. It's a strange attitude.
Having said that, I've some suggestions to make -
1. Change your thread title to reflect that an unlocked bootloader is required.
2. Remove the part where you say that data will not be lost, as unlocking the bootloader wipes data and sdcard. This is quite important, as it seems somebody already lost their data following this guide.
3. You should mention that DRM keys should be backed up by backing up the TA partition before unlocking the bootloader to prevent their permanent loss and loss of warranty.
http://forum.xda-developers.com/showthread.php?t=2292598
4. Linking to the thread or at least crediting the creator of whichever boot.img you're using would also be polite or indeed essential.
5. A direct link to Chainfire's site, where the latest version of SuperSu is available would be better than attaching whatever version you have lying around, as security fixes may be made at any time.
http://download.chainfire.eu/supersu
Sent from my C6603 using Tapatalk
kingvortex said:
First, nobody needs to be a moderator to comment on a thread/post. This is the second time I've seen someone say this in 24 hours. It's a strange attitude.
Having said that, I've some suggestions to make -
1. Change your thread title to reflect that an unlocked bootloader is required.
2. Remove the part where you say that data will not be lost, as unlocking the bootloader wipes data and sdcard. This is quite important, as it seems somebody already lost their data following this guide.
3. You should mention that DRM keys should be backed up by backing up the TA partition before unlocking the bootloader to prevent their permanent loss and loss of warranty.
http://forum.xda-developers.com/showthread.php?t=2292598
4. Linking to the thread or at least crediting the creator of whichever boot.img you're using would also be polite or indeed essential.
5. A direct link to Chainfire's site, where the latest version of SuperSu is available would be better than attaching whatever version you have lying around, as security fixes may be made at any time.
http://download.chainfire.eu/supersu
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
1) ok.
2) I myself have done everything ... and I have not lost ANYTHING. was wrong in the user process. It is not my fault.
3) I think it was a logical thing.
4) DooMkernel.
5) thank you.
6) I will never do anything to help this forum. I know it will not matter anything to anyone, but a small contribution had a lot to me.
I have in no way lessened your contribution by what I posted, neither did I intend to. As you will see, I already said your post was useful. They were simply suggestions to make your guide better. No need to get upset about it.
As for not losing data, I'm sorry, but you're wrong about this. Unlocking the bootloader on this device wipes both /data and the internal SD card. There was no user error.
See the warning in DooMLoRD's guide - http://forum.xda-developers.com/showthread.php?t=2153261
Please just remove the part that falsely states that data will not be lost or I'll have to ask a moderator to do it as it's not fair on inexperienced users that may lose their data when following this guide.
No malice intended, only the intention of correct information being posted.
By their very nature, guides are followed by less experienced users, so the information in them must be correct and complete. Even if backing up DRM keys is a logical step to you, a new user may not even know about it.
Sent from my C6603 using Tapatalk
Ok first off, if you haven't anything constructive to say then don't say anything at all. Users helping other users is what makes XDA a pleasant place for developers and users alike.(this is not directed at the OP)
Also I have added a warning about data being wiped when unlocking the bootloader to the OP.
A backup is required as unlocking the bootloader on this device wipes both /data and the internal SD card
@djnino4style, @kingvortex was only making suggestions to help this thread and you, if it was criticism it was constructive. We do appreciate guides which could help new users so do not think we are getting at you.
Thanks again,
wedgess said:
Ok first off, if you haven't anything constructive to say then don't say anything at all. Users helping other users is what makes XDA a pleasant place for developers and users alike.
Also I have added a warning about data being wiped when unlocking the bootloader to the OP.
A backup is required as unlocking the bootloader on this device wipes both /data and the internal SD card
@djnino4style, @kingvortex was only making suggestions to help this thread and you, if it was criticism it was constructive. We do appreciate guides which could help new users so do not think we are getting at you.
Thanks again,
Click to expand...
Click to collapse
Ok delete this thread. Thanks.
djnino4style said:
Ok delete this thread. Thanks.
Click to expand...
Click to collapse
I think you misunderstand my intentions and the moderator's post above.
Nobody is getting at you here. My posts are simply constructive criticism intended to make your guide more complete. Nothing more.
Nobody is saying that your guide is no good or that it needs to be closed or removed.
Put simply; chill out, friend.
{
"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"
}
kingvortex said:
I think you misunderstand my intentions and the moderator's post above.
Nobody is getting at you here. My posts are simply constructive criticism intended to make your guide more complete. Nothing more.
Nobody is saying that your guide is no good or that it needs to be closed or removed.
Put simply; chill out, friend.
Click to expand...
Click to collapse
Words of wisdom as always @kingvortex
Thanks. I try my best hahaha.
thanks buddy. its a;; thanks to you,doomlord androxyde i have succesfully rooted my device...
thanks...
The problem with this thread is that they mention it's a root methods for Xperia z 4.3, and they are talking of backing up TA partion which is not possible without rooting the device. In that case you will have to downgrade to 4.1 or 4.2.
Dear it's not possible till now to back up TA partition in uprooted 4.3' so useless step.
If you want to root 4.3, u must downgrade otherwise u gonna loose TA partition and hence, warranty, dry keys, ba2 forever. Never think of recovering these and relocation,
So please correct the title or make suggestion to downgrade.
I've got a Verizon Note 3 now with the NC4 ota on it already. I need root. Not want need. I use my hotspot religiously. Tried towel root. Busy box wont install because of superuser permissions. I uninstalled all of them etc.. Nothing.. Factory reset my phone. Towelroot'd again. Then busybox. same message. "there was a problem opening a shell with root access. This is either being caused by a superuser/supersu or by a device that is inproperly rooted. Try removing superuser permissions, uninstalling this app reinstalling this app then regranting permissions. Well After rooting a factory reseted nc4 with towel root busybox showed this. So then i proceded to supersu. Tries to install shows option to disable knox fails. Installed superuser and tried to update binary, failed and crashed superuser.
Ever phone i've had has been rooted. thunderbolt/s3/n2/s4.. the note 3 has became the b*tch of the family that doesnt want to listen. Please help. I feel these threads overpopulate the forums but i've tried multiple times. given up waited a few months and tried again. This being my fourth attempt owning the phone im to the point where i want to give up and get my old s4 back.. So please help me with any information you can give.
Thanks
edit: yeah signature is old.. havent been on in a while sorry.
clark707 said:
I've got a Verizon Note 3 now with the NC4 ota on it already. I need root. Not want need. I use my hotspot religiously. Tried towel root. Busy box wont install because of superuser permissions. I uninstalled all of them etc.. Nothing.. Factory reset my phone. Towelroot'd again. Then busybox. same message. "there was a problem opening a shell with root access. This is either being caused by a superuser/supersu or by a device that is inproperly rooted. Try removing superuser permissions, uninstalling this app reinstalling this app then regranting permissions. Well After rooting a factory reseted nc4 with towel root busybox showed this. So then i proceded to supersu. Tries to install shows option to disable knox fails. Installed superuser and tried to update binary, failed and crashed superuser.
Ever phone i've had has been rooted. thunderbolt/s3/n2/s4.. the note 3 has became the b*tch of the family that doesnt want to listen. Please help. I feel these threads overpopulate the forums but i've tried multiple times. given up waited a few months and tried again. This being my fourth attempt owning the phone im to the point where i want to give up and get my old s4 back.. So please help me with any information you can give.
Thanks
edit: yeah signature is old.. havent been on in a while sorry.
Click to expand...
Click to collapse
Make sure usb debugging is enabled. then retry towel root
RomsWell said:
Make sure usb debugging is enabled. then retry towel root
Click to expand...
Click to collapse
Enabled USB debugging. Uninstaller Chinese superuser crap. Install supersu from play store. Try to update. Failed knox.
clark707 said:
Enabled USB debugging. Uninstaller Chinese superuser crap. Install supersu from play store. Try to update. Failed knox.
Click to expand...
Click to collapse
Go back to towelroot. After rooting use a root checker to verify root. Don't worry about updating SU Binaries or disabling Knox, if you are planning to flash a custom rom this will all get taken care of as pretty much every rom has done this for you, you should still be able to grant permissions without updating. If the busybox app you are using doesn't work, try another one, the one I always use is created by a Steven something (can't remember last name).
If you are not going to flash a custom rom follow the instructions in the 3rd post found here.
kinstre11 said:
Go back to towelroot. After rooting use a root checker to verify root. Don't worry about updating SU Binaries or disabling Knox, if you are planning to flash a custom rom this will all get taken care of as pretty much every rom has done this for you, you should still be able to grant permissions without updating. If the busybox app you are using doesn't work, try another one, the one I always use is created by a Steven something (can't remember last name).
If you are not going to flash a custom rom follow the instructions in the 3rd post found here.
Click to expand...
Click to collapse
alright. UNinstalled everything and reinstalled towel root. Ran towelroot no errors. downloaded root tester and no root access. The busybox I download is the first one that comes up by Stephen. Still gives me the same error.
Something is wrong with superuser. I UNinstalled them all and I've tried them all. Superuser by chains fails to download manifest. Busybox X says no root or bad superuser.idk what to freaking do its pissing me off
clark707 said:
alright. UNinstalled everything and reinstalled towel root. Ran towelroot no errors. downloaded root tester and no root access. The busybox I download is the first one that comes up by Stephen. Still gives me the same error.
Click to expand...
Click to collapse
Just to make sure, you did install SuperSU prior to running root checker? Permissions are required to verify root.
If so, I would reflash the stock firmware via Odin and start over. The firmware file can be found here. After flashing through Odin boot into recovery and factory reset/wipe cache. Then try rooting again, make sure you have the latest towelroot.
kinstre11 said:
Just to make sure, you did install SuperSU prior to running root checker? Permissions are required to verify root.
If so, I would reflash the stock firmware via Odin and start over. The firmware file can be found here. After flashing through Odin boot into recovery and factory reset/wipe cache. Then try rooting again, make sure you have the latest towelroot.
Click to expand...
Click to collapse
For an obvious answer I just did towelroot then root checker. Because none of the super users work.. and I'll have to do that when I get off work tonight. Would prefer a different route though.
{
"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"
}
clark707 said:
For an obvious answer I just did towelroot then root checker. Because none of the super users work.. and I'll have to do that when I get off work tonight. Would prefer a different route though.
Click to expand...
Click to collapse
As I tried to say before, you don't need to update the binaries for SuperSU to do its job. Just install it, don't worry about opening it or trying to disable Knox. Something about NC4 OTA doesn't like rooting as Verizon continues to try to lockdown our phones as much as they can.
ATM, Towelroot is the best root method I know of as it is a one click method that works, I haven't seen anywhere on these forums that it has failed for our device short of users missing some important link in the chain. I haven't tried kingo or the chinese version of rooting since being on KitKat so I don't know if they work on the current firmware nor have I seen anyone talking about them since Towelroot was discovered for our device.
Steps to successful root, busybox, safestrap, custom rom are in the second post of this thread. My only addition to the steps would be to install a switch user app (i.e. SuperSU) in between Steps 1 & 2. You can switch out any 4.4 rom for the Stock rom provided by BeansTown106 as long as you make sure to flash the NC2 kernel in the appropriate step. The only exception would be if you are planning on using Jasmine Rom as hsbadr has recently rebuilt his 2 versions on the NC4 kernel, in which case you don't need to do anything special, simply flash via Safestrap following the instructions in his OP. (I apologize if you already understand all this, just trying to be thorough so we don't have to keep going back and forth).
Alright well with just supersu installed and towellroot ran busy box fails each time.
These are the steps I took with a fresh factory reset. USB debugging. Towelroot install supersu install busy box run busybox get that error I showed above. Rage quit.
Interesting enough this busy box installer shows that my phone has root but fails to install busybox
clark707 said:
These are the steps I took with a fresh factory reset. USB debugging. Towelroot install supersu install busy box run busybox get that error I showed above. Rage quit.
Interesting enough this busy box installer shows that my phone has root but fails to install busybox
Click to expand...
Click to collapse
At this point I don't know what else to try other than reflashing the stock firmware via Odin and starting again.
kinstre11 said:
At this point I don't know what else to try other than reflashing the stock firmware via Odin and starting again.
Click to expand...
Click to collapse
I'm gonna try this later tonight.
kinstre11 said:
At this point I don't know what else to try other than reflashing the stock firmware via Odin and starting again.
Click to expand...
Click to collapse
Worked!!
Root [X]
Busybox [X]
Safestrap [X]
In the process of downloading jasmine's port from the s5 on my phone so i can set up a partition for it. Never really used safestrap so this is a new world for me. Any advice is much welcomed!
clark707 said:
Worked!!
Root [X]
Busybox [X]
Safestrap [X]
In the process of downloading jasmine's port from the s5 on my phone so i can set up a partition for it. Never really used safestrap so this is a new world for me. Any advice is much welcomed!
Click to expand...
Click to collapse
Only use the stock slot, there are problems with battery drain and other things on rom slots.
kinstre11 said:
Only use the stock slot, there are problems with battery drain and other things on rom slots.
Click to expand...
Click to collapse
Wait wouldn't using the stock slot be dangerous? And I'm coming across another problem. Every rom in the forums I try does not boot up accept for jasmine rom 2.3 I'd like to use a different rom but it's not liking me lol. But it's safe to flash a rom in the stock slot? If so I'll have jasmine in slot one as a backup. Battery drain is outrageous. Even with zero lemons 10,000 nah battery it blows through it.
clark707 said:
Wait wouldn't using the stock slot be dangerous? And I'm coming across another problem. Every rom in the forums I try does not boot up accept for jasmine rom 2.3 I'd like to use a different rom but it's not liking me lol. But it's safe to flash a rom in the stock slot? If so I'll have jasmine in slot one as a backup. Battery drain is outrageous. Even with zero lemons 10,000 nah battery it blows through it.
Click to expand...
Click to collapse
Using the stock slot isn't really dangerous... You can always boot into download mode and reflash the stock rom with Odin. You will need the unified Kitkat kernel with most roms. And each rom should have instructions including flashing it at some point.
sardonicpriest said:
Using the stock slot isn't really dangerous... You can always boot into download mode and reflash the stock rom with Odin. You will need the unified Kitkat kernel with most roms. And each rom should have instructions including flashing it at some point.
Click to expand...
Click to collapse
I kinda understand, what if I flash jasmine 2.3 s5 port for stock
clark707 said:
I kinda understand, what if I flash jasmine 2.3 s5 port for stock
Click to expand...
Click to collapse
I would recommend using 2.4.1 instead, it is a more recently updated version of the S5 port. I believe you can flash the unified kernel in Odin before you install the rom (as long as you are already running Kitkat, otherwise wait until you have a Kitkat rom installed). As for 2.3, I don't remember if it needed the unified kernel, but it shouldn't hurt anything to use it anyways on Jasmine roms. If you do go with 2.3 I would look into the patches (2.3.1 - 2.3.4 i think) for stability/bug fixes, although I am not sure if they all need to be flashed or just the last one as I never used 2.3 (I am happily using 1.9 lol).
Does anyone have the current link for downloading TR v3? I can't seem to find it, and I am debating picking up a note 3 in place of my S5...