Database Users

[Q] Vodafone UK - anyone updated their software today?

I've got BMI6 (baseband) BMI7 (build) and I've been offered an update OTA today which I've postoned
Has anyone updated their Vodafone UK branded N3 in the last couple of days, what version does it go to?
I'm guessing the update will make it more difficult to root? I haven't rooted yet but I'm not sure how much longer I can resist the temptation!

You can root anytime mate. I'm on MJ7 currently. .. It's the bootloader that gets updated meaning you can't go back to old firmware. The bootloader gets locked from MJ3 onwards. You can root your phone without triggering knox...I wasn't bothered about it so I used the normal way ?
Sent from my SM-N9005 using Tapatalk

DO NOT TAKE OTA IF YOU WANT TO ROOT! It contains the new bootloader...
How to update to latest firmware without bootloader, but camera and wifi working:
Step 1)
Download URDLV (script, sd card files, odin v3.09) from its thread http://forum.xda-developers.com/showthread.php?t=2498850
Download your latest firmware from www.sammobile.com/firmwares
-> to do so type *#1234# in the dialer and put your csc minus the last 4 signs into the sammobile search box (sould look like n9005dbt) and download the topmost file
Put urdlv.bat and all its components in c:/urdlv
Win+r
Cmd.exe
Press Enter
Cd c:/urdlv
Urdlv full
Drag your firmware in the console window
press Enter
Wait until its done
Your files are in the output folder
Untar them with e.g. 7zip
Step 2)
Prepare:
NON-HLOS.bin <- extracted from original firmware
boot.img <- extracted from original firmware
cache.img.ext4 <- created by Universal RDLV
hidden.img.ext4 <- extracted from original firmware
modem.bin <- extracted from original firmware
recovery.img <- extracted from original firmware
system.img.ext4 <- created by Universal RDLV
then follow these steps:
install cygwin64 (with all default)
start it once
go to c:/cygwin/home/<username_u_have>
put mentioned files there
in cygwin:
tar -H ustar -c NON-HLOS.bin boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img system.img.ext4 > DMJ7.tar
md5sum -t DMJ7.tar >> DMJ7.tar
mv DMJ7.tar DMJ7.tar.md5
Step 3)
flash generated file with odin v3.09
step 4)
put the rootdelavega.sh and root_files on your internal storage
reboot
remove the files
reboot
RESULT: KNOX 0x0, binary official, latest firmware, root
leave a 'thanks' if i helped
SM-N9005 URDLV 0x0
XDA Developers 4 premium app

fz9999 said:
I've got BMI6 (baseband) BMI7 (build) and I've been offered an update OTA today which I've postoned
Has anyone updated their Vodafone UK branded N3 in the last couple of days, what version does it go to?
I'm guessing the update will make it more difficult to root? I haven't rooted yet but I'm not sure how much longer I can resist the temptation!
Click to expand...
Click to collapse
I'm on Vodafone UK. I rooted using URDLV method while on MI7 and won't update via OTA. If you're not already rooted, updating to MJ7 via OTA will mean you will flash a locked bootloader. This means you will trip your Knox warranty flag if you try to root after OTA.
This update looks like it's the MJ6 release according to what's available on sammobile.com
PDA: N9005XXUDMJ6
CSC: N9005VFGDMJ1
MODEM: N9005XXUDMJ4
If you're already rooted, the easiest method to update would be to use mobile odin pro 3.85. I.e. download the update zip file from sammobile.com, extract zip to tar.md5 and copy it to your phone storage. Then flash using mobile odin pro. This won't flash your bootloader but will update your phone software.
Sent from my SM-N9005 using Tapatalk

dsm52 said:
I'm on Vodafone UK. I rooted using URDLV method while on MI7 and won't update via OTA. If you're not already rooted, updating to MJ7 via OTA will mean you will flash a locked bootloader. This means you will trip your Knox warranty flag if you try to root after OTA.
This update looks like it's the MJ6 release according to what's available on sammobile.com
PDA: N9005XXUDMJ6
CSC: N9005VFGDMJ1
MODEM: N9005XXUDMJ4
If you're already rooted, the easiest method to update would be to use mobile odin pro 3.85. I.e. download the update zip file from sammobile.com, extract zip to tar.md5 and copy it to your phone storage. Then flash using mobile odin pro. This won't flash your bootloader but will update your phone software.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Have to admit thats far easier thsn mine
And working
Thumbs up!
hit 'thanks' if i helped you
SM-N9005 DMJ7 0x0
XDA Developers 4 premium app

