Hi, so I've been flashing for a while now on my phone and my friend wanted to root his phone so i agreed to help him out. After flashing multiple files in order to get cwm recovery and just get everything working, the phone started to act up.
Here are the problems:
Phone can boot into stock recovery but i cant flash anything from it
i wiped data/factory reset many times.
i tried to install the cwm kernal by applying update from sd card (I followed the install custom recovery instructions from here: http://wiki.cyanogenmod.org/w/Install_CM_for_i777) but when into recovery to flash, 2 red signs come up saying "E: Failed to verify whole-file signature" and "E: signature verificatoin failed" after this is just aborts the process
i tried download mode, but none of my computers recocgnize the phone (2 computers) i have tried all usb ports, reinstalling usb drivers, different usb ports many times but all have failed
if i try to boot, the phone just stays stuck on the Samsung galaxy s2 logo (no triangle? even though its rooted)
my only option is to hang out in recovery, i have a bunch of files saved to an external sd card but i cannot access that from stock recovery
any help would be appreciated, Thanks
You can not install any unsigned files with stock 3e recovery, as you have discovered. That is normal behavior.
I don't know why performing a wipe data/factory reset from 3e recovery does not clear the phone to boot normally. It should. But since it won't...
You will need to get the phone recognized by a computer, and then flash with Odin, or you could try flashing with Heimdall command line. I would suggest that you flash the full stock plus root I777UCKH7 (2.3.4), and then when it boots normally into the system, install Mobile Odin Lite or Mobile Odin Pro, and use that to flash a custom kernel. You can find the stock firmware in the Download Repository, and the basic directions in my guide, both of which are linked in my signature.
creepyncrawly said:
You can not install any unsigned files with stock 3e recovery, as you have discovered. That is normal behavior.
I don't know why performing a wipe data/factory reset from 3e recovery does not clear the phone to boot normally. It should. But since it won't...
You will need to get the phone recognized by a computer, and then flash with Odin, or you could try flashing with Heimdall command line. I would suggest that you flash the full stock plus root I777UCKH7 (2.3.4), and then when it boots normally into the system, install Mobile Odin Lite or Mobile Odin Pro, and use that to flash a custom kernel. You can find the stock firmware in the Download Repository, and the basic directions in my guide, both of which are linked in my signature.
Click to expand...
Click to collapse
The hardest part about this is getting my computers to recognize the phone
i guess i shouldve mentioned this earlier, i attempted to flash in Odin but it was stuck on zImage so i unplugged it
before i flashed in odin, i used to be able to boot into the phone like touchwiz and whatnot, now it just gets stuck on the samsung galaxy s ii boot logo
This is now [Solved}! thanks for the help creepyncrawly! i figured it out after doing some more reasearch online. apparently, youre not supposed to use the charger wire that came with the device since samsung doesnt want to waste their time on creating a good enough cable for this kind of stuff. so i grabbed some random cable that i found in my house, hooked it up and BAM! both of my computers were able to detect my phone just finished flashing bone stock on the phone thanks
I noticed in your post that you tried everything but another cable. But I'm glad you got it working. I had the same problem before too. Cables are finicky little things.
Sent from my SGH-I777 using xda app-developers app
Related
Hi I hope someone can help me. I have searched this forum but could not find a similar situation to what I ended up in...
I tried to install a custom ROM on my Galaxy Tab 10.1 using the CWM/Odin.
This seemed succesful but was not, it did not start but was stuck in the Samsung logo.
So I tried entering the CWM and download and install an original Samsung ROM. I can get it into CWM, but CWM cannot enter the download mode only the other mode.
In this mode all options are available:
- reboot
- apply update from SD card
- wipe data/factory reset
- wipe cache partition
All options have been tried without any luck. In the update from SD card it only shows ...
or Error opening /data/media: no such file or directory
Any ideas how I could get this directory back or put a ROM on the Samsung in this situation.
Odin does see the Galaxy but as I cannot get it into Download mode I am unable to download anything to it.
All or any suggestions are very welcome!
1. CWM (Clockworkmod) =! Odin.
In the beginning, you don't have CWM installed. You install CWM, by flashing CWM on your Phone with odin.
Odin is the Windows Programm, that is used to flash Recoveries/ROM's/Kernels onto your device.
2. it seems, that you still have the default Samsung recovery installed, that meand CWM is not yet flashed on your device.
If the flashing process was succesful (I suppose it was done with odin), but you can't get past the Samsung logo, that means, you probably flashed a rom, that isn't made for your device(ex. a GTab 10.1v Rom).
If you DID flash a wrong rom, then you probably ****ed up the partition table and removed the Download Mode(Odin Mode). Strange thing is, that you still have the Stock recovery.
Could you please redirect us to the rom you downloaded?
Also, did you flash with a repartition on and/or a .pit file?
hi Kaukassus,
thanks for the reply.
OK I checked the files and what I did.
I think I totaly screwed this up. It was a theme I tried to install the AOSP_HC_v1.3_3G+KI1.
I rooted the Tab. So first when the Tab was still functioning installed it on the TAB via USB.
Than tried to install this via update from SD card.
This appeared to work initially. But hung at the start.
After that I tried (via Power Volume Up) wipe data/factory reset.
No luck.
After that I tried wipe cache partition followed by wipe data/factory reset.
And this is what I got now..
Bad news is the Tab was/is a X-mas present and I managed to screw it up even before I officially got it !-(
The valuable lesson you're learning is that you need to be aware exactly what things you're flashing and their compatibility with your device and the software it's running.
You haven't mentioned what specific device you're using or the specific things you've tried to flash (as kaukassus pointed out, direct links to threads where you got the files you tried to flash are best). Not sure if you're aware but not all GT 10.1's are equal; there are several models out there and each and every ROM is specific to a particular device. Verizon LTE GT 10.1's like mine can't take ROMs from any other device for example, it's likely that the new T-Mobile 4G one's wont be able to trade ROMs with Verizon ones . . you get the point.
When you say you installed via USB what exactly did you mean? If you simply copied a zip file via USB to the tab to flash in recovery mode that's not installing; the flashing from recovery may be but the file copy operation is not. If on the other hand you pushed things via ADB or you flash using Odin software then that's a different story.
Best thing to do at this point is to properly identify your device, look for a stock recovery image for Odin and flash that via Odin to your device. At that point you can start from scratch again to build what you want.
Thanks Muzzy996.
You are right. I was in a rush and should have taken more time.
However I am getting somewhere. Managed to get in download mode twice today, don't ask me how. This Tab just will not go into download mode!
However I did not have the stock ROM ready to be installed.
Will keep you updated.
i have the same problem. i just rooted my device was going to overclock. decided to save my rom with rom manager. saved it device went to reboot now the samsung galaxy 10.1 shows up screen goes dim then shuts off, and will cont. do this. i can get into download mode but recovery will not work. is there anyway to download my stock rom. im using verizion 4g 10.1 any help would be great, btw sorry to thread jack
Problem solved.
Managed to get it in download mode again and install stock rom via Odin.
Appeared to work fine. But kep switching off, even after full night of charging.
This morning Tab was dead after recharging whole night..
Got it back on by holding volume down and power button down.
i found a stock rom and im trying to upload it via odin, however odin does not find my tab? any ideas. btw congrats on getting ur tab back
I crashed both my I9000 (galaxy s) flashing custom roms and my tab 10.1 (editing some system files) both ended up just looping but managed to get both back. I purchased a small connector of ebay £1.59 that has just a resistor accross pins 4&5 331k I think anyway plugging this into most samsung devices boots them into download mode. Even before getting my resistor I managed to get things working I think that you'd have to be properly unlucky to really brick a samsung I've flashed both my devices with all sorts of crap with my little resistor I just reset them with ease.
Brian
h2bmess said:
i found a stock rom and im trying to upload it via odin, however odin does not find my tab? any ideas. btw congrats on getting ur tab back
Click to expand...
Click to collapse
did you ever resolve this issue? i am currently faced with the same issue.
Hello.
I have a GT-i9305 andI tried the rooting by following the instructions at http://galaxys3root.com/ on my Ubuntu laptop with heimdall.
I managed to install the recovery and also flash the cwm zip. I saw som problems related to /cache/ so I wiped cache and after that I have not been able to get past boot logo. I hav ealso tried flashing a custom rom and doing a factory reset and wipe dalvik cache bu
t it did not help. I have tried Odin and flashing from a .tar.md5 file but it results in FAIL.
I can reach both download mode and recovery but that is all.
Please help, I need my phone.
did you use a i9300 method on your i9305? you've probably killed the phone.
flash a stock ROM via Odin (i9305 one) and factory reset from recovery. if that doesn't help - send it to Samsung.
And this is the i9300 section, you're in the wrong place
Thanks.
I got back to stock. I will try to use the i9305 method.
Mount /sdcard not possible
Wel, I have the same problem.
Samsung SIII International version. After installing a new rom (believe it was "jellybam-v6.1.0_i9300-STABLE.zip") but I am not sure, the phone boots only to the original logo and then the screen goes black. Nothing more.
I can get into recovery mode and download mode so I tried several recovery versions (CWM, TEAMWIN, latest ClockworModRecovery v 6.0.2.8.) and several ROM.
No mater what I install, I get the same results. Boot phone and it hangs after the standard Samsung logo.
I was able to find out "/sdcard" could not be mounted. All the recovery programs I used with the option "mount unmount" reporting the same "/sdcard could not be mount" error.
Formatting /sdcard all so won't work.
I am thinking installing a new kernel but I have some difficulties in finding witch one will work with my phone?
Any suggestions or help is really appreciated b/c I have no idea what to do next.
Samsung I9300
Win 7
Latest USB drivers from Samsung installed
No Kies installed.
Odin3_v3.07 installed.
Using Odin I flashed:
CF-Root-SGS3-v6.4.tar
recovery-cwmtouch-6.0.2.8-GTI9300.tar
recovery-stock-dlj4-GTI9300.tar
recovery-stock-blg9-GTI9300.tar
And a few more.
Due to being unable to acces the phone installing a zip file is not possible. Using "installing a rom from zip, or sdcard" from recovery is not possible.
I tried installing a file using sideload but was not succesfull. I can get the phone in receiving a file from sideload but was unable to send a file from the PC.
Thanx in advance
you have to do a factory reset after flashing a new rom
Did wipe/clear/factory set etc every time just to find the phone goes black after the Samsung logo.
One particular thing: I can see the /sdcard in some recovery programs but can't modify it.
How can I transfer a zip file using Sideload?
I can get into "download a file using Sideload" on my phone but what should I do to get a zip file transferred. Maybe then I can use "install from zip" from a recovery.
Update Problem solved (for me) http://forum.xda-developers.com/showthread.php?t=2162908
I flashed the 9305 firmware from here http://www.samfirmware.com/ in Odin then I was back to stock.
Then I rooted the phone by this instruction.
http://www.ibtimes.co.uk/articles/4...-lte-android411-android412-jellybean-root.htm
I have not tried a custom rom but I think it should work.
Hello, first post here and I am hoping you guys will be able to help me.
I have here a SII that will only access download mode. I have tried re-flashing it several times with various Odin flashable files all of which returned a "Pass" but still would not allow me to pass the first "Samsung" screen. The files I have flashed include Clockworkmod, TWRP, and the stock UMCD8 firmware with and without pit file.
Is there any other option left short of replacing the motherboard?
You should be able to boot the phone after performing a wipe data/factory reset from within recovery. To enter recovery, hold all three buttons (vol+ vol- & pwr) continuously until the boot screen appears the second time, then release all three. You can perform a wipe data/factory reset from stock 3e recovery, or from a custom recovery, depending on which you have, it doesn't matter. That being said, you success will depend perhaps on what you flashed. I am assuming by ClockworkMod and TWRP you mean I-777 kernels containing those recoveries, as the I-777 does not have a separate recovery because the recovery is built into the kernel. If the kernel version does not match the system version (UCMD8 is Jelly Bean) then the phone would not boot even after a reset. But you could flash the full I777UCMD8 again, and then it should boot. If you have additional questions or issues, let us know.
creepyncrawly said:
You should be able to boot the phone after performing a wipe data/factory reset from within recovery. To enter recovery, hold all three buttons (vol+ vol- & pwr) continuously until the boot screen appears the second time, then release all three. You can perform a wipe data/factory reset from stock 3e recovery, or from a custom recovery, depending on which you have, it doesn't matter. That being said, you success will depend perhaps on what you flashed. I am assuming by ClockworkMod and TWRP you mean I-777 kernels containing those recoveries, as the I-777 does not have a separate recovery because the recovery is built into the kernel. If the kernel version does not match the system version (UCMD8 is Jelly Bean) then the phone would not boot even after a reset. But you could flash the full I777UCMD8 again, and then it should boot. If you have additional questions or issues, let us know.
Click to expand...
Click to collapse
Retried flashing the I77UCMD8 using odin 1.83 but it still wont boot. I also realized that when I try to access recovery it doesn't actually shut down, but gives me a black screen from which it will reboot if left for approximately five minutes. Is there anyway to get access to adb, like perhaps flashing a. insecure bootloader or something?
Berthfield said:
Retried flashing the I77UCMD8 using odin 1.83 but it still wont boot. I also realized that when I try to access recovery it doesn't actually shut down, but gives me a black screen from which it will reboot if left for approximately five minutes. Is there anyway to get access to adb, like perhaps flashing a. insecure bootloader or something?
Click to expand...
Click to collapse
Since you get a pass in Odin when you flash the full UCMD8 distribution, you should be able to get into recovery. Pull the battery for at least 30 seconds, then put the battery back into the phone and hold all three buttons continuously until you see the Samsung logo appear, the screen to go black, the Samsung logo appear a second time, and the screen to go black a second time, then release all three buttons.
If this does not boot the phone into recovery mode, then please describe in detail in your next post exactly what happens when you follow this procedure.
And, if the phone will not boot into recovery, then I will need additional information in order to troubleshoot the issue further. You have not given much information about the phone. What is the history of the phone before the problem manifested? Has this been your phone since new, or did you get it from another user? What was it running before the problem. Exactly what happened when the phone stopped working. Are you an individual trying to get his personal phone going, or a business trying to fix a phone to sell? Give me as much information as you can possibly think of.
creepyncrawly said:
...
Click to expand...
Click to collapse
On a side note, very honored to have issued your 3,001 'thanks'. I swear you should have triple that amount, due to the quality and depth of help you've given to the community - and continue to do so.
creepyncrawly said:
Since you get a pass in Odin when you flash the full UCMD8 distribution, you should be able to get into recovery. Pull the battery for at least 30 seconds, then put the battery back into the phone and hold all three buttons continuously until you see the Samsung logo appear, the screen to go black, the Samsung logo appear a second time, and the screen to go black a second time, then release all three buttons.
If this does not boot the phone into recovery mode, then please describe in detail in your next post exactly what happens when you follow this procedure.
And, if the phone will not boot into recovery, then I will need additional information in order to troubleshoot the issue further. You have not given much information about the phone. What is the history of the phone before the problem manifested? Has this been your phone since new, or did you get it from another user? What was it running before the problem. Exactly what happened when the phone stopped working. Are you an individual trying to get his personal phone going, or a business trying to fix a phone to sell? Give me as much information as you can possibly think of.
Click to expand...
Click to collapse
Okay. I am a student who repairs phones part-time, I am not new to the android platform or to the galaxy line however this is the first I am experiencing this particular problem.
This phone is a unlocked and refurbished device that was purchased recently by my cousin. He claims he was just installing an app when it shut down and refused to boot back up. I initially took it with the intentions of wiping the data and returning it, however I was unable to access the recovery menu.
As I had no idea what rom was on it before, other than the fact that it was a samsung original, I proceeded to trying to flash various recoveries hoping that one would load from which I could install a custom rom. Failing that I then went on to flashing the I777UCKH7 firmware which also failed to boot and/or access recovery. Unsure what to do next I then attempted to flash the I777UCMD8 firmware which also did not boot. I then made a second attempt at flashing the I777UCKH7 firmware and .pit file from your download repository which also failed to boot.
All were loaded using Odin versions 1.82, 1.83 or 1.85 (Mostly 1.85). They all returned a "Pass" status but would be stuck on the "Samsung" screen when they rebooted. It was at this point having run out of ideas that I made the O.P.
I have also tried leaving the battery out and then following your instructions for recovery, when I do so I get a black screen. If i leave it in that screen for some time (approximately 5 mins) it will reboot and again be stuck on the "Samsung" screen.
We appreciate that you aren't new to the android platform or to the galaxy-line. Regarding the i777, you are in good company, and if we know NOTHING about any other device, we know the i777 very well. We're here to help.
You mentioned that you flashed several recoveries to the device. For future reference, the recovery for the i777 is packaged with the kernel, and is not installed separately. Even the often-troublesome temporary flash-recoveries that can be found, are actually a kernel/recovery combination. The s959g (straight talk's s2) has the same partition layout as the i9100 and i777 (and several other s2's), and DOES use a separate partition for recovery.
The fact that desktop ODIN indicates PASS when the flash is complete tells us that all of the factory nand images flashed successfully (including boot). It is very common that the device needs to have the factory data reset even after the factory images have been installed via desktop ODIN, but of course that requires access to recovery. If after a successful factory flash, the vol+ & vol- & power button held-concurrently-until-recovery (<--while NOT plugged into a USB port) truly doesn't get you to recovery, then that would be a new one for me as well; all other signs (as you have stated them) point to a correctly functioning device.
I'm hesitant to point you to flash a custom kernel;
there's some unnamed part of the procedure affecting the process, and flashing another boot image won't be helpful
-or-
there's a hardware failure, and flashing another boot image won't be helpful
-or-
you're using an incorrect method to get to recovery, and flashing another boot image won't be helpful
If you want to try it anyway, custom_kernel_twrp_v2.7.1.0.tar file via desktop odin might be worth a try.
^^this will trip the flash counter
^^this will install any custom firmware, but will not boot anything below android 4.4.x
I apologize for the hijack @creepyncrawly
Berthfield said:
Okay. I am a student who repairs phones part-time, I am not new to the android platform or to the galaxy line however this is the first I am experiencing this particular problem.
This phone is a unlocked and refurbished device that was purchased recently by my cousin. He claims he was just installing an app when it shut down and refused to boot back up. I initially took it with the intentions of wiping the data and returning it, however I was unable to access the recovery menu.
As I had no idea what rom was on it before, other than the fact that it was a samsung original, I proceeded to trying to flash various recoveries hoping that one would load from which I could install a custom rom. Failing that I then went on to flashing the I777UCKH7 firmware which also failed to boot and/or access recovery. Unsure what to do next I then attempted to flash the I777UCMD8 firmware which also did not boot. I then made a second attempt at flashing the I777UCKH7 firmware and .pit file from your download repository which also failed to boot.
All were loaded using Odin versions 1.82, 1.83 or 1.85 (Mostly 1.85). They all returned a "Pass" status but would be stuck on the "Samsung" screen when they rebooted. It was at this point having run out of ideas that I made the O.P.
I have also tried leaving the battery out and then following your instructions for recovery, when I do so I get a black screen. If i leave it in that screen for some time (approximately 5 mins) it will reboot and again be stuck on the "Samsung" screen.
Click to expand...
Click to collapse
cyril279 said:
I apologize for the hijack creepyncrawly
Click to expand...
Click to collapse
On the contrary, your input is valuable and desired.
@Berthfield,
If there was actual nand damage in any partition that was flashed, you would not get a pass in Odin, as far as I know. Since you are unable to boot into any recovery, this indicates a problem with the nand memory, possibly a corruption issue. Please try the following (you might try accessing recovery after each step, and if you get to it, perform a wipe data/factory reset):
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 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.
I was away from home for a bit and so was unable to work with the phone. I have followed the instructions given above but I am still unable to boot.
I was using the "I777UCKH7-REV02-home-low-CL503881.tar.md5" file downloaded from the download repository, is this the right file or is there another Gingerbread flash that wold be better to use?
I am really puzzled at what exactly is happening with this phone.
Yes, that is correct. That is the original stock gingerbread from when the phone was first released.
I agree that it is a puzzle. Just to be sure, you followed the directions exactly? I'm not sure why, but the sequence will clear nand read/write corruption. You might try once again with the SBL -> Siyah Kernel -> Full Gingerbread, just to make sure.
1) Flash the SBL by itself and pull the battery.
2) Flash the Siyah kernel by itself and pull the battery.
3) Flash the full Gingerbread stock and pull the battery.
4) Enter recovery and perform a wipe data/factory reset.
5) Reboot.
creepyncrawly said:
Yes, that is correct. That is the original stock gingerbread from when the phone was first released.
I agree that it is a puzzle. Just to be sure, you followed the directions exactly? I'm not sure why, but the sequence will clear nand read/write corruption. You might try once again with the SBL -> Siyah Kernel -> Full Gingerbread, just to make sure.
1) Flash the SBL by itself and pull the battery.
2) Flash the Siyah kernel by itself and pull the battery.
3) Flash the full Gingerbread stock and pull the battery.
4) Enter recovery and perform a wipe data/factory reset.
5) Reboot.
Click to expand...
Click to collapse
Did the above and it is still a no go.
I have come to realize that the phone seems to think it is in recovery mode when I attempt to enter it as if it is plugged in while on the black screen it doesn't display the charging animation. This occurs regardless of the kernel/recovery combo that is on the phone and while in that state it is also not detected by the computer. To rule out possible problems I have also attempted the flash on a different computer with a different cable and it is still the same.
I remember reading about the ICS hard-brick bug and that it was possible to brick the phone is a large enough file was written to memory. Is it possible that this could be my problem or would Odin return a error if the chip was damaged? Also I am not sure if this matters but I find it odd that after flashing the Siyah kernel and CWM the phone still hasn't tripped its custom binary counter.
Berthfield said:
Did the above and it is still a no go.
I have come to realize that the phone seems to think it is in recovery mode when I attempt to enter it as if it is plugged in while on the black screen it doesn't display the charging animation. This occurs regardless of the kernel/recovery combo that is on the phone and while in that state it is also not detected by the computer. To rule out possible problems I have also attempted the flash on a different computer with a different cable and it is still the same.
I remember reading about the ICS hard-brick bug and that it was possible to brick the phone is a large enough file was written to memory. Is it possible that this could be my problem or would Odin return a error if the chip was damaged? Also I am not sure if this matters but I find it odd that after flashing the Siyah kernel and CWM the phone still hasn't tripped its custom binary counter.
Click to expand...
Click to collapse
Evidently, this situation is beyond my experience.
My understanding is that if emmc memory is damaged within a given partition, then Odin will not be able to successfully flash that partition. While I don't know exactly how Odin functions, I believe there are checks within the flashing sequence for each partition. So as stated before, it is assumed that if you get a pass in Odin, there is not emmc damage, at least not within the various partitions that Odin flashes.
There was one case I remember with the emmc super brick bug where the phone would boot, but would not function correctly. Evidently in that case, a small portion of the emmc memory was damaged. The usual symptom of that bug was a hard brick.
The charging issue could be hardware or it could be a failing or failed battery. Have you tried another battery?
Flashing the Siyah kernel and not tripping the flash counter is more than a little odd. The code that governs that behavior is in the secondary boot loader as far as I know, and you have reflashed that. Please bear in mind that anything I say is speculation, but this issue give me a lot of reasons to think it is a failed hardware issue.
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
Just woke up to see my phone on the Samsung Galaxy i9300 logo.
(I had just flashed LineageOS the previous day)
I was able to get into recovery CWM but nothing could mount, so I tried TWRP. Same thing. Couldn't sideload too (because you couldn't sideload to anywhere duh).
Tried flashing stock rom and repartitioning. Failed. And now the phone says Firmware upgrade failed etc instead of the logo.
Can't get into recovery anymore.
Can get into odin mode, but Odin doesn't recognize the phone.
SDS?
EDIT:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
You can still flash a stock ROM when you see the "upgrade failed" screen.
Did you try using different USB cables and ports to flash the stock ROM? Tried using Odin 3.07 with and without a pit file?
If you can get to download mode try another cable and install the pc drivers while the phone is connected in download mode or install kies for your operating system, stop the processes and try again.
Make sure your stock firmware is the correct one for your device/region/variant and that the md5 hash matches.
The problem you are having is caused by a borked recovery. It is very possible that the partition is corrupt, inevitably causing the death of your phone.
Beamed in by telepathy
Odin 3.07 / 3.09 and Heimdall don't recognize the phone.
The usb cable seems fine considering I used to flash the day before and if I remove the battery the phone is still on while connected to the usb cable.
I already ordered a new phone but if I can get this one fixed that'd be great. The new phone may come with a usb cable so I will try that.
I guess I was stupid enough to flash TWRP and SuperSU on top of LineageOS.
EDIT:
Before getting to this point I was able to flash stock rom while the Firmware upgrade has failed... logo showed. However I can't flash stock rom because the phone can't mount anything, not even /system. So it fails as soon as it tries to write something.
New usb cable - couldn't flash but was detected by odin.
Deleted hidden.img from the stock rom and now it flashes!
Let's hope it works.
Update: it did not.
After flashing it booted to recovery, said something about missing sd card and a countdown to 20s. After that was over it went to the recovery menu and I got a bunch of the same errors: couldn't mount /system /cache (no such file or folder found).
I put back my sdcard but I couldn't get to recovery, also, instead of the samsung galaxy logo I got a white screen. I could still get to download mode, and get recognized by odin and heimdall, but can't flash anymore ANYTHING.
Either There's no PIT file or stuck at Get pit for mapping if I do include one.
I've tried 3 different versions of odin.
I've tried heimdall under windows and linux with root without success (Either couldn't set up interface or there's no pit file).
I'm gonna try 1.85 odin tommorow. I lost all hope at this point. ****ed up my partitions.
RIP I9300.
Idk if that may work but you may have a go to just try flashing stock rom with a box. Gsm service points shouldn't take much for it
KayleMaster said:
Update: it did not.
After flashing it booted to recovery, said something about missing sd card and a countdown to 20s. After that was over it went to the recovery menu and I got a bunch of the same errors: couldn't mount /system /cache (no such file or folder found).
I put back my sdcard but I couldn't get to recovery, also, instead of the samsung galaxy logo I got a white screen. I could still get to download mode, and get recognized by odin and heimdall, but can't flash anymore ANYTHING.
Either There's no PIT file or stuck at Get pit for mapping if I do include one.
I've tried 3 different versions of odin.
I've tried heimdall under windows and linux with root without success (Either couldn't set up interface or there's no pit file).
I'm gonna try 1.85 odin tommorow. I lost all hope at this point. ****ed up my partitions.
RIP I9300.
Click to expand...
Click to collapse
Your emmc Nand Flash chip died. I had same problem with my n7100 last month. Had to change motherboard.
I took it to a service center. The told me the screen was dead because of the white screen. It was white cus corrupted BL or something, but definitely not the screen, considering you can go into download mode and you can clearly see it's functioning.
I laughed all the way through the front door.
Correct the screen is not the issue. The nand will be borked.
Beamed in by telepathy