Related
I had installed TNT Lite v 4.3.0 a couple of weeks ago and it was working pretty good. But today my tablet has gone into a bad state. Every app that I run results in FC. Even the ADW launcher EX that I had selected default is crashing. It then gives me the options: ADW Laucher, ADW Launcher EX, and the regular Launcher. The plain ADW Launcher also fails, but fortunately the regular Launcher still works so I can access the apps.
But unfortunately almost every app that I am trying fails. The only one that doesn't fail is the Web browser. The Settings starts and I can access Applications menu but once I choose say System Applications, after that if I try to choose some other option such as Installed Application, it crashes as well.
Last night however when I started the tablet the battery was probably down and while it was powering it up, it turned off and then restarted by itself and then turned off, without reaching the lock screen. I don't know if it has something to do with all this.
What do I do now? Any help will be appreciated.
Thanks.
A well known issue.
http://forum.xda-developers.com/showthread.php?t=896395
This is why I'm an advocate of people doing the partitioning right before they flash their first custom rom. This way, they won't have to wipe everything later on.
I could only wonder why people aren't mentioning this in every custom rom thread.
Thank you so much. Will try it out tonight.
Unfortunately it seems I have run into a worse issue (without even doing anything yet). Now when I power it on, it starts and shuts off within a few seconds, just shows the birds for like 5 secs and bang, black screen.
The tablet is fully charged (if I put it on charge the light turns green in no time). Looks like the battery is dead.
You might be dropping into APX mode. Do you know how to use nvflash?
Thanks for the reply. You are absolutely right. After multiple tries it did boot up and I was able to install clockworkmod and it all worked great. It wiped off everything but I could live with that. And I turned it off and back on and it was working fine.
But then it went back into the same mode - shutting off immediately after turning on. I decided to return this tablet thinking that it is bad. But before I would do that I thought to restore it or else Viewsonic won't honor the warranty. So I started reading the thread about restoring the tablet to stock using nvram flash. In that procedure it requires me to put the tablet in APX mode and that's when I thought that maybe it is going into APX without pressing the volume - button.
Anyway I was successfully able to flash nvram. Or so it said. I still have the output from the batch file. But now my tablet is totally bricked. It does not boot at all. No pretty birds for me.
I hope there is some way out of it. Please help.
Edit: After re-flashing and using a different file, it seems to have made it a little better. At least I am seeing the birds again. But the original problem of shutting off, or going into the APX mode without pressing Volume button, has returned. All I am getting is the birds for a few seconds and then black screen. I will continue to retry, and if I see it booting up successfully to the stock, this thing is going back to the factory.
1) What image did you use to nvflash?
2) What happened when the flash was finished? Did it boot normally at least once?
3) Does the screen just stay dark all the time now?
1) First time nvflash_gtablet_46_2010112600.zip and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Later I flashed nvflash_gtablet_2010110500.zip. This at least recovered it enough that it shows the birds, but soon after the screen turns black. I have confirmed that it is going in APX mode. If I have USB cable connected to my PC, the PC reports discovering the NVIDEA APX device.
2) It hasn't booted normally since I flashed nvram.
3) No I get the birds, but after that it turns dark.
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Thanks for your response. I tried it. Did not work. When you say Replace part9.img with the recovery.img, does it mean copy recovery.img into the NVFlash directory and rename it to part9.img or leave it as recevery.img. I renamed it to part9.img and backed up the original part9.img to part9.img.tmp. The size of recovery.img and the original part9.img are very different. I am confused. Please help.
K J Rad said:
Ok. Using Bekit's 1105 image...
1) Replace part9.img with the recovery.img out of the clockworkmod installation zip.
2) Put the tablet into APX mode.
3) Type in the command to start nvflash but before you hit the enter key hold down the Volume Up key and continue to hold it down until the flash finishes.
4) The tablet should boot into clockworkmod recovery.
5) Repartition 2048 and 0
6) Clear everything (cache, data and dalvik)
7) You might need to re-nvflash at this point.
Click to expand...
Click to collapse
Yes, that is exactly what I meant.
Are you sure you're holding the volume UP key? Birds and then black screen is APX mode which is normally entered by holding volume DOWN.
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Any ideas?
I was thinking about formatting the gtablet. Please let me know if this is the right move, or there is something else I could try first.
shah123 said:
Well it goes into APX mode even if I don't press any Volume button at all. That is the problem I am trying to fix. When I press power button (without touching the volume button) the birds come and then black screen. And this is APX mode because if I am connected to the PC it brings up an NVIDIA APX device on the PC.
Now if I press the Volume UP button along with the power button, nothing happens, not even the birds come up.
So the fact that the recovery.img (3.7k) is much smaller than part9.img (16k) is ok? Or I am doing something wrong.
Click to expand...
Click to collapse
A little more than "It did not work" would be helpful.
What step failed? Please tell me what happened after each step.
Did you get into CWM and repartition?
Did you get everything cleared?
What happened when it rebooted?
What was the original filename of the image you tried to flash?
What version of clockworkmod do you have installed?
Have you ever used ROM Manager?
All of this is important and no one can help you if you don't provide enough information.
Oh, I am sorry. Here are the answers to the questions you asked:
What step failed? Please tell me what happened after each step.
Ans: Out of the 7 steps you provided, the steps 1, 2 and 3 worked fine. It is the step 4 that failed (and of course I can't proceed with the steps anymore). In other words I cannot go into clockworkmod recovery.
Did you get into CWM and repartition?
Ans: No I was not able to do so. If I press power and Volume Up key at the same time, nothing happens, screen remains black, not even birds come up.
Did you get everything cleared?
Ans: I believe you are referring to step 6. No, I could not get to that step.
What happened when it rebooted?
Ans: Nothing showed up. Because when Volume Up is pressed while it is powered on, nothing shows up on the screen.
What was the original filename of the image you tried to flash?
Ans: Actually first time nvflash_gtablet_46_2010112600.zip (and this is before you provided the 7-step recipe - see post #6, 7, 8 of this thread) and after that it did not boot at all. Only black screen. I flashed it couple of times, no avail. Maybe that was my mistake. I chose a wrong file. Later I flashed nvflash_gtablet_2010110500.zip. This recovered it enough that it shows the birds now, but soon after the screen turns black (goes into APX mode).
What version of clockworkmod do you have installed?
Ans: v08
Have you ever used ROM Manager?
Ans: No. What is it?
I really appreciate your help.
What happened at the end of step 3?
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 seconds after the flash starts.
When the flash was done did it say "Recovery Key detected" on the screen? If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
It sounds to me like you did the nvflash then tried to reboot into recovery.
Its unbelievable. Tonight when I powered it on it started booting up normal instead of going into the APX mode. I was glad. The stock UI came up, but some of my apps like Quadrant, File Expert etc were still there. It also notified me of the Update 3588. So I downloaded it and started installing it. Pretty soon it rebooted itself (sooner than I thought - I don't know if the remaining installation was supposed to happen after the reboot).
But instead of booting up into 3588 it is unfortunately gone back to the same old issue - the birds followed by black screen - aka APX mode. It never booted up after that. No matter how many times I tried to reboot, it goes into APX mode just like before. I don't know what caused it to complete bootup. One thing I noticed was that the battery was totally drained when I started tonight. I don't know if the drained battery somehow took it out of the APX mode. But now it has a little bit of charge because of hooking up to power supply. I have disconnected the power supply and will leave it in APX mode over night and try it again tomorrow when the battery would be totally drained and see if it boots up fully.
To answer your questions though:
What happened at the end of step 3?
The screen went black and after that it stayed black. No CWM.
Did you start holding the volume UP before you pressed the return key for the nvflash? If not... go back and do it again.
Yes, I did.
Did you continue to hold it until the flash was happening? You must continue to hold it down for at least 5 - 10 secondsafter the flash starts.
Yes, I continued to hold it all the way until the flash completed and the screen went black and quite some time after that.
When the flash was done did it say "Recovery Key detected" on the screen?
I don't think it did.
If it didn't say this that is an indication that you didn't hold the volume UP key long enough.
So I guess I need to give it another try. Tomorrow I will try to reboot the tablet again and if it continued to go into APX I will do the nvflash one more time.
If all of the above was done correctly and did happen but you didn't get to clockworkmod then what did you get? Did it look like stock recovery?
A black dark screen. No CWM or stock recovery.
It sounds to me like you did the nvflash then tried to reboot into recovery.
No at the time of nvflash I held the Volume UP button and nothing happened. Since then I have been trying to bootup or put it in CWM Recovery but only thing the tablet wants to do is go into APX mode.
So I guess my theory of "drained battery takes it out of the APX mode" is correct. I tried to reboot the tablet several times but it just kept on going into the APX mode until the battery was completely drained. And then it started booting up normally but it went into some installation (probably the stock 3588 that I had downloaded in the previous successful bootup). And then the green android with the exclamation sign came and the exclamation sign was rotating for a second or two and then stopped. And it looked like it was hung. I waited for a minute or two but nothing happened, so I pressed one of the buttons, I don't know if it was Menu or Back button, and all of a sudden clockworkmod recovery screen came up.
I have attached the picture of the screen. It still shows the green android with the exclamation sign in the middle of the screen, along with the CWM Recovery.
One other thing I noticed and I am not sure if it is normal is that if I choose say Reboot System Now from CWM menu and it shows like 10 entries with many No's and only one Yes. I can only use the volume Up + button to go down, if I try to go up using volume Down - button it does not go up. Is that normal? Is the only way to go is go down using Voume Up button in CWM menus? I have a feeling that my Volume Down button has gone crazy and it is not functioning properly and that is what is causing it to go into APX mode at the startup as well.
Anyway I first attempted "Apply SDCARD:update.zip" hoping that it might continue with the stock 3588 installation, but that failed. You can see the messages in the picture. Then I tried the Factory Reset and it was successful. I then rebooted the tablet. But now again it keeps on going up into APX mode. I will have to wait until tomorrow for it to completely drain battery again and then try to reboot again.
Any ideas? I know it is overwhelming and the behavior is very weird. At this point I am trying to bring it back to the stock firmware so that I can get this tablet replaced under warranty.
There are quite a few things that are not acting normal from what I see here.
Did you try to repartition 2048 and 0? If not, I would start with that then I would format everything and re-nvflash a stock ROM onto it. That might clear things up. If not you could be looking at a hardware reset.
When I try to install a new ROM,
Installation:
1. Power down your device.
2. Power on device holding power button and both volume keys simultaneously.
3. Upon power up you will see the birds logo and 'enter recovery' text in the top left corner of the screen.
4. Use the volume keys to step through the menu, power to select and back.
At this point, the vol key don't do anything,
all I can do is a reset with a paper clip.
Vpad 7 sw ver= 3.16R, model= FM6-0001, hw ver= 1.06
Regards
Mike Pratt
Errrr, let's see, just to be sure - you had previously rooted this Vpad7 and installed ClockWorkMod Recovery 2.x or 3.x on it?
Do you have a Backup on the mSD card that you can restore from, although that's not likely the problem ....
I'm guessing that it's a hardware (power switch) issue so replacing it under warranty (if it's still covered) would be the best option ....
P.S. What ver. of Recovery are you using, just to be sure ?? I just upgraded mine from 3.0.2.8 to CWM 5.0.2.6 and there might be a "minor" issue(s), maybe on my end ....
Letitride said:
... I'm guessing that it's a hardware (power switch) issue so replacing it under warranty (if it's still covered) would be the best option ....
Click to expand...
Click to collapse
Yeah. I'm having the same issue. Just got off the online chat with "Mia", and she gave me the ok to send my unit in. It's been less than a year, so I'm in luck. I would do the same if I were him.
Hey XDA, you did informed me and help me a lot when I would search for a solution and find it on your forums. But now I had to make account in order to find solution for particular one here (I suppose this is a correct topic, please move if I'm wrong):
I forgot to change a really bad pattern password back to regular slide lock, and I didn't know the combination. After trying few times most combinations that I ha din my head, it suddenly asked me a google account in order to unlock it. Well, I know it, I type it and as soon as I press "sign in", a message flashes that it is loading something (just for a split second) and..... nothing. Still there, at same lock screen. I tried those without @gmail.com and null password but nothing worked, none of combinations. I read somewhere that other solution is wipe data or factory reset. Well, I'm okay with that, but how do I enter recovery mode or boot menu where I can access that?? I don't have USB debugging on, I'm sure of that, and my tablet isn't rooted (it was rooted before, but it went on service once for data wiping and it came back un-rooted I suppose)
I don't have hard reset button, but I do have physical back button on side of tablet that I can click, but I never use it. I tried with holding power button and volume up. When it shows me that image of opened android with red triangle warning sign. I release power button and now I'm stuck with that image on my screen, not knowing what to do! I can press power + volume up again to turn off tablet. Power + volume down activates safe mode and turns on tablet, atleast I discovered that feature...
If you know how to get pass that lock screen that asks for google account, anything how to wipe data with locked out tablet I would be very pleased to hear it (technically see it on here). My tablet is still in its case, locked out, and turned off for now.
Note: If I manage to get to pattern lock screen again somehow, that will also work for me. I'm sure I know correct pattern.
instal moborobo and phoenixSuit go in recovery mode and pres volume ap and power and
Daxmarko said:
Hey XDA, you did informed me and help me a lot when I would search for a solution and find it on your forums. But now I had to make account in order to find solution for particular one here (I suppose this is a correct topic, please move if I'm wrong):
I forgot to change a really bad pattern password back to regular slide lock, and I didn't know the combination. After trying few times most combinations that I ha din my head, it suddenly asked me a google account in order to unlock it. Well, I know it, I type it and as soon as I press "sign in", a message flashes that it is loading something (just for a split second) and..... nothing. Still there, at same lock screen. I tried those without @gmail.com and null password but nothing worked, none of combinations. I read somewhere that other solution is wipe data or factory reset. Well, I'm okay with that, but how do I enter recovery mode or boot menu where I can access that?? I don't have USB debugging on, I'm sure of that, and my tablet isn't rooted (it was rooted before, but it went on service once for data wiping and it came back un-rooted I suppose)
I don't have hard reset button, but I do have physical back button on side of tablet that I can click, but I never use it. I tried with holding power button and volume up. When it shows me that image of opened android with red triangle warning sign. I release power button and now I'm stuck with that image on my screen, not knowing what to do! I can press power + volume up again to turn off tablet. Power + volume down activates safe mode and turns on tablet, atleast I discovered that feature...
If you know how to get pass that lock screen that asks for google account, anything how to wipe data with locked out tablet I would be very pleased to hear it (technically see it on here). My tablet is still in its case, locked out, and turned off for now.
Note: If I manage to get to pattern lock screen again somehow, that will also work for me. I'm sure I know correct pattern.
Click to expand...
Click to collapse
instal moborobo and phoenixSuit go in recovery mode and pres volume ap and power and kommt fabrick restore
Hi guys.
I seriously need help right now.
My friend bought an s2 i9100 in cheep which was stuck on bootloop and he thought it could be repaired.
so we don't know what caused the problem.
But i was surprised that few repair shops weren't able to fix it.
let me explain the problem:-
when we hold power button or plug in a charger it show the logo, goes into recovery and reboots repeating it in loop.
so whenever i charge it goes into this loop.
we can use volume up & down key in those 2-3 seconds in recovery but not the power key.
we can access download mode and it doesn't reboots automatically but going into recovery mode manually also start this loop.
it's like we are only going in recovery mode again & again.
i installed this file "I9100XWLPW_I9100ODDLPC_I9100DDLPB_HOME.tar.md5" through odin and also used the pit file "I9100_STOCK-System_2GB-Data_512MB-Preload.pit" but nothing changed.
i don't know what to do now.
i cant find any gingerbread rom to test.
i don't know how it can be fixed,
so please help me.
Update
After doing a lot of things I finally managed to boot into system but the problem is not solved.
I flashed i9100XXLSJ which had modem and CSC files other than the PDA only.
The device actually booted in system (just the samsung logo) but it was a bootloop.
This time I kept holding power button by which the bootloop stopped and it successfuly booted but power button is not working inside the system so I can't reboot, power off or even switch on the screen.
By holding down up vol + home + power for a considerable long time I can boot into recovery. But again the power button is not working so I can't select any option.
I flashed a cwm touch recovery which is working.
So can anyone tell me what is the problem here and what can I do to actually fix it.
If you have problems with flashing stock ROM, consider flashing a custom ROM, like Cyanogenmod.
BenjyTec said:
If you have problems with flashing stock ROM, consider flashing a custom ROM, like Cyanogenmod.
Click to expand...
Click to collapse
The problem is not about flashing it's about the bootloop & tell me can I flash cyanogenmod with Odin?
@kuro2052
Try flashing the 4.1.2 JellyBean leak ROM via ODIN linked in this thread (scroll down to you see "Another option for i9100"):
[GUIDE][Troubleshoot a failed Odin flash]
This will factory reset the device which may hopefully resolve your problems.
gsstudios
gsstudios said:
@kuro2052
Try flashing the 4.1.2 JellyBean leak ROM via ODIN linked in this thread (scroll down to you see "Another option for i9100"):
[GUIDE][Troubleshoot a failed Odin flash]
This will factory reset the device which may hopefully resolve your problems.
gsstudios
Click to expand...
Click to collapse
Actually the ROM you are talking about is the ROM which I flashed which is mentioned in my second post " update".
PDA = CODE_I9100XXLSJ.tar
PHONE = MODEM_I9100XXLS6.tar
CSC = CSC_HOME_OXX_I9100OXXLS1.tar.
That's how I got this far, previously it was impossible to boot into system.
kuro2052 said:
After doing a lot of things I finally managed to boot into system but the problem is not solved.
I flashed i9100XXLSJ which had modem and CSC files other than the PDA only.
The device actually booted in system (just the samsung logo) but it was a bootloop.
This time I kept holding power button by which the bootloop stopped and it successfuly booted but power button is not working inside the system so I can't reboot, power off or even switch on the screen.
By holding down up vol + home + power for a considerable long time I can boot into recovery. But again the power button is not working so I can't select any option.
I flashed a cwm touch recovery which is working.
So can anyone tell me what is the problem here and what can I do to actually fix it.
Click to expand...
Click to collapse
In CWM touch recovery, you can swipe (or touch) to confirm the option.
Try factory reset. Reboot.
If that doesn't help, try wiping system, cache and data.
Let me know how that goes
gsstudios
gsstudios said:
In CWM touch recovery, you can swipe (or touch) to confirm the option.
Try factory reset. Reboot.
If that doesn't help, try wiping system, cache and data.
Let me know how that goes
gsstudios
Click to expand...
Click to collapse
Wiping data/factory reset and cache doesn't solve the problem.
There is format option in 'mounts and storage' so I formated system, data, cache & also emmc. But the bootloop is not gone. The only thing that is gone is the ROM because of those formats. I have yet to to install the ROM again.
maybe is a faulty power button... Do u have to push it down a little harder than normal?
affigne said:
maybe is a faulty power button... Do u have to push it down a little harder than normal?
Click to expand...
Click to collapse
It might be the problem of power button. Sometimes it boots as soon as I put the battery. It always boot when I plug in charger. Sometimes it boots after I press and hold the power key for maybe 15 second & sometimes it doesn't boot when holding power key & I have leave hold again to boot it. And important thing is when it boots, I have to hold the power key until the key lights up to stop it from bootloop but then the power is Jo longer functional in system. Same goes for recovery. But this is the only till nowROM which actually boots into system. Other ROMs were booting into recovery automatically.
I wanted to test cyanogenmod but I am not able to install twrp. I followed the steps here using HeimdallSuite https://twrp.me/devices/samsunggalaxys2i9100.html
I had no problem in the steps but the recovery is not actually replaced when I boot into it.
The recovery that I have currently is not able to flash isorec_twrp or any cyanogenmod directly. It always shows error code 7.
I am going to replace the power button with my friend's s2 (other friend who have an s2 laying around) only to see it works.
Anyways tell me how to install twrp successfuly.
The actual power button needs to soldered, I thought It would be a connector, so I am not going to do that. But as far as I can tell, the plastic button isn't the problem.
kuro2052 said:
It might be the problem of power button. Sometimes it boots as soon as I put the battery. It always boot when I plug in charger. Sometimes it boots after I press and hold the power key for maybe 15 second & sometimes it doesn't boot when holding power key & I have leave hold again to boot it. And important thing is when it boots, I have to hold the power key until the key lights up to stop it from bootloop but then the power is Jo longer functional in system. Same goes for recovery. But this is the only till nowROM which actually boots into system. Other ROMs were booting into recovery automatically.
I wanted to test cyanogenmod but I am not able to install twrp. I followed the steps here using HeimdallSuite https://twrp.me/devices/samsunggalaxys2i9100.html
I had no problem in the steps but the recovery is not actually replaced when I boot into it.
The recovery that I have currently is not able to flash isorec_twrp or any cyanogenmod directly. It always shows error code 7.
I am going to replace the power button with my friend's s2 (other friend who have an s2 laying around) only to see it works.
Anyways tell me how to install twrp successfuly.
Click to expand...
Click to collapse
Since I was on leaked JB firmware, what I did was to install philz recovery via android stock recovery, then install latest dorimanx isorec recovery/kernel, then install TWRP...
---------- Post added at 01:10 AM ---------- Previous post was at 01:09 AM ----------
kuro2052 said:
The actual power button needs to soldered, I thought It would be a connector, so I am not going to do that. But as far as I can tell, the plastic button isn't the problem.
Click to expand...
Click to collapse
check the battery contacts...
Phone info:
Off-brand chinese phone
MT6582
Android 4.4.2
Kernel 3.4.67
Capacitive home button
16MB recovery partition
Google play identifies the phone as "Alps"
I installed TWRP 2.8.2.0 on my phone using the MT TWRP installer http://forum.xda-developers.com/show....php?t=2798257 and when I boot into recovery, touch positions are messed up. (and only in recovery) I have not been able to identify an overall pattern for where the touches end up. I tried different touch orientations and was able to determine that the screen is not flipped and X and Y are not swapped. It seems like it is normal/no swap/no flip, and there is something else scrambling the touch locations - touches seemed to jump around, even within small sections of the display. I believe Carliv touch recovery had a similar/the same issue, but I didnt do much testing on that one.
Touching about 1/3 down the right side presses the back button, although touching a bit to the left correctly presses the Restore button. About 1/2" above that presses the Reboot button. Another 1/2" up presses the Settings button.
Touching the bottom right presses the Settings button. 1/2" up presses the Reboot button. Another 1/2" up presses the Wipe button.
The top half is pretty consistent in what button is pressed, but the bottom half seems to be a bit random, sometimes even pressing the left side.
How can I get touch working properly?
Can anyone suggest another method for booting to recovery? I have been using ADB, but that wont work if the phone ends up unbootable. Volume up + power boots normally, Volume down + power boots to a Chinese factory test mode (touch works fine in the touch tests), Volume up + volume down + power does nothing
I have been trying to install a custom ROM (ported http://forum.xda-developers.com/android/development/rom-cyanogenmod-13-0-mt6582-t3374016), but I get errors during installation. I originally got one error with set_metadata_recursive, searching suggested it was SELinux related. In the TWRP log, I see a line saying "Full SELinux support is present". The original issue was resolved when I copied file_contexts, property_contexts & seapp_contexts from stock recovery to TWRP. Now I get this error after a few minutes when trying to flash:
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
set_metadata_recursive: some changes failed
What else do I need to do to get a ROM installed?
I managed to get TWRP 3.0.1 running on my phone, but it has similar touch issues. However, the scrambling seems to be different than what I get with 2.8.2.0. The version I ported seems to have flipped X, Is there a way to fix that at least, or do I need a different build?
I see TWRP has mouse support, but my phone doesnt support OTG. Is there a way to force the cursor to display? Or is there some recovery that has a drawing screen or other way to show where the touch ends up?
With 3.0.1, I was able to flash CM13, but either I ported it wrong, or it just wont work on my phone. It failed to boot, then booted into recovery. Are there any logs saved during boot?