@Killberty
Hi,
I finally took the pludge after a good week of research and tried your method, I was on URDLV MI7 and wanted to upgrade to MK2.
I followed your instructions but it appeared that I encountered a boot loop (3/4 times) so had to power off the phone and then Odin back the stock MI7 to recover the device. Yes I tripped. Phone was also very laggy, the camera didn't work and I got errors such as Process system isn´t responding (wait/ok). WIFI was ok. No SIM was present so I didn't check network connection.
After URDLV'ing MI7 again, I then used Mobile Odin pro to get to MK2 with no problems and the phone was back to its normal performance.
@GalaxHe also described a similar method in the Universal Root de la Vega v0.5 [ Root without tripping KNOX or Malware! ] thread (direct post link) but his method includes the additional files:
rpm.mbn sbl1.mbn sdi.mbn tz.mbn
I would like to ask please;
how long did your device take to install/reboot when you upgraded to the latest bootloader?
how many times did your device reboot?
why did you not include the same files that @GalaxHe did?
Many thanks
& thanks to @Chainfire for Mobile Odin as I was not confident in trying your method a 2nd time in an attempt to recover.
All good.

xitobor said:
@Killberty
Hi,
I finally took the pludge after a good week of research and tried your method, I was on URDLV MI7 and wanted to upgrade to MK2.
I followed your instructions but it appeared that I encountered a boot loop (3/4 times) so had to power off the phone and then Odin back the stock MI7 to recover the device. Yes I tripped. Phone was also very laggy, the camera didn't work and I got errors such as Process system isn´t responding (wait/ok). WIFI was ok. No SIM was present so I didn't check network connection.
After URDLV'ing MI7 again, I then used Mobile Odin pro to get to MK2 with no problems and the phone was back to its normal performance.
@GalaxHe also described a similar method in the Universal Root de la Vega v0.5 [ Root without tripping KNOX or Malware! ] thread (direct post link) but his method includes the additional files:
rpm.mbn sbl1.mbn sdi.mbn tz.mbn
I would like to ask please;
how long did your device take to install/reboot when you upgraded to the latest bootloader?
how many times did your device reboot?
why did you not include the same files that @GalaxHe did?
Many thanks
& thanks to @Chainfire for Mobile Odin as I was not confident in trying your method a 2nd time in an attempt to recover.
All good.
Click to expand...
Click to collapse
1) i did never upgard my bootloader thats why i didnt trip
2) once then i rebooted twice for the URDLV sd card part
3) sbl= secondary bootloader bl1 = bootloader1 so i dont inculde em, no bootloader updates
u might have skipped some step but i myself any many others can confirm it works...

Killberty said:
1) i did never upgard my bootloader thats why i didnt trip
2) once then i rebooted twice for the URDLV sd card part
3) sbl= secondary bootloader bl1 = bootloader1 so i dont inculde em, no bootloader updates
u might have skipped some step but i myself any many others can confirm it works...
Click to expand...
Click to collapse
Thank you for your reply.
Doh, @1) I didn't mean bootloader, I meant to say firmware.
I didn't upgrade my bootloader either and I didn't skip any steps. As I said, its all good, my phone is ok but who knows what happened in my case. Just had a few questions to see if I could understand it more.
Cheers.

xitobor said:
Thank you for your reply.
Doh, @1) I didn't mean bootloader, I meant to say firmware.
I didn't upgrade my bootloader either and I didn't skip any steps. As I said, its all good, my phone is ok but who knows what happened in my case. Just had a few questions to see if I could understand it more.
Cheers.
Click to expand...
Click to collapse
Hahah np and sorry for your knox :/
Maybe you had kies open or a lil bug in the cable or whatever (noone knows what samsung software does....) well i dont understand it at all as is worked for at leasr 5 people...
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app

[Q] Firmwareupdate after Root without triping KNOX or loosing root.

