after tried several rom,i found some rare problem on my mt3g(maybe).
on hero rom:
1. my phone always show headset icon on top bar (kings [1.1,1.3],kings droid eris 1.1.2,qtek,ace cupcake hero).
2. i can't hear sound from my speaker when i set phone ringtone,when someone call(ringtone and people voice),but notification it's okay.i must use headset to hear the sound.this happen on kingdroid eris an ace rom.i didn't try on qtek because to much fc .
3. when i flash kings rom,i don't have problem.it can boot.but when i use ace rom,mlign,jac rom.it will stuck on mt3g green screen.so i try to connect usb cable and use adb logcat to know what the problem when my phone booting.and this is the weird miracle happen.use adb logcat(not yet tried another adb command) when phone boot make ace cupcake rom can boot and run.i not yet try this method on mlign or jac rom.on log cat,it's written dalvik bla bla freeze if i not wrong.i try to pull out the usb cable and reboot the phone,the result is my phone stuck again in mt3g green screen.so i must use usb cable+adb logcat to boot ace and mlign rom.
4. can't hear sound from built in speaker when play music,youtube,video.no problem if i use headset
on cyanogen.
1. phone ringtone dont have problem.but i cant hear sound when play music,youtube,video.
i think i have problem with my usb port.and this is that make me more confused. i try flash Blue Magic MKIIr1 and all the problem above not happen.
everything is okay.
i'm really gratefull if someone can show me the way to fix this problem.thank u so much
Related
OK
I've always had troubles flashing radios for some reason, I've managed to just not do it but now with Duttys 6.1 out I really need some help
- I've flashed Duttys latest successfully
- I've flashed HardSPL
- But whenever I flash the radio (1.64.08.21) I get a connection error at 99%!!
Now I can still get into the phone using mtty and the boot command.
Am I doing something stupid -- Any help gratefully received!
Alex
ps - I have a UK o2 XDA Stellar
I'm a newbie been here with a AT&T Tilt less than a week and I promise I'm reading, but I'm having the exact same problem. Flashed Duttys dual V4 as my first try last Tuesday without a problem and of course be a crazy new guy I wanted his newest work. So I flashed Duttys 6.1 today and I guess I just can't figure out how to flash radios, because I've tried 2 now and both error out at 99% and I too have to use mtty to get back into the phone. I'll keep reading, but if someone could tell us new guys what the heck we are doing wrong that would be great.
PS I'm glad to be here and this looks like a lot on fun thanks for having me and look forward to helping out someday.
JMan
Hey Alex! I figured it out Brother! Do this and you should be able to upgrade your radio. I was using JumpSPL1.56-KAIS run from my device and I was running into the same problem everytime I tried to upgrade my radio. Would get to 99% and then would error out. So I followed these steps taken from a number of different post and put together until it worked!
1) Make sure you have JumpSPL1.56-KAIS somewhere on your device the file for me is in "my docs" on my Tilt.
2) Run kaiser-HardSPL from your PC with your device hooked up via usb with the green act sync icon. Once you get to the white screen of death on you device, stop unplug you device and soft boot it via your stylus and the reset button. Leave your pc alone right where it stopped in the kaiser-hardspl screen. "should be to the point where it says unplug and replug in your usb you should have the tri color screen press enter to proceed"
3) Now set your connection settings in active sync to not allow usb connections.
4) Now plug you device by in via usb and run Jumpspl1.56-kais on your device. When it has the tri color screen and says usb, unplug usb and plug back in.
5) Now back in the kaiser-hardspl window, continue on with the on screen directions. This should now install hardspl just like the rom or roms that you might have already installed and will say finished.
6) The device should reboot.
7) close the kaiser-hardspl window and let you device fully reboot.
8) Once it is fully rebooted follow these directions: Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up
9)Now run your radio update and it should go through without erroring out at 99%. It will stay at 99% for a bit then jump to 100% success!
My Tilt is working great now with sound and everything. Have not tested anything else yet, came right here and started to let you know what I did to get radio installed.
So now I'm running Duttys WM6.1 newest release with radio 1.64.06.
Call me crazy and sure I know I might have taken more steps than I needed to, but I got it working.
Hope this helps you.
Take care,
JMan
First, are you using a 6.0 rom or a 6.1 rom? If you are using a 6.0 rom you cannot flash any of the 6.1 radios and vice versa. Also, if you have hardspl installed, why would you need to use jumpspl. I have never used jumpspl and I promise I have flashed 50+ times counting, roms, radios and splash screens.
I believe that was my problem, I was never able to get Hard-spl installed and I was using jumpspl to install the 2 roms that I have installed since I got my tilt a week ago. The method I used above allowed me to get hard-spl installed and then I was able to install the radio rom. I am using Duttys WM6.1 rom.
JMan I want your babies!!!
Ok I had actually done everything upto the final step (holding the camera button after a soft reset) but that made it possible to flash the radio just as you described.
So many thanks for sharing your solution!!
Alex
jmandss said:
Hey Alex! I figured it out Brother! Do this and you should be able to upgrade your radio. I was using JumpSPL1.56-KAIS run from my device and I was running into the same problem everytime I tried to upgrade my radio. Would get to 99% and then would error out. So I followed these steps taken from a number of different post and put together until it worked!
1) Make sure you have JumpSPL1.56-KAIS somewhere on your device the file for me is in "my docs" on my Tilt.
2) Run kaiser-HardSPL from your PC with your device hooked up via usb with the green act sync icon. Once you get to the white screen of death on you device, stop unplug you device and soft boot it via your stylus and the reset button. Leave your pc alone right where it stopped in the kaiser-hardspl screen. "should be to the point where it says unplug and replug in your usb you should have the tri color screen press enter to proceed"
3) Now set your connection settings in active sync to not allow usb connections.
4) Now plug you device by in via usb and run Jumpspl1.56-kais on your device. When it has the tri color screen and says usb, unplug usb and plug back in.
5) Now back in the kaiser-hardspl window, continue on with the on screen directions. This should now install hardspl just like the rom or roms that you might have already installed and will say finished.
6) The device should reboot.
7) close the kaiser-hardspl window and let you device fully reboot.
8) Once it is fully rebooted follow these directions: Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up
9)Now run your radio update and it should go through without erroring out at 99%. It will stay at 99% for a bit then jump to 100% success!
My Tilt is working great now with sound and everything. Have not tested anything else yet, came right here and started to let you know what I did to get radio installed.
So now I'm running Duttys WM6.1 newest release with radio 1.64.06.
Call me crazy and sure I know I might have taken more steps than I needed to, but I got it working.
Hope this helps you.
Take care,
JMan
Click to expand...
Click to collapse
You are the STAR! Trillions of thanks. Solve my problem!!!
I love it when when the new guy can help out! Glad it worked guys, and thanks to all the old pros around here for allowing us to read so we can try and help ourselves out.
Take care,
JMan
I think I have fallen in love with this thread. This is truly nice to see guys. Keep up the great work.
i've the same problem, but when reboot Appear immediately hardspl, but i can't re-install nothing !
please help me
I don't want to miss mi tytn
pedro_se_rooot said:
i've the same problem, but when reboot Appear immediately hardspl, but i can't re-install nothing !
Click to expand...
Click to collapse
You need to use MTTY to get things going for you again, here is the thread to get mtty:
http://forum.xda-developers.com/showthread.php?t=371154&highlight=mtty
Search around and see if you can find the step by step to use it, might even be a how to text file in the zip file not sure. This should get you back on your way.
Can someone locate the step by step to use mtty for this man and put it in this post?
Have a good one,
JMan
Not a good day for the Wolfpack, Damn Tarheels!!
Hi everyone,
I have a Mytouch 3G Fender, rooted (of course), and I'm running Ginger Yoshi RC7 with the recommended SPL and radio and the kernel that is specifically recommended for the Fender. Everything's been going absolutely great for about a week, but now, when I plug the phone into my computer, it won't recognize that anything is plugged in. The phone starts to charge when I do it, but no data connection is made. It's as if I'm plugging it into a wall outlet. I took my phone and cable to work and tried it on my work computer, and same thing. I've plugged it into that computer before, and it recognized it. This tells me that it's the phone, not the computer or any drivers or anything. What's really crazy is that I just did a full wipe and reflashed the rom and kernel thinking that whatever got jacked up would be wiped or reset, but the problem remains. Any thoughts? Thanks in advance.
If anyone can help me out with this, I'd really appreciate it. I should add that I just went to t-mobile earlier today and they gave me another cord, and that didn't work either. So we know it's not the computer or the cord. It must be the phone. If anyone has any ideas on why it's doing this and what I can do about it, please let me know. Thanks.
come on people, anyone?
I should add one thing that I just discovered. I AM able to make a connection in fastboot mode, but that's it. I cannot get it to recognize in ADB, in recovery, or when the phone is turned on normally.
I'm sure someone out there has some input for me. If I should be posting this elsewhere, let me know. Someone please assist. Tethering is my source of home internet, so I REALLY need to be able to plug my phone to my computer.
Does Ginger Yoshi RC7 come from Cyanogen mod?
hoshikoong said:
Does Ginger Yoshi RC7 come from Cyanogen mod?
Click to expand...
Click to collapse
I don't think so. Here is the link for it.
http://forum.xda-developers.com/showthread.php?t=932118
However, I don't think it has anything to do with the rom, for three reasons. First, I've looked through the posts in the link above and no one else seems to be having this problem. Second, I've tried getting rid of it and flashing the stock rom for this phone, and still nothing. Third, I can't even do a USB-MS toggle when I'm in recovery mode. In recovery mode, it doesn't matter what rom I have in there, if any at all. I know it's not a hardware issue since I am able to get fastboot to see it. I am quite stumped...
thank you very much work on my device
I literally had the worst combination of events take place the other day:
So, I was running Firefly 3.0, and I planned on replacing it with a gingerbread ROM, (since my apps weren't saving data, for some reason), and I started to notice that my unlock button was starting to hang a bit. I thought this was just another side effect from Firefly 3.0 acting weird.
So, I boot to download, and flash the CM7 kernel with CWM 3.0 on it, and it passes.
The next step is to navigate around in CWM to install the ROM file before you can boot up. But, the power/lock button still doesn't work! So I'm stuck in CWM 3.0, unable to boot correctly. The touch buttons don't work like they do in CWM 2.x, so I'm... stuck.
So, I call Samsung, and I'm having a replacement sent to me within the week, since I can't even power on/off my phone (if it wasn't for CM7's auto-boot when you put the battery in)
So, already having adb installed on my Linux boot, I jump over there to send the adb reboot download command. All this does is reboot the phone "normally"!
What are my options here? I've already copied everything off my phone with adb, and I'm not afraid to use terminal commands to flash something usable just to get it back to stock before I send it back.
*cough*JIG * COUGH*
Sent from my SAMSUNG-SGH-I897 using XDA App
Would that work with CWM 3.0/CM7 Kernel? I've always had weird issues with plugging things in and it just booting up, even when my power button worked.
The jig should work...the only thing that would cause the cm7 kernel to boot when plugged in is if it was off and you were only trying to charge it. The jig just redirects some power into pin 4 telling the bootloader to initiate download protocol...kinda the same way your phone knows when its hooked to a mountable usb port and when its charging out of the wall or something.
similar issue
I recently attempted a flash of fantasy II (2.3.5) captivate, and i got the bootload, and kernel installed and then installed the stock 2.3.5 rom to flash fantasy II over. . . . well after getting the stock rom, i found it had what i wanted, so i was going to stick with that.
i noticed about ten minutes after getting that rom, that my lock button was not working, and the phone would auto boot, i would pull the battery and put it back in and BOOM at&t boot screen right away, not one button pushed, I have bricked and unbricked my phone since then, and i am now simply running 2.1 stock, however; the dang lock button still does not respond at all, and it will auto boot still, is this the kernel or the bootloader? I know its not the rom now . . . . Please help this is awful!
and if you have a solution that i can download please post it!
OK, I have a Samsung SCH-i500 SHOWCASE, (yes I know its not a fascinate/mesmerize). My provider sent a text message to me telling me about Gingerbread update so I installed it. Now my LED flash doesnt seem to work correctly: for instance, when I take a pic with flash on auto it never flashes. If i turn the flash to "ON" then it flashes only when taking the pic, not during the "autofocus" period. Also NONE of the flashlight apps that I had installed can turn on my LED. One more thing, the flash will NOT turn on in video camera mode either. Anyone else have this issue or know of a fix? Below is the Gingerbread update I used (Generic CDMA SCH-I500)
https://www.wirelesspioneer.com/pdfs/i500SWUpgrade.pdf
After months of searching I found the fix (does NOT require root and its very simple). In the same link there is root instructions that work flawlessly!
Follow the instructions in the link below: (to get your phone into download mode power off and hold the volume down button while plugging usb cable into phone.
http://rootzwiki.com/topic/18637-fix-flashlight-issue-root-235-showcase/
Enjoy
provider issue
sounds to me like the update ur provider gave u had a glitch. If i were you, id try to flash back to a later rom then reinstall the update. see if that fixes the issue
Hi Everyone,
I've come on bended knee, and I have about 30 xda windows up where Ive tried to upgrade a perfectly working LG from android 2.2. But no matter what I try I cant get beyond the LG wink icon on the screen.
I have tried fastboot omao4boot 1.22 modified etc but I cant get past MLO (x-loader) I say YES to this but NO to 'fastboot devises' as per instructions (although why I say no to this, I dont know?) anyway it just says 'waiting for device' but nothing happens even if I take the battery out and disconnect from USB and reconnect, nothing ever happens?
So having redone the fastboot procedure, I managed to into boot mode - yellow round icon on screen and then tried to flash using LG flash tool 1.2 with LGP920 30A bin & fls files which it does and completes successfully, I have also used the LG recovery tool to flash recovery and firmware but all of the above wont let me boot the devise it just sits at the LG Icon.
Tried booting into recovery with 3d + vol + key but just ignores and goes to red LG Icon with the usual boot sound, I just cant get anything else to work! Is it down to the MLO loader issue. I dont know what else to do.
Please can anyone help me recover my phone I wanted to upgrade to JellycreamR5 cause its suppose to be a good rom but nothing now works :crying:
I know its not a busy forum now days and most have moved on, but please any assistance to get this beautiful phone going again would be brilliant.
Thanks for the time to read about this dilemma!
ATB
Ok, so if it boots to the LG logo with boot sound it is probably nothing wrong with bootloaders. It is either the system or just something incompatible on the data partition. Of you can make it too recovery try factory reset
Ok I think Ive fixed it!
Did lots of things to try to get to work, but heres roughly the guide.
Used 'rebooter' for Optimus 3d which saved the phone in the 1st instance, it was the only flasher that completed the flash... but remember 1st unplug the phone but micro usb in then remove the battery, then hold the + vol key and insert into the Win XP computer usb, I had already prepared and ran the rebooter.bat file which was waiting for omao device. Once detected keep hold the + key add battery when it says wait 5 secs, dont let the key go, say NO to flash boot but yes to the rest. It will say job done or words to that effect.
Turn on phone holding just the + key to get into download mode. Change the LGE CDMA USB SERIAL PORT to com41 in control panel device manager, refresh search for new hardware to check updated port.
Then use LG Flash to flash V3.0A which worked !
Disconnect the phone remove battery and reinsert, reboot devise, it will boot in TWRP which isnt great but good enough for flash, loaded a Rom onto the sd card and installed the software, after the usual clearing everything like Delvick/Settings etc.
Job done, rebooted and worked, still got TRWP on the boot loading would prefer Clockwork but never mind, had enough of fiddling and just enjoying having my device back
Havent tried a sim in it but might have to to the IMEI fix but hoping not.
Many thanks for your input, I know tech moves on, but there is a wealth on knowledge on these devices and it just seems to be lost in the ether.
Best wishes.