Help, "Fake" Verizon S4 - Verizon Samsung Galaxy S 4

hi,
i have a verizon galaxy s4 (sch-i545) with android 5.0 made to say its a i9505, every data icon (H+,E,G,H,3G) was modified to show 4G and the battery drains in less than a hour after a full charge
is it possible to flash a stock verizon s4 jelly bean on this phone? its unusable with the "stock rom" it has.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

dragonelwars said:
hi,
i have a verizon galaxy s4 (sch-i545).........
Click to expand...
Click to collapse
This is not possible as the bootloader is locked up and cannot be unlocked.
If you attempt to flash another devices stock firmware, or even an older stock firmware, the security feature (aka Knox) within the bootloader will perform a check of the Firmware and immediately reflect an error message via the Odin software.
Also, the I9505 device has a slightly different architecture/hardware than the I545 variant. So... even IF the bootloader was unlocked, it wouldn't work and create a huge mess for you.
Ultimately, if you attempt any of the above items, you'll be taking a very high risk at Soft/Hard Bricking your device.
I wish you the best of luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.

Ibuprophen said:
This is not possible as the bootloader is locked up and cannot be unlocked.
If you attempt to flash another devices stock firmware, or even an older stock firmware, the security feature (aka Knox) within the bootloader will perform a check of the Firmware and immediately reflect an error message via the Odin software.
Also, the I9505 device has a slightly different architecture/hardware than the I545 variant. So... even IF the bootloader was unlocked, it wouldn't work and create a huge mess for you.
Ultimately, if you attempt any of the above items, you'll be taking a very high risk at Soft/Hard Bricking your device.
I wish you the best of luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
i tried flashing 4.3,4.4 and 5.0.1 (newer), none worked
it just soft bricks, nothing terrible happened so far

Try flashing the latest official stock Verizon firmware. If that doesn't work try flashing the latest i9505 firmware. If you have root, grab a copy of flash fire v0.53 or 0.52 I think it is and try flashing a custom Verizon ROM like stang 5 liter.

Related

[Q] Bought AT&T phone, but want tmobile firmware, what to do?

