Related
Hey there, i am feeling somewhat overwhelmed with all of the advice going on out there and need someone who can give me the answer to my specific problem hardware wise without breaking a sweat...
I flashed a froyo 2.2 rom onto my phone a while ago, recently all of my apps stopped working, and i could no longer install any apps.
Couple days ago i tried openning gmail and the screen went black and gave me the bzzzzzz...............................bzzz...bzzz...
vibrating error that you usually get when an app crashes.
Now the phone continues doing that even when booted up and stuff
It starts right after the S screen and repeats until the battery is removed.
My phone can't get into download or reset mode using the 3 button method so i bought a jig off of ebay, works like a charm.
however NOW, i cannot get the computer to see the phone; both when it is on and attached and in download mode and attached. Odin can't see it, neither can Kies.
If i can get either to see it, i can look up the flashing process to make sure everything is right.... but as of yet nothing i am doing is making a difference.
Thanks for any help
Ok, I'd focus on odin so disable Kies (in task manager processes - all the kies processes).
Then I would 1) reinstall the drivers (standalone ones) 2) Have a few versions of odin to try (like 1.3, 1.7 and ez odin) 3) Clean your usb port on the phone (and computer maybe too - whats the harm?).
Usually if you are sure the drivers are Ok then you should be able to odin working with a nice clean port. They are more sensitive to dirt/moisture or whatever than they should be.
Try that and let us know...
BTW Some people think that the order is important but I've never noticed that. I always have odin open and then connect it but cant hurt to try the other way around too.
Hey thanks alot,
I am at work right now but i am optimistic about trying that out lol.
Just so i know for when the time comes and if Odin works, what files do i need to flash it? .pit, .tar and anything else specific for Bell Canada?
I only ask because you are with Bell so it is probably a very simple answer for you. Otherwise I am sure i can find it elsewhere.
Thanks,
I'll keep you updated
Josh
Download the complete jl2 rom from link I posted yesterday (search my posts) with repartition ticked, then flash the kc1 rom from stock rom link on xda or at samfirmware.com and flash without repartition if you want the latest. You could just try the kc1 step but I you need to repartition.
Sent from my GT-I9000M using XDA Premium App
Hey man,
my phone has never been sent in for repairs or replaced...
I was reading one of your other posts and you advised another member to send it in and maybe they will replace/update hardware?
I have still had my phone for less than a year so sending it in will be no problem at all...
Should i flash to the latest myself or return to stock and send it in?
I really appreciate your help.
Thanks
Well he knows his is broken as he can see that his internal memory reads 0 (which means its cooked - ask me how I know...) and he was trying to fix it in a round about way. Or there was the guy who flashed a captivate rom - that was just a big no-no.
You might just have a corrupt partition or some other corruption in the file system. I seem to get that all the time and its a pain but very fixable .
Alright, sooo
-uninstall Kies
-install drivers only
-try to connect to Odin
-If succesful flash with Odin
-dance with joy
Got it, I will update you later when i get home.
Thanks
installed drivers on my work computer (32 bit windows xp) and nothing... I've tried phone off, phone on, phone in d/l mode... It doesn't pick up anything...
I can try it on my Windows 7 comp at home and see if that works but i'm wondering what the worst case scenario is just bringing into Bell and having them fix it... Am i looking at charges, warranty voiding, etc.. etc... to have it fixed or could i BS my way out of it?
Fuuuuuuuuuuuuuuuuuu
pretty sure i flashed the wrong firmware on my phone, when it boots up it says GT-I9000 not GT-I9000M.
It worked fine for like 6 months so i never questioned it... damn damn damn
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
I9000 firmware is completely compatible. The text you see is from the kernel which are always for i9000 unless you have one of the three bell firmwares. So that's not the issue.
Sent from my GT-I9000M using XDA Premium App
RogueCow27 said:
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
Click to expand...
Click to collapse
I would keep trying. I have gotten warranty before and I was in the same predicament as you almost except I knew that the internal memory was dead. But that was also around the time when most of the I9000M models were dying. They might be checking more now.
If you get odin to flash a stock rom then you can go for it but by then you should be able to fix it.
Sent from my GT-I9000M using XDA Premium App
Alright i will keep trying.
As far as the firmware goes, my gf and i both have the same phone, but she kept heres official and i put custom roms on mine (just the 2.2 because it wasn't available)
We are both on bell canada so i asked her to boot up her phone and the beginning message on hers says GT-I9000M so it freaked me out lol
I will try on my home computer,
keep your fingers crossed for me
Alright, so Odin can now see my phone (it was the damn cord, my Win 7 comp couldnt see it but my xp work laptop can)
Which firmware would you recomend flashing? Stock gingerbread or a slight variation?
I am at work right now so i can wait a bit for a good response. It'd really help me out if you could provide links and tips to the best firmware out right now (i have no problem flashing a custom ROM if it is good).
Thanks alot,
Josh
Succesfully Flashes Gingerbread 2.3.4
Thanks for all your help!!!
how did you manage to see it in odin?
i have te same problem with restarting just after first screen (after flashing to gingerbread) but i cant see it in odin so i cant flash it again?
when i connect it when turned off, a small icon appears with usb connected sound but its still not visible.
Is it maybe my win7?
help, anyone please
Did you start in Download mod? Did you kill the Kies processes in you Win7 task manager ?
If yes, sometimes Windows takes time to install the drivers (be sure ton be connected to the internet), you should also close and relaunch Odin.
i launched download mode with sdk, and now i cant start it.
i went to another pc with xp. it installs drivers but odin cant recognize it.
Well i did it on my work XP computer becuase WIN 7 wasn't recognizing it. But it turns out the whole time the cable i was using would connect to charge, but not act as a pc connection.
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
Ive searched and havent been able to find a solution to this, although Ive seen it asked before.
Galaxy Tab P100 bought from a pawn shop. It still has the prior owners (unknown) gmail info minus p/w. I cannot remove the account, or access market because of this. Everytime I tried to data reset (both via Privacy settings and also CWM), add a new rom, or add apps - after I reboot it goes back to the prior owner settings and apks.
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root. Ive rooted/added root explorer and deleted accounts.db and user.db - they go back after. Ive spoken with Sprint and we tried everything they had, as well as a ##786# and MSL number (resetting phone activation I think?). Their response was take it in to send back. I want to fix it myself.
It seems to me that this prior info is overriding and reinstalling every reboot, preventing any new flashing/etc from taking place.
Here is my question. I took it apart this morning and disconnected the battery (thinking maybe it will wipe any memory). But does it have a CMOS-type battery? I noticed there is a small round battery-looking connection soldered into the mainboard (see here - step 7/8 http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1)
Does anyone know what this is? I dont really have anything to lose, but Im not great with a soldering iron, but will try. Im thinking this might be for the memory, and disconnecting/reconnecting this would erase any permanent user information, freeing it up for me to add mine.
Or if anyone has any new ideas I would appreciate it.
Thanks for the time. Ed
Sent from my rooted/rom'd PG86100 using XDA Premium App
It is not a battery backed memory, it is a NAND chip.
Sounds like the chip gone bad.
Sent from my GT-P1000 using XDA
Just an update.
I did not do anything with the round battery thing, as priyana stated the memory is stored on a nand chip. I put the tab back together.
I rooted again, and found the ea24 firmware and loaded it via odin. It took, but the prior user info was still there, and everything (I mean a crapload of apps) began force closing. I did confirm that ea24 was on it. I then flashed back to ef17.
I contacted Sprint repair store again, and they told me that they probably cant fix it, and its something they have to send back. They said that I have done all that they would do in-store.
I dont understand what could be wrong, as I found the prior owner and spoke with her. She had no issues with it. It worked fine prior to her getting rid of it. And it works fine, I just cant get rid of any prior info. I googled it and it seems like there are people out there who have the same problem, but no one has an answer, including sprint or samsung.
So much for my venting. Ill keep trying to find an answer.
roninep said:
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root.
Click to expand...
Click to collapse
First of all, I'd like to apologize for posting something that won't really help, but I recognize this from somewhere else. On some devices, there's some kind of file (that you can delete via the adb prompt when you're root) that on every bootup checks to see if the installed ROM matches stock, and if not, restores to stock. This sounds exactly what you're experiencing when you mention that no ROMs "stick".
I think you should try to look into if there's some files that need to be erased in order for a ROM to be cleanly installed that you haven't gotten rid of. It might also be some kind of feature that the previous user enabled, so maybe it's somewhere around in the settings that you can disable it, who knows.
It definitely does not sound like a memory issue because I don't see how a memory issue could make the stock ROM suddenly appear again after you've installed a custom ROM through CWM (assuming CWM gives no errors or anything and the custom ROM has actually been wiped).
Maybe you can do a more thorough wipe of the device memory manually with some guidance from someone who knows more about how these tablets work :fingers-crossed:
I agree with you about some type of file and bootup. Thats why I went with maybe it being a cmos/nand issue. I couldnt understand that I wiped everything, and information was still coming back. It makes me think that somewhere, something is being stored separate from the main drive.
Ive used the factory restore, CWM (2 different versions - 3 and 5 I believe), and wiped data (factory reset), cache and Davlik three times each before I flashed the CM ROMs. And I have not had any errors or problems installing any of the CWMs.
I spoke with the previous user, and she did nothing above turning it on/off, and using it. I am not on the Sprint network with it, and the wi-fi doesnt turn on until I set it up, so I cant see it being something that contacts Sprint and OTAs from them.
Can anyone tell me if, using ADB, there is a more thorough wipe I can perform ? More than the normal one done through CWM or Android factory restore?
Something similar to the reformatting of a hard drive?
Thanks
Ed
I have the same problem. Did you find any solution?
I believe the previous owner info is stored on sprint servers. When you reboot, it downloads all the crap.
The long time required to reboot explains the slow transfer of data - wireless.
These wireless service providers are pretty sneaky.
Thanks
Hi,
Have you tried formatting both internal and external Sd via Windows? (connecting via USB)
You can also try CM10, it has a different memory map which will write your device completely.
Regards
Sent from my GT-P1000 using Tapatalk 2
I have this same problem with a tab. Its not connected to sprint,has not been on the internet at all. Was there ever a fix for this?? Please let me know its a christmas present and i need to fix this issue. Thank you
Q&A for [GUIDE]How To Unbrick Your Galaxy Tab!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE]How To Unbrick Your Galaxy Tab!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Galaxy Tab 3 T210R / Bricked?
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Bricked, or not bricked? Samsung Galaxy T210R
gtcreative said:
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
___________________________________________
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Click to expand...
Click to collapse
____________________________________________
Update 07/07/2015
I let the tablet's battery run down (as was suggested in one of the threads), and when I plugged it in to the AC power, I got the Samsung Galaxy logo!
I was then able to restart in download mode, and reinstall the md5 file via Odin. Not sure why letting the battery run down works, but at this point, I don't really care. I'm glad that the tablet could be resurrected from the dead, in spite of my mistake.
I hope this is helpful! :victory:
tab not showing up in ODIN
I have my galaxy tab soft bricked, but when I plug it in to ODIN, the pc does not recognise the tablet and therefore I can't reinstall the firmware, although the tablet is connected to the pc, as it gets charging when plugged in.
I've tried reinstalling samsung drivers, killing every samsung keys program running in background, another cable and even three different ODIN versions (v.1.7 // v3.07 // v.3.09), but it is not showing up in any version.
I have been looking for a solution since last year. last year I had windows 8 and it didn't work; then I upgraded to win 8.1. again nothing, and with windows 10 the same story. can anyone help me please?
thank you very much.
internal memory read only my p3100
hi ..
thanks in advance
i dont know what happened to my tab p3100, i am not able place any files in internal memory.
it will get into the main screen and gives bunch of errors like process google play is not working... bla bla bla...
i can uninstal the function but after reboot it will be there in the phone. i am bit tensed what is this is this a bricked one or?
please help me out i tried odin, through odin i installed omia rom 5.1 after that this error i am getting please help me out to solve this.
my phone already rooted..
Once again thanks hooping for the fix.
please mail the fix to [email protected]
So I have been up all night and day trying to figure out how to root my old phone, every root app is just BS. I've followed instructions which are not very clear.
The phone is currently at 6.0.1 and apparently I need to downgrade BUT ODIN won't detect it. probably due to the port being wonky. I have tried many troubleshooting tricks and nothing is working.
If someone could please help me figure this out or tell me I am wasting my time and redirect me to another thread that this was already figured out, that would be great. I will try to provide as much information as possible.
mrpoppop said:
So I have been up all night and day trying to figure out how to root my old phone, every root app is just BS. I've followed instructions which are not very clear.
The phone is currently at 6.0.1 and apparently I need to downgrade BUT ODIN won't detect it. probably due to the port being wonky. I have tried many troubleshooting tricks and nothing is working.
If someone could please help me figure this out or tell me I am wasting my time and redirect me to another thread that this was already figured out, that would be great. I will try to provide as much information as possible.
Click to expand...
Click to collapse
If ODIN isn't detecting the phone in download mode, try on a different PC, you might just need to install or replace drivers.
There is a full root guide here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
AptLogic said:
If ODIN isn't detecting the phone in download mode, try on a different PC, you might just need to install or replace drivers.
There is a full root guide here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Click to expand...
Click to collapse
I tried, I did the whole drivers thing, what I'm saying is the COMPUTER isn't even recognizing my phone, the port on my phone has been messed up for a while, it USED to work with ODIN a few months ago but I haven't tried until recently. Again, I heard there IS ways to do a root without ODIN, which would be nice rather than all this complicated driver stuff. That's honestly what I would rather do.
Side note, I was told to post here after a reddit user said the response time and help would be great. (lol @ me)
I don't have another computer to try, and I have tried several versions of ODIN. So could someone please give some advice, I am starting to think I have 0 options. I hate how the G900A is the most difficult (or one of the more difficult).
Currently there is no root method for the S5 on 6.0.1, downgrading and staying on a lower firmware version is the only way to have root for this phone until a viable security exploit is found; and since you cannot downgrade through ODIN because of the damaged port I'm afraid your only option is to accept the phone as is or get a different phone. All carrier branded smartphones are generally difficult to root, but Verizon and AT&T variants are more so. In the future look for a foreign variant (like the G900F in this case) if root is truly important to you if you plan on staying on a GSM network like AT&T.
Alternatively you could try ordering a new board from eBay if your port is bad but that would require some skill putting it back together (and also your phone would no longer be water resistant) but personally that would be too much of a hassle for me, but it is an option.