[Q] few questions on boot loader and root - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi I am new to note3 and my phone is running N9005ZZHBMI7. sorry I have many questions and couldn't find a answer yet.
how can I check the boot loader version?
which boot loader versions are considered "safe" for rooting?
I think boot loader cannot be downgraded right?
I want to do the root via Universal Root de la Vega soon, in sammobile I see only this HK rom, I think it should be OK? newer build, and root de la vega should remove boot loader for me.
Model: SM-N9005
Country: Hong Kong
Version: Android 4.3
Changelist: 2061029
Build date: Tue, 05 Nov 2013 06:08:04 +0000
Product Code: TGY
PDA: N9005ZHUDMK1
CSC: N9005ZZHDMK1
MODEM: N9005ZHUDMJ9

I can tell it works with mj7 ( type in n9005zhu and you will see it) as i have, bit i havent seen anyone trying it with mk1 or mk2
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

mobilevil said:
Hi I am new to note3 and my phone is running N9005ZZHBMI7. sorry I have many questions and couldn't find a answer yet.
how can I check the boot loader version?
which boot loader versions are considered "safe" for rooting?
I think boot loader cannot be downgraded right?
I want to do the root via Universal Root de la Vega soon, in sammobile I see only this HK rom, I think it should be OK? newer build, and root de la vega should remove boot loader for me.
Model: SM-N9005
Country: Hong Kong
Version: Android 4.3
Changelist: 2061029
Build date: Tue, 05 Nov 2013 06:08:04 +0000
Product Code: TGY
PDA: N9005ZHUDMK1
CSC: N9005ZZHDMK1
MODEM: N9005ZHUDMJ9
Click to expand...
Click to collapse
For the time being I believe only bootloaders to about MJ2 or so are safe (and so far the bootloader can not be downgraded).
Here is a list of 3 ROMs for TGY:
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=TGY#firmware
The oldest one is probably the one currently in your phone, and with that one Root De La Vega (RDLV) will most likely work perfectly.
However I have my doubts that it will work directly on the much newer MK1 - I am not saying that 100% will fail but the safer approach IMHO would be to use first RDLV on your existing MI7, get (and test) root on that MI7 and then use Mobile Odin Pro to upgrade to MK1 and inject/keep root! (all that sequence will keep your bootloader on the original MI7; and of course you should never leave the ROM updates on auto on your ROM).

Curorisity kills....sometimes
I updated to MK1 from MI7 with root de la vega in a single step.
root works, uninstalled rom bundled flipboard with titanium backup, backed up EFS.
ODIN MODE
PRODUCT NAME:SM-N9005
CURRENT BINARY: Samsung Offical
SYSTAM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECURE BOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
WRITE PROTECTION: Enable
Baseband version
N9005XXUBMI5
Kernel version
3.4.0-1626679
[email protected] #1
Wed Sep 11 19:48:23 KST 2013
Build number
JSS15J.N9005ZHUDMK1
SELinux status
Enforcing
SEPF_SM-N9005_4.3_0002

you mean there is no way to check current boot loader version?

