[Q] Help Rooting P605 (VZW) - Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl

Just purchased and received Note 10.1 2014 edition.
Model # SM-P605V
Andriod Version 4.3
Baseband Version P605VVRUANB1
Build number JSS15J.P605VVRUANB1
Hardware Version P605V.02
Would love to Root (if possible). Having a difficult time finding instructions and a working method though. I think the Chainfire method was for older OS versions. I did try the CF method and all I get is Error messages in ODIN and on the Tablet itself. (ODIN shows: <ID:0/008> FAIL! (Auth) and the Tablet shows: secure magiccode check fail : recovery )
Is there a method out there yet for P605 with 4.3?
Please note that I have searched these forums high and low and still haven't seen a valid method to get my Note Rooted!

WorldOfJohnboy said:
Just purchased and received Note 10.1 2014 edition.
Model # SM-P605V
Andriod Version 4.3
Baseband Version P605VVRUANB1
Build number JSS15J.P605VVRUANB1
Hardware Version P605V.02
Would love to Root (if possible). Having a difficult time finding instructions and a working method though. I think the Chainfire method was for older OS versions. I did try the CF method and all I get is Error messages in ODIN and on the Tablet itself. (ODIN shows: <ID:0/008> FAIL! (Auth) and the Tablet shows: secure magiccode check fail : recovery )
Is there a method out there yet for P605 with 4.3?
Please note that I have searched these forums high and low and still haven't seen a valid method to get my Note Rooted!
Click to expand...
Click to collapse
BTW, the CF AutoRoot I tried is located here: http://download.chainfire.eu/380/CF-Root/CF-Auto-Root/CF-Auto-Root-lt03lte-lt03ltexx-smp605.zip

Try this it worked on p607
http://forum.xda-developers.com/showpost.php?p=53140560&postcount=12

NexVision said:
Try this it worked on p607
http://forum.xda-developers.com/showpost.php?p=53140560&postcount=12
Click to expand...
Click to collapse
Thanks, but I'm a bit worried about bricking... would rather have/see a "How To" specific to the P605V.

Sooo... nothing? My tablet is now asking to do an OTA and I don't want to do it if there is still a working method for my current firmware.

WorldOfJohnboy said:
Thanks, but I'm a bit worried about bricking... would rather have/see a "How To" specific to the P605V.
Click to expand...
Click to collapse
As long as you don't touch the bootloader, you're safe from bricking your tablet. You can always flash back the stock rom with Odin in auto download mode. Try to install TWRP recovery first, once it's working just flash supersu and your tablet is rooted.

AkiraBBQ said:
As long as you don't touch the bootloader, you're safe from bricking your tablet. You can always flash back the stock rom with Odin in auto download mode. Try to install TWRP recovery first, once it's working just flash supersu and your tablet is rooted.
Click to expand...
Click to collapse
OK, a couple of dumb questions:
1) To flash recovery, would I download the Zip file, go into Download Mode and use ODIN to flash?
2) If something did go awry, would I need to Download the firmware from SamMobile site, could I just use Kies, and finally, would it factory reset my tablet?
Just want to make sure I do it right and that I know the consequences if it goes bad. Thanks in advance.

1. Yes
2. It would (will) just fail. No need to do anything. Just reset. No it didn't reset your tablet.
Our bootloader is locked. I tried and failed. But give it a shot... it was an older version of Odin
Sent from my SM-N900P using Tapatalk

