I would like to install a custom rom on a samsung galaxy s4 gt i9505 with android 5.0.1, is there some help to unlock the bootloader? Do the root and then install a miui rom?
First root your device with the proper root file by using Odin (you need a computer to install and use Odin program) then install TWRP that will help you install any room you want (.zip) directly from your phone.
Most S4 have an unlocked bootloader. Unless you're American, then it's locked most probably and can't be unlocked.
Ok but in odin mode says "Write Protection: Enabled".... It's normal?
Inviato dal mio Redmi 4 utilizzando Tapatalk
The only s4 with a locked bootloader is the AT&T and Verizon versions.
The i9505 doesn't have a locked bootloader and was never carried by any north American carriers.
Yes, it's normal.
No need to root before flashing twrp and a custom ROM.
Hi guys,
It is October 2017 now and I can still read all over the net that only very few models of the international version of the Samsung Galaxy S4 GT-I9505 (Jfltexx) – and those only in the States - have a locked bootloader.
I was advised to update to the newest available firmware before flashing and find myself now at stock Android 5.0.1 (Bootloader: I9505XXUHPK2, Firmware: LRX22C.I9505XXUHPK2, Knox Warranty Void 0x1). I tried to install TWRP according to https://wiki.lineageos.org/devices/jfltexx/install and it doesn’t matter whether I use Odin or Heimdall, switch off antivirus and the firewall, nothing works. It *looks* as if it does, but it is impossible to boot into the recovery.
The phone, being second hand, is out of warranty anyway. I don’t care if I wipe all my data, but I don’t like the idea of an unrecoverable brick.
I did download “cfar_samsung_gt-i9505_jfltexx_lrx22c.i9505xxuhpk2_t0.zip” from https://desktop.firmware.mobi/device:63/firmware:5743 but I am wary of Chainfire’s admonition on https://desktop.firmware.mobi/device...are:5743/cfar?
”BOOTLOADER UNLOCK: If your bootloader is not unlocked, depending on the device, it may be automatically unlocked (wiping all data), flashing may fail, or the device may brick altogether.”
I would very much like to run Lineage OS on my phone. Does any one have an idea on how to proceed from here without incurring *too much* risk?
Greetings from Flensburg, Germany.
KrautHolg
Here's what I recommend:
download Odin 3.07: https://www.google.ca/url?sa=t&rct=...tid=1168421&usg=AOvVaw0aq_x8M8nbsqDFAFe9tFoy;
download the tar version of TWRP for gt-i9505: https://dl.twrp.me/jfltexx/;
open Odin 3.07 and put TWRP tar file in PDA slot;
uncheck everything in Odin except f reset time;
flash TWRP. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use the phone buttons to boot into recovery.
Do NOT run any program that tries to unlock the bootloader as these programs can hard-brick the phone.
Related
Tried to flash a rom using TWRP and now I'm stuck on the Samsung Custom screen??? Seems like a soft brick. Need the phone to function......
Looks like you didn't flash the proper version of TWRP and flashed one for one of the other versions of the S4, 9500 or 9505 which have unlocked bootloaders. A special version of TWRP is made for the SGH-I337 because of its locked bootloader which contains the Loki exploit to allow it to boot.
Download Odin and the Stock Firmware, install USB drivers for phone, drivers are included in Samsung Kies or you can get them seperately
Put phone into Download mode
Restore stock firmware.
Use this to Root your phone and install the proper TWRP in one blow. http://forum.xda-developers.com/showthread.php?t=2297900
Use TWRP to flash any SGH-I337 Rom you want if thats what you were going to do, as long as it has the Loki patch. (Current CM10.1 does).
I have decided to root my N9005 2 days ago. So this is what i've done:
I was on version 5.0, I downgraded it to 4.4
i flashed Stock official ROM with a version of 4.4 using odin.
After that, my phone stop at Samsung logo. I then removed the battery and hold volume -, home, and power button.
I Flashed the CF-root. I tripped my knox 0x1 and i don't care since my warranty is due. Then i flash a recovery soon after i flashed a custom ROM.
After so, i checked my "about device => Status"
I found unknown IMEI and unknown IMEI SV", also i notice that i have unknown baseband version.
I then power off my phone, boot into recovery, and wipe cache partition and did full wipe.
I reboot to "Download" (The recovery ask me to install root, i chose "no")
Then i flash again the 4.4 official version.
Waited till it boot. After boot was completed, i immediately Checked my IMEI, and found out, it was still unknown.
My question is How to get back my IMEI, IMEI SV, Baseband version?
Thank you!
whymewho007 said:
I have decided to root my N9005 2 days ago. So this is what i've done:
I was on version 5.0, I downgraded it to 4.2
i flashed Stock official ROM with a version of 4.2 using odin.
After that, my phone stop at Samsung logo. I then removed the battery and hold volume -, home, and power button.
I Flashed the CF-root. I tripped my knox 0x1 and i don't care since my warranty is due. Then i flash a recovery soon after i flashed a custom ROM.
After so, i checked my "about device => Status"
I found unknown IMEI and unknown IMEI SV", also i notice that i have unknown baseband version.
I then power off my phone, boot into recovery, and wipe cache partition and did full wipe.
I reboot to "Download" (The recovery ask me to install root, i chose "no")
Then i flash again the 4.2 official version.
Waited till it boot. After boot was completed, i immediately Checked my IMEI, and found out, it was still unknown.
My question is How to get back my IMEI, IMEI SV, Baseband version?
Thank you!
Click to expand...
Click to collapse
1. Why you downgraded your device to root it?
2. Why you didn't create a backup of your IMEI before make a downgrade that is risky for your device?
3. Flash the latest stock ROM via ODIN with .PIT file and clicking the Re-partition box. This method doesn't work maybe, but you don't have so much choices. Try it and if works, you will recover your real IMEI. You will have a beaty paperweight if not.
Joku1981 said:
1. Why you downgraded your device to root it?
2. Why you didn't create a backup of your IMEI before make a downgrade that is risky for your device?
3. Flash the latest stock ROM via ODIN with .PIT file and clicking the Re-partition box. This method doesn't work maybe, but you don't have so much choices. Try it and if works, you will recover your real IMEI. You will have a beaty paperweight if not.
Click to expand...
Click to collapse
i downgraded because i can't see note 3 being rooted on version 5.0, therefore i follow this guide:
http://forum.xda-developers.com/galaxy-note-3/development/root-guide-note-3-lte-sm-n9005-lollipop-t3093183
I follow the part 1 procedure and yes i was able to downgrade from 5.0 - 4.4 version.
After im done with the downgrade, i checked this CF-auto-root guide: http://forum.xda-developers.com/showthread.php?t=2466423
I notice in the download area this "
SM-N9005 (International Qualcomm): CF-Auto-Root-hlte-hltexx-smn9005.zip
(only works on 4.4 bootloaders, if you're still on 4.3 use the old version which you can find here: http://d-h.st/J32)
Also the reason why i downgraded my version.
I was not able to back up my IMEI since i don't know that it will be wipe out after installing custom rom. I was not able to find a guide that i should back up my IMEI before flashing custom roms. Also i anticipate
that it would not be wipe out. Like on HTC Sensation, flashing custom roms does not give unknown IMEI, if ever it happens, i have no idea since i was not able to experience it on my part rooting a Sensation.
I already fix my IMEI number.
-I am here in Philippines, so what i'ved downloaded was Philippine Official Firmware ROM 4.4. Then i realize that my phone came from Singapore, Therefore i downloaded a Singapore Official Firmware ROM 4.4.
-I go into recovery, wipe cache, format and full wipe.
-I was going to boot on download mode. Whenever exiting the recovery coming from full wipe, it tells me that "NO ROOT" was found, Install SU or NO. I chose "NO".
-Then im on download mode, i use ODIN, Flash my Singapore Official Firmware ROM.
-After 5-10 minutes, my Note boot up, and noticed i already have signal bar, IMEI, IMEI SV and baseband.
I will now back up my IMEI number.
Okay, here is the deal. I was trying to install a costum rom on my att galaxy s4. What I did was I rooted it using king root and tried to flash a rom through rom toolbox, but I believe it was just going to take me to my recovery. After that the screen got stuck on the costum screen with the padlock, and only seems to turn on with a charger plugged into it. I am on 5.0.1 lollipop and have managed to flash the original recovery, but any stock rom I try to flash using Odin fails by saying complete thread failed or something like that, and says on my phone binary 1 or something like that. I really need help on where to start.
Thanks
What is the exact Odin error?
AT&T never released a full firmware for flashing via Odin beyond 4.1.2. Look here for a possible solution: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Once the phone is running a 4.3 or higher bootloader, the bootloader is locked and custom ROMs can't be installed unless the custom ROM is based on a stock ROM.
There's an ODIN flashable Android 4.2.2 MDL bootloader tar file out there somewhere too.
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
audit13 said:
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
Click to expand...
Click to collapse
Are there any other options, or should I just give up on it?
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2
audit13 said:
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2
Click to expand...
Click to collapse
I finally fixed it. I had downloaded that rom before, but it hadn't worked. I decided to try it again and used a different USB port and it worked! Thanks for the help!
Hi guys, to my understanding BL/CP are available in tar or zip formats and may be updated via Odin or Twrp respectively. Appreciate any advice as to differences (if any) between the two methods. TIA
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
CuBz90 said:
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
Click to expand...
Click to collapse
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Xp3riaXpr3ss said:
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Click to expand...
Click to collapse
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
CuBz90 said:
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
Click to expand...
Click to collapse
True that. I only ever return to Odin to flash official firmware in the event of soft bricks with denied access to Twrp, however, was getting confused partly due to written instructions for roms requiring BL/CP to be flashed in download mode. Thanks for clearing this up. Cheers.
my current booloader is version 1...can anybody tell me how can update it to version 4? i am using s7 edge SC02H(snapdragon) japan.
thanks
Looking for the right modem and bootloader files
Hello,
I'm running Nougat on my s7 g930f it's using the tgp rom. In preparation for an oreo upgrade I atempted to flash an odin-zip file I found on LightRom's page, thinking it would give me a modem update. This was an extremely bad idea. Now my system does still boot, but I have no signal at all, my phone number, base band, IMEI, mobile network, etc all show as unknown under settings, about phone and the various status checks. Now when I atempt to go in to odin again to flash another modem update now I'm told that the atempt has failed. I'd appreciate some help. What file do I need to get the bl and the cp file? I'm running twrp 3.2.3, and i'd like my signal back.
Thanks.
Dave.
Hello everyone,
I was thinking about installing Lineage OS on my Samsung Galaxy S4 GT-I9515 (Value Edition) currently running Stock Android Version 5.0.1 without root.
Is the version of Lineage OS and TWRP I found at https://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-cm14-1-galaxy-s4-jfvelte-gt-i9515-t3534552 appropriate for that purpose?
Now, my confusion arises from the fact that different guides seem to give incomplete or even contradictory instructions on how to approach that. As a first step, I need to install a custom recovery, such as TWRP:
Does this require my device to be rooted?
Some guides apparently require my bootloader to be unlocked; Is this necessary? If so, how do I do that?
Other guides suggest that I use Odin. Is this the correct approach? Does my bootloader need to be unlocked for that method? Is a root required?
Anything else I should pay attention to?
Thank you very much in advance
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Not able to root S4 GT-I9515
TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
I tried to flash CF-Auto-Root on my phone after completing the flash till reset on odin phone gets restarted and is showing following messages on top left corner on the samsung s4 logo screen
recovery booting....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
it is not going any further than this please help.
TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
the twrp file bricks the phone
raffux3 said:
the twrp file bricks the phone
Click to expand...
Click to collapse
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google
TheFixItMan said:
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google
Click to expand...
Click to collapse
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)
raffux3 said:
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)
Click to expand...
Click to collapse
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that
TheFixItMan said:
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that
Click to expand...
Click to collapse
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always
raffux3 said:
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always
Click to expand...
Click to collapse
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)
TheFixItMan said:
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)
Click to expand...
Click to collapse
I have re-installed the usb drivers and odin works fine finally. I will try to root and install twrp again...thank you for support