Database Develop

[Q] Samsung Galaxy S 19000M MAJOR problems, bad kernal, bad ROM...HELP:(

Hey guys I been having a huge problem with my Samsung Galaxy S 1900M its currently locked with Bell/Virgin Canada. I bought it off of some 2nd hand company. The phone was sold as is saying that it was unable to connect to the computer, (computer does not recognize it at ALL). I bought the phone amusing it was a ROM load problem. It came to me rooted and in almost perfect condition so I was quite happy with my purchase considering I paid $180 USD ($170 CAD). I tried connecting to the computer using the USB that came with the phone, and as stated it does not recognize it at all on ANY Windows/Linux base PCs. I also have another Samsung USB cable that I know works, I tired that as well...no success.
So I am assuming who ever loaded a ROM did not know what they were doing.So I have been searching all over the internet/google, XDA forums and Q&A and everyone point to loading a new kernal....BUT here is where it gets weird. Who ever had this phone previous did not flash a new kernal when updating and put the 3e recovery on the phone, WHICH MEANS I cannot flash any new: Kernals, OR ROMS using the CWM, which btw I am pretty sure isn't working properly because it goes into the base recovery mode with limited options, ex. reboot, sdcard update.zip, wipe cashe, format sdcard...nothing else.
Which brings us back to the original problem, I can not connect to the PC for ODIN to work its magic on the kernal....Please help....
Here is the current load,
Firmware Version: 2.2
Baseband: 19000UGJK4
Kernal Version: 2.6.32.9 shout.leeSEP-09 #1 ( I have never heard of this?)
Build: FROYO.UGJK4

may be a issue with drivers dont quote me though, i had to update drivers after flashing and updateing my galaxy s, as i had simular issue with odin, by not reconize, do you mean windows wont even detect the phone added, or is it connect and nothing? does the phone charge when connected to the pc ?

The phone does charge, but even with the Samsun Keis app, and having the proper Sumsung drivers it still wont even detect the phone. I even went to Device Manager and searched for new hardware/device. I also tried putting it into download mode, and connecting Odin. Windows still wont even detect it. I think its a problem with the kernal....for both issues...

Fixed the problem, hope this helps for others.
Just following up on this as I figured out what to do on my own in case anyone else has this issue.
It was quite simple actually, the kernal was faulty, and so was the ROM that was loaded just as I anticipated
1st:The person that previously owned the phone loaded FROYO custom build that was taken from a leaked version prior to the official release and had no USB support, therefore being unable to connect to the computer.
2nd: The kernal was a custom build and had a 3e recovery built into it and was not able to load any un-verified files(unofficial ROMS, firmwares, updates etc.), therefore I was not able to load a new ROM to fix the first problem, stated above, and visa versa.
I found a program on the market place called "kernal manager", I downloaded the PRO version by searching Google on the computer for the .apk file, I then copied the .apk file onto my external 2 GB SD card and ran the .apk file through the phone. I then opened "kernal manger pro" and opened the menu button, then hit search for kernals. A list of different models of phones came up, I browsed down to my handset maodel (Samsung Galaxy s 19000), press on it, and got a list of kernals. I took each top rated and downloaded kernal listed, did a little research on the internet and found one of them to be suitable. I then went back to the phone chose that kernal through "kernal manager", it asked me to flash then reboot, I hit yes, it then begun the process, and when finished reboot on its own. I then reboot into recovery again after the kernal had loaded and the first reboot and found that the new kernal had succsefully been flashed. I then was able to go about as I please. I uploaded a cm7.zip file to the external sd card, put it in the phone, boot to recovery browsed to the file, and ran it having complete success.
I am now happily running Cyanogen 7. Hope this helps anyone that needs it. Any questions just ask

[Q] ROM issues - newly flashed

Hi All,
I am very new to Android flashing. I got my first Android phone at the start of this year and just decided to go ahead with flashing a rooted ROM onto it tonight. Its a SG3 4G model - GT-i9305T
It all seamed to go ok except that I can no longer connect it to Samsung Kies and am therefore unable to access my backup data. I also cannot upgrade the firmware to the latest Android version because it tells me that my phone has been modified.
this is the ROM I used (in the second quote bubble of the first post):
http://forum.xda-developers.com/showthread.php?t=2080463
I would really appreciate it if someone has some answers for me because I'm seriously stressing out about this! Hopefully someone can tell me how I can get it to mot show up as modified so I can upgrade the Android version. I'm wondering if maybe the modified tag is preventing me from connecting to Kies...?
Thanks in advance
Dave

You can only have Kies/Ota with official Samsung firmware for your phone not custom .
You cannot mix and match custom and official .
Official or XDA Developers forum your choice .
Suggest you read the basic faqs and guides before flashing anything .
jje

research
I guess I should have done a little more research because I never read anything about how rooting my phone would prevent Kies connectivity and the ability to update Android versions....
I have downloaded a stock ROM now so hopefully if I flash that, it will bring things back to normal, which is all I wanted anyway. I just wanted to get rid of some of the restrictions placed on my phone by the carrier

got a result in the end...
Well after finding out the hard way that a rooted ROM isnt all that I thought it was and having to completely erase everything off my phone to do so, I had a possitive result in the end. (if you can call it positive) I downloaded a stock samsung ROM (which is what i wanted in the first place, however didnt search any further after finding the rooted ROM), flashed it to my phone and now I am back in business, all without the crappy Telstra carrier rubbish they forced upon me.
The problem now is that the ONLY reason I tried any of this was in an attempt to have the option to turn off the shutter sound for the camera. Now when the phone was running the rooted ROM, i had this. Since putting the stock ROM on it, I dont have the option in the camera settings to turn off the shutter sound, nor can I take photos siliently when the phone is in silent mode....WHY????? I have even paid for another camera app (camera zoom FX) which claims to have this function although even with the setting for no shutter sound enabled, I get a shutter sound....
Can someone please help me with this one?? I feel like a wasted a heap of time and effort, not to mention stressing out and having to reinstall everything and re-setup my screens, apps and shortcuts, all for nothing!

Remove the shutter sound from the firmware .
System/ media/ audio/ notifications .
Shutter sound removed probably a feature of the rom you used .

nowhere to be found
JJEgan said:
Remove the shutter sound from the firmware .
System/ media/ audio/ notifications .
Shutter sound removed probably a feature of the rom you used .
Click to expand...
Click to collapse
I just tried looking in that location but couldn't find it. there was only 1 file in there and it wasn't the shutter sound. i had a hunt around elsewhere but found nothing. (this is all just using the file browser on the phone - "my files")

You need to read the basics .
You require Root and a root file explorer .

[Q] Samsung Gear1 bricked after update

My gear watch is stuck on the (firmware upgrade encounter an issue please select recovery mode in kies and try again }
Here is what I did:
When trying to get the null rom running.
I got into this problem "IF TWRP IS NOT DISPLAYING CORRECTLY LIKE THE FOLLOWING:", as shown here:
http://forum.xda-developers.com/showthread.php?t=2537338
So I followed the first step:
DOWNLOAD THE STOCK V700XXUAMK7 IMAGE. (FLASH A FRESH INSTALL, DO NOT SKIP)
I accidentally flashed V700XXUCNE9, instead of V700XXUAMK7.
And then without setting up the watch on samsung gear and without getting into the debug mode, I tried to flash null again and it kept on stuck in the "NAND Write Start!!" message.
So I then tried to flash V700XXUAMK7 and it got stuck too after which I started getting
"firmware upgrade encounter an issue please select recovery mode in kies and try again"
I am unable to get into the download mode or the recovery mode. When I long press the power button, it throws me back to the "firmware upgrade encounter.." error.
Please please help. Is my watch recoverable ?
Update: I reflashed V700XXUCNE9 and its up and running now Looks like I was trying to downgrade it and thats where it was failing.
I want null rom on it and looks like it only can be put on top of V700XXUAMK7. How do I go back from V700XXUCNE9 to V700XXUAMK7 ? Can I flash null_03_TWRP2.7.tar on top of V700XXUCNE9 ?

You can, it does not care about any bootloader or stuff like that. It just repleaces a bunch of files on the system partition.

Lucky you, most of the times its a brick, i recommend you to use tizen the battery life on tizen is amazing

Thank you all. I was able to get back to Android and then flash the null ROM. I have the nova launcher running now but I am unable to use internet from my Android phone (LG Optimus G E970). It shows as paired but does not connect to the internet.
Also Play Store crashes when I try to add an account of use existing (says Google Account manager has stopped working).
How do I sync this thing with my phone, getinternet to work, make calls etc. ? Please help.
FYI: I have already checked for this from the FAQ page:
http://forum.xda-developers.com/show....php?t=2573449
INTERNET ACCESS
GO INTO "FULL SETTINGS -> BLUETOOTH -> SELECT YOUR PHONE SETTING ICON (ON THE RIGHT OF PHONE NAME) -> TICK INTERNET ACCESS".
ENSURE BLUETOOTH TETHERING IS ENABLED ON YOUR PHONE BEFORE HAND OBVIOUSLY.
But I am still unable to access internet.

did you get this working,
Did you add bluetooth tethering on your mobile

Flashing Null on V700XXUCNE9
@getmexda,
Did you come right with this eventually?
I have gone through a nearly identical process as you, accidentally flashing V700XXUCNE9, instead of V700XXUAMK7 and have been unable to get either TWRP or Null installed. You said, "I was able to get back to Android and then flash the null ROM". How did you do this? And did you resolve your issues with the internet access?

How to UnBrick Galaxy Gear !
( U CAN TRY THIS METHOD TO UNBRICK YOUR GG )
Hello friend .. previously im also got the same problem as u all when im trying to upgrade my GG1 but after a long search i found this link . What u need is just follow the instructions as given and the important things is DO NOT TRY TO SKIP ANYTHING !
How to UnBrick Galaxy Gear: h*t*t*p://youtube/fS4878klPAQ
( delete * from h t t p coz im not allowed to post link yet )
I hope this will help u coz my GG1 has been recover back .. not to original stock rom but it also upgrade my GG1 to TIZEN !!! :good:
And dont forget to thanks to that guys that send the video and me ( coz i need a credit to post another reply to whom that need a help ) and good luck to u all.
AND TO ADMIN : PLEASE DO NOT BANNED ME COZ IM JUST TRY TO HELP SOMEBODY THAT HAS THE SAME PROBLEM WITH ME .... PEACE !

After Binary Update - Cannot Make Outgoing Calls...???

Hello Everyone...
Posting here first rather than in the "Update Failure" thread because I'm not so sure I have a "failure" with the update....just an issue after the udpate.
I have 2 cloned HTC M9 phones. I say "cloned" as they are exactly the same make, model, ROM, etc (one business, one personal phone). They have the following information if needed:
Sprint HTC M9
SuperSU Free v2.65
Custom ROM ViperOneM9 3.5.0 with no custom kernal
Android 5.1
HTC Sense 7.0
Kernal (standard) 3.10.49-perf-g26c593c
[email protected] #1
SMP PREEMPT
I updated some apps this as I normally do through Google Play. A little while afterward I was prompted to update the SU Binary. I did so on one of my phones. I hit the TWRP option (on the right side of the prompt screen), nothing happened, phone did not reset so I rebooted into recovery. The update ran automatically and the phone rebooted.
I noticed two issues (perhaps there are more). The huge problem is that I cannot make OUTGOING calls. I use a custom dialer PixelPhone Pro. I click on a contact to dial and nothing happens. I type in number to dial, hit the green "send" button to make the call, nothing happens.
I also tried the stock Phone app....same thing, cannot dial out.
I attempted to update the Profile and PRL for the phone, however, as that appears to need to make a "special call" that function is not working either
The other problem I noticed is with an app I have called Quick Settings. The app is always accessible through the pull-down notifications on the phone. Although the app is still installed and functional, it no longer appears in the pull-down notifications. I tried to reset the option to show it there (turning the option off and back on) and it will not show up despite the proper setting chosen.
I still have full root access as I tried a couple root apps (such as Titanium Pro) and have full root access.
I have been prompted on my other phone to update the SU Binary and I am concerned with doing so. Any idea why this is happening and how I can troubleshoot and fit my outgoing call issue??
THANK YOU all very much!!
Scott

Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott

Scudderb said:
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Click to expand...
Click to collapse
**UPDATE**
Still problems....
Right after I first updated the binary the "only" problem was that I could not make calls which I could use the other functions of the phone. I rebooted the phone and I cannot reach any function of the phone because I constantly get the message "...the process com.android.phone has stopped" obviously related to the previous problems.
I dirty-flashed the ROM...that did no help. I even tried to flash an older SuperSU version (I don't know what that would have done....I'm running on HOPE now ) and that didn't help. Re-dirty-flashed the ROM a second time. Again that didn't help.
I flashed an old backup and THAT WORKED fine. Problem is that the backup is 6 months old. I could quit and totally clean/wipe/install the ROM and start again from scratch but I reeeeeeallly don't have time for that at the moment.
Is there ANY way I can simply get my com.android.phone process back?? Why did all this happen in the first place??
ANY help is greatly appreciated!! THANK YOU!!!

Motorola G6 no sound during calls after flash

Hello,
I have a motorola G6 that after bad root get stuck on bootloop.
I flash the phone with two roms but the phone after flash dont have sound during calls, the earpice dont work even in loudspeaker, but the phone rings when is receving calls.
anyone already have this problem?
tanks

This question is probably in the wrong section but anyway...I did. I never checked the phone prior to rooting so I'm not sure if a "bad root" was the cause or not. However, I experienced the exact same problem as you. I was originally on build OPS27.82-19-4 so I reflashed stock OPS27.82-19-4 as described here. But I still had the same problem. On a whim I randomly flashed build OPS27.82-19-4 following the same instructions. The phone has been working great ever since (I have it rooted, xposed. etc...). Not sure why there was a problem, or if reflashing the newer build "fixed" it or not...but as I said, all is good now. FWIW, when I check the sim status in settings>about phone, the network section is blank. It was blank when I had problems too.
Perhaps this will help you..
PS When I reflashed the firmware, the phone would boot into fastboot mode, then when I selected "Start" it would boot to the OS. If you run into that, here is how it was fixed. See posts 5, 6, 7, & 8.
Good luck!

I had a similar problem, I did the root, TWRP, I ended up giving up and flash again on the stock of the bike G6 Play (Brazil) available here in XDA, to my surprise, he made and received calls normally, the speaker for music and connections of other applications (Whatsapp, Messenger, Hangouts, etc.), but it did not work for the rom dialer.
I thought I had a problem, it was when a system update appeared, I installed it and it worked again.
I figured it was some rom bug I installed.

Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks

Multiredes said:
Tanks for the help.
I solved the problem flashing the phone with flashrom.bat instead of put the comand one by one.
Many tanks
Click to expand...
Click to collapse
That's because a custom rom or GSI does not have all the necessary files. 99.9% of the time, flashing stock will fix a problem.