I successfully rooted my Note 3(N9005) with Universal Root de la Vega v0.5 ( wasn't alowed to post a thanks in that thread or leave my commend but donated and used thanks button ).
I got the Note 3 last Saturday, mission was to get root without trigger KNOX warenty bit in 14 days or send device back without comment. So far I succeed.
I keept my orginal Firmware Version before root, because I learnt from my Note 1(N7000) that putting the an actual firmware on the device and want to get root is a bad idea.
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is abad idea because it will trigger KNOX. I have also bad expirens with it on my Note 1. 2 times soft brick and once damaged chache partition, needed to use Odin(used v1.85) to get device back running. No succsessfull flash, so never used it again.
I now found what Mobile Odin should work with Knox 0x0: http://forum.xda-developers.com/showthread.php?t=2522729
I still not sure if Ishould use it.
Update over OTA or Kies will not work or update to newer bootloader and loose root.
My idea is to use latest Firmware and Odin( v3.07 version used for Root de la Vega) without flashing bootloader(I never done on my old).
With Odin I will loose root, so I need to root with Universal Root de la Vega method again?
Which partition are nessary AP,CP, CSC and UMS?
Of course not BL and EFS.
Ordered my Note 3 over Amazon. Strange is I got a dutch/netherland version.
I most likly want to have german version(downloaded N9005XXUDMK2_N9005DBTDMK2_DBT from SamMobile).
So far I know the diffrenz is in the cache so maybee I need to wipe cache.
So here also a question why can I flash cache and still have data on, which I need to wipe if I hasve problems?
Are this different partitions?
Could be the old bootloader makes problem with newer firmware?
Is were a save way to dowload actual firmware over Kies without starting the update(will install new bootloader).
Like disconnect device while downloading, can't try because my Note 1 has already actual Firmware and my Note 3 I don't want to risk.
On the Note 1 I could download firmware wit Kies but Update failed(I think because of root), but the I had the firmware and could use Odin.
On my old Note 1 I just flashed back to older firmware with Odin then something was wrong(warenty counter was already one).
I'm just not sure about this KNOX counter, should I use Odin with Universal Root de la Vega on actual Firmware or use Mobile Odin.
Or have you another save method to update with keep root.
Let me hear your comments.

Sony667 said:
I successfully rooted my Note 3(N9005) with Universal Root de la Vega v0.5 ( wasn't alowed to post a thanks in that thread or leave my commend but donated and used thanks button ).
I got the Note 3 last Saturday, mission was to get root without trigger KNOX warenty bit in 14 days or send device back without comment. So far I succeed.
I keept my orginal Firmware Version before root, because I learnt from my Note 1(N7000) that putting the an actual firmware on the device and want to get root is a bad idea.
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is abad idea because it will trigger KNOX. I have also bad expirens with it on my Note 1. 2 times soft brick and once damaged chache partition, needed to use Odin(used v1.85) to get device back running. No succsessfull flash, so never used it again.
I now found what Mobile Odin should work with Knox 0x0: http://forum.xda-developers.com/showthread.php?t=2522729
I still not sure if Ishould use it.
Update over OTA or Kies will not work or update to newer bootloader and loose root.
My idea is to use latest Firmware and Odin( v3.07 version used for Root de la Vega) without flashing bootloader(I never done on my old).
With Odin I will loose root, so I need to root with Universal Root de la Vega method again?
Which partition are nessary AP,CP, CSC and UMS?
Of course not BL and EFS.
Ordered my Note 3 over Amazon. Strange is I got a dutch/netherland version.
I most likly want to have german version(downloaded N9005XXUDMK2_N9005DBTDMK2_DBT from SamMobile).
So far I know the diffrenz is in the cache so maybee I need to wipe cache.
So here also a question why can I flash cache and still have data on, which I need to wipe if I hasve problems?
Are this different partitions?
Could be the old bootloader makes problem with newer firmware?
Is were a save way to dowload actual firmware over Kies without starting the update(will install new bootloader).
Like disconnect device while downloading, can't try because my Note 1 has already actual Firmware and my Note 3 I don't want to risk.
On the Note 1 I could download firmware wit Kies but Update failed(I think because of root), but the I had the firmware and could use Odin.
On my old Note 1 I just flashed back to older firmware with Odin then something was wrong(warenty counter was already one).
I'm just not sure about this KNOX counter, should I use Odin with Universal Root de la Vega on actual Firmware or use Mobile Odin.
Or have you another save method to update with keep root.
Let me hear your comments.
Click to expand...
Click to collapse
Ok, so download the DBT firmware you need to match your bootloader from Sammobile (*#1234# to check current firmware) -- You won't be able to go any higher firmware than your current without upgrading your bootloader without using Mobile ODIN as far as I know. However @Killberty may chime in here as he uses DBT also and may be able to help you better.

Sony667 said:
...
So now I want to put the actual firmware on device but don't trigger KNOX or loose root.
Mobile Odin is a bad idea because it will trigger KNOX.
...
Click to expand...
Click to collapse
Mobile Odin is a bad idea because you will lose root.
Mobile Odin PRO is a great idea - there is an entire thread about that and I have used it with zero problems. We don't know 100% certain that in future versions of firmware it will still work with knox 0x0 , but so far is OK.

So I more and more thing I will give Mobile Odin Pro a change.
Yes I have the Pro version already, but had the bad experience like I posted.
Sorry I forgot to post my current version, I thought I did.
AP: N9005XXUBMI7
CP: N9005XXUBMI6
CSC: N9005PHNBMI2
So I used N9005XXUBMI7_N9005PHNBMI2_PHN to make root(same version as original).
So you think it better to flash first to the N9005XXUBMI7 N9005DBTBMI1 to have german to have same bootloader.
And later go to actual N9005XXUDMK2 N9005DBTDMK2 using Mobil Odin Pro.
Or better first try N9005XXUDMJ7 N9005DBTDMJ4 which is confirmed to work with MOP.
I'm not sure about the change XXUB to XXUD but i think a change in the former digits I also have seen on my Note 1.
Maybe this is the bootloader.
About flash with Odin, I think you right, it Flash always the complete package, this is the reason I flashed on rooting firmware 2 times.
Because I had but the package on AP and CSC.
So the only way to flash without bootloader is to repackage like in Universal RDLV.

Sony667 said:
...
So you think it better to flash first to the N9005XXUBMI7 N9005DBTBMI1 to have german to have same bootloader.
And later go to actual N9005XXUDMK2 N9005DBTDMK2 using Mobil Odin Pro.
Or better first try N9005XXUDMJ7 N9005DBTDMJ4 which is confirmed to work with MOP.
...
Click to expand...
Click to collapse
I have MJ7 but do not know about MK2 - the URDLV + Mobile Odin Pro thread is probably the right place to ask.
http://forum.xda-developers.com/showthread.php?t=2522729

OK Thanks for the answer.
I'm currently reading the URDLV + Mobile Odin Pro thread, if after what it's not clear I will ask were.
Thanks.

If u dont wanna pay 5 bucks for the MOP, just quote me
10mins of work - save 5 bucks
EDIT: uhh mk2 is out ill use my method to flash it soon
EDIT2:
http://forum.xda-developers.com/showthread.php?p=47390175
This btw.
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

I have now flashed the MK2 with Mobile Odin Pro.
I had trouble to download the flash-kernel with MOP, so I downloaded it here in the forum.
The Problem was unstable WiFi with Firmware MI7.
With MK2 I get the full speed of my Internet connection(50 MBit/s,WiFi Interface is 65 MBit/s), the Note 1 didn't(about 5-10 MBit/s).
@Killberty: I have read your thread very nice, I would have used your method if MOP had failed.
It's very good to know the command to create firmware update package.
I had bought MOB over a year ago for my Note 1, but because of 3 times it failed, I newer used it again.
I flashed with Odin and inserted root(Super User + Busybox) with temporary CWM.
This is why I hesitated and asked back here, but after all the positive response I tried.
Only Samsung realy detects what the firmware is rooted, so no firmware downloads from Samsung, I have to trust SamMobiles.
And Knox is not running, they tell you before activation of knox what all your data(in Knox Software) are lost if firmware is modified(won't start).

So I give a status update.
I wanted to find out why I can't update and maybe try Knox.
The strange think was Kies has shown PHN version, but i flashed DBT version with MOP.
I thought maybe language version is in bootloader.
So I first flashed back to MI7 with MOP. Now I don't have Modem acces(no wifi, gms..) and device restarts regulary.
So I wanted to flash the N9005XXUBMI7 N9005DBTBMI1 with standard odin, but failed because of to small hidden partition.
Hidden update for PHN was 8MB and for DBT over 60Mb, I think hidden partion is about 10MB.
So this was why Kies still have shown PHN version, because it couldn't be updated.
So I flashed original N9005XXUBMI7_N9005PHNBMI2_PHN, this was working.
Because I can't flash DBT I downloaded latest PHN N9005XXUDMJ7_N9005PHNDMJ4_PHN without bootloader of course(Killberty method, thanks.).
So I find following out.
I can't change to DBT version, because of to small hidden partition. I need a PIT file to repartition and could probably brick my device I will check forum if someone have successfully done it(I mean successfully repartitioned to other language, not bricked the device).
Kies updates can still be done, problem was I had version language combination with didn't exit from Samsung.
Downgrade is not possible, because modem isn't running.
OTA updates are available on unrooted device, even with RDLV updated script, so it should be possible to unroot by put the system partition to original state except RDLV script and get root later back without re flash.
This will not help to get Knox running, because Knox will check bootloader and not run with old one.(state from Samsung https://www.samsungknox.com/en/blog/about-root-de-la-vega).

I now have changed to DBT version.
To do what I needed a pit file, hadn't found the information on XDA but I found it on another forum.
It's in german and very nicely explained:
http://www.android-hilfe.de/anleitu...note-3-debranding-alle-eu-modelle-zu-dbt.html
http://www.android-hilfe.de/anleitu...8844-anleitung-pit-file-backup-erstellen.html
If somone need this ifo I can try to translate.
So to create a backup of your N9005 pit file you open terminal Emulator on rooted device.
su
dd if=/dev/block/mmcblk0 of=/sdcard/My-N9005.pit bs=1 skip=17408 count=4244
So you have the pit file on your internal sdcard.
I have now attached 2 pit files.
Netherlands N9005_PHN.pit
German N9005_DBT.pit
The DBT has 10 times bigger hidden volume, so the data partition is smaller. The rest is equal.
You need to flash with Re-Partition and Firmware with old boot-loader.
Go in recovery and format data partition.
Now install the actual Firmware with RDLV(without boot-loader).

Glad u got sorted
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app

Success to root I9192xxbnb1 without tripping KNOX

Hi;
I have SG s4 mini duos with xxubnb1 firmware 4.2.2 (PDA: I9192xxubnb1; phone: I9192xxubnb1; CSC: I9192OJVBNB1).
I'd like to root without trip KNOX.
I tried several methods without success:
-saferoot not compatible phone (only MK4 i9192)
- Towelroot not compatible;
-srsroot found a method "root4" but when I check with rootcheker not have root;
-kingoroot after trying several fault, without success, he proposed at the end of injecting this "tar" file "wmrecovery_samsung_GT-I9192.tar" I refused. (could change knox).
This is the compressed file picked from temporaly kingoroot folder: (see in attached file)
After several readings on different forums, an idea occurred to me: doing the same thing using the "ROOT newest 4.4.2 without tripping KNOX" method that involves injecting a kernel that can be root, realize the root then reinject the original kernel.
I explain:
1) flashing the kernel 9192xxubmk4 "boot.img" in my phone;
2) root with saferoot
3) run the phone to see if there is not bug, if
4) flashing the original kernel and keeping the root.
What do you think of this approach?
Thank you

succes
dedelekid said:
Hi;
I have SG s4 mini duos with xxubnb1 firmware 4.2.2 (PDA: I9192xxubnb1; phone: I9192xxubnb1; CSC: I9192OJVBNB1).
I'd like to root without trip KNOX.
I tried several methods without success:
-saferoot not compatible phone (only MK4 i9192)
- Towelroot not compatible;
-srsroot found a method "root4" but when I check with rootcheker not have root;
-kingoroot after trying several fault, without success, he proposed at the end of injecting this "tar" file "wmrecovery_samsung_GT-I9192.tar" I refused. (could change knox).
This is the compressed file picked from temporaly kingoroot folder: (see in attached file)
After several readings on different forums, an idea occurred to me: doing the same thing using the "ROOT newest 4.4.2 without tripping KNOX" method that involves injecting a kernel that can be root, realize the root then reinject the original kernel.
I explain:
1) flashing the kernel 9192xxubmk4 "boot.img" in my phone;
2) root with saferoot
3) run the phone to see if there is not bug, if
4) flashing the original kernel and keeping the root.
What do you think of this approach?
Thank you
Click to expand...
Click to collapse
I just have my answer now : " it's a great et un grand succès".
I have do it just like I had explain in first thread, just use this script to prepare kernel mk4 for flashing with odin:
http://forum.xda-developers.com/show....php?t=2446269
Et voilà, root checker confirme the root and supersu update su binairies with stopping knox .
And in download knox 0x0 ........... yes.
Now I place my double sim to see if all is right, if not i'll flash in second time with the original kerne nb1.
Good night.

