I probably shouldn't have even attempted this without more info, apparently, but I wanted to give Cyanogenmod and lolipop a try, so I sort of blundered ahead and now Im soft bricked at the "Firmware upgrade encountered an issue." screen.
So, basically first I tried to update TWRP from 2.7 to 2.8.5 via TWRP updater on the play store. It rebooted and didn't take, so I went and proceeded with installing Cyanogenmod via 2.7 TWRP, wiped the pertinent caches and such, and the flash seemed to take, but when I rebooted, I couldn't get passed the Galaxy S4 screen and I had weird brief flickering when I rebooted to try to get it working again, which it never did.
At this point, I just figured I would flash the backup I made prior to trying to install Cyanogen, but that flash failed and I was stuck at Odin, with no option to boot into recovery.
Here is where I probably screwed things up even more, as I didnt realise there was a specific ROM I was supposed to flash from Odin, so I've tried and failed to flash a bunch of stock images I've found online, none of which appear to be the right one. Im stopping here and deferring to the forum for some help, hopefully. Apologies if this is a common thing, but my searchings haven't turned up anything I can use, and Im afraid to screw up my phone more.
The last image I tried to flash was this:
SCH-I545_VZW_1_20130613171315_24s13crny1_fac
Odin got to aboot.mdn and then failed, with this message
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
the ODIN screen on my phone reads
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
EMAC BURST MODE: enabled
START [224,1440]
SW REV, CHECK FAIL : fused : 6(or possibly 8? it looks more like a 6 though), Binary : 3
Also, I wasn't aware I needed a PIT file, so at this point I pretty much need every relevant file and detailed instructions on what to do. Apologies for my noobishness, this is the first time in 5 years I've needed this much help flashing a ROM... =(
Thanks in advance!
Edit: The problem was indeed that I was trying to flash an older ROM onto my phone. For the stupid inclined, always check what baseband model your phone is before flashing a stock image. If you're locked out of the OS, you can find this on the sticker on the side of the box your phone came it, under the listing "s/w" version, the last three characters will tell you what baseband version your phone shipped with.
Beginning to see where I went wrong in Odin, as I've been trying to flash earlier android versions. Downloading an NC5 factory image now, Will report back.
Christ, Im an idiot.
mort_subite said:
I probably shouldn't have even attempted this without more info, apparently, but I wanted to give Cyanogenmod and lolipop a try, so I sort of blundered ahead and now Im soft bricked at the "Firmware upgrade encountered an issue." screen.
So, basically first I tried to update TWRP from 2.7 to 2.8.5 via TWRP updater on the play store. It rebooted and didn't take, so I went and proceeded with installing Cyanogenmod via 2.7 TWRP, wiped the pertinent caches and such, and the flash seemed to take, but when I rebooted, I couldn't get passed the Galaxy S4 screen and I had weird brief flickering when I rebooted to try to get it working again, which it never did.
At this point, I just figured I would flash the backup I made prior to trying to install Cyanogen, but that flash failed and I was stuck at Odin, with no option to boot into recovery.
Here is where I probably screwed things up even more, as I didnt realise there was a specific ROM I was supposed to flash from Odin, so I've tried and failed to flash a bunch of stock images I've found online, none of which appear to be the right one. Im stopping here and deferring to the forum for some help, hopefully. Apologies if this is a common thing, but my searchings haven't turned up anything I can use, and Im afraid to screw up my phone more.
The last image I tried to flash was this:
SCH-I545_VZW_1_20130613171315_24s13crny1_fac
Odin got to aboot.mdn and then failed, with this message
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
the ODIN screen on my phone reads
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
EMAC BURST MODE: enabled
START [224,1440]
SW REV, CHECK FAIL : fused : 6(or possibly 8? it looks more like a 6 though), Binary : 3
Also, I wasn't aware I needed a PIT file, so at this point I pretty much need every relevant file and detailed instructions on what to do. Apologies for my noobishness, this is the first time in 5 years I've needed this much help flashing a ROM... =(
Thanks in advance!
Edit: The problem was indeed that I was trying to flash an older ROM onto my phone. For the stupid inclined, always check what baseband model your phone is before flashing a stock image. If you're locked out of the OS, you can find this on the sticker on the side of the box your phone came it, under the listing "s/w" version, the last three characters will tell you what baseband version your phone shipped with.
Click to expand...
Click to collapse
My phone stuck in download mode because i install twrp from twrp manager apk. Now it cannot go to recovery or to OS, just download mode.. I have tried to odin some recovery & ROM but no luck..
octantcomp said:
My phone stuck in download mode because i install twrp from twrp manager apk. Now it cannot go to recovery or to OS, just download mode.. I have tried to odin some recovery & ROM but no luck..
Click to expand...
Click to collapse
I had the same problem. I tried to update to 2.8.5.0 via TWRP's Play Store app and got a soft brick. Couldn't get to OS or into TWRP recovery. The phone was stuck at "Booting into recovery" blue text.
This is a common problem: http://forum.xda-developers.com/galaxy-s4-verizon/help/q-twrp-2-8-5-0-t3029191
You'll notice you can only download 2.8.4.0 on TWRP's official website: http://dl.twrp.me/jfltevzw/
I figured I lost the bootloader and the OS since I could only get into download mode. Worst case scenario, I could push the Verizon MDK image again, and push loki'd TWRP recovery back into bootloader with dd command in terminal.
I was in major 'screw it' mode. So I put the phone into download mode and fired up Odin. I tried to push the TWRP 2.8.4.0 tar for the jfltexx firmware via the "bootloader" field. I know the Odin mode isn't compatible with jfltevzw and it did say "failed" as expected, however on reboot I didn't get stuck at the "Booting into recovery" blue text. Everything was intact. Somehow, it fixed the bootloader/recovery on my device.
Once into the OS, I reflashed the jfltevzw img 2.8.4.0 using the "dd" mode in terminal. I didn't want to give it a chance to get stuck at the blue text again on reboot: http://twrp.me/devices/samsunggalaxys4verizon.html
Hope it helps someone!
Related
Hey guys, long time lurker, couple time poster here. I'm going to try my best to explain what's going on. A while back I rooted and installed a custom ROM on my Verizon S4. It had some data issues so I dabbled with it for a while, managed to brick it once, finally got it up and running again. LTE was still an issue so I took it to Verizon and played dumb hoping to just get a new phone. They called tech support and managed to get it running as normal.
Fast forward to tonight. I decided to get adventurous again and re-root my phone. However after I installed TWRP via GooManager (also tried CWRM after I ran into trouble) I tried rebooting to recovery to flash a custom ROM and recovery appears to not exist. It instead boots straight into Download Mode. I tried installing TWRP via Odin, that Failed. Now with every reboot it goes straight to Download Mode. My only remedy to boot the phone is to attempt to boot into Download Mode then proceed to cancel. I have tried re-flashing CWRM and TWRP numerous times. Below is the text available on the Download Mode screen. Any ideas on how I can regain Recovery? Please let me know if there are any additional details I can provide.
Download Mode text
Could not do normal boot.
ODIN Mode
Product Name: SCH-I545
Current Binary: Samsung Official
System Status: Official
CSB-Config-LSB: 0x30
Write Protection: Enable
PUstudentNDfan said:
Hey guys, long time lurker, couple time poster here. I'm going to try my best to explain what's going on. A while back I rooted and installed a custom ROM on my Verizon S4. It had some data issues so I dabbled with it for a while, managed to brick it once, finally got it up and running again. LTE was still an issue so I took it to Verizon and played dumb hoping to just get a new phone. They called tech support and managed to get it running as normal.
Fast forward to tonight. I decided to get adventurous again and re-root my phone. However after I installed TWRP via GooManager (also tried CWRM after I ran into trouble) I tried rebooting to recovery to flash a custom ROM and recovery appears to not exist. It instead boots straight into Download Mode. I tried installing TWRP via Odin, that Failed. Now with every reboot it goes straight to Download Mode. My only remedy to boot the phone is to attempt to boot into Download Mode then proceed to cancel. I have tried re-flashing CWRM and TWRP numerous times. Below is the text available on the Download Mode screen. Any ideas on how I can regain Recovery? Please let me know if there are any additional details I can provide.
Download Mode text
Could not do normal boot.
ODIN Mode
Product Name: SCH-I545
Current Binary: Samsung Official
System Status: Official
CSB-Config-LSB: 0x30
Write Protection: Enable
Click to expand...
Click to collapse
You're probably running release VRUAME7, which means that you can't successfully flash an updated recovery using ODIN.
Grab the stock no-wipe ME7 image and flash that using ODIN. That'll get you out of download mode.
The no-wipe images are at http://forum.xda-developers.com/showthread.php?t=2301259
Hey guys, I dug out my old i605 the other day and wanted to update to the latest cm nightly for the device. Not realizing I was about to do something wrong, I downloaded an app called Flashify and installed the latest cm recovery through the app. Well this made my device boot loop. So now, I need to flash a working recovery to my device to fix it. After googling for a bit, I learned that I need Odin to do so. So I am now using Odin v3.10.7. But, I cannot get any recovery tars I've found to flash. They all come back as failed. I'm at a loss here and hope someone knows how to get this thing back up and running.
My PC is on Windows 10 and I do have the latest Samsung drivers installed. On my Note 2 in download mode, it says my current binary is Samsung Official and my system status is custom. What I do not know is what recovery and firmware my i605 was on previously.
Thanks guys
EDIT: I guess what I'd really like to do is get the device back to stock rooted.
Edit 2: Fixed the problem. Uninstalled the Samsung drivers and reinstalled them and changed to Odin 3.07. Ended up restoring the device with the unlocked bootloader restore here: http://forum.xda-developers.com/showthread.php?t=2040264
Hi, I have a GS4 (SCH-I545) and I tried to get TWRP and then CyangenMod, so I rooted my phone, used ROM Manager to get TWRP, rebooted into recovery, only to get the stock recovery. So I tried Flashify, rebooted, but got the Verizon warning screen, so then I used the workaround to get back in to my phone. I then tried again but then I couldn't get bacl into a recovery mode, just odin mode with "Could not do normal boot" in the top left. So I did the workaround again, I then figured something was wrong with the bootloader, so I used Flashify to flash "a-boot.img" hoping it would work, now I can't get into recovery mode, can't get into Android, can't even charge my phone, the odin mode will always come on, I can go intpo normal odin mode though, but that's it, I can't do anything on my phone, only go into odin mode, so I guess I've bricked my phone. What should I do?
SolidSG said:
Hi, I have a GS4 (SCH-I545) and I tried to get TWRP and then CyangenMod, so I rooted my phone, used ROM Manager to get TWRP, rebooted into recovery, only to get the stock recovery. So I tried Flashify, rebooted, but got the Verizon warning screen, so then I used the workaround to get back in to my phone. I then tried again but then I couldn't get bacl into a recovery mode, just odin mode with "Could not do normal boot" in the top left. So I did the workaround again, I then figured something was wrong with the bootloader, so I used Flashify to flash "a-boot.img" hoping it would work, now I can't get into recovery mode, can't get into Android, can't even charge my phone, the odin mode will always come on, I can go intpo normal odin mode though, but that's it, I can't do anything on my phone, only go into odin mode, so I guess I've bricked my phone. What should I do?
Click to expand...
Click to collapse
Well, first of all, if your galaxy didn't have the MDK bootloader (first version of firmware, android 4.2.2) you are not able to get CM nor Recovery (CWM, TWRP...), because Verizon locked the bootloader in all the other versions. If you touched our "lovely" bootloader you could have messed up your device, but you can get into download mode so you should try downloading a stock rom equal or newer to the android version you used to have before you bricked your device (you cannot downgrade your phone), if that doesn't work you can try Samsung Smart Switch to repair it.
Okay ill try downloadig a stock rom, but I don't really know how to do it, got any links telling how?
Well, we can't point you to a stock ROM to odin with. You can't just simply Odin back to MDK. That has been blocked off by a physical qfuse, which will further mess up your device. Can you get into download mode and tell us what version do you have?
All download mode says is this: odin mode
Product name: SCH-I545
Current binary: Samsung Official
System status: custom
CSB-CONFIG-LSB: 0x30
Write protection: Enable
eMMC BURST MODE enabled
Nothing about the version
Id say the version I have was later than 4.2.2 considering I couldn't get a recovery working, the previous owner updated it some time in early 2014 maybe june so any version of KitKat later than that might work
Hello!
First of all, I'm not a native speaker so let me know if there is something that is not clearly stated / confusing.
I got a little problem with my phone and was unable to find a solution to my problem in this forum or anywhere else so I just registered moments ago
My phone: Samsung Galaxy S2 GT-i9100, running freshly flashed stock ROM (android 4.1.2 , stock recovery)
*HISTORY*
I tried to flash a custom recovery and after soft-bricking it I flashed a "stock ROM" from Samsung which I found on the internet and everything works perfectly again.
However, this shouldn't be of any relevancy to the following problem(s).
*WHAT I WANT*
I want to install the latest snapshot build of Cyanogenmod 12.1 (I would choose CM13 but there are only nightly builds and I don't want that).
As I'm new to all of this I followed manuals which told me to install the custom recovery "TWRP".
To do so I followed this manual: https: //twrp.me/devices/samsunggalaxys2i9100. html
and used "twrp-3.0.2-1-i9100.img"
*THE PROBLEMS*
After Heimdall tells me that everything was successfully flashed (noreboot is set) I turned the phone off and restarted it straight to recovery mode.
Instead of booting the TWRP custom recovery which I just flashed the android stock recovery was booted.
QUESTION 1: Does anyone have an idea why that happens?
As far as I know there is just a 'vestigial' recovery partition on the i9100.
Apparently 'isorec' offers a way to make it available for my custom recovery so that TWRP does not get overwritten by the recovery
which is part of the CyanogenMod (which I'm going to install later on). Is that correct?
QUESTION 2: Is there anything I need to do to make isorec work which is not covered by the manual I use?
Apparently the system partition is too small for CyanogenMod13 + GoogleApps (but I want to use both later on).
QUESTION3: How can I repartition, how much space will I need and how do I do it? Do I have to do it before I flash recovery or before I flash the CM12.1 ROM?
So far I found several really unspecific tutorials and now I'm afraid to brick the phone.
Looking forward to any advice, thanks a lot!
blackdaw
Hi @blackdaw
I'll explain what went wrong and how to do what you want...
1. The TWRP 3.0.2-1.img is a isorec recovery. It won't boot unless you have an isorec-enabled kernel. If the kernel you have is not, then the recovery that is bundled with the kernel is booted instead(ie. the old style monolithic kernel/recovery in the kernel partition). So you need a newer kernel(which means a newer rom that runs with a isorec enabled kernel). Until you have that don't worry, we'll get to that.
2. Re-partitioning. You will eventually need to re-pit, as the newer roms(android 6+) often need a bigger system size even if you don't use gapps. 1GB should be ample. Here is a good guide for updating to MM roms, but also has links for re-partitioning. Take your time and study the different ways to re-pit, but personally I would just re-pit before flashing any roms, then it's done. I use odin(windows) and re-pit at the same time as installing a recovery using this method. As I said there are other ways....
3. What I would do:
Odin re-pit method
*I use gustavos kernel to flash with odin at the same time as the .pit file. Some .tar kernels don't work(Idon't know why)
Once you are in the TWRP/CWM recovery, do your backups/wipes and flash the rom and gapps(if you want) and TWRP 3.0.2-1.img, then reboot.
(No yellow triangle method)
download a kitkat compatible kernel such as the one I've attached
find the correct philz kernel for your stock rom from here. It needs to be in .zip format. Flash the kernel in the stock(3e) recovery, then reboot to recovery. This is all you need to flash older custom roms(you will be rooted and could stay on stock if you wanted but the recovery is obsolete for kitkat and above)
from the new philz/CWM recovery, flash the TWRP kernel I attached then reboot straight to recovery once again. (This kernel won't boot the rom; you will end up with a bootloop if you try. You only need the newer recovery)
now from this TWRP 2.8.7.0, flash the TWRP 3.0.2-1.img just to make sure you have that recovery installed to the recovery partition, and CM12.1(*note below) and gapps(if you want).
use Lanchons re-pitting tool to re-partition
Install diskinfo app from the store to check your partition sizes and if you want an easy way to see free space etc.
Note: I would strongly recommend you use the last nightly or newer unofficial build of CM12.1 if you are set on that rom. There are several major fixes(including the implementation of isorec) that are not included in the last official snapshot build. I've uploaded the last nightly here
I hope I've covered everything. Happy flashing
Hello noppy22,
thank you so much for your reply! I literally spent days reading all sorts of stuff so I would know and understand all alternatives and not brick my phone. However, I didn’t succeed so far, I’m stuck with the first step where I am supposed flash the philz kernel as preparation for flashing the TWRP stock kernel (which you attached).
So far I had about 15 different attempts with different methods but I try to remember what I did and what went wrong:
First I tried to repartition and flash the philz kernel
(versions “philz_touch_6.07.9-i9100.tar.md5” and “philz_touch_6.05.6-i9100.tar.md5”)
at the same time, following the manual you linked under “this method”.
Here is the log of what happens:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-i9100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
It was stuck at “NAND Write Start!!”. After a long, long time I just pulled the cable.
Afterwards I booted into recovery and tried flashing zip files of the same philz kernels.
Here I encountered an error looking something like this: “ This package is for "9100, …, …" devices; this is a ‘’ “
Instead it should say “ this is a ‘9100’ “ but the space between the ‘ ‘ is just empty, it doesn’t seem to recognize my device.
Others have this problem too: http://forum.xda-developers.com/showthread.php?t=2602107
Next thing I tried was the manual in cyanogen wiki:
(https:// wiki.cyanogenmod.org /w/Install_CM_for_i9100 )
Before the softbrick (as mentioned in first post under ‘history’) this enabled me to use CWM recovery.
Now that I tried it again it does not work any more, saying something like “no kernel partition detected”.
I thought this problem was caused by the new partitioning so I used the repart option in odin together with stock PIT-file. No success.
Now I ran out of options, I tried everything that came to my mind.
Any idea how to fix this? Try fifferent Kernel? I was not brave enough to pick one on my own.
Btw, after all this messing around I’m stuck in bootloop but can still reach Download Mode and Stock recovery.
If you need more detailed information/logs I'll try to reproduce the errors.
Thank you so much, I'm quite desperate!
All the best, blackdaw
Hi @blackdaw
I realise reading your post I was a little unclear on a couple of points. Sorry about that. I'll edit my post above to make it clearer for anyone needing the same help.
All you need to do is flash this kernel I've attached, in odin. Just untick reboot device and when you get a pass, turn off the device and boot into recovery. You will get a bootloop if you try to boot your rom. Before you do this, make sure you have your rom and gapps(if you want them) ready to flash from this new recovery.
Alternatively find the stock rom from sammobile.com and flash the .tar.md5 file from odin and start again. This is usually my goto step if I've messed anything up.
The two points I didn't explain very well were to use philz kernel in .zip format to flash from stock recovery before re-pitting, and I didn't explain when to re-partition. Again sorry about that.
EDIT: I've edited my first post. Hopefully it explains thing a bit better. Let me know how you go
Hi @noppy22,
it works, thank you so much!
So here is what I did in the end:
1. First I followed gsstudios guide to Increase system partition size and used all the software he attached.
The Samsung drivers were already installed so I launched Odin 3.07, loaded the "I9100_1GB-System_4GB-Data_512MB-Preload.pit" in the pit file section, checked "repartition", unchecked "reboot", loaded the "AOSP-LP-Kernel+_26-07-2015_TWRP-2.8.7.0.tar" (which you attached in your last post) in the PDA section and hit start. It took a while but in the end the odin log said something like "1succesfull / 0 unsuccessful"
2. After turning the phone off I rebooting to recovery mode which was now TWRP 2.8.7.0. Just to have the latest version I wanted to flash TWRP 3.0.2-1 but I didn't work because the device was "unable to mount emmc".
However, I justed flashed "cm-12.1-20160203-NIGHTLY-i9100" which you linked to in your first post and rebooted to system. TA DA! It worked!
There was still a problem with the storage. The now 4GB large Data partition and the 32GB external SD-Card were visible but not the 9GB internal SD-Card (UMS) wasn't. After rebooting to recovery to fix the problem a little surprise awaited me: TWRP version 3.0.2 was displayed, even though the previous update pretended to have failed. Well, I can't complain. Wiping the Data partition resolved the problem so android could successfully mount it.
End of story.
Now that everything is working, how can I get updates to the latest CM version? What really puzzles me is that they deleted the latest nightlys of CM12.1 and only left CM13 nightlys on the official CM download page.
Where did you get the CM12.1 nightly version you uploaded?
Is it safe to just do and OTA update?
I read in that one thread that OTA update is not safe for CM13 so if I find a reason to flash it I'll do it via recovery.
Thanks again!
All the best,
blackdaw
Hi @blackdaw,
I'm glad you got it working! The step you missed straight after the re-partition was formatting the new partitions from recovery. Especially sdcard0: without formatting sdcard0, the system will normally report that as corrupted or unable to read.
The 3.0.2 TWRP only booted after you had flashed the isorec enabled kernel(that is, by flashing CM12.1) The older kernel you used re-pitting wasn't isorec enabled, and so it used its own bundled TWRP 2.8.7 recovery. This was over-written by the kernel in CM12.1 when you flashed it......TWRP 3.0.2-1 will now work whenever you have isorec enabled kernel/rom and you don't need to flash it again; it will survive any normal wipes or flashes you make as it resides in the recovery partition.
Don't use OTA when you want to upgrade to CM13. You will need to do a full wipe and install with recovery.
The CM12.1 I still had on my computer from when it was on the CM page. They normally wipe older builds and keep newer ones for space I imagine. They will keep "snapshot" builds a lot longer, but CM12.1 never got a final snapshot, and we've never got a snapshot CM13 build despite being mostly stable depending on when they introduce new features/commits. Check on posts in the official CM13 thread for more info on bugs and which versions are more bug-free.
Good luck
Changing kernel sorts all issues
Changing kernel sorts all issues, thanks you for your help. :good:
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