Related
hi, i just got my note 3 n9005 international a couple of days ago & now its time to root...you can say i am a little new to samsung because the last device i used was an s3 & that was a long time ago.....
i dont have any warranty so knox isnt that big of a concern unless it may cause some sort of damage to the phone...so far i have read..its only for warranty purposes like the flash counter for s3.
i was wondering if anyone would be kind enough to point me to rooting & everything else i need to do to install custom roms including recovery...
i tried to read through the instructions of root de la vega but i find it too complicated...so i was thinking of doing cf auto root....
thank you
linx1287 said:
hi, i just got my note 3 n9005 international a couple of days ago & now its time to root...you can say i am a little new to samsung because the last device i used was an s3 & that was a long time ago.....
i dont have any warranty so knox isnt that big of a concern unless it may cause some sort of damage to the phone...so far i have read..its only for warranty purposes like the flash counter for s3.
i was wondering if anyone would be kind enough to point me to rooting & everything else i need to do to install custom roms including recovery...
i tried to read through the instructions of root de la vega but i find it too complicated...so i was thinking of doing cf auto root....
thank you
Click to expand...
Click to collapse
Samsung issue a 24month warranty on the Note 3 (maybe country specific?) -
If KNOX isn't an issue for you and you do not mind tripping it, the CF-Auto is the way to go.
RDLV is complicated if you're lazy, but it does preserve KNOX status depending on your bootloader version, put in #*1234# into your dial pad and post the results. We can know if you can use RDLV.
However, if you want to flash a Custom ROM, then you will need a custom recovery, which will trip your KNOX (can't be done without) - on the Android dev section and Orginal Android dev section (in this sub forum) are some Custom ROMs and the instructions on how to do so.
I have used X-Note, Crash and am currently using AllianceROM, but there are a few others.
Just be careful with custom kernels until you're pretty confident cause you can bootloop and ruin your EFS quite easily (it is fixable 99% of the time tho, script is on here also)
EDIT : All you need is here pretty much
thank you for your reply & these are the stats
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005EVRDMJ4
also RDLV is way too complicated for me & besides i do plan to install a custom recovery so i think that defeats the point ....since you seem to have tripped knox, there hasnt been any kind of system issue i hope? this whole knox business gave me cold feet when i read about it...but so far as i can see..its just a flash counter.... could you tell me the tools i need to get started with? i already downloaded the usb drivers & odin 3.09..is there anything else i should need?
p.s. i was reading about "before or later MJ7 4" whatever...& i was wondering which of these was it refering to? ap? thank you
Once you trip the knox counter it makes no difference to the phone except not being able to use knox containers, and of course the warranty which you know. -- if you have the drivers and odin. Go grab cf-autoroot, run it thru odin and voila all done, similar for twrp or Cwm which ever you choose as your custom recovery (I use twrp) flash in odin and that's it all set.
Just make sure and I can't stress this enough, that you flash the right ROM for the N9005, and N900 doesn't work. - avoid doing restores with twrp for now also when you do a back up, some issues have arose recently and not sure of they're resolved or not yet.
Have fun man, just read everything about the ROM etc before you flash the odd one has FC's or NFC issues
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok so backing up & restoring with recovery is, for the time being, a no no? yes i will make sure to see if the roms are made for n9005 only....i will probably start off with omega roms as they are the 1st choice i had when i started modding the s3 ....thank you soo much mate for all the info...1 last thing to clear up is i am reading on developers talking about MJ or MK or whatever it is....are they talking about the build number i find in Settings/About??
1 thing i couldnt get a proper answer for...is how does 1 know they have the international variant of the n9005 anyway? normally if a n9005 is under some sort of carrier...the carrier logo would flash when booting up right? because thats what happens on my brother's note 3 n9005...when he boots up his phone..it shows SFR logo before going to the samsung bootanimation.....but on mine there is no such thing...the simple note 3 n9005 text then samsung boot animation & then straight to system...that means mine is the unbranded 1 am i correct?
linx1287 said:
1 thing i couldnt get a proper answer for...is how does 1 know they have the international variant of the n9005 anyway? normally if a n9005 is under some sort of carrier...the carrier logo would flash when booting up right? because thats what happens on my brother's note 3 n9005...when he boots up his phone..it shows SFR logo before going to the samsung bootanimation.....but on mine there is no such thing...the simple note 3 n9005 text then samsung boot animation & then straight to system...that means mine is the unbranded 1 am i correct?
Click to expand...
Click to collapse
Yeah yours is unbranded, only thing that may/will apply to you is region lock (which unless you're leaving the country your purchased your phone in isn't an issue at the start.
Although I see your CSC is EVR (if I recall correctly that is EE UK's firmware on board)
EDIT: Yes MK/ML are build numbers
no i dont have region lock..THAT i checked...so can i go forwards with all the rooting recovery & custom roms? i did find a orange core services apk on my apps manager under ALL tab..... also what original firmware can i roll back to incase anything goes wrong? any specifics?
linx1287 said:
no i dont have region lock..THAT i checked...so can i go forwards with all the rooting recovery & custom roms? i did find a orange core services apk on my apps manager under ALL tab..... also what original firmware can i roll back to incase anything goes wrong? any specifics?
Click to expand...
Click to collapse
Yup can go forwards. EVR (EE aka Orange/T-Mobile) have unlocked phones so yeah you won't have region lock. Which means yours is unbranded but carrier unbranded.
As for firmware, it depends on what region you are using? And what country you are in (you could use BTU (also UK, unbranded but EVR is ok also) - You are **now I say this depending on your country/region** OK on MJ7 or MK2 IF you upgrade since you're using a UK based ROM/CSC your network obviously supports it. However battery life is better on lower than MJ6. So it's your choice really.
Most custom ROMs are MK2 or ML2 atm I think, - Not sure if any upgrade your bootloader to MJ7 (if they do, you can't roll back any lower currently)
i just need a stock firmware so as i have a fallback if anything goes wrong...nothing more really as i plan to stick with custom roms...will this do?
http://samsung-updates.com/details/17028/Galaxy_Note_3_Snapdragon/SM-N9005/EVR/N9005XXUDMJ6.html
i am in Bangladesh so i am pretty confident that there isnt any rom for my region
yea i was wondering about the battery life myself...i dont know what version my brother's note is but his battery lasts noticibly longer than mine does....i was even planning on swapping batteries as i thought it might be a cell related issue
linx1287 said:
i just need a stock firmware so as i have a fallback if anything goes wrong...nothing more really as i plan to stick with custom roms...will this do?
http://samsung-updates.com/details/17028/Galaxy_Note_3_Snapdragon/SM-N9005/EVR/N9005XXUDMJ6.html
i am in Bangladesh so i am pretty confident that there isnt any rom for my region
yea i was wondering about the battery life myself...i dont know what version my brother's note is but his battery lasts noticibly longer than mine does....i was even planning on swapping batteries as i thought it might be a cell related issue
Click to expand...
Click to collapse
As long as your bootloader doesn't go to MJ7 - that firmware is OK, If your bootloader updates ( I think it may with the custom ROM) you can't roll back to MJ6, you can go to MJ7 or MK2 via BTU which will work for you since EVR works.
the latest omega is ML2 so by that measure...i wont be able to roll back to MK2 either & the latest on this thread http://forum.xda-developers.com/showthread.php?t=2459328 is MK2
linx1287 said:
the latest omega is ML2 so by that measure...i wont be able to roll back to MK2 either & the latest on this thread http://forum.xda-developers.com/showthread.php?t=2459328 is MK2
Click to expand...
Click to collapse
You can drop back as far as MJ7 ( I have at least when I've returned to stock due to mess ups) my build is MK2 atm
the bootloader only goes to MJ7 (last I checked, If it has changed then mine still lets me roll to MJ7)
csc seems a very complicated mess...GOD when did the mod friendly samsung go this crazy? the s3 was the most fun thing to mod...now this feels more complicated then Sony's!! :'( since my csc is EVR...is it possible to put BTU? i saw someone post this but didnt get any replies... http://www.usofttech.com/t128991.html
OH CRAP you said this BTU already...sorry my bad.... just trying to absorb all this
1 last query & i think i can start....with my current MJ6 build...can i do the cf auto root? or do i need to be on a lower build? if i can...then i think i will start or should i wait for the MJ7 to finish downloading & root that with cf auto root? & mate...thank you... you helped clear a lot of the confusions stopping me from modding this...now i think i can start things with a bit of confidence...thank you.... MUCH appreciated
linx1287 said:
1 last query & i think i can start....with my current MJ6 build...can i do the cf auto root? or do i need to be on a lower build? if i can...then i think i will start or should i wait for the MJ7 to finish downloading & root that with cf auto root? & mate...thank you... you helped clear a lot of the confusions stopping me from modding this...now i think i can start things with a bit of confidence...thank you.... MUCH appreciated
Click to expand...
Click to collapse
You can CF root straight away, - since you're triggering KNOX anyway it won't affect you. Then on with custom recovery etc, just keep MJ7 as your stock back up on your PC just incase. and IF you run into any issues with EFS (bootloops/no signal/wifi/baseband etc) use THIS It has saved me and quite a few others.
EDIT: And no problem man, glad to help, we all start somewhere with new devices
mate....the odin inside the cf root is 1.85 & the 1 got from google is 3.09 which should i use? & is PDA & AP the same thing because they are diff in the 2 versions of odin
linx1287 said:
mate....the odin inside the cf root is 1.85 & the 1 got from google is 3.09 which should i use? & is PDA & AP the same thing because they are diff in the 2 versions of odin
Click to expand...
Click to collapse
I use 3.07 personally - and flash using PDA -- Use the one with CF root if you're unsure
the phone is rooted ahhh feels like home again ....mate you said earlier that restoring backups on twrp causes system issues....i was wondering if this is true for just twrp or ALL current recoveries in general? which recovery would you suggest? also i was wondering about that script you told me about...the 1 about soft brick.... that fixes corrupt efs due to flashes yes? if so, does that mean it doesnt require my backup of efs?
linx1287 said:
the phone is rooted ahhh feels like home again ....mate you said earlier that restoring backups on twrp causes system issues....i was wondering if this is true for just twrp or ALL current recoveries in general? which recovery would you suggest? also i was wondering about that script you told me about...the 1 about soft brick.... that fixes corrupt efs due to flashes yes? if so, does that mean it doesnt require my backup of efs?
Click to expand...
Click to collapse
TWRP has issues *sometimes* there's a few posts about it around, I personally have had no problems and use TWRP fine, but I mentioned it because what works for one, doesn't always for another.
As for EFS backup, keep it just incase -- IT seems Android can rebuild the EFS again with that fire script. -- It's handy though, gotten a few out of the crapper including myself
I've been on 4.3 for a while now, hesitating to upgrade to KK because I've read some complaints about SD card issue and battery life.
Just want to ask, are they resolved or have workarounds developed already? Or should I still hold off upgrading?
Edit: Found a list of potential issues w upgrading. Can anyone (esp. SG users) confirm?
1. SD card problems
2. Force close for action menu, handwriting and Samsung keyboard
3. Unable to switch GMS/UMTS in the Preferred network mode menu
fterh said:
I've been on 4.3 for a while now, hesitating to upgrade to KK because I've read some complaints about SD card issue and battery life.
Just want to ask, are they resolved or have workarounds developed already? Or should I still hold off upgrading?
Click to expand...
Click to collapse
that problem is sovled. u should try 4.4.2 and feel it. more comfotable than 4.3
Sorry for bad eng
4.4.2 is noticeably snappier overall for me.
For all who have updated to KK, can you confirm the known issues in this thread (http://forum.xda-developers.com/showthread.php?t=2658315) I'm planning on following the tutorial in that thread, or does anyone know of a better way?
fterh said:
I've been on 4.3 for a while now, hesitating to upgrade to KK because I've read some complaints about SD card issue and battery life.
Just want to ask, are they resolved or have workarounds developed already? Or should I still hold off upgrading?
Edit: Found a list of potential issues w upgrading. Can anyone (esp. SG users) confirm?
1. SD card problems
2. Force close for action menu, handwriting and Samsung keyboard
3. Unable to switch GMS/UMTS in the Preferred network mode menu
Click to expand...
Click to collapse
fterh said:
For all who have updated to KK, can you confirm the known issues in this thread (http://forum.xda-developers.com/showthread.php?t=2658315) I'm planning on following the tutorial in that thread, or does anyone know of a better way?
Click to expand...
Click to collapse
I'm in Singapore, but my handset is export set (France firmware).
I was on MJ7 for 1 month+ (non-rooted), and just upgraded into KK 4.4.2 DBT NB7 Germany. And I rooted with CF-Autoroot with Philz CWM installed now.
So to be frank the link you have provided earlier, I have no idea, because I have never got a chance to root before upgrading to MJ7 4.3.
by the time I upgrade to MJ7, then I know I can't root without tripping its KNOX warranty bit.
So I have to bear with non-rooted until I set up my mind to upgrade to KK and finally I rooted my device on KK, and of course KNOX is tripped, but I don't care with it, as long as no other effects, other than warranty...
After using KK - DBT NB7 for 3 days, I can tell you, my SD card has no problem (only when I want to download and save to SD card from Dolphin browser, it doesn't recognize my SDcard because it is read as "external SD" instead of "storage\external SD"). Other than this, my SD card is just fine.
For problems no. 2 also never exists.
my network is running very well in 4G, H+, H, G. No problem at all.
But the happiest thing is... battery much much much better.
It is more reasonable to be used on KK, compare on earlier version of android for the battery.
And in sleep mode, for 4 hours, it dropped only 2%, things which I never found on my earlier device running on earlier android.
Cheer!
antique_sonic said:
I'm in Singapore, but my handset is export set (France firmware).
I was on MJ7 for 1 month+ (non-rooted), and just upgraded into KK 4.4.2 DBT NB7 Germany. And I rooted with CF-Autoroot with Philz CWM installed now.
So to be frank the link you have provided earlier, I have no idea, because I have never got a chance to root before upgrading to MJ7 4.3.
by the time I upgrade to MJ7, then I know I can't root without tripping its KNOX warranty bit.
So I have to bear with non-rooted until I set up my mind to upgrade to KK and finally I rooted my device on KK, and of course KNOX is tripped, but I don't care with it, as long as no other effects, other than warranty...
After using KK - DBT NB7 for 3 days, I can tell you, my SD card has no problem (only when I want to download and save to SD card from Dolphin browser, it doesn't recognize my SDcard because it is read as "external SD" instead of "storage\external SD"). Other than this, my SD card is just fine.
For problems no. 2 also never exists.
my network is running very well in 4G, H+, H, G. No problem at all.
But the happiest thing is... battery much much much better.
It is more reasonable to be used on KK, compare on earlier version of android for the battery.
And in sleep mode, for 4 hours, it dropped only 2%, things which I never found on my earlier device running on earlier android.
Cheer!
Click to expand...
Click to collapse
If I try to update to KK while keeping root and face problems, I can always just flash "normally" through desktop Odin (no more root) and root using CF autoroot, and everything will be fine, just that root is tripped right?
Hello
My S4 got lollipop this weekend, (I9506XXUDOA6) and i want to root it without tripping knox. Is there any way to do this? Ive tryed towelroot or kingoroot but nothing worked
thanks in advance
I'm not 100% sure, but I don't believe you can downgrade the Android 5.0.1 modem to an earlier version and root using Towelroot. CF Autoroot still works, but it will trip Knox.
Yes thats the case.. I dont want to trip knox and i wont try to downgrade the modem.. Ok maybe patience is what i need
Im just facing some curious lags on my phone that have no sense... For example in the recent apps, on facebook, on messenger, and on swiftkey keyboard.. But i have to admit that battery is at its best. On kitkat with normal use, the phone was dead for about 20 hours, and now on lollipop for about 2 and a half days i guess? Does anyone know how to fix those lags or minimize them?
My main concern, and something I'll have to do further research into, is whether I'd lose my SIM unlock on an upgrade. I used RegionLock Away to unlock my S4 after repairing it. The unlock survived the restoration of Android 4.4.2, but I have my concerns as to whether it would survive an upgrade to 5.0.1. Especially as downgrading the modem apparently is not possible.
It might simply be easier for me to find a custom Touchwiz ROM and install it instead, but there aren't many of them as of yet.
Can anyone confirm that there is no way to saferoot a s4 lte-a with official lollipop?
Hi Guys,
New to this device, but not new to Android... Read all over the web, various sites (esp this one) about this device and seeing mixed views/comments. Some saying its possible, others saying it will brick or flag the Knox.
Is it possible to downgrade this phone (G900F) currently on the latest 6.0.1 stock rom. But was wondering if I could try either official stock of 4.4.2 or 5.1.1 of this device.
Or due to this bootloader, is it likely to brick or even trip Knox?
Thanks, Lister
Lister Of Smeg said:
Hi Guys,
New to this device, but not new to Android... Read all over the web, various sites (esp this one) about this device and seeing mixed views/comments. Some saying its possible, others saying it will brick or flag the Knox.
Is it possible to downgrade this phone (G900F) currently on the latest 6.0.1 stock rom. But was wondering if I could try either official stock of 4.4.2 or 5.1.1 of this device.
Or due to this bootloader, is it likely to brick or even trip Knox?
Thanks, Lister
Click to expand...
Click to collapse
Official stock ROMs shouldn't trip Knox because they are, ummm, official.
I think the G900F bootloader is unlocked.
Sent from my Samsung SM-G900I using XDA Labs
Why downgrade in the first place..... ? 6.0.1 is way better than previous FWs...
Hi @Dirty Flasher,
Yeah, that's what I thought... It's all stock, so all should be good... But I've read reports saying it will trip Knox as since a certain version of Marshmallow, the bootloader has been locked to only go with future firmwares and not allow downgrades. I assume to prevent people restoring to the older firmware (with bootloader) which was unlocked, that allowed rooting without tripping. But some say it will trip, others say it will not... I'm confused, and wondered if anyone has tried this, and what the outcome was... Don't want to trip Knox unnecessarily... if someone has already tried and tested it.
Dirty Flasher said:
Official stock ROMs shouldn't trip Knox because they are, ummm, official.
I think the G900F bootloader is unlocked.
Sent from my Samsung SM-G900I using XDA Labs
Click to expand...
Click to collapse
Hi @Zlate2255,
I got this device when it was already one 6.0.1, so I missed seeing it go through the various stages. I would like to see how it used to look like and work. As there are some features that have been removed since, such Face Unlock and Iris tracking when viewing pages. Whilst the latter is still there burried away, it barely works, so should be removed completely. But would just be nice to see what it did look like.
Zlate2255 said:
Why downgrade in the first place..... ? 6.0.1 is way better than previous FWs...
Click to expand...
Click to collapse
Thanks, Lister
With my G900W8, I could downgrade to 4.4.2 with very-first firmware for G900W8 (NCG). Just try the earliest version of 4.4.2 and then upgrade back to 5.1.1
You can downgrade the g900f to every firmware (if unlocked) you want. On some s5 devices who have a locked bootloader like the at&t version there have been reported some problems.
Therefore, you shouldn't run into any problems while downgrading.
If you want some pro and cons to the firmwares:
Kitkat:
+ dark design (the touchwiz apps like contacts)
+ more battery friendly than marshmallow
- less security due to no security updates
- you might run into some minimal bugs, for example on wikipedia you sometimes have to reload the page to watch pictures (at least on mine)
- no app permissions can be removed (only with root and app ops)
Lollipop:
Honestly, I havent used this one that much, but here you have a white design with the different statusbar and pull down menu, better security (but not as good as on marshmallow) and the material design, but slightly worse battery time.
Marshmallow:
+ OTA Updates still available, best option for security
+/- White design, material design
+ new icons (but tbh not a real deal)
- less battery friendly (atleast for me even tho doze is enabled on marshmallow)
So yeah, choose what you want
And be sure that you have an unbranded device (check your csc) before downgrading/updating.
Hi @tm60405,
Wow, what a fantastic post... Thank you, exactly what I was looking for, and thanks for your reviews of each rom too.
- appreciate that, cheers
Quick question, how do I know if my Bootloader is unlocked??
Its a G900F (UK) was originally on the Three network, however I've flashed it to pure stock BTU, and to the EE network and back to stock BTU (all Marshmallow roms).
So where am I looking, or how do I know if the Bootloader is unlocked? Also, what am I looking for in the CSC info...??
Many thanks, Lister
Install the app called phone info from the play store.
Then, you swipe to the csc code and you can see your info and remember the csc you are on.
If it is BTU, you can install another firmware based on BTU without problems. But even if you don't have BTU, you can try installing BTU because it doesn't contain much bloatware. In the worst case, you just install the firmware with the csc you had before.
Then, follow the instructions on sammobile.com and there will be no problems during the installing process.
After downgrading, you might get a bootloop. Then, you have to factory reset your device, so get the data from the internal storage elsewhere BEFORE the installation.
And if the download takes too long, try another browser like opera, for me it takes around 1 hour only instead of 4-5 hours on chrome.
If you might have another problem while installing the firmware, say so.
Ok, I bought a new Verizon S5 in July of 2015. I rooted it a couple days later using Towelroot. The CID is 11, so it has a locked bootloader. I never had a single issue with the phone, and honestly, never thought about doing any updates, as it just kept chugging along dependable every day. I recently retired the S5, as I bought a mint, used Note 4 and fell in love with it. I am getting ready to sell the S5, but want to fully update it to 6.0.1 Marshmallow DQH2. I am not worried about losing root, as I am selling the phone, and will probably remove root anyway. I have a few questions though:
1) Can I update from Kit Kat all the way to Marshmallow and the latest update, or do I have to do it in increments?
2) Is it easier to update, then remove root?
3) What would be the easiest way to update to DQH2?
4) Since its rooted, can I just download the stock DQH2 firmware and flash it in Odin and go from KK to MM?
4A) If it can be flashed as stated above, will I lose root?
4A-1) Is there a rooted DQH2 firmware that can be flashed?
Thanks in Advance!!!
0) Check if Reactivation Lock is turned OFF.
...
4) Flash this DQH2 and it will erase everything, including root.
4A) Yes.
4A-1) No.
Forget the rest of the questions.
P.S. The first boot after flashing will take 10-15 min. so be patient.
bbsc said:
0) Check if Reactivation Lock is turned OFF.
...
4) Flash this DQH2 and it will erase everything, including root.
4A) Yes.
4A-1) No.
Forget the rest of the questions.
P.S. The first boot after flashing will take 10-15 min. so be patient.
Click to expand...
Click to collapse
Thanks. Whats the highest I can update, and retain root? I am re-thinking things now, as the package disabler app I was using and very fond of.... has been updated, and evidently does not work like it used to. I used this app on my Note 4, and was so happy with being able to disable all the bloatware and OTA etc... that I didnt bother to root the Note 4. I thought that if I lost root upgrading the S5, I would just install the same package disabler app, so it wouldnt be a problem, as thats really the only reason I root.... to get rid of bloatware. I may want to keep root now though
widowmaker17 said:
Whats the highest I can update, and retain root?
Click to expand...
Click to collapse
BPB1, Android 5.0.
You may also like the idea to install a custom debloated 6.0.1 ROM without root. If you've decided not to sell the S5.
Just another viewpoint if you haven't updated the phone yet: there are buyers who look primarily for phones with earlier versions of android, and it could actually increase the value/selling chance of your phone if you keep it on an earlier version and advertise it as such.
This gives the purchaser the opportunity to install the version they might want, especially since it's relatively difficult to find a Verizon S5 (or any Verizon Samsung phone) with 1. an unlocked bootloader and 2. an earlier version of Android such as KitKat installed.
I know this doesn't necessarily answer your questions, but it might be of benefit.