Simple, complete. It was my guide of root. Thank you so much.

[Q] Towelroot "match kernel to ROM"

I've read the guide on how to use Towelroot to root my S4 i9505. I have the GNG8 software so Towelroot fails.
http://forum.xda-developers.com/galaxy-s4/general/root-how-to-obtain-root-permissions-t2862768
The guide says at point (7): "flash via Odin your original kernel, matched to the ROM version you are using. You can find HERE a kernel stock collection."
So how do I match the Kernel?
It looks like I can't complete this anyway because Mobile Odin doesn't work yet with new 4.4 updates according to the Mobile Odin instructions. But I'd like to understand everything ready for when Mobile Odin release an update that works with my phone.

Just to clarify, your Knox flag is 0x0, i.e. not tripped?
To get your modem, dial *#1234# into the dialer. The AP should be the modem. From there you should be able to find it in the list. If not in the list, you can get it by downloading the stock ROM from sammobile.com or samsung-updates.com, using the information given through the dialer to search for it.

Hi, when I go into download mode I see that the Knox counter/fuse is 0. So I understand what I'm doing, why does this make a difference what the knox counter is at for the rooting?
So, following instructions, *#1234* gives me the following AP:
AP: I9505XXUGNG8
Going back to the rooting instructions, point (7):
"Reboot your phone into download mode and flash via Odin your original kernel, matched to the ROM version you are using. You can find HERE a kernel stock collection."
I follow the link and see the following file. Is this the one I should flash using Odin at that point?
Kernel_Stock_GNG8.tar.md5

