Related
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.
Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps
muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App
will do thanks guys, ill try it tonight and let ya know how it goes for me.
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much
muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.
I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...
Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!
Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App
Woops ahahahha. Was talkin to my friend. SOrry!
fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/
Okay so yesterday I decided that I wanted to restore the factory EP4 ODIN package from imnuts' website so that I can factory upgrade to FP1 and re-root.
So I downloaded the factory image and the PIT file and started the flash process with ODIN - yes, all checkboxes were selected appropriately. Well about 10 seconds into the flash, a little red message popped up on the top left corner of my phone while in DL mode that says "RX_TIMEOUT". However, the flash continued on to eventually (after about an hour) succeed.
When I went to boot up my phone, I got a Samsung logo for about an hour. Pulled the battery, tried again, same thing. Tried the flash again, same thing. Tried a few more times (each time taking 30-50 minutes, sometimes an hour) and same thing. Downloaded EE4 and tried that - same thing.
Here are the things I've tried:
- flash with battery in AND out
- flash with PIT file and without
- downloaded the EP4 image again, in case of bad download
- downloaded EE4 and tried to flash it (same result)
- let the phone charge for a bit
- tried ALL USB ports
A few flashes ago, I ended up in factory recovery (thought that was a good sign) but when I clicked reboot, I got the Sammy logo again.
EDIT: Well, after the last failed flash, I lost download mode it's toast. Any advice?
What version of Odin are you using?
Does the charging icon come up if you plug it into the wall? Maybe the cable is bad.
I've noticed that either my cable, or the mini usb port on the phone are going bad. If I move the cable/phone even slightly, it loses USB connection with the comp. Now I make sure there is a good connection, and I don't move the phone/cable AT ALL when I am flashing via ODIN.
edit: this is actually being discussed in another thread RIGHT NOW: http://forum.xda-developers.com/showpost.php?p=24412728&postcount=290
I would guess cable, though I would have tried a new cable before going through so many bad flashes.
Thanks for the replies - yes, I know it's being discussed in that thread, I started the discussion. I just figured it would be easier to post a new thread than to extend that one.
Anyway, Imnuts, I actually did try a different USB cable and the funny thing is that the ODIN flash was WAY faster, but failed (actually reported as failed). With the first cable, it was taking a really long time but it the flash passed.
But it doesn't matter anyway because I figured since I managed to (somehow) get into the stock recovery (even though I was unable to do anything), the phone must have been wiped and restored to factory, although bricked. So, I called up Big Red and they sent me a new one under factory warranty
New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.
n1ghtwish said:
New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.
Click to expand...
Click to collapse
After USB1 pass, phone off, three button press didn't work? (Vol. up, home, power) try quick boot app from market see if that'll get you in recovery.
Sent from my SCH-I510 using xda premium
n1ghtwish said:
New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.
Click to expand...
Click to collapse
I suggest try someone else computer. Obviously, there is data drops and caused between the driver and your O/S or hardware.
After a few more tries and almost throwing the laptop and the phone out the window, it passed and I now have recovery and stock rooted FP1.
Good lord.
For future reference, I would avoid using Odin with the phone connected to a USB hub. It only adds a failure point in the connection. Given that you already have one bad USB port the way it sounds, odds are the other one is partially bad as well, given your issues with Odin.
imnuts said:
For future reference, I would avoid using Odin with the phone connected to a USB hub. It only adds a failure point in the connection. Given that you already have one bad USB port the way it sounds, odds are the other one is partially bad as well, given your issues with Odin.
Click to expand...
Click to collapse
Well, that's why I tried without the hub. Oh well, it's done.
I'm not much of a computer person really, I only use this thing for breaking my phone
n1ghtwish said:
Well, that's why I tried without the hub. Oh well, it's done.
Click to expand...
Click to collapse
That's what imnuts was saying, though. Using a hub adds a failure point, which is a bad thing, but you also said one of the USB ports on the laptop had already gone bad. Two side-by-side ports are typically linked, whether out at the ports or back at the controller. If one went bad, the other is also likely to not function properly. The main point is that in the future I would avoid flashing using that laptop all together.
Hi. I have a Galaxy Note 10.1 tablet. I went to turn it on this morning and it for stuck in a boot loop. all it says it "Samsung Galaxy Note 10.1" and then shuts off. I try and into recovery and the TWRP title screen shows up and then immediately turns off. What should I do?
Try flashing stock rom through odin
Sent from my GT-I9100 using xda app-developers app
raducux said:
Try flashing stock rom through odin
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Is the Stock Rom the same thing as a Stock Recovery? If not, where would I find a Stock Rom and how do I install it?
kyleschepis said:
Is the Stock Rom the same thing as a Stock Recovery? If not, where would I find a Stock Rom and how do I install it?
Click to expand...
Click to collapse
Answer no but it includes stock everything .
Stock roms on the forum or sammobile.com samsung-updates .com .
Would flashing the stock ROM erase everything from the tablet? Is there a way to retrieve the files from it in download mode?
Bootloop - No Recovery Mode
kyleschepis said:
Would flashing the stock ROM erase everything from the tablet? Is there a way to retrieve the files from it in download mode?
Click to expand...
Click to collapse
Hi all,
I have a similar issue to kyleschepis.
I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started a week ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But last week, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I AM able to get into the Odin download mode but CANNOT get into recovery mode no matter what I do.
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00 _user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. The installation in Odin seems to run fine - I get the "PASS" message at the end of the prodedure. But the power + volume up combination does NOT get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for a full week now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Boot loop (soft brick)
robb-x said:
Hi all,
I have a similar issue to kyleschepis.
I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started a week ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But last week, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I AM able to get into the Odin download mode but CANNOT get into recovery mode no matter what I do.
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00 _user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. The installation in Odin seems to run fine - I get the "PASS" message at the end of the prodedure. But the power + volume up combination does NOT get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for a full week now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Click to expand...
Click to collapse
I am having near the same experience as rob-x. I have had problems with some files on my SD card missing or arbitrarily renamed. I had the tab on charge and the next day it was looping through the boot screen,
I have tried flashing the firmware with Odin and also CWM, without results. I am unable to boot into recovery, only into download.
Also the only way to turn the machine off is to plug it in to charger then hold the on/off until the screen goes black.
My next plan is to flash the PIT and the firmware at the same time,
tcm13 said:
I am having near the same experience as rob-x. I have had problems with some files on my SD card missing or arbitrarily renamed. I had the tab on charge and the next day it was looping through the boot screen,
I have tried flashing the firmware with Odin and also CWM, without results. I am unable to boot into recovery, only into download.
Also the only way to turn the machine off is to plug it in to charger then hold the on/off until the screen goes black.
My next plan is to flash the PIT and the firmware at the same time,
Click to expand...
Click to collapse
Hi tcm13,
Three weeks later and I am still none the wiser with my Note. It is still caught in the bootloop.
I can tell you that I have tried flashing the PIT and the stock firmware, but in my case it did not help. You are welcome to try. It didn't get any worse, but it did not get any better either. I have also tried flashing the stock German and UK ROMs for the GT-N8010 (mine is the US GT-N8013) with or without the PIT. These both fail fairly early on in the flashing process. But the behavior of the device does not change. Still the same bootloop, stuck at the same place.
Sorry for the bad news. Like I said, in my case flashing the PIT didn't help, but I have read on forums that people did have success with it. So it is definitely worth trying. It doesn't make things any worse, any way.
Let me know how it goes for you.
Ditto, same issue. I can flash a .tar file (I have tried CF-Auto and TRWP) in download mode using Odin but can't get the device into recovery mode.
It is just boot looping to the Samsung GALAXY Note 10.1 screen every 15-20 seconds. Can't even turn the damn thing off to save battery!!
Topazzar said:
Ditto, same issue. I can flash a .tar file (I have tried CF-Auto and TRWP) in download mode using Odin but can't get the device into recovery mode.
It is just boot looping to the Samsung GALAXY Note 10.1 screen every 15-20 seconds. Can't even turn the damn thing off to save battery!!
Click to expand...
Click to collapse
Hi,
I have been able to turn the device off by plugging it in to charge then hold the on/off down until the screen goes dark.
---------- Post added at 08:59 PM ---------- Previous post was at 08:40 PM ----------
robb-x said:
Hi tcm13,
Three weeks later and I am still none the wiser with my Note. It is still caught in the bootloop.
I can tell you that I have tried flashing the PIT and the stock firmware, but in my case it did not help. You are welcome to try. It didn't get any worse, but it did not get any better either. I have also tried flashing the stock German and UK ROMs for the GT-N8010 (mine is the US GT-N8013) with or without the PIT. These both fail fairly early on in the flashing process. But the behavior of the device does not change. Still the same bootloop, stuck at the same place.
Sorry for the bad news. Like I said, in my case flashing the PIT didn't help, but I have read on forums that people did have success with it. So it is definitely worth trying. It doesn't make things any worse, any way.
Let me know how it goes for you.
Click to expand...
Click to collapse
Hi,
I have tried all and every PIT, ROM custom or not, and various recoveries without success.
I presume, as opposed to assume that it is a hardware fault.
Faulty SD card reading, random freezing, crashes and long charging cycles lead me to surmise some basic fault is the cause, also seeing that my device is not the only one to have been stricken.
I have now surrendered my system to the "tender mercies" of the appointed Samsung technicians as my device is still under warranty.
I dislike admitting defeat but I have gone as far as I can without picking up a screwdriver.
Let hear if you have found another alternative.
Hi,
Could you let us know how it went after the service? I had similar problems with my Note 10.1 (n8013) but it seems to have gone away by itself. Had to let the battery die a couple of times a couple of times though, but now I'm running IOKP without a hitch. . Would really like to know what the Samsung service people diagnosed...
Bump
mowgli_writes said:
Hi,
Could you let us know how it went after the service? I had similar problems with my Note 10.1 (n8013) but it seems to have gone away by itself. Had to let the battery die a couple of times a couple of times though, but now I'm running IOKP without a hitch. . Would really like to know what the Samsung service people diagnosed...
Click to expand...
Click to collapse
BUMP : Same behavior here. I was able to upload an older stock ROM via odin but upon rebooting, the behavior persists and I still cannot boot into recovery mode. It would help tremendously if Samsung would pull their heads out of the asses and provide links to firmware but I cannot find an official source for any US version of the Note 10.1 (gt-n8013eavxar).
Side note to the origin of the problem. The tablet I am attempting to recover had never been rooted so I'm ruling out operator error as to how the device became so jammed up.
robb-x said:
Hi all,
I have a similar issue to kyleschepis.
I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started a week ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But last week, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I AM able to get into the Odin download mode but CANNOT get into recovery mode no matter what I do.
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00 _user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. The installation in Odin seems to run fine - I get the "PASS" message at the end of the prodedure. But the power + volume up combination does NOT get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for a full week now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Click to expand...
Click to collapse
bro have you found the solution ?
Boot into recovery
I had a similar issue but then realised that the instructions I had been following were slightly inaccurate i.e. hold down power and volume up...... what worked for me was hold down power and volume up, when logo comes up, release power but hold on to the volume.
lets know if you already tried that.
harrisyn said:
I had a similar issue but then realised that the instructions I had been following were slightly inaccurate i.e. hold down power and volume up...... what worked for me was hold down power and volume up, when logo comes up, release power but hold on to the volume.
lets know if you already tried that.
Click to expand...
Click to collapse
Thanks a lot for stupid it seams I did that and oala CWM XD.
Im resurrecting my tab from a hard brick so entering recovery is a greate deal for me a few ours ago i could only enter in download mode no at least i have a boot loop and recovery.
It´s factory reset and cache whipe time to get rid of the boot loop
rodrigofantino said:
Thanks a lot for stupid it seams I did that and oala CWM XD.
Im resurrecting my tab from a hard brick so entering recovery is a greate deal for me a few ours ago i could only enter in download mode no at least i have a boot loop and recovery.
It´s factory reset and cache whipe time to get rid of the boot loop
Click to expand...
Click to collapse
great ☺
Envoyé de mon GT-N8010 en utilisant Tapatalk
harrisyn said:
I had a similar issue but then realised that the instructions I had been following were slightly inaccurate i.e. hold down power and volume up...... what worked for me was hold down power and volume up, when logo comes up, release power but hold on to the volume.
lets know if you already tried that.
Click to expand...
Click to collapse
i tried your way its shows green android logo with blue lines in centre and then next screen it shows is android lying down with its stomach open and red exclamation.
what does that mean >?
Hi.
I'm having a similar issue wih my n8010
Im am unable to boot the tablet, its stuck on the samsung logo, and here it stays untill it runs out of battery.
I cannot enter recovery mode, it will not get past the samsung logo. (I have tried holding down the vollme up key and releasing the power key when the logo apears) Nothing works.
I am able to get into Download mode, and the tablet is also reconized by Odin, But when i try to flash a stock firmware downloaded from Sammobile, It right away sais Fail!
This is the output from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the tablet i get: SW REV. Invalid magic string
I have tried to flash a new recovery using Heimdall and that i can do with no errors, but i canot enter recovery mode.
Am i tryind to flash the wrong firmware fra Sammobile?
Hope that someone can help me to solve this.
NOTE: Before this went wrong i had CM 10.2 Nightly on the tablet, but could not play any videos, so i want to go back to stock. So i connected the tablet to odin and tried to flash the firmware from Sammobile, but it failed, and now, this is where im at.
EDIT: I got the problem solved.. I tried various stock roms from Sammobile, different countries and regions, ended up with a stockrom pointing at Netherlands even tho i live in Denmark, but that one flashed with no errors, and i was able to get past the "Samsung Galaxy 10.1 ) logo, but got stuck at the "Samsung" logo. But i was now able to enter revovery mode (Power + Vol Up) and do a full wipe and the reboot. Now everything works.
A littel bonus question i would like someone to help me understand. When i want to download a Stock Rom from Sammobile, what should i choose? I live in Denmark, but there is no option for that when i am to selct a download from Sammobile.
Another question, can i Select a 4.1.2 firmware and flash that on my Tablet, now that i have the 4.4.2 installed? I hate the new KitKat placement of buttons on the tablet.. Back button in the middle where you cant reach it with your thumb and the drop down menus are a pain.. i hate it.
Will i for example be able to flash this rom : http://forum.xda-developers.com/showthread.php?t=2119547
Or are there some problems with me having 4.4.2 now, and want to go back to 4.1.2?
Please advise.
Thank you in advance.
I am glad it helped several members but unfortunately not me and probably also others with the same issue as ROBX described.
I think it has something to do with hardware, original cable etc. tomorrow I have it flashed at the Samsung shop and see if it works there.
harrisyn said:
I had a similar issue but then realised that the instructions I had been following were slightly inaccurate i.e. hold down power and volume up...... what worked for me was hold down power and volume up, when logo comes up, release power but hold on to the volume.
lets know if you already tried that.
Click to expand...
Click to collapse
Jrod236 said:
EDIT: I got the problem solved.. I tried various stock roms from Sammobile, different countries and regions, ended up with a stockrom pointing at Netherlands even tho i live in Denmark, but that one flashed with no errors, and i was able to get past the "Samsung Galaxy 10.1 ) logo, but got stuck at the "Samsung" logo. But i was now able to enter revovery mode (Power + Vol Up) and do a full wipe and the reboot. Now everything works.
Click to expand...
Click to collapse
Any one tray this and solve the problem?
Sent from my SM-T805 using XDA Premium HD app
Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated
Hi, I too have similar issue. Would like to know how you got it resolved.
tanzeeb210 said:
Hi, I too have similar issue. Would like to know how you got it resolved.
Click to expand...
Click to collapse
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue
oscar_ferreiro said:
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue
Click to expand...
Click to collapse
its seems like battery issue more for me than the board!
you should replace or disconect her first before selling the device... could worth the try...
oscar_ferreiro said:
Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated
Click to expand...
Click to collapse
Same issue here, any idea to solve that? (I'm Brazilian, sorry for some typing wrong)
I don't opened the device (yet), but if is a battery issue, someone tried to fix?
My device is SM-G920I, i tried to flash this FW: G920IDVU3FQD1_G920IXSA3FQC3_XSA without sucess, i will try with a "pit" file that i've found here on XDA and update here, but until the moment, the problem remains
Update: The PIT file does not solved the problem, after this I decided to open the device and swap the battery, but the problem remained, i'm buying a new board today, i think this board can't be saved
I've had similar problem with my Note4. It would sucessfuly apply firmware via Odin but refuse to boot. (tried multiple times)
I then did a flash via SmartSwitch (takes forever) but the phone worked again.
any update for this ? i have the same issue
Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Could someone please help!
bestfootie said:
Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Click to expand...
Click to collapse
Had to come back and add on to my previous post - I sorted it. It was simply a driver issue... Make sure you download all the correct Samsung USB Drivers people if you're having similar issues...
I finally restored my Android to Stock Android (albeit the latest Android system 7.1).
[SOLVED, ANSWER BELOW]
Hi
Yesterday I tried to install TWRP Custom Recovery on my phone. I have done it before succesfully on different models.
The installation went smoothly, and I managed to boot into TWRP quickly. However the touch screen went all funky. Every little button I had to press was a difficult process, and I could barely swipe the unlock mechanism. Using the keyboard to type 'yes' for certain functions was impossible. I tried everything from aluminium foil to special gloves..
I looked up methods how to fix this and this site came up multiple times. Some solutions offered however were too complicated for me to use, because I have no knowledge on the core electronics of my device.
I decided to just leave it at this and turn off my phone. I tried going to the menu to power my phone off, however it decided pressing a lot of buttons was a better idea. I have no idea what buttons were pressed during that moment of craziness, and now I can only get my phone into the download mode. If I try to acces TWRP, it boots up to the first screen, then immediately turns off, and does it again. I can shut that process off, by pressing the power button + volume down, and then using volume up+down+power button to go into download mode.
I have the version of Odin that matches my android 9.0 Pie version, not the latest, as the latest version of Odin did not even install TWRP the first time I tried this, but the matching yet older version did.
I tried reinstalling TWRP. No luck.
I tried flashing stock firmware. I get a Complete(write) Operation failure.
I have up-to-date USB drivers
I tried Samsung Smart Switch but it does not recognize my device. I tried reinstalling my USB drivers to no avail. I used different USB ports, and a different USB cable.
I have tried to look up any and everything that may relate to this issue but I have not succeeded in finding anything that fixes my issue.
When I started the process, OEM unlock and USB Debugging was turned on. It may or may not have turned off in that crazy moment, I can't tell
All of my data is backed up or not valuable to me. A factory reset, or wipe, or whatever, is something I'm okay with. I just want my phone back.
Thank you for your help
Greetings, Jaxus
[SOLUTION]:
I decided to go ahead and use the latest Odin anyway. It worked. My touchscreen issue has been fixed, and I can go back to rooting as I expected I should be able to. I apologize if I broke any social convention in my post.
SM-A530W
I just recently ran into same'ish TWRP issues and locked up totally upon a reboot with a SM-A530W. Here's why,apparently. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 I got the "Only official released binaries are allowed to be flashed" message. Most certainly worth a read. Wow, 7 full days (168h) going unmolested, who would of guessed such.
Does Rooting work for Android 9?
I don't know what to do!!!
uwannabananababy said:
I just recently ran into same'ish TWRP issues and locked up totally upon a reboot with a SM-A530W. Here's why,apparently. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 I got the "Only official released binaries are allowed to be flashed" message. Most certainly worth a read. Wow, 7 full days (168h) going unmolested, who would of guessed such.
Click to expand...
Click to collapse
I have the same phone and I've got a similar problem I've used every odor known to man the newest one to the oldest one I can no longer load TWRP I can't root it I can't do anything please tell me what I can do thank you in advance