hi, I have a galaxy tab 2, I had to install chainfire 3d, when I rebooted my tab, is stuck in the logo, and now I've run out of battery, I try to charge my tab, but it not charging,just stuck on battery logo,and now i can't open my tab, I do not know what I should do, I really love my tab,anyone can help me please?..
Just let it charge for 2-3 hours and then flash a recovery (philz recommended/search the forums for it) , restore from a backup if you have, if not then download a ROM to your PC and stick it in an SD card, boot up in recovery and then select install zip -> choose zip for EXTERNAL SD card -> ***.zip file
thanks, but it did not work, I have charges my sg tab for 5 hours, but I can not boot to recovery mood, or download mood..
Sent from my GT-I9300 using XDA Premium 4 mobile app
It's work!!..thank you so much catalinjulia..i can use my tab again..thanks so much!!..:thumbup:
Sent from my GT-I9300 using XDA Premium 4 mobile app
I have solution
chamsoffi said:
hi, I have a galaxy tab 2, I had to install chainfire 3d, when I rebooted my tab, is stuck in the logo, and now I've run out of battery, I try to charge my tab, but it not charging,just stuck on battery logo,and now i can't open my tab, I do not know what I should do, I really love my tab,anyone can help me please?..
Click to expand...
Click to collapse
Do you want to help contact me in Facebook [email protected]
chamsoffi said:
hi, I have a galaxy tab 2, I had to install chainfire 3d, when I rebooted my tab, is stuck in the logo, and now I've run out of battery, I try to charge my tab, but it not charging,just stuck on battery logo,and now i can't open my tab, I do not know what I should do, I really love my tab,anyone can help me please?..
Click to expand...
Click to collapse
Kids these days... Chainfire 3D is only for Froyo and Gingerbread ROMs only and will brick any devices which are ICS/JB and later.
Tab 2 7" espressowifi stuck in boot after chainfire supersu
Can someone please tell me which chainfire supersu version I should use. I just installed the latest version with the latest TWRP and now I'm stuck in the boot animation for the latest lineageos rom- oct 2 nightly. This was my first supersu install on the device and research so far makes me think I should've used an older version. Everything was fine before the su install as I've been using the rom for days. I can get back to TWRP, so I should be able to flash another version with odin/adb... if a factory reset won't get it booted so I can download and flash another su version.
I wouldn't be in this situation if TWRP had saved my backup as a zip. Hopefully it's a setting that needs changing. I've used TWRP for years and it's always zipped backups by default when creating them. I wanted root so Root Explorer could access the directory where I could zip the backup folder while booted. Then I could install the backup when needed. I don't want to take the sd card out since it's mounted as adopted storage.
Thanks very much
jdl512 said:
Can someone please tell me which chainfire supersu version I should use. I just installed the latest version with the latest TWRP and now I'm stuck in the boot animation for the latest lineageos rom- oct 2 nightly. This was my first supersu install on the device and research so far makes me think I should've used an older version. Everything was fine before the su install as I've been using the rom for days. I can get back to TWRP, so I should be able to flash another version with odin/adb... if a factory reset won't get it booted so I can download and flash another su version.
I wouldn't be in this situation if TWRP had saved my backup as a zip. Hopefully it's a setting that needs changing. I've used TWRP for years and it's always zipped backups by default when creating them. I wanted root so Root Explorer could access the directory where I could zip the backup folder while booted. Then I could install the backup when needed. I don't want to take the sd card out since it's mounted as adopted storage.
Thanks very much
Click to expand...
Click to collapse
the latest version of chainfire's supersu is v2.82-SR5. you can download here https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
smart-t78 said:
the latest version of chainfire's supersu is v2.82-SR5. you can download here https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thanks I was able to flash supersu 2.74 with TWRP and that older version worked. The current version would not allow the tab to boot.
Related
I searched this forum a bit and I can't find a nice guide. I am currently running rooted .19 on my TF101, B70KAS. Is it as simple as dropping the ROM on my internal SD and letting it update to the latest Revolver release (based on .21)? Or can I do it with booting into recovery mode? This is my first tablet and I have no clowworkmod on my tablet... do I need to flash that somehow? Where's a guide?
thanks!
ninjai117 said:
I searched this forum a bit and I can't find a nice guide. I am currently running rooted .19 on my TF101, B70KAS. Is it as simple as dropping the ROM on my internal SD and letting it update to the latest Revolver release (based on .21)? Or can I do it with booting into recovery mode? This is my first tablet and I have no clowworkmod on my tablet... do I need to flash that somehow? Where's a guide?
thanks!
Click to expand...
Click to collapse
Since i am firm believer you need to learn what you are doing i will lay down the basics from there you are on your own.
1) read and study SU access
2) read and study SU access
3) read and study SU access
4) root
5) install clockwork recovery
6)download Revolver
7)verify the MD5SUM
8)boot into recovery
9)do a nandroid back up
10) do a factor reset via CWRI
11) flash the OS you want
12) reboot
13) enjoy
neidlinger said:
Since i am firm believer you need to learn what you are doing i will lay down the basics from there you are on your own.
1) read and study SU access
2) read and study SU access
3) read and study SU access
4) root
5) install clockwork recovery
6)download Revolver
7)verify the MD5SUM
8)boot into recovery
9)do a nandroid back up
10) do a factor reset via CWRI
11) flash the OS you want
12) reboot
13) enjoy
Click to expand...
Click to collapse
I am very familiar with CWM, flashing, nandroid backups, etc. I've had a nexus one for a long long time. I just can't find any good stickies on how to install CWM on my tablet, which I assume is my first step, though I find it odd there are no stickies. On the Nexus One forum there are lots! Where can I learn about installing CWM on my tablet with stock (but rooted) .19 FW?
ninjai117 said:
I am very familiar with CWM, flashing, nandroid backups, etc. I've had a nexus one for a long long time. I just can't find any good stickies on how to install CWM on my tablet, which I assume is my first step, though I find it odd there are no stickies. On the Nexus One forum there are lots! Where can I learn about installing CWM on my tablet with stock (but rooted) .19 FW?
Click to expand...
Click to collapse
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
I had the Same issue coming from the nexus s. the tricky bit is that rom manager does not support the transformer. I've got a galaxy tab 10.1 as well and flashing over a custom recovery was easy as pie.
anyway, what you have to do is this: http://forum.xda-developers.com/showthread.php?t=1213723
(http://forum.xda-developers.com/showthread.php?t=1093818)
then you need to install an app (i use reboot2recovery) from the marketplace to get into the custom recovery. i've tried quickboot or rom manager but all it does it take me to a black screen or reboot the device. reboot2recovery will actually drop you into clockworkmod recovery. from there, do your nandroid backup. you'll need an SD card in your transformer for it to actually go ahead with the backup.
aside: from my reading, the backup should backup to internal storage with that modded clockwork. i've never been able to get it to work though. anyway, just use an SD card for now so you can get through the difficult stuff.
so at this point uve done the following:
installed clockwordmod using the first 2 links and installed the reboot2recovery APK to get into recovery.
now you have an SD card in your transformer and you are doing a nandroid backup.
once completed, put the 200+mb revolver rom on the root of your SD card. you may also want to put another kernel. i use the one recommended by revolver.
now just wipe the cache, data, etc as usual. now flash the rom, reboot the system when completed. plug in your gmail account, wifi password etc. and then reinstall the reboot2recovery apk. now reboot to recovery and then flash the kernel. reboot and ure good to go. install revolver parts to allow for additional tweaking and OTA updating.
i got my transformer from bestbuy this thanksgiving and went to revolver 3.9.5 immediately. last night i actually flashed revolver 3.11 right over it. not a single problem.
edit: reading the above post, i remember that my FIRST recovery installation was using that one-click tool and, as was said, it works flawlessly. you still need the reboot2recovery though. and recoveryinstaller WILL NOT install the modified for internal storage version of clockwork. i'm thinking maybe i just havent tried backing up since updating to the internal storage version, which is why i think i've "never gotten it to work"
baseballfanz said:
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
Click to expand...
Click to collapse
Awesome, I had tried it earlier and it didn't do anything. Then I realized that my superuser app was FCing, however I could still use adb shell and su just fine! After I realized there was an update for the superuser app, I installed it. Everything is perfect now.
kramer987 said:
I had the Same issue coming from the nexus s. the tricky bit is that rom manager does not support the transformer. I've got a galaxy tab 10.1 as well and flashing over a custom recovery was easy as pie.
anyway, what you have to do is this: http://forum.xda-developers.com/showthread.php?t=1213723
(http://forum.xda-developers.com/showthread.php?t=1093818)
then you need to install an app (i use reboot2recovery) from the marketplace to get into the custom recovery. i've tried quickboot or rom manager but all it does it take me to a black screen or reboot the device. reboot2recovery will actually drop you into clockworkmod recovery. from there, do your nandroid backup. you'll need an SD card in your transformer for it to actually go ahead with the backup.
aside: from my reading, the backup should backup to internal storage with that modded clockwork. i've never been able to get it to work though. anyway, just use an SD card for now so you can get through the difficult stuff.
so at this point uve done the following:
installed clockwordmod using the first 2 links and installed the reboot2recovery APK to get into recovery.
now you have an SD card in your transformer and you are doing a nandroid backup.
once completed, put the 200+mb revolver rom on the root of your SD card. you may also want to put another kernel. i use the one recommended by revolver.
now just wipe the cache, data, etc as usual. now flash the rom, reboot the system when completed. plug in your gmail account, wifi password etc. and then reinstall the reboot2recovery apk. now reboot to recovery and then flash the kernel. reboot and ure good to go. install revolver parts to allow for additional tweaking and OTA updating.
i got my transformer from bestbuy this thanksgiving and went to revolver 3.9.5 immediately. last night i actually flashed revolver 3.11 right over it. not a single problem.
edit: reading the above post, i remember that my FIRST recovery installation was using that one-click tool and, as was said, it works flawlessly. you still need the reboot2recovery though. and recoveryinstaller WILL NOT install the modified for internal storage version of clockwork. i'm thinking maybe i just havent tried backing up since updating to the internal storage version, which is why i think i've "never gotten it to work"
Click to expand...
Click to collapse
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
It mean open your command prompt in your computer fire up the ADB server and type
Code:
adb reboot recovery
Why why not download the reboot recovery app from the market?
https://market.android.com/details?id=com.transformer.recovery
Sent from my Transformer TF101 using Tapatalk
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
Have you installed CWM recovery?
Rooting alone does not install CWM recovery.
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
thank you guyz i just needed to install cwm recovery, its just that those steps are not on any step by step , i can access now in to cwm recovery
Once in recovery it cant mount sd
SGS Dutchie said:
Once in recovery it cant mount sd
Click to expand...
Click to collapse
You have a micro sd card insert into the slot?
baseballfanz said:
You have a micro sd card insert into the slot?
Click to expand...
Click to collapse
Nope,thought it was the internal sd just like is shown in file explorer.
SGS Dutchie said:
Nope,thought it was the internal sd just like is shown in file explorer.
Click to expand...
Click to collapse
CWM only work with external card for now
Removable/MicroSD
baseballfanz said:
CWM only work with external card for now
Removable/MicroSD
Click to expand...
Click to collapse
Ah, I must go and search for one then.
baseballfanz said:
CWM only work with external card for now
Removable/MicroSD
Click to expand...
Click to collapse
Thx man, you really helped me out today. First with my root/cwm problem and now with this rom.
You really are a great help. Thx again!
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
HoPi` said:
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
Click to expand...
Click to collapse
Download a clean copy of Odin and install .
Auto Reboot is normal .
Root and Recovery TWRP
http://forum.xda-developers.com/showthread.php?t=1851548
Root and Recovery CWM
http://forum.xda-developers.com/showthread.php?t=1831173
jje
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet. But since this is getting off topic, I might be better off asking in other threads.
Thanks anyway!
HoPi` said:
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet.
Click to expand...
Click to collapse
Then you are not understanding instructions .
What is your intention .
Root or flash a stock rom .
Root via either method i posted .
Stock rom direct flash tar file via Odin.
ODIN flash is a tar not a zip.
Custom rom via a rooted phone with recovery zip file from ext sd card or sd card .
jje
Come on, the instructions are pretty clear boot in Odin Mode, click a button in Odin, let it restart, finished. The SuperSU zip file is from another guide, where the tar-file didn't include it. So I tried to manually install it via CWM (I think it was 6.0.2.7 or 8), but that didn't work either. Whenever the device reboots, Root Checker Basic runs for a few minutes and says "Sorry, the device does not have proper root access". If it helps, I used this guide:
http://www.android-hilfe.de/root-cu...ly-root-fuer-anfaenger-n8000-n8010-n8020.html
Even though it's in german, the screenshots are pretty obvious.
Sorry never ever seen any method with those sort of instructions.Personally not a clue what they mean .
I have used two methods as posted to root note 4 or 5 times. Rooted standard Samsung phones with cwm and root hundreds of times without any of those instructions.
Even run one standard cwm root via Odin to allow a specific rom install followed by a reroot using TWRP this afternoon .
jje
Sent from my GT-N8010 using xda premium
Thanks to Darkman, I finally got it. The problem was the current firmware update from Samsung. I reflashed with the version from January, followed his tutorial (like I did before - wow, after doing this 3-4 times, it certainly becomes second nature), and BAM, the device is rooted. Thanks anyway JJegan
hi folks,
Need information on how to load CM 10.1 Android 4.2.2 on my Samsung Galaxy S Plus.
Currently i have the CM 10 Beta 4 (JB 4.1.2) installed. Current recovery is Recovery-clockwork-5.5.0.4-ariesve.
I've downloaded these files.
cm-10.1-20130622-dev_connection_team-release2-ariesve.zip
DevCon-gapps-jb-20130622-signed.zip
cwm6032-Build2-ariesve-alireza7991.zip
Kernel_JB-4.2.2_3.4_20130622_Google-4.6_Stock_Signed.zip
When i checked the AriesDevCon team's link and XDA Wiki Samsung SGS+ link there was some confusion.
The Wiki link doesn't say anything about the recovery installation. Should i use Odin to install the CWM6032 or just put it in the SD card and reboot into recovery? I'd used Odin for the 5.5.0.4 recovery.
From the XDA forums on recovery (alireza7991's) saw that i could use Odin to install the recovery first.
Also, what do i do with the 3.4 kernel ? Should i load that too in the SD card before recovery mode for the installation?
My current kernel is 3.0.70.
Could someone with the proper knowledge please guide ? And please provide the exact steps and the files needed.
I've done the CM 10.1 already and it worked pretty well, but was not able to do any upgrade later (to release 2.5 etc). Had my phone soft-bricked two times and had to install the stock Gingerbread ROM to come back to JB 4.1.2 ROM.
regards,
Anoop
The files you got are .ZIP files.
It should be possible to flash these using the recovery. I have To check back for further instructions cause i'm not familiar with the s+ but cwm should be installed automatically when the kernel has be installed.
Sent from my GT-I9100 using xda app-developers app
Did it work?
Sent from my GT-I9100 using xda app-developers app
Hey dude...u must wipe data,dalvik....maybe it can help u...
Sent from my HTC ChaCha A810e using xda app-developers app
lil.masoud said:
Hey dude...u must wipe data,dalvik....maybe it can help u...
Sent from my HTC ChaCha A810e using xda app-developers app
Click to expand...
Click to collapse
You have to wipe data and cache, wiping dalvik cache is useless.
anoopgkris said:
hi folks,
Need information on how to load CM 10.1 Android 4.2.2 on my Samsung Galaxy S Plus.
Currently i have the CM 10 Beta 4 (JB 4.1.2) installed. Current recovery is Recovery-clockwork-5.5.0.4-ariesve.
I've downloaded these files.
cm-10.1-20130622-dev_connection_team-release2-ariesve.zip
DevCon-gapps-jb-20130622-signed.zip
cwm6032-Build2-ariesve-alireza7991.zip
Kernel_JB-4.2.2_3.4_20130622_Google-4.6_Stock_Signed.zip
When i checked the AriesDevCon team's link and XDA Wiki Samsung SGS+ link there was some confusion.
The Wiki link doesn't say anything about the recovery installation. Should i use Odin to install the CWM6032 or just put it in the SD card and reboot into recovery? I'd used Odin for the 5.5.0.4 recovery.
From the XDA forums on recovery (alireza7991's) saw that i could use Odin to install the recovery first.
Also, what do i do with the 3.4 kernel ? Should i load that too in the SD card before recovery mode for the installation?
My current kernel is 3.0.70.
Could someone with the proper knowledge please guide ? And please provide the exact steps and the files needed.
I've done the CM 10.1 already and it worked pretty well, but was not able to do any upgrade later (to release 2.5 etc). Had my phone soft-bricked two times and had to install the stock Gingerbread ROM to come back to JB 4.1.2 ROM.
regards,
Anoop
Click to expand...
Click to collapse
It is not necessary to install recovery before every ROM installation. CWM 5.5.0.4 is a stable and safe recovery for our device.
According to the kernel i recommend you to use K^Kernal 3.4.x. It is more battery friendly with good performance.
The procedure is as explained in there
1. Boot in to recovery and
2. flash CWM 6.0.3.2 (if you want to, otherwise skip this) and reboot in to recovery.
3.Wipe data(not necessary when you are coming from a previous build of the same ROM, but recommended), wipe cache, and wipe dalvic cache
4. Flash ROM, Flash Gapps and flash kernel and reboot,
You are done.!
[SOLVED] How to install CyanogenMod 10.1 on my Samsung Galaxy S Plus
Hey folks,
Thanks to all of you for the kind advises!
In fact, i checked for any reply one hour after posting my question and only H3llwar's one reply was visible.
Was too impatient and thought to go ahead with the Modding.
First tried to flash the latest recovery cwm-emmcbrickedpatch-ariesve-6.0.3.2-alireza7991.img using Odin.
This one stuck at one stage (<1> recovery.img download) and didn't move further. So disconnected the USB and removed the battery (I forgot though in what sequence). I expected this to happen since it had happened two times before when trying to flash a non-tar recovery. Also I expected my phone to be soft-bricked, but luckily it did'nt. :good:
Then went through some more info on XDA and other forums and found a WORKED.rar solution.
from http://forum.xda-developers.com/showpost.php?p=30015714&postcount=22
Used that AriesVE.ops version and the recovery-clockwork-6.0.1.0-ariesve.tar.md5 and was able to flash the new recovery.
The reason i flashed the new recovery is that because i always used to find on these forums to use a specific recovery for a specific ROM.
Anyway, then i loaded the CM 10.1 and Gapps into the SD card, set debugging mode on and restarted in Recovery mode.
Then backed up data (Nandroid). Then wiped data/factory reset and wiped cache partition.
Then asked recovery to install from zip card selecting the CM10.1 ROM followed by Gapps. These processes happened very fast this time.
Then rebooted and there it was, a new magenta Cyanogen footer logo along with with the Samsung logo.
Skipped the initial parts and went to the About Phone section with the Android 4.2.2 indication.
Was very happy to also see my Kernel updated to 3.4.49. Three days now on the new ROM and loving it, battery life improved by at least 5% (from the 4.1.2). But missing the 4.1.2 fonts for the clock etc. Although the other internal fonts are smoother and easier on the eye.
Pasting the info screenshot here.
anoopgkris said:
Hey folks,
Thanks to all of you for the kind advises!
In fact, i checked for any reply one hour after posting my question and only H3llwar's one reply was visible.
Was too impatient and thought to go ahead with the Modding.
First tried to flash the latest recovery cwm-emmcbrickedpatch-ariesve-6.0.3.2-alireza7991.img using Odin.
This one stuck at one stage (<1> recovery.img download) and didn't move further. So disconnected the USB and removed the battery (I forgot though in what sequence). I expected this to happen since it had happened two times before when trying to flash a non-tar recovery. Also I expected my phone to be soft-bricked, but luckily it did'nt. :good:
Then went through some more info on XDA and other forums and found a WORKED.rar solution.
from http://forum.xda-developers.com/showpost.php?p=30015714&postcount=22
Used that AriesVE.ops version and the recovery-clockwork-6.0.1.0-ariesve.tar.md5 and was able to flash the new recovery.
The reason i flashed the new recovery is that because i always used to find on these forums to use a specific recovery for a specific ROM.
Anyway, then i loaded the CM 10.1 and Gapps into the SD card, set debugging mode on and restarted in Recovery mode.
Then backed up data (Nandroid). Then wiped data/factory reset and wiped cache partition.
Then asked recovery to install from zip card selecting the CM10.1 ROM followed by Gapps. These processes happened very fast this time.
Then rebooted and there it was, a new magenta Cyanogen footer logo along with with the Samsung logo.
Skipped the initial parts and went to the About Phone section with the Android 4.2.2 indication.
Was very happy to also see my Kernel updated to 3.4.49. Three days now on the new ROM and loving it, battery life improved by at least 5% (from the 4.1.2). But missing the 4.1.2 fonts for the clock etc. Although the other internal fonts are smoother and easier on the eye.
Pasting the info screenshot here.
Click to expand...
Click to collapse
You tried to flash .IMG recovery file via Odin. That won't work.! You need a .tar or .tar.md5 file to flash via odin.
Sent from my GT-I9001 using xda premium
Good battery life - CM 10.1
Hey Jabrief, thanks for the advise, I'll note it.
Until now, CM10.1 - 4.2.2 is running very smooth on my SGS+. Getting a very good battery life too. GPS is somewhat slow but maybe it's because odd the cloudy weather all the month.
Attaching a battery stats pic.
Got 32 hours and 40 mins on single charge.
About 16 mins of call, 45 mins of browsing in all.
thanks,
Anoop
Hello,
I have a Samsung galaxy tab 2 (p5110), with root and clockwork recovery.
When i wan't to install a rom (made for p5110) i get the error (status 7) even when i alter the file with notepad or if i 'toggle signature vertification.
I have tried it with mutiple ROMS (like slimrom) but they all don't work.
Can someone please help me?
Try updating your recovery, allot of the new roms are running Kitkat and if your recovery is outdated it won't work.
Pp.
I have ROM manager clockworkmod 6.0.2.7 witch should be the latest version.
I also have ROOT, so i don't understand why no rom will install on my tab...
Any progress with your tablet?
Pp.
No, it still doesn't work
Here is exacty what I do:
- Download a ROM (from XDA) for the P5110
- Put the ROM on a SD card (in the samsung tab)
- Boot into clockwork recovery (version 6.0.2.7)
- Install from external SD card
- Get error 7 (even if I put verification signature on)
Witch forces me to re-install my backup of android 4.2.2 samsung tab 2
I must be doing something wrong, but i can't figure out what...
Thanks for the help
Looks like the rooting method doesn't really went well.
What you're doing isn't wrong in my opinion.
You could try to reroot the tab.
Might wanna install original firmware with odin and start the progtess again.
But when I use rootchecker, it says my tablet is rooted, also most of the root apps work (like Greenify, xposed installer apps, SuperSU)
I rooted it some time back, using something like cappuchino (??, it was some time ago hahaha).
If i must do it again, what guide to root do you use personally?
Thanks
mennogabler said:
But when I use rootchecker, it says my tablet is rooted, also most of the root apps work (like Greenify, xposed installer apps, SuperSU)
I rooted it some time back, using something like cappuchino (??, it was some time ago hahaha).
If i must do it again, what guide to root do you use personally?
Thanks
Click to expand...
Click to collapse
Normally I look at the Zedomax movies on Youtube.
When i had a Sammy tab (i thought it was the p7500?) I remember rooting it by some of the Zedomax (HighOnAndroid) movies on youtube.
It is strange that rootchecker etc says you are rooted.
You can try to return to stock and like i said before reroot everything. But... could it be that you are on a current bootloader wich is not the same as the rom you are trying to install ?
Sent from my SM-G900F using XDA Free mobile app
I have tried ALL the ROM's from XDA for p5110...
Witch bootloader do you recommend?
Why put rom on external SD card?
Typical download goes to internal, select from internal not external. Forget about the external, typically I move stuff I don't want to erase to external but not roms or gapps.
Pp.
Here is a screenshot of the last ROM & gapps I installed.
These downloaded straight to SD card (internal) typical instructions from developers is to (download and install from internal.)
Try it, you might like it. ? ?
Pp.
tried to install another rom from XDA (for p5110) kitkat from internal sd
Still doesn't work...
Here a screen:
Check your downloads make sure your downloading for your specific model, make sure you have a P5110 ?
Pp.
Downloads are specificly for p5110
I'm sure i have GT-P5110, see photo.
??? Running out of suggestions, maybe try installing a stock rom.
Look in original development.
Pp.
hahaha just my luck...
Where can i find stock roms?
Try Google xda has no original development for GTAB 2..
Just check the dates, don't d/l old stuff.
Pp.
While you're running the latest OFFICIAL CWM for this tab, it is too old to flash a KitKat ROM. But there are newer unofficial versions that work just fine.
Update recovery from here:
http://forum.xda-developers.com/showthread.php?t=2548476
Sent from my Nexus 4 using XDA Premium HD app
I did it
I unrooted it, and then rooted it again with philz clockworkmod recovery
After that, it wanted to install slimkat build 8.0 (official) just fine (android 4.4.4) and it runs smooth!
Thanks for all the help!
was rooted on lollipop, tried to update to 2.2 but i think i installed the wifi version (i am an lte owner) tried to put the aosp rom on since i needed to wipe and start fresh anyways. Now i am on the aosp rom which changed my recovery the recovery that loads doesnt mount the sd card (and doesnt see the internal storage). I figure if i can just get back to another recovery i should be able to get back on track.
Scoobydumb said:
was rooted on lollipop, tried to update to 2.2 but i think i installed the wifi version (i am an lte owner) tried to put the aosp rom on since i needed to wipe and start fresh anyways. Now i am on the aosp rom which changed my recovery the recovery that loads doesnt mount the sd card (and doesnt see the internal storage). I figure if i can just get back to another recovery i should be able to get back on track.
Click to expand...
Click to collapse
Are you rooted? if so, with flashify, flash another custom recovery. I'd recommend TWRP 2.8.5.0. Its here, http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117/ and its on the latest posts as zip attachment (you need to extract the zip, because it contains an *.img).
If not, (I have not tried this because I haven't got the need to do it)
you can flash TWRP 2.8.5.0 via fastboot, but you need to unlock the bootloader.
problem is i dont have gapps installed so unable to use flashify. When i try to use adb to install them i get error closed
then waiting for device.
tablet is showing in device manager as google galaxy nexus adb interface
so i believe drivers are installed correctly.
Scoobydumb said:
problem is i dont have gapps installed so unable to use flashify. When i try to use adb to install them i get error closed
then waiting for device.
tablet is showing in device manager as google galaxy nexus adb interface
so i believe drivers are installed correctly.
Click to expand...
Click to collapse
You could do the second solution. But I have never done it, so I cant help you with that, just with what I theoretically know.