The reason why I asked about the Knox fuse is this: if tripped there's no need to use Towelroot and CF-Autoroot could be used instead.
The file you mentioned is the correct one for your device.

If you're not concerned about tripping knox then use CF-Auto-Root.

Note 3 STock Firmware Rogers Canada SM-n900w8

Hello Everyone,
I have spent all last night looking for the stock firmware for my above listed phone and i have had no luck. Does anyone have a copy or provide me a link?
Also if you do, please advise how i install it.
I have found two last night but only one seemed to work via ODIN. I am not too knowledgeable but can get around. I found one but it is for T-Mobile and i had to upload files into BL / AP / CP / CSC which totally confused me. I am just use to uploading the file into AP. The phone turned on and looked stock but as mentioned it was for T-mobile and i am here in Canada. The problem with this Firmware is i get the following message "unfortunately, samsung keyboard has stopped".
This is the link to that firmware:
http://forum.xda-developers.com/showthread.php?t=2618633
I also went to Sammobile.com and downloaded:
http://www.sammobile.com/firmwares/download/26660/N900W8VLUCNB7_N900W8OYACNB7_RWC/
But the phone wouldn't even boot. I uploaded it using ODIN in AP.
Maybe i have the right file and i am doing it wrong.
Help would be appreciated.
Thank you!

