Hi.
I have a Nook Tablet (16gb version) with which I have a problem.
Once upon a time (couple summers ago), I decided to flash another touchscreen firmware through the Touchscreen Firmware Flasher app included in the KK version of LiquidSmooth, unofficial build for NT. I had just changed the glass part of the screen, so I was looking forward to using my tablet for months to come.
The problem is that the flasher app crapped out on me and force closed in the middle of the installation, leaving me without a usable touch driver. I have tried using SD-boot ROMs and I believe they have done nothing for me. I flashed many ROMs, including MIUI, stock and CM 10.1.3, with no result other than a successful boot. But still no touch input.
I talked to demetris about this (seemed like a good idea) and he gave me many tips. Essentially, all I have to do is run a script after placing a file in /system/etc/firmware and it should be fixed. Alas, this has not worked. I shall include a screenshot of the error.
I am now in possession of a Nook Tablet with a screen that will not respond to touch at all, but can boot standard CM 10.1.3, TWRP and CWM. I used the ADB included in TWRP for the procedure, and nothing. This is probably something that has to be done from within the system, so...
Is it possible to add a line in build.prop saying "ro.secure=0"? I read online that this will disable secure ADB (remove the need for RSA key approval) so that I may run the script?
UPDATE: I made a breakthrough. I am currently trying to put this script into a flashable zip. The part I still can't do by myself is the updater-script. It's mostly working but the recovery says the zip is bad. The exact thing is in the thumbnails below.
If anyone can use Edify (Recovery Script Language) and at least give me some tips, I'd be grateful. Thanks for checking!
TheAnonymusModUser said:
Hi.
I have a Nook Tablet (16gb version) with which I have a problem.
Once upon a time (couple summers ago), I decided to flash another touchscreen firmware through the Touchscreen Firmware Flasher app included in the KK version of LiquidSmooth, unofficial build for NT. I had just changed the glass part of the screen, so I was looking forward to using my tablet for months to come.
The problem is that the flasher app crapped out on me and force closed in the middle of the installation, leaving me without a usable touch driver. I have tried using SD-boot ROMs and I believe they have done nothing for me. I flashed many ROMs, including MIUI, stock and CM 10.1.3, with no result other than a successful boot. But still no touch input.
I talked to demetris about this (seemed like a good idea) and he gave me many tips. Essentially, all I have to do is run a script after placing a file in /system/etc/firmware and it should be fixed. Alas, this has not worked. I shall include a screenshot of the error.
I am now in possession of a Nook Tablet with a screen that will not respond to touch at all, but can boot standard CM 10.1.3, TWRP and CWM. I used the ADB included in TWRP for the procedure, and nothing. This is probably something that has to be done from within the system, so...
Is it possible to add a line in build.prop saying "ro.secure=0"? I read online that this will disable secure ADB (remove the need for RSA key approval) so that I may run the script?
Click to expand...
Click to collapse
Did you see this thread?
nmyshkin said:
Did you see this thread?
Click to expand...
Click to collapse
Yes, I did. I tried booting off an SD card and the screen still would not respond at all.
Related
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
psychoticdemon said:
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
Click to expand...
Click to collapse
The kernel is incompatible with your phone.
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
psychoticdemon said:
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
Click to expand...
Click to collapse
kernel is for mango??unofficial port right...can you provide the rom link once.....??
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
psychoticdemon said:
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
Click to expand...
Click to collapse
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Dark Wraith said:
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Click to expand...
Click to collapse
Thanks a lot for pointing it out, mate! Usually the roms I tried didn't require such a thing, but this might be it. I'll provide feedback if the steps works.
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
psychoticdemon said:
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
Click to expand...
Click to collapse
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Dark Wraith said:
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Click to expand...
Click to collapse
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
psychoticdemon said:
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
Click to expand...
Click to collapse
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Dark Wraith said:
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Click to expand...
Click to collapse
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
psychoticdemon said:
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
Click to expand...
Click to collapse
Yeah.....waiting for other roms wont work.....cz they are all based on 3.4.x kernel.......Umm can you check your baseband after flashing full ftf...baseband should be : 8x55A-AAABQOAZM-203028G-77..every other rom based on 3.4.x kernel works right???...btw if you want to see how it looks just download a kitkat launcher from playstore....
Yes, the baseband is .77 after flashing the ICS 4.1.0.B.587. I used 3.4.x kernel with CM10.1, but never really tried CM10.2 to that extent. Maybe I'll try downloading that and see if it works... or even the EOL CM10.1.
And sure, the launcher would give in the feel, but I want the full experience possible really.
Hi,
I do not have enough posts to post in the cyanogenmod nightlies thread to get a definitive answer, hence why this subforum. I guess my question may be rom independent anyway.
I 'upgraded' from an M release of cyanogenmod to a nightly and buggered my phone. I was forced to flash the stock firmware and then reflash the nightly to fix everything. Except my camera shows a black screen (behind the onscreen focus and options) and force closes nearly all the time. I thought it was just the nightly, but 2 months and 20+ new nightlies later, I still have the issue. In the nightles dev thread, people say the camera is fine. I know the hardware is fine, because 1 in 40 tries the camera randomly works.
I tried a factory wipe, which I now know just wipes user data. So In CWM, under 'mounts and storage' I formatted everything I could and did another factory reset, cache etc. No fix.
I guess this issue is with the rom itself, if the camera is force closing? So I'll have to use Odin or such to flash a stock rom again and flash another cyanogenmod version? But I want to check this is correct before continuing, and how I can completely wipe any trace of the current rom before flashing the stock and another nightly - so I don't get this issue again.
Thanks
So I finally found the issue, after battling with heimdall on ubuntu 14.04 for hours. Its a hardware problem.
I'm just going to leave my experience here in case someone else has the same issue, since anything to do with all the issue I am about to describe don't seem to be documented anywhere on the web clearly.
Firstly, I battled with heimdall 1.3.2 to recognise my phone on ubuntu. I kept getting;
Code:
ERROR: Failed to receive response!
After a number of threads talking about installing usblibx drivers I found one about which libs to install from terminal;
Code:
sudo apt-get install libXXXX
Code:
libusb-ocaml
libdevice-usb-perl
libhpmud0 (not sure if it's essential)
libusb-0.1-4
libusb-1.0-0
libusb-1.0-0-dev
libusb-dev
libusbprog-dev
libusb++-0.1-4c2
libusb++-dev
libusbtc08-1
libusbmuxd-dev
libusbprog0
libusbmuxd1
I installed all but couldn't find libusbmuxd1, restarted anyway, to the same error. I purged heimdall 1.3.2 and instead installed it from the Ubuntu software centre, which using
Code:
sudo apt-cache policy heimdall
showed that I had version 1.4 installed. Then I managed to find
Code:
libusbx-1.0.14_1.0.14-1_amd64.deb
floating somewhere on the internet, which finally installed the proper libusb stuff and allowed heimdall to continue without the error message.
I made a .pit file from my phone. I recommend this first. After hours searching for a stock rom (samsung has removed most of its firmware downloads? and asked links to be removed on other sites!?) came across this site
(I can't post links as a new user) - google [TUTORIAL] Flashing i9000, i9100 or i9300 with Heimdall
Which explains how to flash using heimdall. After a successful flash, my phone didn't get farther than the boot animation. I booted into stock recovery with vol up-home-power to factory reset, but noticed a dead droid and red writting. Rather than continue, I wanted to fix this, so I followed the tutorial again, but this time checked repartition under the pit path, and hoped for the best. The phone stalled at the boot anim again, but this time in recovery, all was good.
I did a data wipe / factory reset, cache wipe etc, but nothing. So I stuck the stock rom zip onto the micro sd and installed it from recovery, factory reset, and rebooted. (which is odd, having to install the rom from recovery - because doesn't that kinda defeat the point of using the same image on heimdall in the first place?!?)
The phone booted! So after all that, (Having data/factory reset, wiped the cache, (wiped the dalvik cache when i had CWM before and formatted all I could in mounts and storage) flashed the stock ROM AND repartitioned the phone) i thought that would eliminate any software issues. I thought the camera would work.
Nope.
As usual, the front camera worked, but the back, now, after a pause would give the samsung error:
Code:
unknown error by errorcallback
Now, after googling this (Cyanogenmod gave a different error with no related answers on google) and being annoyed at my time lost, I took the tongue and cheek advice from some random forum commenter, to tap the camera hard.
It worked.
Apparently, the entire time the camera was suffering from a hardware issue. Something about a 'sticky shutter'. Anyways, i'm going to leave the stock ROM and take it into a shop to get it fixed. Just leaving this trail of breadcrumbs in the hope it helps someone else.
Perhaps this could be marked as 'solved'.
Same problem
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
JCNouel said:
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
Click to expand...
Click to collapse
Try flashing stock rom and see if this fixes your problem.
gsstudios said:
Try flashing stock rom and see if this fixes your problem.
Click to expand...
Click to collapse
It fixed it, but then I flashed back the AICP ROM, which is KK, and it malfunctioned again. I'm going to try with a JB Custom ROM.
Update: I flashed a JB Custom Rom (Fusion Rom) and it's working good so far.
Coming from the simplicity of a Nexus 7 and a Moto G, I am a little confused by how the Z3TC handles recovery and flashing. After a two hour session last night I finally got CM12 20150217 running but not matter what I try, I can't seem to get Xposed 2.7 alpha1 to run (it works just fine on Cm12 on my Nexus so it ought to work, somehow).
In the god awful CM12 recovery, flashing xposed fails with an error message I remain unable to read. Flashing it with the twrp that someone integrated into the stock kernel succeeds according to the twrp status but then the xposed installer still does not see the app_process (it sees the bridge however, which I find weird and have not seen like this before).
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
In principle, I am open to going to AOSP if someone can point me to a scorpion_windy image (all I can find on FXP is scorpion for AOSP, which is another weirdness that confuses me) and feels I have better chances of getting it to work there....
Hi,
what you need to do is to install twrp recovery to the FOTA partition.
(This will also allow you update cm12 through cyanDelta, which is not possibe with the crappy cm12 recovery)
It's all decribed here: http://forum.xda-developers.com/z3-tablet-compact/development/daily-cm12-unofficial-builds-t2983400
The twrp img is actually a modified Z2 twrp, but it seems to work.
(i am writing "it seems" because i have a SGP621 myself, for this one I can say "it works").
Please note:
- It is no problem if app_process displays only ---, that is a known bug of the alpha
- not all xposed modules are working. XGELS is working for sure, if you want to test.
- You need to invoke soft reboot from within the xposed app after each flashing of the xposed zip (which you need to flash after each ROM update). Otherwise xposed will not work currently.
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Edit: Or not, a 10 s power & vol + action followed by power on lets me boot both TWRP and CM12, very strange.
Now lets see if I can get Xprivacy to do its job (for starters, the boot.img contents are different than on the GOogle/Moto devices so we shall see)
nupi said:
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Click to expand...
Click to collapse
wow, I'm really sorry to hear that ... I have no idea what might have gone wrong.
You can turn off the device by holding the power button for 7-10 seconds.
If ou want to remove twrp from the FOTA partition, simply reinstall (ONLY) FOTA from the current ftf (SGP621_23.0.1.A.0.167_CE.ftf) through flashtools.
Never mind, I got it back and TWRP flashed xposed cleanly but I can't get it to work - soft reboot does not help, either
However, the kernel seems to have the wrong WiFi drivers for the SGP611 (at the very least, I don't get WiFi anymore). Back to flashing the CM12 kernel for now... I am thinking I should go back to KitKat until someone with a little more clue figures this one out
nupi said:
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
Click to expand...
Click to collapse
Cyanogen has made the worst mistake every with CM12 and CM Recovery Testing at the same Time.
As long as Cyanogen does not develop a real Recoveryfunction to CM Recovery this crap will block much more then Xposed.
Hi everyone,
I recently have a problem on my (old) TF201. The touch screen works fine, except the right and left edge. When I turn on Developer options and enable 'Show touches' i clearly see that when I move my finger to the right or left it sort of 'snaps' to the edge. So there a small stroke (left and right) that doesn't respond to input. Very frustrating when trying to point out something on the very right or left of the screen
I've opened my TF201 to see it wasn't a loose cable; but everything is in place. No difference.
Anyone an idea?
I did replace the factory ROM with a custom recovery (TWRP) and used
http://forum.xda-developers.com/devdb/project/dl/?id=6853 to install once a CROMBi-kk ROM for TF300t. Maybe this generates this screen edge fault? If so; how do I revert back to TF201? My TF201 thinks it's a TF300 now.
Thanks for reading this problem.
Hi,
Same problem here. It looks like it started after installing KatKiss. I was previously using Cyanogenmod without any problem. I thought that this could be caused by the new bootloader, but the problem persisted even after reverting back to the stock BL and ROM.
I even tried to replace the touch screen, no luck.
Have you been able to fix the issue?
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
[email protected] said:
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
Click to expand...
Click to collapse
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
altya said:
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
Click to expand...
Click to collapse
I am not sure exactly which kernel it was. But as I explained, I first installed Androwook AiryBean 2.31.
Then I used the "Androwook airyBean 2.31 Kernel Installer" to reinstall the default Androwook kernel, meaning the default kernel shipped with the kernel installer. That probably not Grimlock lite 5.1... See this page to download the kernel installer (and the Androwook ROM): http://forum.xda-developers.com/showthread.php?t=2407248
Maybe I should clarify a bit:
1. I completely wiped the tablet and did a clean installation of Androwook, following the instructions to the letter, including the 30 to 60 minutes wait "for the system to cache itself", followed by a restart. At that point, I still had the issue with the screen edges.
2. I then re-installed the kernel, again following the instructions to the letter. After the final reboot, the problem was gone.
3. And I finally re-installed KatKiss (v26). Since then I enjoyed my TF201 without any issues.
The reason why I tried to re-install the default kernel is because of the following quote:
HairyBean 2.31 Kernel Installer will allow you to try different kernel options without re-flashing the rom. It will also clean up bits left behind by the previous kernel before installing a new one
Click to expand...
Click to collapse
I am not sure that this is what solved the problem, but this is definitely a software issue. And since wiping the tablet multiple time, downgrading to stock and trying various ROMs didn't do anything, this was my last hope. It worked for me, and I hope that it will work for you too...
I can confirm that this is a software issue. After installing the reverse axis kernel of Hairy bean, the unresponsive areas in the touch screen was also reversed! I tried the solution provided above, unfortunately without success. Is it right to assume that everyone got this issue after installing Katkiss version after V26?
jan3586 said:
Is it right to assume that everyone got this issue after installing Katkiss version after V26?
Click to expand...
Click to collapse
I don't think so. I got the problem with an earlier version of KatKiss, and I believe (but may be mistaken) from the research I did in the past that a few people ran into this problem with other custom ROMs.
Thanks, are you using ver 2 of the kernel installer?
Sent from my Nexus 4 using XDA Free mobile app
jan3586 said:
Thanks, are you using ver 2 of the kernel installer?
Click to expand...
Click to collapse
Yes, it was version 2 that I used.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2