Develop Bugs

Stuck at Boot Screen

Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance

Luke44 said:
Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance
Click to expand...
Click to collapse
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot

shhbz said:
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot
Click to expand...
Click to collapse
I flashed philz recovery. After pressing the power button just the battery symbol appeared... no reboot. So I treid to boot into the new recovery... but still the old recovery boots
Heres the log from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.11.2-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!

http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....

Luke44 said:
http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....
Click to expand...
Click to collapse
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you

shhbz said:
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you
Click to expand...
Click to collapse
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1

Luke44 said:
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1
Click to expand...
Click to collapse
do u have kies installed when u trying odin if yes then delete it just install the samsung drivers nothing else and disable your antivirus too.
orelse u may try
thats quite strange ok now its time to try the mskip tool just delete all old samsung drivers and kies
and start fresh from here http://forum.xda-developers.com/showthread.php?t=1923956
and as far as the count in concerned its 1 as you were only able to enter recovery once thats why after that u were not able to so as many times u enter custom recovery the count increases

http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...

Luke44 said:
http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...
Click to expand...
Click to collapse
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe

shhbz said:
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe
Click to expand...
Click to collapse
Sorry but I cant find such a viedo...

Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
I tried to flsh this, but odin says:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

What exact information you can see on Download Mode Rt Upper corner.
post full details here

dr.ketan said:
What exact information you can see on Download Mode Rt Upper corner.
post full details here
Click to expand...
Click to collapse
In the right upper corner is nothing...
In the left upper corner:
ODIN MODE (written in red)
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom

Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG

Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
There is I am on phn so would be difficult for me to find but its simple u just select the pit file first in odin and flash keeping ur phn in download mode and then the firmware tar file

Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried a different computer with different cable. On the computer I used this time there is not even kies installed.
Same result as before...

dr.ketan said:
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried it a few more times..it really doesnt work
Whats wrong with this !"§$%& phone:crying::crying::crying:

Bricked?

I have a problem with my Tab3. When i am in download mode all i get is this. See picture.
I had a problem that the tab always reboots into recovery. So i want to flash a stock firmware. Any ideas?

same issue.
Erik1805 said:
I have a problem with my Tab3. When i am in download mode all i get is this. See picture.
I had a problem that the tab always reboots into recovery. So i want to flash a stock firmware. Any ideas?
Click to expand...
Click to collapse
i have come to a similar dead end.
came from fastdreamV6 rom and odin'd in T210RUEU0COB1_T210RXAC0COB1_HOME .tar .md5
pardon my terminology but i guess you'd say i dirty Odin'd it?> did not wipe or revert.
its where things went wroung for me
soo any ways.. looking for helpful and knowledageble people to begin trouble shooting this issue
after the install it rebooted and showed the tab3 splash screen then android package installer full screen before an OS. when the page installer screen disappeared that was the end of any responsiveness from the device.
mine always boots to black screen. no recovery , no audible/visual anything until odin mode.
always a black screen until i walk through the odin/download mode key' sequence blind
i have only half of what should look like a odin/download mode screen, the android guy has disappeared.
WIN7 does find the tab3 thats in [email protected]$$ odin mode in the device manager
odin also sees the tab3 but odin doesnt want to work to upload anything < hangs at setupconnection.. or pit mapping failed even when i have the new pit file being pushed,
ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
hemidall gives me communication conflicts
adb .. i currently have no os on the tablet as far as i can tell. maybe somebody can tell me if i can fastboot a command to push a recovery into it. but without adb-communication. i dont see it happening?
i presume i have a corrupted .pit file thats its not allowing me to replace.
OR KITKAT needs its own .pit file and i will need help aquiring one.
or its just a really bad flash alltogether. being boot.img. system img. recover img
how should i proceed if there is a way ? looking to get back to stock 4.4.2.
i can solder and make a usb jig if nessasary.
1 week later; further developments and workaround to boot here:
http://forum.xda-developers.com/gal...ably-hard-bricked-t3057440/page2#post60682636

SGH-M919: Complete(Write) operation failed when flashing stock 4.2.2 rom by Odin3