hondss said:
Thank you!
Click to expand...
Click to collapse
1. The right file is the one you downloaded of Sammobile.com: HERE.
2. This .zip file contains one file inside .md5 or .tar. Unzip the .zip file and flash the .md5 via ODIN (like in the example pic attached)
3. Reflash the same firmware again like you was telling coz your phone don't boot. Let it boot till the final. Maybe you don't have wifi or can't call. You will have to dial *#1234# and have to appear this :
AP: N900W8VLUCNB7
CP: N900W8VLUCNB7
CSC: N900W8OYACNB7
4. Tell me something if not

Joku1981 said:
1. The right file is the one you downloaded of Sammobile.com: HERE.
2. This .zip file contains one file inside .md5 or .tar. Unzip the .zip file and flash the .md5 via ODIN (like in the example pic attached)
3. Reflash the same firmware again like you was telling coz your phone don't boot. Let it boot till the final. Maybe you don't have wifi or can't call. You will have to dial *#1234# and have to appear this :
AP: N900W8VLUCNB7
CP: N900W8VLUCNB7
CSC: N900W8OYACNB7
4. Tell me something if not
Click to expand...
Click to collapse
Awesome! Thank you very much as it worked!
So now that my phone is restored, is the phone still rooted? It was rooted before. I am trying to edit some features now on the phone such as DPI and screen layout but i am getting the feeling it isn't rooted as when i went into Titanium backup, the app says it "root access" Fail.

hondss said:
Awesome! Thank you very much as it worked!
So now that my phone is restored, is the phone still rooted? It was rooted before. I am trying to edit some features now on the phone such as DPI and screen layout but i am getting the feeling it isn't rooted as when i went into Titanium backup, the app says it "root access" Fail.
Click to expand...
Click to collapse
It's not rooted. You will have to root it again :highfive: