Related
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
rushmix said:
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
Click to expand...
Click to collapse
which rom did u come from?
Froyo. I followed the guide to a 't' and got this black screen. I have no idea what I did wrong.
Well, I need to run off to work now, but I'd really appreciate any responses.
It seems like my phone isn't being detected by odin or windows when it is in download mode, though windows does recognize that a Samsung USB device is being connected. This is recognized in the windows tray (under the name "Samsung_Android"), and in Heimdall's Zadig driver tool ("Samsung_Android").
Hmm first tthings first, your reinstall package error seems pretty simple, yu dont have the right update.zip and recovery combination... if u wanna solve that problem, find the recovery 3e to 2e tool (google it) and run it (follow directions).. then you can run reinstall packages (might havr tto do it twice). If that doesnt cut it, find the CWM update.zip and put iit into the root of your internal sd card (the 12gb one), then run reinstall packages again. You may have to reinstall packages more than once.
Your odin problem might be caused by a lack of drivers on your comp... go on the android dev section and look for a thread talking aboout ms64 and 86 drivers samsung something...
If you can get into download mode, you can unbrick your phone so dont panic
Now odin is a very dangerous tool imo so if you really are sorry about askint, do us a favir and read the sticky oon how to odin before you use it so you dont have to come back and ask us about how to Really unbrick your phone
Also, your brick is referred to as a soft brick and the android recovery program is referred to as recovery mode.
And if you really **** up, we now have the unbrickable mod in the vibrant android dev section which will unbrick your phone no matter wat (it takes somr hardware modifying though)
Sent from a cell tower to the XDA server to you.
And if i were you, id redownload the cm7 package again to make sure that it wasnt a bad download and id read some general vibrant info before diving into cm7... if youre running stock recov and have never odined before etc, youre prob not the best candidate for flashing.. just my opinion
Sent from a cell tower to the XDA server to you.
Thank you very much for your reply. I couldn't find a related tool with the Google search string "3e to 2e recovery tool vibrant," but I did find a modified 3e tool at dkszone(*)net/bypass-e-signature-verification-fail-issue-on-samsung-vibrant-android-2.2 . However, this gets stuck at "checking for temporary root."
As for installing drivers, I have installed the Samsung galaxy 64 bit drivers several times now, but I'll give the 32 bit drivers a whirl as well.
I am unable to access the SD card, and don't have a mini SD card reader, so that compounds the problem (damn my lack of cash!).
*Edit* Upon my attempted installation of the 32 bit drivers I get the following (word for word) "Swallowtail has being used. You need to eject device and reboot your computer. Rerun (Japanese or Chinese characters) after reboot your computer." Google returns zero results when I search for this error. I tried rebooting my computer and running it again, but got the same error (even with the phone unplugged from the computer).
*Double Edit* I've been trying to use the AIO Vibrant Toolbox to restore my phone to factory defaults, but I've been having no luck, as it claims my phone is not in USB debugging mode (and obviously I can't change this, as I have no access to the Android OS).
Try this, mate and hopefully you will be up and running soon...
http://forum.xda-developers.com/showthread.php?t=1278683
When I run this the program handshakes, downloads the pit file, then restarts and "...Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.."
It reboots to the black screen of death and stays there. Perhaps I could select "Flash Bootloader," but the warning of possible permanent damage scares me.
According to the thread...
"REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware."
So I guess one of the roots of my problem is that my partition tables do not match the firmware. I have no idea what to do about that.
In this case try another computer if you can, install the right drivers and see odin recognizes your phone. I'm sure it will, for some people sometimes it takes fair few tries for no reason.
Another suggestion, take out sim card and external sd while connecting in download mode. Sometimes that helps.
---------- Post added 29th September 2011 at 12:01 AM ---------- Previous post was 28th September 2011 at 11:43 PM ----------
Here is a recent thread where someone had issue with odin connection.
http://forum.xda-developers.com/showthread.php?t=1225197#16797271
Well, I ran Heim one click on another computer and had the same boot-to-blackscreen process happen.
I was, however, successful at getting Odin to recognize the phone with AIO vibrant toolbox. Odin kept getting stuck at "set pit file" though.
Baby steps...
This is so frustrating. I feel like I'm so close.
How do I get the right PIT file on my phone if ODIN is getting stuck at that step?
Now, after installing the drivers provided with Heimdall-one-click's Zadig, ODIN doesn't recognize the phone.
One step forward, two steps back.
*Edit* Nevermind, got ODIN to recognize it again by uninstalling/reinstalling all related drivers.
Then odin to stock with tthe stock jfd files.. follow the manual, report results
Sent from a cell tower to the XDA server to you.
http://forum.xda-developers.com/showthread.php?t=734475
Use those files and the procedure for ODIN.
As for what caused your problem. You flashed a clockwork recovery for a different phone, possibly the Vibrant (non-MTD) mode? Usually installing Clockwork on the Vibrant only works from ROM Manager app when its running stock JFD. At least for me anyway. Any other ROM it ****s it somehow and I end up in a situation like yours. Not to worry though. Here's a quick install guide after you ODIN the phone to stock.
Put latest nightly of CM7 on the phone memory (not external microSD)
Install clockwork (Easiest way to do this is put the update.zip file I've attached onto the root of your phone memory, not the external microsd card, then reboot into recovery (hold both volume buttons and turn it on) and select Reinstall packages twice. It will then boot you into Clockwork).
Wipe data and cache in clockwork
Install zip from SD card--> pick the latest CM7 nightly.
DONE.
I'd like to use those files, but every single link is broken...
*Edit* Never mind. Found another source. I'll post upon success/failure.
*Edit again* Actually, it doesn't seem like the new link on mediafire has all the files required by the process (OP: http://forum.xda-developers.com/showthread.php?t=734475), and I can't post in that thread (because I'm a new user).
This is the post that uploaded the files: http://forum.xda-developers.com/showpost.php?p=17512889&postcount=615
So I haven't changed a damn thing yet, and all that happens when I try to put the phone in download mode is | Phone----Warning (!) Sign----Computer | screen comes up.
Even when I only plug it into a power outlet...
Flashing the IPhone was easier and more stable than this, years ago. I honestly expected better from Google.
*Edit*
OH MY GOD. Odin is going somewhere! Go, AIO Vibrant Toolbox, Go!
*Edit again*
And it stopped at about 90% with "<ID:0/003> dbdata.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
"
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
rushmix said:
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
Click to expand...
Click to collapse
959v is the not the vibrant, tis the galaxy s4g, if you odined vibrant files on your 4g then that's why you are in a bootloop
Dear god do I feel stupid. I googled it a while ago just to be sure, and it seemed to say that the V stood for "Vibrant." I guess that would be why I've been having this sneaking suspicion...
Well it's good news for you, mate. Head over to galaxy s 4g
forums and hopefully you will be able to get your phone back.
ok well here it is ive been the very proud owner of my galaxy note since launch date well ive been too chicken to root but after recieving my stock ics update yesterday i decided to look into rooting it so i came on here seen a couple threads and seen they were saying that the old root method with gingerbread would work with the ics so i attempted it downloaded odin v1.85 ran the tar file it looked liked it worked odin said pass well it rebooted and now it is stuck on the second samsung logo with the blue glowing behind it well i searched many threads and cant find a answer on rootgalaxynote.com another guy had the same problem and i seen they told him to factory data reset so i di but with no luck it is still lokking at me stuck on the samsung logo man and i dont have insurance effin atnt screwed me on that one so wat are my options here or do i have none im prayiung this is not a hardbrick please help
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
You MUST have Kies full installed on the desktop/laptop and make sure you're updated to the latest version.
1) Boot your note into download mode(hold down volume button at the same time as the power button, let go of power button when you feel
your phone vibrate but keep holding down button until you see a prompt to push up volume button to continue or down volume button to
cancel, hit the up button your are now in download mode.)
2) Connect your Note to the laptop with factory USB cable
2) Launch Kies on your desktop (full version)
4) Choose Tools, Firmware upgrade & initialization
a) While in download mode, pull battery and enter the S/N & model name (ALL CAPS!!)
b) It will prompt to initialize to original settings. Click "YES"
c) It will prompt to initialize the latest version. Click "YES"
d) It will download the firmware upgrade components (DO NOT DISCONNECT THE DEVICE!!)
5) It will prompt for firmware upgrade and initialization.
a) Click check box for reading above information
b) Click your choice if you want your information saved on Samsung Kies corporate servers (I choose WITHOUT saving).
Just kick back, wait and the phone will update to the original out of box software with the latest updates already applied. No issue with anything, no tripping of the flash counter, and Samsung/AT&T knows now different (if you tripped the counter back before performing this, or performed the process of installing CWM recovery through ADB as to NOT trip the flash counter when changing recovery).
This is the EXACT process I did, and had an AT&T tech verify and it's not detectable I was rooted, and was running a custom ICS ROM. Now, I will qualify that I DID the Recovery installation with ADB so that I didn't trip the counter with the Recovery installation. So if they are able to check the binary information to detect modification even with flash counter reset, that's out of my hands and can't confirm or deny.
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
isimme said:
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...
You MUST have Kies full installed on the desktop/laptop and make sure you're updated to the latest version.
1) Boot your note into download mode(hold down volume button at the same time as the power button, let go of power button when you feel
your phone vibrate but keep holding down button until you see a prompt to push up volume button to continue or down volume button to
cancel, hit the up button your are now in download mode.)
2) Connect your Note to the laptop with factory USB cable
2) Launch Kies on your desktop (full version)
4) Choose Tools, Firmware upgrade & initialization
a) While in download mode, pull battery and enter the S/N & model name (ALL CAPS!!)
b) It will prompt to initialize to original settings. Click "YES"
c) It will prompt to initialize the latest version. Click "YES"
d) It will download the firmware upgrade components (DO NOT DISCONNECT THE DEVICE!!)
5) It will prompt for firmware upgrade and initialization.
a) Click check box for reading above information
b) Click your choice if you want your information saved on Samsung Kies corporate servers (I choose WITHOUT saving).
Just kick back, wait and the phone will update to the original out of box software with the latest updates already applied. No issue with anything, no tripping of the flash counter, and Samsung/AT&T knows now different (if you tripped the counter back before performing this, or performed the process of installing CWM recovery through ADB as to NOT trip the flash counter when changing recovery).
This is the EXACT process I did, and had an AT&T tech verify and it's not detectable I was rooted, and was running a custom ICS ROM. Now, I will qualify that I DID the Recovery installation with ADB so that I didn't trip the counter with the Recovery installation. So if they are able to check the binary information to detect modification even with flash counter reset, that's out of my hands and can't confirm or deny.
THIS WILL FIX YOUR ISSUE AS I WENT THROUGH THE SAME PROBLEM YOU ARE EXPERIENCING.
WARNING IT WILL DELETE YOUR DATA. IF YOUR DATA IS IMPORTANT FIND ANOTHER MEANS...[/QUOT
well thanku friend im doing it now and every time i get to 69 percent it says ther was a problem with the download file and starts over again this happened wen i originaly did the ics update but after it restarted it wold go to 100 but this time it has already been 3 times it stoped at 69 percent trying again wellit got past the 69 percent and got to 85 percent and said unzip error and closed the whole operation i had to enter in the s/n n model again and start over hopefully it works im trying again
Click to expand...
Click to collapse
getting stuck
every time i get to 69 percent it says error in donload file wt hell
you r amazing
yes it worked after 15 trys but it did work you r the man i c its getting past the sam logo
You cannot root an ice rom with a gb kernel. You need to find a rooted ics kernel and flash it with Odin. Keep in mind it needs to be an Odin flashable .tar. if you need help finding one pm me and I will direct you to one.
Sent from my SAMSUNG-SGH-I717 using xda premium
Rooting is very easy and quite low risk as long as your getting your information from reliable sources. The xda community is very knowledgeable and generous. MOST of the information you find here can be taken to heart.
Sent from my SAMSUNG-SGH-I717 using xda premium
aevans88 said:
You cannot root an ice rom with a gb kernel. You need to find a rooted ics kernel and flash it with Odin. Keep in mind it needs to be an Odin flashable .tar. if you need help finding one pm me and I will direct you to one.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yerp LOL, he knows now...we been pm...a learning experience for him....
We were all noobs at one time. Hell I still find things that I wonder about. I used to be really scared of bricking my phone because I soft bricked my international sgs2 the first time and thought I was screwed. Now I know that its pretty hard to hard brick a galaxy series phone
Sent from my SAMSUNG-SGH-I717 using xda premium
My phone was working fine on Thursday morning. Around noon I went to check my phone and it was off. I turned it on and it gets stuck at the initial Samsung boot screen. With the research and testing I have done so far the current state of the phone is...
- Any attempt at normal boot results in getting stuck at the initial Samsung boot screen.
- I am NOT able to enter recovery mode by any method I've tried so far.
- I AM able to enter download mode by holding volume down or both volume buttons while inserting the USB cable.
- The phone DOES charge via USB.
- Connecting to the computer gives a "USB Device Not Recognized" error.
- I have tried cleaning the USB port with alcohol pads as best I can and it had no effect.
- ADB does NOT see the devices (and I know ADB/Drivers/USB Debugging/etc is configured correctly because I develop with this device)
- The phone is NOT rooted nor have I changed ANYTHING within the past few weeks.
- The device IS carrier unlocked (not that this should matter at all).
- The phone does have Google Voice with Groove IP Lite installed (and I remember news that the GV API would change around this time, maybe it broke something?)
- ODIN 3 v1.85 can SOMETIMES see the phone at 0:[COM3] (I'm still trying to figure this out. I THINK it only works if I put battery in, boot to download mode by inserting USB, then after it boots to download I remove and re-insert USB to re-connect the device on the computer, but I'm not certain yet)
I was going to replace the device next month anyways so I don't really care about the device itself. What I am trying to figure out is whether there is any way to recover certain data such as memo notes or game/app data from the device? If I tried to install a new rom via ODIN will that wipe out my app data and notes and stuff or would the data persist like it would for a carrier-pushed update? Can I somehow pull this data off the device from within download mode before I try to flash the device? Am I going in the wrong direction and should be trying something entirely different to begin with? What do you guys suggest? Thanks.
I was waiting to see if anyone else would pitch in with useful information about recovering your data. However, since no one has, I can say that I am pretty sure that you will not be able to recover anything currently in any of the system partitions. (System, kernel, data, preload, etc.) Once you recover your phone, you will still almost certainly have the information that was on your internal sdcard (USB Memory.)
Using Odin3, you should open Odin on the desktop of your pc first, then use the method that works for you to get into download mode, and Odin should recognize your phone.
I understand that you are not too concerned about the device. I would point out that a working I777 that is in good working condition with a clean esn is worth probably $100.00 to $125.00 on Swappa. It would be in your best interest to recover the phone. (Or if that's too much trouble, you can always send it to me, lol.)
Since the phone can enter download mode and be recognized by the computer, it is almost certainly recoverable. The only possible reason that it would not be recoverable is if the problem is due to damaged emmc memory in some part of the system partitions. When you flash the stock firmware, or any firmware, you will lose any possible access to the data partition. You will most likely be required to enter recovery after the flash to perform a wipe data/factory reset before the phone will boot into the system. The data will not persist as it would for an over the air or kies update. But again, as I said in the other thread, you may retain the game data if it is saved to the sdcard. Memo notes are definitely stored in the data partition, so those are lost.
The only thing you can do within download mode is flash firmware, nothing else is possible. I don't know of any other direction you could be going than what we have discussed so far.
As I said before, someone with good developer skills and understanding may be able to help, but as far as I know, no one with that level of skill hangs out in this forum, or has any interest in the I777 any more.
creepyncrawly said:
I was waiting to see if anyone else would pitch in with useful information about recovering your data. However, since no one has, I can say that I am pretty sure that you will not be able to recover anything currently in any of the system partitions. (System, kernel, data, preload, etc.) Once you recover your phone, you will still almost certainly have the information that was on your internal sdcard (USB Memory.)
Using Odin3, you should open Odin on the desktop of your pc first, then use the method that works for you to get into download mode, and Odin should recognize your phone.
I understand that you are not too concerned about the device. I would point out that a working I777 that is in good working condition with a clean esn is worth probably $100.00 to $125.00 on Swappa. It would be in your best interest to recover the phone. (Or if that's too much trouble, you can always send it to me, lol.)
Since the phone can enter download mode and be recognized by the computer, it is almost certainly recoverable. The only possible reason that it would not be recoverable is if the problem is due to damaged emmc memory in some part of the system partitions. When you flash the stock firmware, or any firmware, you will lose any possible access to the data partition. You will most likely be required to enter recovery after the flash to perform a wipe data/factory reset before the phone will boot into the system. The data will not persist as it would for an over the air or kies update. But again, as I said in the other thread, you may retain the game data if it is saved to the sdcard. Memo notes are definitely stored in the data partition, so those are lost.
The only thing you can do within download mode is flash firmware, nothing else is possible. I don't know of any other direction you could be going than what we have discussed so far.
As I said before, someone with good developer skills and understanding may be able to help, but as far as I know, no one with that level of skill hangs out in this forum, or has any interest in the I777 any more.
Click to expand...
Click to collapse
Yeah. It was worth a shot but I think I am out of luck on this.
I tried using Odin 3 v1.85 and also Odin 3 v3.09 from 2 separate computers with several cables in order to flash the PDA/AP from 'I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5' but without any luck. After 10-20 minutes Odin says 'fail' and there is never any change on the phone screen at any point in the process. I also tried the 'I777UCKH7 OCD No BL.exe' one-click link from your signature links with a similar result. The program starts with factoryfs.img but the progress bar never moves and after 10-20 minutes it fails. The phone never shows any change at any point in the entire process.
I might be doing something wrong (perhaps with Odin I MUST flash the bootloader/phone/csc as well?) but it's looking more and more like the phone has a memory issue or something like that. Do you have any other suggestions? I'm willing to try anything at this point just to get the phone running for a few weeks while I decide on the next phone (hmmmm, Nexus 5, OnePlusOne, G3 or...)
Regardless of all that, thanks for all your help so far!
Both of those packages are complete in themselves. On the UCMD8 you only need the one tar in the PDA slot.
To discover if there is nand read/write corruption try this:
Instructions to clear nand read/write corruption. Instructions are specific. Do in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
For the record, no one writes those kinds of instructions as well as you do - both you and 4-2ndtwin have been great examples of how to help people for many years.
Thank you both for showing the rest of us how to convey help in an eloquent manner.
I tried your instructions with both v1.85 and v3.09 and although there was a brief glimmer of hope it looks like my device really is locked up beyond any further use. Odin shows the 'KERNEL' flash and the progress bar fills up in a second or two but then it goes to '<ID:0/003> NAND Write Start!!
' and like every other attempt it either hangs here indefinitely or fails after 10-20 minutes.
The only other things I can think of is to do a repartitioning or to physically disassembly the phone to look for any trouble spots (maybe a little dust or corrosion is shorting something) but of course being realistic there is virtually no chance of these having an effect.
I don't frequent the boards enough to know the standards here but I can say thank you for all the help you have provided. It's more than anyone can ask for such an old (but still good!) device.
Maybe it will take a jtag repair to get it going again, or perhaps there is actual eMMC damage, which can also be repaired. Whatever the problem is, a good option at this point would be the folks at Mobile Tech Videos repair shop. They have an excellent reputation here in the forum, and can do all sorts of repair.
I've searched for hours for different solutions and have tried them all. I'm on my last leg, and I can't wrap my head around what is going on.
I'm running an S2 with ShoStock3 rom. It's been rooted for over a year now without any major hiccups at all. Last night, it froze on me. Usually when it does this, I just force-restart by holding the power button down until it cycles. Phone usually boots right back up, and I'm all set. This time it just stayed on the boot screen. For eternity. I let it sit like that for more than 45 min, and it never budged. Turn it off from the booth screen, it'll boot right back up. I can go into download mode, but not recovery, and every little trick I've tried works.
I've tried flashing new kernels with ODIN. Tried various recoveries, like Philz and even went as far as the one touch factory ROM and using the regular method for getting the stock ROM. Nothing. Maybe I'm doing something wrong. Most people who have this problem only recently added a new ROM or modified something. I haven't touched the ROM, kernel, etc. for over a year before this happened.
ODIN never makes it far when trying to flash anything. It depends on what is being flashed. It never gets past nand read/write. It never gets past boot.bin. It never gets past factory.img. Etc. Etc. I don't know if maybe something isn't going through between computer and phone, and that's why I'm not having success or what in the world is going on. Every tutorial or help I found confidently stated that all you have to do is flash this kernel, go to recovery, clear cache, and you're all set. But I feel like I'm the odd man out.
I'm afraid that this won't see much attentions, as the S2 is far from new, but like I said I am on my last leg. I just don't understand how it stops working from cycling power. I also don't understand how every attempt doesn't even scratch the surface. Any and all help will be greatly appreciated
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
SteveMurphy said:
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
Click to expand...
Click to collapse
^^ while the device is NOT USB connected to a computer.
Actually, you're lucky. This device is so popular, even though is it getting old, that there are still a handful of knowledgeable people hanging around.
You need to get into recovery. As Steve and Cyril have said, try the correct button combination, and post back here to verify that you are using the correct combo and that it will not go into recovery.
If you do get into recovery, perform a wipe data/factory reset and see if that gets your phone to boot into the system.
If you are unable to get into the recovery with the correct combo, then you may have one of several possible issues. The first possibility to troubleshoot is nand read/write corruption. Do the following:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
creepyncrawly said:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
Click to expand...
Click to collapse
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
XxArxAngelxX said:
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
Click to expand...
Click to collapse
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
creepyncrawly said:
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
Click to expand...
Click to collapse
Tried using different computer. Brand new cord. Multiple times tried. Different ports. I dunno, it's doing the same thing. It stops whenever it gets to NAND Write Start.
EDIT: Tried something I saw in another thread. Used stock binary with pit file. Never finished, so aborted it. Now phone doesn't come on at all for any reason whatsoever. -.- Pretty sure I fried it
Is my Samsung Galaxy Note 2 Bricked ?
I got the phone from Ebay on July 6,2015 everything was great
But on the morning of Sep 21st looking at my gallery pictures, I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right the phone restated saying "Samsung's firmware upgrade encountered an issue" so the next day did some research first before trying anything. I downloaded Odin3 and entered download mode & flashed the Samsung it restarted had it on for 3-4 hours
then turned it off & turned it on later to find it would not go pass the Samsung logo so I went to hold the off button shutting the phone off that happen 2 times and on the 3rd try turning it on It did not come on at all. Went to see if google had anything on this some say it is bricked and need to use a jig so I got one from a USA seller on ebay and returned it because it did not work at all. Not the phone still won't come on & I can't enter download mode, how do I fix this, is it a boot loader problem? is it hard bricked? do I need to take it to someone if so who & how much would that cost? you think.
Other Info of the phone
70% of battery is on the phone
It's factory Unlocked
Root Software I tried to use was (Kingo SuperUser)[Root]
I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right "UNQUOTE"...........What was the reasoning behind the rooting your phone for lost pictures??? if had wanted to get into the stock 3E recovery of your phone, all you had to do was, rocker up on Volume,pwr on, and menu key......dr phone may have flashed the wrong Bootloader, which makes you extremely lucky it even turned on to Odin it.....the problem your facing with it not turning on at all could be either [1] you have the wrong primary boot loader on it, which means its hard bricked, but im thinking you have a bad battery, because you were able to restart it after you flashed what exactly with Odin??......what did you flash with Odin??...an entire ROM, a bootloader file, or a kernel file by wrong chance, whatever it was we need to know... your not giving out enough info here, to determine if it was the correct SW for the phone you have, also what did you tick or not tick with Odin??.... extremely weak or going bad battery's cause abnormal voltages and abnormal symptoms as well...you might have a battery that finally went completely bad!!....there's usually only 3 things that cause a phone to not power on!...1] flashing wrong firmware, corrupting the primary bootloader...2]bad internal/failed hardware...3] a bad battery either its causing abnormal voltages or producing nothing from being totally dead!!...you state you cant power on anything, nothing visually illuminates, plus your saying it wont go into DL mode....volume rocker down, menu button and the pwr button all together will get you into DL mode, if you can power on a DL mode to the phone it is NOT HARDBRICKED!!...that means a softbrick situation= SW corruption....we need further more detailed info here!!...BTW YOU POSTED THIS QUESTION IN THE WRONG FORUM, THIS IS DISCUSSION FORUM , OTHER FORUM IS FOR TROUBLESHOOTING, WHICH IS WHAT YOUR TRYING TO DO HERE!!!
dseldown said:
I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right "UNQUOTE"...........What was the reasoning behind the rooting your phone for lost pictures??? if had wanted to get into the stock 3E recovery of your phone, all you had to do was, rocker up on Volume,pwr on, and menu key......dr phone may have flashed the wrong Bootloader, which makes you extremely lucky it even turned on to Odin it.....the problem your facing with it not turning on at all could be either [1] you have the wrong primary boot loader on it, which means its hard bricked, but im thinking you have a bad battery, because you were able to restart it after you flashed what exactly with Odin??......what did you flash with Odin??...an entire ROM, a bootloader file, or a kernel file by wrong chance, whatever it was we need to know... your not giving out enough info here, to determine if it was the correct SW for the phone you have, also what did you tick or not tick with Odin??.... extremely weak or going bad battery's cause abnormal voltages and abnormal symptoms as well...you might have a battery that finally went completely bad!!....there's usually only 3 things that cause a phone to not power on!...1] flashing wrong firmware, corrupting the primary bootloader...2]bad internal/failed hardware...3] a bad battery either its causing abnormal voltages or producing nothing from being totally dead!!...you state you cant power on anything, nothing visually illuminates, plus your saying it wont go into DL mode....volume rocker down, menu button and the pwr button all together will get you into DL mode, if you can power on a DL mode to the phone it is NOT HARDBRICKED!!...that means a softbrick situation= SW corruption....we need further more detailed info here!!...BTW YOU POSTED THIS QUESTION IN THE WRONG FORUM, THIS IS DISCUSSION FORUM , OTHER FORUM IS FOR TROUBLESHOOTING, WHICH IS WHAT YOUR TRYING TO DO HERE!!!
Click to expand...
Click to collapse
Should I post this in the Troubleshooting Forum?
The pictures I took on the phone disappeared all 300+ pictures disappeared .I am the only one using the Samsung
and it was on my table all that day. So I went to google to find a photo recovery software & found a software called
Wondershare Dr.Fone for Android (you can find videos on youtube) & using the software it can do 2 things, auto root the phone to find the photos and bring it back to normal or you Have to have your phone rooted. The auto root setting was not working on the Wondershare Dr.Fone for Android software so I went to the google play store on my Samsung and found a root app that a lot seem to like as it was 4.4 stars, went to install that the app stated I should have "Kingo SuperUser" on my computer so had that put on the went to root the phone & it did not work.
I got a screen on the Samsung saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Youtube had a video on this same problem so I went to Sammobile's site and download the firmware what was
"2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies. After I downloaded that I downloaded Odin3_v3.10.6 opened it had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion then Entered Download mode on the Samsung & hooked it up to my computer
then I hit start about 30min later it Passed with a green light and everything seem back to normal 3 hours later I went to turn the Samsung off and latter that night when I went to turn it on it got stuck at the Samsung logo that happen 2 times and on the third time it did not come on & so can't "enter download mode" and the "usb Jig" did not
work. What happen & what do I need to next. Do I take the phone to someone to fix this.
Short version of the story
.Pictures I took 300+ disappeared so when looking for recovery software
.Found a software called "Wondershare Dr.Fone for Android" (the software had "2" Options for recovering. 1 the software would
Auto Root and bring the Samsung back to normal after recovering the pictures or I would have to had the phone already rooted.
. When to the google play store with the Samsung, found a root app download that & "It stated I should download "Kingo SuperUser" to my computer so I did that.
.It failed & got a screen on the Samsung Saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
.Went to Sammobile's site and download Firmware 2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies
.Download Odin3_v3.10.6 had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion
Entered download mode & the Samsung passed
.Everything was back I had it on for 3-4 hours then shutdown the phone later that night went to turn on and it got stuck
at the Samsung logo 2 times and on the 3rd time it would not turn on nor enter "Download Mode"
.Got a "usb Jig" & that did not work and now I am here wondering what do next & what happen to my Samsung Galaxy Note 2 do I need to take to someone to fix it ?
Samsung Galaxy Not 2 Unlocked
SCH-I605V version (Verizon)
my battery was %70 full
You may have a possible hardware problem then= a bad motherboard and possible replacement!!!....Can you power it on in anyway shape or form??...meaning can you toggle it into recovery??...can you toggle it into DL mode??....does it pwr on to the bootloader screen and continuously loop???.....if you can do any of those things then its not hardbricked, which means you need to reconstuct the SW and then see if the Hardware holds stable....If it doesn't....then it could be a severe HW problem!!!....For the future be advised that, you completely took the wrong road to achieving blindly what you intended to do!!...meaning ....you should've completely took control of the situation and been totally proactive in your rooting and unlocking the bootloader...you wrongly turned to 3rd party APP's when you should've read first...educated yourself completely on what you were to embark on, and then set everything up with 3 different choices of rooting/unlocking..again depending on what ROM version your operating on, before engaging!!.....NEVER TRUST 3rd party APP's to do something only you should have step by step control of = lazy!!!.....I personally wouldve 1st tried to get to the stock 3e recovery, and attempt a nandroid backup of the phone as it was...then afterwards try to get the phone detected on my computer, so as to access the file containing the photos, transferred them to the computer safely... then flash the phone to a stock ROM with root already baked in or not = equals totaly factory stock.. doesnt really matter!!!.... and then set up the phone again, and see what it WILL!!! or WONT!!! do!!...point is, easter-egging a problem carelessly, will cause you to either install the wrong stuff or go completely outta proper sequence and either hose the SW, or worst case scenario....corrupt the primary Bootloader and hardbrick it!!....if you can power it into DL mode!!!.... Then, 1st BEFORE YOU DO ANYTHING!!.... go get Odin 3.07....then get the Samsung drivers for your computer to detect the phone...then DL the Pit file "sch-1605-16gb.pit"....then the proper stock ROM..4.1.1...4.1.2 in .TAR files only, BTW there is a stock 4.1.2 with rooted already in it!!....and then flash your phone using Odin with the pit file and then tick the PDA .tar file of whatever ROM. you choose.....I suggest 4.1.2 as a base to start with and reconstruct it, re-root it if necessary, that's if you choose the one W/O rooted baked into the ROM and unlock it with advice above using ghetto root, do not use adams outlers unlocker, there seems to be problems with it, triggering KNOX, and YOU DO NOT WANT THAT TO HAPPEN!!....relying on 3rd party app's will FK you up....use your head...not your heart!!...and yes you really should post NEXT time in the trouble-shooting forum, but for now leave it here!!...for your benefit!!
dseldown said:
You may have a possible hardware problem then= a bad motherboard and possible replacement!!!....Can you power it on in anyway shape or form??...meaning can you toggle it into recovery??...can you toggle it into DL mode??....does it pwr on to the bootloader screen and continuously loop???.....if you can do any of those things then its not hardbricked, which means you need to reconstuct the SW and then see if the Hardware holds stable....If it doesn't....then it could be a severe HW problem!!!....For the future be advised that, you completely took the wrong road to achieving blindly what you intended to do!!...meaning ....you should've completely took control of the situation and been totally proactive in your rooting and unlocking the bootloader...you wrongly turned to 3rd party APP's when you should've read first...educated yourself completely on what you were to embark on, and then set everything up with 3 different choices of rooting/unlocking..again depending on what ROM version your operating on, before engaging!!.....NEVER TRUST 3rd party APP's to do something only you should have step by step control of = lazy!!!.....I personally wouldve 1st tried to get to the stock 3e recovery, and attempt a nandroid backup of the phone as it was...then afterwards try to get the phone detected on my computer, so as to access the file containing the photos, transferred them to the computer safely... then flash the phone to a stock ROM with root already baked in or not = equals totaly factory stock.. doesnt really matter!!!.... and then set up the phone again, and see what it WILL!!! or WONT!!! do!!...point is, easter-egging a problem carelessly, will cause you to either install the wrong stuff or go completely outta proper sequence and either hose the SW, or worst case scenario....corrupt the primary Bootloader and hardbrick it!!....if you can power it into DL mode!!!.... Then, 1st BEFORE YOU DO ANYTHING!!.... go get Odin 3.07....then get the Samsung drivers for your computer to detect the phone...then DL the Pit file "sch-1605-16gb.pit"....then the proper stock ROM..4.1.1...4.1.2 in .TAR files only, BTW there is a stock 4.1.2 with rooted already in it!!....and then flash your phone using Odin with the pit file and then tick the PDA .tar file of whatever ROM. you choose.....I suggest 4.1.2 as a base to start with and reconstruct it, re-root it if necessary, that's if you choose the one W/O rooted baked into the ROM and unlock it with advice above using ghetto root, do not use adams outlers unlocker, there seems to be problems with it, triggering KNOX, and YOU DO NOT WANT THAT TO HAPPEN!!....relying on 3rd party app's will FK you up....use your head...not your heart!!...and yes you really should post NEXT time in the trouble-shooting forum, but for now leave it here!!...for your benefit!!
Click to expand...
Click to collapse
I guess it's the hardware? as It won't come on nor enter Download mode.
Now what, Do I take it somewhere? to fix it what ever it is ?
http://mobiletechvideos.com/
bigmike35 said:
Are you saying I can take it to them to fix it ?
Click to expand...
Click to collapse
SamsungNoteFan said:
bigmike35 said:
Are you saying I can take it to them to fix it ?
Click to expand...
Click to collapse
You cant take it but you can mail it. They unbricked my phone awhile back when something happened. It was good service. I rec'
Click to expand...
Click to collapse