I have a Galaxy Ace...which came with Android 2.2
My partner rooted it and everything was fine. At the same time he upgraded to Gingerbread 2.3.3
But a couple of weeks ago he upgraded it to Gingerbread 2.3.6....and now it says it is root...but it doesn't have access to the root only apps....and it doesn't show the Superuser app that is needed.
Somehow it seems to be in some sort of limbo between unrooted and rooted.
I am well confused. Can anyone out there help please.
It looks like that the latest GB ROM used for the upgrade does not have the root.
You can add root to it. Before you do that, check by using terminal app with su command if the phone is rooted or not.
Sent from my Amazon Kindle Fire using Tapatalk
Thank you....it sounds a bit technical.
I will get my partner to read it in a while.
Although it sounded like I KNOW what I am on about...I am, in fact, a complete beginner when it comes to Android.
Updating from kies or from odin will make your phone unroot again. U need to reroot.
Sent from your phone
julado said:
I have a Galaxy Ace...which came with Android 2.2
My partner rooted it and everything was fine. At the same time he upgraded to Gingerbread 2.3.3
But a couple of weeks ago he upgraded it to Gingerbread 2.3.6....and now it says it is root...but it doesn't have access to the root only apps....and it doesn't show the Superuser app that is needed.
Somehow it seems to be in some sort of limbo between unrooted and rooted.
I am well confused. Can anyone out there help please.
Click to expand...
Click to collapse
a stock rom update resets your phone to most basic version..all things gone root,,clockworkmod etcc.....
u need to re-root follow this thread---
http://forum.xda-developers.com/showthread.php?t=1034145
happy rooting..
Root issue on Ace...
Hello all! I am Julado's partner. I had better explain what this is about in more detail here...
I took the original OS (Froyo) and updated it to Gingerbread (2.3.3) via Kies, I then used SOC to root it using ChainFire method - then installed and performed a TB back up. ALL Good - a few weeks later - I flashed an update using Odin to get 2.3.6 and an updated version of CF's kernel. At THAT point, CWM recovery had root access - but fully booted GingerBread had no SU app or returned root status via test command (both using a script and terminal). Sys info in settings shows 2.3.6 and ROOTED kernel image, but NO ROOT ACCESS is there in GB ~ Just in CWM Recovery.
I have re-flashed the CF kernel a few times and STILL have the same situation. I cannot understand why CWM has ROOT access but FULL 2.3.6 system doesn't.
Can anyone offer my any help please? Or possibly point out the blindingly obvious if I have missed what's clearly staring me in the face! Thanks.
So u already flashed ketut's cfroot kernel and still doesn't have root access in the rom? Thats weird.
Btw kernel name in system settings even if it said root doesnt mean your rooted. thats the build host of the kernel compiler.
Sent from your phone
When you are in GB, you can't root your ace via SOC. It will look success, but actually it's not. You have to root it using update.zip and flash via recovery. Just find it by googling.
Sent from my GT-S5830 using Tapatalk
an0nym0us_ said:
So u already flashed ketut's cfroot kernel and still doesn't have root access in the rom? Thats weird.
Btw kernel name in system settings even if it said root doesnt mean your rooted. thats the build host of the kernel compiler.
Sent from your phone
Click to expand...
Click to collapse
Thanks for the speedy reply!
I understand that the settings name is from build compiler. I have tested for root access with terminal and various apps (even tried downloading & installing SU app myself!!) - but don't understand why CWM DOES have root - but full OS doesn't!
I am truly baffled ATM!
mikeybaby72 said:
Hello all! I am Julado's partner. I had better explain what this is about in more detail here...
I took the original OS (Froyo) and updated it to Gingerbread (2.3.3) via Kies, I then used SOC to root it using ChainFire method - then installed and performed a TB back up. ALL Good - a few weeks later - I flashed an update using Odin to get 2.3.6 and an updated version of CF's kernel. At THAT point, CWM recovery had root access - but fully booted GingerBread had no SU app or returned root status via test command (both using a script and terminal). Sys info in settings shows 2.3.6 and ROOTED kernel image, but NO ROOT ACCESS is there in GB ~ Just in CWM Recovery.
I have re-flashed the CF kernel a few times and STILL have the same situation. I cannot understand why CWM has ROOT access but FULL 2.3.6 system doesn't.
Can anyone offer my any help please? Or possibly point out the blindingly obvious if I have missed what's clearly staring me in the face! Thanks.
Click to expand...
Click to collapse
Sits and grins at screen.....having absolutely NO idea what any of this post means
Would anyone like me to KNIT them an Android
hallidafykzir said:
When you are in GB, you can't root your ace via SOC. It will look success, but actually it's not. You have to root it using update.zip and flash via recovery. Just find it by googling.
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
I did get FULL root access after using SOC to root (chainfire method) GB - I rooted 2.3.3 with SOC, NO PROBLEMS! - THEN made TB (needs root) successfully. It was only after using Odin to flash 2.3.6 that SOC root resulted in the current quasi-rooted state.
I have tried re-flashing CF kernel both using Odin AND via CWM (update.zip) method - Neither worked = STILL BAFFLED???!
Related
is there an one click root 2.3.6 for the atrix? I tried the 2 programes but none of them seemed to work?
Same question here, thanks
http://briefmobile.com/motorola-atrix-4g-root
works for me with a locked bootloader.
There's also a voodoo root method that saves root before the update and restores root after the update.
gnahc79 said:
http://briefmobile.com/motorola-atrix-4g-root
works for me with a locked bootloader.
There's also a voodoo root method that saves root before the update and restores root after the update.
Click to expand...
Click to collapse
ok so now I screwed up and I am getting
svf 108 1:2
failted to boot 3
You got a failed to boot 3 using the fastboot preinstall method?? At which step did you get the error
Sent from my MB860 using XDA App
Ok, I'm on 2.3.4 and rooted using the instructions from brief mobile. I don't believe I have an unlocked bootloader. The only things I have done to the phone were original script from here for rooting (not one click), and then a modified version of it after the first Atrix update which had a before update and after update script to run.
Then, when upgrading to 2.3.4, I used the brief mobile/fastboot method to root it.
So, am I correct in thinking that to update the phone now I need to:
1. Download the update installer from Motorolla and update the phone to 2.3.6? (am I right that I the OTA update won't work or could cause a problem????)
2. Follow the instructions at Brief Mobile to root the phone.
Is this right, or should I wait a while before upgrading for things to be sorted out? The message popping up is irritating, but I can live with it if it avoids bricking my phone or having other problems.
Thanks
[Q] rooting help on 2.3.6
what is the proper way to root without unlocking the bootloader on 2.3.6 att?
http://briefmobile.com/motorola-atrix-4g-root
It still works
hdblab said:
http://briefmobile.com/motorola-atrix-4g-root
It still works
Click to expand...
Click to collapse
+1
Sent from my MB860 using XDA App
Root 2.3.6 one click
can someone upload a script or program that is one click root (not unlock) att atrix using 2.3.6?
http://forum.xda-developers.com/showthread.php?t=1505900
http://forum.xda-developers.com/showthread.php?t=1502735
http://forum.xda-developers.com/showthread.php?t=1500819
The preinstall method is real easy. If that is too challenging then maybe you should wait for someone to volunteer to provide a 1-click/batch script on their own rather than requesting(demanding) it.
sillyshyme said:
can someone upload a script or program that is one click root (not unlock) att atrix using 2.3.6?
Click to expand...
Click to collapse
I tried that before and I got soft booted.
Try again by using the instructions from the "Android-advice" website.
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Note: In those instructions specifically, it is important clarify that the phone should be in "fastboot" before entering in commands. Basically, do "step 6" before "step 4".
sillyshyme said:
I tried that before and I got soft booted.
Click to expand...
Click to collapse
do you need to undo the root on 2.3.4 before you upgrade to 2.3.6?
przemeknzb said:
do you need to undo the root on 2.3.4 before you upgrade to 2.3.6?
Click to expand...
Click to collapse
yes
btw, before you unroot 2.3.4. can you check if you have su, dosu and superuser.apk in /system/preinstall/ ? I'm not sure if I had those files when I was on 2.3.4, but I see them now on 2.3.6. I only removed the su related files as listed in the link when I was on 2.3.4, never removed su, dosu, etc from system/preinstall...guess it's not necessary for the 2.3.6 OTA to be successful on a locked bootloader.
I just rooted my Atrix after the OTA to 2.3.6 using this method. Worked perfect.
http://androidadvices.com/root-motorola-atrix-4g-45141-gingerbread-236-firmware/2/
no not had any of those files
tnedator said:
Ok, I'm on 2.3.4 and rooted using the instructions from brief mobile. I don't believe I have an unlocked bootloader. The only things I have done to the phone were original script from here for rooting (not one click), and then a modified version of it after the first Atrix update which had a before update and after update script to run.
Then, when upgrading to 2.3.4, I used the brief mobile/fastboot method to root it.
So, am I correct in thinking that to update the phone now I need to:
1. Download the update installer from Motorolla and update the phone to 2.3.6? (am I right that I the OTA update won't work or could cause a problem????)
2. Follow the instructions at Brief Mobile to root the phone.
Is this right, or should I wait a while before upgrading for things to be sorted out? The message popping up is irritating, but I can live with it if it avoids bricking my phone or having other problems.
Thanks
Click to expand...
Click to collapse
1) unroot 2.3.4 first:
http://androidforums.com/atrix-4g-all-things-root/423259-best-way-unroot.html
2) apply the 2.3.6 OTA update
3) redo the fastboot preinstall root method
btw before you unroot 2.3.4 can you check to see if you have su, dosu and superuser.apk in /system/preinstall? I see it now in 2.3.6 and am not sure if I had it there back when I was on 2.3.4
I didn't unroot before updating to 2.3.6 and now I can't get it to work. I keep getting the error "cp: write error: No space left on device", what should I do now?
Thanks.
sillyshyme said:
is there an one click root 2.3.6 for the atrix? I tried the 2 programes but none of them seemed to work?
Click to expand...
Click to collapse
what i did ...
UPDATE FROM STOCK 4.2.91 UNLOCKED BOOTLOADER AND ROOTED ATRIX 4G
try using OTA keeper from the market , before trying the OTA update , this is what i did
1 ) i unlocked my atrix 4g (2.3.4 all stock) with AUTOMATIC_UNLOCK_V4.2 and rooted with PetesMotorolaRootTools_v1.07 after that i installed CWM recovery
2 ) Make a Full backup of you rom using CWM and Titaniumbackup (never is enough)
3 ) MANY people say that using RSD LITE is not good , i just take the risk , because anyways the touch of my atrix is not doing good so i will be sending it to warranty soon anyways , i take the risk , i flash my atrix with RSD Lite 5.5 and this sbf
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
i don´t know any other people but i did not loose any data or apps from my atrix it was everything there , unlocked sign erased , CWM recovery partition erased , ROOT was there it is like everything go back to stock ... almost everything my data part was untoched.
4 ) download from the market OTA Root Keeper make a backup of your root and then press unroot temp
5 ) with that done I started to download and install the OTA update
6 ) after this point the phonewill reboot to stock recovery mode and start to upgrade it took almost 10 min to do the update after finishing copying files, it restarted 2 times on the moto logo then started booting , it take a longtime to pass the att boot image be patience mine took almost 5 min after that the phonestarted with everything loaded my apps , photos videos etc.
I think this could be a workaround (it work for me) for updating to .141 , also the baseband was updated to N_01.77.37P_usa_att
The only thing that was untoched was the webtop part , it stays on WT 1.2, ireally don´t use it , but i think if im already on 2.3.6 i can RDS the full SBF to get Webtop upgraded also the kernel say 2.6.32.9 is that the correct kernel for 2.3.6 i read that kernel is for a Froyo sbf not pretty sure
The thing now is , i wanna try installing CWM recovery and see if im already "unlocked" and try fruitcakes to downgrade 2.3.4 but i am not pretty sure about this i think i will get a brick
Also , you can try investigate to downgrade of wait for a generous dev to take out of the oven the fruitcake for 2.3.6 and try the method above
I TAKE no responsibility with this mini-tuto for anything that could happen to your atrix it on you own do this , i take the risk and it works !!!
thanks everyone
Greetings,
I rooted my note using Da_G's process which worked great. I then tried to "unroot" it using the kernel pda-odin-att-stock-kernel.tar and it appears to be still rooted (Titanum Backup still gets root privs). Do I need to flash the 400MB .rar to remove root?
Thanks,
Bugly
I believe you need to follow the instructions here: http://forum.xda-developers.com/showthread.php?t=1506330
Don't forget the factory reset at the end.
Thanks for the reply...
I did use that particular process but since I only flashed the kernel to root it shouldn't I only have to flash the stock kernel to unroot?
Bugly
bugly said:
Thanks for the reply...
I did use that particular process but since I only flashed the kernel to root it shouldn't I only have to flash the stock kernel to unroot?
Bugly
Click to expand...
Click to collapse
No because a kernal by itself doesn't provide root. If you read Da_G's original post it says that the kernal runs an auto-root script on /system. That is where the root takes place. That is why when you flash only the kernal your system is still rooted. You must flash stock system as well.
Okay... that explains it...
Thanks for the help...
One more question if I might... If I just flash the kernel does this set things up for a successful OTA upgrade?
Thanks...
It's only guaranteed you will get OTA updates if the phone is completely stock. Sometimes rooting alone will still allow you to get OTA updates, but from what I've heard, it's very hit or miss.
However, if the trend continues from what was done with the Samsung Captivate, then any serious update for the phone will be via Kies and not OTA anyway.
Had my S3 for a couple of months and had it rooted within the day I purchased it, ICS 4.0.4 using the ODIN CF-Root 6.4.
As it has been mentioned several times in the last few days the UK users have had a large update (mine was 79meg) to remove certain features.
Many people complained that the OTA update failed them and had to use Kies to do it however my OTA installed and worked perfectly however I lost root on my device, no biggy though I, I simply fired up ODIN and redid the root precedure..
Everything went fine except I no long have root, the 'about' on the phone lists me as 'modified' and I downloaded the updates for SuperSU but nothing seems to work anymore, no root required programmes ask super SU for root and its list is clear.
I have tried to uninstall the root required programmes (setCPU, titanium etc) but they instist I dont have root.
The only clue I can find is that CWM now errors telling me that the kernal is different and I need at least CF-ROOT 5.0 or better (when I am using 6.4)
Has anyone else come accross this problem, or is there a better root work around out there, do i need to put a different kernal version on the phone first?
Im not a total root newbie (long live the advent vega) but this one seems beyond me.
Have you tried using mskips Galaxy S3 Toolkit from the development section?
Sent from my GT-I9300 using xda app-developers app
I would redownload CFRoot from Chainfires thread and install .
jje
JJEgan said:
I would redownload CFRoot from Chainfires thread and install .
jje
Click to expand...
Click to collapse
Already downloaded a slughtly different version number and retried to no avail.
Will try a re root later to see if that sticks if not will try the other method...
Damn you work getting in the way.
I downloaded the full ROM from Sammobile, flashed using Mobile Odin and reapplied 6.4 with no problems.
Has not increased the counter, all official and Normal in settings.
Sent from the App that Time Forgot.
Hi,
i bought a Samsung Galaxy S3 GT-I9300 about two months ago, it's a Spanish device. I think the device came with 4.0.1 update of ICS, some weeks after buying it got 4.0.4 update and then using CF-Root 6.4 and Odin 1.85 managed to get root access so i was able to install busybox and UMS application from xda forums. So everything was working fine. Then, about 3 days ago i got an update notification which showed me a message which said "Updates will be provided in the request order preference" or something like this, i tried to update a few times more but no luck, i always got the same messages so i thought i had to wait for 4.1 update to get published but anyway everything was working fine.
The curious thing is yesterday ( August 25, 2012), when i woke up i noticed a firmware update was ready to be installed so went through it (without uninstalling CF-Root 6.4, supersu, etc.) but the strange thing was, after the update completed fine, went to settings to check the version and i saw it still/again was 4.0.4 version of ICS. Also noticed Google Play Books and Google Play Movies got installed so on one hand it seemed everything went fine cause new apps were there and everything worked as expected but on the other hand i think i already had 4.0.4 update installed on the device. Till that point one can think i got confused on the versions i got installed before the update and no major problem here. After that, as i already had root access on the device, i went to check if i still could run UMS app but it complained about missing root access so as i did before that last Android update took CF-Root 6.4 and Odin 1.85 to flash the device and get root access again (Without removing any previous install of CF-Root, super su, busybox, etc. ) but had no luck, so now it's not possible for me get root access again but i'm also still wondering how is it possible that today's update left the phone with the same Android version as before the update.
The only explanation i can find is the phone came with 4.0 version, first update got me to 4.0.1 and today's update guided me to the 4.0.4 but i'm still wondering why root access is not working as it should.
So my questions are, did i got confused about each version update? Then why can't i get root access again just repeating the same first process?
When opening busybox i can read "Not Enough Free Space in /system". Opening /system directory with Root Explorer i can read 1.05GB used, 436.39MB free. Is it right /system directory takes up to 1GB of the space? Why Busybox thinks there is 0.0MB free there?
Hope someone can help. Thanks in advanced!
Thousands of posts say OTA updates may fail if the phone is rooted .
Usual is to fail part way through an update ..
Suggest wipe the phone flash stock rom with Odin then root .
jje
JJEgan said:
Thousands of posts say OTA updates may fail if the phone is rooted .
Usual is to fail part way through an update ..
Suggest wipe the phone flash stock rom with Odin then root .
jje
Click to expand...
Click to collapse
Thanks a lot for the info. Am i going to loose installed apps, system settings, etc when doing the suggested process? Do i really need to wipe the phone before flashing the phone? I suppose i can find stock rom for my model here in the forums. Thanks!!
Hi,
i'm looking for a stock firmware for my SGS3 BaseBand I9300XXLH1 but i'm not able to find it. I think the firmware which came with my phone is unbranded and from Spain. But the question which i'm wondering is, do i really need to flash the phone? Isn't possible to solve the issue in another manner? After updating through OTA the rooted device, what's supposed to went wrong?
Lastly, what's wrong on updating a stock rooted firmware using Phone/Android update system? Don't understand how doing that can break the phone forcing me to wipe data and flash the phone.
Hope someone can help. Thanks a lot!
PD: After rebooting the phone in recovery mode i can see stock recovery has been installed with last update. Hope someone can make a bit of sense about it all. Thanks in advanced.
sibok said:
Hi,
i'm looking for a stock firmware for my SGS3 BaseBand I9300XXLH1 but i'm not able to find it. I think the firmware which came with my phone is unbranded and from Spain. But the question which i'm wondering is, do i really need to flash the phone? Isn't possible to solve the issue in another manner? After updating through OTA the rooted device, what's supposed to went wrong?
Lastly, what's wrong on updating a stock rooted firmware using Phone/Android update system? Don't understand how doing that can break the phone forcing me to wipe data and flash the phone.
Hope someone can help. Thanks a lot!
PD: After rebooting the phone in recovery mode i can see stock recovery has been installed with last update. Hope someone can make a bit of sense about it all. Thanks in advanced.
Click to expand...
Click to collapse
Get your firmware from here http://www.samfirmware.com/
then use odin to flash it, I had the same problem
Baseband is modem not firmware.
jje
Sent from my GT-I9300 using xda premium
Thanks to both for your answers. Maybe it's stupid but i'm some what more peaceful knowing other people also happened the same issue although it still feels very weird. All i did is flashing with CF-Root 6.4.
I've been looking for the stock firmware which is supposed to came with my phone at sammobile site but i'm not able to find it, although at that point ( where the phone got the same update twice, 4.0.4 ) i don't think i can trust the information provided by the phone. Under phone settings i can see Model Number is GT-l9300 and Base Band Version is i9300XXLH1 but i can't find it no sammobile site. What i find at sammobile site is I9300XXBLH1 ( notice B letter ) but i think that before this weird behaviour happened the phone showed Base Band Version I9300XXBLFB.
Is it all possible or the weird one is me?
Kickasskev, did you got 4.0.4 update twice?
Thanks again to all!
REPEAT BASEBAND IS NOT FIRMWARE nor is it firmware version .
To locate firmware try CHECKFUS .
Or stock providers roms from the sticky on XDA .
jje
sibok said:
Hi,
i bought a Samsung Galaxy S3 GT-I9300 about two months ago, it's a Spanish device. I think the device came with 4.0.1 update of ICS, some weeks after buying it got 4.0.4 update and then using CF-Root 6.4 and Odin 1.85 managed to get root access so i was able to install busybox and UMS application from xda forums. So everything was working fine. Then, about 3 days ago i got an update notification which showed me a message which said "Updates will be provided in the request order preference" or something like this, i tried to update a few times more but no luck, i always got the same messages so i thought i had to wait for 4.1 update to get published but anyway everything was working fine.
The curious thing is yesterday ( August 25, 2012), when i woke up i noticed a firmware update was ready to be installed so went through it (without uninstalling CF-Root 6.4, supersu, etc.) but the strange thing was, after the update completed fine, went to settings to check the version and i saw it still/again was 4.0.4 version of ICS. Also noticed Google Play Books and Google Play Movies got installed so on one hand it seemed everything went fine cause new apps were there and everything worked as expected but on the other hand i think i already had 4.0.4 update installed on the device. Till that point one can think i got confused on the versions i got installed before the update and no major problem here. After that, as i already had root access on the device, i went to check if i still could run UMS app but it complained about missing root access so as i did before that last Android update took CF-Root 6.4 and Odin 1.85 to flash the device and get root access again (Without removing any previous install of CF-Root, super su, busybox, etc. ) but had no luck, so now it's not possible for me get root access again but i'm also still wondering how is it possible that today's update left the phone with the same Android version as before the update.
The only explanation i can find is the phone came with 4.0 version, first update got me to 4.0.1 and today's update guided me to the 4.0.4 but i'm still wondering why root access is not working as it should.
So my questions are, did i got confused about each version update? Then why can't i get root access again just repeating the same first process?
When opening busybox i can read "Not Enough Free Space in /system". Opening /system directory with Root Explorer i can read 1.05GB used, 436.39MB free. Is it right /system directory takes up to 1GB of the space? Why Busybox thinks there is 0.0MB free there?
Hope someone can help. Thanks in advanced!
Click to expand...
Click to collapse
0. Remove all root apps from your phone.
1. Back up your rooted rom in cWM.
2. Use triangle away to get rid of the traingle.
3. Format system and cache.
4. Flash an official rom.
5. You should have all your apps + settings on a stock rom without the status being 'modified'.
victorator said:
0. Remove all root apps from your phone.
1. Back up your rooted rom in cWM.
2. Use triangle away to get rid of the traingle.
3. Format system and cache.
4. Flash an official rom.
5. You should have all your apps + settings on a stock rom without the status being 'modified'.
Click to expand...
Click to collapse
I've used checkfus and now i know my firmware.
Thanks for the step by step tips, but my phone is not rooted so i cannot use cwm, triangleapp and so. I. Annot also remove cwm manager nor supersu. I suppose i'll have to flash stock firmware first of all. Am i right?
Pretty strange, first time i rooted the device through cf-root6.4 it run flawlessly, but now i had to remove the battery after flashing ( while device was on ) and enter into recovery mode by hand which started the rooting process.
Thanks!
I've followed all the steps on the foru as to how to root my Tab (7510) but haven't gained root access. First, let me say that I've had my Galaxy Nexus phone rooted for more than 6 months so I'm not a noob to rooting.
I've successfully installed TWRP v2.2.0 recovery. Then, in TWRP I installed Samsung_Galaxy_Tab_10.1_root.zip. It successfully installed.
Once I reboot I see SuperUser and it will run. However, when I run Titanium Backup the app informs me that it can't obtain root access. I've also installed and run Root Checker Basic and it also says I don't have Root access.
Could it be that the zip file I installed was for Honeycomb? If so, where is the link to SuperUser for ICS?
Thanks for your help.
I have same problem. All seems to go well with Superuser app etc but root access fails.
P7510 Stock ICS 4.04
sapper29 said:
I have same problem. All seems to go well with Superuser app etc but root access fails.
P7510 Stock ICS 4.04
Click to expand...
Click to collapse
sapper,
I solved it. As I suspected, I was using the Honeycomb version of superuser which wouldn't root ICS. I found the ICS superuser here. I installed it via TWRP and was granted super user access. Good luck.
Brilliant - fixed it for me too.
Thanks so much
TWRP help
Where did you guys find the TWRP 2.2.0 that works with the P7510? I can't find anything to use for recovery mode on mine. I go the the TWRP site and I can only get the the 2.3 page and they only support the Tab7.7, not the 10
muddychief said:
Where did you guys find the TWRP 2.2.0 that works with the P7510? I can't find anything to use for recovery mode on mine. I go the the TWRP site and I can only get the the 2.3 page and they only support the Tab7.7, not the 10
Click to expand...
Click to collapse
take a look here : http://forum.xda-developers.com/showpost.php?p=36126353&postcount=997
2.3.3.0 should be working for the p7510
however, you can download it here : http://forum.xda-developers.com/showpost.php?p=31343407&postcount=131
Worked for me after installing the zip posted above