Hi,
I've been having some trouble restoring my SCH-I605 to functionality after a nice surprise bricking yesterday.
-------------------------------------------------------------------------------------------------------------------
History of Incident:
-------------------------------------------------------------------------------------------------------------------
A few months back I managed to get a successful on my Note 2 after quite a bit of work. Everything was great, and I managed to do all of the modifications I wanted on the stock firmware.
Last night I decided it would be a good idea to make a backup of my current setup in preparation for potential tinkering. I installed Clockworkmod's Rom Manager and Recovery apps. In one of them I clicked something like "Fix Permissions" which requested root access and completed successfully. Following this, the phone requested a restart.
Post restart, I received the standard "verizon has ruined your day" message as follows: "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
-------------------------------------------------------------------------------------------------------------------
I researched the topic and found this thread:
http://forum.xda-developers.com/showthread.php?t=2040264
I have tried each of the firmware downloads including the alternates here, along with a variety of others from similar threads claiming to be stock images or stock rooted.
-------------------------------------------------------------------------------------------------------------------
Throughout this process I have managed to get the ODIN Mode Prompt to read:
-------------------------------------------------------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: SCH-I605
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
RP SWREV: A3
And
ODIN MODE
PRODUCT NAME: SCH-I605
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: CUSTOM
RP SWREV: A3
-------------------------------------------------------------------------------------------------------------------
Typical failures during and post flash included:
-------------------------------------------------------------------------------------------------------------------
SW REV. CHECK FAIL. DEVICE: 3 BINARY 2
ODIN v3.07 Readout
...
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
-------------------------------------------------------------------------------------------------------------------
SW REV. Invalid magic string.
ODIN v3.07 Readout
<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/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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
-------------------------------------------------------------------------------------------------------------------
The second error yields the interesting result of changing the Binary from CUSTOM to SAMSUNG OFFICIAL and replaces the verizon message with the following:
"Firmware upgrade encountered an issue . Please select recovery mode in Kies & try again."
Kies will not connect to the device in this state or ODIN mode, but it does try.
When the Verizon message is present, the usb connection has no activity and thus yields no connection in Kies.
-------------------------------------------------------------------------------------------------------------------
I have attempted making some other .tars with the TAR_MD5_PACKAGER but these pacakges yielded similar results. I can remove the sboot.bin file from the package and get it to install, but the same verizon message comes up. I have tried on multiple ODIN versions and two computers with no change in results.
Any thoughts on what to do now? I have included all the information I think is pertinent. If you need more I can provide it.
Thanks,
Donkey545
I have managed to get the device to boot past either of the error messages by flashing the OTA 4.4.2 Rom I605VRUFND7_I605VZWFND7_VZW.
-------------------------------------------------------------------------------------------------------------------
I found that rom here
(Cant post URLs Because I am a new member)
androidfilehost /?fid=24052804347837519
-------------------------------------------------------------------------------------------------------------------
The system is hanging at the Verizon logo now, but the fact that it is no longer stuck at the error message is promising. I will attempt so more things to get the system to work..
-------------------------------------------------------------------------------------------------------------------
EDIT:
-------------------------------------------------------------------------------------------------------------------
- Booting in Safe Mode does not remedy the issue.
- Booting into recovery now works!
- Wiping the cache yields no results
-------------------------------------------------------------------------------------------------------------------
Recovery mode information:
-------------------------------------------------------------------------------------------------------------------
Android system recover <3e>
KOT49H. I605VRUFND7
--------------------------------------------------
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC.
E: failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E: failed to mount /data/log/recovery_log.txt
-------------------------------------------------------------------------------------------------------------------
I will now attempt a factory reset. I was trying to avoid this, but I probably lost all of my data anyway.
-------------------------------------------------------------------------------------------------------------------
EDIT 2:
-------------------------------------------------------------------------------------------------------------------
The factory reset has successfully un-bricked my phone! I suspect that I will no longer have root, and I definitely lost all of my data. I will confirm these results shortly.
Related
Hey guys i have a rooted Samsung Galaxy S4, 16GB, SGH-I337, with the safestrap custom recovery. and 2 days ago i tried to do a factory reset so i could have enough space to install a custom rom. Through my carelessness , i seem to have wiped the OS off of the device. Now if you try to turn the device on its stuck on the "Samsung custom" boot screen with the unlock icon in the middle. The device can go into download mode but fails to go into recovery mode.
Every time i try to go into recovery it displays the following:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warrenty Void: 0x0
CSB-CONFIG-LSB:0X30
Waite Protection: Enable
eMMC Burst MODE enabled
Then the phone-computer caution emblem comes up in the middle of the screen and says, " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So ive tried Upgrade and Initialization and the Emergency Recovery feature but both failed. They both return a pop up message saying that " Firmware emergency recovery stopped due to GALAXY S4(SGH-I337) error. If the problem persists, please contact the Samsung service centre.". So then i tried the odin method and downloaded both the 1337DB and DL file and tried running them in Odin. Odin fails and shows this in the messages: <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this occurs whether i check the boxes or not and if i add a pit file or not. Then on my phone it says in red, " SW REV. CHECK FAIL: fused:4, Binary 1".
Everything that i have tried has resulted to a fail from Kies to Odin so right now im just about ready to give up and get a new phone. Is my Galaxy S4 still saveable and if so how would i go about saving it? thanks
(oh and sorry for the long question i just wanted to describe exactly what i was going through so you guys have all the information you need in order to develop a solution to my problem, if their is one.)
anyone please?
Looks like you have a knox enabled rom... have you tried mf3 or mk2. I think that of you didn't have at least mf3 that would have worked. I could be wrong on that part but if you cannot use your phone I wpuld try flashing one of those roms.
I337 stock, unlocked, rooted
Hi there guys...I've stumbled onto a problem that I can't fix myself, hence some of your help/expertise is required.
Here's what has happened sofar...
Yesterday a family member of mine lost her phone and asked me for my old SGS3 which was lying around the house.
So after factory resetting the device I gave the phone to her...but then the device got an OTA update...but after update, when the device went to reboot itself, the droid laid dead with a red triangle.
Note: the device was not rooted and was running Touchwiz etc...
Upon reboot, the device got stuck at the Samsung Galaxy SIII - GT-I9300 logo
Then she brought the device back to me and after some searching the web, it seemed that the diagnosis was that the software/firmware may have gotten corrupted.
I followed the TUT (link: here) using ODIN 3.10 , I flashed the International version of 4.3 on my device.
I got the I9300XXUGNJ2_I9300MSTGNJ1_MST file from Sammobile and it worked like a charm...all is well, so I thought.
Today when she turned the phone on in the morning, (she turns it off at night)...the device got stuck at the same place.
But now, even the TUT with ODIN isn't helping...now the whole thing is stuck at SetupConnection.
I have tried the cable, updating the samsung usb drivers, switching the USB ports (not using any USB hub),
making sure that I run the program in admin mode and that there's no ext card connected to the device...but to no avail.
When I hard reset the device I get the following error while the droid lays dead
Code:
E: failed to mount /cache (No such file or directory)
...etc...
Wiping the data/factory reset etc isn't helping either...as it still gives me similar E: failed error.
Rebooting the system gets me back to the stuck Samsung Galaxy SIII - GT-I9300 logo.
Plugging the device with the USB cable to the computer doesn't get me to the ext sd card etc either.
Any ideas?? Help is greatly appreciated.
*UPDATE*
After persisting to follow the TUT mentioned above, finally it went through ODIN and was shown as "PASS"
But when the device reboots after that, the "E: failed to mount error" persists...and I'm back to square one.
contactmsd said:
*UPDATE*
After persisting to follow the TUT mentioned above, finally it went through ODIN and was shown as "PASS"
But when the device reboots after that, the "E: failed to mount error" persists...and I'm back to square one.
Click to expand...
Click to collapse
Sounds like partitions maybe corrupt try the resuce firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << follow instructions exactly as it containes a pit file there are two versions and i think the pit file is in the 4.1.2 version.If this does not work then i think it would probably be a service repair.
tallman43 said:
Sounds like partitions maybe corrupt try the resuce firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << follow instructions exactly as it containes a pit file there are two versions and i think the pit file is in the 4.1.2 version.If this does not work then i think it would probably be a service repair.
Click to expand...
Click to collapse
OK...
First try..gave me the following error in ODIN.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I tried again, after changing the port.
This time I got the following error.
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> tz.img
<ID:0/007> param.bin
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> tz.img
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
*Sigh*
Emmc chip is corrupt/damaged. Try reading the dead boot restore thread in general forum, but doubtful if worth repairing.
^^above, I was using the 4.1.2 firmware which I got from the thread that @tallman43 mentioned.
But as you can see I got the errors shown above.
Then I tried the same using the 4.3 firmware also from that thread but it had no *.pit file.
In that thread on page 41 though, @k-semler added the *.pit file that he used.
But that resulted in ODIN getting stuck at the .pit thing.
After renaming that *.pit file to mx.pit it worked...
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> param.bin
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
BUT after rebooting, the issue remains though.
I'm still stuck at the Samsung Galaxy SIII - GT-I9300 logo
Factory reset in recovery, check for mounting errors.
boomboomer said:
Factory reset in recovery, check for mounting errors.
Click to expand...
Click to collapse
E: failed to mount /cache (No such file or directory) etc...list goes on...
I got some suggestions trying installing Philz Touch Recovery...
So here's what I did...
1. I flashed Philz Touch Recovery using ODIN
It was a pass...and I was able to boot into Philz Recovery.
2. Then I tried installing a Custom ROM (PA) through SD Card.
At first I was getting an error, after checking it seemed that I couldn't access the SD Card.
Then I got myself a new SD card, formatted it to fat32 and transferred the zip files onto it.
3. Installing the Custom ROM (PA)
At first I was getting a Status 7 error.
After editing the updater-script as shown on xda forums..the error went away.
BUT now the installation just aborts and I get the following on my screen.
Code:
Installing: /storage/sdcard1/pa_i9300-4,41-20140705.zip
E: Can't mount /cache/recovery/last_install
E: failed to open last_install: File exists
Finding update package...
Opening update package...
Installing update...
Installation aborted.
press any key to continue.
Note: I also tried with different ROMs (CM11) but same result as above.
Why can't it mount the /cache folder? Could it be a chmod issue??
The error in full from my first post is the following...
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
If it's corrupted then why is it listing only that folder and not other folders as well?
Help is really needed and is greatly appreciated guys/gals.
[SOLVED]
I finally got it working...my issue has been resolved.
For those who are interested, this is how I fixed the problem.
I went and got myself:
- stock *.pit file for the SGS3 GT-I9300 16GB variant.
- stock bootloader for SGS3 GT-I9300
- stock Firmware from my Region (Single File variant)
Step 1
Flash the stock *.pit file using ODIN with the following settings ticked on:
- auto reboot
- re-partition
- f.reset time
- Nand erase all
Note: IF for some reason it doesn't work, re-try and it should pass (I myself had to try 3 times).
Step 2
Flash Philz Touch Recovery using ODIN with the following settings ticked on:
- auto reboot
- f.reset time
Note: IF for some reason it doesn't work, re-try and it should pass.
Step 3
Take a Mirco SD card (format if needed, make sure you format it in fat32). Transfer the stock bootloader zip (no need to extract the .zip file) on it and insert the card in your phone.
Step 4
Press Vol.Up+Power+Menu button and keep pressing it until you see the Samsung Galaxy SIII GT-I9300 logo, then release the buttons and the Philz Recovery will boot.
Install the bootloader zip using the "Install from sdcard" option in Philz Touch Recovery.
Step 5
Reboot to recovery and wipe cache and factory reset.
Go to download screen (ODIN MODE).
Step 6
Flash the stock firmware using ODIN with only the following settings ticked on:
- auto reboot
-f.reset time
Note: IF for some reason it doesn't work, re-try and it should pass (I myself had to try 2 times).
Step 7
If all of this is done...then go to Recovery mode (you'll notice that it's no longer the Philz Touch Recovery. No problem, in the current Recovery mode:
- wipe cache
- factory reset
and reboot the device.
This should resolve the problem and your device will work once again.
No cellular due to wrong/fake imei
^^The above did fix my previous problem but I did encounter a new one.
I had a wrong/fake IMEI ("0049..."), which caused that I had no cell reception and couldn't use the phone to call or send/receive sms etc...
I googled a lot and I tried some of the TUT on the web, but nothing helped.
Until I found a thread on the xda that said one could try to flash a newer stock ROM (don't know the exact thread).
So I went ahead and checked the version I was on...luckily it was 4.0.4
I then downloaded a newer stock ROM 4.3 for my region.
And flashed that using ODIN...
and voila...when I checked the IMEI code again, it was back to the original one.
Files that I used to resolve my issues.
I've been asked which .pit file or which ROM etc...did I use to resolve my problem.
So here it is...but do keep in mind, these files may have worked for me but I can't guarantee that they'll work for you too.
Note: therefor use these at your own risk...I'm not responsible for any problems that you may encounter.
Philz Touch Recovery:
I got the "philz_touch_6.12.8-i9300.tar.md5" file from: here
Stock ROM:
I got the stock ROM (single file) "I9300XXUGNJ2_I9300PHNGNJ1_PHN.zip" from: here
That's the: GT-I9300 Netherlands 2014 November 4.3 I9300XXUGNJ2 I9300PHNGNJ1
The stock *.pit file and the stock bootloader that I used, are attached to this post.
The exact steps that I took are in this post: here
Note: Don't forget to backup your EFS, search on xda for how to do that etc...
Best of luck...
Pretty sure i bricked this to no repair.
So got my Sprint s6 edge few months ago and rooted it a week after. Sadly i dont know what i used rom wise to root it since its been a month+. Sadly i reformated pc awhile back so can't see the files i used.
Got bored and wanted to try and install xposed to add some new features to my phone. So just tried and i'm prety sure i bricked it hard...
what i followed
gs6.wonderhowto.com/how-to/install-xposed-framework-your-samsung-galaxy-s6-s6-edge-0163918/
It said make a recovery so i did by following
gs6.wonderhowto.com/how-to/install-custom-recovery-your-galaxy-s6-s6-edge-0161619/
I did what he did and after it asked for a reboot i rebooted and it got stuck on samsung boot logo saying "Recovery not SEANDROID Enforcing" in top left corner.
So i googled how to remove root and how to get past this screen and many suggested stock rom. I tried that and odin (v3.09) wont get past "Write NAND!"
I let it set for 20 minutes and nothing happened so i googled and everyone claimed trying different usb hubs and cables so i did that. I've tried every usb hub on my pc(8) and all 3 cables i had. So then tried different version v3.10.7 of odin and it fails with following
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> sboot.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)
And in top right under Odin mode it reads
Product Name: SM-G295P
Current binary: Custom
System Status: Custom
FRP Lock: OFF
Secure Download: Enabled
Knox warranty void: 1 (0x0301)
RP SWREV: B:3 K:2 S:2
SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1
So now i'm just lost and scared at what to do. I googled "SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1" And my findings are just to use stock rom...but thats what i did in first place. So now i'm stuck with a phone that is continuously rebooting itself to the samsung boot logo....
G925PVPU1AOCF_G925PSPT1AOCF_G925PVPU1AOCF_HOME.tar.md5 is the rom im trying to flash with and i believe it is stock because got it off this forum from a post claiming it was the new stock updated rom.
Can someone please help? I can skype or teamspeak or ventrilo or just use this forum to help me but i'm beyond confused on what to do now...
edit- phone is continuously rebooting itself to the samsung boot logo...but i managed to make it stop by making phone sit in download mode...
edit2- i can not go into recovery or safe mode. All i can do is wtach my phone go to the boot logo "Samsung Galaxy S6 Edge" screen then to black screen back to boot screen. And i can put it into download mode.... Thats it...The brick is real...
edit 3- 40 views and not one help lol, seems i'll be craigslist shopping soon.
You tripped the Knox counter, that is for sure. Since you can enter download mode that means it is still possible to install the stock firmware. Did you use the correct firmware for your model?
Snowby123 said:
You tripped the Knox counter, that is for sure. Since you can enter download mode that means it is still possible to install the stock firmware. Did you use the correct firmware for your model?
Click to expand...
Click to collapse
I'm pretty sure
SPR-G925PVPU1AOCF-20150415164450
forum.xda-developers.com/sprint-galaxy-s6-edge/general/sm-g925p-firmware-available-t3084414
Is the stock rom i used to try and fix that recovery screwup.
i tried G925PVPU3BOJ7_G925PSPT3BOJ7_G925PVPU3BOJ7_HOME.tar which is a 5.1.1 stock rom and still same results!!!
Try performing a log cat. That is a low skill technique of diagnosing problems in android during a boot loop.
Snowby123 said:
Try performing a log cat. That is a low skill technique of diagnosing problems in android during a boot loop.
Click to expand...
Click to collapse
I dont know how or what a log cat is.
Edit- just turned device back on and plugged itno computer and now blue screen saying An error occured while updating the device software. use emergency function in the smart switch pc software. Yet the smart switch software says unsupported device.
randomly got it to work after 2 hours of leaving it alone i can now start to install the stock firmware but it stops
<ID:0/007> 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/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cm.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
i dk if phone not charged enough or what
edit---
It fails on same part, but progress bar is sometimes farther. Tried it 3 times in total, just going to put phone on charger(wall outlet) for a few hours then try again
also sorry for double posting...
Seriously bangin' my head against the wall. Now I have drywall to fix. After failed attempt at root/rom installation, I'm trying to get my phone back.
ANY help is appreciated.
Thanks in advance.
Ken
Installed Odin 3.09.
Downloaded/installed drivers
into download mode
connected (beboop)
Downloaded and reinstalled pit file (don't ask)
Downloaded rootjunky's Verizon i545 md5 file
attempted reinstall and in Odin get this:
<ID:0/004> 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 Successfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On screen says:
Odin Mode
Product name SCH-1545
Current Binary - Custom
System Status - Custom
Reactivation Lock - ON
CSB-CONGFIG-LS: 0x30
SECURE DOWNLOAD - ENABLED
WRITE PROTECTION - ENABLED
eMMC BURST MODE - ENABLED
START [224,1440]
SW REV. CHECK FAIL fused 8 binary 5
START [224,1440]
SW REV. CHECK FAIL fused 8 binary 5
secure check fail means you are trying to flash the wrong firmware or firmware older then what is one there
download the matching firmware version
Thanks Legitsu
Legitsu said:
secure check fail means you are trying to flash the wrong firmware or firmware older then what is one there
download the matching firmware version
Click to expand...
Click to collapse
I think I may be drowning in an sea of terminology. (and my own stupidity) Please correct me if I'm wrong.
Flash= overwrite any existing software (bootloader, ROM, OS)
ROM= A replacement OS
bootloader= place on disk/drive where POST looks for information on where to load OS.
firmware= permanent software loaded at POST (includes bootloader?)
IMEI= identifier for Verizon customers to determine individual phone.
Odin= software to reinstall OS and firmware
in Download status, Odin on the phone says:
Product Name: SCH-I545
Current Binary - Custom
System Status - Custom
Reactivation Lock - On
CSB-CONFIG-LSB 0X30
SECURE DOWNLOAD - ENABLE
WRITE PROTECTION - ENABLE
eMMC BURST MODE - ENABLED
If I've been so shortsighted as to not make note of the build/firmware or OS (5.0.1), do I just keep trying different restore images until I get one that fits?
I can't tell you how much I appreciate your help.
Ken
KJenkinsAF said:
I think I may be drowning in an sea of terminology. (and my own stupidity) Please correct me if I'm wrong.
Flash= overwrite any existing software (bootloader, ROM, OS)
ROM= A replacement OS
bootloader= place on disk/drive where POST looks for information on where to load OS.
firmware= permanent software loaded at POST (includes bootloader?)
IMEI= identifier for Verizon customers to determine individual phone.
Odin= software to reinstall OS and firmware
in Download status, Odin on the phone says:
Product Name: SCH-I545
Current Binary - Custom
System Status - Custom
Reactivation Lock - On
CSB-CONFIG-LSB 0X30
SECURE DOWNLOAD - ENABLE
WRITE PROTECTION - ENABLE
eMMC BURST MODE - ENABLED
If I've been so shortsighted as to not make note of the build/firmware or OS (5.0.1), do I just keep trying different restore images until I get one that fits?
I can't tell you how much I appreciate your help.
Ken
Click to expand...
Click to collapse
if you can boot into stock recovery it should tell you which firmware/rom you are running 5.01 should be OC1 or OF1
you can just flash OF1 as thats the latest https://www.androidfilehost.com/?fid=24651430732237492
Success!
You did it! Thanks so much. That link in your message did the trick. Was not looking forward to spending more money for Christmas. Tiny Tim gets an extra orange Christmas morning.:good::victory:
I hope I am in the right section the structure of the forum seems to have changed on me or something.
I have gotten frustrated at this point and do not even remember the entire process that has got me this far.
I am not new to rooting as I have rooted maybe 10+ phones all using the xda forum. I just do not trust any other site. This does not mean I am claiming to be a pro. I just know how to follow directions and always try to have a backup before I even get started.
Anywho to the best of my recollection I started with this guide: [ROOT][Samsung Galaxy Tab E][sm-t377p/sm-t560nu]
When I started root I had Marsh 6.0.1
I don't think I ended up rooting using that exact method, or if i did the tablet wouldn't start up but it had twrp.
Somewhere in between my tablet had twrp and I used the backup that was given by @shawn1976 for the system, boot and modem.
The tablet worked but the wifi was refusing to turn on. I searched and searched and couldn't fix the problem and so I think at that point I decided to try and maybe flash the 6.0.1 that it had originally had on it and worse case scenario I would just end up where I started nothing lost.
Anyhow at this point I have TWRP 2.8.7.0 and it gives error that zip file is corrupt on the 6.0.1.
and using odin it just gives:
<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.1203)..
<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> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to restore the @shawn1976 Backup now it doesn't show anything in the list below [ Select Partitions to Restore] list.
when i first started i took note of the OEM Unlocking steps and made sure it was on, but am wondering now after it got reflashed was I supposed to redo that step again before trying to reflash?
I have no backup and I'm wondering what to do at this point. I tried looking for a solution hoping I could avoid posting like a nub about my problems. Any help you guys could give me would be appreciated.
so brief description is:
Galaxy Tab E sm-t377p (sprint)
Tablet doesn't boot up just goes straight to recovery.
TWRP is 2.8.7.0
And no partitions show up for restore in twrp for what was supposed to be my backup @shawn1976's Backup )
is it fixable?
In download mode it says:
ODIN MODE
PRODUCT NAME: SM-T377P
CURRENT BINARY: Custom
FRP LOCK: OFF
WARRANTY VOID: 0x1 (2)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A2, P1
SECURE DOWNLOAD : ENABLE
S8Gonzo said:
In download mode it says:
ODIN MODE
PRODUCT NAME: SM-T377P
CURRENT BINARY: Custom
FRP LOCK: OFF
WARRANTY VOID: 0x1 (2)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A2, P1
SECURE DOWNLOAD : ENABLE
Click to expand...
Click to collapse
If you have the T377P use the firmware from SamMobile to unbrick your device.
https://www.sammobile.com/firmwares/database/SM-T377P/
I tried downloading it twice and twrp doesnt like it. It errors with [ zip file is corrupt] or just restarts twrp.
I'll try a 3rd download.
I have a twrp version 3 in my device which is running on android 5.1.1
I think the problem is with your recovery , 2.8.7.0 is too old to run new binaries maybe?
Try installing latest version of Philz for your device.
Happened with me before when i had a mtk kitkat device and when i tried to install a lollipop rom using an old twrp recovery.
Fixed it by upgrading to traditional cwm-philz
S8Gonzo said:
I tried downloading it twice and twrp doesnt like it. It errors with [ zip file is corrupt] or just restarts twrp.
I'll try a 3rd download.
Click to expand...
Click to collapse
That's because you need to unzip it and flash the md5 with odin not twrp.
ashyx said:
That's because you need to unzip it and flash the md5 with odin not twrp.
Click to expand...
Click to collapse
They were all giving me errors. The flash image with odin and the twrp backup. After a bunch of troubleshooting it turns out my microSD card was the problem. It started giving me errors in windows so i reformatted and put all the files back. Then I reflashed the twrp backup and its able to boot up.
The problem is back to wifi switch flipping off as soon as i turn on. Im guessing it doesnt like the modem flash.
I keep trying to download a diff version of stock rom but I can't keep connected. It's a poopy line i have.
anywho I tried to install the stock rom I did manage to download and I get:
<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> Added!!
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried a few versions of odin, same result.
Please help me, i have a hard bricked SM-T377P, if you have one in hands you can help me to unbrick mine, it will take only 2 minutes! Here is my thread: https://forum.xda-developers.com/android/development/help-sm-t377p-hard-bricked-debrick-img-t3711889
Thankssssssss!
can I hide tethering with out root on this device