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
Related
[Q] GT-P7501: Stuck in "Downloading... Do not turn off target !!" [resolved]
Hi all,
I just bought a GT-P7501.
I was going to root it as described in http://forum.xda-developers.com/showthread.php?t=1239185
I ended up with a flickering CWM recover version 4. Flashed with Odin a version 5 from overcome. Same flickering...
And then something must have gone terribly wrong...
I now cannot flash anything via Odin anymore. The tab starts and sits then with a very small percentage display in "Downloading...". Odin stays at
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
Click to expand...
Click to collapse
When I boot normally I get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Kies does not allow me recovery mode though.
(I can (at least occasionally) boot into the stock by fiddling with the flickering CWM recovery.) Not anymore, I cannot get into recovery.. :-(
Any hint, how to resolve this?!?! I am desparate.
DrData
PS: Resolved with http://dl.dropbox.com/u/18512051/andrewrecov.tar.md5
PPS: flickering resp. rolling recovery fixed with http://forum.xda-developers.com/showthread.php?t=1555984
Using a TAB GT-P7500
Got the same problem, after trying to update to ics with KIES. It stopped in the beginning, and cant do anything else anymore.
Tried draining the tab, didnt work. Tried almost everything and it doesnt work so it seems. I will try to flash it with the recov tar. If you could tell me how you did it. Just flsh it in ODIN?
edit*
Tried flashing the recov.tar in ODIN, doesnt work it seems. Maybe it is time to throw my tab out of the window, its getting annoying
Okay, ive managed to flash the recovery tar, yet when i want to flash a stock rom it still freezes after a few seconds (attached screenpic). I can get into the overcome cwm recovery, and wipe everything, yet after that i can still not flash a rom, it will be stuck at hidden.img.
Anyone any idea on what to do next?
Two choices: copy a ROM to your storage, flash a custom recovery and boot into recovery and install the .zip from your SD card
Or, Odin to stock.
Beezer80 said:
Two choices: copy a ROM to your storage, flash a custom recovery and boot into recovery and install the .zip from your SD card
Or, Odin to stock.
Click to expand...
Click to collapse
Can't reach internal storage, it will only see the tablet as an apx. Odin to stock keeps on freezing. Drained my tablet now completly, will try it again once i recharged.
Odin to stock doesnt work, not with a pit file, not without, it will still freezes at hidden.img and then do nothing again.
Well, send it to samsung for repairs, they will fix it under guarentee.
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
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!!
This morning i found my phone stuck on the Samsung logo.
Entering the TWRP recovery I noticed it was not mounting anything, not even the external sd card, which seemed strange to me.
I tried to flash the last twrp via ODIN and it completed.
But it even don't boot the Samsung logo which was doing before.
In dowload mode the counter is set pratically to 0.
Trying to flash again ODIn gives the error saying that the pit partition is missing.
Only thing I could resort to is download mode.
Please help
Flash an official clockwork recoverymod recovery and see if that boots. Twrp is dodgy at best.
Beamed in by telepathy.
Hello today i made a call and bought an s6 edge in a bootloop situation.
When i first took it in my hand i tried to get into recovery mode but that wasn't possible as i took a no command screen.
Then i Tried download mode which was ok.
I downloaded the latest nougat stock rom i could find on samy and tried to flash via odin i took an error when tried to flash hidden.img
After a research on net i tried to pull off hidden.img and gave it a flash, after reboot it got me to an updating screen, then erasing then bootloop again.
Tried to flash firmware without hidden.img inside, flash was succesfull but bootloop again.
After sometime when i was letting phone hanging on screens while searching, i noticed that from no command in got into recovery but after sometime it freezes(seems the weirdest thing to me).
Now downloading repair firmware with SamFirm tool and will give it a try but i'm not sure about the .pit files
I've read here that is the best way to permanent destroy devices but i don't have much hopes for that phone tbh :/
Update.
I tried the latest repair firmware with no success.
(Getting always stuck in erasing screen)
Also can't access recovery no more,i cannot pass the no command screen.
After i noticed that i cannot also access recovery i flashed ZEROLTE_EUR_OPEN_HIDDEN240M.pit along with the repair firmware.
Again i stucked at erasing screen.
After that i found a tar file with the stock recovery
Tried to flash it with odin but i get a kernel rev check fail device 2 binary 1 guess i need a newer file .