Hello Everyone,
I've dug myself into a pretty big hole and am hoping to get some direction to dig myself out of it.
I recently moved to a new apartment, and internet service won't be set up until Tuesday evening. In my infinite wisdom, i decided to "take a crack" at installing a custom ROM on my Verizon Galaxy S4 in order to use the tethering option for free.
I used the instructions at this thread to install Safestrap. So far so good.
I then downloaded CM12.1 from this website. (Please note that this is an external link). This is mistake #1, though I did not know that CM12.1 was not compatible with Safestrap.
When I booted into SafeStrap recovery, I was also unaware that the default ROM slot is the stock slot, and I installed CM12.1 in the stock slot. This is mistake #3. What was mistake #2, you ask? Well, I didn't make any backups.
When I tried to boot into the system in the stock ROM slot, I got an error that SafeStrap was disabled. I then installed CM12.1 in a new slot, and I no longer get that error, but after SafeStrap's boot screen, I get an error that says "Secure Fail: Kernel" and "System software not authorized by Verizon Wireless has been found on your system."
So, I can still boot into SafeStrap recovery, I can still boot into Odin mode, and that's about it. I have heimdall installed on my Mac OS X, and I have a Linux computer as well that I can use to fix this problem.
I also wrote down this information before trying to get tethering for free:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLED
eMC BURST MODE enabled
ANDROID VERSION: 4.4.2
BASEBAND VERSION: 1545VRUFNC5
KERNLE VERSION: 3.4.0 [email protected] #1 FRI MAR 29 13
BUILD NUMBER: KOT49H.1545VRUFNC5
SE FOR ANDROID STATUS: ENFORCING
SECURE BOOT STATUS: TYPE SAMSUNG
SECURITY SOFTWARE VERSION MDF V1.0 RELEASE 2
So again, this has been a series of errors on my part. At this point, I'd like to "Unbrick" the phone.
Thank you!
I think the best course of action is to odin NC5 from this forum if you want a chance to have your data back if not just download the nc5 tar (just search for it) and find a guide on how to use odin.
Edit: Nvm forgot you used heimdall find a guide to use heimdall but the same files work.
I'd have to agree with whowatchlist. Hands-down, a bootloader-mode (as in Odin) flash will absolutely be your best bet. If you give no ****s about data, or you happen to keep the important stuff on an ext. SD, then just flash your appropiate stock TAR file (NC5 if I recall the OP) via Odin or Heimdall.
Data recovery may or may not be possible, I really couldn't say without more information. Whowatchlist's link/method should be first and foremost. If that's a no-go just come on back and we'll go from there and get you all sorted.
Or since you are already on a locked bootloader, why not consider upgrading to Lollipop? And if you're still set on safestrap, you can try out stang50liter. Just something to ponder. The phone is by no means 'bricked', at least not in the traditional sense, just comes down to where you wanna go from here.
The rest of this post is probably going to be largely irrelevent and/or not needed, but seeing as I'm still new to posting on XDA rather than just lurking around, I'm attempting to be extra super duper helpful to build my rep/credibility and show i'm not just another window-licker with my helmet on backwards...so I wouldn't blame you for skipping the rest.
As I'm not all that knowledgable when it comes to Safestrap due to my faith in the BL being unlocked/exploited someday, take this as more of a general reference if you would.
Judging by your terminology and that ever-so-fun phrase "i'm gonna take a crack at it", I'm going to assume that this (android modding) is a relatively new field in which you've wandered? If so allow me to touch on a few key points. If not, disregard etc. etc.
Every bootloader EXCEPT for the original one the device released with, MDK, are all locked. This includes ME7, MI1, MJ7, MK2, NC5, NG6, NK1, OC1, and OF1. In general, if you attempt to flash over it, even with a stock kernel that's been tampered, tweaked or altered in any way, your phone/ODIN will give you the finger. But kernels boot the system (e.g. the "ROM"). TouchWiz (courtesy of Samsung) roms are very different from AOSP-based roms. Of course Cyanogenmod is AOSP-based. Because a Kernel that will boot CM cannot be flashed, trying to flash and boot a CM rom will only end in gnashed teeth, swearing and possibly holes in walls.
Safestrap is a middle man. Because it lies on the /system partition, it avoids poking the Kernel-bear, but it boots before the 'ROM', allowing you to select whatever ROM you want to boot.
So if you ended up replacing your stock rom slot with CM12, I can only imagine you essentially ended up attempting to flash your actual partitions instead of a safestrap container, and following that, the locked BL NOPE'd at the Kernel in the zip, and made you quite the unhappy camper. That's my current theory anyway.
If so, there are options. There's always options!
Anyway if you need help or clarification on anything, or have any other questions just hollar back! Thread or PM works (so I don't clutter the forums with walls-of-text like this.) Hell, I'm in a good mood today, I'd even do a Skype step-by-step walkthrough or something lol.
@whowatchlist / @Atomicmuffin, thank you both for the helping hand.
First, I'm glad to hear that the phone is not bricked in the traditional sense.
Secondly, I don't care about the data. I would just like the phone back to a working state and, if possible, I'd still like to flash something on it.
Thirdly, @Atomicmuffin, that "wall of text" was incredibly helpful.
I'm going to try some of the links that you guys pointed me to, and see what transpires.
My apologies for not getting back on this thread sooner. Unfortunately, there were a lot of changes at the startup I work for this week so it's been a rough ride.
Thank you both - I'll be back with updates.
It's alive! Hey everyone. I just wanted to let you know that the phone is back in operation.
And, the thread that you linked me to (http://forum.xda-developers.com/showthread.php?t=2776189) also helped me understand that I need to use Safestrap, and then only with certain ROMs. Thank you both! I'm going to give this another try, now that I know better. Hopefully all goes well, but if not, I know how to press the reset button.
Stvnx7 said:
It's alive! Hey everyone. I just wanted to let you know that the phone is back in operation.
And, the thread that you linked me to (http://forum.xda-developers.com/showthread.php?t=2776189) also helped me understand that I need to use Safestrap, and then only with certain ROMs. Thank you both! I'm going to give this another try, now that I know better. Hopefully all goes well, but if not, I know how to press the reset button.
Click to expand...
Click to collapse
Hey that's awesome man, glad to hear it and i'm glad my ramblings helped you out! Haha, sometimes I tend to over-ramble and don't know where the line is between helpful and annoying, but what I do know however, is the feeling of being stuck in a spot like that. Weren't no wall-o-texts in my early days. Would have saved me a lot of stress (like when I got cocky and accidentally flashed the wrong firmware, leaving me hard bricked.) All I ask is to just pay it forward!
And Read! Read! Read! Thankfully most people who release stuff on XDA care enough to post massive textwalls that dwarf mine with instructions to keep you on track. So even if you've read enough to recite whatever it is in your sleep....keep reading til you can do it backwards. In a foreign language. And in sign language. Simultaneously. Then you should be good to go!
As a general rule of thumb, I'd suggest sticking with reputable websites like XDA and AndroidFileHost at least until you get familiar, to help avoid blunders like this. There's a lot of misinformation out there in the world beyond, and even more window-lickers who do a one-click root and think they're hot stuff enough to take take their helmet off and start teaching other window-lickers, haha. But I digress...
Safe travels man! And If you got questions just let us know! Oh I almost forgot, so what'd you decide? Gonna stay NC5 and SafeStrap it again?
Edit: A GREAT starting resource is http://xda-university.com
Atomicmuffin said:
Hey that's awesome man, glad to hear it and i'm glad my ramblings helped you out! Haha, sometimes I tend to over-ramble and don't know where the line is between helpful and annoying, but what I do know however, is the feeling of being stuck in a spot like that. Weren't no wall-o-texts in my early days. Would have saved me a lot of stress (like when I got cocky and accidentally flashed the wrong firmware, leaving me hard bricked.) All I ask is to just pay it forward!
And Read! Read! Read! Thankfully most people who release stuff on XDA care enough to post massive textwalls that dwarf mine with instructions to keep you on track. So even if you've read enough to recite whatever it is in your sleep....keep reading til you can do it backwards. In a foreign language. And in sign language. Simultaneously. Then you should be good to go!
As a general rule of thumb, I'd suggest sticking with reputable websites like XDA and AndroidFileHost at least until you get familiar, to help avoid blunders like this. There's a lot of misinformation out there in the world beyond, and even more window-lickers who do a one-click root and think they're hot stuff enough to take take their helmet off and start teaching other window-lickers, haha. But I digress...
Safe travels man! And If you got questions just let us know! Oh I almost forgot, so what'd you decide? Gonna stay NC5 and SafeStrap it again?
Edit: A GREAT starting resource is http://xda-university.com
Click to expand...
Click to collapse
Thanks for that awesome resource @Atomicmuffin. I haven't decided what route to take now that I've got the phone working. My baseband now reads NG6, so and all I really want is the ability to use the phone's hot-spot feature. I'll look into that a bit more.
xxxxxx
link5505 said:
I've been trying to put the stock nc5 file on my s4 with odin but it keeps failing, what gives?
<ID:0/003> 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/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What does the phone display when this happens?
Related
Hello, I have a 10.1 that runs on Verizon 4G here in the states. I'm familiar with rooting, as I have done it on other devices, but this was different. I had a update.zip that I used to get back to working condition until I can find the fix.
My model number is SCH-I905
I was in the process of odining the "[stock rom][3.0.1] P7100BUKDF + bootloader unlock" by chainfire. For some odd reason, I keep getting this error.
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
Click to expand...
Click to collapse
I either need to figure why this is not working, and finsh the bootunlock, and proceed to root from there.
If anyone can please help me fix this problem I'd be greatly appreciated. I fly out in a matter of hours and would like to have this fixed by then.
Why are you flashing that version? It's supposed to be for the Galaxy Tab 10.1v (7100, not SCH-I905)
What you want to do is root your device and change your recovery for CWM (stock ROM), just that, right?
If that's what you want, check this thread: http://rootzwiki.com/topic/2242-root-recovery-galaxy-tab-101-lte/
That thread is a little old, but it looks like still works for HC 3.2. If you want a newer version of CWM, don't flash the recovery from the previous link, instead download it from here: http://droidbasement.com/db-blog/ and flash it via Odin.
And have this threads at hand in case something goes wrong
http://forum.xda-developers.com/showthread.php?p=16812034
http://forum.xda-developers.com/showthread.php?t=1205639
Curses all these different verisons. I already flashed SU and flashed CWM via rom managee. Is that the equivilent to what you posted?
Sent from my GT10.1
How did you flashed SU?
I don't have the verizon tablet, but I think that the CWM provided by ROMManager is only for p4wifi, maybe they change it. Anyway, if everything is working fine, then leave it like that. But I prefer flashing cwm with Odin or a flashable (via recovery) zip.
I used this method:
http://forum.xda-developers.com/showthread.php?t=1657758
Root appears to be working, I know I installed root uninstaller and it did grant it access upon opening.
Would anyone be kind enough to share a good PIT file? I'm having a lot of really weird issues with my phone and I want to NAND erase the device and ODIN the .tar I got from SamMobile. Please don't share your unfounded fears of NAND erasing a device. I've done it at least two dozen times with my last three devices. Contrary to popular belief there is no danger here unless your phone is damaged with bad blocks. Please just share the PIT file if you have it. I am EXTREMELY comfortable here. Thank you.
I'm in need of this as well
I'd give it to you, but I don't know how to get the file you're after.
Hola. Sorry for late reply. I keep forgetting to check on the Sprint Edge page. There aren't many of us
I just created this pit file from my phone. I'm not sure if it matters, but I am running tx_dbs_tx's 4/28/15 stock, rooted, deodexed, KNOX-less 5.0.1 ROM.
https://www.dropbox.com/s/h9kmco32dnz5019/SM-N915-5.0.1 (Sprint).pit.zip?dl=0
Lemme know how it goes.
Hello. Having read a bunch of threads for this matter, i haven't yet encountered a solution for my particular problem. It may be impossible altogether.. but i thought i'd hopefully ask anyway.
My device is the Samsung Galaxy S6 Edge(SM-G925F, international variant, not carrier branded). I have MM 6.0.1 running on it, with the latest security patch and bootloader that is available in my country, that is:
S6 edge SM-G925F ROM Romania - G925FXXS5DQC1 - downloaded and flashed via ODIN 3.12.3 from sammobile
However, recently i wanted to downgrade to LP 5.0.2(or 5.1.1 - and from there my target is 5.0.2), as i like the look and feel of it more. But, as i have said, upon researching around the forum and on the whole internet i haven't found a positive solution, and i decided to make an account on here and hopefully get lucky.
I've tried multiple ODIN versions, multiple 5.0.2 and 5.1.1. ROMs found on the internet for different countries, but the end result is always the same: download mode says SW REV DEVICE 5 BINARY 1(or 2,3,4)
As for ODIN:
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It doesn't matter to me if i have to root, flash custom roms and custom recoveries all over, i just want to know if there is a way to get my phone on the old bootloader and flash stock 5.0.2 rom.
Any info/advice is appreciated. Thank you all!
android2819 said:
Hello. Having read a bunch of threads for this matter, i haven't yet encountered a solution for my particular problem. It may be impossible altogether.. but i thought i'd hopefully ask anyway.
My device is the Samsung Galaxy S6 Edge(SM-G925F, international variant, not carrier branded). I have MM 6.0.1 running on it, with the latest security patch and bootloader that is available in my country, that is:
S6 edge SM-G925F ROM Romania - G925FXXS5DQC1 - downloaded and flashed via ODIN 3.12.3 from sammobile
However, recently i wanted to downgrade to LP 5.0.2(or 5.1.1 - and from there my target is 5.0.2), as i like the look and feel of it more. But, as i have said, upon researching around the forum and on the whole internet i haven't found a positive solution, and i decided to make an account on here and hopefully get lucky.
I've tried multiple ODIN versions, multiple 5.0.2 and 5.1.1. ROMs found on the internet for different countries, but the end result is always the same: download mode says SW REV DEVICE 5 BINARY 1(or 2,3,4)
As for ODIN:
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It doesn't matter to me if i have to root, flash custom roms and custom recoveries all over, i just want to know if there is a way to get my phone on the old bootloader and flash stock 5.0.2 rom.
Any info/advice is appreciated. Thank you all!
Click to expand...
Click to collapse
The only answer for your query is unfortunately no. You can not downgrade from mm to lp. It is impossible. Sorry its not the news you wanted.
I suppose the only way it could be done is to buy a new motherboard that is on lp firmware and replace the full board.
Other than that there is no way.
Understood. Thanks for the info!
Extremely sorry to post this thread again - actually I referred all the threads in XDA Developers Forums but though a few of them matched my requirement but it was closed since 2013 - hence reopening again...
I have a Samsung GT-P1000 - Made in Korea (I don't live there - live in India though) - FCC ID: A3LGTP1000 - S/N: R2DB129469E
I will provide complete details to make it coherent to you...
CURRENT STATUS -- Soft Bricked (Symbol: A mobile - A yellow triangle with exclamation - A desktop) - (The only thing I see in the tab now!!!)
BEFORE -- Android 2.3.3 Gingerbread, no mods (no root, no custom boot-loader, etc...) -- Complete Original Tablet
What I tried to do --
Install Android 6.0.1 Marshmallow (Following this guide: https://www.droidthunder.com/galaxy-tab-gt-p1000-android-marshmallow-rom/) but soon failed in the rooting step itself, precisely, while installing cwm13...
Now, what I want to do --
After some research, which I must have done earlier, not sure, but maybe people are trying to say that installing Android 6.0.1 Marshmallow is not possible... I did not go deeper...
Anyway, I thought we will revert back to what it was... to Android 2.3.3 Gingerbread...
The problem I face doing this --
To install Android 2.3.3 Gingerbread back I used,
-- Odin3_v1.83
-- And the PIT, PDA, and Phone files are here (https://drive.google.com/drive/folders/1CLrfcUdk-oZ1N6ZZ90LbDCdMW5KYkHnV?usp=sharing) - (I got these while referring to a YouTube video:
)
-- And also installed the USB drivers (updated)
And then, following the above YouTube video, I came up with this, (After connecting the device with the PC - after around 15 mins the brick screen appears - It shows a yellow color port in odin - and I start), And stops after this log,
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Then I switched the ports aswell, and the only difference from the above error is the id changes from 7 to 6...
Also, tried with Odin_v3.07, Odin_v3.13.1, Odin_v3.09, Odin_v3.12.3, but the same logs...
And then, started researching this error but no answer was up to my requirement (there are same threads in this forum but the answers for them did not work for me)
Any help would be highly appreciated,
Thank You
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
It_ler said:
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
Click to expand...
Click to collapse
Thank You for replying @It_ler , this was my 1st question in this forum and waiting since a month or more, I am glad you put your precious time in this thread.
I am new to this forum, and I see you are pretty experienced in here, I would really really appreciate if you can help me gather more minds into this. I have memories linked with this tab, and all these days I have been eagerly waiting for a reply.
As you said, to check the re-partition in Odin, I see that it automatically gets checked once I start flashing, but the logs remain the same...
hey guys, so i am trying to downgrade my samsung galaxy note 20 5G to android 10 from android 11. i am not sure which files i need to download from sammobile.com because when i try to find my verizon phone that has a baseband version number of N981USQS2DUE2 well there is none under sammobile firmwares. so i looked around and found it under the usa/cha xfinity mobile i think it was firmwares. oh and by the way my service provider software version is SAOMC_SM.N981U_OYN_VZW_RR_0014 VZW/VZW/VZW. so clearly its a verizon phone not a cha infinity one.. so why is my baseband version coming up under the other section and not under verizon section. well i went with some research i did and chose to do the android 10 vzw download for the AP BL CSC CP files and this is the output i get in odin 3.14.4 .... please help me ... i dont know what is wrong.. and on my phone it says sw rev error (abl) then i forget the numbers.. ill have to run it again and see to confirm.. but if anyone could please help me out that would be much appreciated.. thanks and have A GOOD DAY..
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 9172 M
<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> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> abl.elf
<ID:0/007> xbl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hainguyenthao said:
You can't downgrade bootloader and you already updated to N981USQS2DUE2 and android 10 is N981USQU1DUB7
Click to expand...
Click to collapse
As Admiral Akbar said:" It's a trap!"
i had same problem...
sctvnn said:
i had same problem...
Click to expand...
Click to collapse
It's not a problem it's device security. Called anti rollback. The whole point is to make your device more secure with each incremented bit
TheMadScientist said:
It's not a problem it's device security. Called anti rollback. The whole point is to make your device more secure with each incremented bit
Click to expand...
Click to collapse
Exactly how does that bootloader OS version lockout serve the consumer?
It's not like it can be remote flashed without your knowledge...
blackhawk said:
Exactly how does that bootloader OS version lockout serve the consumer?
It's not like it can be remote flashed without your knowledge...
Click to expand...
Click to collapse
It really don't. It serves the company more than anything we find exploits. Some severe enough. The increment so we can't exploit that exploit. It hurts consumers more than not in my opinion.
So Sony just released update 9.0 for ps4. And is in some cases even bricking consoles. Nothing we can do. Same implementation. Anti rollback. Be easily fixed if we could rollback to the previous firmware.
Their answer is. If you didn't already update we suggest you hold off til we patch it. So what now I can't play ps4s on most games because they require internet and psn access. Which I don't have due to not being updated.
It's to prevent Theifer Sutherlands from downgrading to remove FRP lock.. since I believe there's currently no workaround for Android 11.
TheMadScientist said:
It really don't. It serves the company more than anything we find exploits. Some severe enough. The increment so we can't exploit that exploit. It hurts consumers more than not in my opinion.
So Sony just released update 9.0 for ps4. And is in some cases even bricking consoles. Nothing we can do. Same implementation. Anti rollback. Be easily fixed if we could rollback to the previous firmware.
Their answer is. If you didn't already update we suggest you hold off til we patch it. So what now I can't play ps4s on most games because they require internet and psn access. Which I don't have due to not being updated.
Click to expand...
Click to collapse
Just saw your post, oops. Yeah the lockouts and even the updates many times serve the manufacturer's interests more than the end user's. That's my conclusion.
Been true on all my Samsung's for 8 years. My N10+'s never get upgrades or updates and run like bats out of hell. Current load on this one still running on Pie will 3 yo in June. Very stable and security is not an issue. No vax, no upgrade... still here running wild and free