Related
Hey guys, I really need some help here.
This morning there was a notification about system update, I bet it was the honeycomb 3.1 so I just let it run. However, it turned out that the update failed at last. Since then I can't get the system update notification anymore. I manually checked the update in settings and it showed that "There is no update available for your device currently." I have rebooted the unit several times and tried "Factory data reset" and got no change. I searched around the forum and found this post: http://forum.xda-developers.com/showthread.php?p=14345169
and tried the approach mentioned in it and it's still the same.
I even tried using the leaked update file to update the device and it still won't get updated.
Would you please help me look into this issue? Thanks a lot.
are you still on .9?
if so, just root the device, and install a 3.1 rom via clockwork.
xformulax said:
are you still on .9?
if so, just root the device, and install a 3.1 rom via clockwork.
Click to expand...
Click to collapse
Yes, I have downgraded the firmware to .9. But the thing is, I have a mac and the root guide I found here seems require a windows system. And it really bothers me that something isn't working out of blue. So I'd really like to understand why this is happening. Thanks anyway, I will try to root it if I can't figure this out.
sirejulius said:
Yes, I have downgraded the firmware to .9. But the thing is, I have a mac and the root guide I found here seems require a windows system. And it really bothers me that something isn't working out of blue. So I'd really like to understand why this is happening. Thanks anyway, I will try to root it if I can't figure this out.
Click to expand...
Click to collapse
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/Update_Launcher_SOP_WW.pdf
I dug into the forum and found out a very helpful post about how to set adb work on your non-windows system. If somebody has the same problem, you maybe need to refer to this one.
http://forum.xda-developers.com/showthread.php?t=649663
Hey guys, I just got a Focus i917R, and after updating through Zune, it seems like my keyboard isn't keeping up with my typing. The keyboard doesn't miss anything I'm typing either, it just takes forever to catch up with me.
For example, I'll type "Hi how are you doing today?"
And by the time I'm done, I'm watching the keyboard type by itself at "you doing today?"
Any idea how to fix this? It's kind of annoying.
ShensMobile said:
Hey guys, I just got a Focus i917R, and after updating through Zune, it seems like my keyboard isn't keeping up with my typing. The keyboard doesn't miss anything I'm typing either, it just takes forever to catch up with me.
For example, I'll type "Hi how are you doing today?"
And by the time I'm done, I'm watching the keyboard type by itself at "you doing today?"
Any idea how to fix this? It's kind of annoying.
Click to expand...
Click to collapse
What version do you have, 8107?
Yes, 8107. The problem gets better when I disable keyboard press sounds.
ShensMobile said:
Yes, 8107. The problem gets better when I disable keyboard press sounds.
Click to expand...
Click to collapse
You need to read this and this. Not a fix, but at least gives you an idea: it's because of the "Samsung update" from AT&T, so you'll need to restore.
Well that's ridiculous, why would Zune install an AT&T update onto my Rogers phone?
Is there a guide on restoring to an earlier update? What will I lose by not having this update? I don't want to go pre-mango.
ShensMobile said:
Well that's ridiculous, why would Zune install an AT&T update onto my Rogers phone?
Is there a guide on restoring to an earlier update? What will I lose by not having this update? I don't want to go pre-mango.
Click to expand...
Click to collapse
The point I was trying to make is that the updates released from the carrier (in those cases AT&T, in your case Rogers) affected the phone's performance. The specific update we are talking about is NOT any of the WP7 OS updates but the "Samsung update".
For restoring, sync first in Zune. Then, when connected, go to Settings (top) and then click Update (left). I should say "your phone is up to date" and in the lower part of the screen you should have a "Restore" option.
Alright, thank you for clearing that up.
As for restoring, won't that just restore my phone to the same 8107 update? Or does restore downgrade me somehow?
ShensMobile said:
Alright, thank you for clearing that up.
As for restoring, won't that just restore my phone to the same 8107 update? Or does restore downgrade me somehow?
Click to expand...
Click to collapse
Restore is downgrade to the version you had just before the update, which in your case it's probably 7740. After that, you can try to update again and see if the update is good this time? Sometimes the update is "upgraded" (updated for compatibility, stability etc).
A backup is performed by Zune, for your phone, each time you update, exactly so you can restore in case something goes wrong.
Well, ****, I just restored my computer and no longer have the backups. I guess I can't use restore... Is there any way I can flash an older version on, like on Android phones? Or am I just stuck waiting until a new update comes out?
ShensMobile said:
Well, ****, I just restored my computer and no longer have the backups. I guess I can't use restore... Is there any way I can flash an older version on, like on Android phones? Or am I just stuck waiting until a new update comes out?
Click to expand...
Click to collapse
You can downgrade and then go through the whole update process again. See point 1 in this thread.
However, I suggest that before you do the downgrade, first you:
- sync all your files in the phone so you can restore later
- make a list of all the apps you have installed
- save all your important SMS, read here
- you read how to make a backup and make one (see point 0 in the noob thread)
Alternately, you can consider a custom ROM. See this post.
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
So where are you at right now. What rom and what exactly have you done to your tab.
Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
shaun298 said:
So where are you at right now. What rom and what exactly have you done to your tab.
Click to expand...
Click to collapse
At this moment right now, my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Moscow Desire said:
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
Click to expand...
Click to collapse
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Mkami said:
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Click to expand...
Click to collapse
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
cruise350 said:
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Click to expand...
Click to collapse
What do you mean by RUU? Also I've tried a couple of the OTA updates, when I first got the tab it was on 3.1 HC didn't even update it or anything, just had a custom ICS ROM on it. Do you think you can post the steps or anything on how to do this properly and go fresh? It would be sincerely appreciate buddy.
Moscow Desire said:
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
Click to expand...
Click to collapse
Hmmm....I'm not even sure what I am doing wrong but whatever it is, it seems to be not working. I looked for you post for the earlier person that you did, but don't know what it is under. By the way when I first bought the tab it was under 3.1 HC and after getting flexreaper it became to ICS 4.0.3...
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Mkami said:
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Click to expand...
Click to collapse
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
lcd047 said:
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
Click to expand...
Click to collapse
You're right! I was able to fix it and boot up to the usual! Thanks mate!
chismay said:
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
Click to expand...
Click to collapse
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Mkami said:
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Click to expand...
Click to collapse
tkirton said:
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Click to expand...
Click to collapse
Hahaha! Good job on guessing all that! I just followed your order from step to step and I was about to boot up normally! Everything might be erased and stuff, but hey at least I have my tablet working again :good: Case solved!
Tab boots to "welcome" screen but does not register touches, leaving me unable to move forward. Ready for the long story?
I am helping a friend who bought this tab from a third party. When he received it, the previous owner stated that they did a factory reset back to Honeycomb but he noticed that it did in fact still have ICS on it. Probably OTA'd when the previous owner did the reset. Tab worked fine for about two weeks until one day he came home and the lockscreen would not register touches. That's where I come in.
I did the "erase, wipe" (booting while switching the screen rotation back and forth.) Tab wiped and brought me to the "Welcome" screen where you select country and language and still does not register touches. I have tried blackthund3r's flash and manager tools, as well as multiple guides to recover from what I have seen referred to as "flu." The main problem I have is that I cannot get a valid UID. Using USBDeview gives me an 11 digit serial but it returns as invalid when plugged into DotNetDetector and I am unable to use SDB because the non working touchscreen has left me unable to enable USB debugging.
Any suggestions, help, advice, on things I can try? I am really stumped and would like to help my friend/conquer this problem. Thanks for anyone who has taken the time to read this/offer help.
generalagony said:
Any suggestions, help, advice, on things I can try? I am really stumped and would like to help my friend/conquer this problem. Thanks for anyone who has taken the time to read this/offer help.
Click to expand...
Click to collapse
Get ready for some Ubuntu... Here is the guide that will get you a valid sbk. My nephew just brought his tab to me after forgetting his password. So I was in the same boat as far as UID/SBK. This is gonna take a while so put some time aside.
JdgM3NT4L said:
Get ready for some Ubuntu... Here is the guide that will get you a valid sbk. My nephew just brought his tab to me after forgetting his password. So I was in the same boat as far as UID/SBK. This is gonna take a while so put some time aside.
Click to expand...
Click to collapse
As sure as I am reading yoru reply the damn thing just started working. I was able to get to USB debugging and via ADB I was able to pull the UID; which was the same as the one I got from USBDeview btw. Still an 11 digit code. The only thing I can guess is that it has a faulty touchscreen, or maybe the battery was just too low to register touches? Thanks for your reply though. Always nice to be able to rely on the folks at XDA.
That is too cool. The other way is a learning experience to be sure. Enjoy.
JdgM3NT4L said:
That is too cool. The other way is a learning experience to be sure. Enjoy.
Click to expand...
Click to collapse
I have now realized that the touchscreen does work but is very glitchy and have found that lots of people have had problems with the OTA ICS update. Any suggestions on a good custom ROM for this tab? It isn't mine so I have not been following this section. Would like something close to stock ICS but with fixes that resolve the problems associated with OTA.
generalagony said:
...I was able to get to USB debugging and via ADB I was able to pull the UID; which was the same as the one I got from USBDeview btw. Still an 11 digit code...
Click to expand...
Click to collapse
generalagony said:
I have now realized that the touchscreen does work but is very glitchy and have found that lots of people have had problems with the OTA ICS update. Any suggestions on a good custom ROM for this tab? It isn't mine so I have not been following this section. Would like something close to stock ICS but with fixes that resolve the problems associated with OTA.
Click to expand...
Click to collapse
First check in Settings>About Tablet>Build Version - this will tell you what rom you are currently running -
Then, if you can, download and install Acer Recovery Installer
This tells you what bootloader and recovery is installed.
The glitches you speak of and the 11 digit uid point to an ICS Rom and unpatched HC bootloader - updating to the new BL often fixes these weird glitches BUT if you flash a custom rom as well, you'll be running sweet!!!
If you wanna stay close to Stock then I'd recommend ezterrys one here comes pre-rooted and busy box installed - and if you want to you can install his Over clocked kernel too.... plus its well maintained and supported
there are many tools and guides around to help you...the ones in my sig for instance the cpuid one has a lot of general info in it too re bootloaders, sbk and flash tools.
If you have any q just ask, there's always someone round willing to help...good luck!!
Isn't there anyone one here who would be willing to make a rom for the ME301t besides the stock ones? If we were willing to donate money to get it done?
krash1256 said:
Isn't there anyone one here who would be willing to make a rom for the ME301t besides the stock ones? If we were willing to donate money to get it done?
Click to expand...
Click to collapse
No offense, but i don't think this is the section for requests. FAQ and general discussion would be more appropriate.
Oops, sorry
DaringDomino3s said:
No offense, but i don't think this is the section for requests. FAQ and general discussion would be more appropriate.
Click to expand...
Click to collapse
Sorry didn't know.
I assumed, that's why i said something as soon as i saw it. I'm new to the posting rules here too, and i have seen that the development section is taken seriously.
Sorry about your device scenario. Im sure something will come along start a thread campaigning in a place where it wont get deleted and you may find more people that know someone wlling.
Cromi-x and Geimlock are already compatible with ME301T... :good::good::victory:
Since the ME301T is so close to the TF300 in terms of specs and because of how easy it was to make the ME301 work on CROMI or GRIMLOCK, its possible that there might only be a few minor things that need to change to make a ME301 work on a CM rom. Since there are no devs who own an ME301T we would needs some help from the community to get it to work.
Mainly we would need for someone with an ME301T to install a CM based rom and see if it will boot. From there you would need to get a logcat and send it to us so we can see if we can fix the issues that are preventing it from working.
hardslog said:
Since the ME301T is so close to the TF300 in terms of specs and because of how easy it was to make the ME301 work on CROMI or GRIMLOCK, its possible that there might only be a few minor things that need to change to make a ME301 work on a CM rom. Since there are no devs who own an ME301T we would needs some help from the community to get it to work.
Mainly we would need for someone with an ME301T to install a CM based rom and see if it will boot. From there you would need to get a logcat and send it to us so we can see if we can fix the issues that are preventing it from working.
Click to expand...
Click to collapse
Someone tried it here. http://forum.xda-developers.com/showthread.php?p=48077047#post48077047
It didn't work for me yet. Maybe you could take a look and see if I'm doing something wrong or if there's something wrong with the file. Am more than willing to help in anyway I can.
krash1256 said:
Someone tried it here. http://forum.xda-developers.com/showthread.php?p=48077047#post48077047
It didn't work for me yet. Maybe you could take a look and see if I'm doing something wrong or if there's something wrong with the file. Am more than willing to help in anyway I can.
Click to expand...
Click to collapse
Sounds like it isn't too far off. What I need is for someone to try and flash a CM rom and send me logs of when it is booting up etc. As a suggestion, I would try this rom: GRIMLOCK_CM_3.0 as it is the rom I am working on. It would be easiest for me to help on that.
hardslog said:
Sounds like it isn't too far off. What I need is for someone to try and flash a CM rom and send me logs of when it is booting up etc. As a suggestion, I would try this rom: GRIMLOCK_CM_3.0 as it is the rom I am working on. It would be easiest for me to help on that.
Click to expand...
Click to collapse
Okay, will do. I'll download and it and give it a shot. I'm not very good with the logcat stuff, lol, but I will do my best.
Well, it boots into the rom and I get a little circle which is a mouse I guess. I can get around and I can get into settings but I can't figure out how to get down to about tablet so I can get to usb debugging. If I try to adb while it's booting up adb just says waiting for device... So I can't do the logcat. Any suggestions on what I'm doing wrong or a way to get adb working?
krash1256 said:
Okay, will do. I'll download and it and give it a shot. I'm not very good with the logcat stuff, lol, but I will do my best.
Well, it boots into the rom and I get a little circle which is a mouse I guess. I can get around and I can get into settings but I can't figure out how to get down to about tablet so I can get to usb debugging. If I try to adb while it's booting up adb just says waiting for device... So I can't do the logcat. Any suggestions on what I'm doing wrong or a way to get adb working?
Click to expand...
Click to collapse
Okay, I messed around and finally got usb debugging turned on. Rebooted and did this logcat. I can't get wifi turned on at all.
BTW: I love this rom without all the google crap on it. I have always hated having to run through all the setup wizard crap too. Thank you for helping with this. I'm very excited about getting this rom for my tablet.
krash1256 said:
Okay, I messed around and finally got usb debugging turned on. Rebooted and did this logcat. I can't get wifi turned on at all.
BTW: I love this rom without all the google crap on it. I have always hated having to run through all the setup wizard crap too. Thank you for helping with this. I'm very excited about getting this rom for my tablet.
Click to expand...
Click to collapse
Try to flash THIS after flashing the rom and see what happens.
hardslog said:
Try to flash THIS after flashing the rom and see what happens.
Click to expand...
Click to collapse
Okay, I wasn't sure if you meant to flash both files one right after the other, so I flashed the rom, then the test. Sticks me at CyanogenMod animation. Then I did a clean flash of just the rom, rebooted and flashed the test, it booted, said Android is updating apps and then gets stuck at starting apps. So then I rebooted just to see if maybe that would do it but that just sticks at CM animation once again.
krash1256 said:
Okay, I wasn't sure if you meant to flash both files one right after the other, so I flashed the rom, then the test. Sticks me at CyanogenMod animation. Then I did a clean flash of just the rom, rebooted and flashed the test, it booted, said Android is updating apps and then gets stuck at starting apps. So then I rebooted just to see if maybe that would do it but that just sticks at CM animation once again.
Click to expand...
Click to collapse
I meant to flash the rom then the test.
Can you get my any logs?
hardslog said:
I meant to flash the rom then the test.
Can you get my any logs?
Click to expand...
Click to collapse
I don't know how to get log during boot. I tried turning on usb debugging first and then flashing the test and then tried to logcat but it just says waiting for device. Is there a specific way to get adb to work during boot?
hardslog said:
I meant to flash the rom then the test.
Can you get my any logs?
Click to expand...
Click to collapse
I wasn't doing adb devices first then the logcat command. Duh. Here's the logcat.
Test # 2
@krash1256
Ok here is another one to try. Again Flash GRIMLOCK_CM first and then try flashing this one. According to the logs its possible that the wifi got fixed but the extra files I put in borked other stuff.
hardslog said:
@krash1256
Ok here is another one to try. Again Flash GRIMLOCK_CM first and then try flashing this one. According to the logs its possible that the wifi got fixed but the extra files I put in borked other stuff.
Click to expand...
Click to collapse
Okay, it now boots into the rom but you still have to use the little circle as a mouse and I can now turn wifi on but it just sticks at turning on wifi.
Turned wifi off and back on now it says To see available networks, turn on wifi.
krash1256 said:
Okay, it now boots into the rom but you still have to use the little circle as a mouse and I can now turn wifi on but it just sticks at turning on wifi.
Turned wifi off and back on now it says To see available networks, turn on wifi.
Click to expand...
Click to collapse
Ok so wifi still doesn't work, but it is a step in the right direction.
I don't really understand what you mean by a little circle as a mouse though?
and again, the more logs the merrier
hardslog said:
Ok so wifi still doesn't work, but it is a step in the right direction.
I don't really understand what you mean by a little circle as a mouse though?
and again, the more logs the merrier
Click to expand...
Click to collapse
Instead of being able to just touch the screen and make choices, this little round circle pops up when you touch the screen and you have to move that little circle around and tap on the circle twice to make choices. It's like using a touch pad for the mouse on a laptop. For instance, if you want to open settings you have to position the little circle on the settings button, tap twice, it opens settings, then you have to position the circle on say wifi and tap the circle again. To scroll, you have to position the little circle at the very bottom of settings, and it's a hit or miss type of thing, tap it and then move it upwards to get to the bottom, like about tablet and tap the little circle again. Does that make since? The rom is basically mouse driven instead of touch driven.
This logcat is while it's booting and also once I'm in the rom.
Bluetooth is definitely working. I connected a bluetooth mouse and I can navigate with that instead of having to navigate with the little circle.