Hello everyone,
My girlfriend was playing with her phone, and accidentally deleted almost 2,000 pictures from the ATT GalaxyS4, which of course were not backed up.
I tried looking for various data-recovery tools, but they all require a rooted phone. I tried to root it with the Kingo app, and using towelroot, but both failed. I am aware you can also do it downloading an older firmware, with the help of Odin, then using towelroot, then flashing with the NJ4 firmware again, since towelroot doesn't work on current version.. but I am afraid using this method will eliminate or overwrite any trace of the invisible "deleted" photos still left on the internal memory.
Does anyone have any suggestions / ideas on how to safely either root this phone, or restore the photos?
Appreciate any reply/info/help. I have spent hours looking into all this and am pretty new to it, all to no avail..
If nothing else is anyone familiar with any reputable paid data-recovery services out there? These photos are pretty important to us both so that is also an option we would look into.. just not sure how effective any of this is. Maybe send the phone to the CIA or NSA...
Thank you for any help.
Disk digger may be an option but I think it requires root. Odin will wipe the device so that's not an option
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Disk digger may be an option but I think it requires root. Odin will wipe the device so that's not an option
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yea, I looked into Disk Digger already, unfortunately it requires a root, which seems to be the case with almost all, if not all data-recovery programs for the phone. Not sure if there is any way to even do this without a root.. I have had no luck finding one.
Kingo has good reviews and claims to support most of the main phones, but I have had no luck with it, it just goes into a loop of downloading and waiting for device.
Thanks.
Anybody ever hear of a root called, "CC root gadget"?
Should come up in google, I can't post links yet. Couldn't find any info on it and didn't want to try it.. seems a bit shady.
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.
Hi. Before you read all that mess below, just answer this simple question first: Is it possible to restore to stock (as in with all bloatware and pre-loaded apps intact) on an AT&T Samsung Galaxy S4 SGH-I337 Baseband Version I337UCUAMF3 on Android Version 4.2.2? If not, just say so and disregard reading the rest lol. (If it's any help, the Kernel Version is 3.4.0-812098 and Build # is JDQ39.I337UCUAMF3).
So I have been messing around with my S4, specifically with NoBloat and rooting, trying to delete bloatware and such. And with that line, you should already know by now what has happened. Though I did backup most of the things I deleted, I think I've deleted some important things and now want my phone returned to stock. It has been rooted so I also want to get rid of the binary counter as well. Before you send me to another thread however, I want to tell you guys what I have already tried and researched, yet always encounter an obstacle in:
I have tried using Odin (3.07 AND Odin3 v1.85) and flashing (correct term?) to my phone with I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 as the PDA, but when I pressed start, Odin would get to the first box then say FAIL!. My phone then has START [224, 1440] then under it SW REV. CHECK FAIL : fused :2, Binary : 1. I think it may be because in the ID: COM space, my phone recognizes as a 0:[COM:3], 4, or 5, but not a 6, which in a video tutorial I've watched, says it must be a COM:6 for it to work. I have tried many of the troubleshooting tips such as removing and putting the battery back in, changing usb ports, and reinstalling drivers, all of them leading to the same FAIL! screen. I know the file and the version of my phone doesn't match (wishful thinking I guess xP ), but is there any other way pr a tar.md5 file for my version to restore using Odin?
Another thing I've tried is using ADB to reupdate (?) my phone. I downloaded the adt files and put the tar.md5 file in the platform-tools folder. Then I opened a command prompt but when I type in adb sideload <filename.tar.md5>, it says it could not be read or could not start. Backtracking, I tried downloading sdk properly but got lost in that and jumped off this method completely.
Finally, giving up all hope of reverting back to complete stock, I simply wanted to reset the binary counter, and even here I had issues. I found out that AT&T is one of the carriers that locks their bootloader, so I searched and found djrbliss' LOKI method to get around it. I tried downloading at the github link, but didn't know how to download it (maybe I somehow just didn't see the download button), so sadly, I couldn't do this either.
I have reset and restored using past backups but the applications, lock screen, and a few other things did not restore properly (while the rest of it did fine, strangely).
Sooo...yeah. I think I may have exhausted almost every method possible, so this thread is really my last resort. Please help me find a way or just tell me it can't be done, so I can put this to rest.
Sorry for the long-winded message, haha, but thanks to all who'll help me find a solution to this dilemma
Go to a best buy Samsung experience. They can flash the stock mf3 firmware.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Go to a best buy Samsung experience. They can flash the stock mf3 firmware.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
But because I rooted before, won't that void my warranty? Or will they just restore to mf3 stock firmware no questions asked anyway?
Also, double checking, doing this will restore all stock apps and reset binary yes?
Thanks for responding quickly. I will try this out asap. :laugh:
AquaYan said:
But because I rooted before, won't that void my warranty? Or will they just restore to mf3 stock firmware no questions asked anyway?
Also, double checking, doing this will restore all stock apps and reset binary yes?
Thanks for responding quickly. I will try this out asap. :laugh:
Click to expand...
Click to collapse
It is void, but multiple people have taken in rooted phones and gotten them flashed. Just say it isn't, and they should. I don't know about binary but the system will be factory fresh
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
There is a thread on how to remove the 'custom' boot screen, but I am not sure if it works on mf3. Sorry, but can't find the link right now
im on sph-l720 had 4.3 mk2 all methods was not working for me either would fail right off the bat or go thru the proccess say it was rooted then when doing root checker i wasnt rooted..... finally after messing with this for about a week i finally found a way to do it i used kingoapp.... this method was very simple and easy to use and i am now rooted..... just thought i would post this if there was those out there that was having the same trouble that i have been having
sk907 said:
im on sph-l720 had 4.3 mk2 all methods was not working for me either would fail right off the bat or go thru the proccess say it was rooted then when doing root checker i wasnt rooted..... finally after messing with this for about a week i finally found a way to do it i used kingoapp.... this method was very simple and easy to use and i am now rooted..... just thought i would post this if there was those out there that was having the same trouble that i have been having
Click to expand...
Click to collapse
newbi (to s4)here and still looking... went to there site and didnt see the i720 on there list... did it trip knox when u rooted?
root
ibcenu said:
newbi (to s4)here and still looking... went to there site and didnt see the i720 on there list... did it trip knox when u rooted?
Click to expand...
Click to collapse
My Knox was tripped by one of the failed attempts. ... As far as I know the kingo route did not trip Knox unless the counter only stays on 1... If it adds up then no kingo did not trip my Knox that is something I'm not to sure of may be something to ask one of the ppl that know a lil more but I do know that Knox only voids the Samsung warranty. ..If something does happen u can still pay the deductible to replace ur phone... wich is only $150 that's as long as u have the insurance coverage on ur plan... As long as u follow the steps wich is really simple u won't brick... sph-l720 is not on the list for kingo but it does work that's what I used... All the other ways says that the su is out of date so I recommend if u are going to do it use kingo after I did that I downloaded rom manager n installed a CWM my phones working fine
What's up team,
still getting used to things around here and I apologize for the stupid questions in advance! However, you all have been amazing and helpful to me thus far and I appreciate it.
So, I finally decided to root my Sprint GS4 thanks to the helping hand of the great QBKing77
I was trying to go even further and be able to do the free hotspot which QBKing77 had a video for as well. However, I noticed that the download links that he had supplied us folks with did not include baseband version is MK2 - which is what I am currently running (whatever that means.)
So among several other questions, first and foremost; what can I do to get the free hotspot/tether with MK2? Should I simply download one of the other links instead or will this damage my device?
Also, as said, I am new to this. I just rooted my device for the first time and am unaware what the difference is between odexed and deodexed? What does this mean, what is the difference, and how do I know which one I am?
Leading in to that, I installed TWRP custom recovery. I tried to click on back up then select "boot," "system," and "data." However, it is saying that the attempt was failed. I am going to assume that this is because the whole back up would be roughly 3gb's and it says that I have only 502mb's available on my phone.
I read somewhere a while back that I could delete stock apps from my phone after I route. How can I do this? I am guessing that this would free up a significant amount of storage and thus could accomplish the back up. Is it safe to delete stock apps? How can I know which apps I can safely uninstall?
Thanks guys! Any other tips or tricks or words of advice...even constructive criticism are welcomed!
erquiagomon said:
What's up team,
still getting used to things around here and I apologize for the stupid questions in advance! However, you all have been amazing and helpful to me thus far and I appreciate it.
So, I finally decided to root my Sprint GS4 thanks to the helping hand of the great QBKing77
I was trying to go even further and be able to do the free hotspot which QBKing77 had a video for as well. However, I noticed that the download links that he had supplied us folks with did not include baseband version is MK2 - which is what I am currently running (whatever that means.)
So among several other questions, first and foremost; what can I do to get the free hotspot/tether with MK2? Should I simply download one of the other links instead or will this damage my device?
Also, as said, I am new to this. I just rooted my device for the first time and am unaware what the difference is between odexed and deodexed? What does this mean, what is the difference, and how do I know which one I am?
Leading in to that, I installed TWRP custom recovery. I tried to click on back up then select "boot," "system," and "data." However, it is saying that the attempt was failed. I am going to assume that this is because the whole back up would be roughly 3gb's and it says that I have only 502mb's available on my phone.
I read somewhere a while back that I could delete stock apps from my phone after I route. How can I do this? I am guessing that this would free up a significant amount of storage and thus could accomplish the back up. Is it safe to delete stock apps? How can I know which apps I can safely uninstall?
Thanks guys! Any other tips or tricks or words of advice...even constructive criticism are welcomed!
Click to expand...
Click to collapse
You can find the MK2 hotspot mod in this thread post #337: http://forum.xda-developers.com/showthread.php?t=2256950&page=34
Make sure you download the correct one. If you only rooted the stock rom then you need the odexed version, if you downloaded and installed a custom rom then you need the deodexed one. As you guessed, if you use the wrong one you will brick your phone.
TWRP backup, you need an external sdcard if you want to make backups or your internal memory will max out. If you have an external sdcard, look on the twrp backup page closely and you should see an option to switch to the external sdcard.
Stock apps delete, you can delete stock apps if you are rooted but be careful, if you don't know which ones can safely be removed then search on here to make sure you don't delete one that is required. You will need a file explorer app that has root permissions to access the system partition. I would recommend an app like titanium backup to remove these apps so that you can first back them up so you can replace it if you mess up. Again, you should use an external sdcard or it doesn't make sense to back up if you are doing it to save space.
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
lidor578 said:
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
Click to expand...
Click to collapse
Questions should be in Q & A. That's what its there for.
Buying a 900V is a big mistake if your not on Verizon. No, you cannot flash N9005 roms on this device. Your best bet would be installing one of the roms in the development section here. http://forum.xda-developers.com/verizon-galaxy-note-3/development
lidor578 said:
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
Click to expand...
Click to collapse
how do you rooted your mje n990v? i can't
huess113 said:
how do you rooted your mje n990v? i can't
Click to expand...
Click to collapse
Kingo... worked on mine
shiftr182 said:
Kingo... worked on mine
Click to expand...
Click to collapse
I don't know if there is a scamware version of Kingo going around or something, but I've never been able to get it to work.
I can use ADB without any problems on my SM-N900V. I then run Kingo and it does nothing, just sits there "waiting" for the devices. Windows Firewall disabled, No AV software, Trying Kingo w/Admin permissions and without. Nothing works.
After wasting hours with this, I finally decided I'd try a vanilla Windows 8 install, nothing on it but Kingo. Still didn't work.
Brought my phone back to my PC, ADB works just fine -- tried Kingo again -- nothing.
...On a related note...
After searching the forums for some time, there is one question I just can't determine definitively:
Can the SM-N900V (Verizon Galaxy Note 3) be truly "unlocked" with a custom recover (or) are we still limited to Safestrap options?
Thank you in advance,
RKM
rkmFL said:
I don't know if there is a scamware version of Kingo going around or something, but I've never been able to get it to work.
I can use ADB without any problems on my SM-N900V. I then run Kingo and it does nothing, just sits there "waiting" for the devices. Windows Firewall disabled, No AV software, Trying Kingo w/Admin permissions and without. Nothing works.
After wasting hours with this, I finally decided I'd try a vanilla Windows 8 install, nothing on it but Kingo. Still didn't work.
Brought my phone back to my PC, ADB works just fine -- tried Kingo again -- nothing.
...On a related note...
After searching the forums for some time, there is one question I just can't determine definitively:
Can the SM-N900V (Verizon Galaxy Note 3) be truly "unlocked" with a custom recover (or) are we still limited to Safestrap options?
Thank you in advance,
RKM
Click to expand...
Click to collapse
I had the same problem with Kingo initially. I don't remember how I fixed it, but it was a simple fix.... something stupid. Now it works with no problem.
In regard to the recovery, if you have a retail Note 3 from Verizon you will brick it if you flash a recovery other than safestrap. The bootloader will recognize the recovery is not stock, your knox will void you warranty and the phone will not boot. The only available recovery option for retail is safestrap.
shiftr182 said:
I had the same problem with Kingo initially. I don't remember how I fixed it, but it was a simple fix.... something stupid. Now it works with no problem.
Click to expand...
Click to collapse
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
rkmFL said:
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
Click to expand...
Click to collapse
Any luck with vroot?
I wish you could recall the "something simple" to make Kingo work. Where can I get "Safestrap?"
I just got a Verizon SM-900V with MJE yesterday. I need root to be able to use ARUnchained with my AppRadio 2. I tried Kingo, and it just kept switching between "connecting" and "downloading drivers" it never would connect to the phone. At this point, I'm not to concerned about custom ROMs, nor am I concerned about voiding the warranty. I just need to be able to obtain ROOT without bricking my phone. All of the threads on successful rooting of this device are from around November of last year. So, is there a way to successfully root any more? Thanks in advance!
please help.. I have 900v upgraded to 5.0.1....lost pics and voice recorded files...
please help with my note 3
rkmFL said:
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
Click to expand...
Click to collapse
I am looking to root my Samsung Galaxy S8 so I can access deleted camera and video files accidentally deleted. Was looking to restore via EaseUS Mobile Recovery software and it calls for the phone to be rooted first.
Any helps on best method is much appreciated.
Thanks.
If you want to root without unlocking the bootloader then you can try using KingoRoot's (not to be confused with KingRoot) one-click root app.
It's the simplest way and doesn't onvolve any major risks (other than those of rooting of course). If it can't root your device then it won't try, so there is no risk of bricking your device by rooting via its app. You can also remove root easily using it.
I tried KingoRoot initially first the app version and it states if that doesn't work to try the PC version, however I cannot find a download for the PC version anywhere. It seems even on KingoRoot's website the download for Windows has been removed and the download page says for information purposes only.
If you know of another place I can get the download for KingoRoot?
I wouldn't recommend the pc app. It's probably better if you do it yourself via magisk and twrp.
Any chance you could link me to a guide for that specific for my model of phone?
4ramsayc said:
Any chance you could link me to a guide for that specific for my model of phone?
Click to expand...
Click to collapse
you have the exynos variant or the snapdragon one?
Its the exynos variant
Wait you can't root without unlock bootloader, which in the process, will wipe your phone clean, so it kind of defeats the purpose.
Kingoroot and those stiff doesn't work since Android 6 (those are tech one thousand years ago)
4ramsayc said:
I am looking to root my Samsung Galaxy S8 so I can access deleted camera and video files accidentally deleted. Was looking to restore via EaseUS Mobile Recovery software and it calls for the phone to be rooted first.
Any helps on best method is much appreciated.
Thanks.
Click to expand...
Click to collapse
There are apps which can get deleted photos back without root. Also if deleted with google photos then you can get them back from the bin. If you're data is being backed up to any cloud storage service then you can most likely get it back from the bin.
Thanks for all your info