Related
Hi,
I tried doing the Oneclick root with my Epic that is running 2.1 Eclair. When I installed Titanium and busybox it said phone is rooted. BUT when I start the phone in Manual mode to install update it only has 4 options:
Reboot
Install update
Wipe data
Wipe Cache
When I scroll down and select Install update it starts the process and then says e.signature verification failed update aborted. Is there something I am not doing right? I tried to unroot and reroot the phone but still get the same thing.
When I try the Root process with Oneclick Software for Samsung Galaxy One Click root it says the phone will restart and to select reinstall packages but I do not have that option. It still has the options shown above.
I know when I did my Hero and Evo I could get root and install Roms with no problems.
Can someone help please.
From reading you just need to install clockwork and then install roms and stuff. The kernels include a root, so install clockwork and install the rom I have in my signature. It already includes a kernel so that helps by one less thing you have to do. The one in my signature I have had no issues at all.
I installed rom manager (which is clockwork, right?) and tried to install a rom that way but when it reboots it goes to the same screen and gives the same message.
KateC1 said:
I installed rom manager (which is clockwork, right?) and tried to install a rom that way but when it reboots it goes to the same screen and gives the same message.
Click to expand...
Click to collapse
How are you rebooting into recovery? It sounds like you're hitting the stock recovery. Shut the phone down entirely and hold Vol -, Camera, and power. Keep holding until after the Samsung logo goes away.
Does this bring you more options?
If you still get nothing, try this instead
http://forum.xda-developers.com/showthread.php?t=808103
Nope.... Same options. I will read the link you provided.
Also, Busybox says that my phone is rooted then I click install and it says I do not have nand unlocked. Maybe this is the problem?
KateC1 said:
Nope.... Same options. I will read the link you provided.
Also, Busybox says that my phone is rooted then I click install and it says I do not have nand unlocked. Maybe this is the problem?
Click to expand...
Click to collapse
I might be wrong here, but I'm pretty sure getting nand-unlocked is a part of the rooting process. Perhaps the root didn't work entirely for you, I had a lot of problems using the 1 click root with my first epic because of timing, I had to open the batch file and replace the ping 127etc (the delays) with a pause command because the phone took too long to respond and the second half of the rooting process would fail. Try the link I posted, it worked out well on my first phone.
Thanks....So far I have removed the Oneclick root from it and now it says the phone is not rooted. My next step is to root again... Hope it works.
Worked great! Thank you!!!
KateC1 said:
Worked great! Thank you!!!
Click to expand...
Click to collapse
Awesome, Glad to hear you're up and running, Now you get to do the fun stuff (roms!!!!)
Yup.... Already got my Rom of choice installed and happy... Did not take long at all.
All I've done to it was root it a few days ago. Today I started getting FC's on Instagram, so I rebooted it. Now it is stuck on the GT7+ boot screen, will not go past. I can reboot it, but nogo. Recovery loads, but then it reboots. I CAN get into download mode though.
After searches here, I'm downloading Kies and Odin3-v1.85.zip.
What else do I need? Do I need a file from here: http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-T869&r=5#regiona
??? If so, which one? It's the U.S. T-Mobile 4g GT7+...
Thanks for any help!!! I'm hoping to fix it in the next hour or so before I go to work...
I *can* get to the Power + Volume Down update screen. I am DL'ing the firmware now. What do I do once I get it, how, exactly, do I update/recover it?
Also,
When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application...
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
:crying:
Fixed! It took a lot of work, but I got it. So, here is the question...
I rooted the other day, no custom ROM at all. Could this have been due to that root? That's all I can think of that might have caused this issue. I want to root again, but not sure if I should.
Thoughts?
(and before it's said, yes, it did recover, but I don't want to have to recover it again)
VisualOddity said:
Fixed! It took a lot of work, but I got it. So, here is the question...
I rooted the other day, no custom ROM at all. Could this have been due to that root? That's all I can think of that might have caused this issue. I want to root again, but not sure if I should.
Thoughts?
(and before it's said, yes, it did recover, but I don't want to have to recover it again)
Click to expand...
Click to collapse
Rooting in itself will not cause this as all root is is adding the su binary file to the system bin folder. It doesn't do anything except give you permission to access system folders. Did you also install a custom recovery too? A bad install of a custom recovery could possibly cause it to hang at reboot.
kzoodroid said:
Rooting in itself will not cause this as all root is is adding the su binary file to the system bin folder. It doesn't do anything except give you permission to access system folders. Did you also install a custom recovery too? A bad install of a custom recovery could possibly cause it to hang at reboot.
Click to expand...
Click to collapse
Nope. All I installed root related were Busy Box and Super User so I could use Titanium Backup...
Did you use titanium to remove anything?
Enviado de meu MB525 usando o Tapatalk 2
There was a thread in here about some people having problems with busybox though I have never experienced any problems with it. With so many different versions of this device it possible it could cause problems for some of them.
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
pedrohell said:
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
Click to expand...
Click to collapse
Welcome to the club. Take a look at all the sections for the tablet and make sure you read the stickies too.
Method #2 and youl be good to go.
http://forum.xda-developers.com/showthread.php?t=1831152
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
Let me ask you this, why no flashing? As far as I know it's either Odin or flash. You need to get a custom recovery on it in order to root.
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Also with the s2 the recovery and kernel are in one. This is not.
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
No problem, but it don't get any easier than odin or recovery.
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
There was an Exynos exploit method but Samsung patched the security hole a few updates ago.
The method in the link that was posted does alter your flash count and that can be correct but you are the owner of the device and if you are not comfortable flashing you tablet I wouldn't.
I have flashed mine and tried a few rom's but I always ended up resetting my flash counter and going back to stock.
Folder mount works great and that was the reason I rooted in the first place but you can store your files on the ext drive and transfer them back and forth manually but I found with my fast wifi I'm better off re-downloading the data along with "Helium - App Sync and Backup" to backup and restore my data and you do not need root, only draw back is that you have to have a computer connection for backup and restore to work.
.
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
I don't think you read that right. You're not flashing a ROM, just a custom recovery through ODIN, then a root app. It's actually very simple. (Any simpler and I would be concerned about rogue app exploits)
Fyi: I'm also new to Samsung devices and bought my tablet this week. Rooted it this morning by following the stickies, but sticking with the stock ROM for now. I'm more than happy with the tablet so far.
Sent from my GT-N8013 using xda app-developers app
pedrohell said:
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
Click to expand...
Click to collapse
There is no flashing a rom with method 2. You Odin the custom recovery then you have to flash the superuser into the system. You need superuser to get root and Odin is the easiest way.
Trust me we have all been in your shoes about being nervous, I've been doing this a long time and this method is really easy.
You can also use this method - http://forum.xda-developers.com/showthread.php?t=1957002
It does require ODIN but as has been stated this is the norm. You are not replacing any kernels or flashing another rom, you are just adding the root components. Using this method also leaves stock recovery intact...
If you woory about flash counter then run triangleaway after to reset the flash counter and recoveries....
I found doing this, doing a factory reset from settings then reflashing the Stock rom using Mobile ODIN pro gave me a stock standard, but rooted, rom with all statuses "Official" and 0 flash count....
A lot of work I know but then worthwhile things generally require it...
Ok, I followed the Method 2 made everything like on video, after pressing Power+Volume Up, I entered on STOCK Recovery, not the CWM,even so, I apply the .zip and I get:
MANUAL MODE
--Appling Multi-CSC....
Applied the CSC-code:LUX
Successfully applied multi-CSC.
--Install /sdcard....
Finding update package....
Opening update package....
Verifying update package.....
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:signature verification failed
I also retryed and turned off auto-reboot in Odin before starting the process but I get the same thing, now what should I do?
Its not rootable?
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
I see that I'm probably too late now to answer the OP.
But maybe others can be interested.
I find that the easiest way to root (without odin and without installing a custom recovery) is Framaroot.
It uses some Exynos exploits, and has been also recently updated by the developer to counteract Samsung's patches.
It may work or it may not work on some devices and with some of the more recent firmware.
In any case giving it a try doesn't cost anything. It's just an app.
If it works the app can also be used to temporarily remove the root.
For me it worked with Firmware N8000XXCLL3 and I know that it works with some more recent fw too.
Furthermore it doesn't change the counter and even the Devices Status remains "Official". Well, actually the devices status may change to "Custom" after few days with the tablet on, but it returns Official after a simple reboot.
pedrohell said:
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
Click to expand...
Click to collapse
Awesome to hear! I ran into the same thing you did, forgot to go straight to recovery from odin.
Enjoy!
Stuck
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
What were your options on the page right before that? What option did you select to initiate that?
Maybe try using the files from here instead:
http://droidviews.com/2013/root-and...ung-galaxy-note-10-1-n8000-n8010-n8013-n8020/
bigtoysrock said:
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
Click to expand...
Click to collapse
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
brix696 said:
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
Click to expand...
Click to collapse
I would use the touch cwm, and what rom are you trying to install?
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Maybe if you could give some more detail about what exactly you can and can't get the phone to do, what screens can be accessed, and what you did that lead to this condition, we could offer some advice.
Also, no offence to the devs, but twrp is the devil lol. Most issues I have had in the past have led back to it in one way or another, so I never use it. (Just my opinion)
Tappin G2 Style
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
kungpowchicken said:
Everything is screwed for me. I can't even RSD back to stock. I can access TWRP, but can't wipe System or Data. Fastboot is just there and won't actually push anything. I already have a Moto X now, and I was talking about this issue about a week ago on the Android Development subcat, but I thought I would give it one last go on here to see if I can at least make it a backup.
Click to expand...
Click to collapse
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
scoobaspeaz said:
Is it this problem?: http://forum.xda-developers.com/showpost.php?p=47558893&postcount=47
If so use this solution: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Click to expand...
Click to collapse
Nope, my status us unlocked: 3. But when I get home, I'll try the mfastboot instead if fastboot.
kungpowchicken said:
I can get to the Fastboot screen, I can access TWRP, and I can get the phone to bootloop at the boot animation screen.
I can't push anything through ADB or Fastboot, I cannot mount data or system in TWRP or otherwise. RSD comes back failed every time with every single stock build I use.
Literally two weeks ago, I was in bed, watching TV, with the phone charging. I unlock it to see if I had any notifications, and it kept saying that Nova launcher FC'd. So logically, I rebooted my phone and that's when it started boot looping.
I did nothing to the phone for a couple of hours, it was on the official CM 10.2 11/9 build. I had that ROM running fine for at least 24 hours before it went FUBAR.
Click to expand...
Click to collapse
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
bweN diorD said:
i made a modified utility to fix the partition error but need someone to test it please. it should do the process previously suggested automatically through the script.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
Testing now.
UPDATE: Still no go.
kungpowchicken said:
Testing now.
UPDATE: Still no go.
Click to expand...
Click to collapse
Well that sux.
Your problem is different than what I made this for but I was hoping it would work for you.
What did it do, fail all the way through?
When I tested it on my phone it reported flashing the partitions ok. There was actually extra text displayed while it was doing it that I didn't put into the script, that's how I knew it was working.
Tappin G2 Style
Failed all the way.
kungpowchicken said:
Failed all the way.
Click to expand...
Click to collapse
im running out of suggestions
if you havent tried to put stock recovery back on yet, how about we try that and see what happens.
if you dont know how to do it through adb, just grab the 1.34 utility from the dev forum, it will push it through fastboot.
something is obviously wrong with twrp, maybe we can fix that first.
I tried flashing even the stock Recovery manually and through the 1.34 utility. Always comes up failed. :sad:
Did you try the manual steps that I posted in my links?
i hope that works, but im doubtful.
the utility essentially flashes exactly as you would manually.
he doesnt have a partition issue, im guessing something is wack with the permissions.
if twrp somehow screwed up the permissions to read only, i believe even the partition file cant overwrite it. i could be wrong.
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
kungpowchicken said:
So I think it has something to do with the Permissions of one or more of the partitions. I just noticed it keeps saying Permissions Denied when I try to fastboot or mfastboot.
Click to expand...
Click to collapse
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
penser said:
Are you sure you have the snapdragon fastboot? Can't hurt to reinstall it.
Sent from my MB886 using Tapatalk
Also have you tried flashing it manually? (fastboot flash system system.img, etc.)
Click to expand...
Click to collapse
he defiantly has the right fastboot, its in the utility that has been downloaded thousands of times.
if its write protected some how, its not going to flash no matter how you try it.
what i was wondering is if recovery can fix permissions that deep, not sure he said he tried that.
What do you mean with recovery?
kungpowchicken said:
What do you mean with recovery?
Click to expand...
Click to collapse
go into twrp, advanced (i think thats the right section) and look for a line that says "fix permissions" and do it.
Keeps saying it can't mount anything.
kungpowchicken said:
Keeps saying it can't mount anything.
Click to expand...
Click to collapse
thats what i figured would happen
Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?
jimbub said:
Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?
Click to expand...
Click to collapse
I always selected yes, jsut in case. But I made the jump to official TWRP and no longer get that nag. Maybe check that out. To me its better, esp since its 100% working now.
jimbub said:
Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?
Click to expand...
Click to collapse
I've been getting the same issue since rooting. Root seems to work just fine regardless (can write to /system and everything.)
From what I can tell, it's an issue with the permissions on the su binary. The permissions are rwx-r-x-r-x where as they should be rws-r-x-r-x (setuid bit set.) The easiest way to check this on your device is through the rootchecker app. You can try and manually change the permissions but they don't stick, and I haven't found anybody else with the problem or a solution.
I used to get this on twrp on my s4 and with cwm on this device as well. Always selected no and everything was fine.
Sent from my HTC6525LVW using Tapatalk