Hi all. I thing my phone is struggeling to survive.
First I'll give you some background info:
Phone is SGS3 I9300.
[ROM] Has been running Omega Rom since one of the first versions. Been running v32 since it was released (not v32.1)
[Kernel] Been running Omega's tweaked stock kernel most the time, but installed SiyahKernel 1.7rc3 some days ago.
About a week ago I recieved a 64gb SanDisk MicroSDXC card and installed Mittiadj's ExtSD2InternalSd script.
[recovery] CWM V6.0.1.2
So, what happened?
Well, when I installed the extsd2internal it wouldn't apply on boot, so per his guide, I installed Script Manager and got it working.
Some days ago I wiped system, flashed omega 32, flashed siyah kernel and flashed the extsd2internal for custom kernels.
Now the script worked without script manager.
After I installed Siyah, the phone reboted twice, about a day or 2 apart. The 3rd time it rebooted automatically, it did not manage to boot again (stopped at the Siyah boot logo,the purple eye).
From here, I switched the phone off, and using vol-up+home+power, I am SOMETIMES able to get into recovery. However, in recovery, I am able to flash cache but not dalvik, I tried flashing Omega, but it froze during the install wizard, I tried wiping system (for another attempt at Omega) but it rebbots then also.
Now the phone only gets to the White Samsung logo or to recovery (but recovery only shows version and the text)
E: can't mount /cache/recovery/command
Click to expand...
Click to collapse
If I hold vol-down+home+power, I get to a question if I want to install Custom ROM, vol down for cancel, up for yes. Pressed down.
Warning!! A custom OS can cause critical....
If you want to download a custom OS, press the volume up key, otherwise, press volume down
Click to expand...
Click to collapse
Where can I go from here?
What has gone wrong?
I am suspecting the memory chip is fubar, but hope someone can tell me otherwise
For the record, I have tried booting with and without sim and microsd, no change comes from that.
In the mean time I guess it's time to resurrect the god'ol Nexus One
Requiem87 said:
Hi all. I thing my phone is struggeling to survive.
>>>>>>
f I hold vol-down+home+power, I get to a question if I want to install Custom ROM, vol down for cancel, up for yes. Pressed down.
Quote:
Warning!! A custom OS can cause critical....
If you want to download a custom OS, press the volume up key, otherwise, press volume down
This reads as totally bolocksd firmware and recovery .
Remove SD card and format it in windows as FAT 32 .
Boot to download mode and flash stock rom via Odin as alternative is a non warranty repair .
jje
jje
Click to expand...
Click to collapse
JJEgan said:
Requiem87 said:
Hi all. I thing my phone is struggeling to survive.
Remove SD card and format it in windows as FAT 32 .
Boot to download mode and flash stock rom via Odin as alternative is a non warranty repair .
Click to expand...
Click to collapse
Tried flashing CWM via ODIN, but get an error after Writing stage. (i shoulden't have done that, because before the flash counter was 0, and it showed stock, after it shows as modified
Any reason to believe that flashing a stock rom will work better than flashing CWM?
Click to expand...
Click to collapse
Confused flashed CWM >> do you mean root ???
Stock rom has a kernel and would at least be on the right road for a warranty repair .
jje
JJEgan said:
Confused flashed CWM >> do you mean root ???
Stock rom has a kernel and would at least be on the right road for a warranty repair .
jje
Click to expand...
Click to collapse
Phone is allready rooted, as i had Omega Rom installed.
CWM means ClockWorkMod Recovery. I allready had that installed to, but as i wrote in first post, I had trouble getting it into recovery mode.
Nothing's changed in that regard tho
Update:
Tried flashing a stock rom via Odin, and this is the error message I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLJ4_I9300TENDLJ3_I9300XXDLID_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Requiem87 said:
Phone is allready rooted, as i had Omega Rom installed.
CWM means ClockWorkMod Recovery. I allready had that installed to, but as i wrote in first post, I had trouble getting it into recovery mode.
Nothing's changed in that regard tho
Update:
Tried flashing a stock rom via Odin, and this is the error message I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLJ4_I9300TENDLJ3_I9300XXDLID_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
not looking so good - I think I would have another go at flashing stock - my AV/ firewall sometime stop odin trying disabling them - I suspect it wont help but hopefully it will
Related
I have a bricked i9300 galaxy s3 16gb,i have it bricked 3 months or more...i want to resurrect it, but i dont know how... Please, help, I had flashed every kind of roms but it doesn´t starts,it continuously reboot in the samsung screen,i delete ALL in the odin but without any success... Please help me, i am not a developer,I am a spanish 18 years old and I am very lost...please help...
I tryed to flash the stock rom of samsung
I9300XXELLC
I tryed to flash the "unbrick" method of the 2nac program but it fails when it starts to flash (it fails when he beggins to flash "boot.img")
http://www.2nas.com/index.php/site/page?view=howto#unbrick
I tryed to flash the resurrect rom to unbrick it
http://checkrom.com/threads/resurrection-odin-checkrom-evohd™-v4.896/
And all this methods of unbrick failed. Now, I am trying to flash this
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
This is the message of odin when I flash the files
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I don´t know why it fails, because when i flash only a PDA file,the stock rom for example,it flash perfectly, but when I flash other files it fails.
Somebody can help me??? PLEASE...
you should flash a stock FW via odin.
just make sure before starting odin you need to close all kies processes via task manager, this could lead to the failed operation.
GL
i tried it but it fails... :S
eytan123 said:
you should flash a stock FW via odin.
just make sure before starting odin you need to close all kies processes via task manager, this could lead to the failed operation.
GL
Click to expand...
Click to collapse
when i flash it,the process is success but after the flash,when I try to turn the device on just restarts over and over again when it reaches the samsung screen, the animated image, not the "samsung galaxy s3" beggining image
Go into recovery and do a reset after the flash
1) Flash a stock ROM via ODIN
2) If it keeps restarting at the Samsung logo, go into recovery (turn the phone off and then hold volume up + home button + power button until the Android appears) and factory reset/wipe data.
3) Restart
DeadSOL said:
1) Flash a stock ROM via ODIN
2) If it keeps restarting at the Samsung logo, go into recovery (turn the phone off and then hold volume up + home button + power button until the Android appears) and factory reset/wipe data.
3) Restart
Click to expand...
Click to collapse
after the flash i cant enter to recovery mode...
davidmartins said:
after the flash i cant enter to recovery mode...
Click to expand...
Click to collapse
You will need to flash 3 things
1. Stock firmware
2. Cf auto root
3. CWM recovery touch
And then enter into recovery and make a reser
Sent from my GT-I9300
Recovering a bricked Galaxy S3
davidmartins said:
I have a bricked i9300 galaxy s3 16gb,i have it bricked 3 months or more...i want to resurrect it, but i dont know how... Please, help, I had flashed every kind of roms but it doesn´t starts,it continuously reboot in the samsung screen,i delete ALL in the odin but without any success... Please help me, i am not a developer,I am a spanish 18 years old and I am very lost...please help...
I tryed to flash the stock rom of samsung
I9300XXELLC
I tryed to flash the "unbrick" method of the 2nac program but it fails when it starts to flash (it fails when he beggins to flash "boot.img")
http://www.2nas.com/index.php/site/page?view=howto#unbrick
I tryed to flash the resurrect rom to unbrick it
http://checkrom.com/threads/resurrection-odin-checkrom-evohd™-v4.896/
And all this methods of unbrick failed. Now, I am trying to flash this
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
This is the message of odin when I flash the files
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I don´t know why it fails, because when i flash only a PDA file,the stock rom for example,it flash perfectly, but when I flash other files it fails.
Somebody can help me??? PLEASE...
Click to expand...
Click to collapse
I've got a Galaxy S3 which goes into a reboot loop from time to time and I found this which should help you:
http://reviews.cnet.co.uk/mobile-phones/how-to-recover-a-bricked-samsung-galaxy-s3-50009490/
I'd be interested to know if it solves your problem.
JohnOfStony said:
I've got a Galaxy S3 which goes into a reboot loop from time to time and I found this which should help you:
http://reviews.cnet.co.uk/mobile-phones/how-to-recover-a-bricked-samsung-galaxy-s3-50009490/
I'd be interested to know if it solves your problem.
Click to expand...
Click to collapse
Sorry but...I´ve done it and it reboots like before... Really thank you even so...
Problem...
I think i fried the EMMC... because when i try to flash the pit it doesn´t works...
But when I try to flash a PDA file, the stock rom, it flash succesly, but after the flash, it reboots continuously... i think the partition of bootloader is the bad flashed here...
If you´ve got other pit files can you post here the url? Thanks!
davidmartins said:
I think i fried the EMMC... because when i try to flash the pit it doesn´t works...
But when I try to flash a PDA file, the stock rom, it flash succesly, but after the flash, it reboots continuously... i think the partition of bootloader is the bad flashed here...
If you´ve got other pit files can you post here the url? Thanks!
Click to expand...
Click to collapse
When stock rom has flashed by odin each write is verified and if any error is found will be logged in odin textarea.
So, probably problem is not emmc.
The common cause to boot loop is data partition has been corrupted.
To solve is necessary format data partition.
To boot direct in recovery mode, use the combination volume_up+home+power.
Use recovery menu to issue the factory reset.
davidmartins said:
I have a bricked i9300 galaxy s3 16gb,i have it bricked 3 months or more...i want to resurrect it, but i dont know how... Please, help, I had flashed every kind of roms but it doesn´t starts,it continuously reboot in the samsung screen,i delete ALL in the odin but without any success... Please help me, i am not a developer,I am a spanish 18 years old and I am very lost...please help...
I tryed to flash the stock rom of samsung
I9300XXELLC
I tryed to flash the "unbrick" method of the 2nac program but it fails when it starts to flash (it fails when he beggins to flash "boot.img")
http://www.2nas.com/index.php/site/page?view=howto#unbrick
I tryed to flash the resurrect rom to unbrick it
http://checkrom.com/threads/resurrection-odin-checkrom-evohd™-v4.896/
And all this methods of unbrick failed. Now, I am trying to flash this
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
This is the message of odin when I flash the files
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I don´t know why it fails, because when i flash only a PDA file,the stock rom for example,it flash perfectly, but when I flash other files it fails.
Somebody can help me??? PLEASE...
Click to expand...
Click to collapse
Dear Brother I think u flash stock recovery 1st and then try to flash new rom.then f-reset and restart,mey bit solve.sorry 4 my bad English.find zip 4 sotck recovery
sam77744 said:
Dear Brother I think u flash stock recovery 1st and then try to flash new rom.then f-reset and restart,mey bit solve.sorry 4 my bad English.find zip 4 sotck recovery
Click to expand...
Click to collapse
flash via odin
I've tried same as davidmartins but all failed w/ the same Odin log.
Initial rom on my S3 was I9300XXLEF (Hong Kong) and I flashed Samsung Galaxy S III GT-I9300 Stock Firmware Collection I9300XXEMA2 after that it didn’t re-boot because of wrong ROM, if I try to get into recovery it shows the “Firmware upgrade encountered issue. Please select recovery mode in Kies & try again” screen.
I tried also to re-flash the Stock FW but failed too.
Any further advise to bring my S III back to life would be highly appreciated.
Cheers.....LinChina
your motherboard are dead .. I had the same problem with an HTC HD2. motherboard has failed without doing something wrong.
andreivibefm said:
your motherboard are dead .. I had the same problem with an HTC HD2. motherboard has failed without doing something wrong.
Click to expand...
Click to collapse
i will do a JTAG in a week.If it doesn´t works, I will buy another galaxy s3 T.T
davidmartins said:
i will do a JTAG in a week.If it doesn´t works, I will buy another galaxy s3 T.T
Click to expand...
Click to collapse
y havet same isuse bat y resolvet . try to flash diferent cw recovery and then the room
sory for bad eng.
HI.
I had installed Odin and flashed the touch CWM 6 to my phone then I installed PureHD custom rom.
I noticed that the phone would reboot on its own every now and then.
But when it reboots, it just goes into a boot loop up to the logo , then reboots again.
Till I take out the battery, wait a little while , then re-insert the batter.
After that the phone will boot "normally" and would be functional for some time again.
I decided to change the Firmware, so i downloaded the cm-10.1-20130701-crDroid-build5-i9300.zip and install it.
That loaded fine for the most part.
I say that because when i try to use the sms application i noticed 2x since last night.
It does the same thing. It just reboots and get stuck at the logo once again.
Also I cannot copy items to my phone when its connected to my computer via the usb cable.
It tells me "cannot copy to device, either the device has either stopped responding or has been disconnected.
All this is very frustrating.
I am thinking about trying to load a stock rom via Odin to see if that will help.
Any ideas will be greatly appreciated.
Thanks..
Protorianbz
[READ THlS FlRST] POST QUESTIONS IN THE Q&A SECTION AND NOT HERE!!!!
Wipe phone and flash stock rom.
jje
I tried that.
I tried to isntall the STock rom.
It was installed via Odin successfully.
I saw the green Android man for a split second.
And phone just reboots, and now is stuck in the boot loop to the logo..
then reboots again..
This is the output form Odin 3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMC3_I9300NEEEMC1_I9300XXEMB6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
have you tried a hard reset? format data , cache and dalvik in recovery? after you successfully flashed stock rom? hope that helps
Try using MegaWipe from here: http://forum.xda-developers.com/showthread.php?t=1832326&page=31
and then flash a ROM.
Just don't forget to backup the Important stuff.
Just wipe phone and install stock rom
Sent from my GT-I9300 using xda premium
Thread moved to proper forum.
DiDA™ said:
Try using MegaWipe from here: http://forum.xda-developers.com/showthread.php?t=1832326&page=31
and then flash a ROM.
Just don't forget to backup the Important stuff.
Click to expand...
Click to collapse
^^ What s/he said...
You don't mention the word wipe so I figure you didn't do that. If you can't get into the phone you should do your battery-removal thing and let the phone get into the OS, then connect USB and copy out the files you need to save. If you've got a backup to your extSDcard that would be helpful - you can always restore data from an advanced CWM Restore setting.
Copy the ROM you want across to the estSDcard using USB
Download megawipe, copy it to estSDcard and flash it in CWM.
Flash your ROM and restart phone, Set it up and once done, then start adding apps and restoring data, THEN make a full backup.
As a rule, the only time you do not do a full wipe of your phone is when you are flashing a point upgrade. i.e. going from AbcROM 7.1 to AbcROM 7.2 - if you are changing ROMs or doing a full step upgrade (AbcROM 7.x to AbcROM8.x) you need to do a full wipe to avoid problems.
So I think I may have bricked my Samsung GS4. This is what I did.
I had previously been rooted with TWRP custom recovery partition. I did the new update (I know, I know). Surprise surprise my root access was gone ans so was the recovery partition. Now I have none at all. I wanted to flash the new Google play edition ROM onto the S4 so I went about re-rooting using the root exploit method and a microsd card.
The root went fine and I gained access again. Here is where I messed up though. I tried to re-install the TWRP recovery partition using goo manager. The install went fine, but when I rebooted the phone I got an error message and was sent straight into Odin mode. ****. Phone won't boot at all except into this mode.
I then went to my PC and attempted to re-install the MDK tar file to re-flash. Didn't work. I got a firmware error upgrade error message and advice to recovery using Kies. I tried this. Kies could not locate my device on the USB drive. (I'm using the stock cable mind you). I then did some searching on here and found out that I needed to use the ME7 tar file in odin. You can't flash back. I did this. I got an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
The highlighted in red is where things went wrong I suspect but I didn't know what to do after that. I went on to try the "OneClick unbrick" method from there.
I put into odin mode and using the soft unbrick and I got an error claiming my device has not been plugged in. Now I have all the device drivers so I'm not sure what the problem could be is. Any help or suggestions? I called verizon and they're sending me another S4 but I'll be phone less until tuesday. In the mean time if I can figure out how to fix this I would much rather do that then deal with possibly be found out of voiding my warranty.
Thanks,
Dolph
Dolphlungegrin said:
So I think I may have bricked my Samsung GS4. This is what I did.
I had previously been rooted with TWRP custom recovery partition. I did the new update (I know, I know). Surprise surprise my root access was gone ans so was the recovery partition. Now I have none at all. I wanted to flash the new Google play edition ROM onto the S4 so I went about re-rooting using the root exploit method and a microsd card.
The root went fine and I gained access again. Here is where I messed up though. I tried to re-install the TWRP recovery partition using goo manager. The install went fine, but when I rebooted the phone I got an error message and was sent straight into Odin mode. ****. Phone won't boot at all except into this mode.
I then went to my PC and attempted to re-install the MDK tar file to re-flash. Didn't work. I got a firmware error upgrade error message and advice to recovery using Kies. I tried this. Kies could not locate my device on the USB drive. (I'm using the stock cable mind you). I then did some searching on here and found out that I needed to use the ME7 tar file in odin. You can't flash back. I did this. I got an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
The highlighted in red is where things went wrong I suspect but I didn't know what to do after that. I went on to try the "OneClick unbrick" method from there.
I put into odin mode and using the soft unbrick and I got an error claiming my device has not been plugged in. Now I have all the device drivers so I'm not sure what the problem could be is. Any help or suggestions? I called verizon and they're sending me another S4 but I'll be phone less until tuesday. In the mean time if I can figure out how to fix this I would much rather do that then deal with possibly be found out of voiding my warranty.
Thanks,
Dolph
Click to expand...
Click to collapse
Solved.
Fix:
Resinstalled Odin (wouldn't let me run as administrator before. Reinstalled Me7 from zip (extracted). Booted up Odin. Unchecked repartion. and voila. It re-flashed successfully.
Question:
Is there a way to install custom ROMs on this with the ME7 bootloader? I want to install the Google Play edition port, but everything I see suggest using TWRP or the Clockwork Recovery Mod. Since these can't be loaded onto Me7. How does one do this? Via a .tar in Odin?
i had the same problem. if your just trying to get unbricked i can help. (warning i am extremely new at all this). so i did the update and ever since had been trying to get root access and flash a custom ROM. i too tried to install twrp through goo manager. i kept bricking my device by trying to boot into recovery. i found out that if do a battery pull, and hold the volume down and power button (booting into recovery) but dont let go until a warning page comes up. it should warn you about installing custom roms and give you the option of continuing by pressing the volume up button, or pressing the volume down to reboot. choose to reboot and you should be back to nromal. hopes this helps and was what you where looking for.
Dolphlungegrin said:
Solved.
Question:
Is there a way to install custom ROMs on this with the ME7 bootloader? I want to install the Google Play edition port, but everything I see suggest using TWRP or the Clockwork Recovery Mod. Since these can't be loaded onto Me7. How does one do this? Via a .tar in Odin?
Click to expand...
Click to collapse
There is currently no way to install a different rom after taking the ME7 update. You cannot go back to MDK either.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Yo Guys! I think my bootloader was already updated, and I tried to flash back to original 4.3 or 4.1.2, but nothing of it worked.
When I try to flash f.e. the
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMR2_I9300VFREMA3_I9300BUEMA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me I was on CM 10.2/CM11 and wanted to restore factory images, because my Audio Plug-In didnt work properly anymore and my screen had some pixel errors.
I tried to flash a CWM touch recovery, but that did work only once - then flashed the bootloader downgrade Restore_Bootloader_XXBLFB.zip, but
I still couldnt flash any factory firmware
I also tried this here:
http://forum.xda-developers.com/showthread.php?t=2083860
Tried method 2 of that one, didnt get me in position to install the stock firmware.
Does anyone have any advice?
I still can enter CWM (or install it) and can enter Download Mode
I tried 4.3, 4.1.2 and 4.0.4 , nothing worked
Update #1 I could reflash cyangenmod over cwm again and my cell works too. *phew*
How do I get back to stock rom? Meanwhile I'll try mobile odin
update #2
mobile odin worked, got back to stock. just letting u know.
Have you tried another version of ODIN? I used to have some issue with version 3.0 and above. So it seems that version 1.8.5 is more stable that the new ones... try redownload your ROM, maybe it has some issues too.
Finally, use SAMSUNG SG3 TOOLKIT, I have used that too and without any issue.
Good Luck
:cyclops:
froycard said:
Have you tried another version of ODIN? I used to have some issue with version 3.0 and above. So it seems that version 1.8.5 is more stable that the new ones... try redownload your ROM, maybe it has some issues too.
Finally, use SAMSUNG SG3 TOOLKIT, I have used that too and without any issue.
Good Luck
:cyclops:
Click to expand...
Click to collapse
Read post above you
I tried Version 1.85 and 3.09, both didn't work. But thanks to Chainfire for developing this awesome tool :laugh::good:
mobile odin got my phone finally flashed
Hey everyone,
I tried updating my Verizon Galaxy S4 to Lollipop via Samsung Kies. The update process produced an error message (at app. 10%) and offered me to start the recovery process, which failed subsequently. Needless to say, Android OS does not work, however I can still boot into download/recovery mode.
I've been trying to flash various stock ROMs via Odin 3.10 with no success. The build numbers of the ROMs I've been trying to flash contained the I545VRUFNC5 number, since I tried preserving compatibility with the previous (Stock) ROM that had the same build number. Prior to flashing Lollipop via Kies, I made the made a screenshot (attached below) in case I ran into some kind of trouble. It contains the Model/Build of my S4.
I've also tried using a PIT file during the flashing process with no success.
The error message Odin gives me always reads:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The main question is whether I need to stick to build I545VRUFNC5 to reflash. If not, which Stock ROM am I able to Install via Odin without bricking the phone further
For exact phone model/specs pls open the screenshot below. I would also be very grateful if someone could provide me a stock ROM (name/link/version) that I could flash via Odin to resolve the mess Kies and I created.
Any help is much appreciated.
Thanks in advance.
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
XxD34THxX said:
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
Click to expand...
Click to collapse
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
intel.fan said:
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
Click to expand...
Click to collapse
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
XxD34THxX said:
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
Click to expand...
Click to collapse
No mate, since the bootloader seems to be locked. It simply didn't flash TWRP - the stock bootloader is still present and running. Trying to flash TWRP was kind of a desparate measure, since I don't have OS access to flash/install any of the above. Also, my phone was 100% stock Kitkat 4.4.2 with no root access
Resolved the issue! =)
The problem was in that the Lollipop update process had already been started (unsuccessfully), Odin was "seeing" the flash process as a downgrade - so it wouldn't allow it.
I tried flashing a stock Lollipop ROM via Odin and it worked like a charm
Thanks for your support.
@mods: Please close/archive this thread.