As the title states, I bought an AT&T S5 for my wife for christmas. She likes some of the stock apps that tmobile offers and I was wondering if i could just install the tmobile rom on the AT&T phone with minimal risk.
Thanks for the help.
EvilDylan said:
As the title states, I bought an AT&T S5 for my wife for christmas. She likes some of the stock apps that tmobile offers and I was wondering if i could just install the tmobile rom on the AT&T phone with minimal risk.
Thanks for the help.
Click to expand...
Click to collapse
Usually people buy the t-mobile S5 to use on at&t. You could always just download a Tmo rom and pull the apks from the zip.
As for flashing a Tmo rom not to sure. Barely learned tmo S5 supports international roms.
I want to do the same thing.
I have restored 900A to old AT&T stock firmware with odin, towelroot then worked.
What is my next step now?
I want T-Mobile softcard and T-mobile call-over-wifi to work and also simply removing all the AT&T default apps.
So I want my phone to be like it came from from T-Mobile store.
A at&t and t-mobile S5 phone should be in hardware the same?
Quote:
Important Note: You may only download and install the specified stock firmware according to your Galaxy S5 phone model number. As you may not know, there are numerous versions of the Galaxy S5 in each and every countries. Each of these Galaxy S5 versions uses different firmware build, flashing a non-specified stock firmware to other Galaxy S5 variants may result into bricks. Meaning it will also causes damage to your phone and you cannot recover it by your own.
Solved my issue, not the overall thread, sorry for the confusion. (please delete this post, I can't do it from Tapatalk)
kchannel9 said:
Solved
Click to expand...
Click to collapse
Please do tell what solution you came up with! I'm in the same predicament. I would love a Tmobile rom that supports wifi calling on my att s5 900a.
reloadeds5 said:
Please do tell what solution you came up with! I'm in the same predicament. I would love a Tmobile rom that supports wifi calling on my att s5 900a.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showpost.php?p=60638012&postcount=619
Another option, but beware, homie in the thread said Wifi Calling not working for him
Btw I decided against trying this out for now, and am just using Hangouts as a wifi calling solution

Installing CM on LGMS769/P769

So long story short: Finally got CWM installed on the MS769 from Metro by using some chinese root program to get root, installed busybox, then used the L9 Recovery installer from artas to get CWM on there. So then I try to install bobzhome's P769 CM ROM and met with undesirable results.
Here is CWM installed by the L9 Recovery Installer v1.5:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The rom I'm trying to install:
The "This package is for "p769,p760,u2" devices; this is a "p940" error
This most certainly not a p940! So I suspect CWM is a bit outdated. But how can I get the most up to date CWM when I've already used the most up-to-date L9 Recovery Installer? I've tried other flashing programs like flashr and CWM's official rom manager on Google Play but I get met with the dead android picture when trying to boot into the new recovery I flashed.
I also tried opening up the CM ROM and finding the script that does this check and disabled it. But then shortly I get this error regarding setting recursive metadata. I googled "setting recursive metadata" error and folks just say to update CWM. So I guess I gotta really get CWM updated.
Is this a dead end for me? Should I just toss this phone in a pit of lava?
Have you unlocked the bootloader? If not, you can't install CM.
The CWM you've installed is a 2nd-init recovery. You need to unlock the bootloader to install a) a proper recovery, and b) to install ROMs that aren't based on stock
Darren
Sent from my Bell Mobility Samsung Galaxy S6 SM-G920W8 using Tapatalk
DarryDoo said:
Have you unlocked the bootloader? If not, you can't install CM.
The CWM you've installed is a 2nd-init recovery. You need to unlock the bootloader to install a) a proper recovery, and b) to install ROMs that aren't based on stock
Darren
Sent from my Bell Mobility Samsung Galaxy S6 SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. Alas, I feared the worst. I had that feeling since there were several people saying there's absolutely no way to unlock the bootloader, and that there was even a petition to unlock it.
It can be unlocked, using a 910k cable and plenty of patience.
Until then, you can only run stock ROMs, or modified stock ROMs such as Kumakan or UltraROM. Try them out, they may suit your needs if you don't want to go through the BL unlock process.
Cheera
Darren
Sent from my Bell Mobility Samsung Galaxy S6 SM-G920W8 using Tapatalk

[HELP] Where do I start with roms?

I've been searching for a post that tells me how to start installing roms on a verizon s4, but most of these post are out-dated.
So is there a way to start installing roms or am I shut out completely (lollipop 5.0.1 latest)?
What roms should I consider for stable phone use?
Where is said tutorial for noobs?
mooseshoes said:
I've been searching for a post that tells me how to start installing roms on a verizon s4, but most of these post are out-dated.
So is there a way to start installing roms or am I shut out completely (lollipop 5.0.1 latest)?
What roms should I consider for stable phone use?
Where is said tutorial for noobs?
Click to expand...
Click to collapse
IIRC, Vzw bootloader was never unlocked unless it was the MDK version. If you have any other versions you will need to familiarize yourself with something called Safestrap. It should be covered in the Verizon GS4 forums.
Sent from my Pixel XL using Tapatalk
wtherrell said:
IIRC, Vzw bootloader was never unlocked unless it was the MDK version. If you have any other versions you will need to familiarize yourself with something called Safestrap. It should be covered in the Verizon GS4 forums.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I believe my version is "PL1"... i don't even see that as an option on most tutorials.
mooseshoes said:
I believe my version is "PL1"... i don't even see that as an option on most tutorials.
Click to expand...
Click to collapse
It's a brand new update, not much information on it yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So how do i go about roooting to install xposed? What xposed frameworks are recommended?
mooseshoes said:
So how do i go about roooting to install xposed? What xposed frameworks are recommended?
Click to expand...
Click to collapse
I would try the OF1 methods outlined in the General section. You have to use a Samsung specific Xposed. The one by arter97 is for deodexed ROMs, there is one by dcclark for odexed (stock) ROMs.
wtherrell said:
IIRC, Vzw bootloader was never unlocked unless it was the MDK version. If you have any other versions you will need to familiarize yourself with something called Safestrap. It should be covered in the Verizon GS4 forums.
Click to expand...
Click to collapse
I am in the same situation with the OP, except I am on an older firmware NC5. I just saw a video about how to root it and install Safestrap. Is Safestrap a custom recovery like CWM and TWRP?
If I manage to get Safestrap on my phone, would I be able to install AOSP-based Roms? (Many ROM claim it will only work with MDK. ) I mean if we can get Safestrap on it, then we can already bypass the locked bootloader, right?

Newest Build Supported by Phone?

I have an S4 that is no longer used, so I decided I would see if I could root and install a custom ROM on it. Every one I find seems to be 5.1, and I was curious if the phone was even capable of running a newer version of Android. If so, are there any custom ROMs of the higher OS?
figarojones said:
I have an S4 that is no longer used, so I decided I would see if I could root and install a custom ROM on it. Every one I find seems to be 5.1, and I was curious if the phone was even capable of running a newer version of Android. If so, are there any custom ROMs of the higher OS?
Click to expand...
Click to collapse
Not with a locked bootloader. The Sprint S4 has tons of 7.1+ so the hardware is capable but the locked bootloader really limits things.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Not with a locked bootloader. The Sprint S4 has tons of 7.1+ so the hardware is capable but the locked bootloader really limits things.
Click to expand...
Click to collapse
I'd read reference to bumping the bootloader, and assumed that was a term for unlocking it. Is it really impossible to unlock?
figarojones said:
I'd read reference to bumping the bootloader, and assumed that was a term for unlocking it. Is it really impossible to unlock?
Click to expand...
Click to collapse
Not unless you're on MDC, which was the first build released for this device. It would be a miracle if your device was still on that build. There's no downgrading that far, so yeah pretty much impossible. Not sure what "bumping the bootloader" means, but the answer is still the same.
figarojones said:
I'd read reference to bumping the bootloader, and assumed that was a term for unlocking it. Is it really impossible to unlock?
Click to expand...
Click to collapse
Bump is a vulnerability only for older LG bootloaders.

Question Error when trying to unlock bootloader

Hi all.
I'm trying to unlock the bootloader of my 8 Flip but am having a couple of issues. First one is that there's no "OEM Unlock" option in my Dev settings. I've tried running the official unlock tool anyay, and it errors out saying "Failed to unlock your device, please try again later.[11006]"
Any ideas?
Thanks.
Solved it - Just had to turn wifi off and use mobile data and it worked
My friend has an error code when unlocking the Bootloader. Do you know why?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why are you trying to unlock the bootloader? Are there custom roms available?
lew4man said:
Why are you trying to unlock the bootloader? Are there custom roms available?
Click to expand...
Click to collapse
To root the phone
where did you buy the phone? Some vendors sell phones that cannot be rooted.
You can see it with the app CPU-Z in System section if you see bootloader : no, you can't root
I was just about to unlock the bootloader to try to dump the recovery.img and use that to create a twrp image.
But there is a big warning saying:
Before you download, install, and use the Unlock Device App (“Service”), you understand that you need to take all risks in terms of quality and performance of the Service, including but not limited to: once you trigger the Service, you’re not able to recover your ASUS products to the original status at the time of manufacturing (“Original Product”) anymore. Original Products which is used with the Service (“Changed Product”) will no longer be regarded as the Original Products. The software updates will not be available to the Changed Product, and the digital content in the Changed Product may no longer be used. (...)
Click to expand...
Click to collapse
Does this mean I would not get security updates and later the Android 13? I only want to get twrp to be able to root the device. but losing the OS updates would be a big no-no.
Are those who have unlocked it getting updates? Can anyone confirm this?
iceinsight said:
I was just about to unlock the bootloader to try to dump the recovery.img and use that to create a twrp image.
But there is a big warning saying:
Does this mean I would not get security updates and later the Android 13? I only want to get twrp to be able to root the device. but losing the OS updates would be a big no-no.
Are those who have unlocked it getting updates? Can anyone confirm this?
Click to expand...
Click to collapse
Would also like to know the answer to this. Did you ever find out?

Categories

Resources