Related
considering this is my 1st android, what should i do with the tab? step by step
lurking in this forum, i definitely want to root and be able upgrade firmware or to do anything in my tab
but what should i prepare? in the noob root for beginner, there's only explanation about rooting
can i save the original rom? what app to use? do i need to back up 1st? using what?
and can i upgrade the stock firmware to the jk1 without flashing it 1st to jj4? (since from what i read jj4 is full flash and jk1 is not, logically the stock firmware must be full flash also)
many thanks to those who can explain it in beginner's language
or maybe a couple of links would help
i already got the tutorial for the rooting process, so basically, what i need to do before rooting is what i need so i wont lose anything precious
I'd just start using it. Get some apps installed, see what you need/want/like to do with it, and if something you need/want/like to do is prevented by not having root access, then root it.
I'd say for the majority of Android users, there really is not much need to root, since Android lets you do so much right out of the box, unlike the competition that requires "jailbreaking" (God I hate that term) just to do simple **** like customizing.
Same goes with firmware. Unless you really enjoy the process of flashing and all that's associated with it, there's not always a clear need to do so. The only time I recommend somebody flash custom/leaked firmware for more than the fun-factor is if there's a problem in the current firmware that can only be fixed by flashing.
That said, this is XDA, which is all about custom ROMs and rooting and extracting more from a device than what the manufacturer shipped it with. Have at it.
jailbreaking lol, yeah, hate that
well something that bugs me is about the mobile browser view that some ppl actually advising rooting to be able to do that
hmm, what about what to do 1st if i actually want to root? any advice what to do and what app to use?
rooting on the Galaxy Tab is extremely simple:
1) Open the Market
2) Install and run 'z4root'
3) Hit the 'root' button' and wait
That's it.
Once you're done with that, one of the first things I'd suggest is to get AdFree installed and updated. It'll quite successfully block all those annoying ads.
i know about z4root, what i need to know is what i should do before rooting, like backing up the stock OS or data or app or anything like that, so i wouldnt regret having rooted my tab in case i flashed it with newest firmware like jk1
Rooting doesn't prevent flashing, or do any harm by itself, and when you flash, you wipe/reset the root.
oh, i see
so basically it just void my warranty and give me administator authorities like in windows?
thanks then
If you have to return your tab for any reason just reflash stock rom from whatever cell provider you got it from and the root is gone thus no breaking of the warranty
Yep, I rooted with z4root the other day. Was a piece of cake, although 1st attempt required a restart before it got going. 1st thing to install after that is Adblock.
Perfect.
Oh yeah, after that I installed titanium backup to get rid of the crappy gallery and replace it with the modded gallery 3rd form hi res zooming.
Sent from my GT-P1000 using XDA App
What modded gallery are you talking about? I'd like to change the gallery because I hate the stock one!
I ve rooted s3s note 2 etc... BUt I just tried to root my GS4 on Sprint, and it said write protected, now even though I was able to install super user on the device but it isn't working properly, and I cant flash any rom's any advice would be very much appreciated, I also noticed when I out the device into download mode to push cwm recovery it said write protection enabled, how can I disable this. thanx ahead XDA members...:fingers-crossed:
Are you on MF9 or MDL?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Mf9
Sent from my SPH-L720 using Tapatalk 4
Which root method did you use?
Sent from my SPH-L720 using xda app-developers app
I don't know how members mess up rooting a device. We have great and VERY easy methods. Plus tutorial vids from QBKing77.
Sent from my SPH-L720 using Tapatalk 4
You're supposed to use ChainFire's auto root method: CF-auto-root
Sent from my SPH-L720 using XDA Premium 4 mobile app
PearlS4 said:
I ve rooted s3s note 2 etc... BUt I just tried to root my GS4 on Sprint, and it said write protected, now even though I was able to install super user on the device but it isn't working properly, and I cant flash any rom's any advice would be very much appreciated, I also noticed when I out the device into download mode to push cwm recovery it said write protection enabled, how can I disable this. thanx ahead XDA members...:fingers-crossed:
Click to expand...
Click to collapse
The write protect is normal and does not impact rooting or flashing anything. So any issues you are having are unrelated. It would be a problem with something you installed or are trying to install.
As Salil999 said, cf auto is the preferred rooting method if you aren't installing an already rooted Rom.
Sent from my SPH-L720 using Tapatalk 4
an updated method/step by step procedure "how to root" IS really needed.
Salil999 said:
You're supposed to use ChainFire's auto root method: CF-auto-root
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
(Sorry but this is NOT directed at you i am simply quoting to prove a point)
This is something I have had an issue with as well. Despite how easy it might be for most not everyone catches on as quickly because of common misconceptions or how they might perceive the information because everyones mind works differently. I have used the CF root method and it is NOT the best method to use considering even after I used it i still had NO root. Top that off and add the fact that i even downgraded the version I had several times and i have searched countless times how to do a manual root and just havent had the time to complete a full root. Not everyone has the option to tinker all day (not saying that you do) to understand or figure it out IE real life - kids work school etc. what ever the case is. I have flashed a bootloader several times after establishing root to do nandroid backups/iso imgs and actually completed several come to find out that for some reason my Root did not stick at all when i had thought it did and i followed everything many times step by step to no avail achieve a permanent root. There is a problem with the process and I am sorry but everyone else that has gotten root is just fortunate the latest update has really put a damper on doing root the way it is described and is NOT current to fit everyones needs ATM. I am sure there are MANY others like the OP myself and others that are having the SAME EXACT ISSUE. I am not new to ADB and have been rooting my phones since the HTC came out with the original Supersonic Evo 4G using the ADB method and some people without providing any options just have to think that because some of us are having problems that we (or I) are not "intelligent" enough to figure it out and i have worked with computers since windows for workgroups 3.11 and construct my own Gaming RIGs, Servers, Laptops (and phones recently as of the last 2+ years) never having any issues because its just second nature to me at times with PCs and Laptops. Phones on the other hand are much more complicated because of incompatibility issues with OTA updates from the manufactures and cellular service providers either because they dont want people messing with their brands and wish to be a pain in the butt for whatever the reason, financial or whatnot. I am seeing it ALL over XDA for Sprint Users mostly since thats where i am confining my search patterns. I am actually going through ADB to manually archive root because im tired of searching through countless postings to find nothing on the subject and do not enjoy the dumb comments people think they have to leave on my post and others posters. Im sure im going to get a stupid comment or a flame of some type because even when im just "venting" at my frustrations as im sure everyone does from time to time no one enjoys being messed with when they are already pissed off and frustrated that just makes matters worse for the OP and the community. Eventually the problem works itself out, but c'mon people, seriously not everyone gets to have the opportunity to get the root achieved right because of the stupid OTAs released time and time again that make the latest root option obsolete because thats what it IS RIGHT NOW OBSOLETE. It is being a pain in my ass because KNOX was tripped with a custom rom and even though the custom ROM sticked the ROOT DID NOT. they (cell manufactures or providers) prevent rooting in the first place by ADDING additional roadblocks in OTAs just to slow down/prevent users or people that enjoy the ability of having the option to use root to their technical advantages (because they lose money, which really is more profit on top of original costs inflated to a ridiculous amounts not fair to consumers). Even with development, future development, paying employees, etc. its not even close to being fairly priced market for consumers and already the rate are increasing at a rate to costly and unfair to consumers with little to no option of maxing the potential life of a product. I dont know about everyone but not all can afford to keep updated with the latest gear. We have great developers that probably get no where NEAR the amount of donations that they SHOULD be receiving to keep up when they are devoting their own personal time and currency to making apps and ROMs but the fact remains that it is easier for a huge company to crank out software because they PAY people to do it knowing that freeware developers are not going to have the time or resources to keep up. If anyone knows of an updated method or a manual method to root or another option the help is very much appreciated by myself others and the OP. Thank you to the people that have taken the time to help everyone else in a positive manor.
VenomousViper said:
(Sorry but this is NOT directed at you i am simply quoting to prove a point)
This is something I have had an issue with as well. Despite how easy it might be for most not everyone catches on as quickly because of common misconceptions or how they might perceive the information because everyones mind works differently. I have used the CF root method and it is NOT the best method to use considering even after I used it i still had NO root. Top that off and add the fact that i even downgraded the version I had several times and i have searched countless times how to do a manual root and just havent had the time to complete a full root. Not everyone has the option to tinker all day (not saying that you do) to understand or figure it out IE real life - kids work school etc. what ever the case is. I have flashed a bootloader several times after establishing root to do nandroid backups/iso imgs and actually completed several come to find out that for some reason my Root did not stick at all when i had thought it did and i followed everything many times step by step to no avail achieve a permanent root. There is a problem with the process and I am sorry but everyone else that has gotten root is just fortunate the latest update has really put a damper on doing root the way it is described and is NOT current to fit everyones needs ATM. I am sure there are MANY others like the OP myself and others that are having the SAME EXACT ISSUE. I am not new to ADB and have been rooting my phones since the HTC came out with the original Supersonic Evo 4G using the ADB method and some people without providing any options just have to think that because some of us are having problems that we (or I) are not "intelligent" enough to figure it out and i have worked with computers since windows for workgroups 3.11 and construct my own Gaming RIGs, Servers, Laptops (and phones recently as of the last 2+ years) never having any issues because its just second nature to me at times with PCs and Laptops. Phones on the other hand are much more complicated because of incompatibility issues with OTA updates from the manufactures and cellular service providers either because they dont want people messing with their brands and wish to be a pain in the butt for whatever the reason, financial or whatnot. I am seeing it ALL over XDA for Sprint Users mostly since thats where i am confining my search patterns. I am actually going through ADB to manually archive root because im tired of searching through countless postings to find nothing on the subject and do not enjoy the dumb comments people think they have to leave on my post and others posters. Im sure im going to get a stupid comment or a flame of some type because even when im just "venting" at my frustrations as im sure everyone does from time to time no one enjoys being messed with when they are already pissed off and frustrated that just makes matters worse for the OP and the community. Eventually the problem works itself out, but c'mon people, seriously not everyone gets to have the opportunity to get the root achieved right because of the stupid OTAs released time and time again that make the latest root option obsolete because thats what it IS RIGHT NOW OBSOLETE. It is being a pain in my ass because KNOX was tripped with a custom rom and even though the custom ROM sticked the ROOT DID NOT. they (cell manufactures or providers) prevent rooting in the first place by ADDING additional roadblocks in OTAs just to slow down/prevent users or people that enjoy the ability of having the option to use root to their technical advantages (because they lose money, which really is more profit on top of original costs inflated to a ridiculous amounts not fair to consumers). Even with development, future development, paying employees, etc. its not even close to being fairly priced market for consumers and already the rate are increasing at a rate to costly and unfair to consumers with little to no option of maxing the potential life of a product. I dont know about everyone but not all can afford to keep updated with the latest gear. We have great developers that probably get no where NEAR the amount of donations that they SHOULD be receiving to keep up when they are devoting their own personal time and currency to making apps and ROMs but the fact remains that it is easier for a huge company to crank out software because they PAY people to do it knowing that freeware developers are not going to have the time or resources to keep up. If anyone knows of an updated method or a manual method to root or another option the help is very much appreciated by myself others and the OP. Thank you to the people that have taken the time to help everyone else in a positive manor.
Click to expand...
Click to collapse
Wow, sounds like you are having a bad day. Not trying to piss you off or anything. But cf autoroot works, and works very well. And all knox does is trigger a warranty flag that can not be reset and limits you going backwards on firmware. It doesn't do anything to prevent rooting. I think the best method for you would be to reset and start with a clean phone. By reset, I mean downloading and installing the full MJA tar file and doing a factory reset. This way you have a clean phone with nothing that might be blocking your rooting process. Next, grab cf autoroot and make sure you are using a newer version of odin. I use odin3 ver. 3.07. Run cf autoroot and let it boot all the way up. Now go into your app drawer and see if supersu is installed. If it isn't install it from the play store. Open cf autoroot and install the binaries, use the normal button. Now, if it errors on the binary install don't panic. Redo the cf autoroot and repeat the install of supersu again if it is not in the app drawer. If it is in the app drawer open it and install the binaries if it asks. It's basically a rinse and repeat operation. On MJA it sometimes takes a few attempts for it to stick. After you successfully have root, then use goo manager to install twrp or install the latest philz recovery. It takes a little patience but cf autoroot does work, and it is the best method available. Remember, starting with a clean slate is best. And if you want to be the most up to date, take the MK2 OTA before you start the root process. CF autoroot works on MK2 also.
Thanks for the useful help
cruise350 said:
Wow, sounds like you are having a bad day. Not trying to piss you off or anything. But cf autoroot works, and works very well. And all knox does is trigger a warranty flag that can not be reset and limits you going backwards on firmware. It doesn't do anything to prevent rooting. I think the best method for you would be to reset and start with a clean phone. By reset, I mean downloading and installing the full MJA tar file and doing a factory reset. This way you have a clean phone with nothing that might be blocking your rooting process. Next, grab cf autoroot and make sure you are using a newer version of odin. I use odin3 ver. 3.07. Run cf autoroot and let it boot all the way up. Now go into your app drawer and see if supersu is installed. If it isn't install it from the play store. Open cf autoroot and install the binaries, use the normal button. Now, if it errors on the binary install don't panic. Redo the cf autoroot and repeat the install of supersu again if it is not in the app drawer. If it is in the app drawer open it and install the binaries if it asks. It's basically a rinse and repeat operation. On MJA it sometimes takes a few attempts for it to stick. After you successfully have root, then use goo manager to install twrp or install the latest philz recovery. It takes a little patience but cf autoroot does work, and it is the best method available. Remember, starting with a clean slate is best. And if you want to be the most up to date, take the MK2 OTA before you start the root process. CF autoroot works on MK2 also.
Click to expand...
Click to collapse
No Sir, not pissed off and maybe what i wrote was misconstrued since I left out some pertinent information listed here now... very pleased with your answer. Probably some of the most productive and useful information thus far and the best I have received/come across yet. I was currently trying to update the post when I saw your comment to me. I had failed to mention some important facts to include what I have had successfully completed listed down here:
KNOX tripped of course 0x30 Custom ROM via Odin Flashed/Stuck; MDC/MDL downgraded from a MF9 Baseband Modem Flashed via Odin/Stuck; Custom Recovery CWM 6.0.6.6 touch Flashed via Oden/Stuck PASSED; Root I HAVE TRYED MANY DIFFERENT WAYS POSTED VIA POSTS ON THE SPRINT COMMUNITY and FAILED TO KEEP ROOT. HOWEVER, it was succesful according to ODIN 1.85 & 3.07 many times over and over with CF-Auto-Root it stated as it PASSED via Odin... DID NOT STICK OR STAY when the reboot restarted the phone and loaded the Custom ROM every time I look up with root checker as stated still NO ROOT!
There isn't much I can possibly be missing but I am hoping there is some kind of solution via information you have provided by MK2 OTA root
I certainly am going to try posting all of this information for others to see in an easier to read/find post to benefit the community sometime before the new year. I was able to gain more by reading the posts to Unlock SIM which helped a lot since it was a refresher on ADB commands/steps for me.
Thanks again. i will update as soon as I figure it out or do not figure it out.
I LOVE YOU!!!! I feel the same way. Like im smart ok i am not near as knowledgeable as u r but i have messed with phones since iphone 3g came out and since the first ibm desktop cost 4000.00 lmao my dad and i are alike in that we cant just leave **** alone lol i dont understand a damn bit of what these posts say. Sometimes u have someone who has no knowledge of how these damn phones work mentally but u give me one i can tear it appart and fix anything on it even waterdamage thats my favorite. But no one tells you what these files are what they do and why u want it and then in like odin what the abrev mean what file goes there and why like if a rom is basicay windows but custom what slot does it go in then what are the rest for? Do u need to fill all or just one u need, why? Would it mess it up, why will one mess it up n the other not? What is this mk9 bs and how do i know what mine is? Ya know and im a single mom with 2 kids and my phone is important and the damn thing is stuck cause its update jacked up and now its in a boot loop and i cant get it out. It wont recongnize it in kies it wont take the md5 update through odin it wont even let me get to the menu that lets me clear cache or factory reset it. Ive done all sorts n got no where.
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Not at the moment. There is a root method, but no factory image to flash back to.
http://forum.xda-developers.com/showthread.php?p=43890414 check here for recovery updates.
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
sheek360 said:
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Click to expand...
Click to collapse
We all just have to be patient! It's not the end of the world, rooting it allows you to remove some bloatware, then you can install themes and launchers to make it a little better!~
You can still tweak the device so it's enjoyable!
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
jd1639 said:
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
Click to expand...
Click to collapse
You get around alot, have you seen any update to the MF3 bootloader issue?
TheAxman said:
You get around alot, have you seen any update to the MF3 bootloader issue?
Click to expand...
Click to collapse
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Tons and tons of uninformed people are messing up their phones. You're right, it's sad.
It will be great when people can comfortably root their device knowing there is a way back when all is said and done.
In the mean time, to the OP, playing the waiting game will not kill anyone in this situation.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Agreed, if most would have read just a little, they would not be having this issue. For me, I always wait until a dev gets a hold of an update and does their thing, and then I update to the newest...I have NEVER updated direct on the phone, even with all the phones I have ever owned.
Not happening OP, do a search on MF3 in the search bar you will find all kinds of things related to it.
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
ThePerson98 said:
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
Click to expand...
Click to collapse
I just wanna plus 1 that for the OP
Sent from miPhone using XDA Premium HD app
As long as you're a smart cookie and don't go around attempting to mod your twframework and other important inner system files, I wouldn't get too disheartened and held back from touching the partition. Simply be intuitive and anything you intended on replacing, rename instead to the file with a *.temp extension. Wouldn't be that hard to roll back then (as long as you can still boot). Rooting itself mods the system, so people have already jumped ship in that regard.
Just don't go around trying to enable verbose boot or flash a recovery from some kind of mobile ODIN or GooManager.
BE SMART, not eccentric and living by the standards of yolo.
I thought that I could survive without registering, but the day did come. I have rooted successfully several phones but have not fiddled with Samsung before and was not so familiar with the models. I checked the phone model too busy and remembered wrong it to be i9505. Too bad i noticed the mistake after using the motochopper, when trying to find correct CWM. It was an i9506. The phone is working fine, but the su requires updating. I used root checker and not surprisingly "not rooted". After noticing my mistake I would not want to do anything before getting some advice. I have a linux and using of the odin is not possible, at least without visiting some of my friends. Too bad I could not find any help without posting. Can you please suggest how to proceed to prevent bricking and even eventually rooting the phone? If I manage to get access to windows, how hazardous is it to proceed from the beginning with the guides for i9506, after failing the rooting? What excatly is there going on at the moment, when super su is installed but does not have root?
Take a look this thread: HERE
Thanks for your reply! I checked the thread all way through. I think that the only solution is to try the basic method of the first post and see what happens. I should have done that in the first place. Luckily the phone has 4.2.2. without knox. I hope that the previous rooting attempt does not interfere somehow. I will visit my friend some day and report the result here.
I promised to report how things sorted out. Everything went smoothly with rooting as I followed the guide here , not a single issue. Although it would probably have worked with heimdall as well, I did not want risk anything and used windows computer of my friend. Thanks for Joku1981! Keep up the good work! Over and out.
Hey guys.
I've managed to find a couple of videos and tutorials on rooting the A1000 (99% of them using KingRoot), but there's absolutely no info on the A1000m. While it's basically the same phone with a bit less memory, it won't root. I've tried pretty much everything I found on the web with no success. And quite frankly I'm scared to keep going, because I can't find the firmware and if I brick this stupid phone I'll probably have to pay for it, because it's not mine. Not a big deal, it's one of the cheapest devices available in my country, but I'd rather find a way to root it or at least keep it in working condition before returning it to it's owner.
Any help on the matter will be greatly appreciated. Even if all you can do is tell me that it's impossible to root. I just need to be sure, before I return it.
topdawg89 said:
Hey guys.
I've managed to find a couple of videos and tutorials on rooting the A1000 (99% of them using KingRoot), but there's absolutely no info on the A1000m. While it's basically the same phone with a bit less memory, it won't root. I've tried pretty much everything I found on the web with no success. And quite frankly I'm scared to keep going, because I can't find the firmware and if I brick this stupid phone I'll probably have to pay for it, because it's not mine. Not a big deal, it's one of the cheapest devices available in my country, but I'd rather find a way to root it or at least keep it in working condition before returning it to it's owner.
Any help on the matter will be greatly appreciated. Even if all you can do is tell me that it's impossible to root. I just need to be sure, before I return it.
Click to expand...
Click to collapse
Just needed to know:
Do you tried KingRoot or skipped it because you were scared?
Tried it. And that's the one that scared me. At first it wouldn't work. Someone told me to give it another try and it said the phone was rooted. But it wasn't. All it did was break the playstore and it wouldn't let me download anything. The phone froze and restarted a couple of times... It was a pain in the ass. And the other app that came with it, King User - it wouldn't go away even after a hard reset. I had to install KingRoot again, try rooting it a couple of times until it said it was successful and then do the unroot procedure in King User to get rid of the app.
In my opinion, KingRoot is a total waste of time. Never used it before, don't plan on doing it in the future.
topdawg89 said:
Tried it. And that's the one that scared me. At first it wouldn't work. Someone told me to give it another try and it said the phone was rooted. But it wasn't. All it did was break the playstore and it wouldn't let me download anything. The phone froze and restarted a couple of times... It was a pain in the ass. And the other app that came with it, King User - it wouldn't go away even after a hard reset. I had to install KingRoot again, try rooting it a couple of times until it said it was successful and then do the unroot procedure in King User to get rid of the app.
In my opinion, KingRoot is a total waste of time. Never used it before, don't plan on doing it in the future.
Click to expand...
Click to collapse
A1000 has older chipset Spreadtrum SC7731 without G mark on the end. your vibe A has half memory and smaler kapacity of battery bad plastiks and dimensions look same on www gsmarena com
ps: kingo root for windows with debuging activate in phone working with A1000 on second try (and another few phones year before), and cpu-z (cpuid) confirm it is root acess
hey, I ve got Lenovo A1000m too but I ve tried many softwares and tutorials but noone goes...Can anyone help me?
A1000m unlock bootloader?
Hey guys
Has anybody managed to unlock the bootloader?the method with Fastboot oem unlock doesn’t work.
Any help?
Thanks