OK, so I see a few posts HERE that people are able to root using De La Vega. I think I may give it a whirl tomorrow and report my status after all is done. (Side note: Seems crazy to me that no one has created a DLV firmware package for the P605 and posted it so others can just flash via ODIN and finish the rest of the process.

WorldOfJohnboy said:
OK, so I see a few posts HERE that people are able to root using De La Vega. I think I may give it a whirl tomorrow and report my status after all is done. (Side note: Seems crazy to me that no one has created a DLV firmware package for the P605 and posted it so others can just flash via ODIN and finish the rest of the process.
Click to expand...
Click to collapse
Just wondering if you rooted your device? If not you could use Towelroot and it should works on 4.4 kk also without tripping Knox counter, good luck!
Sent from my Galaxy Nexus using Tapatalk

buhohitr said:
Just wondering if you rooted your device? If not you could use Towelroot and it should works on 4.4 kk also without tripping Knox counter, good luck!
Click to expand...
Click to collapse
Well, tried De La Vega root and it didn't work (everything up to and including the ODIN step worked, then it failed).
Downloaded Towelroot, ran it, and it worked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BTW, Knox is is still 0x0!

I can second that towel root worked on my 605v.
Sent from my LG-VS980 using Tapatalk

mllacey said:
I can second that towel root worked on my 605v.
Click to expand...
Click to collapse
I assume that (from your signature), it works on the 4.4.2 firmware as well as 4.3 (which is what I have)?
EDIT: Nevermind, I flashed 4.4.2 via ODIN and re-ran Towelroot and all is well. Now if I could only figure out how to update the binaries with a locked bootloader/stock recovery...

WorldOfJohnboy said:
I assume that (from your signature), it works on the 4.4.2 firmware as well as 4.3 (which is what I have)?
EDIT: Nevermind, I flashed 4.4.2 via ODIN and re-ran Towelroot and all is well. Now if I could only figure out how to update the binaries with a locked bootloader/stock recovery...
Click to expand...
Click to collapse
Well, all is good now! Here's what I did:
Flashed stock 4.2.2 ROM from Sammobile
Ran Towelroot
Downloaded latest SuperSU zip from Chainfire
Extracted superuser.apk and installed
When prompted to update binaries, chose to update using normal (non-recovery) method and it succeeded.

I'm glad that worked out.
Now I'm looking to figure out to load a customer recovery aka TWRP.
Sent from my SM-P605V using Tapatalk

Thanks guys... Been waiting for this.
+1 that it works

Related

[Q] Android Red Triangle

Hi all
I have phone Galaxy Nexus and I am having trouble updating ota where it after receiving the update must be recovery is stock and when I tried to retrieve recovery (With Galaxy Nexus ToolKit) does not work with me and show this is Death robot. I've access to Root and Recovery before ( CWM ) and Bootloader is open & I have a Custom Kernel
NOw How To Retrieval The stock recovery ??
sorry for my English
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ahmedsaber20005 said:
Hi all
I have phone Galaxy Nexus and I am having trouble updating ota where it after receiving the update must be recovery is stock and when I tried to retrieve recovery (With Galaxy Nexus ToolKit) does not work with me and show this is Death robot. I've access to Root and Recovery before ( CWM ) and Bootloader is open & I have a Custom Kernel
NOw How To Retrieval The stock recovery ??
sorry for my English
Click to expand...
Click to collapse
Manually flash the latest factory image, job done!
EddyOS said:
Manually flash the latest factory image, job done!
Click to expand...
Click to collapse
This is not a logical solution every time issue a new version of Android will be forced to do so and I have to take copies of the software, games and music and then restored again!!
What is the main reason for this problem?? And what is the solution
ahmedsaber20005 said:
This is not a logical solution every time issue a new version of Android will be forced to do so and I have to take copies of the software, games and music and then restored again!!
Click to expand...
Click to collapse
True, but it's always worth making a backup with Titanium to restore if required. That or make sure you keep the stock recovery after each build is released
EddyOS said:
True, but it's always worth making a backup with Titanium to restore if required. That or make sure you keep the stock recovery after each build is released
Click to expand...
Click to collapse
I always do that, but sometimes we need cwm formal and sometimes I need to air updates
4 Up
that is the stock recovery. something else on your phone is not stock and therefore it is failing.
ahmedsaber20005 said:
4 Up
Click to expand...
Click to collapse
1. Don't bump threads
2. Have you edited/deleted any system files? If so, there's your issue
EddyOS said:
1. Don't bump threads
2. Have you edited/deleted any system files? If so, there's your issue
Click to expand...
Click to collapse
No just root
Zepius said:
that is the stock recovery. something else on your phone is not stock and therefore it is failing.
Click to expand...
Click to collapse
I am have root&unlock bootloder&custom kernel+Busy box
That all
ahmedsaber20005 said:
I am have root&unlock bootloder&custom kernel+Busy box
That all
Click to expand...
Click to collapse
you have a custom kernel and busy box. those 2 things modify system files.
YOU ARE NOT ON A STOCK ROM.
the ota will never work until you return those things to stock (good luck finding all the things busy box changes.)
Zepius said:
you have a custom kernel and busy box. those 2 things modify system files.
YOU ARE NOT ON A STOCK ROM.
the ota will never work until you return those things to stock (good luck finding all the things busy box changes.)
Click to expand...
Click to collapse
If I uninstall this kernel and basybox and flash the stock recovery wiil be working ? Or I should to flash a new factory image?
ahmedsaber20005 said:
If I uninstall this kernel and basybox and flash the stock recovery wiil be working ? Or I should to flash a new factory image?
Click to expand...
Click to collapse
Just flash a system image, so simple
flash the factory images is the best. busybox is known to update system files and just uninstalling it will not revert the changes.
Thanks All For Help me put I have a little questions
1-Does Root Make Errors With OTA ?
2- If I want to flash image factory with Odin or toolkit?
3-If I install custom recovery and I want to back to stock can I do this with toolkit or other?
Thanks
1. Yes
2. Neither - learn to do it manually
3. Flash manually using the stock recovery in the factory image
EddyOS said:
1. Yes
2. Neither - learn to do it manually
3. Flash manually using the stock recovery in the factory image
Click to expand...
Click to collapse
Is there a way combines the powers of Root and ota Together ?? Will the program help on that?
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
No, that only masks root so some apps can run. It won't make any difference to the phone with regards to OTAs. Basically, if you're going to unlock the phone just go custom and ignore OTAs
EddyOS said:
No, that only masks root so some apps can run. It won't make any difference to the phone with regards to OTAs. Basically, if you're going to unlock the phone just go custom and ignore OTAs
Click to expand...
Click to collapse
please dont spread mis-information.
root alone does not stop you from getting OTAs, as i have root and nothing else and get OTAs just fine and they install just fine.. root does allow you to modify system files which can cause OTAs to fail.
what you did mention about rootkeeper is correct. it just masks root to allow certain apps to run and allow a easy way to return root after an OTA.

[Q] urgent please help I rooted my phone.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I got this after rooting my phone and I want to update the phone but I can't. Is there a possible fix? All I did was root and add 2 apps to the system folder (along with using some root programs that are Freedom and Link 2Sd)
Please Help
Unroot. Your phone. If you root your phone u can not make updates OTA.
Sent from my GT-N7100
You can upgrade software via odin
download latest firmware from Samsung-update
and flash it via odin and then root again
or use touchwiz custom roms with latest software
I unrooted and I still get that error ;/ any suggestions?
Download titanium backup
Clear data for two apps i.e.
Sysscope
Enterprise sysscope service
Carefully only wipe data nothing else
Reboot and ota update
Sent from my GT-N7100 using xda premium
thethiny said:
I unrooted and I still get that error ;/ any suggestions?
Click to expand...
Click to collapse
the problem is ur system status is "modified"..
its really very difficult to turn ur device normal once rooted.i tried everything from unrootin, clearing sys scope data and all that....but no success
i was in the same condition in which u currently are..then i thought there's no need to get my status normal..so i flashed a custom rom to get the latest update on my phone
Sent from my AweSoMe ☆♥Note2♥☆
mannyvinny said:
the problem is ur system status is "modified"..
its really very difficult to turn ur device normal once rooted.i tried everything from unrootin, clearing sys scope data and all that....but no success
i was in the same condition in which u currently are..then i thought there's no need to get my status normal..so i flashed a custom rom to get the latest update on my phone
Sent from my AweSoMe ☆♥Note2♥☆
Click to expand...
Click to collapse
Call me bad luck brian, I dropped the phone today and I broke the corner, my warranty covers that (1 month hardware warranty). So they need a non modified phone :/ also could you explain to me the flashing ot updates thing?
thethiny said:
Call me bad luck brian, I dropped the phone today and I broke the corner, my warranty covers that (1 month hardware warranty). So they need a non modified phone :/ also could you explain to me the flashing ot updates thing?
Click to expand...
Click to collapse
reset ur flash counter if its raised..download stock rom from sammobile of ur region.flash it via odin..that's it
Sent from my AweSoMe ☆♥Note2♥☆
mannyvinny said:
reset ur flash counter if its raised..download stock rom from sammobile of ur region.flash it via odin..that's it
Sent from my AweSoMe ☆♥Note2♥☆
Click to expand...
Click to collapse
I just rooted with busybox and didn't install any custom OS (I think rooting flashed a custom stock firmware? )
1 more Q, doesn't flashing erase everything?
mannyvinny said:
the problem is ur system status is "modified"..
its really very difficult to turn ur device normal once rooted.i tried everything from unrootin, clearing sys scope data and all that....but no success
i was in the same condition in which u currently are..then i thought there's no need to get my status normal..so i flashed a custom rom to get the latest update on my phone
Sent from my AweSoMe ☆♥Note2♥☆
Click to expand...
Click to collapse
well i just tried tday going back stock again with ketan pre rooted rom and then use triangle away 3.1 and all was fine at 1 go nothing more i did it was all normal , i have tried it before even and everytime it comes to normal and official as triangle away does it all for me, hard luck on ur side
thethiny said:
I just rooted with busybox and didn't install any custom OS (I think rooting flashed a custom stock firmware? )
1 more Q, doesn't flashing erase everything?
Click to expand...
Click to collapse
well after you flash stock firmware via odin just check ur status in download mode if its normal and official all good , if not enter stock recovery and wipe data .cache and if you have ever used any custom recovery then ur binary count can be solved using triangle away
thethiny said:
I just rooted with busybox and didn't install any custom OS (I think rooting flashed a custom stock firmware? )
1 more Q, doesn't flashing erase everything?
Click to expand...
Click to collapse
Busy box will set your device status to modified.
Boot into download mode and check your flash counter is zero. If not download and run triangle away.
Once that's done, use Odin to flash stock firmware and then factory reset.
Sent from my GT-N7100
I had the same issue. I use AllShare Cast a lot and it (and other DRM dependent) apps won't work with a status of "modified." As everyone's figured out, newer stock ROMs have kernel modifications that prevent using Triangle Away to reset the counter/status.
Here's what I found to be the easiest way to get back to stock. Go to Samfirmware or Samsung-Updates and find an older ROM that's at least a couple of months old and install it using Odin. Use Triangle Away to reset your counter. If it doesn't work the ROM you have installed is too new and has Samsung's kernel modifications. After that's done, use SuperSU's unroot function to unroot your phone. After that you can download the latest stock ROM and install it via Odin; your status will be unaffected. I did all this without reseting so my apps and settings were untouched.
BarryH_GEG said:
I had the same issue. I use AllShare Cast a lot and it (and other DRM dependent) apps won't work with a status of "modified." As everyone's figured out, newer stock ROMs have kernel modifications that prevent using Triangle Away to reset the counter/status.
Here's what I found to be the easiest way to get back to stock. Go to Samfirmware or Samsung-Updates and find an older ROM that's at least a couple of months old and install it using Odin. Use Triangle Away to reset your counter. If it doesn't work the ROM you have installed is too new and has Samsung's kernel modifications. After that's done, use SuperSU's unroot function to unroot your phone. After that you can download the latest stock ROM and install it via Odin; your status will be unaffected. I did all this without reseting so my apps and settings were untouched.
Click to expand...
Click to collapse
Will give it a shot
Edit:Luckily the "Status" thing glitched out and it ALWAYS shows Scanning... , no modified , no official, nothing. it lagged, so they agreed on fixing it. I'll send it later for repairs. thanks.
I have a Samsung Note 2 N7105 on stock EE UK firmware, rooted, and with chainfire's TriangleAway installed and used to reset the flash counter.
I can receive OTA updates via KIES and the phone's onboard updater, but I may have to restart the phone and run the update in the 5 minutes after reboot (during which TriangleAway suppresses superuser - tick System Modified Workaround in the settings), and also root after every update. It's a bit erratic. Depending whether I have triggered the modification scanner, my phone status may be Normal or Modified. Right now it's still Normal despite ~1000 hours of uptime.
It wasn't originally EE firmware, I had a couple of months of frankenstein CSC code. I flashed EE a couple OTA updates ago, then OTA/Kies'd it to its current state.
I dunno about AllShare Cast, I don't use it.
I've had people on here tell me that Samsung have to honour their warranty in the EU on rooted phones.
After lots of emails they sure as hell won't fix mine!
So thanks for the unrooting advice, I'll try this and try sending it back again
porcupineadvocate said:
and also root after every update. It's a bit erratic.
Click to expand...
Click to collapse
Use Mobile odin pro application for OTA or ROM flashing to keep device rooted.
So no need to root every time you change firmware.
sent from my GT-N7100. Press thanks if I helped..
BarryH_GEG said:
I had the same issue. I use AllShare Cast a lot and it (and other DRM dependent) apps won't work with a status of "modified." As everyone's figured out, newer stock ROMs have kernel modifications that prevent using Triangle Away to reset the counter/status.
Here's what I found to be the easiest way to get back to stock. Go to Samfirmware or Samsung-Updates and find an older ROM that's at least a couple of months old and install it using Odin. Use Triangle Away to reset your counter. If it doesn't work the ROM you have installed is too new and has Samsung's kernel modifications. After that's done, use SuperSU's unroot function to unroot your phone. After that you can download the latest stock ROM and install it via Odin; your status will be unaffected. I did all this without reseting so my apps and settings were untouched.
Click to expand...
Click to collapse
Just tried this,
1-When Flashing an Old (couple of months back) or any ROM other than 4.1.2 , I get a SAMSUNG loop.
2-I flashed the Stock XEF DME6 ROM. Now my baseband is different, was DMF1 , now DME4.
3-I keep on getting CP: Unknown when dialing *#1234# , and I always have no Signal , and Airplane mode is grayed out.
Any help?
You have lost your efs or imei code. Go to this thread.
sent from my GT-N7100. Press thanks if I helped..
MBariya said:
You have lost your efs or imei code. Go to this thread.
sent from my GT-N7100. Press thanks if I helped..
Click to expand...
Click to collapse
as long as I'm restoring my EFS, it is working, but as soon as I restart it happens again, and I must restore it again.
Please read out that guide and information from above posted link. Dr.ketan has provided information regarding why this happens.
sent from my GT-N7100. Press thanks if I helped..

[Noob] - How can I root this version? Please Help Me...

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Additional info:
*#1234#
AP: N7100XXUEMK9
CP: N7100XXUEMJ9
CSC:N7100COAEML2
A wonderfull day to all. I've been a member here wayback long ago. I know for myself that I don't contribute here a lot. It's because I'm not a very techie person.
But when my mom gave me her old Galaxy Note 2 and try to lurk around here about this phone. I've read a lot of good things about this phone and it's capabilities. Now I'm really getting interested about some things. But almost all of those Applications, Roms, Custom Roms, Recoveries, and Kernels reqiure root access, which my phone doesn't have. Hehehe. I tried to read a lot of post about rooting, but there's a lot of things and terms that confuses me, like MJ5, MK9, Baseband, Modem, Knox enabled, etc. I know that these things need to be considered when rooting. And I know that if I messed things up, my phone wil turn into an expensive paper weight. Hehehe.
The first thing I want to try is to root my phone, and try installing and uninstall system apps and enjoy rooted capabilities. So I'm hoping for somebody that can guide me how can I root this Model and Version. Hoping for your kind consideration guys. As I'm new about this rooting things.
Note:
AFAIK the Android version of this phone is previously 4.1.2 out from the box (not sure though). Then my mom got it updated to 4.3 and noticed that "Knox" is already in the app drawer. But if i open Knox it says: "You need to download and install this app. Downloading via mobile networks may result in additional charges depending on your payment plan." and there's an "Install" button that can be press. Do I need this app or do I need to install this? Is it safe? The phone doesn't have warrranty anymore. And I'm planning to Root, Install Custom Recovery, and Custom ROM in the futere. But I want to do it gradually.
Thank you very much guys for helping people like me.
asin_punk said:
Additional info:
*#1234#
AP: N7100XXUEMK9
CP: N7100XXUEMJ9
CSC:N7100COAEML2
Click to expand...
Click to collapse
Knox is kinda security for phones which when installed secures it (you can google what KNOX really is,I wont go in detail).Now to answer your main question.You can do two things either root your current 4.3 firmware or update to 4.4.2 and root it.Most of the people rooted 4.4.2 after getting the official stock firmware and flash it through odin. If you want to stick to 4.3 firmware and only root and remove unwanted apps and enjoy root privileges then follow this guide to root your phone and have a custom recovery on it.This will trigger knox which means warranty will be void and knox status will be 0x1 and it cannot be reversed.It doesn't harm the phone at all.If you decide to upgrade to 4.4.2 stock ROM and want to root it follow this guide.Flash SuperSu from here via your custom recovery.
singhpratik87 said:
Knox is kinda security for phones which when installed secures it (you can google what KNOX really is,I wont go in detail).Now to answer your main question.You can do two things either root your current 4.3 firmware or update to 4.4.2 and root it.Most of the people rooted 4.4.2 after getting the official stock firmware and flash it through odin. If you want to stick to 4.3 firmware and only root and remove unwanted apps and enjoy root privileges then follow this guide to root your phone and have a custom recovery on it.This will trigger knox which means warranty will be void and knox status will be 0x1 and it cannot be reversed.It doesn't harm the phone at all.If you decide to upgrade to 4.4.2 stock ROM and want to root it follow this guide.Flash SuperSu from here via your custom recovery.
Click to expand...
Click to collapse
Thanks man. I think i have to start reading those thread now. Once again, Thank you.
Maybe in the future I will just use this thread to ask more questions while I'm on the process of rooting my phone.
singhpratik87 said:
Knox is kinda security for phones which when installed secures it (you can google what KNOX really is,I wont go in detail).Now to answer your main question.You can do two things either root your current 4.3 firmware or update to 4.4.2 and root it.Most of the people rooted 4.4.2 after getting the official stock firmware and flash it through odin. If you want to stick to 4.3 firmware and only root and remove unwanted apps and enjoy root privileges then follow this guide to root your phone and have a custom recovery on it.This will trigger knox which means warranty will be void and knox status will be 0x1 and it cannot be reversed.It doesn't harm the phone at all.If you decide to upgrade to 4.4.2 stock ROM and want to root it follow this guide.Flash SuperSu from here via your custom recovery.
Click to expand...
Click to collapse
Hi again. Just followed your instruction. I chose to stick at 4.3 and have it started. I followed the instruction here http://forum.xda-developers.com/showthread.php?t=2531965. But after flashing Philz recovery and checked if its successful by trying the recovery, my stock recovery still appearing. Not the Philz recovery. I tried it twice. But still failed to have Philz recovery. And I checked my custom binary download, it says "Yes (2 counts)" and my knox is 1. After flashing thru odin, odin says "Pass" and my phone reboot automaticaly. But still no Philz recovery. Thanks.
asin_punk said:
Hi again. Just followed your instruction. I chose to stick at 4.3 and have it started. I followed the instruction here http://forum.xda-developers.com/showthread.php?t=2531965. But after flashing Philz recovery and checked if its successful by trying the recovery, my stock recovery still appearing. Not the Philz recovery. I tried it twice. But still failed to have Philz recovery. And I checked my custom binary download, it says "Yes (2 counts)" and my knox is 1. After flashing thru odin, odin says "Pass" and my phone reboot automaticaly. But still no Philz recovery. Thanks.
Click to expand...
Click to collapse
I forgot to mention that you need to uncheck "auto reboot" in odin before you flash the recovery file.So once odin says pass the phone will be still in download mode.Unplug the usb cable from laptop ,pull the phone battery out to turn it off then wait for sometime plug the battery back in and then reboot directly into recovery by pressing volume up plus home plus power button.Your newly flashed recovery that is philz should load up.Try it and let me know.If that works then flash supersu from recovery without booting into your ROM.Once superSu is flashed reboot your phone and let it boot into android.
singhpratik87 said:
I forgot to mention that you need to uncheck "auto reboot" in odin before you flash the recovery file.So once odin says pass the phone will be still in download mode.Unplug the usb cable from laptop ,pull the phone battery out to turn it off then wait for sometime plug the battery back in and then reboot directly into recovery by pressing volume up plus home plus power button.Your newly flashed recovery that is philz should load up.Try it and let me know.If that works then flash supersu from recovery without booting into your ROM.Once superSu is flashed reboot your phone and let it boot into android.
Click to expand...
Click to collapse
Woah! Thanks for your quick reply. I did what you said... And YES!!! I have a Philz Recovery Version 5.15 .0 now... I just skip the flashing of super su, because i want to use dr.ketan's Multitool Advance Version in rooting and in removing of bloatwares or dr.ketan's "Bloatware Remover"http://forum.xda-developers.com/showthread.php?t=2440951 to remove desired bloatwares only. Do you think it's fine? Thanks again.
But the sad part is...
Custom Binary Download: Yes (4 counts)
Knox Warranty Void: 1
Any harm with this status?
asin_punk said:
Woah! Thanks for your quick reply. I did what you said... And YES!!! I have a Philz Recovery Version 5.15 .0 now... I just skip the flashing of super su, because i want to use dr.ketan's Multitool Advance Version in rooting and in removing of bloatwares or dr.ketan's "Bloatware Remover"http://forum.xda-developers.com/showthread.php?t=2440951 to remove desired bloatwares only. Do you think it's fine? Thanks again.
But the sad part is...
Custom Binary Download: Yes (4 counts)
Knox Warranty Void: 1
Any harm with this status?
Click to expand...
Click to collapse
Only harm in tripping KNOX is that your warranty is void (so no samsung repair center will fix your phone for free).Regarding custom binary download when you flash official 4.3 or 4.4.2 STOCK ROM that would get reset.Yes you can use dr ketan's multi tool to reoot and deknox and debloat.Also I suggest you upgrade your philz recovery to 6.25.0 or 6.26.0 version just get that corresponding zip file of newer philz and flash it via your philz 5.0 and done.Enjoy your newly rooted note 2
singhpratik87 said:
Only harm in tripping KNOX is that your warranty is void (so no samsung repair center will fix your phone for free).Regarding custom binary download when you flash official 4.3 or 4.4.2 STOCK ROM that would get reset.Yes you can use dr ketan's multi tool to reoot and deknox and debloat.Also I suggest you upgrade your philz recovery to 6.25.0 or 6.26.0 version just get that corresponding zip file of newer philz and flash it via your philz 5.0 and done.Enjoy your newly rooted note 2
Click to expand...
Click to collapse
Wahahaha!!! Huhuhu!!! But before anything else I would like to say Thanks again sir.
Im going crazy... Upon learning around with my Newly Rooted Note 2... I came to the point that I need to reset the phone to factory... I made a full back up using Philz Recov. It is created under internal storage... I forgot to copy it to my Ext_SD...Then make a reset under settings menu... And it got stucked to Samsung Logo. I have to pull the battery out... Then I remember that I made a backup... I quickly boot into recovery, then I cant see my backup. Realized that it is also have been erased during hard reset. Waaahahahaha....
Unfortunately, I don't have a copy of my Stock 4.3 N7100XXUEMK9_N7100COAEML2_N7100XXUEMJ9-COA(Romania/Cosmote) ROM. And now I'm having a hard time to search for my 4.3 STOCK ROM that can be really downloaded. There are some links that has a false download file.
Do you have a link for that file? Sorry for wasting too much of your time. But thanks really.
asin_punk said:
Wahahaha!!! Huhuhu!!! But before anything else I would like to say Thanks again sir.
Im going crazy... Upon learning around with my Newly Rooted Note 2... I came to the point that I need to reset the phone to factory... I made a full back up using Philz Recov. It is created under internal storage... I forgot to copy it to my Ext_SD...Then make a reset under settings menu... And it got stucked to Samsung Logo. I have to pull the battery out... Then I remember that I made a backup... I quickly boot into recovery, then I cant see my backup. Realized that it is also have been erased during hard reset. Waaahahahaha....
Unfortunately, I don't have a copy of my Stock 4.3 N7100XXUEMK9_N7100COAEML2_N7100XXUEMJ9-COA(Romania/Cosmote) ROM. And now I'm having a hard time to search for my 4.3 STOCK ROM that can be really downloaded. There are some links that has a false download file.
Do you have a link for that file? Sorry for wasting too much of your time. But thanks really.
Click to expand...
Click to collapse
It might be difficult to get 4.3 stock ROM link.I can get you 4.4.2 FNG4 link .You would need to flash it via your existing philz recovery and you are set.
Dedoxed stock FNG4 post # 4
(no need to re root your phone,just follow instructions in post # 5).Or you can use dr ketan's tool to debloat etc.Good luck
singhpratik87 said:
It might be difficult to get 4.3 stock ROM link.I can get you 4.4.2 FNG4 link .You would need to flash it via your existing philz recovery and you are set.
Dedoxed stock FNG4 post # 4
(no need to re root your phone,just follow instructions in post # 5).Or you can use dr ketan's tool to debloat etc.Good luck
Click to expand...
Click to collapse
Hi again. The instruction says "Use TWRP", is it ok if I use PhilzTouchReco? Just to inform you, I just downloaded official 4.4.2 (Philippines Openline) from sammonile and my phone is previously Romania (cosmote), and i'm from Philippines. I can use Romania(Cosmote) here in Philippines. Is it ok if I flash 4.4.2 Philippines(Openline)? And once I'm in 4.4.2, can I still use dr.ketan multitool adv in rooting, deknoxed, debloat and etc? Thank you very much sir.

XT1064 Lollipop Root

Step 1: Download this: http://downloads.codefi.re/savoca/root/titan
Step 2: fastboot flash boot xt1064_lollipop_boot.img
Step 3: Flash SuperSU
http://imgur.com/jJO86tC
Unlocked boot-loader needed right?
surenzxx said:
Unlocked boot-loader needed right?
Click to expand...
Click to collapse
Of course.
savoca said:
Of course.
Click to expand...
Click to collapse
Do you know if any custom recoveries work on Lollipop at the moment?
surenzxx said:
Do you know if any custom recoveries work on Lollipop at the moment?
Click to expand...
Click to collapse
I'm using TWRP 2.8.0.1, only used it to backup/restore boot partition a few times and install SuperSU.
Did you have your boot-loader unlocked before your install of Lollipop?
I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?
EDIT: Nevermind; sorry for the mistake. It's booting back up.
surenzxx said:
Did you have your boot-loader unlocked before your install of Lollipop?
I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?
Click to expand...
Click to collapse
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.
savoca said:
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.
Click to expand...
Click to collapse
Thanks for your help. So we just flash the .img, flash SuperSu from the site, and fastboot flash recovery? Thanks again.
EDIT: Uh, I'm not booting past the unlocked bootloader screen after flashing your .img.
EDIT 2: I'm just a person that worries a lot. Gave it a few minutes to load and it works. Thanks. Really sorry to discredit you.
EDIT 3: Thanks man.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't seem to get root, I flash superSu after the boot img but still no root
edit: nevermind I figured it out thanks!
Hello.
Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc
Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?
Also have you tried modifying the hosts file? Does it work?
Sent from my XT1064 using XDA Free mobile app
Which Version of SuperSU are you flashing?
2.16?
Beta 2.17 or 2.19?
Greetz
savoca said:
I'm using TWRP 2.8.0.1, only used it to backup/restore boot partition a few times and install SuperSU.
Click to expand...
Click to collapse
Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."
who_ohw said:
Hello.
Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc
Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?
Also have you tried modifying the hosts file? Does it work?
Sent from my XT1064 using XDA Free mobile app
Click to expand...
Click to collapse
All I did allow the su daemon to init from the ramdisk - similar to how custom ROMs implement this.
luckiesjohnny said:
Which Version of SuperSU are you flashing?
2.16?
Beta 2.17 or 2.19?
Greetz
Click to expand...
Click to collapse
fathergweedo said:
Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."
Click to expand...
Click to collapse
Yes to the TWRP, (though we should make it an official build )
And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L
Thanks a lot.
I've tried it already with 2.19 and it worked fine.
savoca said:
All I did allow the su daemon to init from the ramdisk - similar to
Yes to the TWRP, (though we should make it an official build )
And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L
Click to expand...
Click to collapse
Gracias. Will get it later today...
ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?
Bobboman said:
ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?
Click to expand...
Click to collapse
If you're talking about the line in the bootloader, just ignore it. Your recovery still flashed.
yea i figured that out...however now i can't even boot my moto g to anything but the bootloader
thank god i have the 4.4.4 stock files on my laptop, time to get flashing...anyone got a link to the most recent version of supersu?
Will this work on XT1063 variant, or will it require a separate kernel patch?
blah i think i bricked my phone, i cant get past the moto logo, but i can get into the bootloader, not that helps anything

[TOOL][ZEN6] TOOL ALL IN ONE (Drivers|TWRP|Factory Image|Stock Recovery)

This is the Zenfone 6's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
getting the ZF6 next week, can I use this tool to install twrp and magisk and root in the current android version? from searching it seems to be android 10.
cwucwzz said:
getting the ZF6 next week, can I use this tool to install twrp and magisk and root in the current android version? from searching it seems to be android 10.
Click to expand...
Click to collapse
Yes you can
playing around with the app until i get the phone, but what steps would you take with the all in one tool to rooting the phone assuming the bootloader is unlocked?
cwucwzz said:
playing around with the app until i get the phone, but what steps would you take with the all in one tool to rooting the phone assuming the bootloader is unlocked?
Click to expand...
Click to collapse
Just click on "Recovery Flasher and Device Rooter", choose the TWRP (there is one for pie and one for Q), check "And Root it", choose a magisk version and start the procedure, the tool will automatically download the twrp, boot it, flash it and then will flash also magisk
Is this thing able to unlock the bootloader without using the ASUS method? Or lock it? That's what I'm most interested in.
admirdante said:
Is this thing able to unlock the bootloader without using the ASUS method? Or lock it? That's what I'm most interested in.
Click to expand...
Click to collapse
The unlock function can't be done with the tool for zenfone 6, the lock option i don't know if it will work or not, it's the only thing not tested
speaking of unlocking bootloader. is there any difference between the 2 methods explained in this link? cyano//removethis//genmods.org/how-to-unlock-asus-zenfone-6-bootloader
I would be VERY cautious trying to re-lock the bootloader with this tool.
If a guinea pig tester wants to give it a go and report back though, feel free to take that risk
All other functions will most likely work as expected.
It's also worth noting before anyone asks, the Trojan:Win32/Spursint.Q!cl (or similar) virus detected within the .zip is almost certainly false.
As always though, you use these sort of apps at your own risk.
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
molex329 said:
speaking of unlocking bootloader. is there any difference between the 2 methods explained in this link? cyano//removethis//genmods.org/how-to-unlock-asus-zenfone-6-bootloader
Click to expand...
Click to collapse
As far as I am aware there is only one way to unlock the bootloader, and that is to use the official tool from ASUS:
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
NOTE: Unlocking your bootloader will void your warranty.
Hello, has anyone tried this tool to root latest WW version (android 10)? Once rooted, would OTA updates work?
Jorgepfm said:
Hello, has anyone tried this tool to root latest WW version (android 10)? Once rooted, would OTA updates work?
Click to expand...
Click to collapse
Once the bootloader is unlocked you will no longer get OTA automatically. You can still download them manually to the root of your internal memory and install them.
mauronofrio said:
Just click on "Recovery Flasher and Device Rooter", choose the TWRP (there is one for pie and one for Q), check "And Root it", choose a magisk version and start the procedure, the tool will automatically download the twrp, boot it, flash it and then will flash also magisk
Click to expand...
Click to collapse
Is this still working for zenfone 6?
vernj123 said:
Is this still working for zenfone 6?
Click to expand...
Click to collapse
Yes
OK that's good news. Just putting out there but a nice little YouTube overview instructional video would be cool. In any case Thank you.
isthisadagger said:
Once the bootloader is unlocked you will no longer get OTA automatically. You can still download them manually to the root of your internal memory and install them.
Click to expand...
Click to collapse
Install manully will work even if the phone is rooted and twrp install on it?
Sent from my ASUS_I01WD using Tapatalk
baster72 said:
Install manully will work even if the phone is rooted and twrp install on it?
Sent from my ASUS_I01WD using Tapatalk
Click to expand...
Click to collapse
Yes
Can you help me a little as I can not do it, so what I am doing wrong ? - trying to install TWRP (chosen preoption Adroid Q from context) and Magisk 20.3 (for the lastest WW_17.1810.1911.110, Android 10)
Administrator: Flashing TWRP fails: Booting TWRP .... sending boot.img (22040 kb), Booting, Finished . Total time:: 10.902s and then waiting the TWRP boots .... but nothing happens
Jaripi said:
Can you help me a little as I can not do it, so what I am doing wrong ? - trying to install TWRP (chosen preoption Adroid Q from context) and Magisk 20.3 (for the lastest WW_17.1810.1911.110, Android 10)
Administrator: Flashing TWRP fails: Booting TWRP .... sending boot.img (22040 kb), Booting, Finished . Total time:: 10.902s and then waiting the TWRP boots .... but nothing happens
Click to expand...
Click to collapse
which rom you have actually? your bootloader is unlocked?
mauronofrio said:
which rom you have actually? your bootloader is unlocked?
Click to expand...
Click to collapse
The lastest stock, WW_17.1810.1911.110, Android 10. Bootloader is unlocked.
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
It works now, using MANUAL MODE and your unofficial TWRP - TWRP 3.3.1-24 Zenfone 6 (I01WD) by mauronofrio, thanks. Well, preoption Android Q (from context) and official TWRP did not work ...

Categories

Resources