Hi,
Yesterday, my gTablet had some strange issues with sound. When I push the buttons to change the volume, I can only hear "Puck, puck, puck...". If I go to the volume settings and change the volume there, I can hear the test sound. I found later that I could only hear sounds coming from the system ( notification, ringtone, etc. ).
I was using the C&C v6 Rom. I tried to reset factory, reinstall the rom, reformat partition, tried stock rom, FlashBack 8.1, NVFlashed back to latest 1.1 stock rom and then installed VeganTab 5.1 but still no luck. It's also not working when I'm plugging my headphone. When I'm on Flashback, the sounds work but only with a headphone. Any idea on fixing this ? Or is it a hardware defect (I really hope not...) ? What's weird is that I can hear all the Android system sound but not video/music from Youtube or any mediaplayer...
Another user had the same issue
gitah said:
Hi,
Yesterday, my gTablet had some strange issues with sound. When I push the buttons to change the volume, I can only hear "Puck, puck, puck...". If I go to the volume settings and change the volume there, I can hear the test sound. I found later that I could only hear sounds coming from the system ( notification, ringtone, etc. ).
I was using the C&C v6 Rom. I tried to reset factory, reinstall the rom, reformat partition, tried stock rom, FlashBack 8.1, NVFlashed back to latest 1.1 stock rom and then installed VeganTab 5.1 but still no luck. It's also not working when I'm plugging my headphone. When I'm on Flashback, the sounds work but only with a headphone. Any idea on fixing this ? Or is it a hardware defect (I really hope not...) ? What's weird is that I can hear all the Android system sound but not video/music from Youtube or any mediaplayer...
Click to expand...
Click to collapse
Recently worked with another user that had the same problem..could hear notifications, but not music or video audio. The kicker was that he could hear music playing when the gtab goes into sleep mode (try it). Come out of sleep & the sound stops. Also has the same puck, puck, puck as you when you change the volume.
Last heard from him a week ago so I don't know if he got it resolved. He was also on 1.1 branch & it cropped up on him when he nvflashed back to 3588. He was going to try & nvflash to 1.2 branch 4349 & see if it made a difference
aabbondanza said:
Recently worked with another user that had the same problem..could hear notifications, but not music or video audio. The kicker was that he could hear music playing when the gtab goes into sleep mode (try it). Come out of sleep & the sound stops. Also has the same puck, puck, puck as you when you change the volume.
Last heard from him a week ago so I don't know if he got it resolved. He was also on 1.1 branch & it cropped up on him when he nvflashed back to 3588. He was going to try & nvflash to 1.2 branch 4349 & see if it made a difference
Click to expand...
Click to collapse
I tried what you said ( put the gtablet in sleep mode ) and yes I could hear the music playing.
gitah said:
Yesterday, my gTablet had some strange issues with sound. When I push the buttons to change the volume, I can only hear "Puck, puck, puck...". If I go to the volume settings and change the volume there, I can hear the test sound. I found later that I could only hear sounds coming from the system ( notification, ringtone, etc. ).
Click to expand...
Click to collapse
Interesting problem. Can you get me a logcat and a dmesg output from your system?
1. Reboot the gTab.
2. Once the system boots into the desktop, play with the volume settings (both HW and SW).
3. Then run these commands inside a Terminal Emulator app and attach the output:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]dmesg >/mnt/sdcard/dmesg.txt[/B] [I]Get kernel logs[/I]
# [B]logcat -d -v time >/mnt/sdcard/logcat.txt[/B] [I]Get Android system logs[/I]
gitah said:
I tried what you said ( put the gtablet in sleep mode ) and yes I could hear the music playing.
Click to expand...
Click to collapse
I got ahold of the other user with the same problem (sk01bim) and he has not resolved his issue either. I consulted with rajeevvp and he suggests capturing dmesg & logcat output to aid in troubleshooting.
See rajeevvp's instructions on the post above.
I'll try to have sk01bim do the same & post them here also.
Al
rajeevvp said:
Interesting problem. Can you get me a logcat and a dmesg output from your system?
1. Reboot the gTab.
2. Once the system boots into the desktop, play with the volume settings (both HW and SW).
3. Then run these commands inside a Terminal Emulator app and attach the output:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]dmesg >/mnt/sdcard/dmesg.txt[/B] [I]Get kernel logs[/I]
# [B]logcat -d -v time >/mnt/sdcard/logcat.txt[/B] [I]Get Android system logs[/I]
Click to expand...
Click to collapse
Here is a archive containing the two files ( files were too big so I had to zip them ) . Thank you for looking into this problem
gitah said:
Here is a archive containing the two files ( files were too big so I had to zip them ) . Thank you for looking into this problem
Click to expand...
Click to collapse
Wow! There are so many NAND flash-related errors in that dmesg.txt file that most of the relevant messages were ditched (the kernel keeps a fixed sized buffer for messages and old messages are discarded). Try getting me a dmesg while in ClockworkMod. It has a different kernel:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
I don't know if your NAND flash errors are causing your sound problems. We may have to fix them (if possible). However, try this first: Disable bluetooth, unplug wired headphones, then reboot the tablet and check sound. If there is still no sound, kill the abtfilt program if it's running and then check the sound again.
In a Terminal Emulator window:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]kill -9 $(busybox pidof abtfilt)[/B] [I]Kill abtfilt[/I]
# [B]/system/bin/ps | fgrep abtfilt[/B] [I]Check that it died[/I]
# [I]No output means it did[/I]
rajeevvp said:
Wow! There are so many NAND flash-related errors in that dmesg.txt file that most of the relevant messages were ditched (the kernel keeps a fixed sized buffer for messages and old messages are discarded). Try getting me a dmesg while in ClockworkMod. It has a different kernel:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
I don't know if your NAND flash errors are causing your sound problems. We may have to fix them (if possible). However, try this first: Disable bluetooth, unplug wired headphones, then reboot the tablet and check sound. If there is still no sound, kill the abtfilt program if it's running and then check the sound again.
In a Terminal Emulator window:
Code:
$ [B]su[/B] [I]Become superuser[/I]
# [B]kill -9 $(busybox pidof abtfilt)[/B] [I]Kill abtfilt[/I]
# [B]/system/bin/ps | fgrep abtfilt[/B] [I]Check that it died[/I]
# [I]No output means it did[/I]
Click to expand...
Click to collapse
Hmm...sorry but how do I do a dmesg while in CWM ? I tried to go to recovery then use adb but it couldn't find my device.
Also, my bluetooth wasn't on and I tried to kill abtfilt but it says that there's no such process.
gitah said:
Hmm...sorry but how do I do a dmesg while in CWM ? I tried to go to recovery then use adb but it couldn't find my device.
Click to expand...
Click to collapse
The command is already given above, but, you have to set up adb first. Go through this thread, or, a less hassle-free method is to use a Linux live CD.
Okay here's the dmesg while in CWM.
gitah said:
Okay here's the dmesg while in CWM.
Click to expand...
Click to collapse
No errors from the CWM kernel. We'll have to try the ROM kernel again--possibly a different one--to get the error messages (if any)... but, for the time being, do a quick test:
Remove the external SD card from its slot, power on the gTab and see if media playback comes back.
Still no sound after I removed my microsd card
gitah said:
Still no sound after I removed my microsd card
Click to expand...
Click to collapse
Can you install a different kernel and get the logs again (w/o micro sd card in slot)?
Ok...I just installed GHarmony for 1.2 bootloader and still no sound. BUT ! I tried something for the lulz, I ticked the Silent mode in the sound menu and guess what ? I get sound from Youtube... -.- If I untick the Silent mode, I get no sound...
I attached the logcat and dmesg when on Calkulin's rom and when on GHarmony. I tried to do the trick on Calkulin's Rom but it didn't work so I went back to GHarmony.
+1 -- you seem to have figured this out on your own.
Ughh...Now my trick is not working anymore and I DON'T why ?! I only installed the GAPPS for GHarmony and now whatever I set in the volume settings, I get no sound... I guess that the only thing to do now is to use Flashback 8.1 with headphones until something comes out of this :'(
gitah said:
Ughh...Now my trick is not working anymore and I DON'T why ?! I only installed the GAPPS for GHarmony and now whatever I set in the volume settings, I get no sound... I guess that the only thing to do now is to use Flashback 8.1 with headphones until something comes out of this :'(
Click to expand...
Click to collapse
I installed GHarmony yesterday, but, could not reproduce your problem. I can't even see any error messages from the kernel, so I don't know where your problem lies: HW, or SW (kernel or ROM).
The only problem that I did find in your kernel messages is that you have an unreadable bad block on your system partition. So, format just the system partition and reload the ROM of your choice. This should keep all your data intact.
Have the ROM of your choice ready on your SD card, put the gTab into APX mode, then fire up nvflash and format only the system partition (called APP in nvflash). After this boot into CWM and flash whatever ROM you want. You can also wipe the system partition while inside CWM using a
Code:
C:\> [B]adb shell erase_image system[/B]
command, but, I'm operating under the assumption that nvflash might do a more thorough job "fixing" non-factory-marked bad blocks.
Code:
C:\> [B]nvflash --bl bootloader.bin --format_partition 11 --go[/B]
You can use whatever bootloader.bin you want (1.1 or 1.2) as long as it is for the gTablet--it is not stored on the NAND flash when you run it with "--bl ...".
See this post http://forum.xda-developers.com/showpost.php?p=17926964&postcount=3. This user says he fixed his by opening & moving one of the speaker wires away from a contact on the board. Worth considering.
aabbondanza said:
See this post http://forum.xda-developers.com/showpost.php?p=17926964&postcount=3. This user says he fixed his by opening & moving one of the speaker wires away from a contact on the board. Worth considering.
Click to expand...
Click to collapse
Looks like a great solution. I will still try to format my gtablet and see if it works. If not, I'm going to open it. I have a question about your solution. You say that the sound works when the screen is off because there is no current. How comes that the notification sounds still work even with the screen on? Anyway, it fix the problem, I will try it
gitah said:
Looks like a great solution. I will still try to format my gtablet and see if it works. If not, I'm going to open it. I have a question about your solution. You say that the sound works when the screen is off because there is no current. How comes that the notification sounds still work even with the screen on? Anyway, it fix the problem, I will try it
Click to expand...
Click to collapse
You should definitely do rajeevvp's format suggestion since you are getting the unreadable block errors.
I was skeptical when I read the post (and even more skeptical as to why the user said it worked, but hey, stranger things have happened). I don't have the problem & I didn't say I had an explantation as to why it worked for this user. All I did was see the post & thought it was worth a try for you. If you want an answer you'll have to go to the post & ask the user.
Related
I have been talking this over with Condemned Soul but wanted to see if anyone else has ran into this problem since he & I are both confused.
My fiances phone has been force closing a lot lately aka com.android phone not responding. I saw the first force close when I tried flashing Tazzs cm7 on his phone so thats when I first put on gsb 1.2
I switched his over to Sheds GSB on the 8th and it was great everything was fine but then I decided to try to improve on a few settings and when I restarted the phone it decided to start force closing.
I reflashed the rom and the gapps and everything seemed fine but then I wanted to put cs skull theme on his phpne since we had it on Kaos v9 but then when I restarted the phone after flashing the theme it force closed again.
So then I reflashed the rom and gapps again and got all his apps and settings all back how he had it and decided to do a Nandbackup so that we wouldnt have to keep reflashing the rom again and once I restarted the phone after the nandbackup it force closed again.
Long story short I reflashed the rom and gapps and now am in the process of getting his apps and settings back how he had it once again.
Am I doing something wrong to make it keep force closing? I would like to make a nandbackup at least for him so that we wont have to keep setting up his phone.
Thank you for any help
When you say you flash the ROMs, do you also do a wipe beforehand? If not, try doing a wipe and then install and see if that changes anything.
Yes I wiped both the factory and dalvk sorry I thought I mentioned that. lol.
labnjab said:
Yes I wiped both the factory and dalvk sorry I thought I mentioned that. lol.
Click to expand...
Click to collapse
Its a problem that happens on certain ROMs with certain themes. Not sure there's a fix for it, I just got around it by not applying the phone.apk theme.
zerocool79346 said:
Its a problem that happens on certain ROMs with certain themes. Not sure there's a fix for it, I just got around it by not applying the phone.apk theme.
Click to expand...
Click to collapse
phone.apk wasn't changed in the theme. Strange part is it's only on the one phone and haven't heard of it on any of the others.
CondemnedSoul said:
phone.apk wasn't changed in the theme. Strange part is it's only on the one phone and haven't heard of it on any of the others.
Click to expand...
Click to collapse
That is odd.
Update:
This is still causing issues. Going to try and format the sd like tazz suggested, but moving my phone.apk to his didnt work, and yesterday he had to restart his phone and it did it again and needlessto say hes not very happy with his phone. Says its not reliable at all. If anyone else has anything else I can try it would be a big help. I have tried searching on google but dont find a whole lot of information. I just wish I could figure this out its got to be something I did or something stupid that I am missing.
There are a couple of next steps you can take.
If the problem is a software configuration issue, then it is possible that you will see the reason for the FC in the logcat.
The system logcat is designed as a "circular buffer" (in a way that it has a maximum size) - once you fill it to capacity, each new record which is added to the end causes information at the beginning to be lost. But, this also means that if a FC occurs, so long as you "dump the logcat" within a reasonable period of time after the FC happens, you will capture the moment in time that the FC occurred,
Generally, the "logcat" buffers get filled to capacity quite quickly at boot time (because there is lots and lots of "android" app activity), and quite a bit slower after the phone has been completely booted. If you are trying to capture a logcat event during the first boot, you need to continuously capture output to a file on your PC (it will be quite large) - but once the phone has completed booting, so long as you "run a logcat" within 5 or 10 minutes after a FC occurs, the relevant event(s) will be in the logcat.
If you want to capture it during the first boot cycle of a freshly flashed ROM, probably you ought to have a PC attached and dump the prodigious output to a file on the PC, as in
Code:
C:\MyWindozePC> adb shell logcat -v time > LogcatFileOnMyPC.txt
So long as the ROM you have flashed has "USB debugging" turned on by default, you can run the above command about 10-15 seconds after you see the 3 skating droids, and it will continuously place output into the local file on your PC. You need to interrupt the above command (Control-C) to get it to stop; you would usually do that a few seconds after you saw the FC, and then you would know that the log entries you are looking for at the end of the file.
(Note that logcat dumps are usually huge - don't bother trying to look at them with a text file viewer on the phone - they suck at handling large files... well, at least the ones that I have tried).
You could also instrument this on the BF's phone in a way where he can capture the info to the SD card anytime he is using the phone during the day with a couple taps of the screen, and then you could look at the logcat(s) later at your leisure - for instance by using Gscript Lite, and a simple script like this:
Code:
#! /system/bin/sh
_LOGDIR='/sdcard/logcats'
if [ ! -d ${_LOGDIR} ]; then
mkdir ${_LOGDIR}
fi
_tstamp=`date +%Y%m%d-%H%M`
logcat -v time -d > ${_LOGDIR}/logcat_${_tstamp}.txt
With this method, you just need to train him like a monkey to press the right keys after a FC occurs. If he's a clever monkey, you could even train him to send the logcat files to you via e-mail.
If the problem is due to an intermittent hardware issue with the phone, that will be tougher to identify. About the best you can do to make that determination is to return the phone software to stock and use the phone without installing any apps for a reasonable period of time and see if the problem continues to occur.
cheers
bftb0
Thank you for the detailed reply bfbt0 I was about to msg you when you responded.
I will have to give what you mentioned a try.
Is the gscript lite what I use for the adb shells or do I need another app as well. I have never done anything with adb or if I have it was something simple.
To clarify I would have to get his phone to fc again which is easy to do and then run a logcat. It sounds easy through the pc I just want to make sure I do it right. I would make a folder dedicated to where the logcats would be stored and then run it in the gscript lite? Meaning run the first code you posted.
Update ~ Never mind I found you had to have android sdk on your pc Im downloading that now. I still may need help tho.
labnjab said:
Update ~ Never mind I found you had to have android sdk on your pc Im downloading that now. I still may need help tho.
Click to expand...
Click to collapse
GScript Lite is a free app on the market. It was put together by XDA member "rogro", and he has a paid version as well if you want to throw a couple bucks his way.
Using the script above with Gscript (Lite or Pro), you don't need to be tethered to a computer nor set up the SDK and drivers. (Only when you want to capture a full first ROM boot do you need to use a PC (because the logfile grows so big in that specific case).
If you can force the FC to occur, then using the Gscript Lite script I showed above will capture the information you want.
bftb0
PS There is a brief outline of how you load a script into Gscript Lite in that "Universal Root for Dummies" thread over on AF.
cheers
Thank you I will try that tonight and hopefully can figure out what the issue is
labnjab said:
To clarify I would have to get his phone to fc again which is easy to do and then run a logcat. It sounds easy through the pc I just want to make sure I do it right. I would make a folder dedicated to where the logcats would be stored and then run it in the gscript lite? Meaning run the first code you posted.
Click to expand...
Click to collapse
That code I posted checks to see if a folder exists, and if not creates it - /sdcard/logcats
No need for you to do it manually; the first time the script runs it creates that folder
But, yeah - wait for the FC to happen and then run that script within the next couple of minutes (no real hurry). It is also useful to make note of the time the phone displays when the FC occurs - it will be easier to find things in the logcat file by timestamp if you do that.
bftb0
Thank you I will do that as well. Thanks also for taking the time to help me.
I did the code on my phone to make sure I did it right and it gave me an error
says cannot create/logcat_20110222-1558.txt read only file system
did I do something wrong, just want to make sure that I can get it right before attempting it on his phone tonight. Thanks in advance.
labnjab said:
I did the code on my phone to make sure I did it right and it gave me an error
says cannot create/logcat_20110222-1558.txt read only file system
did I do something wrong, just want to make sure that I can get it right before attempting it on his phone tonight. Thanks in advance.
Click to expand...
Click to collapse
If you typed that script in by hand, you made a typo.
I checked it by cutting and pasting it - and then I tested it afterward, and it worked.
Probably you bolluxed up the _LOGDIR variable, or you inserted a space in the logcat command where there should not be one.
I would suggest that you cut and paste, rather than type.
Hmmmm... it occurs to me that those little "scrolling CODE text boxes" don't render correctly on the phones browser. Here's the same script, but without enclosing it in [ CODE ] [ /CODE ] tags:
#! /system/bin/sh
_LOGDIR='/sdcard/logcats'
if [ ! -d ${_LOGDIR} ]; then
mkdir ${_LOGDIR}
fi
_tstamp=`date +%Y%m%d-%H%M`
logcat -v time -d > ${_LOGDIR}/logcat_${_tstamp}.txt
Thank you for all your help. I got it to work and come to find out I didnt even need to use that program because it hasnt forced closed yet. He said he wiped the phone a bunch of times the other day when he was trying to get it back up and running when it forced closed on him while at work and now i rebooted it and backed it up and that usually caused a problem, so far so good.
I am tho going to format the sd card and redo the rom again just to be sure this problem doesnt happen again. Thank you again for all the help.
On some builds (even though it shouldn't be required) it is necessary to wipe multiple times. On Tazz's earlier builds of GB, people reported having to wipe 3x or more to get it running smooth. Always make sure you do a nand backup before flashing in the future lol. Hopefully the phone stays running good! If not, people are always here to help!
Sent from my Ginger Tazz using XDA App
Okay guys, so here's a weird one.
My g-tablet was working great. Was running VEGAn-Tab Build, BETA 5.1.1, no reason to update it, because it did everything I needed. I finally had it to where I wanted it, then it all kind of started falling apart. Here's how.
I power it on and notice my home screen got all messed up for some reason (using launcher pro). All of the settings defaulted to the original. I tweaked it back to more or less how I wanted it, and when I had it back to normal, thought nothing better of it. Must have glitched out some how.
Then I notice a bunch of things starting to force close, specfically android market, amazon market, titanium backup, google services framework, launcher pro, etc. Odd thing is it would do it one at a time, but otherwise my tablet would carry on as normal.
I go ahead and restart the tablet, to see if that helps at all, and what do you know, the homescreen is messed up again! I thought launcher pro might have been the culprit, so I un-installed the app and rebooted... And launcher pro is still there.
I go ahead and delete it again and start deleting other apps, restarting the tablet, and no matter what I do, everything stays the same. time for some clockwork mod action. I go into clockwork mod, and try to do the factory reset option, thinking what the hey, I'll try anything right now. Hit it, mourn the loss of my user data, and reboot the system... and again, everything is still the same.
I hook up my tablet to the computer via usb, and it looks like I'm able to at least delete misc. files that way. But when I return to good old Tabatha (my nickname for Gtab) everything is stuck just the way it is.
Needless to say, it feels like I'm stuck in the twilight zone.
I know I should have researched it by now, but I'm going to finally look it up to see if I can recover with NVFlash (I know I know, very noobish of me, using strange roms and not knowing any of the basics).... but I'm increasingly worried I've got some kind of a hardware malfunction on my hands. Could it be the memory? The internal SD card?
Oddly enough, my tablet still functions... I can browse the web, hook it up to my computer, etc etc, but no matter what I do I can't alter the data I already have on my tablet. Can't delete things, can't change settings, update apps, etc. etc. Which makes it pretty much useless for what I wanted to use it for.
I finally realized what this is like. The movie groundhog day, and I'm stuck in the same day, over and over again.
Any help or input that might get me out of this mess would be greatly appreciated.
Phil: "I was in the Virgin Islands once. I met a girl. We ate lobster, drank piña coladas. At sunset, we made love like sea otters. *That* was a pretty good day. Why couldn't I get *that* day over, and over, and over..."
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
rajeevvp said:
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
Click to expand...
Click to collapse
Thanks for the direction, at least I know it isn't an isolated incident. It's 1:45 AM where I am right now, and I have to wake up for work in about 5 hours... So I probably won't be able to get in depth with the follow up on this stuff untill after work tomorrow night (so long as the wife doesn't hog the computer )
Again thanks for the quick response, I appreciate you pointing me into some sort of direction. Can't wait to try to get this sorted out!
Currently trying to figure out how to get ADB going.... pretty intimidating, but I'm trying. I got the Java JDK installed, installing the SDK, but can't find the "SDK Setup.exe" file or even a USB driver folder in the SDK directory. Got a good resource for getting ADB set up?
Save yourself some trouble. Got to http://www.knoppix.org/ and download the latest Knoppix live CD image.
Burn it, boot it, then use the adb executable from this post. For simple things like just running adb, you don't need the entire Android SDK.
Get me a dmesg while inside ClockworkMod:
Code:
$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
ADB commands documentation
Thanks, I'll try it out sometime this weekend!
Well, I really screwed myself now. I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive. [Do I need to load the OS onto a flash drive instead?]
So I started messing with some stuff in clockwork mod. I apparently really goofed it, and I got a "Magic Value Mismatch" error everytime I tried to boot it up.
I looked up Magic Value Mismatch, and from there it pointed to using NVFlash to try to fix that problem. So tried that. After I flashed it, I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
I looked up this issue and apparently the key is to get into clockwork mod and do factory reset, reset cache, and partition the SD card to 2048 and 0, which I did... (per post #4 on this thread: http://www.slatedroid.com/topic/17501-helpstuck-in-bootloop/ ) but still no dice.
Not sure where to go from here, or if I can even get it to interface with ADB in its current state. Looks like I'm done for
Thanks for trying though
On second thought, I may have had a breakthrough, at least in getting ADB to see my tablet!!! Woohoo! It finally sees the device and has a serial number. Was following the device on this thread:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
But I have a 64 bit machine, so I finally figured it out and plopped that into the 64 bit portion of the .inf file. DOH!
So now let me see what I can drum up through the previous commands above.... though the parameters have changed now to be sure... Due to my haste things may have taken a turn for the worse.
To recap, now my tablet is stuck in a boot loop after having done NV Flash, after having screwed up some settings in clockwork mod trying to fix a "Magic Value Mismatch" error.
Tried:
$ dmesg > /mnt/sdcard/dmesg.txt
I just run this in the cmd prompt at my platform-tools directory where the adb is correct?
All it says is, "The system cannot find the path specified."
Am I doing something wrong, or is my tablet that messed up?
Okay, this is slightly weird. So I was browsing around in clockwork mod, and lo and behold, the original zip flies for vegan tab are all STILL THERE. So I reloaded them... And My tablet zips back to exactly the way I had it before!
Only this time, so far no force closes. This looks way too good to be true after what I've been through. I'm going to try modifying some files and settings and restart my tablet to see what it does. I'm pretty sure I can't be out of the woods yet. Allthough it is 3:33 AM as this is happening... magic hour. I may be going insane.
EDIT: Nope, was definitely way too good to be true. All my data is as stuck as it was ever was. But at least now I can get into it again. But now we're back to square one. Lemme figure out this dmesg business and get back to you. X(
So I would try issuing the following exactly in the command line at the adb platform tools folder:
$ dmesg > /mnt/sdcard/dmesg.txt
Is that code supposed to be copy and paste in? I don't seem to be getting anything. I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file. And you want me to do that while the g tablet is in recovery, correct?
FYI, trying to do it through Windows 7. Would that command only operate in the linux environment via knoppix?
Thanks
titobetlogs said:
I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file.
Click to expand...
Click to collapse
Redirect the output to a file:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
titobetlogs said:
I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive.
Click to expand...
Click to collapse
I suggested using Knoppix just because it is so easy to use adb in Linux. Broken-down steps for future reference:
1. Download and burn the latest Knoppix Live CD iso image. Check the downloaded file size. The .iso file should be ~700MB in size. Also, test the CD by booting it and then typing at the boot prompt: knoppix testcd
2. Boot Live CD and skip the creation of any partition or file to store user data. After all, we just want to run adb.
3. After Knoppix has booted into the desktop, run a browser, right click on the adb.zip attachment in this post, then select "Save Link As..." and save the zip file into /tmp.
4. Connect the gTablet to the PC via the USB cable.
5. Open a terminal window, then type in it:
Code:
hostpc$ [B]cd /tmp[/B] [I]Change to the dir. where adb.zip was saved[/I]
hostpc$ [B]unzip adb.zip[/B] [I]Unzip zip file[/I]
hostpc$ [B]ls -l adb[/B] [I]Check if the adb program was extracted OK[/I]
-rwx------ 1 rvp rvp 159620 Dec 1 22:23 adb
hostpc$ [B]chmod 555 adb[/B] [I]Make adb executable.[/I]
hostpc$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
Note 1: do not type in the shell prompt, 'hostpc$'. It is only there to show you what the screen should (roughly) look like.
Note 2: If adb says something like "device not found", just unplug the USB cable from the PC, wait a few moments, then re-plug the cable and re-run the adb command again.
6. Go back into the browser and attach the dmesg.txt file that is there in /tmp. You will have to tell the Noscript plugin to allow scripts from xda-developers to enable attachments. Right click on the page, then select the Noscript menu item, then choose "Temporarily allow xda-developers.com".
I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
Click to expand...
Click to collapse
I'm not surprised. If the files on the internal SD card cannot be modified then that boot loop behaviour is to be expected. Here's why:
Android requires certain partitions to exist on the system. These partitions can be either on the flash or on SD cards. The partitions are:
/system: This is where the binaries and system apps that come with the firmware are stored. This partition is usually mounted read-only to protect it. On the gTablet, this partition is on the 512MB built-in NAND flash chip.
/cache: As the name indicates, this is the partition used to speed up the execution of the Java apps. Temporary files are also created here. This partition too is on the built-in NAND flash chip.
/data: This is where user-downloaded apps are stored by default, and also where Android stores its system configuration data. This partition, on the gTablet, is on the internal SD card.
/sdcard: This is where user content like media files, books, and the apps moved to SD card are stored. This partition too is on the internal SD card.
The first 3 partitions are critical and Android won't come up without them being present (or, if there are any errors on them). Among these 3, only /system needs to be correctly populated (When you install a ROM, new stuff is copied here). The other 2 partitions, /data and /cache can be empty and the system will boot up fine--with defaults. In fact, when you select "wipe data/factory reset" in CWM, /cache and /data are re-formatted--effectively, wiped clean.
(There are 2 other important partitions on the NAND flash chip, but, these are not mounted because they don't contain a proper filesystem. You have to use special tools to create the contents of these 2 partitions.
The first of these is the "boot" partition. This one and "system" are re-written when you install a new ROM. The "boot" partition holds the Android Linux kernel. If you install a new kernel, only the "boot" partition is rewritten.
The second is the "recovery" partition. This contains a separate, and usually different (and safe), Linux kernel and a mini filesystem image. This is a fail-safe partition. Stock recovery and ClockworkMod sit here.)
In your case, nothing on the internal SD card can be modified, so the stuff in /data will still be from your old ROM. (nvflash also cannot modify SD card contents, as I mentioned before.) When the stock firmware boots up, it will find incompatible stuff in /data. Critical apps will then die. Android will restart them, they will die again. This is your boot loop.
Get me the dmesg output and then we'll run a few tests using CWM, but, judging from your previous posts, I don't think your internal SD card can be fixed. You have 2 options:
1. Return the tablet for a replacement.
2. If you can't return it, I can switch the internal and external SD cards on your ROM so that you can boot and use the system (almost) normally. But, this is a custom solution and you will need to have an external SD card in its slot always. Read through this thread.
Wow, you really know you're stuff! I'll see what I can get you later on in the day with regard to the dmesg, I'm currently still at work.
I had suspected a hardware error... bummer. I'll definitely be interested in seeing if I can just use the external micro sd slot to sub out for the internal sd card. I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Do you know if this thing takes 32 gb micro sd cards? That would be pretty awesome, I at least wouldn't feel too limited on space.
By the way, thanks for all your help on this, I know I'm a huge noob. I greatly appreciate your patience and taking the time to break everything down for me. I have absolutely zero background in programming or anything computer related, though I do find this stuff extremely fascinating! If I could rewind the clock and study this stuff in school, I would do it in a heartbeat.
Again, thanks so much, can't thank you enough.
titobetlogs said:
I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Click to expand...
Click to collapse
No, you should be able to run whatever ROM you want. I'll send you an installable zip file, in a few days, which should get you going again on Vegan-Tab, at least. You'll just need to remember to flash this zip file right after you've flashed the ROM (of your choice).
Right now, I don't know if I need one zip file for each kind of ROM in existence for the gTablet, or, if I can use some scripting and do the internal/external SD card switch using just a single installable zip file. I'll look into this on the weekend.
Do you know if this thing takes 32 gb micro sd cards?
Click to expand...
Click to collapse
Yes, it does.
By the way, thanks for all your help on this, I know I'm a huge noob...
Click to expand...
Click to collapse
I was a complete noob to Android myself back in April of this year. I've picked all of this up in just a few months. I'm pretty sure you can do it too, with a bit of poking around in the system. Of course, having a background in Unix/Linux helps a lot.
In your honor, below are some inspiring lyrics from the Karate Kid soundtrack:
You’re the best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you dow-ow-ow-ho-how-ho-own
INSPIRING GUITAR SOLO
Dude! you're embarrassing me -- I haven't send you the zip file yet... and, you haven't sent that dmesg output I wanted.
I know I've been stuck at work and family functions every day this week so far. Hopefully I'll get to it soon
Finally got to this! Here you go! Thanks again!
titobetlogs said:
Finally got to this! Here you go!
Click to expand...
Click to collapse
Can't see any problems in that dmesg output. Time for some tests on the internal SD card.
Boot into CWM, then run on PC (on Linux run: sudo ./adb shell):
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I] Mount internal SD card partition[/I]
~ # [B]mkdir -p /sdcard/a/b/c[/B] [I]Make a directory tree[/I]
~ # [B]echo test > /sdcard/a/b/c/test.txt[/B] [I]Create a file[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Read it back again[/I]
test [I]Correct[/I]
~ # [B]echo 3 > /proc/sys/vm/drop_caches[/B] Flush kernel caches
~ # [B]cat /sdcard/a/b/c/test.txt[/B] Read it back again
test Correct
~ # [B]umount /sdcard[/B] [I]Unmount[/I]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I]Remount /sdcard[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Reread file[/I]
test [I]You should see "test" here[/I]
~ # [B]umount /sdcard[/B]
You should see "test" after the kernel flush and the remount.
Next, reboot the tablet--back into CWM, then run the cat command again. `cat' should output "test", again, if the SD card is OK.
Here's a screen of the commands I entered and what I got back. Did I do anything wrong? Looks like something's a bit off.
For some reason the upper left part of my touchscreen doesn't work.
I tried the "Touch Screen Recalibrate" apk from gojimi but it didn't help, well not with the corner at least.
I really noticed it while running CM7.1 (which unfortunately was my favorite ROM until this situation occurred) because I could not hit *anything* in that freaking corner , and I am very ocd so it irritated me way too much to be ignored. So i had to change back to Beasty's Froyo Ultimate (in the meantime) until this can be resolved. Correction, if this can be resolved.
If ANYONE has anything that may help please please PLEASE share it
Any help is appreciated
I have had good success with the procedure that starts by using a terminal emulator (like the one from Jack Palevich). From the terminal emulator, you do the following:
1. $ su
2. # touch /sdcard/calibration.ini
3. # /system/bin/TSCalibration
This is discussed in threads like: http://forum.xda-developers.com/showthread.php?t=1098010
Good luck.
Cannot open the file...?
I followed all the steps exactly as stated and this happened:
get devicetype!
get btmac!
can not open the file calibration.ini in emmc !
Except the last line repeated endlessly
poymeister said:
I have had good success with the procedure that starts by using a terminal emulator (like the one from Jack Palevich). From the terminal emulator, you do the following:
1. $ su
2. # touch /sdcard/calibration.ini
3. # /system/bin/TSCalibration
This is discussed in threads like: http://forum.xda-developers.com/showthread.php?t=1098010
Good luck.
Click to expand...
Click to collapse
So I looked at the thread you posted and tried the procedure given for Gingerbread ROMs (because I switched to cm7 again to do this) and it says that calibration.ini is a read only file system.
Heres what i followed:
rajeevvp said:
Ah! you're running one of the Gingerbread-based ROMs. The error message tells you what you need to do:
Code:
$ [B]su[/B]
# [B]touch /emmc/calibration.ini[/B]
# [B]/system/bin/TSCalibration; sleep 5[/B]
Don't type in the prompts ('$' and '#')--they're only there to show you how the screen should look--and don't touch the screen until you get the '#' prompt again. Make sure you have the Superuser app (also free) from Market first for the su command to work.
Remove the calibration.ini file if calibration succeeded:
Code:
$ [B]su[/B]
# [B]rm -f /emmc/calibration.ini[/B]
Click to expand...
Click to collapse
See post #20 of that same thread for a much simpler method.
rajeevvp said:
See post #20 of that same thread for a much simpler method.
Click to expand...
Click to collapse
Thank you SO much! this worked finally *phew*.
Still busted...
I took my gTab a part a few days ago to fix the power connector that had come loose. When I put it back together I did not have any sensitivity on the right side of the screen (when holding it in landscape position). I ran calibration.ini and later tried the TouchRecalibrate app. I finally got it all working again except for the last inch. When holding it in landcape position the last inch from top to bottom on the right has no sensitivity. Is there anything else that I can do to fix it?
21.03.2014 RELEASE #4 UPDATE
Here is first ever CM for LG D605 (Optimus L9 II).
This is unofficial ROM and might have some serious faults, if this breaks your phone or they fire you from your job because alarm didn't start it will be your own fault since you have installed it. You have been warned!
The installation procedure was tested with unbranded phone (OPEN_EU variant). This might not work with branded ROM (but it would be good if someone check it).
Sources can be found at:
https://github.com/Varcain/android_kernel_lge_d605
https://github.com/Varcain/android_device_lge_d605
Things that don't work and won't be included in this ROM by default (possible enable by porting stock apps):
- FM radio
- IR port
Things that I already know that don't work at all or are bugged:
- NFC (no support at all yet)
- Manual service network selection (only auto supported right now)
- SIM card contact/SMS reading
For best battery life keep bluetooth off if you are not using it. It will keep constant wakelock if left on right now
NEWEST RELEASE #4
- Added USB tethering
- Added Bluetooth tethering
- Working move to sd-card function (but MTP on internal memory is disabled, external SD card is now mandatory)
- Vibration patterns tuning
- Correct WLAN and Bluetooth MAC addresses should be used now
CHANGES FROM RELEASE #3
- Fixed first call with no voice bug
- Fixed incoming call volumes
CHANGES FROM RELEASE #2
- Fixed voice call volume
- Fixed mute microphone option during calls
NEWEST ROM RELEASE #4:
d605_cm10_v4.zip - 164.61 MB
GAPPS:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Old releases:
release #3:
http://d-h.st/Zr4
How to install:
1. Flash CWM (from here: http://forum.xda-developers.com/showthread.php?p=50407619)
2. Download the ROM and gapps to sdcard
3. Boot to recovery
4. Wipe all userdata
5. Install CyanogenMod first then gapps
6. Reboot.
Now wait for CM to boot... (first boot will take longer as always).
For reporting bugs/problems:
- Send me logcat output (it would be good to have "logcat -b radio" output too if this is related to sim card/radio)
- Send me dmesg output
If you experience reboot (kernel panic most likely) then send me contents of /proc/last_kmsg (you have to copy this right after reboot, you can do it from terminal application if you don't have access to PC with adb at that time).
Reserve for info.
Thanks Varcain!
Beginning installation right now.
----------------------------------------EDIT---------------------------------------------
Help: http://forum.xda-developers.com/showpost.php?p=50007962&postcount=318
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
TaZRAge said:
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
Click to expand...
Click to collapse
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
How to install:
Unzip contents, boot your phone to stock ROM, connect via USB with USB debugging mode on, install adb (if you don't have it yet), then adb push all unzipped files to /data/local/tmp (for example adb push ./system.tar /data/local/tmp). After that enter adb shell, issue "su" command and:
# cd /data/local/tmp
# chmod 777 clear_partitions.sh
# chmod 777 loki_flash
# chmod 777 system_update.sh
# mkdir mntpoint
# ./clear_partitions.sh
# ./loki_flash recovery rom.lok
# ./system_update.sh
After that locate your unzipped gapps and do the following (I assume gapps are unzipped directly in /storage/external_SD/Download
# cp -r /storage/external_SD/Download/system/* mntpoint/
# sync
# reboot recovery
Click to expand...
Click to collapse
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/sdcard1/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Varcain said:
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/external_SD/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Click to expand...
Click to collapse
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
TaZRAge said:
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
Click to expand...
Click to collapse
I made a typo, try /storage/sdcard1 instead of /storage/external_SD.
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
TaZRAge said:
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
Click to expand...
Click to collapse
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Varcain said:
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Click to expand...
Click to collapse
reinstalled everything
maybe I gona set up a dualboot on my PC too =)
made 2 screenshots from my adb shell with wel.... rare behaviour
but now it worked!
i have Gapps
Not rare behavior at all! You forgot Download directory in first screenshot and in second one it looks fine to me.
Varcain said:
Not rare behavior at all! You forgot Download directory in first screenshot and in second it looks fine to me.
Click to expand...
Click to collapse
*headpalm* no wonder it did not work
Well whatever.... that is one fine port =)
I am only missing my apps i installed via the amazon appmarket =D
And since its not really a ROM for daily use i will not install everything i have in my stock ROM
---------- Post added at 07:44 PM ---------- Previous post was at 07:14 PM ----------
Varcain said:
Just use the ROM like you normally would, compare with stock and if you find some anomalies report it in my ROM's thread, I will add them to bug list and hopefully fix in next release.
you can save logs to sd card and then load them from PC connection (I turned off MTP setting by default so it wont be detected as MTP device for file transfers, you need to turn it on in settings>storage>press menu> select MTP).
To do this from console app in phone:
logcat -d > /storage/sdcard1/logcat.txt
logcat -d -b radio > /storage/sdcard1/logcatradio.txt
dmesg > /storage/sdcard1/dmesg.txt
cat /proc/last_kmsg > /storage/sdcard1/lastkmsg.txt
Click to expand...
Click to collapse
This should be in here too!
And by the way, after activating MTP in the ROM i can use adb shell at my computer again!
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
TaZRAge said:
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
Click to expand...
Click to collapse
Settings>Launcher>Homescreen>Homescreens
TaZRAge said:
*headpalm*
Click to expand...
Click to collapse
Thanks again
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Varcain said:
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Click to expand...
Click to collapse
Works this way!
---------- Post added at 11:01 PM ---------- Previous post was at 10:39 PM ----------
I connected my BT stereoheadset to listen to some music that doesn't sound like coming out a can....
Music via BT is no fun with this right now
I'm sitting next to my phone and the music comes interruptedly and sometimes with crackling sounds.
Gets even worse when i begin to experiment with the equalizer.
Next song comes flawless.... Ah display got disabled.
Screen back working and interruptions are back.
Controlls work perfect as i am used to (volume up + down + start/stop + next song + previous song do what they are supposed to do).
BT Speed to slow?
Disabled GPS now its better again.
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Varcain said:
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Click to expand...
Click to collapse
I tested it with stock many times before. Without problems like these.
And its sure I am in a radio-noisy environment. Around here are 4 wifi nets and the one i am in has 3 repeaters.
I had BT disabled on my computer during the test.
I will test it with a cable headset today, I don't have another BT headset.
Yet i had no other problems, bugs or errors!
Just install it!
First impression is VERY GOOD!
I think is faster than stock rom.
Minor problems with installation.
GApps works ok.
Known problem with camera.
Play some games, all run ok and FAST.
I think battery goes faster.
Install some themes, minor problems.
Basic Bluetooth ok.
That's all for now. I will play more later.
Thanks a lot Varcain! :victory:
I will upload new build in a moment and update the OP with it. There is major bug in first alpha release which causes constant wakelock (so the phone never goes into deep sleep). I managed to debug and fix it, please install new version.
First time posting and I wanted to say thank you to all the excellent talent here on XDA! None of this would have been done without the work of so many people.
I have a Moto G Play (2021) (XT2093-4) that I recently purchased (Best Buy - $159 US/Carrier Unlocked) and I wanted to document my adventure in to rooting, making '/system' RW, and fixing the missing LED notification light (hint: I used the charging light) (hint^2: It's not required to make '/system' RW in order to fix the LED notification light - I just wanted more control over my phone).
First, "OEM unlocking" was greyed out for me, but became available after several days of having the phone online with a SIM card.
I followed the instructions here to unlock the bootloader and root with Magisk (Non-TWRP). Along with these instructions.
Once bootloader is unlocked, you will need the 'boot.img' file from your stock firmware. I used the "Rescue and Smart Assistant" utility to grab a copy of the stock firmware (GUAMNA_RETAIL_QZAS30.Q4_39_35_9_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml) and extracted the "boot.img" file for the next steps.
Continue installing Magisk (Filenames may be different! Don't just copy and paste.):
Code:
adb install Magisk-v23.0.apk
adb push boot.img /sdcard/Download
(Follow the instruction on your phone to patch 'boot.img' in Magisk)
adb pull /sdcard/Download/magisk_patched-23000_aKKMt.img
adb reboot bootloader
fastboot flash boot_a magisk_patched-23000_aKKMt.img
fastboot flash boot_b magisk_patched-23000_aKKMt.img
You should now have a working, rooted Moto G Play. You can just stop here and have fun with your phone, but I noticed that even with root, the system partition was not RW.
I followed these instructions to make '/system' writable (Note: you will need the 'sysrw_repair.zip' that's included in the bundle and a Linux system):
Code:
adb push systemrw_1.32_flashable.zip /data/local/tmp/
adb shell
su
cd /data/local/tmp/
unzip systemrw_1.32_flashable.zip
cd systemrw_1.32/
chmod +x systemrw.sh
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` out=/data/local/tmp/systemrw_1.32/img/super_original.bin size=50
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
(On another Linux terminal)
Code:
cd /path/to/unzipped/sysrw_repair/dir/
chmod +x sysrw_repair.sh
./sysrw_repair.sh
This results in a new folder (img) with a rather large bin file (super_original.bin).
(Back on the phone adb)
Code:
exit # Exit root
exit # Exit adb
adb reboot bootloader
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
You should be able to login and have a writable '/system':
Code:
adb shell
su
mount -o rw,remount /
No errors should appear.
Last, I like having an LED indicator that tells me that I have an SMS/MMS notification waiting. Motorola thought it would be wise to eliminate that feature altogether instead of having the option to enable it. So, I forced it back on using a startup script that dumps the notifications and greps for some key words. And, if it finds something, it "breaths" the charging LED. The script loops until the notification is gone, then keeps checking for new notifications every 30 seconds. (Note: the "/data/adb/service.d/" directory is used by Magisk like an INIT service):
(Still root on the phones adb)
Code:
cd /data/adb/service.d/
cat <<EOF > ledfix.sh
#!/bin/sh
while true; do
if dumpsys notification | egrep NotificationRecord | egrep sms > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) == 0 ]]
then
echo 1 > /sys/class/leds/charging/breath
sleep 2
continue
else
sleep 2
continue
fi
elif egrep 'Charging' /sys/class/power_supply/battery/status > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) -ne 0 && $(cat /sys/class/leds/charging/brightness) -ne 0 ]]
then
echo 0 > /sys/class/leds/charging/breath
echo 255 > /sys/class/leds/charging/brightness
elif [[ $(cat /sys/class/leds/charging/breath) == 0 && $(cat /sys/class/leds/charging/brightness) == 0 ]]
then
echo 255 > /sys/class/leds/charging/brightness
else
continue
fi
else
echo 0 > /sys/class/leds/charging/breath
echo 0 > /sys/class/leds/charging/brightness
fi
sleep 30
done
EOF
chown 0.0 ledfix.sh
chmod 0755 ledfix.sh
reboot
Now, the charging light will fade off and on about every 2 seconds if there's an SMS/MMS notification waiting. And will check for notifications every 30 seconds. I'm sure someone can come up with a better way of doing this, but this was a nice quick-and-dirty way to get what I wanted.
Hope this helps!
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
PROFSLM said:
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
Click to expand...
Click to collapse
You can also get the firmware from
Lolinet Mirrors
https://t.me/MotoUpdatesTracker
Search for Firmware by codename, software channel, Software Version, and build #
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
mario0318 said:
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
Click to expand...
Click to collapse
I know!
I don't know what triggers that light to come on. I even waited until the battery was at 6% and the light still never came on.
So, I updated the script above to make the light go full brightness if the battery is charging. The order matters, so if a notification comes in while charging, it'll "breath" the LED. Also, if the battery is full, then the light will turn off. Kind of telling you that it's time to unplug.
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
jorduino said:
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
Click to expand...
Click to collapse
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
mario0318 said:
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
Click to expand...
Click to collapse
Im not completely sure how to get the right file, but I think the first time it was the wrong one, but then when i got what i thought was the right one, it just didn't work at all and I had to recovery flash it. I had just updated so maybe the correct image wasn't available yet. Im going to try again though
Oh! Hello @latentspork. Thanks for your interest in my SystemRW project. I just came across this thread randomly...
I'm happy you got my script to work on your Motorola device by using the included sysrw_repair script
Please feel free to send me your log files from script folder. Thanks. It's useful for further development of the script
latentspork said:
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
Click to expand...
Click to collapse
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Yes that's true the included sysrw_repair script (Linux only) pulls the image files from the phone to your computer and attempts to run the same lpmake command with the same arguments that just failed with error 73 on the phone itself and now all of a sudden it just works in Linux. Go figure.
latentspork said:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Click to expand...
Click to collapse
Why would you delete the super_original.bin ? That's your stock read-only super image which by default is automatically dumped by script for backup purposes in case you ever get a bootloop.
And if you launch the script by specifying a custom input value (in=x) like in your example above then you won't even have a super_original.bin file to begin with because script will skip the whole dumping of original super image process.
latentspork said:
This results in a new folder (img) with a rather large bin file (super_original.bin).
Click to expand...
Click to collapse
I think you mean super_fixed.bin
latentspork said:
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
Click to expand...
Click to collapse
Here in your instructions you are manually flashing the wrong file. Shouldn't you be flashing super_fixed.bin to your super partition?
Usually I only flash the super_original.bin to get back out of a bootloop...
latentspork said:
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
Click to expand...
Click to collapse
See that's why I included that automatic flash() function in the repair script. Then you don't have to worry about manually flashing the wrong file to your super partition
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
@lebigmac
I really appreciate the reply and the tool! It did work really well on my model (XT2093-4).
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Click to expand...
Click to collapse
I only assumed that "Error 73" was caused by insufficient space, because the phone really did run out of space. I noticed that the phone was out of space because I got a home screen notification warning, asking me to free up space. I confirmed it with a "df -h" at the shell. Apparently, the OS takes up almost 15GB. When you add the ".img" files, there's only about 5GB left. There wasn't enough room to complete the ".bin" file. Maybe I could have used an SD card or something.
You're probably correct in that "Error 70" is the correct error for that, but on my phone, I never saw that error. I did notice that the tool was still trying to write data as the phone ran out of space, then it would throw the "Error 73". Maybe it didn't register the lack of space, or just an oddity with my model? No idea.
Why would you delete the super_original.bin ?
Click to expand...
Click to collapse
This is the file that was created when I initially ran the "./systemrw.sh" command on the phone. The result of running the command on the phone were several ".img" files and a very large "super_original.bin", but it was incomplete because the command threw an "Error 73". I was following your instructions, and I noticed that the output name of the file was "original" instead of "fixed". I probably could of outputted it to a new name to reduce confusion, but I didn't really care too much about the name as long as I had a working file.
I think you mean super_fixed.bin
...
Shouldn't you be flashing super_fixed.bin...
Click to expand...
Click to collapse
Normally, yes. But the Linux script also outputted the filename "super_original.bin". Again, as long as it worked, I was okay with it. The commands I used above were the exact commands that I ran at the time. I copied them from the terminal consoles I was using. So I don't know why it wasn't outputting the correct filename (again, I was following your instructions and was a little confused that the names came out differently - I just figured I was doing something wrong like not use the proper output command or something).
Then you don't have to worry about manually flashing the wrong file to your super partition...
Click to expand...
Click to collapse
I was really just being cautious because my previous phone broke and I didn't have a fallback.
But, at no point were there two bin files (original and fixed), so there wasn't much confusion. Where I originally had just ".img" files before running the script, I now had a single ".bin" file. I knew that was the file I needed.
But again, thank you for all the hard work on this tool! I was reading that it's worked on lots of different model phones, and it's always good to see the open source community doing things that help all kinds of people.
For moto notification for this phone at least use https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledreborn or moto led reborn from the play store it just works
Hi, sorry. This can be removed. I put it in place because I was having issues with the xda app. For whatever reason, every time I tried to share this particular post, it would share a link for the post which I used originally, rather than the current post. I knew that if I commented I could get back here easily on my PC.
So what is the place holder for