Guest Frankish Posted August 19, 2015 Report Share Posted August 19, 2015 All of you who cannot root. Can you please post your software version from your phones about screen. Which method you have tried to root. Exact steps you have taken would be good. Screenshot of about screen would be nice too. Link to comment Share on other sites More sharing options...
Guest Frankish Posted August 19, 2015 Report Share Posted August 19, 2015 Possibly made some progress...So following a conversation with member Unable we have managed to get him rooted and install custom recovery. Now I'm not saying this will work for everyone however it worked for him after he tried for 4 days to root. After a reboot root would always be lost if he even got as far as it saying he was rooted. He started with a clean ROM install fully wiped. Download twrp recovery and put it on sdcard. Download flashify from play store but don't run it. Download latest Kingroot which worked for him 4.5.0.722. Run this app until you appear to have root. Reopen the app without rebooting make sure it says you have root access. Now run flashify and flash TWRP!Once this is done download SuperSU app from play store but don't run it. Download SuperSU latest update zip from https://download.chainfire.eu/396/supersu/ Reboot into recovery and install the SuperSU update zip. Upon rebooting he found SuperSU working and persisting over multiple reboots. Can someone try who hasn't been able to root and see if this works for you too!? Link to comment Share on other sites More sharing options...
Guest macbreakweeklyfan Posted August 19, 2015 Report Share Posted August 19, 2015 How about someone taking a logcat whilst rooting using MobileGo? Seems a good idea. I'd do it, except I am using my phone... and it's rooted and working well, so I don't want to unsettle it, haha. Link to comment Share on other sites More sharing options...
Guest Frankish Posted August 19, 2015 Report Share Posted August 19, 2015 Probably a good idea although the log would be very large it could be worth a look. And the same with King root. Link to comment Share on other sites More sharing options...
Guest macbreakweeklyfan Posted August 19, 2015 Report Share Posted August 19, 2015 Probably a good idea although the log would be very large it could be worth a look. And the same with King root.Just grep it :) Link to comment Share on other sites More sharing options...
Guest ohyesman Posted August 20, 2015 Report Share Posted August 20, 2015 Glad u managed to sort one out lol.I would have another blast myself but I'm now fully up and running as daily driver (new sim finally arrived) and everything is set up as I like and u can't be bothered spending another day going over the whole process again. No real need for root either atm. I will check this or if need to root in future though. Not sure if it would work as not getting successful with any of the three oneclick programs (I did use 4.1 kingroot though as recommended by chains for Supersu) and kingo root took bloody ages and still failedBelow is screen shot of build if helps for future or anyone elsr. Btw I've tried complete stock and stock + ota for all 3 and always on clean stock reinstall. Link to comment Share on other sites More sharing options...
Guest Unable Posted August 20, 2015 Report Share Posted August 20, 2015 Possibly made some progress...So following a conversation with member Unable we have managed to get him rooted and install custom recovery. Now I'm not saying this will work for everyone however it worked for him after he tried for 4 days to root. After a reboot root would always be lost if he even got as far as it saying he was rooted.He started with a clean ROM install fully wiped.Download twrp recovery and put it on sdcard.Download flashify from play store but don't run it.Download latest Kingroot which worked for him 4.5.0.722.Run this app until you appear to have root. Reopen the app without rebooting make sure it says you have root access. Now run flashify and flash TWRP!Once this is done download SuperSU app from play store but don't run it.Download SuperSU latest update zip from https://download.chainfire.eu/396/supersu/Reboot into recovery and install the SuperSU update zip.Upon rebooting he found SuperSU working and persisting over multiple reboots.Can someone try who hasn't been able to root and see if this works for you too!? Still runing smooth! Thanks mate!Nice tutorial Link to comment Share on other sites More sharing options...
Guest Frankish Posted August 20, 2015 Report Share Posted August 20, 2015 Glad u managed to sort one out lol.I would have another blast myself but I'm now fully up and running as daily driver (new sim finally arrived) and everything is set up as I like and u can't be bothered spending another day going over the whole process again. No real need for root either atm. I will check this or if need to root in future though. Not sure if it would work as not getting successful with any of the three oneclick programs (I did use 4.1 kingroot though as recommended by chains for Supersu) and kingo root took bloody ages and still failedBelow is screen shot of build if helps for future or anyone elsr. Btw I've tried complete stock and stock + ota for all 3 and always on clean stock reinstall. Ok that's strange as same hardware and same software as me so why wouldn't it work. Link to comment Share on other sites More sharing options...
Guest ohyesman Posted August 20, 2015 Report Share Posted August 20, 2015 (edited) Ok that's strange as same hardware and same software as me so why wouldn't it work.Yer, I've never had so many issues rooting a phone. I've tried like 10+ times total and closest I got was with mobilego saying rooted and installing supersu but unable to update binaries. Still most of the stuff I used back in the day rooted was for space saving and CPU management - not really needed now so only missing custom battery circle and replacement of bootscreen Edited August 20, 2015 by ohyesman Spelling Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 20, 2015 Report Share Posted August 20, 2015 Ok that's strange as same hardware and same software as me so why wouldn't it work. Nothing in 'About phone' actually shows any accurate (dynamic) information. It just reads from few hardcoded lines from build.prop and you could change those to whatever...I can't see how this would be a hardware problem anyway. These are software exploits that are used to gain root access. These are originally Portuguese devices that can't be rooted the same way? There's your software difference. Link to comment Share on other sites More sharing options...
Guest LiNe171 Posted August 20, 2015 Report Share Posted August 20, 2015 Nothing in 'About phone' actually shows any accurate (dynamic) information. It just reads from few hardcoded lines from build.prop and you could change those to whatever...I can't see how this would be a hardware problem anyway. These are software exploits that are used to gain root access. These are originally Portuguese devices that can't be rooted the same way? There's your software difference.Well, im Portuguese and root works fine on mine :P Link to comment Share on other sites More sharing options...
Guest macbreakweeklyfan Posted August 20, 2015 Report Share Posted August 20, 2015 No one ever seems to remember to post their build version which they were on when they rooted; for example, PRE-OTA or POST-OTA. Why? This could make all the difference when trying to work out why most people can root and a few can't. Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 20, 2015 Report Share Posted August 20, 2015 So Portuguese devices that have installed the OTA that was later pulled? Link to comment Share on other sites More sharing options...
Guest LiNe171 Posted August 20, 2015 Report Share Posted August 20, 2015 I tested both ways. Without OTA worked and with OTA worked too. Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 20, 2015 Report Share Posted August 20, 2015 I tested both ways. Without OTA worked and with OTA worked too.And you're again failing to mention if you're even talking about UK or PT firmware!? Was there even an OTA update available for the PT firmware in the first place? Link to comment Share on other sites More sharing options...
Guest ohyesman Posted August 20, 2015 Report Share Posted August 20, 2015 Mine is UK and tried pre and post ota update and I couldn't/can't root Link to comment Share on other sites More sharing options...
Guest LiNe171 Posted August 20, 2015 Report Share Posted August 20, 2015 And you're again failing to mention if you're even talking about UK or PT firmware!? Was there even an OTA update available for the PT firmware in the first place?I said i'm Portuguese on post above.. And yes, we have a OTA update on PT too. Link to comment Share on other sites More sharing options...
Guest KonstaT Posted August 20, 2015 Report Share Posted August 20, 2015 I said i'm Portuguese on post above.. And yes, we have a OTA update on PT too.Which makes absolutely no difference if you've installed the UK firmware to your device. Where can we download the PT OTA? What's the firmware version on after the OTA?Mine is UK and tried pre and post ota update and I couldn't/can't root OK, so UK devices also. Makes very little sense then (like many other things with this device).I'd really recommend sticking with devices that have unlocked/unlockable bootloaders. Unlock bootloader -> flash custom recovery -> flash SuperSU. That's how simple it should be. One update from ZTE/Vodafone and those vulnerabilities that are currently exploited are patched. Link to comment Share on other sites More sharing options...
Guest LiNe171 Posted August 20, 2015 Report Share Posted August 20, 2015 Which makes absolutely no difference if you've installed the UK firmware to your device. Where can we download the PT OTA? What's the firmware version on after the OTA?OK, so UK devices also. Makes very little sense then (like many other things with this device).I'd really recommend sticking with devices that have unlocked/unlockable bootloaders. Unlock bootloader -> flash custom recovery -> flash SuperSU. That's how simple it should be. One update from ZTE/Vodafone and those vulnerabilities that are currently exploited are patched.No, no difference. Already tested the stock rom from Paul and works. Well, you can't download it.. Just via OTA. MR01B version. Link to comment Share on other sites More sharing options...
Guest Roboffabike Posted August 21, 2015 Report Share Posted August 21, 2015 Still runing smooth! Thanks mate!Nice tutorialGot this to work, after about 4 attempts! I think the key for me was Flashify as rebooting to recovery always lost root Link to comment Share on other sites More sharing options...
Guest Umrtvovacz Posted August 22, 2015 Report Share Posted August 22, 2015 (edited) I had problem getting root. I found a way to do it:SOLVED: http://www.modaco.com/forums/topic/375680-guide-testedhow-to-get-reliable-root-and-twrp-on-su6-that-is-problematic/ Edited August 22, 2015 by Umrtvovacz Link to comment Share on other sites More sharing options...
Guest brackehill_mob Posted August 23, 2015 Report Share Posted August 23, 2015 This has been the worst phone I've ever tried to root. Both MobileGo and Kingroot failed because they lost root after rebooting. So I tried this method. Everything installed and worked until I rebooted - again I lost root. The SuperSU d/l'ed from the Play Store couldn't update the binaries even before I rebooted which I've never had before.In desperation I had a poke around in supersu 1.94 and compared it to v2.46 that I used on my Hudl2 (thanks again to @PaulOBrien!) and spotted lots of differences. I installed v2.46 via TWRP and it stuck!!! @Unable has a link to v2.46 in his thread hereIt might be worth updating the OP accordingly.Now to root my wife's one - wish me luck!! Link to comment Share on other sites More sharing options...
Guest LiNe171 Posted August 23, 2015 Report Share Posted August 23, 2015 This has been the worst phone I've ever tried to root. Both MobileGo and Kingroot failed because they lost root after rebooting. So I tried this method. Everything installed and worked until I rebooted - again I lost root. The SuperSU d/l'ed from the Play Store couldn't update the binaries even before I rebooted which I've never had before.In desperation I had a poke around in supersu 1.94 and compared it to v2.46 that I used on my Hudl2 (thanks again to @PaulOBrien!) and spotted lots of differences. I installed v2.46 via TWRP and it stuck!!! @Unable has a link to v2.46 in his thread hereIt might be worth updating the OP accordingly.Now to root my wife's one - wish me luck!!Try to install stock ROM again, download it from zte device website, put it on storage and install it by offline way.. After installing the stock ROM, install the new update via OTA, let it install then try to root with mobilego. Link to comment Share on other sites More sharing options...
Guest brackehill_mob Posted August 23, 2015 Report Share Posted August 23, 2015 Try to install stock ROM again, download it from zte device website, put it on storage and install it by offline way.. After installing the stock ROM, install the new update via OTA, let it install then try to root with mobilego. Had to do this with both phones!However MobileGo kept losing root when rebooting. But I was able to install TWRP using the commands in the OP of the TWRP thread and then installed SU via recovery as per my post 2 above this one. Much quicker than faffing about with Kingroot etc!Result :) Link to comment Share on other sites More sharing options...
Guest cRaZyzMaN Posted September 3, 2015 Report Share Posted September 3, 2015 i cant root properly, mobilego and kingroot not working baseband - P839V55B01kernel - 3.10.49vdf-995nb01PT_MR01bhardware - vodafone995NT3 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now