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.
Related
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.
Hello folks. Unsure weather or not i post this in the correct place. So i rooted my SM-N9005 the other day just because well i"had" to. Ofcourse the next day the 4.4 update got released and i couldn't upgrade since my by now unfriendly phone told me i had tampered with it. I tried to restore it without really knowing what the hell i did and feeling a bit stupid for not getting it. I managed to remove root but it still says it's tampered with. Reckon i triggered the flash counter somehow. I could really use your help removing root and get my little phone back to "original" shape. Talk to me like a 3 year old since i apparently couldn't figure it out on my own. Cheers!
(And yes I have been reading so much about this my head spins now. I tried different ways to recover but i cant get it to work. I intentionally left out all the different apps i used here from the forum since that will probably confuse you guys aswell.)
how did you root?
download the kitkat firmware from sammobile then flash it using odin (so you don't need to upgrade via ota) then re-root
toinktoink said:
how did you root?
download the kitkat firmware from sammobile then flash it using odin (so you don't need to upgrade via ota) then re-root
Click to expand...
Click to collapse
Ok, it started when i tried to root it by following an online gtuide. However it didnt work so I tried another one and "semi-bricked" it. Using odin. I tried readiing up on it as much as i could but the more i read the more different ways i found. Long story short, i rooted it. It worked fine. But removing root didnt seem to do the trick. I would just like to return it to stock without ruining anything. And be able to upgrade OTA if possible.I love fiddling with these things but since i pay so much for this damn phone I rather not do anything more that can destroy warranty etc. As i understood it rooting it wouldnt leave a trace and should be easy to undo. Now I understand that wasnt the case. I know I am the one to blame but would love if anyone could just try to explain what to do in a simple step by step way. If you need any info on what i did I can try to explain but i ended up with like 12 different webpages open with different solutions and to be honest I am not sure I can explain everything i tried...
JFKruuse said:
Ok, it started when i tried to root it by following an online gtuide. However it didnt work so I tried another one and "semi-bricked" it. Using odin. I tried readiing up on it as much as i could but the more i read the more different ways i found. Long story short, i rooted it. It worked fine. But removing root didnt seem to do the trick. I would just like to return it to stock without ruining anything. And be able to upgrade OTA if possible.I love fiddling with these things but since i pay so much for this damn phone I rather not do anything more that can destroy warranty etc. As i understood it rooting it wouldnt leave a trace and should be easy to undo. Now I understand that wasnt the case. I know I am the one to blame but would love if anyone could just try to explain what to do in a simple step by step way. If you need any info on what i did I can try to explain but i ended up with like 12 different webpages open with different solutions and to be honest I am not sure I can explain everything i tried...
Click to expand...
Click to collapse
Solved
Hey everybody, if you've already opened up this thread, you already have my gratitude for seeing what my problem is.
If you haven't already caught on, I want to unroot my Samsung Galaxy S4. I have no idea why I decided to root it in the first place (maybe because that's what everybody else was doing? maybe because I'm just stupid? who knows), but now I really need to unroot it because I need the latest firmware.
The thing is, I've done a lot of stupid stuff to try and unroot it. I know, I should have looked for help instead of going out and doing stupid stuff on my own, but.. well, I don't really have an excuse - I'm just an idiot. My phone is still fully functional, but the device status is custom. But let me just tell you what happened.
1. I decided that I didn't want this phone to be rooted anymore. I opened up SuperSU and investigated the settings, and found an option to uninstall the phone. I decided to just go with it, and I uninstalled it. Everything went smoothly, nothing big happened, and before I knew it, SuperSU wasn't there anymore and everything seemed okay.
2. But it wasn't. I checked my device status, but it was custom. I was so confused. Wasn't it meant to be back to normal now? SuperSU wasn't there anymore, but it was still.. rooted? I turned on my S4 on Download mode. It said that it was still custom (or something similar to that, I don't remember the specific word). By now, I was confused and scared - what have I done?!
3. I searched around the internet for tutorials, and one in particular told me to download TriangleAway. Sweet, an app that unrooted and all I had to do was sit back and relax and let it do it's job! So I downloaded it and... it said that I didn't have SuperUser permissions or that I was unrooted. WHAT. I re-downloaded SuperSU and it said "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" JESUS CHRIST, tell me something I don't know, SuperSU! You're useless to me!! How could something be rooted yet unrooted at the same time? Life is so hard.
So now I'm sitting here, typing on my laptop, wondering what I could do to fix everything that transpired today. I searched up tutorials, but none of them had the same specifics on their phone as mine was. You see, my phone's baseband version is different from most. I have no idea why, but I'll list everything specific out here:
Model number: GT-I9505
Android version: 4.2.2
Baseband version: I9505XXUBMG4 (and for some reason, there is barely any help regarding this baseband, is it really rare to have this or something? or is is just the same as the I9505XXUBMGA? I don't know, so I don't want to take the risk)
If you've read and got up to here, you are already in my gratitude. If you help me, you have my thanks, and even if you don't, you still have my thanks for reading thus far.
If you could please help me, it would make this world just a little bit better! Thank you in advance. If you need any more information, please just tell me and I'll do the best I can to provide you with it.
Nyxdan said:
Hey everybody, if you've already opened up this thread, you already have my gratitude for seeing what my problem is.
If you haven't already caught on, I want to unroot my Samsung Galaxy S4. I have no idea why I decided to root it in the first place (maybe because that's what everybody else was doing? maybe because I'm just stupid? who knows), but now I really need to unroot it because I need the latest firmware.
The thing is, I've done a lot of stupid stuff to try and unroot it. I know, I should have looked for help instead of going out and doing stupid stuff on my own, but.. well, I don't really have an excuse - I'm just an idiot. My phone is still fully functional, but the device status is custom. But let me just tell you what happened.
1. I decided that I didn't want this phone to be rooted anymore. I opened up SuperSU and investigated the settings, and found an option to uninstall the phone. I decided to just go with it, and I uninstalled it. Everything went smoothly, nothing big happened, and before I knew it, SuperSU wasn't there anymore and everything seemed okay.
2. But it wasn't. I checked my device status, but it was custom. I was so confused. Wasn't it meant to be back to normal now? SuperSU wasn't there anymore, but it was still.. rooted? I turned on my S4 on Download mode. It said that it was still custom (or something similar to that, I don't remember the specific word). By now, I was confused and scared - what have I done?!
3. I searched around the internet for tutorials, and one in particular told me to download TriangleAway. Sweet, an app that unrooted and all I had to do was sit back and relax and let it do it's job! So I downloaded it and... it said that I didn't have SuperUser permissions or that I was unrooted. WHAT. I re-downloaded SuperSU and it said "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" JESUS CHRIST, tell me something I don't know, SuperSU! You're useless to me!! How could something be rooted yet unrooted at the same time? Life is so hard.
So now I'm sitting here, typing on my laptop, wondering what I could do to fix everything that transpired today. I searched up tutorials, but none of them had the same specifics on their phone as mine was. You see, my phone's baseband version is different from most. I have no idea why, but I'll list everything specific out here:
Model number: GT-I9505
Android version: 4.2.2
Baseband version: I9505XXUBMG4 (and for some reason, there is barely any help regarding this baseband, is it really rare to have this or something? or is is just the same as the I9505XXUBMGA? I don't know, so I don't want to take the risk)
If you've read and got up to here, you are already in my gratitude. If you help me, you have my thanks, and even if you don't, you still have my thanks for reading thus far.
If you could please help me, it would make this world just a little bit better! Thank you in advance. If you need any more information, please just tell me and I'll do the best I can to provide you with it.
Click to expand...
Click to collapse
Once you flash root the custom word wont get away unless you use triangle away to get rid of it that the use of triangle away and if you want stock :
Download latest firmware for your model and flash it through Odin done.
Why do you take the hard route?
You know you can just flash the stock rom you want with Odin? No need to unroot etc.
Hello everyone,
I am trying to root a SM-T537V, and I am having no success. My end goal is to attempt to run a linux distro on my tablet for fun and to use for my school assignments. I tried KingRoot, which achieved root, but lost it upon reboot. Some more research said this was because the bootloader was locked. I also tried towelroot, and the app seemed to do nothing. I don't mind doing it manually, but I just cant find any steps or information on the process.
DeepSpaceGalileo said:
I tried KingRoot, which achieved root, but lost it upon reboot. I also tried towelroot, and the app seemed to do . I don't mind doing it manually, but I just cant find any steps or information on the process.
Click to expand...
Click to collapse
Hi there I also have a SM T537 but mine is the AT&T Variant (the other overbearing service provider), I wish I had some advice for you, But I too have only had success in getting temporary root with Kingroot. No other one click rooter has had any success.
My device in question :
Samsung Tab 4
SM-T5337A
Running Android 5.1.1
BUILD # LMY47X.537AUCU1BOJ3
Has any one been able to get permanent root?, or able to point us to the proper thread, or even a “search phrase” to get us on the right path.
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk