Related
I took my stock AT&T tab and wiped it then flashed Roto JME-4. When I rebooted, I had a black screen for about 60 seconds, with a skinny white line, and I could hear the samsung music. After about 1.5 minutes, I pressed the power key, and screen went totally black - no line. Then I pushed power again, and everything was normal after that, unless I rebooted.
Anyway, here is it fix:
1) go to http://forum.xda-developers.com/showthread.php?t=899196 and download the jj4bootloader.zip file
2) use odin to flash the unzipped jj4 file. It goes in PDA and nothing else in any options.
3) upon reboot, you will have a 100% normal startup with logo and music.
I used the Bootloader Patch app to check this, and it reports it is safe, and that I can flash anything.
Thanks to Roto, Chain Fire, and alexnoalex
Ok, so, just to be sure I'm not going to break my Tab, doing this ONLY changes/fixes the boot animation etc. (get's rid of the AT&T stuff, and puts in the Samsung stuff).
To be clear, I just flashed Roto's latest Euro firmware (Baseband P1000XXJMA, Build FROYO.XXJME), so performing this fix won't affect/change ony of this stuff right?
If I have to re-flash everyting from scratch, then it's really more trouble than it's worth (Blank screen at bootup? Big deal... It's just at boot right? Everything else works perfectly!)
I wish rotohammer and other rom devs would include this information clearly in their initial posts. Took me awhile to find this fix but it works well. This is also important because you can't see the recovery screen without it.
Sent from my GT-P1000 using Tapatalk
Jade Eyed Wolf said:
If I have to re-flash everyting from scratch, then it's really more trouble than it's worth (Blank screen at bootup? Big deal... It's just at boot right?
Click to expand...
Click to collapse
This is just a quick 30 second flash thru odin, it only repairs the black screen, and doesn't touch anything else!
The developers took out the sound and logo to make the rom file size correct.
That's just the answer I was looking for! Thank you good sir!
Glad I could help.
Hello, I have the same problem but I cannot flash the zip file because my computer doesn't detect the tab when I'm in download mode. I tried updating the drivers and software and it still doesn't want to detect it. I cannot get into recovery mode because of the black screen/white line. Do you know what I can do to get my computer to detect my TAB? I tried searching the forum but could not find any info that helped. Any help is much appreciated. Thanks!
AT&T SGH-i987
Firmware 2.2
Baseband P1000XXJHA
Kernel 2.6.32.9 [email protected] #19
Build Froyo.XXJMA
Are you using windows xp, or 7? Put the tab in download mode before you connect to the computer. Is your tab set to usb debugging mode?
I used Win XP, Windows 7 x64 and x86, non of them worked. They can detect my Galaxy S I9000 phone but not my TAB. Yes, I tried it with both debugging on and off, it still doesn't work. Could it be the kernal's fault? Maybe the cable? It will charge the TAB but for some reason my computer won't detect it.
Try different usb cables and ports on the computer.
I tried a different wire and usb ports and it's still not working. I just realized the TAB is not charging anymore. It doesn't make the charging sound when I plug it in. Figured out it's not the cable because it worked on another TAB. Could it be the firmware or kernal?
Not charging when plugged in the computer, or in the wall outlet? Plug it in the wall for at least for hours to get a full charge.
It charges if I plug it into the wall but its very slow like when you charge it via usb. Im using the original charger and cable. There is an x next to the charging/lightening icon on the top when I plug it into the wall and computer.
Just let it charge all night. Be sure its off when charging.
What's the point of having it fully charged? How will that help? My computer still won't detect it even if it's fully charged. I need help to get my computer to detect it so I can restore the original firmware.
I have seen five problems like yours, and after a complete charge, then reboot the phone into download mode, the problem cleared up. They used a different usb port also.
Go to windows update and update your pc.
Look a few threads further down named «help help help»
Ok its currently 50% now. Ill let you know once its fully charged. Thanks for your help so far.
Its 100% and my computer still doesn't detect it. Now what?
Did you have a chance to see the thread “help help help"?
This will sound crazy, but double check your cable - recently someone had the same trouble, because they had dust in the cable connector.
I cannot see the thread you're referring to.
Yes, I did tried a different cable and it's still the same.
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.
As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!
on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock
eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.
is there a way to get back to stock without using a computer? there is an issue with my USB port and I'm getting the charging/discharging issue when there is nothing plugged into the phone and my computer wont recognize the phone and i need to take it in for replacement. everything i find when i search needs a computer? i have tried to clean out the port and all that and nothing works? thanks for any help!
Hey,
I have looked everywhere found many tricks and tips, guides, programs, drivers, yet i'm still have problems. I think that it could be problems with my phone. I recently bricked my phone (installed a rom from a different note 2 version and was stuck in a boot loop). Went to go plug in the phone to restore back to stock and the phone wasn't detected. It was a new laptop so i figured it was a driver issue. Installed the drivers still nothing. Long story short I have installed multiple drivers, Note 2 toolkit (mskip big thanks), Samsung Kies, and Odin (all at separate times) all in an attempt to get this phone connected. I have tried 2 different USB cords, different plug-ins, different computers yet still nothing. Now I have gotten my phone back to stock but went to install a new rom and now it wont load past the boot screen. But that was after my trying for a whole day of plugging in and unplugging before 1 time it was connected. I can not understand the issue besides it being my phone. I don't have anything else to try besides plugging it in and out over and over for the 1 time it decides to work and connect. I am getting very frustrated with this because I currently have no phone. Is their a way to tell if the connector is messed up in any way? I'm really needing help because nothing i'm doing is working.
Steepgnomeking said:
Hey,
I have looked everywhere found many tricks and tips, guides, programs, drivers, yet i'm still have problems. I think that it could be problems with my phone. I recently bricked my phone (installed a rom from a different note 2 version and was stuck in a boot loop). Went to go plug in the phone to restore back to stock and the phone wasn't detected. It was a new laptop so i figured it was a driver issue. Installed the drivers still nothing. Long story short I have installed multiple drivers, Note 2 toolkit (mskip big thanks), Samsung Kies, and Odin (all at separate times) all in an attempt to get this phone connected. I have tried 2 different USB cords, different plug-ins, different computers yet still nothing. Now I have gotten my phone back to stock but went to install a new rom and now it wont load past the boot screen. But that was after my trying for a whole day of plugging in and unplugging before 1 time it was connected. I can not understand the issue besides it being my phone. I don't have anything else to try besides plugging it in and out over and over for the 1 time it decides to work and connect. I am getting very frustrated with this because I currently have no phone. Is their a way to tell if the connector is messed up in any way? I'm really needing help because nothing i'm doing is working.
Click to expand...
Click to collapse
Have the same issue. I am trying fr a work computer, internet restricted, no kies. Now can only recognize note 2 as a camera. When I switch thw usb settings in android, I get the not supported box. Same thing happens at the home computer. I left bb for this??
This is a simple hardware fail and needs to be taken in for warranty repair. The fact that it's bricked, we'll you're just gonna have to cross your fingers and hope they don't charge you for a new one.
Or you can try a jig to get it into download mode and try to push a rom through.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Thats what i'm going to do take it in and see if they can fix it but i want to get it back to stock firmware before but not being able to plug it in to update it is kinda ruining that plan.
Well I turned in 3 notes with custom roms that were rooted and I never got charged, but I always run a stockist rom.
What rom did you flash?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Are u able to boot in recovery?
PM me if u need help
Sent from MOON......
Can you boot into recovery? If so then you can push a file to your SD card using adb. If your having problems with Samsung drivers or what ever good way to test is connecting your phone to a Linux box and setting up udev and adb. Then you can do a adb device command and see if it sees it.
If you have the time to install Linux on a extra hard drive or duel boot you can connect using adb.
Nice thing about Linux is that you can connect directly to the USB device using udev and the device id and with ADB you can push a file onto your phones SD card. Here's a good how to
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Sent from my SGH-I317 using xda app-developers app
Phone: VZW Galaxy Nexus, Rooted, TWRP Recovery, Lean Kernel
For the first (and last) time in my life I decided to dirty flash a ROM (4/16 build of Project Elite) to my phone (from an earlier build of PE). My phone apparently hated that. It has created an odd world of problems for my phone that I am hoping someone may be able to see a trend with and offer up some suggestions for escaping this odd world.
Here are my phone's symptoms:
(1) Earpiece on phone stopped working: During phone calls, I can only hear audio when using speakerphone. I was able to remedy this by getting the SoundAbout App from the Play store. This tool allows you to manually change how the audio is routed. My phone thinks a headphone is plugged in and tries to route the audio through the headphone jack. This app allows me to fix that problem.
(2) USB File Transfer Mode stopped working: When connecting my phone to the computer it will charge (sometimes, see #3) but my computer will not recognize it as a device. Consequently, adb (and wireless adb), fastboot and ODIN all will not connect to my phone because the phone is not recognized. I have uninstalled, updated and re-installed just about every driver set I can find for the Galaxy Nexus/ I know it is not a driver issue because my wife's Nexus connects to the CPU just fine.
(3) Phone Charging is Intermittent: I have trouble finding a trend with this one. If I toggle Fast Charge (Off or On), my phone will no longer charge. This is fixed by powering off the phone with the cable plugged in. At that point the white battery icon appears and the phone begins charging. If I power the phone back on, the phone will continue to charge but will not be recognized as a USB device.
Here is what I have tried over the past 2 days:
(1) Both GNEX Toolkits: With no USB connectivity, adb and fastboot are not options. This option becomes unavailable with no usb. Have tried both.
(2) ODIN: Phone is not recognized by ODIN tool.
(3) Cleaning USB/Headphone Ports: This produced some interesting black stuff, but no results.
(4) Clean Flash of PE 4/16 Build: Wipe data/cache/dalvik and re-flash. Same problem.
(5) Clean Flash of Stock Rooted Build: Wipe data/cache/dalvik and flash. Same problem.
(6) Mobile ODIN: Cannot locate the tar balls for a stock 4.2.2 factory flash. Have found the necessary files for 4.0.2, but these will not flash in Mobile ODIN. I have read that you have to be on the same android version as the ODIN tar files you are trying to flash. I think this is my best option at this point, but I cannot for the life of me figure out how to get Mobile ODIN to work.
As far as I can tell this is a software problem that is baked somewhere deep in the phone. Since the USB and headphone problem started at the same time, I do not believe it to be hardware. My theory is that somehow fast-charge is locked on (?) and my phone is locked to routing the audio to the headset. If I can find a way to completely wipe everything off and start fresh, I believe my problem will be solved.
Does anybody have any ideas what may be going on here and how I may be able to get this phone back to Stock?
tldr; no usb, no headset audio after dirty flash, how do i get back to stock??
In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus
bk201doesntexist said:
In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus
Click to expand...
Click to collapse
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.
7ontheline said:
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.
Click to expand...
Click to collapse
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?
bk201doesntexist said:
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?
Click to expand...
Click to collapse
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.
7ontheline said:
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.
Click to expand...
Click to collapse
You seem to be confusing stuff... Fastboot is not ADB, and you have to feed the same driver to windows twice.
You've done this? Sure the USB port doesn't have a bent pin or something?
Sent from my Nexus
My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app
tdf666 said:
My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Let me know if you figure anything out. I am just dealing with it right now using the SoundAbout App and rebooting my phone whenever it won't charge. It is pretty annoying, but I am at a loss for fixes at this point.
I am not really confusing ADB and Fastboot. I understand that they are two separate ways of communicating with the phone via USB. However, as I stated, there is no USB connectivity other than for charging.
I'm at a loss. Then the other day I got down to 13 percent battery and it started shutting off. I think I'm just going to get another phone. This has been the best and worst phone I've ever had.
Sent from my Galaxy Nexus using xda app-developers app