I have a Samsung SGH-M919 T-Mobile S4 phone which ran stock 4.2.2 firmware. It was brick when I tried to root it. It is able to go to download mode.
I downloaded M919 4files repair firmware (Odin3 v3.09.3, AP_M919UVUFNB4 stock rom , JFLTE_USA_TMO.pit..) from TSAR3000.com. I uninstalled Samsung Kies. It passed when run Odin3 with JFLTE_USA_TMO.pit. But it failed with message showed: Complete(Write) operation failed when I flashed downloaded stock 4.2.2 rom.
Do you have any experience to resolve this issue?
Do I use any wrong version of Odin3, M919 stock rom or .pit file?
Do you have exact worked SGH-M919 stock 4.2.2 firmware, Odin3 and .pit file so that I can fix my phone?
Thank you very much!
The Odin3 message:
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Try the stock firmware from sammobile.com. The pit file may not be required unless Odin cannot read the partition table from the phone.

I'd recommend flashing the lastest stock firmware:
http://forum.xda-developers.com/showthread.php?p=64431358
Odin v3.09 has never given me problems. Follow the directions in the first post of the thread.

Can Not Enter Recovery Mode By Three Keys
Thank you very much for helping. I used another computer to run Odin3 and flashed full version 4.4.4 stock firmware successfully. Now the Samsung S4 is able to run 4.4.4 stock rom without any problem after root and TWRP 2.8.7.0 installed. I am able to reboot it to recovery mode from TWRP Manager which was downloaded from Play Store. But it NOT able to going to recovery mode by press Vol up+Home+Power buttons, even stock recovery installed before TWRP installed. It still is able to going to download mode by press Vol down+Home+Power buttons. How to fix "Can Not Enter Recovery Mode By Three Keys" issue?
Thank you very much!

Possibly Bricked I9192! Can it be fixed?

Last status
Code:
Device: S4 Mini I9192
ROM: CM13 by k2wl
KERNEL: REMIX
RECOVERY: TWRP 3
So, let me tell you a sad story!
Yesterday I was talking a nap while my phone was charging. There was load-shedding, but my phone charged on IPS. But later I saw that it was showing the boot-up animation. I let it happen, but when I returned the phone was showing the "Samsung Galaxy S4 mini GT-I9192" splash screen and it was stuck there. I removed the battery, and reinserted and it was the same. I tried to boot up to my recovery, but after the splash screen, it was stuck on TWRP splash screen.
After a few try, I thought maybe I should wait for TWRP, maybe its doing something in background. Guess what, TWRP booted. When I checked log it was full of "unable to mount" error with various partitions. I was happy for a moment. So after that I tried to reboot to system. Now, there wasn't even any splash screen either. Tried to boot into recovery but even recovery isn’t booting. So I entered the download mode.
Code:
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
Then I tried to flash the TWRP with Odin 3 v3.09 but it was stuck on:
Code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
When I unplugged the phone while stuck, two more lines appeared:
Code:
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
At this point I lost any hope of recovering data and so I’m ready to flash a PIT file too. So I did some research and found the PIT file and tried flashing it. Odin was stuck at “Initialzation” again. After a few Google search, somebody suggested to use an old Odin, so I downloaded Odin3 v1.85 and retried. No luck but the Odin log was different
Code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
Now I’m totally hopeless as I think the built-in storage is somehow corrupted so that even Odin can’t write it.
Few interesting things:
ADB cannot properly run while the phone is plugged in. ADB shows "server out-of-date" error. Then kills and return nothing. If repeated, same thing. Although all Odin recognizes the phone.
I tried a method of debricking with an img file on a sd card, but it fails on "parted" for some reason.
Kies keeps on showing "Connecting".
If nothing can be done, I'll just have to take my home to the repair shops. But will they be able to fix it? Any thing I'm missing?

I guess you already tried that, but if not - try reinstalling usb drivers. Skipsoft android toolkit might be helpful too. Check it out, it helped me out once in a similar situation.

komor555 said:
I guess you already tried that, but if not - try reinstalling usb drivers. Skipsoft android toolkit might be helpful too. Check it out, it helped me out once in a similar situation.
Click to expand...
Click to collapse
What exactly should I do using the Android Toolkit?

