Database Develop

Help me please...galaxy tab Exclamation mark

i want to flash new firmware but i have little problem...now my tab is show exclamation point between a phone and a computer.
but Galaxy tab can not remove battery for reset this error...
Help me please....

water30 said:
i want to flash new firmware but i have little problem...now my tab is show exclamation point between a phone and a computer.
but Galaxy tab can not remove battery for reset this error...
Help me please....
Click to expand...
Click to collapse
what did you do to get to this screen? Is this after or before you upgraded firmware?

GANJDROID said:
what did you do to get to this screen? Is this after or before you upgraded firmware?
Click to expand...
Click to collapse
after upgrade firmware odin show reset but the my tab not reset then i just manual reset (i can take this method for my galaxys ) after that.....

Edit:
Had the exact same thing happen to me, but its just a bad flash.
Download the JM6 zip (in the development forum) and flash it via Odin. after the device has rebooted, if the previous apps havent been deleted, go into recovery and perform a factory reset and reboot again

i have the same problem, phone - exclamation point - computer ... but i can't get into recovery mode to do a wipe .
is i press VOLUME UP or DOWN + POWER i always end up with the same exclamation point screen ... any help?

primeroz said:
i have the same problem, phone - exclamation point - computer ... but i can't get into recovery mode to do a wipe .
is i press VOLUME UP or DOWN + POWER i always end up with the same exclamation point screen ... any help?
Click to expand...
Click to collapse
Read my above post. Go into download mode (volume down + home + power) you'll still have the same image but the phone WILL be in download mode. Then flash your previous firmware and you're sorted.
Sent from my GT-P1000

You probably got that by messing with the kernel. Fund the zImage from the firmware, extract it with a .tar extractor then use something like heimdall to flash the kernel and it should work.
Sent from my GT-P1000 using Tapatalk

Hi. I'm looking for solution for my problem but nothing has helped me. I cannot restart mu GTab or put it in download mode. I always land into Android system recovery <3e>.
My problem: I cannot restart my GTab anymore. It started when I wanted to do a backup with ROM Manager. Unfortunately EURO TAB isn't supported yet. Then I want to find out whether nandroid backup is possible. From ROM manager I booted into recovery. But there isn't nandroid backup. And now I cannot boot GTab anymore. Every time I restart it brings me back to Android system recovery <3e>. I would be grateful for every solution.

Help please
slaia said:
Hi. I'm looking for solution for my problem but nothing has helped me. I cannot restart mu GTab or put it in download mode. I always land into Android system recovery <3e>.
My problem: I cannot restart my GTab anymore. It started when I wanted to do a backup with ROM Manager. Unfortunately EURO TAB isn't supported yet. Then I want to find out whether nandroid backup is possible. From ROM manager I booted into recovery. But there isn't nandroid backup. And now I cannot boot GTab anymore. Every time I restart it brings me back to Android system recovery <3e>. I would be grateful for every solution.
Click to expand...
Click to collapse
Having the same problem too... anyone can help?

If you see Phone-!-Pc on the Tab screen it is the download mode.
You can reflash it using Odin, however, you will need to do full Rom flash. I had similar problem and solved it by replashing.
I followed the latest guide published in this forum and Roto-JME rom with reformatting of internal sd.

Phone ! PC error FML!!!
GANJDROID said:
Edit:
Had the exact same thing happen to me, but its just a bad flash.
Download the JM6 zip (in the development forum) and flash it via Odin. after the device has rebooted, if the previous apps havent been deleted, go into recovery and perform a factory reset and reboot again
Click to expand...
Click to collapse
Where can i download the JM6 zip??

