I really need some assistance. My galaxy s4 sch-i545 starts with a Samsung logo and a unlocked padlock that says custom. I read I need to flash it to stock so I downloaded pit and stock firmware. I tried checking repartion, not checking it, different USB ports and it always says fail. I cannot return my phone to Samsung like this all help is greatly appreciated. I have USB debugging enabled and I think I saw fuses 5 binary 3 in download mode on top if that is important. I have lost hope in getting rid of that screen my phone turns on normally and everything.
ByteShark said:
I really need some assistance. My galaxy s4 sch-i545 starts with a Samsung logo and a unlocked padlock that says custom. I read I need to flash it to stock so I downloaded pit and stock firmware. I tried checking repartion, not checking it, different USB ports and it always says fail. I cannot return my phone to Samsung like this all help is greatly appreciated. I have USB debugging enabled and I think I saw fuses 5 binary 3 in download mode on top if that is important. I have lost hope in getting rid of that screen my phone turns on normally and everything.
Click to expand...
Click to collapse
Yeah, that "Fused 5 binary 3" is kind of important.
You have a MJ7 or MK2 bootloader (Fused 5) and are trying to flash something older.
You've probably permanently set the warranty void flag because you flashed an incompatible image.
Flash a MJ7 or MK2 full-wipe ROM That'll unroot you and restore to stock.
Thank you
k1mu said:
Yeah, that "Fused 5 binary 3" is kind of important.
You have a MJ7 or MK2 bootloader (Fused 5) and are trying to flash something older.
You've probably permanently set the warranty void flag because you flashed an incompatible image.
Flash a MJ7 or MK2 full-wipe ROM That'll unroot you and restore to stock.
Click to expand...
Click to collapse
Suprising warranty void and knox is 0x0 it is not voided I am kind of a noob I have done a lot of research and can't find a solution. I also noticed I got that dead DROID with the triangle now. Is my phone done for? I can't find the proper 4.3 firmware image for my device.
Thank you very much for the help ( I am a noob)
ByteShark said:
Suprising warranty void and knox is 0x0 it is not voided I am kind of a noob I have done a lot of research and can't find a solution. I also noticed I got that dead DROID with the triangle now. Is my phone done for? I can't find the proper 4.3 firmware image for my device.
Thank you very much for the help ( I am a noob)
Click to expand...
Click to collapse
You need to get it into download mode and flash either mk2 or mj7 it sounds like. Those files are in the dev section....
Sent from my unknown using Tapatalk
---------- Post added at 09:12 AM ---------- Previous post was at 09:11 AM ----------
Mj7 full wipe
http://forum.xda-developers.com/showthread.php?t=2507253
Sent from my unknown using Tapatalk
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
If that doesn't work try mk2
http://forum.xda-developers.com/showthread.php?t=2578209
Sent from my unknown using Tapatalk
Mistertac said:
You need to get it into download mode and flash either mk2 or mj7 it sounds like. Those files are in the dev section....
Sent from my unknown using Tapatalk
---------- Post added at 09:12 AM ---------- Previous post was at 09:11 AM ----------
Mj7 full wipe
http://forum.xda-developers.com/showthread.php?t=2507253
Sent from my unknown using Tapatalk
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
If that doesn't work try mk2
http://forum.xda-developers.com/showthread.php?t=2578209
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
Thank you I definantly will try this later does this trip knox or voids my warranty (MJ7 full wipe)
What do I leave checked and not checked in odin?
ByteShark said:
Thank you I definantly will try this later does this trip knox or voids my warranty (MJ7 full wipe)
What do I leave checked and not checked in odin?
Click to expand...
Click to collapse
No these won't touch your Knox flag since they are official Samsung fw.
Make sure ONLY Auto Reboot and F.Reset Time are ticked off. Very important.
Throw the tar file in the PDA slot and you're good to go. There are instructions on here somewhere if you need them. Fairly easy.
Sent from my unknown using Tapatalk
---------- Post added at 10:24 AM ---------- Previous post was at 10:19 AM ----------
Heres a YouTube video on unbricking an S4
http://m.youtube.com/watch?feature=...top_uri=/watch?v=GL8XwuRYoWU&feature=youtu.be
Sent from my unknown using Tapatalk
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
Any other helpful videos can be found here
http://forum.xda-developers.com/showthread.php?t=2337590
Sent from my unknown using Tapatalk
Mistertac said:
No these won't touch your Knox flag since they are official Samsung fw.
Make sure ONLY Auto Reboot and F.Reset Time are ticked off. Very important.
Throw the tar file in the PDA slot and you're good to go. There are instructions on here somewhere if you need them. Fairly easy.
Sent from my unknown using Tapatalk
---------- Post added at 10:24 AM ---------- Previous post was at 10:19 AM ----------
Heres a YouTube video on unbricking an S4
http://m.youtube.com/watch?feature=...top_uri=/watch?v=GL8XwuRYoWU&feature=youtu.be
Sent from my unknown using Tapatalk
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
Any other helpful videos can be found here
http://forum.xda-developers.com/showthread.php?t=2337590
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
HELP ME
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> sbl2.mbn
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
<ID:0/009> Added!!
ByteShark said:
HELP ME
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> sbl2.mbn
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
<ID:0/009> Added!!
Click to expand...
Click to collapse
I'm not certain on why that's giving you that error. Also I didn't see earlier that k1mu stated you may have flagged Knox doing what you did to get you to this point. I just know that if u Odin back to stock prior to trying to flash the wrong firmware.... You'd be good and not flag Knox.
Anyways..... Someone smarter than me can probably help you here. I'd try either the mj7 one... Or another mk2.
And make sure they are the full wipe files. Your including the pit file???
Sent from my unknown using Tapatalk
mistertac said:
i'm not certain on why that's giving you that error. Also i didn't see earlier that k1mu stated you may have flagged knox doing what you did to get you to this point. I just know that if u odin back to stock prior to trying to flash the wrong firmware.... You'd be good and not flag knox.
Anyways..... Someone smarter than me can probably help you here. I'd try either the mj7 one... Or another mk2.
And make sure they are the full wipe files. Your including the pit file???
Sent from my unknown using tapatalk
Click to expand...
Click to collapse
fixed the problem was the cable many thanks
Related
EDIT: SOLVED. ANSWER IS ON PAGE TWO. REMOVE BATTERY BEFORE ODIN REBOOT YOUR PHONE, AND THEN BOOT IN RECOVERY AND FLASH SUPERUSER. THANKS TO KINGHORSEY FOR THE FIND.
Hi guys,
I'm using a Rogers Galaxy Note on ICS 4.0.4. I'm trying to root it at the moment. I downloaded Odin version 3v 1.85 with CMW found at this link: http://forum.xda-developers.com/showthread.php?t=1584576
So, installed the driver, the phone is recognized in device manager as Samsung Mobile USB CDC Composite Device, and when I plug it into Odin it gives me com 4 ok.
Clicked PDA, added the CMW tar.md5 and pressed start. Odin tells me it has installed the image properly. My flash counter went up one notch, but when I reboot into recovery I still get to Android's stock recovery (which does not allow me to flash Superuser from my SD card).
I'm probably missing something here. What am I doing wrong?
Thank you
Technically....nothing
I'd run it again.....g
I'm at round number 7 haha and still no CWM.
theinvisiblehand said:
I'm at round number 7 haha and still no CWM.
Click to expand...
Click to collapse
Holy cow !!...LOL
Fort Knox note.......:laugh:
Can you list your step sequence ??
Wasn't there a script installed on the Rogers ics OTA that restores original recovery on boot? That script needs to be deleted after root is achieved and then cwm flashed again for it to stick.
Gubment Cheeze
---------- Post added at 01:59 PM ---------- Previous post was at 01:54 PM ----------
Try flashing cwm but don't tick reboot phone on Odin. Once flash is succesful , use 3 button combo to get into recovery. Flash su zip and reboot. Use file explorer of your choice to remove recovery script. Once that's done flash cwm again and hopefully it will stick.
Gubment Cheeze
Froid said:
Wasn't there a script installed on the Rogers ice OTA that restores original recovery on boot? That script needs to be deleted after root is achieved and then cwm flashed again for it to stick.
Gubment Cheeze
Click to expand...
Click to collapse
just reviewed the Rogers ICS 4.0.4 root from braway's thread, and didnt see it, but still looking..
this is the 3rd user root issue in 24 hours....
something is going on....g
gregsarg said:
Holy cow !!...LOL
Fort Knox note.......:laugh:
Can you list your step sequence ??
Click to expand...
Click to collapse
There you go. I'm running all of this on Windows 8 preview 32 bits. The samsung driver I use is the version 1_3_2200. I think its the most recent.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cwm-touch-i717-120414.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Froid said:
Wasn't there a script installed on the Rogers ics OTA that restores original recovery on boot? That script needs to be deleted after root is achieved and then cwm flashed again for it to stick.
Gubment Cheeze
---------- Post added at 01:59 PM ---------- Previous post was at 01:54 PM ----------
Try flashing cwm but don't tick reboot phone on Odin. Once flash is succesful , use 3 button combo to get into recovery. Flash su zip and reboot. Use file explorer of your choice to remove recovery script. Once that's done flash cwm again and hopefully it will stick.
Gubment Cheeze
Click to expand...
Click to collapse
Might as well try that. Where will I find said recovery script? Thank you
Try mount/system/etc folder. It would start with install.recovery or something similar. It won't let you delete it until you're rooted using es file explorer or root explorer type of app.
Gubment Cheeze
---------- Post added at 02:12 PM ---------- Previous post was at 02:09 PM ----------
I'm going from memory here so you might wanna search for more info and if this is even your issue..
Gubment Cheeze
theinvisiblehand said:
There you go. I'm running all of this on Windows 8 preview 32 bits. The samsung driver I use is the version 1_3_2200. I think its the most recent.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cwm-touch-i717-120414.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
yep...root is good,....
still looking for this script issue....g
If you pull the battery after flashing cwm but before it reboots then going into recovery and flashing superuser you'll bypass the install script.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
gregsarg said:
yep...root is good,....
still looking for this script issue....g
Click to expand...
Click to collapse
thanks a lot
Kinghorsey got it.......g
All right it worked! I pulled the batterie before it rebooted and it worked. Thanks a lot everyone. I'm backing up my system as we speak before I reboot.
Thanks!
Probably should put a " solved" into the thread title...so other users can find this..
King ?
Is this info in the root thread ??
Edit:
He's gone I guess....thanks King.....Great find....g
I don't recall if its in the root thread or not. It seemed to be an issue specific to Canadian Notes and their OTA ICS updates. I'm not sure if it also applies to the AT&T version.
There was a thread about it a while back.
Surest way to bypass the script completely is to flash a copy from samfirmware. The script isn't in that copy and you don't get all the bugginess associated with an OTA update.
I highly recommend that method.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
kinghorsey said:
I don't recall if its in the root thread or not. It seemed to be an issue specific to Canadian Notes and their OTA ICS updates. I'm not sure if it also applies to the AT&T version.
There was a thread about it a while back.
Surest way to bypass the script completely is to flash a copy from samfirmware. The script isn't in that copy and you don't get all the bugginess associated with an OTA update.
I highly recommend that method.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the reply....
Bigjoe has added your "trick " into the super thread, and I think it's a great addition to users here ...(credit given )
I searched the thread completely, and found no mention of that trick .....but it's in the thread header now.
Again ...THANK YOU !!!!...g
Just a heads up to anyone who needs to go this route....pulling the battery will get you into cwm recovery the 1st time. Once the phone is booted up the user will lose their custom recovery and will be replaced by stock 3e recovery.
Gubment Cheeze
I'd love to take credit for this fix but I can't - I only read about it here and didn't discover it on my own. In fact, I never had this problem since I used Odin + samfirmware.com as opposed to OTA updating.
The moral of the story is that even stock.upgrades are better when you are in control.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
---------- Post added at 09:19 PM ---------- Previous post was at 09:17 PM ----------
Froid said:
Just a heads up to anyone who needs to go this route....pulling the battery will get you into cwm recovery the 1st time. Once the phone is booted up the user will lose their custom recovery and will be replaced by stock 3e recovery.
Gubment Cheeze
Click to expand...
Click to collapse
From what I understood this only happened if you didn't pull the battery.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
The script is still in place. Pulling the battery just gets you into recovery to root. Once you're rooted you can delete the script. Then you need to flash cwm again and you should be good to go.
Gubment Cheeze
Hi All,
Ok, here is my problem.
I cannot update my SGS2 and I'm stuck in a problem I can't seem to do anything about.
I (foolishly) downloaded a JB ROM and attempted to install it, but it failed. Since then I have been getting the error:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
These are my details:
Phone: Samsung Galaxy S 2 - UK on Three Network
PC: Windows 7
This is what I have done.
I have tried to connect my phone to Kies, but it will not connect - no matter how many times I try to re-install the driver.
I have downloaded maybe 6 or 7 ROMS that apparently would work in an attempt to "downgrade" to Ice Cream Sandwich. Everytime I try to install using Odin, I get the "FAIL!" message after "NAND Write Start!!" (using the reset to download ROMS on my phone).
I am lost as to what to do, and Odin will not allow any ROM I try to write.
Can anyone please help me? My Nokia N95 is just not up to the job!
Many thanks in advance,
Simon
http://forum.xda-developers.com/showthread.php?t=1457458
Please read all instructions carefully before attempting anything!
"To err is human, to forgive is divine"
Sent from my SGS II
you need to flash a new rom using odin.
just download any rom that can be flashed through odin and read the instructions on any of the many threads on it
immortalneo said:
http://forum.xda-developers.com/showthread.php?t=1457458
Please read all instructions carefully before attempting anything!
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Ok, I've gone over and over this - there doesn't appear to be a .PIT file in any of the downloads, so I can't complete some of the steps mentioned.
Here is a selection of ODIN's responses:
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLB1_I9100GATOKL1_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Can't open the specified file. (Line: 1828)
<OSM> All threads completed. (succeed 0 / failed 1)
I have a feeling I have now totally screwed everything up and there is no-way back.
Can anyone else help me from this nightmare?
Many thanks
Simon
Can you still get into download mode (power..vol down..home key combo)?...if you can, all is not lost...
As for Odin.....
1) Make sure Kies is NOT running....use laptops task manager to kill it lf it is
2) disable any firewalls
3) open Odin as an administrator
4) use the usb cable that came with your phone....don't rely on just one usb port...try them all...
5) put your phone in download mode and connect to laptop via usb....
6) wait for com box in odin screen to change colour and begin (following any/all instructions given TO THE LETTER)
7) leave the option to repartition WELL ALONE
.....And.....
8)......DO NOT play with .pit files unless you have ABSOLUTELY NO OTHER CHOICE.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Thanks Keith ... I will work through your suggestions...
No problems fella.....let us know how you get on...... good luck..
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
---------- Post added at 08:37 PM ---------- Previous post was at 08:26 PM ----------
Also...take a look at this thread...
http://forum.xda-developers.com/showthread.php?t=1449771
It might well be able to help if you are still having no success after retrying the above steps.....
Edit....ahh, I see that immortalneo has already beaten me to it with the link.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Btw.....if it's any use, I've copied my copy of 3 UK's branded 4.0.3 ICS firmware up to dropbox
LINK REMOVED
Feel free to download it if you need it. I've used it on both my and my wifes S2's without issue.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
Btw.....if it's any use, I've copied my copy of 3 UK's branded 4.0.3 ICS firmware up to dropbox.....
http://db.tt/iEoOLHaT
Feel free to download it if you need it. I've used it on both my and my wifes S2's without issue.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Fantastic - thanks Keith ... I'll let you know!
AGGGHHH!
Ok, followed all your advice Keith, and it got further than ever before, but failed at the boot.bin process (see below)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLPI_I9100H3GLP4_I9100NELP4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I feel we may be getting somewhere, but not sure what to do next!
Any ideas?
One more thing......maybe....
Can yiu still get into recovery (CWM)
If you can, try wiping cache, dalvic and data before going into download mode to odin flash the firmware....alternatively try flashing a custom rom through cwm then using Mobile Odin to flash the firmware.....otherwise I'm outta ideas....sorry fella....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
---------- Post added at 04:25 PM ---------- Previous post was at 04:02 PM ----------
Edit......
This next idea is untested and entirely hypothetical.
As a starting point, you need a working rooted kernel. From what you said in your OP, I *think* you're running JB (sort of).......
SOMEBODY PLEASE CORRECT ME IF THE FOLLOWING IS WRONG.........
1) download an odin flashable JB compatiable PhilZ modified stock kernel with CWM and flash in Odin
2) download any recent CM10.1 cusROM + GApps
3) use the newly installed CWM to flash the cusROM & GApps
4) wipe cache, dalvic and data and reboot.....hopefully with success........
Don't try this until someone else has commented as to the sanity of this idea........
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
One more thing......maybe....
Can yiu still get into recovery (CWM)
If you can, try wiping cache, dalvic and data before going into download mode to odin flash the firmware....alternatively try flashing a custom rom through cwm then using Mobile Odin to flash the firmware.....otherwise I'm outta ideas....sorry fella....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
---------- Post added at 04:25 PM ---------- Previous post was at 04:02 PM ----------
Edit......
This next idea is untested and entirely hypothetical.
As a starting point, you need a working rooted kernel. From what you said in your OP, I *think* you're running JB (sort of).......
SOMEBODY PLEASE CORRECT ME IF THE FOLLOWING IS WRONG.........
1) download an odin flashable JB compatiable PhilZ modified stock kernel with CWM and flash in Odin
2) download any recent CM10.1 cusROM + GApps
3) use the newly installed CWM to flash the cusROM & GApps
4) wipe cache, dalvic and data and reboot.....hopefully with success........
Don't try this until someone else has commented as to the sanity of this idea........
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Thanks Keith ... I appreciate you having spent time on this...
The only option I have is with Odin as I cannot get into any recovery mode. I also do/did not have CWM installed on the phone.
I can also get to the "Firmware upgrade encontered an issue ...." message on boot, but I cannot connect my phone to Kies. It just wont recognise it (I did uninstall it anyway!).
It *starts* to flash, as when I look on the screen, the progress bar starts to move, but after a very short time it then "FAILS!"...
I will hang fire until someone looks into your other idea before trying anything else.
EDIT: It was a JB ROM that seems to have gone wrong, but it never actually ran so now trying to downgrade - even tried Gingerbread ROM which failed too.
Also just thought I'd mention that the "CUSTOM BINARY DOWNLOADS:" now shows "YES (11 counts)" which has gone up... Don't know if that is significant, or helpful!
Just a quick question before I dash out...
Do I need to have my SIM installed when I flash? I have it in another phone at the moment as its my work number, but have not even thought I might need it in...
ratzz said:
Just a quick question before I dash out...
Do I need to have my SIM installed when I flash? I have it in another phone at the moment as its my work number, but have not even thought I might need it in...
Click to expand...
Click to collapse
No, u don't need a SIM.
"To err is human, to forgive is divine"
Sent from my SGS II
Go pay a friend a visit, ask him/her to use their computer (Windows), get 3 samsung cables fron where ever, download 3 different odin versions, install latest kies, reboot, kill all 4 kies applications. Do the odin thing.
Just to make sure, get a couple of Custom into a flash drive, along with siyah v5 and v6 from Gokhnanmoral.com (I9100 right?).
Flash only code, phone and csc.
Forget about the existance of pit files for now.
Sent from the little guy
Gastonw....can you comment on my "hypothetical idea" comment? Does it have ANY merit?
Is there even a *possibility* it could help?
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
@keithross39
I think it would work, as long as the OP can flash the CWM containing kernel via Odin!
"To err is human, to forgive is divine"
Sent from my SGS II
Keith, the man who got a Ph.D in Mobile Odin via xda
I always read your posts on workarounds and step-by-step guides, you truely are into android, keep it up.
I actually overlooked what you just posted because I was thinking on suggesting the same thing with a different kernel, so yeah, what you are suggesting can work, because it did in the ICS era.
Whenever you get stucked at nand you could flash a custom kernel (.tar) so it'll allow you to get to CWM. Once you get there, you can flash whatever you want.
I mentioned siyah in case he was on ICS ( siyah v5 ) or on jb ( siyag v6), Philz indeed is a better option for all jb related ROM.
Sent from the little guy
Lol....thanks for your vote of confidence Gastonw....it's been a steep learning curve.....got my first smartphone 15 months ago, didn't start modifying it until 9 months ago....and since then I've modded 2 other phones (3 in total) and a Tab.......if you find something interesting, learning becomes enjoyment....but I'm still far far away from PhD level....lol
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
Lol....thanks for your vote of confidence Gastonw....it's been a steep learning curve.....got my first smartphone 15 months ago, didn't start modifying it until 9 months ago....and since then I've modded 2 other phones (3 in total) and a Tab.......if you find something interesting, learning becomes enjoyment....but I'm still far far away from PhD level....lol
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Sounded cool, didn't it?
Sent from the little guy
Hello.
So, I will explain what i did first.
Last night, I was trying to root my note 2, using following link.
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
(it was the first link from google search, stupid me...)
Anyway, after following instruction on that link, my phone got stuck in a boot loop. (ie. when i turn on, the samsung screen comes on, then verizon LTE and then back to samsung and so on.)
So, I tried to fix using following links
http://galaxynote2root.com/galaxy-n...ootunbrick-galaxy-note-2-with-stock-firmware/
http://forum.xda-developers.com/showthread.php?t=2272066&page=18
http://forums.androidcentral.com/ve...-do-i-restore-sboot-bin-causes-odin-fail.html
Samsung Kies
and still can't fix it.
Since you need more than these, here are some results from running odin, etc.
When I run odin with PDA file, I get following
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> cache.img
<ID:0/008> hidden.img
<ID:0/008> modem.bin
<ID:0/008> param.bin
<ID:0/008> recovery.img
<ID:0/008> sboot.bin
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I power up the machine, I get following message.
"Firmware upgrade encountered an issue. Please select recovery mode in Kies &try again"
However, when I connect with Kies, Kies won't recognize my phone, and cannot go into recovery.
When I try CASUAL to unbrick, CASUAL doesn't connect. Also, when I try the download mode (via double-clicking the "DISCONNECTED"), it still can't recognize.
On "My computer", I do not see the I drive (my phone), so I don't think it is connecting....?
I have tried deleting driver and installing and Zadig program as well.
Can anyone help me with going back to original condition?
I would really appreciate and more than willing to pay for your effort.
Please help me.
Let me know, if you need more results.
http://forum.xda-developers.com/showthread.php?p=39299305
Please read the stickies. There's your answer right at the top of this page. Also, I think you learned, but I highly recommend you stay with xda for guides. As you can see these sites just repost xda info and a lot if times it's incorrect or out of date and result in a brick.
Or you could have skimmed and saw where this was addressed just yesterday.
http://forum.xda-developers.com/showthread.php?p=37255435
Sent from my SGH-T889 using xda app-developers app
Did you include the pit file? That may be the problem. Also make sure you right click odin and run as administrator.
Sent from my SCH-I605 using Tapatalk 2
Lodingi it's not the pit. It's a locked bootloader and the op trying to write sboot.bin (which is blacklisted on the newer updates. That's why we use alternate restore because it doesn't contain sboot.bin so it will pass on Odin.
Edit to fix your name, sorry
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Lodingi it's not the pit. It's a locked bootloader and the op trying to write sboot.bin (which is blacklisted on the newer updates. That's why we use alternate restore because it doesn't contain sboot.bin so it will pass on Odin.
Edit to fix your name, sorry
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Gotcha. Thanks.
Sent from my SCH-I605 using Tapatalk 2
Lodingi said:
Gotcha. Thanks.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Ya man, i typed lodingo at first, I guess I edited it before you even saw.
Sent from my SGH-T889 using xda app-developers app
** Thank you to JGeigerM, hexitnow, and joderme for the solution.
** Solver was paid.
** I leave a condensed version in case someone is frantically googling like I was.
[Background]
I downloaded VRUAME7 for my Galaxy S4.
I then tried to flash Blue Toggles apk.
I then began getting the message "Unfortunately, System UI has stopped".
I decided to use Odin to attempt to flash MDK firmware, which FAILED as you will see below:
**ODIN LOG**:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NON-HLOS.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
**PHONE LOG**
START [224, 1448]
SW REV. CHECK FAIL : fused : 3, Binary : 1
**SOLUTION**:
(1) Verizon GS4 I545 VRUAME7 Stock Image = http://invisiblek.org/sch-i545/SCH-I...3crny1_fac.zip
(2) Unzip that file when downloaded
(3) Run Odin 3.07 (latest as of posting) as administrator
(4) Select .MD5 file that you unzipped as a PDA
(5) Hit Start once it loads
Here is the link to the stock ME7 image... http://forum.xda-developers.com/showthread.php?t=2357235
Try this one and see if it works.
You were trying to flash the mdk firmware which you cant flash back to once on me7. the stock me7 file is at this link
http://forum.xda-developers.com/showthread.php?p=43420116
The mods for me7 need to be made for it most of the time I believe framework is quite a bit different from mdk which is why you got yourself a soft brick. Im gonna put this out there just in case yoh were looking into it but youre unable to flash a custom recovery on me7 or else youll get another soft brick of sorts. There are people working on it tho.
Sent from my SCH-I545 using Tapatalk 2
EDIT: Solved
I'm glad I could help. XDA forum stalking has become my new habit so I saw it when you posted :good:
EDIT: Solved
Yeah that was a bad download. Another user posted the same thing. After he redownloaded it he was good to go.
Sent from my SCH-I545 using Tapatalk 2
It lives!
Thank you all so much again.
A mod can switch this to solved.
I'm trying to contact JGeigerM for payment.
Sorry, hexitnow, you were 2 minutes later than his original link.
m0bstr said:
It lives!
Thank you all so much again.
A mod can switch this to solved.
I'm trying to contact JGeigerM for payment.
Sorry, hexitnow, you were 2 minutes later than his original link.
Click to expand...
Click to collapse
I wouldnt of accepted anything for payment so im not worried bout it. You can edit your post and add solved to the title. Glad you got it going though.
Sent from my SCH-I545 using Tapatalk 2
It wasn't much help to send you just a link to an image.
Sent from my SCH-I535 using Tapatalk 4
I rooted on VRUAME7 I am now trying to do a reset/restore. When I did a factory reset in the system, it rebooted and is now stuck on a yellow exclamation mark and says:
"Firmware upgrade encountered an issue. Please select recover mode in Kies & try again."
I downloaded the Stock Restore and followed a guide to restore using Odin.
Odin Failed and says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says:
Start [224,1440]
SW REV. CHECK FAIL: FOUND: 3, Binary: 1
Questions:
1.)How to I charge it (connecting to charger after battery pull immediately starts the phone and pulls up the Yellow Exclamation.)?
2.)How do I unroot and restore this back to factory?
-----------------------------------------------------------------
dreamliner330 said:
FIXED!
I flashed this ME7 image via Odin found on this thread.
Thanks!
Click to expand...
Click to collapse
I have a similar problem.
I rooted on VRUAME7 and get this message
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
on the phone it says:
Start [224,1440]
SW REV. CHECK FAIL: FOUND: 3, Binary: 1
I also want to restore it to Factory?
Thanks
JeppeO
Did you guys uninstall supersu first?
Sent from my SCH-I545 using xda app-developers app
Surge1223 said:
Did you guys uninstall supersu first?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
No. I cant get into the system now either.
FIXED!
I flashed this ME7 image via Odin found on this thread.
Thanks!
That site was using the mdk stock image it didnt provide the me7 stock image thats why it failed.
Sent from my SCH-I545 using xda app-developers app
Surge1223 said:
That site was using the mdk stock image it didnt provide the me7 stock image thats why it failed.
Click to expand...
Click to collapse
Yeah, thats what I realized after I saw the file had 'MDK' in the name, unfortunately, I haven't found a 'restore' thread or post that references a ME7 image. Hopefully, others that have the same issue will find this thread.
dreamliner330 said:
FIXED!
I flashed this ME7 image via Odin found on this thread.
Thanks!
Click to expand...
Click to collapse
That did it for me 2. Thanks Dreamliner330
dreamliner330 said:
FIXED!
I flashed this ME7 image via Odin found on this thread.
Thanks!
Click to expand...
Click to collapse
Did you unzip it first, or just navigate from ODIN (PDA section?) to the zip file and use that?
jesssiii said:
Did you unzip it first, or just navigate from ODIN (PDA section?) to the zip file and use that?
Click to expand...
Click to collapse
Keep as zip, select in PDA section.
Thanks!
dreamliner330 said:
FIXED!
I flashed this ME7 image via Odin found on this thread.
Thanks!
Click to expand...
Click to collapse
Thank you! You saved my bacon!
Mine rebooted OK, but still shows "Custom" and and unlocked padlock when booting. Will this raise a few eyebrows if I return it?
mattevt said:
Mine rebooted OK, but still shows "Custom" and and unlocked padlock when booting. Will this raise a few eyebrows if I return it?
Click to expand...
Click to collapse
It can if they boot it. If you unrooted and are back to a stock rom reboot it a few times and it should go away.
Sent from my SCH-I545 using Tapatalk 2
Is there a way to UnRoot without using a PC? Im currently at work and now my phone is not getting any signal easily, and I want to unroot but do not have a cable and cant install anything on this PC. I don't want to be without signal before I drive home, just in case.
I tried leaving it as a zip but can't find it for PDA. I tried extracting but it says it's corrupted. Please Help! :crying:
txstgoose14 said:
I tried leaving it as a zip but can't find it for PDA. I tried extracting but it says it's corrupted. Please Help! :crying:
Click to expand...
Click to collapse
There is no pda version you use the pda option in odin. You could of got a corrupted download I so I would try downloading it again.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
There is no pda version you use the pda option in odin. You could of got a corrupted download I so I would try downloading it again.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
This is my 3rd time re-downloading and it still says that it is corrupted, when I try to extract.
txstgoose14 said:
This is my 3rd time re-downloading and it still says that it is corrupted, when I try to extract.
Click to expand...
Click to collapse
Get an md5 verifier and verify if the download is good or not. Thats the best way to do it. Which file are you downloading, some dont need to be extracted if I remember right.
Sent from my SCH-I545 using Tapatalk 2
Just checked the md5 and under checksum value it gave me this (891ff0e944bbd2cc3ebbd381d5afa59d)
edit: not to sure if it means that it checks out or not, but ODIN says that the hash value is invalid
---------- Post added at 05:20 PM ---------- Previous post was at 05:12 PM ----------
dreamliner330 said:
FIXED!
I flashed this ME7 image via Odin found on this thread.
Thanks!
Click to expand...
Click to collapse
I'm downloading this me7
txstgoose14 said:
Just checked the md5 and under checksum value it gave me this (891ff0e944bbd2cc3ebbd381d5afa59d)
edit: not to sure if it means that it checks out or not, but ODIN says that the hash value is invalid
---------- Post added at 05:20 PM ---------- Previous post was at 05:12 PM ----------
I'm downloading this me7
Click to expand...
Click to collapse
Yeah youre getting corrupted downloads. The correct md5 is posted here
http://forum.xda-developers.com/showthread.php?p=43420116
Keep downloading it until it matches.
Sent from my SCH-I545 using Tapatalk 2