I have what was a rooted Samsung Galaxy Tab from T-mobile. I installed sipdroid, it somehow fouled up my Dialer program, so in my infinite brilliance I deleted it. Now I can't connect via my cellular radio.
What I've tried already:
Holding power + volume up, wiping and recovering tab
downloaded odin, flashed overcome rom and t-mobile modem
praying
Each time I start it back up, no cellular connection. I try to check out the wireless settings, and the network area is grayed out. I try to go to "About Tablet" and check out the phone status ... it throws up the "process stopped unexpectedly: com.android.phone" error.
I'm totally stuck, and I'd really appreciate some advice/help. I also tried to download the stock firmware from one of the other threads, but the deodexes link appears to be dead.
That stuff is greyed out for a few reasons: no modem installed, no sim card inserted/inserted wrong, tab is in flight mode, fata connection is off (last two are in the power menu).
To check for installed modem: settings, about, baseband.
Related
To start, I was using I9000XXJP2 firmware on an unlocked samsung I9000 from Bell. I installed a lagfix a few days ago and everything was working fine. The phone was really slow and freezing a lot today so I decided to restart. Ever since then, the phone is stuck on the Samsung S screen (not the one with the triangle). I can get into download mode just fine and i tried reflashing XXJP2 using odin back onto the phone. Odin does everything fine up until i see a blue 'reset' on odin and the phone is in recover mode with the options asking for me to restart the system etc. I restored to factory settings from there and even cleared the cache and restarted but it is still stuck on that "S" screen at startup. Odin only says "pass" once the phone is disconnected. So as of yet I haven't been able to flash a working ROM back on the phone. If you have any ideas as to which ROM i should try, if you could place a link with that, I would be very grateful.
I've had this problem myself a couple of times (just happened today in fact).
Boot into recovery mode (vol-up, home & power). Do you see any error messages in yellow under the menu?
I was unsuccessful at reflashing any of the Froyo firmwares so I reverted back to the last official 2.1 firmware from Bell JH2. Since I was coming from a 512 pit firmware, I didn't repartition or specify a pit file. This ended up working for me. I've since flashed to JK3 and am about to go back to JPU.
Reply:
I actually do see an error message E:can't mount /dev/block/mmcblk0p1, Can't mount SD card.
I should mention that Im using the unlocked bell phone on fido. Will i lose the unlock if i downgrade? Also, if you could point me to the site where i can download bell firmware, that would be awesome. I went to samfirmware.com and they dont have canadian versions there.
Unless one of the pros comes by and says otherwise, I understand that's the error indicating internal sdcard issues.
However... if the thing is dead, you can't hurt it more by trying some fixes
You can get the official and unofficial Bell firmwares from samfirmware.com, you just have to look in the US section. You want the firmwares starting with "i9000UG". Here's direct download links for you:
JH2 (official 2.1)
http://www.multiupload.com/ZNBT2RY5Y0
JK3 (unofficial 2.2)
http://www.multiupload.com/WTZGSKJGPF
JK4 (official 2.2)
I've heard people flashing this via CWM but I haven't see the files.
Also, I've seen references to people saying their phones begin working again after this error msg after they've left the battery hour for hours.
Let us know how things go.
Reply:
No go. When i flash to 2.1, it just shows the "S" screen and turns off. When i flash to 2.2, does the same thing as my first post. I still can get to the download screen through all of this so I hope its not messed up too bad.
I tried several times this afternoon before it worked including clearing data/cache.
Although, I had a different error message so you might be SOL in the end.
called samsung
So I called samsung this morning and they basically said they won't repair it because Bell handles repairs. Since I dont have a bell account, I can't get it repaired. I keep reading on forums that if you can get into the download mode, if you see the battery icon when you plug the phone in, its not totally bricked so i still have hope yet everything I've tried doesn't work. I tried to adb into the phone in recovery mode and it detects it but says I dont have permissions to push files onto the phone. If anyone can tell me what possibly went wrong and if it is fixable, how, that'd be awesome because right now this is a very expensive paperweight.
Alright
First of all i would like to say that im a completly noob in android OS and that i possiblely have done something idiotic!
So.. was i getting annoyed by a slow phone (have voodoo lagfix installed and set to be ON. It seems to work like ****!)
I rebooted into recovery mode and entered advanced settings and i was curios about the partition setting.
Then i picked "partition" and set it be on "4096MB" and at last i picked it to be "ON"
I finished it and reboot the phone.
Now i only getting the startup logo and nothing happens.
I have the 3 button fix installed to be sure i can get into recovery mode again, and i have tested it and it WAS working.
Now it does not work with the Vol up+Home+Power button combination.
I can get 3 different screens like the startup logo, the download mode and the battery charging logo, which not showing any sign on charging.
instead it show the loading circle, frozen on the charging logo.
So what can i do ? - I really really hope there is a solution on this huge problem, because it is worthless now and i only got this phone less the a month.
Thank you.
You'll likely need to flash back to your stock firmware and start over (meaning you loose all data on your internal memory).
Do you know how to use odin? Do you know where to find your stock firmware? I'm on my phone right notes so can't provide any links but you can check the reference guide thread in the i9000 general forum (it's one of the stickied threads) on how to flash firmwares. You can find your stock firmware on http://samfirmware.com
Hi. I have a problem with my Ace. I flashed an XWKTM firmware in Odin and I couldn't connect to Wi-Fi anymore. When I enable the Wi-Fi it does nothing and suddenly the "Scanning" text appears and dissapears like 5 times and when I try to connect to my network, it says "Disconnected". I tried to wipe data, cache I flashed it again. I tried the *#*#526#*#* method and it said Driver load successful and still didn't work. How can I fix it?
There's some screens : http://imgur.com/a/vbl70
/EDIT - I plugged another router in and Wi-Fi works now. I thought that my Ace broke. You can delete this thread.
Hello,
I was on stock/rooted OC3, OTA'd to OE2, then rooted.
Here's a breakdown of what I did so far:
Original problem - Tried build.prop memory tweak which caused boot loop that I was unable to recovery from.
I did OC3 Odin, no service, would not activate, constant rebooting after about 30 seconds of use or plugging in USB to PC, with or w/o USB debugging.
I did the full OE3 Odin, from Sammobile, same results as OC3 Odin. Says "unknown" for Baseband in both cases and continuously reboots.
Then I flashed "Trailblazer101_925V_OE2_FLASH_ME.tar" but it still didn't work.
I've tried "Factory Reset" through Android and through the stock recovery, with the same results. At one point it rebooted and gave a message "due to failed factory reset....."
I don't know what else to try. Can anyone shed any light on this issue?
*edit* Today, of course after posting this threat I flashed "Trailblazer101_925V_OE2_FLASH_ME.tar" again and for some reason it stuck and it now seems to work.
Mods can delete this post, if need be. Thank you.
So this issue is testing my sanity and understanding. I was on a custom rom, rooted with OF3. I wanted to ODIN back to stock, flashing all 4 files (OCE).
Everything works successfully, except when the phone boots up I won't have a cellular signal until I update to OF3, which means rooting again with pingpong, loading Flashfire, flashing the of3 zip and then the modem and boot file. After that, signal is back. But why?? Does ODIN not hit every bit of memory on the phone?
Which takes me to my next question. S Voice is missing an option to open via home key. This is true after ODIN, going into recovery and wiping cache partition, loading up cleanrom etc. Long pressing home key only will open google now. If i disable that, nothing happens. If I use a program to map s voice to the hardware button, nothing happens. So it feels like something just isn't quite right.
Anyone have any insights or ideas?
PS- I also tried the option to do a NAND erase with ODIN and "factory data reset' in recovery too. Same signal issue until OF3 update and s voice + home key option missing.
I think I vaguely remember seeing similar behavior in one of designgears' threads for the s6. He found a solution, but I don't remember the details. Hope this helps, at least to point you in the right direction. AoN
anneoneamouse said:
I think I vaguely remember seeing similar behavior in one of designgears' threads for the s6. He found a solution, but I don't remember the details. Hope this helps, at least to point you in the right direction. AoN
Click to expand...
Click to collapse
Thanks for the response.. I sent a pm to @designgears to see if he remembers a solution because I did a search on his posts, and couldn't find anything obvious. The whole issue is a little bizarre and I've been flashing roms for years. It's not so much the fact s-voice is not working via home button or no cell after initial odin as much as why it's not going fully back to factory stock.
I'm going to try one last time to ODIN to stock, then Recovery --> 1. factory default 2. wipe cache partition.
Update: Still no cell after odin. I downloaded the files from this thread: http://forum.xda-developers.com/att-galaxy-s6/general/odin-tar-files-sm-g920a-t3103835. After successful ODIN flash of all 4 files, I rebooted into recovery, selected factory data reset then wipe cache partition and reboot. No baseband/cell signal. Eject and reinsert sim, still nothing. In fact, the whole 'mobile networks' option is missing from the Connections tab. This must have something to do with the OF3 update in Designgear's thread. Home button also still launches google now, with no option in S Voice to activate via home key. Ugh. Going to update to OF3 to get cell back.
ChristopherXDA said:
Thanks for the response.. I sent a pm to @designgears to see if he remembers a solution because I did a search on his posts, and couldn't find anything obvious. The whole issue is a little bizarre and I've been flashing roms for years. It's not so much the fact s-voice is not working via home button or no cell after initial odin as much as why it's not going fully back to factory stock.
I'm going to try one last time to ODIN to stock, then Recovery --> 1. factory default 2. wipe cache partition.
Update: Still no cell after odin. I downloaded the files from this thread: http://forum.xda-developers.com/att-galaxy-s6/general/odin-tar-files-sm-g920a-t3103835. After successful ODIN flash of all 4 files, I rebooted into recovery, selected factory data reset then wipe cache partition and reboot. No baseband/cell signal. Eject and reinsert sim, still nothing. In fact, the whole 'mobile networks' option is missing from the Connections tab. This must have something to do with the OF3 update in Designgear's thread. Home button also still launches google now, with no option in S Voice to activate via home key. Ugh. Going to update to OF3 to get cell back.
Click to expand...
Click to collapse
im pretty sure you cant go from 0f3 back to oce.
Yeah, that does seem to be the case..