Related
Sorry for the wall of text and for being a total noob and thank you for all your help !
So I've been researching all night (read the wiki to no avail too; so please don't simply direct me there) and I have some unanswered noob rooting questions questions and need general reassurance...
Basically I want is full and lasting root permissions on FRG83D 2.2.1 so I can remove system apps (twitter, amazon, etc...) through terminal commands and MAYBE a unlocked boot loader to flash a custom recovery image (Amon_RA) so I can make full nandroid backups.
1) It seems to me that unlocking the bootloader is a more flexible and permanent way to achieve root, as opposed to other '1-click' type methods in the face of firmware updates (2.3...), which would just disable root and it might not be re-achievable till another exploit is found whereas with an unlocked bootloader I can flash w/e I want?
2) Is it possible to enable root and use terminal on my n1 without some "superuser.apk" program? In order to do this would I use an insecure superboot and manually deploy SU?
3) How can I make a backup before rooting if I'm not rooted? I've been using my device for 8 months so there's a lot of stuff on there...
3a) If I can't make a full backup where can I find signed stock recovery images and boot images or updates zips so I can reflash them if I need to?
4) I believe if I superboot.img and leave everything (ROM and Recovery) stock will I still be able to receive and install OTA updates...?
4a) Can someone explain the difference between himem with updated wifi driver and not? I think himem removes permanent virtual address mapping so memory can be used for running applications. Asides from having more memory what are the tangible benefits or downsides to this? Would it make the system faster?Would I be able to multitask more apps before the system quits some because of lacking resources? Would the use of this extra memory inhibit system processes because there is no longer its own personal memory map?
4b) Will installing OTA updates remove root permission? If so, would simply flashing superboot.img re-grant me those permissions? But it would seem I need an updated superboot.img for the appropriate newer build(?). Is the development of superboot images still active and timely?
5) How important are OTAs and the stock recovery image? It would seem if I'm going to do any system moding (even just removing twitter/amazon) I should have a full and function Nandroid backup and would therefor need a custom recovery image- at the sake of missing OTAs (not important mainly because applying them would disable root etc anyway?)?
6) With root permissions and stock everything do I have to worry about manual baseband and radio updates? What about with a custom recovery image?
7) Apps2SD+ doesn't work with stock roms period and I would need a compatible custom rom?
Thanks again.
actually you can flash a recovery image without unlocking boot loader
1. Unlocking bootloader voids warranty and it is the official way to offer you the ability to install third-party roms.
You may get root without unlocking bootloader if you're using an old build. I think there are ways to root frg91 and frg83 without unlocking boot loader), then after you get root, you flash a recovery image, and then install whichever Rom you like. Don't bother with those official release, there will always be someone to release a rooted 2.3 rom.
2. not sure but from security's point of view it's better to have super user GUI program, because not all applications should get root
3. don't know sorry
4. Yes, there are lots of people revert back to stock ROM just for getting next OTA.
4a. I personally have never ran out of memory on my Nexus One, I do want to multi task as much as possible, however no matter how I set low mem killer, Android still automatically kills apps according to oom value (or something like that)
4b. If you get a successful OTA then definitely root is removed, and probably your recovery will revert to stock recovery too, thus you have to re-root..
5. I'd suggest to wait for someone to mod OTA 2.3 to make it rooted, then you flash the rom through recovery.
6. You can freely upgrade baseband (it's radio, the same thing) when you have a custom recovery.
7. There are mainly two ways to App2SD, one is Froyo implementation which works with stock Froyo rom, another way is to use App2Ext which requires root.
houzuoguo pretty much summed it up. I'll add what I can.
3) There is backup software in the market that can backup data without root, although it is not as powerful or thorough as the apps that require root.
3a) You can go back to a stock ROM. I believe there is a sticky round here of ROMs that has some stock ROMs in it. I know someone with a N1 that flashed a CM ROM, didn't like it, flashed a stock ROM, and got the OTA afterwards.
5) Even before an OTA is pushed there are ROMs floating around with the latest and greatest. After the OTAs are pushed you see a lot of very good, stable ROMs based off of them with all features working properly. You can do more with the custom ROMs and recovery images than you could ever do with the stock stuff.
7) DarkTremor's Apps2SD script will not only give you better A2SD than what is built into Froyo but it will give you a few more very useful terminal commands that I can't live without. Good stuff.
hi everyone! i just had my nexus one. i bought it from someone and i don't know if it's already rooted or not. Im already on FRG83D 2.2.1.
1.How do I know that my fone is already rooted?
2.Where can i download the stock ROM just in case the fone crashes and i want to revert?
proteus665 said:
hi everyone! i just had my nexus one. i bought it from someone and i don't know if it's already rooted or not. Im already on FRG83D 2.2.1.
1.How do I know that my fone is already rooted?
2.Where can i download the stock ROM just in case the fone crashes and i want to revert?
Click to expand...
Click to collapse
1. Check if there's application named 'superuser'. Or install any terminal emulator; run it, type 'su'.
**Please make your own thread next time.....
LFact said:
**Please make your own thread next time.....
Click to expand...
Click to collapse
Why?
Sent from my Nexus One using XDA App
Thanks guy!
I think I'm going to superoneclick to get root; back up with titanium and remove the system apps I don't want.
From there I'll be able to flash a custom recovery if I want to get more custom.
I'm probably going to wait till 2.3 comes out cause it's right around the corner; Or did they fix the superoneclick exploit in 2.3...?
Also, doesn't Apps2ext require a custom rom that supports it? i.e. it wouldn't work if I had root and was running a stock rom anyway?
I'm not sure if I'm posting this in the right section, this is my first question. So I decided to finally root my nexus one, mostly to take advantage of the newly integrated wi-fi calling feature in the new cyanmod. i was able to unlock it through fastboot, it now shows the lock when the phone boots up, but it doesnt appear to be unlocked. apps requiring root like rom manager, setcpu, etc. don't seem to be detecting that the phone is rooted. when i first open rom manager i get the message "you must root your phone for rom manager to function. superuser wasnot found at "/system/bim/su" or "/system/xbin/su". use google search on your computerto find instructions on how to root your phone." then when i select to flash a rom it says "an error occurred while attemping to run privileged commands". i tried uninstalling and reinstalling rom manager, rebooting, etc.. no luck. i've been searching threads for hours. please help!
You haven't rooted your phone.
Unlocking the bootloader just allows you to install unofficial images. You can now install a rooted image, to save yourself the trouble of having to root one.
First thing you probably want to do is install a custom recovery, which can then be used to make backups and install custom ROMs, etc.
Go find a custom recovery (look in the wiki), and install via fastboot. Stay away from Clockwork 3.xx...
Sent from my Nexus One using XDA App
mm installing a recovery will not root the phone either...
You need to root the phone (superoneclick works well)
http://forum.xda-developers.com/showthread.php?t=803682
If the bootloader is unlocked, you don't need to root the current ROM, unless you plan on keeping it, which the OP obviously doesn't (because why else would anyone download ROM Manager?)...
With an unlocked bootloader you can just flash any system image you want. You probably still want a custom recovery though, so you might as well flash recovery first, and then use that to flash ROMs...
Sent from my Nexus One using XDA App
danger-rat said:
Stay away from Clockwork 3.xx...
Click to expand...
Click to collapse
thought it was okkay if you are directly flashing 3.something and not upgrading it from a previous release?
Amon RA is the best though...
Sent from my Nexus One
I am a noob.
I followed some instructions to prepare my N1 for the OTA 2.3.3 update and messed some things up. I cleared EVERYTHING from Clokwork recovery, but, then phone would not boot anymore. So I manually loaded a Cyan 6.1 and GApps zip and got the phoen to load. Finally ran clockwork, rom manager, backed it up. Then I downloaded the stock image FR91 from ROM manager, clear cache/data and rebooted. Phone updated from 2.2 to 2.2.2. Now I have all my apps back and stock ROM, but superuser will not work. I cannot flash clockwork now, and cannot use ROm manager. Titanium prompted me to update superuser binary thru a zip file, but it will not run. Now, I tried to access recovery thru bootloader, but it just give me the Android with the ! and nothing more.
Alos, ROM manager keeps saying my phoen is not rooted, but when I bought it (used) it had Cyanogen 6.1. I know it's rooted, I get the unlocked boot screen, but why the problems now? How can I regain superuser functions to use ROm manager again?
Thanks in advance.
This is what happens when people don't read and don't understand what they're doing.
ROOT is a user in OPERATING SYSTEM = Android OS.
LOCK is a property of BOOTLOADER = a program that boots the phone.
Stock = NOT ROOTED, until you root it.
UNLOCKED = allows you to flash ROMs and other partitions directly from bootloader.
The 2 have no relation whatsoever, besides one - being UNLOCKED makes it easier to gain ROOT.
This has been discussed here a zillion of times. Do yourself and XDA a favor, please, and invest some time in reading Wiki - it points to several 101's (things to know) and guides.
So in my case I have unrooted the phone and should research on how to root again?
Thanks for the reply. I suppose I just confused myself.
So if I root again this will/will not affect the OTA update?
Sent from my Nexus One using XDA App
Wiki contains rooting guide.
Rooting won't affect OTA.
Custom recovery will affect OTA, unless signature checking is turned off in it.
You will have to root it.
A stock rooted rom will get the OTA. It will update as long as you don't remove stuff from stock. Like Amazon, twitter.
Please read the wiki.
Sent from my Nexus One using XDA App
Hello
I've just don't an OTA upgrade to Android 4.3 to my new Sprint HTC One.
After the OTA I rooted the device and installed recovery.
After I restarted the phone and launch the SuperSU I got this message :
"There is no SU binary installed, and SuperSU cannot install it. This is a problem.
If you just upgraded to Android 4.3 you need to manually re-root."
I would like to ask what should I do to make the root process sucseful .
I'm a newbe in the Android world and use some root manual I found.
1. What does it mean to re-root?
2. Should I unroot first ? And how it can be done?
3. Is there an 4.3 root manual somewhere to the make the SuperSU work?
Any instructions will be great help.
Thanks
Did you ever figure out how to get root? I am currently experiencing same issue.
Same issue
Same exact problem! Bump.
Any suggestions?
Please don't take OTAs after you've rooted your phone, because almost always it will wipe your root. Here is how I do my rooting.
Step 1: Go to htcdev.com and get your bootloader unlocked (this process will reset your phone back to factory setting, so back up all your pics, music, etc)
Step 2: Right after bootloader is unlocked, install a custom recovery (I prefer TWRP 2.6.3.0 for Sprint HTC One 4.3)
Step 3: As part of TWRP installation, SuperUser will be installed (root)
Step 4: Make a nandroid backup of your phone in TWRP. After that, install a custom ROM of your liking (there are plenty wonderful ones in Development section). This will keep your phone from taking OTA updates from Sprint/HTC. Don't worry, Devs on these forums (and their respective ROMs) are months ahead of Sprint in terms of updates.
For more details, head over to Development section and look for rooting instructions. there are very detailed tutorials there. Hope this helps.
having the same problem! im getting "There is no SU binary installed, and SuperSU cannot install it." from super su! I DO NOT WANT A CUSTOM ROM! i want stock rom but i want to have root. please help! the theres so many devs here im sure someone is kind enough to help
`Ghost` said:
having the same problem! im getting "There is no SU binary installed, and SuperSU cannot install it." from super su! I DO NOT WANT A CUSTOM ROM! i want stock rom but i want to have root. please help! the theres so many devs here im sure someone is kind enough to help
Click to expand...
Click to collapse
If all you want is pure stock with root -- just flash one of the already rooted stock ROMs in your custom recovery (assuming you loaded TRWP or PhilZ or CWM):
http://forum.xda-developers.com/showpost.php?p=48653344&postcount=2
If you want (more or less) stock with a *significantly* better experience (e.g., 30 volume steps, extreme stability, bla bla bla), I'd suggest InsertCoin (the thread is here whereas the download for our phone is here.
For either pick, since your coming in fresh to the ROM, do a full wipe (InsertCoin will do that for you as an option to the install, but I usually do that in recovery anyway).
Also -- note that InsertCoin *might* start the install and seemingly hang. That's a bug in Aroma, just hard restart the phone and try again -- letting the installer perform the wipe. It will work, and you'll be happy -- I'm sure.
---------- Post added at 05:03 PM ---------- Previous post was at 04:22 PM ----------
james341 said:
Hello
I've just don't an OTA upgrade to Android 4.3 to my new Sprint HTC One.
After the OTA I rooted the device and installed recovery.
After I restarted the phone and launch the SuperSU I got this message :
"There is no SU binary installed, and SuperSU cannot install it. This is a problem.
If you just upgraded to Android 4.3 you need to manually re-root."
I would like to ask what should I do to make the root process sucseful .
I'm a newbe in the Android world and use some root manual I found.
1. What does it mean to re-root?
2. Should I unroot first ? And how it can be done?
3. Is there an 4.3 root manual somewhere to the make the SuperSU work?
Any instructions will be great help.
Thanks
Click to expand...
Click to collapse
See my previous post (you can just load a rooted stock ROM). But "re-root" is something you do by either flashing the SuperSU.zip file, or letting your recovery take care of re-rooting.
No need to unroot.
My take? Backup your current ROM (stock, unrooted) and then flash one of those I mentioned.
This might be of some help, or at least clarify the issue you are having.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
fyi i realized i was flashing with an older version of supersu. V1.25 to be exact. I slapped supersu v1.86 on my phone and then installed that through TWRP. Root was successful.
Reason for rooting was I wanted to install titanium backup and freeze sprint id and other bloatware apps. I also wanted to eliminate GPU throttling which i did, and I set up the scrips to stop CPU and GPU throttling while im playing games, and then click the other button to shut off the script. Im happy with its performance. Shadowgun and modern combat 4 run much more smooth since doing that.
as for a custom rom im not sure im that brave yet... i thought all the big hubbub was cyanogen. has that mod lost its step? ill look in to the one you suggested, thanks.
after looking at insertcoin im going to have to pass. Ive read that kitkat completely breaks the phone for gaming and performance becomes horribad
I take no responsibility for what happens to your device if you follow this guide. Rooting or modifying carries risks, however I have tested this procedure many times with 100% success on my SM-t805. It should work for any device, but I can't confirm, so feedback please if it works for your device.
1. Firstly you need to downgrade your device to a XXU1ANF8 or earlier firmware suitable for your particular model. This is available at http://samsung-updates.com/ or you can use this one XSG-T805XXU1ANF8-20140625 which is for the T805 model only.
https://www.androidfilehost.com/?fid=23501681358555496 T800 only
Download and then install the firmware on your device with ODIN.
If you are still on Kitkat then there is no need to wipe the data partition. However if you are running Lollipop after successful installation you will need to boot into recovery POWER + HOME + VOL UP then select WIPE DATA/RESET -
YOU WILL LOSE ALL YOUR USER DATA SO BACK UP ANYTHING YOU NEED TO THE SD CARD FIRST!
NOTE: IF THE INSTALL FAILS AT HIDDEN.IMG OR CACHE.IMG SIMPLY BOOT INTO RECOVERY AFTERWARDS AND WIPE CACHE THEN CARRY ON WITH THE REST OF THE PROCEDURE.
2. Once booted into Android, set up your wifi and google account and skip everything else (this wont be needed if you didn't wipe the data partition)
3. Next we need to install a Few apps, so go ahead and install these apps from Play Store:
System app remover(root)
Root Validator
Terminal Emulator For Android
KINGROOT 4.1
Kingroot updates and earlier versions if posted version doesn't work:
http://androidxda.com/download-kingroot-application
Kingroot 4.5 (latest version)
We also need to download the package from this LINK
4. Using the built in File Manager extract the zip package to your internal SD card. Once extracted, inside the extracted folder is another folder called MRW.
THIS FOLDER NEEDS TO BE MOVED TO THE ROOT OF YOUR INTERNAL SD CARD OR THIS WON'T WORK.
5. Next go to Settings set your display timeout to 10 mins.
Now Run KINGROOT then wait for it to do it's thing. If it reboots part way through the process then after rebooting unlock your device, but don't touch anything for a couple of mins. The app should restart and continue. If you are successful you can move to the next step. If not, exit the app and run it again, it may take several attempts before you eventually achieve root.
6. After success uninstall the KINGROOT app (NOT KINGUSER) (not required with v4.5) and the other blue app with Chinese writing.
Now reboot - DO NOT RUN THE KINGUSER APP
7. Let your device fully boot then run the Terminal Emulator and wait for the command prompt
NOTE: IF AT ANY POINT YOU SEE A POP UP BOX WITH CHINESE WRITING ASKING YOU TO UPDATE THE KINGUSER APP SELECT CANCEL.
Now type or copy and paste the following command into the Terminal window:
su
It will ask for root permission, so select ALLOW.
Without closing the terminal emulator window, hit the HOME button and run the SYSTEM APP REMOVER app. (The app is red and simply called UNINSTALL)
The app will ask for root permission, hit ALLOW.
Look for the KINGUSER app then select it and uninstall it. Exit from the app.
Re-open the terminal emulator window and type the following:
sh /sdcard/mrw/root.sh
This will run a script, you will see a bunch of warnings, just ignore them .At then end of the script the SUPERSU app will run.
8. Hit CONTINUE then NORMAL.
Next you may see another message that 'Samsung knox has been detected'. When you see this message select CANCEL.
Once completed you should see a message saying that installation has been successful. Hit OK.
If you see the message again 'Samsung knox has been detected' select CANCEL then exit the SUPERSU app.
9 . Now check with ROOT VALIDATOR that you have root and everything looks ok.
DO NOT REBOOT.
The root is only temporary, if you reboot you will lose root.
10. The next step is to install our ROM of choice with Flashfire.
For more info on FLASHFIRE see here: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
11. Run FLASHFIRE and grant it root.
12. Agree to the disclaimer and then hit the Red circle with a white +.
Next select 'Flash firmware package' and then navigate to the firmware you want to install (in this case the stock tar package) and select it.
Wait until it finishes scanning the archive.
Next you will see the list of partitions to be flashed, all that is really required is BOOT, RECOVERY and SYSTEM. You can flash the others if you wish.
When you're happy hit the TICK and then you will see a list of what will be flashed. If you tap any one of them you will be able to change the options. Tap the REBOOT option then select DOWNLOAD from the list. This is so we can boot into download mode after the flashing process to flash the Lollipop BOOTLOADER. If not upgrading to lollipop just select REBOOT
I'd advise to leave the rest as is and then hit FLASH
NOW WATCH CHAINFIRES MAGIC!
13. After reboot it should boot directly into DOWNLOAD mode or REBOOT if not updating to Lollipop.
If updating to Lollipop we need to flash a Lollipop BOOTLOADER. I have provided a link below for the T800 and T805. If you have a T700/705/T807/T707 or if the ones provided don't work then you will have to extract it from the Lollipop stock ROM and then TAR it up.
T800XXU1BOCC_BOOTLOADER.tar
T805XXU1BOCC_BOOTLOADER.tar
Latest T800 boot loader thanks DUHasian skillz.
T800XXU1BOE3 bootloader
Flash the BOOTLOADER with ODIN.
If successful then after reboot you should have a rooted version of Lollipop or whatever rom you decided to install and an untripped Knox counter(hopefully)
Good luck and please give feed back.
If you wish you can give feedback to Chainfire at the link posted at the beginning of this post.
NOTE: If you wish to change roms or update and wish to keep root you will have to use the same procedure with Flashfire.
Also note that if you flash a custom KERNEL or BOOTLOADER then it may trip KNOX. Custom ROMs with stock KERNEL and BOOTLOADER should be OK(but don't hold me to that)
CREDITS TO CHAINFIRE FOR FLASHFIRE AND SUPERSU, KINGTEAM FOR ROOT AND WOLFDROID FOR THE KINGROOT REMOVAL SCRIPT.
My god I've been waiting for a thread like this one for a long time.
I don't have time to try it today but I'll give you feedback in a day or two.
Feedback here http://forum.xda-developers.com/showpost.php?p=61296003&postcount=12
Moderators, this thread should be sticked
Just so that I understand the limits of this method I need to ask. Is this method specific to achieve rooted (SuperSU) Lollipop 5.0.2 without tripping Knox or can further changes be made? For example:
1) Remove system apps (removing bloat).
2) Adding system apps such as Viper4Android, busybox, which must be installed in /system/priv-app
3) The Lollipop/Samsung compatible XPosed framework and modules
4) Installing a Tab S model compatible recovery (e.g. TWRP) as I would really like nandroid backups.
I only ask as in the Tab S Kingroot thread there was a post which mentioning that despite Kingroot having successfully achieved root without tripping Knox if you messed with the /system partition files there was the possibility of tripping Knox.
The comment in step 12 "... then navigate to the firmware you want to install ..." suggests that you could install one of the model compatible custom ROMs (e.g. CM). Is that a correct assumption or right now are you restricted to Lollipop stock? Some of those ROMs are from Lollipop 5.1.1 AOSP source (e.g. CM 12.1) which may be going too far with this method and still not trip Knox.
One last question, if I did implemented this could I go back to a pure unrooted stock kitkat/lollipop using Odin or Flashfire without tripping Knox? Odin would be fine.
I greatly appreciate the effort and quality of your post. I had hoped that a "Knox off" SuperSU lollipop root would be found for my month old Tab S 10.5 as I'm used to the low risk flashing on the Nexus devices and have had a mean itch to root without obvious risk to my warranty.
Thanks again
This method can be used to root any Rom.
Once you have root you can practically do what you please.
As for tripping Knox if you mess with the system partition, that's the whole point of root it already messes with the system partition. It shouldn't trip Knox, but never say never.
Just ensure once you have root you remove everything Knox related.
I can't confirm if a custom Rom will trip Knox, but as already stated as long as the bootloader and kernel are stock I believe it won't trip Knox.
Custom recovery may trip Knox.
You can go back to stock any time you wish.
ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again
3DSammy said:
ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again
Click to expand...
Click to collapse
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4
shayind4 said:
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4
Click to expand...
Click to collapse
Firstly, nowhere does it state to flash the kitkat bootloader on a lollipop Rom in step 12 or 13.
By step 13 you should be running a lollipop Rom.
Secondly Knox should not trip when flashing a stock bootloader. The bootloader can be flashed independently in Odin.
Lastly Flashfire does NOT flash bootloaders.
If you don't flash the bootloader your Rom won't boot.
I suggest you digest the guide again.
3DSammy said:
In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
Click to expand...
Click to collapse
It doesn't state to flash the boot loader in step 12? :what:
Your boot loader will be replaced when you downgrade to kitkat via Odin.
You need to reflash the lollipop boot loader after using Flashfire to install your Lollipop Rom or it won't boot.
Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?
Paddiii said:
Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?
Click to expand...
Click to collapse
No, this is the whole point of the post. Flashfire will root for you.
ashyx said:
It doesn't state to flash the boot loader in step 12? :what: ...
Click to expand...
Click to collapse
My bad, I saw the word "Boot" in step 12 and incorrectly assumed that was referring to a bootloader image.
Thanks for correcting me and your patience.
Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !
bibihub said:
Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !
Click to expand...
Click to collapse
The hidden.img failure is because its carrier/region related.For some it will flash ok, for others it will fail. It isn't actually required at all. Even if it fails to flash the rest of the Rom will.
All that needs to be done after that failure is to wipe cache in recovery.
As regards flashing custom roms. Remember your Rom is already custom as you have modified it.
I would say a good chance custom stock roms won't trip Knox as long as it's build properties reflect its a stock Rom.
However something like Cyanogen probably would trip Knox as its not based on stock.
I won't say this is for sure, but I think it's the general consensus.
Over one thousand views and literally only one person has bothered posting feed back.
ashyx said:
Over one thousand views and literally only one person has bothered posting feed back.
Click to expand...
Click to collapse
OK now two. I successfully applied your instructions yesterday. I really appreciate your guide.
What I did, differently is flashed with Odin using a Virtualbox Windows guest VM from my Ubuntu 14.04 host PC. It took a few days of false starts to get that working. Here is a "[How-To] Linux, Virtualbox and ODIN for your Samsung device", that I just posted to help others who do not have access to Windows machines.
Of the whole procedure the scariest moment was after flashing 4.4.2 stock with Odin over my devices 5.0.2 install. The reboot was too fast for me to get into recovery to wipe user data. I could not power off the SM-T800 and holding POWER + VOL DOWN just rebooted where it would hang displaying "SAMSUNG".
Booting into recovery ( POWER + VOL UP + HOME) had no effect what so ever. Finally I found that if I was fast enough I could reboot (POWER + VOL DOWN) and as soon as the screen went blank hold down the "POWER + VOL UP + HOME" buttons, then the tablet booted into recovery where wiping user data worked as described in your guide.
After completing your guide I am on stock Android 5.0.2 with Knox 0x0000.
My root apps so far:
Busybox
Titanium backup
GMD Gestures.
ES File Explorer with RW access to all partitions
System Uninstall Pro
Universal init.d
See Update below: "Unfortunately so far Viper4Android is not working as I cannot get SELinux permissive enabled either by the SELinux app or an init.d shell script using the "setenforce 0" command. From what I've read that is due to the Samsung stock bootloader."
V4A now works, see: "[HOW-TO] Installing Viper4Android (V4A) Audio on a Lollipop Tab S"
I took the high road and only froze the following KNOX related apps using titanium backup:
com.sec.enterprise.knox.attestation
KLMS Agent
KNOX
KNOX
KNOX II
KNOX SetUpWizardClient
So far I debloated 117Mgs of other apps using System Uninstall Pro. I bought the pro version of Flashfire just to show respect for Chainfire's development efforts. I have not tried to see if Flashfire's backups can be successfully restored yet.
Thanks again for your guide.:good:
Thanks for the feedback, it's constructive and encouraging for others to know It's successful.
For future reference you can disable auto reboot in Odin then manually reboot with POWER + VOL DOWN + HOME then as soon as it restarts switch to VOL UP while continuing to hold the other buttons.
The above procedure can be used at any point and will restart the device and get you into recovery every time.
just registered to suport OP, it works
I thought I did not need to run the su script as I could use kinguser w/o problems. But the flashfire is not compatible with other kinguser. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.
vancities said:
I thought I did not need to run the su script as I could use kinguser w/o problems. But the fireflash is not compatible with other root authorization app. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.
Click to expand...
Click to collapse
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.
ashyx said:
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.
Click to expand...
Click to collapse
I had success. What I mean is the step 6 7 8 9 are not necessary if flashfire could work with kinguser.
Also kingroot only works on XXU1ANF8 and maybe lower. I mentioned this because in other thread about kingroot, someone got success but most did not.
So my feedback . everything was great , was a little confused about Odin at first but like you said everything can be found on xda. Need to be on the most recent Odin which I believe is 3.10. Kingroot took forever to root but I believe it has something to do with connectivity to the servers. So my tab s is rooted no Knox counter. I'm hoping the custom tw rom doesn't revert all the hard work ? thanks again op.