Hey guys,
I tried to manually update my tab to Gingerbread today via Odin, but it kept hanging on select partition (I discovered I used the wrong PIT for the firmware I was going to flash, but as I didn't select the firmware yet that shouldn't be a problem). At last I decided to quit Odin (which might have been stupid...) and try it again. Then it kept haning even earlier, so I tried to restart the device in download mode. However, whatever I try it keeps giving the Phone ! PC sign. If I try to just boot, if I try to go into recovery mode or if I try to go into download mode. I saw a lot of possible ways to solve the problem, but my PC doesn't recognize the tab anymore. If I connect it, it does give the "usb device connected" sound, but there is a popup which sais "USB Device not recognized. One of the USB Devices attached to this computer has malfunctioned and Windows does not recognize it. For assistance in solving this problem, click this message". I already tried to reinstall the driver but it doesn't work. Also Odin and Heimdall don't detect any device.
Does anyone know a solution for this problem? Maybe taking the battery out? (for which I have to buy a new triangle screwdriver, so I need to know if it could possibly work first. It takes some weeks to order such a thing I think...)
EDIT: I played around a bit with the drivers again, and suddenly both Heimdall and Odin recognized it. However Odin stopped recognizing it again. Then I pressed "read PIT" in Heimdall, which worked. After that the device started booting up to the Samsung logo animation and then powered off again. Now it doesn't do anything anymore, not even showing the Phone ! PC screen. I'll charge it overnight (maybe it's gone empty during the process), so I hope that helps.....

In some strange way, the phone works again..... So never mind my post above.

[Q] No Downloading mode

Hi
I bought my unlocked samsung captivate recently and it had pre installed continuum rom on it. I tried to install CM7 on it, but things went downhill pretty fast after that.
This is what I did:
- Read the thread "read before flashing" got the cm7 mod and got the phone into downloading mode using the volume buttons and usb
- Then I read that I can use ROM Manager and used that to first backup and then selected the cm7 package in the install rom (I checked all 3 boxes to wipe data, both caches)
- After it rebooted it showed the Cyanogen screen but after that it kept going in loops - restarting and installing (for 3 seconds hardly)
- I put the phone again in the download mode (it went to the mode fine)
- After that, when I removed the USB cable or the battery I forgot which one : it booted back with random dots on black screen
Here is what I have tried:
- The 3 button combos and everything else just shows a blank white screen or a black screen with random dots
- I have installed the heimdall suite and installed the drivers using that
- my phone is recognized as "USB mass storage device" but nothing else works
- I have also tried the Odin method to detect the phone but it doesnt get detected
- I know about the USB jig but it will take 3-4 days before I can procure the mini usb jig
Please let me know what else I can try to get to download mode (I sincerely hope there is still a method left). As you all can see this is my first post here, so please let me know what other details I can provide.

The white screen or black screen can be download mode. The image might have gotten corrupted. I recommend reflashing to stock an reinstalling either heimdall or regular samsung drivers. You can't have both since one mess the other one up.

Check my sig. Link to a thread on how to get download mode.

Hi
Thanks a lot for the prompt response. Something weirder than the last 5 hours happened:
- I connected the phone to the comp and launched kies just to try. It didnt do anything but it was recognizing the device
- I tried for it to connect left it for 10 minutes. Disconnected the phone since nothing was happening
- Then I disconnected again and powered off/battery out. Then connected usb then connected to comp and let go of the volume buttons (which I was holding before connecting to the USB)
- Win7 installed some driver and then somehow....somehow....it was detected in the "Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY" - it showed added
- After this I just clicked on it and all went smoothly from there on
- Now I am on the At&t stock firmware
Can anybody explain/think why this worked? Was it just a miracle ?
Also, any suggestions as to :
- what I did wrong the first time round which I can avoid this time when I install the mod.
- why was the cyanogen mod installation stuck in the reboot/install loop?
- Once I am in the download mode what is the safest mode to exit it? Battery out? USB out?
- Should I use ROM Manager or is it not a good software?

Sometimes you just get lucky. Most likely kies repaired the drivers, restarting phone got the ball rolling. I guess. Just be happy it worked.

I can't speak as what exactly went wrong, and I haven't used CM7 in a long while BUT Rom Manager is trash for our Galaxy S phones. =( sad truth but don't waste your time with it.

Thanks, yeah I am definitely happy that it worked but now I want to try and understand the things I did wrong so that I can do it correctly this time.

Don't use Rom manager next time. Do it from CWM (update.zip) or a kernel that has it baked. Do it manually is the best advice I can give you.

could you guide me to where i can read what a cwm is?

CWM= Clockwork recovery mod. What version of android are you running?

prbassplayer said:
Don't use Rom manager next time. Do it from CWM (update.zip) or a kernel that has it baked. Do it manually is the best advice I can give you.
Click to expand...
Click to collapse
This. Rom manager sucks. I would use odin to flash one of the leaked gingerbread builds, and then flash a custom kernel, also with odin (boogs kernel comes to mind), which has clockworkmod built in. Place the cyanogenmod install file, along with google apps, on the internal sd card. Then it's just a matter of holding power and both volume buttons until the phone reboots, when you see the white at&t screen release the power button but keep holding the volume buttons. You should eventually come to a black screen with green writing if memory serves me correctly, this is clockwork mod. I actually don't remember what color the writing is, but it should say CWM recovery at the top. choose the options to wipe data/factory reset (navigate with volume keys, select with power key), wipe cache, then go into advanced, and wipe the dalvik cache. once this is complete, go back to the main cwm menu, and select "install from sd card", then just find the cyanogenmod zip, select it, and let it go. it will reboot once to repartition to the mtd file format, and then it will automatically continue the install. Welcome to CyanogenMod. Use the same method to flash the google apps package. It sounds more complicated than it actually is.

[Q] CM10 Stuck at bootloop, can't enter recovery, and computer doesn't detect

So I've seen a lot of threads on here with this kind of problem but none of the solutions work for me.
I just flashed CyanogenMod 10 nightly, was tinkering around on it, rebooted and I was just stuck in a bootloop. I can't get into recovery but I can get into download mode. However, my computer just doesn't detect the phone at all. I can't get Odin to detect it to flash a new bootloader or anything. I've tried installing Nexus drivers and everything. It just doesn't even detect that anything has been plugged into the computer. But the usb powers on the phone. If I plug into power I just get a spinny loading wheel that doesn't move and refreshed every few seconds.
I'm stuck. I can't get into recovery to flash, and I can't get my computer to detect it to flash. Help me please?
EDIT:
Okay so tried 3 different USB cables and I've found one that works. I tried flashing a new bootloader but I used the bootloader bit on Odin instead of pda (total noob mistake) now my screen is just black and won't turn on. I can get into download mode to flash stuff again. But what do I need to put in the bootloader section to get it back to normal?

I think you have to start from Gingerbread again
Search on samifirmware a 3 files firmware of Android 2.3.6
After that search on google a Step by Step guide how to flash a Rom with Odin.
I think after that i should work.

ChrissehB said:
So I've seen a lot of threads on here with this kind of problem but none of the solutions work for me.
I just flashed CyanogenMod 10 nightly, was tinkering around on it, rebooted and I was just stuck in a bootloop. I can't get into recovery but I can get into download mode. However, my computer just doesn't detect the phone at all. I can't get Odin to detect it to flash a new bootloader or anything. I've tried installing Nexus drivers and everything. It just doesn't even detect that anything has been plugged into the computer. But the usb powers on the phone. If I plug into power I just get a spinny loading wheel that doesn't move and refreshed every few seconds.
I'm stuck. I can't get into recovery to flash, and I can't get my computer to detect it to flash. Help me please?
EDIT:
Okay so tried 3 different USB cables and I've found one that works. I tried flashing a new bootloader but I used the bootloader bit on Odin instead of pda (total noob mistake) now my screen is just black and won't turn on. I can get into download mode to flash stuff again. But what do I need to put in the bootloader section to get it back to normal?
Click to expand...
Click to collapse
Nothing. Never put anything in the bootloader section. Instead, look for a rom that has bootloader in it. I believe that the darky resurrection rom has bootloader.
Sent from my Nexus 7 using Tapatalk 2

I had the same issue with cm-10-20121125-NIGHTLY-galaxysmtd (after with cm-10-20121126-NIGHTLY-galaxysmtd as well!),
symptoms: after automatic install of mentioned version the phone rebooted, but I've got stuck in bootlop, and I couldn't enter in Recovery Mode, just in Download Mode.
I've managed to fix it in the following way:
1. I've downloaded the Semaphore kernel for JB (Semaphore ver. 2.6.0), and unpacked it.
2. I've used heimdall: `heimdall flash --kernel zImage`
3. After that the phone boots and CM finishes the upgrade as usual. (I've did not lost anything from my data.)
(Environment data: OS: Ubuntu 12.04, Heimdall 1.3.2)

Boot loops with cm-10-20121125-NIGHTLY-galaxysmtd & cm-10-20121126-NIGHTLY-galaxysmtd
frantique said:
I had the same issue with cm-10-20121125-NIGHTLY-galaxysmtd (after with cm-10-20121126-NIGHTLY-galaxysmtd as well!),
symptoms: after automatic install of mentioned version the phone rebooted, but I've got stuck in bootlop, and I couldn't enter in Recovery Mode, just in Download Mode.
Click to expand...
Click to collapse
Thank you very much for the information!
I was thinking I did something wrong... :crying:
Update:
The newer versions cm-10-20121129-NIGHTLY-galaxysmtd & cm-10-20121130-NIGHTLY-galaxysmtd are OK again.
With kind regards
Joe

frantique said:
I had the same issue with cm-10-20121125-NIGHTLY-galaxysmtd (after with cm-10-20121126-NIGHTLY-galaxysmtd as well!),
symptoms: after automatic install of mentioned version the phone rebooted, but I've got stuck in bootlop, and I couldn't enter in Recovery Mode, just in Download Mode.
I've managed to fix it in the following way:
1. I've downloaded the Semaphore kernel for JB (Semaphore ver. 2.6.0), and unpacked it.
2. I've used heimdall: `heimdall flash --kernel zImage`
3. After that the phone boots and CM finishes the upgrade as usual. (I've did not lost anything from my data.)
(Environment data: OS: Ubuntu 12.04, Heimdall 1.3.2)
Click to expand...
Click to collapse
I want to buy you a beer Thanks a ton
I did this on windows 7 x64 without any problems (I had to install driver from heimdall suite)

Same here, but computer WON'T detect, normally does
Hi
I'm desperate, no phone, stuck on galaxy S boot screen, will boot into download mode but not recognised by computer
Any ideas?
Thanks

GT-I9295 Brick? Stock ROM fail on system.img.ext4 in Odin

Hi all.
A newbie, I ended up lost after trying to flash the latest CM 12.1 on my Samsung Galaxy S4 Active GT-I9295.
At first, there was an issue with the recovery, which upon entering showed black screen instead of the tool itself.
Trying to fix this, I managed to remove the recovery through flashing the Stock ROM, which has failed in Odin on the "system.img.ext4" instead - could not paste screenshot link here, feel free to ask for it, please!
I must say that I have tried hard to figure out what to do with the mess I have caused, but now I am helpless.
Would anyone give me some nice piece of advice to get my phone going again?
Thank you so much!

mcjenda said:
Hi all.
A newbie, I ended up lost after trying to flash the latest CM 12.1 on my Samsung Galaxy S4 Active GT-I9295.
At first, there was an issue with the recovery, which upon entering showed black screen instead of the tool itself.
Trying to fix this, I managed to remove the recovery through flashing the Stock ROM, which has failed in Odin on the "system.img.ext4" instead - could not paste screenshot link here, feel free to ask for it, please!
I must say that I have tried hard to figure out what to do with the mess I have caused, but now I am helpless.
Would anyone give me some nice piece of advice to get my phone going again?
Thank you so much!
Click to expand...
Click to collapse
Did you try odin 3.10 by any chance? That could be the problem. Use odin 3.07 or 3.09, boot manually into download mode with complete shutdown & using vol down + power key and odin the stock ROM, reboot and do the same with TWRP (hold down the vol up key after flashing recovery when it is rebooting)

JASONRR said:
Did you try odin 3.10 by any chance? That could be the problem. Use odin 3.07 or 3.09, boot manually into download mode with complete shutdown & using vol down + power key and odin the stock ROM, reboot and do the same with TWRP (hold down the vol up key after flashing recovery when it is rebooting)
Click to expand...
Click to collapse
Hi there, Jason.
Yes, I did exactly as you say - got to the download mode, plugged in, ran Odin (tried 3.10, 3.09 and 3 v1.85) started flashing the latest Stock ROM and the I only got as far as the "system.img.ext4", when the download failed. Sometimes that happened even earlier, saying that there was no PIT etc.
When trying to flash the CWM recovery, it goes through OK, but then when trying to get into it, the screen just goes black, as described in my previous thread - "CWM or TWRP Recovery Black Screen".
I am stuck.
But I still hope that I am not a proud brick owner
John

mcjenda said:
Hi there, Jason.
Yes, I did exactly as you say - got to the download mode, plugged in, ran Odin (tried 3.10, 3.09 and 3 v1.85) started flashing the latest Stock ROM and the I only got as far as the "system.img.ext4", when the download failed. Sometimes that happened even earlier, saying that there was no PIT etc.
When trying to flash the CWM recovery, it goes through OK, but then when trying to get into it, the screen just goes black, as described in my previous thread - "CWM or TWRP Recovery Black Screen".
I am stuck.
But I still hope that I am not a proud brick owner
John
Click to expand...
Click to collapse
Are you using the original USB cable if not then try with another cable. Also what is the device name shown when you boot into download mode

mcjenda said:
Hi all.
A newbie, I ended up lost after trying to flash the latest CM 12.1 on my Samsung Galaxy S4 Active GT-I9295.
At first, there was an issue with the recovery, which upon entering showed black screen instead of the tool itself.
Trying to fix this, I managed to remove the recovery through flashing the Stock ROM, which has failed in Odin on the "system.img.ext4" instead - could not paste screenshot link here, feel free to ask for it, please!
I must say that I have tried hard to figure out what to do with the mess I have caused, but now I am helpless.
Would anyone give me some nice piece of advice to get my phone going again?
Thank you so much!
Click to expand...
Click to collapse
Hi. Try this:
Remove the battery and USB cable from your phone, and wait at least 3 seconds.
Place the battery only back in your phone.
Fingers on volume down and home, then another on power. (cold boot directly into download mode - this is important!)
Press up to enter download mode.
Insert USB cable into phone and lie it down somewhere it won't move or be touched during the flash.
Download a good current copy of Odin from:
https://idlekernel.com/flash-tools/Odin_3.10.7.zip
Extract the archive and run Odin.exe
Download this emergency recover tar for your device (newest firmware revision available as of right now):
https://idlekernel.com/flash-tools/recover/BL_I9295XXUDPA4_RECOVER.tar.md5 (also has official TWRP 3.0.0-2)
Insert "BL_I9295XXUDPA4_RECOVER.tar.md5" in the [BL] slot.
In the Options tab put an [✔] in the "Phone Bootloader Update" checkbox.
If you don't have anything you need on your internal storage, put an [✔] in the "Nand Erase All" checkbox.
Click [Start].
Once the progress bar is near finished, place your fingers on volume up and home to enter directly into official TWRP 3.0.0-2.
If you used the "Nand Erase All" feature earlier, you will need to go into Wipe -> [Format Data] -> type "yes" for your data partition to be usable again.
Hopefully this will get you past your black screen issues.
PS. Remember to flash stock boot.img with your system.img.ext4, as you cannot boot a ROM without a matching boot image.

Please HELP Note 9 Bricked "could not do normal boot. Invalid Kernel Length!"

Please HELP Note 9 Bricked "could not do normal boot. Invalid Kernel Length!"
Hi Everyone,
So it seems like I might have flashed a wrong device twrp in AP tab in odin to my N960f/ds. Now I can not boot device, twrp(recovery) or even download mode :'( . my phone only shows a red error message saying "Could Not Do Normal Boot, Invalid KERNEL LENGTH!" . phone is not read on pc for odin adb or smart switch . I was reading something about using an sd card with preloaded firmware if anyone knows anything about that?? not sure what to do please help !! Thanks in advance

Similar issue after being repeatedly told I need to flash TWRP 3.3.1. I've had no problems with OrangeFox or TWRP 3.4 but when I flashed TWRP 3.3.1 I've ended up with the red message "Could not do normal boot. Invalid KERNEL LENGTH" on startup for around 2 seconds then it powers off. Booting into recovery obviously doesn't work, download mode doesn't work either, all I get is the red message. I thought I was as good as bricked.
It turns out when you run Odin on a PC connected via USB cable it still manages to go into download mode when you hold Vol Down + Bixby. From there you can flash a new recovery using Odin. For Note 9 look here: https://twrp.me/samsung/samsunggalaxynote9.html
You want the download as an .img.tar - see here https://eu.dl.twrp.me/crownlte/
Open Odin (run as Administrator), pick the twrp-{version}-crownlte..img.tar file in the AP slot and click Start. From there I was able to get up and running again, hopefully it works for you too.

FerretallicA said:
Similar issue after being repeatedly told I need to flash TWRP 3.3.1. I've had no problems with OrangeFox or TWRP 3.4 but when I flashed TWRP 3.3.1 I've ended up with the red message "Could not do normal boot. Invalid KERNEL LENGTH" on startup for around 2 seconds then it powers off. Booting into recovery obviously doesn't work, download mode doesn't work either, all I get is the red message. I thought I was as good as bricked.
It turns out when you run Odin on a PC connected via USB cable it still manages to go into download mode when you hold Vol Down + Bixby. From there you can flash a new recovery using Odin. For Note 9 look here: https://twrp.me/samsung/samsunggalaxynote9.html
You want the download as an .img.tar - see here https://eu.dl.twrp.me/crownlte/
Open Odin (run as Administrator), pick the twrp-{version}-crownlte..img.tar file in the AP slot and click Start. From there I was able to get up and running again, hopefully it works for you too.
Click to expand...
Click to collapse
Thank you very much. You just saved my phone. I had the same issue and thought i just hardbricked it