Run the software, let it download all the stuff. Next in the main menu, there are a few input options. First of all, try "I" with your phone connected and in download mode, to see what kind of device info the phone will return. If nothing shows up, try "DR", which will install drivers to work with adb, fastboot and recovery, on your local machine. You should do that even if you get the device info in the first place, just to try getting it again after driver installation for comparison.
Next, input 24 to run galaxy s4 mini module. Let the utility download and install all the module updates. After that, select DUAL SIM GSM MODEL [GT-I9192] by writing "02". It will ask for the android build, select the newest one (option 22). If you have a custom build, then you will have to unlock the Pro version by donating, but there might be no need for that, if option 22 works. Again, let it download.
Then you get access to a variety of options. First, unplug your phone, and run option 1 to install device drivers to your PC. Then, if you are lucky and ADB works, you can Install a .zip file using sideload (option 16) to your phone. Or you can just play around with other options. Maybe something will work. If the download mode works on the phone - that's usually a soft-brick, which is fixable.

Odin FAIL to flash stock ROM on my 7100 (sboot.bin -> NAND Write Start!! -> FAIL!)

Odin FAIL to flash stock ROM on my 7100 (sboot.bin -> NAND Write Start!! -> FAIL!)
Hi all,
I have read all pages of this forum about my problem:
My Galaxy Note II (GT-N7100) show only logo at start and if I press Volume UP + Home + Power it show a lot of red and yellow text (MANUAL MODE E: can't open cache ecc ecc). All option of this menu (factory reset/wide ecc) do not resolve logo freeze so I try to flash stock ROM via ODIN:
I use original cable, I change all my USB port (2.0 - 3.0), I try a lot of ROM (last ROM I try is the same that my phone show at second line in hard reset "kot49h.n7100xxsfqa8"), my note 2 is correctly set on Download mode (Volume down + Home + Power) and ODIN correctly see my phone on COM: (random port).
What I can do?
Thx to all

You confirmed that the model # is gt-n7100 in download mode?
Tried different USB cables and USB 2.0 ports?

Yes I confirm

The sboot.bin fileis the bootloader of the phone. This file can fail to flash is you are using an incompatible phone, USB cable, USB port, or the phone is running a bootloader that is newer than the bootloader you are trying to flash.
Did you try flashing the phone with a pit file and the original Samsung cable?

audit13 said:
The sboot.bin fileis the bootloader of the phone. This file can fail to flash is you are using an incompatible phone, USB cable, USB port, or the phone is running a bootloader that is newer than the bootloader you are trying to flash.
Did you try flashing the phone with a pit file and the original Samsung cable?
Click to expand...
Click to collapse
I try a lot of original samsung USB cable, USB port (2port 3.0 and 1port 2.0)... I try also more than 3-4 odin version and 4-5 stock rom (2 older and last 2 of 2017, the last one have the same name appared on second line of hard reset boot)
I have not try with pit file because I do not understand what I have to choose
best

You need to match the pit file to the amount of internal memory and model #.
This may help if you have a 16 GB phone: https://forum.xda-developers.com/showthread.php?t=2653311 or https://forum.xda-developers.com/showthread.php?t=2769487

audit13 said:
You need to match the pit file to the amount of internal memory and model #.
This may help if you have a 16 GB phone: https://forum.xda-developers.com/showthread.php?t=2653311 or https://forum.xda-developers.com/showthread.php?t=2769487
Click to expand...
Click to collapse
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.

Either something is wrong with the internal memory or the combination of cables and ports are not compatible.
Did you try using Odin 3.07 on Windows 7?

audit13 said:
Either something is wrong with the internal memory or the combination of cables and ports are not compatible.
Did you try using Odin 3.07 on Windows 7?
Click to expand...
Click to collapse
I use windows 10 and now with ODIN 3.07 it freeze at:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..

I have always had good luck with Odin 3.07, Win7, and the original Samsung USB cable for flashing stock ROMs from sammobile.com.
I sometimes have errors when I don't use the original cable when flashing the bootloader or obtaining partition information from the phone.
As an experiment, you could try flashing TWRP to phone and see if you can get into TWRP after flashing.

audit13 said:
I have always had good luck with Odin 3.07, Win7, and the original Samsung USB cable for flashing stock ROMs from sammobile.com.
I sometimes have errors when I don't use the original cable when flashing the bootloader or obtaining partition information from the phone.
As an experiment, you could try flashing TWRP to phone and see if you can get into TWRP after flashing.
Click to expand...
Click to collapse
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!

So Odin fails writing TWRP?

my galaxy s6 touch and network signal is not working after tying to root with odin.
please i need help