Hello,
I have a Verizon Samsung Galaxy S4 which came stock running 5.0.1 lollipop. I managed to root the phone with KingRoot and flashed a custom rom with FlashFire with no issues at all. My main goal was to get Xposed Framework installed. I was able to flash the Xposed sdk-21 arm file with FlashFire and it seemed to install properly but I couldn't ever get the Xposed app to install properly afterwards. So I then decided to uninstall the Xposed sdk-21 arm with a Xposed uninstaller file from the same source which had to be flashed and that's when all the trouble began.
My phone rebooted and got stuck at the Samsung splash screen. I had tried rebooting several times. Firstly I went into stock recovery and tried wiping cache partition to no avail. Secondly I tried to do a factory restore via stock recovery and that was a no go. Still stuck at Samsung splash screen upon boot up attempt. I then decided it was probable best if I had just started from scratch. So I downloaded the stock I545VRUGOC1 rom along with the Pit file and tried flashing that with Odin v3.09. That was a huge fail. Odin went through the process all the way to about 90-95% and wouldn't go any further. I had to keep pressing start after many failed attempts to get to that point.
Here's what I get from Odin now:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUGOC1_I545VZWGOC1_CL4584173_QB451701 6_REV06_user_low_ship_MULTI_CERT.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I can no longer get into stock recovery on the phone at this point. I get this message when trying to enter recovery:
Software Update Failed
Your device didn't update
successfully. Use the Verizon
Software Repair Assistant on a
computer to repair your device and
complete the update.
I CAN get into download mode at the very least. Maybe there's still hope? I'm about cross-eyed and at wits ends trying to find a working solution. Any and all help is much appreciated.
Thanks
Okay, so I came across a Brick Fix .tar (boot disc image) file that I was able to flash successfully with Odin 3.09. I can now get back into system recovery. I still cannot get the phone to boot normally. It only goes to the Samsung Galaxy S4 splash screen. I'm currently trying to figure out if I am able to do an ADB sideload.
Can anyone point me in the right direction to the proper adb files or programs?
First, redownload it, unless you confirmed the md5s...
Second, try different USB ports.
Third, a different USB cable... Some work, some don't...
The OEM samsung cable works best, but I know for sure my monoprice cable for 2 bucks works nicely... Odin is reaaalllly picky..
Really, if it fails, those are the three major things 99% of people have problems with.
XxD34THxX said:
First, redownload it, unless you confirmed the md5s...
Second, try different USB ports.
Third, a different USB cable... Some work, some don't...
The OEM samsung cable works best, but I know for sure my monoprice cable for 2 bucks works nicely... Odin is reaaalllly picky..
Really, if it fails, those are the three major things 99% of people have problems with.
Click to expand...
Click to collapse
Holy wow! First off I just want to say thanks to you for chiming in! Apparently Odin didn't like the stock cable that came with the phone. I used my old Motorola Droid Bionic usb cable, switched usb ports, and flashed the stock 5.0.1 rom with Odin v1.85. The best I could do with Odin v3.09 was about 75% complete before it failed. I've been working on this literally all day (off work today) google search after google search . Thank you so much! :good:
Btw I flashed the stock rom I found here http://forum.xda-developers.com/galaxy-s4-verizon/development/odin-5-0-1-lollipop-oc1-t3174850
Huh. Odin prefers the OEM cord, but whatever works works.
I don't know what it is but I also used my droid bionic cable to charge my galaxy s3 because it works a heck of a lot better than the stock cable. I bought my galaxy s4 from ebay as a manufacturer refurbished phone so that my have something to do with the cable provided. My phone is black but it came with all white oem accessories. I ordered my galaxy s3 from ebay brand new a few years back and it is black and came with a black oem charger. Not sure if any of that makes a difference or not but they are Samsung brand cables. I think Motorola may have better charger/data cables imo.
Related
Hello,
Newbie here... I have followed this forum for three days trying to get my Note II Verizon to boot any ROM. I am only able to get it into Odin Download mode (never been able to get the System Restore Menu). Not sure what this device was originally flashed with but I can't get any bootrom to install.
I have tried the first steps and download the files poseted on this post http://forum.xda-developers.com/showthread.php?t=2043636 and get the folllowing failure:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BootloaderBaseline2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> tz.img
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now gives the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only successful Rom I have partial success with is: KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.
Odin 3.185 will install this ROM successfully with the PIT. Not the phone will not boot and flashes the Galaxy Note II then turns off. It will only allow me to go back into Bootloader Mode but has never allowed me to get into recovery and wipe the phone. Boot Load screen shows everything stock except the "SYSTEM STATUS: Custom". Since I do not know what ROM was originally installed I am stuck on this one and insight would greatly appreciated. I have also tried other Odin versions including 3.07.
Thank you!
jvaldez33 said:
Hello,
Newbie here... I have followed this forum for three days trying to get my Note II Verizon to boot any ROM. I am only able to get it into Odin Download mode (never been able to get the System Restore Menu). Not sure what this device was originally flashed with but I can't get any bootrom to install.
I have tried the first steps and download the files poseted on this post http://forum.xda-developers.com/showthread.php?t=2043636 and get the folllowing failure:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BootloaderBaseline2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> tz.img
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone now gives the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only successful Rom I have partial success with is: KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.
Odin 185 will install this rom successfully with the PIT. Not the phone will not boot and flashes the Galaxy Note II then turns off. It will only allow me to go back into Bootloader Mode but has never allowed me to get into recovery and wipe the phone. Boot Load screen shows everything stock except the "SYSTEM STATUS: Custom". Since I do not know what ROM was originally installed I am stuck on this one and insight would greatly appreciated.
Thank you!
Click to expand...
Click to collapse
Think your version of Odin is too old. try this
https://docs.google.com/file/d/0BwO2K6_pgq39ejFubU43Nkprb2c/edit
See if 307 works better for you.
Note II Won't boot.
dragonstalker said:
Think your version of Odin is too old. try this
https://docs.google.com/file/d/0BwO2K6_pgq39ejFubU43Nkprb2c/edit
See if 307 works better for you.
Click to expand...
Click to collapse
Thank you for the reply. I made a typo and have tried Odin 3.185 and 3.07. Can't seem to get any of them to work. I have contacted Samsung and my phone is under warranty but would like to get the "CUSTOM" off the SYSTEM STATUS to avoid issues with the warranty.
Warranty costs if phone has been rooted
jvaldez33 said:
Thank you for the reply. I made a typo and have tried Odin 3.185 and 3.07. Can't seem to get any of them to work. I have contacted Samsung and my phone is under warranty but would like to get the "CUSTOM" off the SYSTEM STATUS to avoid issues with the warranty.
Click to expand...
Click to collapse
Hello,
Can can anyone share what the Out of Warranty costs are if the Verizon Note II is sent in with a Custom Rom and Samsung doesn't honor the warranty?
jvaldez33 said:
Hello,
Can can anyone share what the Out of Warranty costs are if the Verizon Note II is sent in with a Custom Rom and Samsung doesn't honor the warranty?
Click to expand...
Click to collapse
You will be charged the full price of the device. Just keep trying to fix the issue. There has to be something you aren't doing right. As long as you can get into the boot loader you are in okay shape. Just go back through the instructions and follow them as closely as you possibly can.
Sent from my Nexus 10 using Tapatalk 4
miketoasty said:
You will be charged the full price of the device. Just keep trying to fix the issue. There has to be something you aren't doing right. As long as you can get into the boot loader you are in okay shape. Just go back through the instructions and follow them as closely as you possibly can.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
In my experience no matter how far gone you think your device is, if you can get into download mode and Odin recognizes it you are OK. I am sure there are circumstances where you can't recover even if you are in that position, but I have never heard of any. Agree with miketoasty, read the instructions carefully and then read them again. Be sure you have the correct files and a decently charged battery. And make sure your USB cable is good.
Sent from my GT-P3110 using xda app-developers app
Update on events
mikelikesbikes said:
In my experience no matter how far gone you think your device is, if you can get into download mode and Odin recognizes it you are OK. I am sure there are circumstances where you can't recover even if you are in that position, but I have never heard of any. Agree with miketoasty, read the instructions carefully and then read them again. Be sure you have the correct files and a decently charged battery. And make sure your USB cable is good.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
I have been in the IT business for nearly 25 years and have seen many problems resolved if you have the time and desire to put forth the efforts to investigate the problem every day with a clear head. With that being said I for some unknown ADD moment and decided I wanted to troubleshoot my sons girlfriend's Note II that was having problems. Now here I am wrestling with a problem like a drug addict looking for their "next fix". I am very stubborn and extremely capable of diagnosing hardware and software problems but this one truly has me stumped!
With this being a problem I decided to purchase another Note II off EBay to experiment with and was listed with similar problems, Red Light and wouldn't boot.. I figured for $125 the worst that could happen is I could disassemble it and part out the LCD/Digitizer and recuperate my investment. There are some problems I like researching and resolving and this is one. I personally believe the problems on both Note II's may both related to the charging board based on the information on the following post on another forum: http://forum.xda-developers.com/showthread.php?p=45678812#post45678812. I will elaborate a little more shortly.
Let's go over my three day 50 hour marathon. Here is the only download that successfully downloads but the phone will only splash the "GALAXY NOTE II" screen and turn off after a successful install. I have downloaded Odin 3.185 and 3.07 and get the same results:
sch-i605-16gb.pit
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
Unless the problem resides on my laptop I think I have eliminated the issue of having a good cable(s) by using official Samsung cables, NEW RocketFish cables and they all seem to work fine for viewing and transferring files via USB. I also have an external battery charger and can guarantee an excellent charge on the battery(s). The current files I was recommended to use came from a single Zipped file: GalaxyNote2UnlockVerizon. Please let me know if there are a different set of files I should be using?
Unless I have downloaded the wrong files? I have attempted to install the following bootloader with Odin versions 3.07, 3.13 and 3.185 and they all fail: BootloaderBaseline2.tar.md5. All I know at this moment i am stuck at a point that I have the Note II in a state that will not allow me to boot.
Lets discuss some hardware issues that I need to explore a little further. Since I have a spare phone to test with I thought I would swap logic/motherboards and see if I had any different results. Unfortunately they are exactly the same on both Note II's. Now comes an interesting issue I stumbled upon. When I VERY CAREFULLY reassembled it on an ESD Mat I somehow dislodged or did not securely fasten the display cable to the logic board and when the power was pressed the phone seemed to start booting but there was no display. The sound and the blue light came on normally. I had hoped the original ROM was now installing. I powered off the phone, removed the battery and disassembled it to discover my mishap, so I reconnected the display cable and reassembled the phone only to see the original problem was still present.
Has anyone else had a charging port issue that caused similar problems? I was planning on ordering a new charging port off Amazon today just to try. Any additional information would be greatly appreciated.
Thank all of you that contribute to this site. It is amazing how many problems can be resolved when great minds are put together.
The red light and wont boot indicates a hard brick...more then likely the device had something flashed to it that corrupted the emmc. Moral of the story...its now a paper weight.
No Red Light
droidstyle said:
The red light and wont boot indicates a hard brick...more then likely the device had something flashed to it that corrupted the emmc. Moral of the story...its now a paper weight.
Click to expand...
Click to collapse
It doesn't have a red light. I can get it into the download mode and it will allow the ROM update through Odin but it will only splash the "GALAXY NOTE II" screen and power off.
jvaldez33 said:
It doesn't have a red light. I can get it into the download mode and it will allow the ROM update through Odin but it will only splash the "GALAXY NOTE II" screen and power off.
Click to expand...
Click to collapse
look for a n7100 tar, or maybe "I think, can't remember" there was a stock tar in the I605 mega roll thread somewhere. flash one of them. Try not to use the kies tar as i've had problems with them being corrupted before. Know you've tried both the methods already. Just a suggestion in case you have not. Also check and make sure you have the right pda file.
GS II i9100
Note: Warranty is already expired
Before I write anything further, I have been trying to get the most I can out of this thread: http://forum.xda-developers.com/showthread.php?t=1457458
Sadly, I can't seem to wrap my head around this problem, so here goes:
Yesterday I've found out, that the new CM11 came out. Of course I went off to download it, put it in my phone and started to install it through recovery (I had siyah at that time). Well, it failed, must've been corrupt or something, since I got the error status 7. Anyways, while exiting the install screen, siyah asked me, if I want to repair something, because something may have gotten corrupt (Sorry, can't remember the exact thing). Being the sloppy person I am, I clicked yes.
Five minutes later, after going back to stock firmware, because apparently during the install something did go corrupt, and the phone wouldn't boot, only play the boot sound, I've read, that I need the newest CWM for CM11 to work.
Another five minutes later I'm staring at this:
<ID:0/006> 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/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I've tried changing computers, kicking KIES out through the window, using different USB slots and cables, but to no avail. It just keeps throwing this error at me every time I try to install anything through Odin. The strangest part is, though, that the phone is working perfectly fine.
What could be the problem, and if it is possible, how do I fix it?
Another quick note would be my counter in the download screen of my SII. It's 12 (yeah, I know, I kept forgetting about it, but now, since I'm unable to install anything through Odin, I can't even root the phone and reset the damn thing)
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
andrewwright said:
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
Click to expand...
Click to collapse
And apparently, this is now happening:
Baseband version - XXMS2
Build - XWLSS
I think I may have messed it up a little...
Please close the thread
This thread can be closed.
Should anyone need this:
After losing patience spending hours on the phone I have decided to JTAG it... Ant it worked. The phone is running like a charm now.
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_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> 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> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Bump*
What makes this issue differ from others i've read on these forums, is this:
Akiiras said:
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Any theories?
As much as i hate bumping, i'm feeling kind of responsible to try and fix it. Hope someone got a clue on what might be wrong. Thanks
"I bet you 10 buck you'll get your answer here within a couple days" -a friend said, well, in norwegian though.
I guess a week later and no response means that i've at least earned 10 buck! ^^
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Akiiras said:
Guess i can give it one more shot here before i send it to a repair guy.
*bump*
Click to expand...
Click to collapse
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
LS.xD said:
Are you sure about the right region when choosing a firmware? Did you also try Odin 1.85? Have you tried flash a custom recovery via Odin and flash a rom manually?
Click to expand...
Click to collapse
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Akiiras said:
Hi, and thanks for the reply!
I am pretty sure i got the right firmware region. At least, the only region that covered my location (norway) that i could find, was nordic.
I have not tried Odin v1.85 or manually. I guess i can find a guide on how to do it manually here somewhere, but i'll go for a shot with the older version of Odin right away.
Thanks!
Click to expand...
Click to collapse
BTW there are 4 different versions for nodric countries --> LINK
Odin3 v1.85 didn't work. Well, in the sense that it probably does a job well done and says everything went well, but the phone wont nudge past boot screen.
I'll see if i can learn how to do it manually and come back with the result.
Edit:
LS.xD said:
BTW there are 4 different versions for nodric countries --> LINK
Click to expand...
Click to collapse
Oh, thanks! I couldnt find it at sammobile myself, so i found it somewhere else. This could be it!
any developments?
I Have the Same Problem
I Have the same problem please anyone help me!!!!!
SOLUTION
Akiiras said:
Hello
For a couple of weeks now, i've been trying to fix this phone for a friend who studies as an artist. She wanted the Galaxy Beam for presentations and bought one used as they seemingly ain't to be found in the stores any longer.
Originally, the firmware ends at 2.3.6 on this brand, but this one was rooted to be fit with 4.1.2.
The phone bugged and hung in weird ways, so i thought to follow the steps into downgrading it to stock rom for her and see if that would help.
I am no expert, but since i have successfully rooted several phones and tablets earlier with no issues (its pretty straight forward when it works, right), i felt up for the tast.
I have spent a lot of time googling the last couple weeks, and reading a lot of solutions here on these forums, but i can't seem to find this ecact problem, so here goes.
Samsung Galaxy Beam GT.I8530
Odin3 v3.07
Windows 7 and 8 fully updated (tried both)
No matter which Android version i chose, it ends up at the same spot. Stuck at logo screen after first boot.
I have tried both with and without a PIT file, same result.
This last try was with a PIT and Android 4.1.2. (i understand that PIT is not nessessary, as it should be baked within the PDA if it's a single file, but what won't you try eventually, right?)
Load Odin, admin rights
Boot phone in download mode
Insert USB
-->
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8530DXLJ1_I8530OLBLJ1_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> 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> cache.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img.md5
<ID:0/003> kernel.bin.md5
<ID:0/003> modem.bin.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
- here, the phone reboots and loads to logo screen *
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
- from here the phone wont nudge from the logo screen. can reboot, nothing new happens.
No other functions work, other than:
- volume down+home+power (download mode)
- power (boots to logo screen)
Thanks for reading! Hope someone feels up for the task
Edit: It might be vital information that the phone will uncharge the battery at logo screen eventually, even when connected to a computer. (5v output) But i believe this is common somehow.
Also, if i try and shut down the phone, it will reboot into a frozen "star icon".
Click to expand...
Click to collapse
I have The solution For that remove your battery and charge battery by use of another working mobile or battery charger box
after charging you do the flashing using android 4.1.2
it successfully works on my mobile
the problem is battery is low so that at the time of flashing it turned off ....so fill the battery and use......
I've managed to screw the pooch and got the Yellow Triangle of Death for my efforts. This is a VZW Note 2 sch-i605 that had(has?) a rooted 4.4.2. I tried to get TWRP installed and... yellow triangle. OK, the bootloader's locked up tight.
How do I get back to 4.3? Odin works - that is, it sees the phone, tries to do a NAND write and... party over.
Would trying to get an AOSP ROM loaded help? Can I get Odin to do that? I have the SDK but I guess sideloading is a loss without recovery.
This is what a failure looks like on Odin 3.10.7:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what rev. of Odin, TWRP, CWM, or even I605VRUAND3_I605VZWAND3_I605VRUAND3_HOME.tar.md5 I use... FAIL. And it's always that NAND write.
What options do I have?
I'm happy to say I beat this problem with a stick. The process was brutally ugly but it worked out. It starts with this video from Root Junky: https://www.youtube.com/watch?v=4qtbEevn1VA. But things didn't quite work out. At the very end, the process tanked with, on the phone, a message saying "bad magic string". The good news is I didn't get the VZW Yellow Triangle of Death. I got the Kies or some Samsung utilities Yellow Triangle of Death. Out of simple desperation, I tried the same process seen in the video but... I used the ND7 file instead of the MC3 file. I kept the 16G.pit file (maybe I didn't need to repartition, maybe I did). And the who process passed, front to back. Even more amazing, my data is intact and so are the home screens. I did, however, lose root. I know how to root under ND7, so I'll do that next. And...
Root Checker gave me a scare and said the phone wasn't rooted. I had to install SuperSU first. The only thing this particular rooting process still doesn't do is install SuperSU and BusyBox. I can install them via Play Store, so it's not a real problem.
The procedure used to root at the end:
Originally Posted by NetworkingPro (*)
Everyone, please use this .zip from now on. Please test, and let me know how it goes. I have simplifed the root be a single click root method.
Steps:
Download and unzip file.
Connect phone, ensure usb debugging is on, and device is authorized.
Double click GhettoRoot.bat
Download - Attachment 2922670
In full disclosure I have no idea where the source for this came from, I just made it pretty, and tried to make it super easy. Credit goes to 25yvdgpo06 for finding it. This root very well may work any many other devices, including other Samsung devices. Looking at the source I dont see anything that should hurt another device. Worst case scenario it simply doesn't root it. Please let us know if you try another device with success.
Click to expand...
Click to collapse
My device is Samsung Galaxy Tab3, WiFi, 7.0, 8GB, 32GB Flash disc storage, OS is Android version 4.4.2 Jelly Bean.
A few weeks ago I installed F-secure on this device and all seem to work just fine.
That is until last week when I booted the tablet after being off for a few days, and after logon I noticed this event start to pop up saying 'program has stopped' over and over again.
Then followed by an unplanned reboot.
I tried to disable that AV program but due to those event popups there's just not enough time to stop or disable the AV program in time until the next reboot.
Tablet has been rooted by Kingoroot and that also worked well all the time.
So I thought to find me a proper stock ROM for my Tab3 device on the internet and upload it as '*Home.tar.md5' through Odin (latest version) onto my Tab3.
Unfortunately it then fails verification when I start installation, so I then renamed it to '*Home_CSC.md5' and then it passes verification, but install took only a few seconds.
That's not good.
So now I think that the stock ROM provided, was not the correct one for my device, because even though the ROM specs are correct, the hardware specs differ, as it lacks 3G, so the chipset differs to begin with.
Also when viewing the log I noticed a problem with PIT, it says 'Get PIT for mapping..' which means there's a problem with PIT however not yet fatal, because it still boot up.
If I have to reinstall by using the proper stock ROM, then so be it, but I'd rather think of repairing in some way if possible.
But I'm not sure how to do that.
When I need to reinstall, I'll need the proper stock ROM 'PHN-T210XXBNI1_T210PHNBNI1' but for 'Samsung Galaxy Tab3, WiFi only, 7.0, 8GB, 32GB Flash disc, Android version 4.4.2 Jelly Bean'.
So far, I haven't been able to find the proper stock ROM, can anyone help?
xdausernl said:
My device is Samsung Galaxy Tab3, WiFi, 7.0, 8GB, 32GB Flash disc storage, OS is Android version 4.4.2 Jelly Bean.
A few weeks ago I installed F-secure on this device and all seem to work just fine.
That is until last week when I booted the tablet after being off for a few days, and after logon I noticed this event start to pop up saying 'program has stopped' over and over again.
Then followed by an unplanned reboot.
I tried to disable that AV program but due to those event popups there's just not enough time to stop or disable the AV program in time until the next reboot.
Tablet has been rooted by Kingoroot and that also worked well all the time.
So I thought to find me a proper stock ROM for my Tab3 device on the internet and upload it as '*Home.tar.md5' through Odin (latest version) onto my Tab3.
Unfortunately it then fails verification when I start installation, so I then renamed it to '*Home_CSC.md5' and then it passes verification, but install took only a few seconds.
That's not good.
So now I think that the stock ROM provided, was not the correct one for my device, because even though the ROM specs are correct, the hardware specs differ, as it lacks 3G, so the chipset differs to begin with.
Also when viewing the log I noticed a problem with PIT, it says 'Get PIT for mapping..' which means there's a problem with PIT however not yet fatal, because it still boot up.
If I have to reinstall by using the proper stock ROM, then so be it, but I'd rather think of repairing in some way if possible.
But I'm not sure how to do that.
When I need to reinstall, I'll need the proper stock ROM 'PHN-T210XXBNI1_T210PHNBNI1' but for 'Samsung Galaxy Tab3, WiFi only, 7.0, 8GB, 32GB Flash disc, Android version 4.4.2 Jelly Bean'.
So far, I haven't been able to find the proper stock ROM, can anyone help?
Click to expand...
Click to collapse
We have a whole section for this device as well as some modded stock ROMs, Kernels, Recoveries, etc.
https://r.tapatalk.com/shareLink?ur...&share_sfid=2401&share_fid=3793&share_type=sf
Sent from my LG-Q710AL using Tapatalk
Why reflashing stock ROM with Odin for SM-T210 Tab 3 WiFi repeatadly fail?
xdausernl said:
My device is Samsung Galaxy Tab3, WiFi, 7.0, 8GB, 32GB Flash disc storage, OS is Android version 4.4.2 Jelly Bean.
A few weeks ago I installed F-secure on this device and all seem to work just fine.
That is until last week when I booted the tablet after being off for a few days, and after logon I noticed this event start to pop up saying 'program has stopped' over and over again.
Then followed by an unplanned reboot.
I tried to disable that AV program but due to those event popups there's just not enough time to stop or disable the AV program in time until the next reboot.
Tablet has been rooted by Kingoroot and that also worked well all the time.
So I thought to find me a proper stock ROM for my Tab3 device on the internet and upload it as '*Home.tar.md5' through Odin (latest version) onto my Tab3.
Unfortunately it then fails verification when I start installation, so I then renamed it to '*Home_CSC.md5' and then it passes verification, but install took only a few seconds.
That's not good.
So now I think that the stock ROM provided, was not the correct one for my device, because even though the ROM specs are correct, the hardware specs differ, as it lacks 3G, so the chipset differs to begin with.
Also when viewing the log I noticed a problem with PIT, it says 'Get PIT for mapping..' which means there's a problem with PIT however not yet fatal, because it still boot up.
If I have to reinstall by using the proper stock ROM, then so be it, but I'd rather think of repairing in some way if possible.
But I'm not sure how to do that.
When I need to reinstall, I'll need the proper stock ROM 'PHN-T210XXBNI1_T210PHNBNI1' but for 'Samsung Galaxy Tab3, WiFi only, 7.0, 8GB, 32GB Flash disc, Android version 4.4.2 Jelly Bean'.
So far, I haven't been able to find the proper stock ROM, can anyone help?
Click to expand...
Click to collapse
With the newest version of Odin flashing several ROM's, observe 'Get PIT for mapping' and 'PBL.bin' fail, there's no progres ... so it get stuck, more or less.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1397 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> PBL.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
With versions 1.87, 1.85 and 3.09 of Odin, observe 'Get PIT for mapping' and 'NAND write' fail, below the log I get:
<ID:0/005> Added!!
<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> T210XXBNI1_T210PHNBNI1_T210XXBNI1_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> SingleDownload.
<ID:0/005> PBL.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The stock ROM I seem to need for this device 'SM-T210, Tab3, 7.0, 8GB WiFi, has these specs: KOT49H, T210XXBOB1, PHN, build date Feb 3 2015, Android version 4.4.2
Kernel version: 3.4.5-4081557
I'm not sure about KitKat or Jelly Bean as both seem to have Android version 4.4.2.
So what's going wrong here?
No mather what stock ROM I try to get installed via Odin, any attempt does fail.
When I try to update via 'recovery' on the Samsung Tab3 from a stock ROM on an flash drive, installation will still fail.
Perhaps due to I once forget to uncheck 're-partitioning' in options before any change has been tried, and I've no idea of the concequenses.
Before, when connecting the Tab3 device to an computer, through the USB cable, I was able to browse the Tab3 content.
But after that incident, I seem to have no longer access to the Tab3 device from a (Windows) computer.
So far, I haven't been able to find how to recover from this, or a manual how to get an functioning Tab3 back.
Please help!