mobilevil said:
Curorisity kills....sometimes
I updated to MK1 from MI7 with root de la vega in a single step.
root works, uninstalled rom bundled flipboard with titanium backup, backed up EFS.
ODIN MODE
PRODUCT NAME:SM-N9005
CURRENT BINARY: Samsung Offical
SYSTAM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECURE BOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
WRITE PROTECTION: Enable
Baseband version
N9005XXUBMI5
Kernel version
3.4.0-1626679
[email protected] #1
Wed Sep 11 19:48:23 KST 2013
Build number
JSS15J.N9005ZHUDMK1
SELinux status
Enforcing
SEPF_SM-N9005_4.3_0002
Click to expand...
Click to collapse
Interesting to know
Anyway RDLV only updates the ROM itself - so you are currently on the original bootloader (I would say MI7), original MI5 modem and original kernel 3.4.0-1626679 - for instance my MJ7 is on kernel 3.4.0-2019540 and I would have expected MK1 kernel to be even newer.
There was a program somewhere (sorry, I don't remember the name) that was directly looking into flash for some bytes in the bootloader (and that was working on my S3), but I do not think those are standardized.
Also keep an eye on the output from *#1234# for your CSC version.

Csc is also mk1 now but i noticed that in odin log, it wrote everything twice, is it the effect of checking both pda and csc ? The video tutorial have them both checked so i just follow
Sent from my SM-N9005 using Tapatalk

Curorisity kills..........afterall
the camera is not working even after a factory reset. i think the mismatch of kernel and system partition has something to do with it.
now downloading MI7 to play with.

Solution to camera and wifi probs after using URDLV:
http://forum.xda-developers.com/showpost.php?p=47390175
Is guide for mj7 but should work exactly teh same with mk1 or mk2
Pls report back your results
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

yes it works! thank you so much

Pls write a deatiled report of your phone
Ap
Csc
Cp
Root? Wifi? Camera? System staus fakable with wnam exposed? Do you get force closes? Everything working alright?
EDIT: do you have the 16gb hong kong version of sm-n9005?
EDIT2: how did u get a working efs backup? I tried several ways and i failed
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

test report......
wifi both OK at home and at work
camera OK, front, back, concurrent, flash,
NFC OK, can read my octopus card(wireless payment in hk)
root OK, titanium backup freezing apps is OK
no FC so car
yes system status is offical with Wanam Xposed:good:
so the solution is to use the updated kernel altogether with system partition right? kernel modules from system partition may not load with diffrent version of kernel.
AP: N9005ZHUDMK1
CP: N9005ZHUDMJ9
CSC:N9005ZZHDMK1
ODIN MODE
PRODUCT NAME:SM-N9005
CURRENT BINARY: Samsung Offical
SYSTAM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECURE BOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
WRITE PROTECTION: Enable
Baseband version
N9005ZHUDMJ9
Kernel version
3.4.0-2061029
[email protected] #1
Tue Nov 5 15:01:30 KST 2013
Build number
JSS15J.N9005ZHUDMK1
SELinux status
Enforcing
SEPF_SM-N9005_4.3_0012

mobilevil said:
test report......
wifi both OK at home and at work
camera OK, front, back, concurrent, flash,
NFC OK, can read my octopus card(wireless payment in hk)
root OK, titanium backup freezing apps is OK
no FC so car
yes system status is offical with Wanam Xposed:good:
so the solution is to use the updated kernel altogether with system partition right? kernel modules from system partition may not load with diffrent version of kernel.
AP: N9005ZHUDMK1
CP: N9005ZHUDMJ9
CSC:N9005ZZHDMK1
ODIN MODE
PRODUCT NAME:SM-N9005
CURRENT BINARY: Samsung Offical
SYSTAM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECURE BOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
WRITE PROTECTION: Enable
Baseband version
N9005ZHUDMJ9
Kernel version
3.4.0-2061029
[email protected] #1
Tue Nov 5 15:01:30 KST 2013
Build number
JSS15J.N9005ZHUDMK1
SELinux status
Enforcing
SEPF_SM-N9005_4.3_0012
Click to expand...
Click to collapse
Congrats and nice to hear my lil guide saved u
Idk why it works, maybe the new modem needs some new thing in a new kernel, but i dont care als far as it works
PLEASE take a look at my 2 edits of my previous post
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

I used this script to backup the EFS, I am only assuming that it is working because it didn't give me any special error!
http://forum.xda-developers.com/showthread.php?t=2447342
the kernel version number jumped after using your script so the kernel is in one of those partition files and this kernel is still happy with the root.
and you are right I am using HK 16G SM-N9005 Note 3 LTE

Related

[Q] i9505 safe update?

Hi all
I have i9505 with:
AP: XXUDMH9
CP: XXUDMH9
CSC: DTMDMH2
The device is stock as it could be but is already with the KNOX bootloader. If I flash the following firmware (downloaded from $amsung) will my device status and knox counter remain untouched? (flash with odin 3)
PDA: I9505XXUEMKF
CSC: I9505OXXEMK3
MODEM: I9505XXUEMKF
The correct firmware for ya is: HERE. In theory only KNOX will be 0x1 if u root it, u want come back to android 4.2.2 or install custom kernel/recovery. Flashing STOCK ROM dont have to be a problem with KNOX :fingers-crossed:

[Q] Safe Root & CM 10.2.0 possible?

Hi @ all,
i would like to root my GT-I9505 and install CM 10.2.0 without tripping knox.
I've done this several times with a GT-I9305, GT-I9300 and my GT-N7105.
But here with the GT-I9505 I need some help how to do this without tripping knox and tips where I have to look out for.
Greez Cookie
Here are the facts about the Phone:
Model: GT-I9505
Android: 4.3
FW: I9505XXUEMKE
Kernel: 3.4.0-2085040
Build: JSS15J.I9505XXUEMKE
SE fur Android Status: SEPF_GT-I9505_4.3_0018
Secure boot status: Type: Samsung
Information from Downloadmodus:
Code:
Odin Mode
Product Name: GT-I9505
Current Binary: Samsung Official
System Status: Official
Knox Kerlnel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode Enabled
adb bugreport | find "bootloader"
Code:
androidboot.hardware=qcom
user_debug=31
msm_rtb.filter=0x3F
ehci-hcd.park=3
[email protected]
[email protected] sec_debug.reset_reason=0x1a2b3c00
androidboot.warranty_bit=0
lcd_attached=1
lcd_id=0x408047
androidboot.debug_level=0x4f4c
sec_debug.enable=0
sec_debug.enable_user=0
androidboot.cp_debug_level=0x55FF
sec_debug.enable_cp_debug=0
cordon=fad3ed5b9b7562493d334ff337897297
connie=GT-I9505_OPEN_EUR_15458e43ac6cd65ca2911794c0c7d92c
lpj=67678
loglevel=4
samsung.hardware=GT-I9505
androidboot.emmc_checksum=3
androidboot.warranty_bit=0
androidboot.bootloader=I9505XXUEMKE
androidboot.nvdata_backup=0
androidboot.boot_recovery=0
androidboot.check_recovery_condition=0x0
level=0x574f4c44
vmalloc=450m
sec_pvs=0
batt_id_value=0
androidboot.csb_val=1 and roidboot.emmc=true
androidboot.serialno=4819b8cc
androidboot.baseband=mdm
Cookiekiller said:
Hi @ all,
i would like to root my GT-I9505 and install CM 10.2.0 without tripping knox.
I've done this several times with a GT-I9305, GT-I9300 and my GT-N7105.
But here with the GT-I9505 I need some help how to do this without tripping knox and tips where I have to look out for.
Greez Cookie
Here are the facts about the Phone:
Model: GT-I9505
Android: 4.3
FW: I9505XXUEMKE
Kernel: 3.4.0-2085040
Build: JSS15J.I9505XXUEMKE
SE fur Android Status: SEPF_GT-I9505_4.3_0018
Secure boot status: Type: Samsung
Information from Downloadmodus:
Code:
Odin Mode
Product Name: GT-I9505
Current Binary: Samsung Official
System Status: Official
Knox Kerlnel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode Enabled
adb bugreport | find "bootloader"
Code:
androidboot.hardware=qcom
user_debug=31
msm_rtb.filter=0x3F
ehci-hcd.park=3
[email protected]
[email protected] sec_debug.reset_reason=0x1a2b3c00
androidboot.warranty_bit=0
lcd_attached=1
lcd_id=0x408047
androidboot.debug_level=0x4f4c
sec_debug.enable=0
sec_debug.enable_user=0
androidboot.cp_debug_level=0x55FF
sec_debug.enable_cp_debug=0
cordon=fad3ed5b9b7562493d334ff337897297
connie=GT-I9505_OPEN_EUR_15458e43ac6cd65ca2911794c0c7d92c
lpj=67678
loglevel=4
samsung.hardware=GT-I9505
androidboot.emmc_checksum=3
androidboot.warranty_bit=0
androidboot.bootloader=I9505XXUEMKE
androidboot.nvdata_backup=0
androidboot.boot_recovery=0
androidboot.check_recovery_condition=0x0
level=0x574f4c44
vmalloc=450m
sec_pvs=0
batt_id_value=0
androidboot.csb_val=1 and roidboot.emmc=true
androidboot.serialno=4819b8cc
androidboot.baseband=mdm
Click to expand...
Click to collapse
you can not.
safe root works in some firmwares on I9500.
there is "kingo root", no idea if it works on I9505 http://www.kingoapp.com/android-root.htm
ive just rooted my 9505 after extensive reading -
and i did not read about any way around KNOX

[Q] Virginize I9505

Hello!
I've read this post http://forum.xda-developers.com/showthread.php?t=2265477 but I'm still unable to find answers.
I need to send my phone to repairs because the proximity sensor is not working. I have flashed new modem, new kernel, new rom and Philz Recovery so it's pretty much voided the warranty.
What I want is to rever to stock EVERYTHING, I've searched over SamMobile and found this
Model: GT-I9505
Model name: GALAXY S4 LTE
Country: Chile (Entel PCS)
Version: Android 4.4.2
Changelist: N/A
Build date: Thu, 01 Jan 1970 00:00:00 +0000
Product Code: CHE
PDA: I9505VJUFNC2
CSC: I9505CHEFND1
MODEM: I9505VJUFNC2
Just flashing that and using Triangle Away will leave my phone virgin? What else do I need to do to make sure they won't find out my phone was rooted and flashed?
Thanks!
The unique you can't revert is KNOX if is actived in bootloader (KNOX:0x1). This mean u void ur warranty and, in theory, the service center should not fix ur phone. In practice, i tell u too that no all the service centers are same and maybe they can fix ur phone then.
*Answering ur question: Triangle away only reset the flashes u did in ur phone but not KNOX.

last modem without knox

hi,
i've lost the package for the modem without knox
i'm on gt-i9505
currently i've
AP: I9505XXUGNF1
CP: I9505XXUBMGA
CSC:I9505OXAGNF1
I'm from italy
netanalyzer said:
hi,
i've lost the package for the modem without knox
i'm on gt-i9505
currently i've
AP: I9505XXUGNF1
CP: I9505XXUBMGA
CSC:I9505OXAGNF1
I'm from italy
Click to expand...
Click to collapse
Hi,
Not sure what you want , modem do not have knox , the problem comes from using them with the rom bootloader
http://forum.xda-developers.com/showpost.php?p=50787570&postcount=2549
here is explaned and in the first post offers you different modems and the wifi fix
yeah sry i need the last working modem without knox
netanalyzer said:
yeah sry i need the last working modem without knox
Click to expand...
Click to collapse
Knox has nothing to do with modem...but anyhow
First firmware with knox was I9505XXUDMGG , so in your case the previous one without knox bootloader would be
Model: GT-I9505
Model name: GALAXY S4 LTE
Country: Italy
Version: Android 4.2.2
Changelist: 1081224
Build date: Thu, 11 Jul 2013 10:56:37 +0000
Product Code: ITV
PDA: I9505XXUBMGA
CSC: I9505ITVBMH1
MODEM: I9505XXUBMGA
This modem I9505XXUBMGA or any before this
In the link i gave you before you can find some...
tnx you i've found it
now i've
ap I9505XXUGNF1
cp I9505XXUBMH1
cscs i9505OXAGBF1
this is correct?
i need the lte file too
i've strange problem
screen off =>no signal when i switch on the screen signal is return
i've tried different rom (with full wipe) but the same issue
i've tried to change prefered network tipe 3g instead of lte but same problem
i'll become mad
so i can flash last 4.4.4 modem with the old bootloader without take the knox flag? i don't understand this point sry
i've fixed my issue
with this post
http://forum.xda-developers.com/showpost.php?p=55475958&postcount=528
use odin to flash it select phone
remember flash twice both file and untick auto reboot option

[Q] What does this debug info mean and why?

I got a refurbished Samsung Galaxy S4 i9505 but it had Netherlands (PHN) KitKat firmware on it. So I downloaded UK I9505XXUGNG8 BTU KitKat firmware from SamMobile and flashed it using Odin. I now get some debug info flash up briefly on every start up and in download mode. Why is it showing all this now and how do I remove it?
Code:
[COLOR="Red"]ODIN MODE[/COLOR]
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
[COLOR="Gray"]WRITE PROTECTION: Enable
eMMC BURST MODE enabled
REBOOT MODE = 0xc75e4628
POWER ON REASON = 0x1 (Key Power On)
CABLE: 0x00
DEBUG LEVEL: MID
BOARD REV: 11
MSM CHIP REV: 2
MSM HW ID : 0x71B0E1
BOOTLOADER VERSION : I9505XXEGNG8
BOOTLOADER RP SWREV : 4
SPEED BIN: 2
ACPU PVS: 2
Serial Num: 0x0######7[/COLOR]
Restore the PHN firmware. What happens?
S
Envoyé de mon SM-G130H en utilisant Tapatalk

Categories

Resources