i was on pb1 unlock boot loader try to upgrade to pf4 by doing that
stuck on verizon screen trying to go back into stock pb1 but stuck on
verizon splash screen. i have try all pit file plus pb1 stock tar but all in vain.please help
on startup screen Custom is displayed although i have flashed PB1 Stock
Issue resolved.please close this thread.if anyone want to know do ask
Related
Hi,
I recently did a factory reset through safestrap while using the 4.4 GPE rom, and now I can't boot back into safestrap. It stays stuck at the splash screen. I can however get into download mode and the normal non-safestrap recovery. How do I unbrick this?
Flash the stock firmware that you were on. The link can be found in the all things AT&T thread.
jmjoyas said:
Flash the stock firmware that you were on. The link can be found in the all things AT&T thread.
Click to expand...
Click to collapse
So flash the NC1 tar files in the thread titled "4.4 stock odin tars"
Having a problem... I have an S5 Dev Edition for VZW and I'm having radio problems. I had a rescue .tar that would bring me back to stock, rooted NCG, which was the only ROM i was able to get a cellular signal. Since upgrading to NK2 stock firmware (aboot.mbn deleted after i backed up my aboot) I have not been able to obtain a 4G signal (3G only) on ANY ROM. I want to downgrade BACK to my NCG rescue file and start over, but when I flash it now, it hangs at the Samsung splash screen. Is there something special I'm supposed to know (or do) in order to downgrade from NK2 to NCG? I'm ready to go ahead and flash a stock .tar (since I've got a backup of my unlocked aboot) but this is my last ditch effort to avoid that. PLEASE HELP!
Hey there guys. Running into an error here in my flashing endeavors.
I originally rooted my Galaxy Note 3 this past year and traded phones with my dad who opted to try to unroot to stock. In doing so, he called me to fix his mistake of dirty flashing the nc4 firmware right over from eclipse rom I was previously running in nc4. Now when I flashed it with the correct vzw firmware, itistill boots with the 'custom' boot logo (but no option to boot into safestrap) and gets stuck on the verizon splash screen every time even after multiple reflash.
Any help or ideas?
You can odin flash. Nc4 tar files.
Was running alliancerom on 4.4.2 and found the unlocking bootloader option. Unlock worked and tried the jasminerom after installing ttwrp-3.0.2-0-hltevzw-4.4.img. Then discovered cm13 which worked great but discovered a kernel opps so installed new modem and bootloader based on of1. The bootloader bricked. Odin won't let me install the retail stock roms. It gives an error in korean. I was able to install of1 recovery but cannot get the system.img.ext4 thru odin without the korean error popping up.
At this point I don't see how I can return to stock. Is there a way out or do I have a dead device? Any help appreciated.
Thanks.
[This link makes me think I am screwed: http://forum.xda-developers.com/showpost.php?p=68406517&postcount=515]
Hello community,
My question is about the BL File/Slot in Odin.
What does it do? What does it have? Is it related to the Boot-Animation such as T-Mobile/AT&T/Sprint boot-loading screen?
What I am trying to do is to flash T-Mobile's Official Latest Stock APK1 BUT I would like to do it WITHOUT THE T-MOBILE's loading screen such as the SM-G935U boot screen....
If I flash TMO APK1 AP/CP/CSC with SM-G935U API3 BL work?
I appreciate any advice given..
Thanks
purotijuana said:
Hello community,
My question is about the BL File/Slot in Odin.
What does it do? What does it have? Is it related to the Boot-Animation such as T-Mobile/AT&T/Sprint boot-loading screen?
What I am trying to do is to flash T-Mobile's Official Latest Stock APK1 BUT I would like to do it WITHOUT THE T-MOBILE's loading screen such as the SM-G935U boot screen....
If I flash TMO APK1 AP/CP/CSC with SM-G935U API3 BL work?
I appreciate any advice given..
Thanks
Click to expand...
Click to collapse
The BL slot is ONLY the locked bootloader that controls the device booting up and nothing to do with the boot animation, which is in the RP (the AP slot). DO NOT mess with it if you don't know what you are messing with.
The boot animation is in the /system partition, which you can't get to directly unless you are rooted.