**** if you are looking for rooting your one m9 with android 6.0 , follow this simple guide of mine (http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354 ) ****
HELLO EVERYONE WITH A ONE M9
heres what you've got to do to unlock the monster in your device
1)unlock the bootloader
2)use a custom, more powerful recovery
3)root your phone
4)use a custom rom
you must have working adb and fastboot and htc drivers, if you dont know how to get these files, pls leave a reply.
Now We Will Learn 1,2,3,4
STEP 1:
NOTE:- YOU WILL LOSE YOUR DATA(Unless you have a dev edition htc onem9 , if u have one , skip step 1)
follow these steps:-
A]create a htc dev account here-https://www.htcdev.com/register/
B]go here , make sure ur logged in on htc dev website! -http://www.htcdev.com/bootloader/unlock-instructions/page-2
C] dont download anything ! from htc dev website.
D]connect ur phone to pc and enter download mode :- adb reboot download
E] type the following in cmd< fastboot oem get_identifier_token > look at the pictures on the web page, link in step B, as to how to mark and copy your token identifier code , then paste it in the space provided bellow.
you will get an email from htc dev with a file called Unlock_Code.bin
download it and in cmd type < fastboot flash unlocktoken Unlock_Code.bin>
now, use ur volume buttons to select unlock bootloader and press power button.
FACTORY RESET !
NOTE:- if you have problems following these steps , check out this bootloader unlocking video. im sure it will help you.
https://www.youtube.com/watch?v=Stl4A-ue5IE&app=desktop
DONE! bootloader unlocked
STEP 2:
Note: HTC one m9 is different from previous generation htc ones as it has a block based ota update system. in brief, any modification done to the system will result in an ota update faliure. keeping that in mind, follow my steps as it is
A] download the recovery.img here we are using a beta version of twrp.
http://forum.xda-developers.com/devdb/project/dl/?id=11987
after downloading, rename this file to twrp.img
Also download su bineries+ supersu (required for rooting later)
http://download.chainfire.eu/735/SuperSU/BETA-SuperSU-v2.48.zip?retrieve_file=1
put this file on ur sd card now!
B]go to download mode
type this adb command: adb reboot download
C]go to the directory where you have downloaded the recovery image
type in this fastboot command as soon as the phone is in download mode: fastboot flash recovery twrp.img
DONE!
STEP 3:
A]enter bootloader
B]enter recovery
C] TAKE A BACKUP. A COMPLETE BACKUP . MOST IMPORTANTLY <<<<SYSTEM>>>> DO NOT SKIP THIS STEP. THIS IS VVVVVVV IMP. IF U WANT TO TAKE AN OTA UPDATE EVER WITHOUT RUNNING ANY SORT OF RUU.
D]once thats done, go to advance->terminal and type this as it is:-
mount -t ext4 /dev/block/bootdevice/by-name/system /system
once this is done, go to mount and make sure system is selected.
now install the zip file i had asked you to download in the previous step.
DONE! You are rooted!
if You have forgotten to take a system backup, dont worry, you can find it here, you can flash it at the time of an ota,
https://www.androidfilehost.com/?fid=95916177934550813
STEP 4:
A]For a custom rom , download the customrom.zip file
browse the zip file and extract the file called boot.img
now , put the zip file on ur phone storage or sd-card.
boot to recovery and install the zip file. make sure to wipe cache,dalvik cache, system, and-secure before installing for a clean install, leave data as it is .
IF YOU ARE S-OFF, SKIP THIS STEP:-
B] reboot to download mode and type this fastboot command from the directory you unzipped your rom or extraced the boot.img:-
< fastboot flash boot boot.img>
reboot and enjoy your custom rom !
EXTRA SECTION (VVVVVV IMP)(TO TAKE AN OTA update)
if ever you get an ota update heres what you have to do . do not download it now. first follow these steps.
A)download stock recovery from here:-
https://www.androidfilehost.com/?fid=95916177934554373
rename it as recovery.img
B) download system.img from here ( only if you have not taken the system backup from twrp when in r/o state)
https://www.androidfilehost.com/?fid=95916177934550813
take only the system.emmc.win file from the twrp backup of the original system i had asked you to make before rooting your phone. if you dont have it? you will have to hunt for an ruu, well dont ask me how to do that .
put the system file and recovery.img and put the same folder. run cmd from that folder (right shift+right mouse click ->run command window here)
and type in
adb reboot download
fastboot flash system system.emmc.win / fastboot flash system system.img (depends if you are using a twrp backup or the system image you have downloaded from above)
fastboot flash recovery recovery.img
fastboot reboot
thats it. now download the ota update and once the installation is done, you will need to re-root. follow from step 2 again.
if you get a boot-loop, return to download mode, flash the twrp beta recovery and wipe cache and dalvik-cache. and then reboot , then go back to download mode and re-flash stock recovery.
hope ive helped you
sishirbaid said:
HELLO EVERYONE WITH A ONE M9
heres what you've got to do to unlock the monster in your device
Click to expand...
Click to collapse
Nice job ..thanks
Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now
Duncan1982 said:
Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now
Click to expand...
Click to collapse
If you need help I can start a IRC chat with you. Maybe I can try to help. Let me know.
aooga said:
If you need help I can start a IRC chat with you. Maybe I can try to help. Let me know.
Click to expand...
Click to collapse
That is very much appreciated, I have gone through everything, all SDK stuff installed as per HTC dev but the command is like if the adb and fadtboot is not there on my com, but I have installed.
I will wait as my M8 was so so so easy to unlock, M9 is just a headache.
My computer is off for tonight, I honestly have a sore head with trying to figure it out.
Again your reply and offer of help is appreciated.
Thanks Again, but for tonight "I give up" lol
Haha headache cleared so attempted again from scratch now HTC dev is not allowing me in, reset password and nope saying my login details are incorrect which is Bs as its the one they sent.
I really do now believe my M9 cannot be unlocked lol
That's KARMA.. nothing can be done - everything depends thru which hole you penetrated into this world in the first place..
P.S. Try different web browser though..
jauhien said:
That's KARMA.. nothing can be done - everything depends thru which hole you penetrated into this world in the first place..
P.S. Try different web browser though..
Click to expand...
Click to collapse
Haha Karma indeed, no I'm just going to say F it and be happy with S-On & locked, I managed the all my 12 devices without issue, rooting and unlocking for some, bar the Z2 which was the same headache as this M9 of mine lol
Karma has spoken and I am listening lol
Hello. Great guide. My question is about step 3, system backup for future OTA. I rooted my phone a few days ago, when no all things were clear. So, i made before flashing custom ROM only system backup not a full backup. I have system.emmc.win file saved. can i use it or a full backup is mandatory? thank you.
I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )
Security555 said:
I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )
Click to expand...
Click to collapse
Use TWRP 2.8.6.4
jauhien said:
Use TWRP 2.8.6.4
Click to expand...
Click to collapse
I do. TWRP 2.8.6.4, stock .15 rom
Use SuperSU v2.48 zip
jauhien said:
Use SuperSU v2.48 zip
Click to expand...
Click to collapse
Thanks! Installed 2.48 instead of 2.46 and everything is fine, I have root! Once again, thanks a lot! )
Duncan1982 said:
That is very much appreciated, I have gone through everything, all SDK stuff installed as per HTC dev but the command is like if the adb and fadtboot is not there on my com, but I have installed.
I will wait as my M8 was so so so easy to unlock, M9 is just a headache.
My computer is off for tonight, I honestly have a sore head with trying to figure it out.
Again your reply and offer of help is appreciated.
Thanks Again, but for tonight "I give up" lol
Click to expand...
Click to collapse
don't use google sdk for adb and fastboot! i would suggest this installation. Remember, install it system-wide.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Duncan1982 said:
Haha Karma indeed, no I'm just going to say F it and be happy with S-On & locked, I managed the all my 12 devices without issue, rooting and unlocking for some, bar the Z2 which was the same headache as this M9 of mine lol
Karma has spoken and I am listening lol
Click to expand...
Click to collapse
use chrome , access htcdev , select device not listed and follow the steps , if u want me to make the steps easier i shall post a reply, let me know
Duncan1982 said:
Nope I have spent the last two hours trying to unlock the boot loader using both tools found in the development section.
One my computer rejects and force closes.
The other just reboots into boot loader with it still locked.
HTC dev and command tool windows, comes up with the error can't run fast boot batch file or something to that effect.
All drivers installed.
Head is done in now
Click to expand...
Click to collapse
Remember, install it system-wide.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
also , install htc sync manager,for htc drivers. may be the drivers are outdated , m9 being a new device.mine worked fine with the newest htc sync manager.
Security555 said:
I have a little problem here, I tried several times to install superSU in recovery without success, should I give right to rewrite system partition or do I need to change something in boot.img. Every advice will be greatly appreciated )
Click to expand...
Click to collapse
ill post the link to the newer supersu.
cclhuzhou said:
The other just reboots into boot loader with it still locked.
{
"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"
}
Click to expand...
Click to collapse
i dint get ur problem ?
Haha headache cleared so attempted again from scratch now HTC dev is not allowing me in, reset password and nope saying my login details are incorrect which is Bs as its the one they sent.
I really do now believe my M9 cannot be unlocked lol
Click to expand...
Click to collapse
create a new account ! simple
note- htc account and htcdev account are different
ioni2ioni said:
Hello. Great guide. My question is about step 3, system backup for future OTA. I rooted my phone a few days ago, when no all things were clear. So, i made before flashing custom ROM only system backup not a full backup. I have system.emmc.win file saved. can i use it or a full backup is mandatory? thank you.
Click to expand...
Click to collapse
Did u take a system backup using twrp beta? if so , ur safe else if u used twrp (not beta) then you have taken a backup of system with the changed checksum. you are in urgent need of a stock system backup. let me know, ill host it if u need
and ya, only system.emmc.win is good enough if backuped via twrp beta .let me know as to what exactly you did.
Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------
Duncan1982 said:
Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
Click to expand...
Click to collapse
I want to add the creator of this thread is very helpful though and he offered to guide me through, I was stubborn and knew I could sus it out.
Duncan1982 said:
Woohoo all is sorted after watching a YouTube video, I then seen where I was going wrong.
Im now unlocked and rooted & will be s-off by the weekend.
It transpires I was the one doing things wrong
---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------
I want to add the creator of this thread is very helpful though and he offered to guide me through, I was stubborn and knew I could sus it out.
Click to expand...
Click to collapse
Thankyou for that ,I appreciated. It just another thing, could you post the link to the YouTube video you followed ? Thanks
Related
GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
MOD EDIT: This guide does not apply to the AT&T/Rogers/Telus variants of the Nexus S (i9020A). For those models, please refer to this guide.
Part 1
Download Android SDK release 13 click the file name android-sdk_r13-windows.zip (34 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Note: from SDK release 14 onward, Google removed the fastboot command, you'll have to maker the fastboot command yourself if you want to use the latest version of the SDK
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"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"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-5.0.2.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
droidmage said:
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
To simplify things with the Command Line, it's best to copy and paste the contents inside ..\android-sdk-windows\platform-tools to ..\android-sdk-windows\tools
that way you'll have all the necessary files in the same location to prevent errors
MIRROR:
since CW website seems to be down, here's a mirror for the Image file.
download the 7zip attachment, unzip and flash recovery.img (recovery-clockwork-5.0.2.0-crespo.img)
Good guide but i have a question,
didn't you miss the step about renaming the install-recovery.sh script
that reflash recovery if crc is wrong?
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Cubfan185 said:
Thank you sir, I was hoping for a good step-by-step guide for us first-timers.
Click to expand...
Click to collapse
thank you, that was the idea.
many of the GUIDEs we have here are usually aimed at people that already knows what to do, which usually leaves out all the 1st time owners of the phone.
it's fairly simple, the instructions are as simple as this
http://forum.xda-developers.com/showthread.php?t=884097
and you can choose any stock ROM to flash back
sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse
Alright, just did it successfully. I had a few problems when installing the SDK and using fastboot. The recovery image must have been corrupt a few times for me. I had to take the battery out because it was stuck at the Google screen. My heart skipped a beat at that point, I didn't want to brick anything. Also had to put a required .dll file in the tools directory and the drivers were giving me problems, but got it all figured out. Thanks again.
Edit: Any reason why root required apps are saying they don't have root access?
Will Google definatly release a full restore firmware of the current ROMS, something simular to an HTC RUU, or is it just something we're hoping they'll do?
silly question... which fastboot binary did you use? the one from the htc developer site?
onicrom said:
silly question... which fastboot binary did you use? the one from the htc developer site?
Click to expand...
Click to collapse
it is included in the Android SDK 2.3 ... read the step by step guide again
Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.
AllGamer said:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
Click to expand...
Click to collapse
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again
sinatosk said:
Hmmm I miss this post. Does this happen with 2.3.1 aswell and root will still be on after reboot?
If so. I'm rooting RIGHT NOW!!!
Thank-you
edit: I did some searching and found the answer ... there is a file at "/etc/install-recovery.sh". that restores your recovery back to stock upon reboot while still retaining root ( 2.3 and 2.3.1 ). As stated previously... you simply re-flash the recovery to get to the recovery again
Click to expand...
Click to collapse
yes, i actually like it this way, it keeps your original safe
Titanium Backup and few other apps are why i ROOT the phone as well.
after you fastboot over the CW recovery image and rooted, were you able to install Super User?
there is another trick, you can Install Super User first from Market
then repeat the steps to fastboot the clock work recovery image and get root access
jvblack82 said:
Great guide, I'm new to the SDK and adb and fastboot so this helped a lot. My phone crashed last night and I had to completely restore it. Biggest upset is I was racing my girlfriend to beat Angry Birds Seasons and now my save games are gone. Along with other app data and all my settings.
So the Nexus S is stock what I root phones to get to. I love the pure Google experience. Never had one completely crap out crash though.
I followed your guide to the tee and got it what I thought would be rooted. When I get to the end though I boot up and the ClockworkMod ROM Manager v3.0.0.2 says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Also Superuser app says there is an update available, then tries to install and says it can't. So it puts the update zip on my root of my storage. I boot into CMR and try to install that and it errors saying it's not there. But it is when I look is mass storage mode from my computer.
I boot into clockwork mod recovery just like your guide says the bootloader says unlocked. I don't get it. What did I miss? Only reason I want to root is to use Titanium backup. I really wish google had a better backup system for app data but they don't... yet. So I don't want what happened last night to happen again.
Thanks in advance,
JB
Nexus S, stock rom just want root access for backup.
Click to expand...
Click to collapse
Followed the guide to a T as well and did not get root access. But unlocking the bootloader, installing the SDK and learning about fastboot and such was very helpful. Using that, I used the automated batch file posted in this topic http://forum.xda-developers.com/showthread.php?t=882333 and it worked.
What to do if my Device Manager showed Android 1.0?
ykphuah said:
What to do if my Device Manager showed Android 1.0?
Click to expand...
Click to collapse
you select the correct driver to install the ABD support or Bootloader support, depending in which screen you have the phone on
just review the step by step guide, it is mentioned there
sinatosk said:
Nice guide.
The only thing that's making me hesitate to do root on my NS is reversing the whole process...
stock recovery for example. I know someone made a backup of it but some people are stating odd results of using that backed up stock recovery... wifi broke, missing apps, mobiles stuck on EDGE...
I'll wait until google releases a firmware that contains everything
Click to expand...
Click to collapse
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.
knytphal said:
If you're running 2.3.1 all you need to do to get back to stock recover is reboot the phone, because /etc/install-recovery.sh runs every boot and checks to see if the recovery is stock or not...if not it flashes it for you. So unless you've renamed the /etc/install-recovery.sh file you can easily get stock recovery.
Click to expand...
Click to collapse
... yeah I know. Made a post earlier today about it in this thread...
Hello
I have seen many of you have had problems with ROOT and Recovery for altev (Vk810) G PAD Lte Verizon only. So I have decided to help everyone who is having troubles with either of the two. Another reason to write this guide is that we are gearing up for some serious development in next weeks and months so I think many of you would find it useful. I shall update this guide if necessary. I recommend you read the second post of FAQ before proceeding with this guide.
I woudl not be responsible for any damage nor would be any developer or contributor at XDA. You understand the risks before proceeding on your own. All credits to the developers for their work and I am merely arranging everything in one place.
UPDATE Root 5.02 35A
I have successfully rooted lollipop 5.02 with SuperSU. Proof is given in the postHERE IS THE PROOF
Many thanks to my friend @roirraW "edor" ehT for his help, suggestions and his constant motivation that led me to keep trying!
All instructions are given here ROOT VK810 LOLLIPOP 35A WITHOUT DOWNGRADING
Root 4.4.2
FAQs
1.Make sure you are on latest firmware which is VK81024A.
2.If you are on any previous build especially 23A, I suggest you upgrade your device to the latest build.
3.If you unable to root it via brute force, repair your VK81024A firmware using Verizon tool because there's something wrong with your firmware.(modifications mostly)
4.Repairing would ensure it works. Brute force roots your device in first attempt so if it doesn't, you'll need to repair your firmware and do not waste time to retry.
Instructions :
1.Download stump root and install apk in your device. You can get it from HERE
You will need unknown sources checked in settings for installation.
2.Once installed. Select bruteforce. It'd say device is not supported but brute force works perfectly.
3.Once you run brute force, it'd ask you to restart your device. Do it manually.
4.After restarting your device, install SuperSU from market and run it. It'd ask to upgrade the binary, do it.
5.Uninstall stump tool.
Done.
Recovery :
It is a bit tricky to install it. Recovery requires aboot 4.2.2. Thus if you are on 4.4.2, you'll need to downgrade your aboot first.
FAQs
1.You'll need platform tools and a PC with Usb debugging on.
2.You must unlock developer options in settings by tapping build number 9 times in about device and then turn usb debugging on in developers tool.
3.Make sure you have platform tools(see attachment) and you have opened command prompt and cd to directory. (You can alternatively use ctrl+shift+right click in the directory of platform tool and select open command prompt here)
4.Paste aboot and twrp contents into platform tools folder.
Instructions :
How to downgrade and flash aboot4.2.2
If you are on 4.2.2, skip this step.
1.Download aboot 4.2.2 FROM HERE
2.Rename aboot4.2.2 to aboot. (recomove 4.2.2 from it only)
3.Place it in your internal memory/sd card/platform tools folder.
4.Run the commands.
HTML:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit
Installing TWRP
You will need to install twrp 2.7.0.1 first using loki support. After you are done, you can flash CWM or TWRP (2.7.0.2) zips from recovery.
Refer to last line for TWRP download links.
1.Open command prompt from PC in platform tools folder.
2.Paste contents of twrp 2.7.0.1.zip into the folder.
3.Type these commands
HTML:
adb push loki_flash /data/local/tmp/loki_flash
adb push twrp.lok /data/local/tmp/twrp.lok
adb shell
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/twrp.lok
exit
exit
adb reboot recovery
You would boot into recovery now
How to boot into recovery
To boot into recovery, you will need to first turn off your device.
Hold volume down+power key and switch it on.
Using volume keys, select factory reset data. (I know I know but this isn't a troll)
You will boot into recovery.
How to boot into download mode
To boot into download mode, you will need to first turn off your device.
Hold volume up+ connect it to the PC using a USB.
Change recovery to CWM
1.Download vk810 CWM recovery from the development forum. See Link Below for CWM
2.Flash it using twrp recovery.
To flash twrp.zip from cwm, you might need to toggle loki support in advanced in CWM menu
HOW TO FLASH KDZ FILES
1- Make sure you have installed the proper drivers in Post#2
2- Download LG Flash Tool 2014 from the attachment and extract them.
3- Paste the KDZ file in the LG Flash tool folder that you want to flash for best results.
4- Run the tool and select the file you want to flash.
5- Do not change any other value. (keep the TYPE as CDMA, Phone Mode as DIAG and Reset Time as 33000 )
6- Choose CSE flash (It wipes all the data as well. Normal mode is used for repairing the same firmware that you have installed and it might stuck on boot screen, just hold down power+ down key and do a factory reset. )
7- A new screen would appear. Just choose start
8- It might ask for administrator permissions, Allow
9- A new screen would that would ask for country and language. Completely ignore the language and country. You do not need to change it.
10- It might give you warning like " connection to server failed. Do you wish to cancel S/W Update. Complete IGNORE THIS. Do not even press OK on this screen. Just drag the window and you will see S/W progress.
11- Wait patiently. Do not disconnect the cable until done.
Special Thanks to @paperWastage for the following guide
ALL FLASHING GUIDE
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Click to expand...
Click to collapse
Please refer to this guide for all other problems.
CLICK HERE
The guide includes amongst many others
*non-booting device
*JB4.2.2 Issues
*KK4.4.2
*LTE not working
Some Useful Links
TWRP RECOVERY
CWM RECOVERY
Some Considerations /Frequent Issues:
1.To connect into usb debugging mode or your device to be detected by Verizon tool.
You must select PC connection as Internet connect>Ethernet. It took me a long time to realise that actually.
2.You can not boot into recovery via abd commands or key combination. See recovery post above how to boot into recovery once you have flashed it.
3. For me, old version of drivers which are included in verizon tools worked. I have also attached the latest drivers from verizon website as well.
Download Official Verizon Tools
http://d-h.st/g7UC with XP support (30 MB)
Download Latest Drivers
See attachment
The new lg root kit works for 24a
Sent from my vk810 using XDA Free mobile app
Can you provide me the link and proof?
juggamonkey said:
The new lg root kit works for 24a
Sent from my vk810 using XDA Free mobile app
Click to expand...
Click to collapse
@jparasita @roirraW "edor" ehT
I think you would be interested to see this
juggamonkey said:
The new lg root kit works for 24a
Click to expand...
Click to collapse
Hnk1 said:
Can you provide me the link and proof?
@jparasita @roirraW "edor" ehT
I think you would be interested to see this
Click to expand...
Click to collapse
@juggamonkey, I believe it if you tell me that you have been able to get the new one click root method (via GUI or script) to work on 24A, however like some people that no matter what even after a fresh flash of the 24A KDZ couldn't get Stump to work for them, Stump works for me on 24A but I've tried two or three times after two or three fresh flashes of the 24A KDZ in CSE mode to wipe everything and couldn't get the new root method to work with my VK810. It works just fine with my VS985 G3, however.
I would have to see proof to list it as a viable alternative for others, however. I know that before I had tried it, I and others mentioned it as a possible new way to root the VK810, however it just always hangs on "rooting...." for me (again, only on the G Pad 8.3 VK810 variant, works fine on my G3 VS985).
I'm not really willing to try it again on mine as two-three times is enough to eliminate it as a possibility for me when Stump works for me every time.
@Hnk1, thanks for this thread. I had seriously considered posting a comprehensive all-in-one thread with all the important info needed by VK810 owners but I'm so "AR" (read: perfectionist) that I I was overwhelmed providing all the links and proper credits. I'm an all or none kind of person and in my case it just had to be none.
Let's rate this thread 5/5 and call for it to be stickied (didn't notice if it is already).
roirraW "edor" ehT said:
Let's rate this thread 5/5 and call for it to be stickied (didn't notice if it is already).
Click to expand...
Click to collapse
I have asked the moderator of this thread to pin it, he hasn't however have read my message till yet. I hope it happens soon enough. Cheers for your feedback
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
There's the link what's the best possible way of of me showing proof that I rooted 24a with this tool?I'm currently on cm11 ....I had 24A ..brute force wouldn't work for stump root.. Hooked my tab up to the laptop ran this tool . it stuck at the download screen while rooting I held power down until it rebooted and I was rooted.. Downgraded aboot to 4.2.2 installed twrp and now I'm running cm11
Sent from my Nexus 6 using XDA Free mobile app
juggamonkey said:
There's the link what's the best possible way of of me showing proof that I rooted 24a with this tool?I'm currently on cm11 ....I had 24A ..brute force wouldn't work for stump root.. Hooked my tab up to the laptop ran this tool . it stuck at the download screen while rooting I held power down until it rebooted and I was rooted.. Downgraded aboot to 4.2.2 installed twrp and now I'm running cm11
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, that's the one I tried as well, both script and GUI versions. I totally believe you, though so no worries. I don't have time right now (I'm at work!) to think about how to prove it other than videorecording doing the whole process from start to finish, but I really don't expect that from you. I don't require the proof to believe you, though. I'm just saying I wouldn't tell someone to try that to root their VK810 unless I heard of it working for more than one person, or as a last ditch effort, of course.
Interesting, you say it was stuck at the download screen, did the script itself indicate it was done or was it stuck on "rooting..." just like it showed for me? If the script was stuck on "rooting..." for you too then I'll have to try again. Maybe I assumed that since the script never went beyond that point that it wasn't actually rooted, and I don't remember at this point if I did actually reboot and see if it was.
Thanks for the info.
I know it didnt finish in the GUI of the tool .can't remember exactly what it said but I believe it got stuck at rooting after rebooting into download .I just held power after I realized it was stuck in download mode and all was well
Sent from my vk810 using XDA Free mobile app
roirraW "edor" ehT said:
Yep, that's the one I tried as well, both script and GUI versions. I totally believe you, though so no worries. I don't have time right now (I'm at work!) to think about how to prove it other than videorecording doing the whole process from start to finish, but I really don't expect that from you. I don't require the proof to believe you, though. I'm just saying I wouldn't tell someone to try that to root their VK810 unless I heard of it working for more than one person, or as a last ditch effort, of course.
Interesting, you say it was stuck at the download screen, did the script itself indicate it was done or was it stuck on "rooting..." just like it showed for me? If the script was stuck on "rooting..." for you too then I'll have to try again. Maybe I assumed that since the script never went beyond that point that it wasn't actually rooted, and I don't remember at this point if I did actually reboot and see if it was.
Thanks for the info.
Click to expand...
Click to collapse
juggamonkey said:
I know it didnt finish in the GUI of the tool .can't remember exactly what it said but I believe it got stuck at rooting after rebooting into download .I just held power after I realized it was stuck in download mode and all was well
Sent from my vk810 using XDA Free mobile app
Click to expand...
Click to collapse
I can add a poll for the method. If it works for more than 5 people, I can add it in the guide.
What do you reckon?
Hnk1 said:
I can add a poll for the method. If it works for more than 5 people, I can add it in the guide.
What do you reckon?
Click to expand...
Click to collapse
That sounds like a good idea. Quote Todd Snider "64 percent of all the world's statistics are made up right there on the spot"...
Todd Snider:Statistician's Blues Lyrics
But really, yes, can't hurt!
OK, so the guide is not very n00b friendly...
I get to the part where I run from CMD from PC, and nothing happens. Just 'device not found' errors.
I've tried everything from copying everything in platform-tools to C:/ drive and TWRP in that folder, as well as C:/ drive.
I cannot get TWRP on this device. All that I have gotten so far from this guide is where I started which is that I cannot get custom recovery on my device.
I did however get ONE step further as the Terminal commands FINALLY WORKED on the aboot part. So now I am rooted, ran aboot commands, got supersu, etc.
Now I just need help with the TWRP part.
Please help !!!
---------- Post added at 02:11 AM ---------- Previous post was at 02:07 AM ----------
{
"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"
}
---------- Post added at 03:03 AM ---------- Previous post was at 02:11 AM ----------
Firs the guide tells me to upgrade from 4.2.2 to 'make sure I am on the latest firmware'.
Root
FAQs
1.Make sure you are on latest firmware which is VK81024A.
2.If you are on any previous build especially 23A, I suggest you upgrade your device to the latest build.
Then, the guide tells me if I was already on 4.2.2 (which I was, because after bricking the device, the LG tool auto put me there) to skip this whole section. Really? So first I should be on the latest firmware, and 2 seconds later find out, I should not be on the latest firmware?
How to downgrade and flash aboot4.2.2
If you are on 4.4.2.if you are already on 4.2.2, skip this step.
:/
I'm not being an ass, I am laughing, and I am extremely pleased with the guide, but it isn't n00b friendly. n00b friendly would mean a n00b could do it.
Thank you again!!!
Do u have correct lg drivers for your PC also do you have usb debugging turned on and when connected there will be a RSA box pop up on your tab to trust the PC select always trust PC and it should read your phone from the cmd prop type in adb devices and see if your device shows then
Sent from my Nexus 6 using XDA Free mobile app
SidedX said:
OK, so the guide is not very n00b friendly...
I get to the part where I run from CMD from PC, and nothing happens. Just 'device not found' errors.
I've tried everything from copying everything in platform-tools to C:/ drive and TWRP in that folder, as well as C:/ drive.
I cannot get TWRP on this device. All that I have gotten so far from this guide is where I started which is that I cannot get custom recovery on my device.
I did however get ONE step further as the Terminal commands FINALLY WORKED on the aboot part. So now I am rooted, ran aboot commands, got supersu, etc.
Now I just need help with the TWRP part.
Please help !!!
---------- Post added at 02:11 AM ---------- Previous post was at 02:07 AM ----------
---------- Post added at 03:03 AM ---------- Previous post was at 02:11 AM ----------
Firs the guide tells me to upgrade from 4.2.2 to 'make sure I am on the latest firmware'.
Root
FAQs
1.Make sure you are on latest firmware which is VK81024A.
2.If you are on any previous build especially 23A, I suggest you upgrade your device to the latest build.
Then, the guide tells me if I was already on 4.2.2 (which I was, because after bricking the device, the LG tool auto put me there) to skip this whole section. Really? So first I should be on the latest firmware, and 2 seconds later find out, I should not be on the latest firmware?
How to downgrade and flash aboot4.2.2
If you are on 4.4.2.if you are already on 4.2.2, skip this step.
:/
I'm not being an ass, I am laughing, and I am extremely pleased with the guide, but it isn't n00b friendly. n00b friendly would mean a n00b could do it.
Thank you again!!!
Click to expand...
Click to collapse
thank you for pointing out the mistake. Changes have been made. Now what just follow the recovery instructions.
If you are 4.4.2, then you need to have aboot4.2.2 and then carry on with recovery instructions.
Why do not you send me the screenshot of the errors you have faced.
Secondly , are you connecting your device in modem>ethernet mode else PC wouldnot be able to recognise it.
Have you enabled USB debugging in developer tools ?
What is your driver status ?
Hnk1 said:
thank you for pointing out the mistake. Changes have been made. Now what just follow the recovery instructions.
If you are 4.4.2, then you need to have aboot4.2.2 and then carry on with recovery instructions.
Why do not you send me the screenshot of the errors you have faced.
Secondly , are you connecting your device in modem>ethernet mode else PC wouldnot be able to recognise it.
Have you enabled USB debugging in developer tools ?
What is your driver status ?
Click to expand...
Click to collapse
I did include a screenshot in previous post.
After all steps have been completed, I open a CMD prompt from within Platform tools, and it just says 'device not found'.
If I install the ADB drivers it says ADB Daemon running on port 5087, and then says Device not found.
I have USB debugging enabled, I have tried every driver possible from default ADB to Verizon official, the computer can see the device, the RHA fingerprint key pops up and I agree, but no matter what when I type
adb push loki_flash /data/local/tmp/loki_flash
Nothing happens. Device not found.
SidedX said:
I did include a screenshot in previous post.
After all steps have been completed, I open a CMD prompt from within Platform tools, and it just says 'device not found'.
If I install the ADB drivers it says ADB Daemon running on port 5087, and then says Device not found.
I have USB debugging enabled, I have tried every driver possible from default ADB to Verizon official, the computer can see the device, the RHA fingerprint key pops up and I agree, but no matter what when I type
adb push loki_flash /data/local/tmp/loki_flash
Nothing happens. Device not found.
Click to expand...
Click to collapse
Try rebooting the PC. You can also try another USB port. If you're trying a USB 3.0 port, try a USB 2.0 port instead. Are you using the original cable?
Rooted 35A from Verizon. Instructions and details coming soon
Congratulations for rooting 35A_08 without downgrading to 24A or earlier first!
Hnk1 said:
Hello
I have seen many of you have had problems with ROOT and Recovery for altev (Vk810) G PAD Lte Verizon only. So I have decided to help everyone who is having troubles with either of the two. Another reason to write this guide is that we are gearing up for some serious development in next weeks and months so I think many of you would find it useful. I shall update this guide if necessary. I recommend you read the second post of FAQ before proceeding with this guide.
I woudl not be responsible for any damage nor would be any developer or contributor at XDA. You understand the risks before proceeding on your own. All credits to the developers for their work and I am merely arranging everything in one place.
UPDATE Root 5.02 35A
I have successfully rooted lollipop 5.02 with SuperSU. Proof is given in the postHERE IS THE PROOF
Many thanks to my friend @roirraW "edor" ehT for his help, suggestions and his constant motivation that led me to keep trying!
All instructions are given here ROOT VK810 LOLLIPOP 35A WITHOUT DOWNGRADING
Root 4.4.2
FAQs
1.Make sure you are on latest firmware which is VK81024A.
2.If you are on any previous build especially 23A, I suggest you upgrade your device to the latest build.
3.If you unable to root it via brute force, repair your VK81024A firmware using Verizon tool because there's something wrong with your firmware.(modifications mostly)
4.Repairing would ensure it works. Brute force roots your device in first attempt so if it doesn't, you'll need to repair your firmware and do not waste time to retry.
Instructions :
1.Download stump root and install apk in your device. You can get it from HERE
You will need unknown sources checked in settings for installation.
2.Once installed. Select bruteforce. It'd say device is not supported but brute force works perfectly.
3.Once you run brute force, it'd ask you to restart your device. Do it manually.
4.After restarting your device, install SuperSU from market and run it. It'd ask to upgrade the binary, do it.
5.Uninstall stump tool.
Done.
Recovery :
It is a bit tricky to install it. Recovery requires aboot 4.2.2. Thus if you are on 4.4.2, you'll need to downgrade your aboot first.
FAQs
1.You'll need platform tools and a PC with Usb debugging on.
2.You must unlock developer options in settings by tapping build number 9 times in about device and then turn usb debugging on in developers tool.
3.Make sure you have platform tools(see attachment) and you have opened command prompt and cd to directory. (You can alternatively use ctrl+shift+right click in the directory of platform tool and select open command prompt here)
4.Paste aboot and twrp contents into platform tools folder.
Instructions :
How to downgrade and flash aboot4.2.2
If you are on 4.2.2, skip this step.
1.Download aboot 4.2.2 FROM HERE
2.Rename aboot4.2.2 to aboot. (recomove 4.2.2 from it only)
3.Place it in your internal memory/sd card/platform tools folder.
4.Run the commands.
HTML:
adb shellsudd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/abootexitexit
Installing TWRP
You will need to install twrp 2.7.0.1 first using loki support. After you are done, you can flash CWM or TWRP (2.7.0.2) zips from recovery.
Refer to last line for TWRP download links.
1.Open command prompt from PC in platform tools folder.
2.Paste contents of twrp 2.7.0.1.zip into the folder.
3.Type these commands
HTML:
adb push loki_flash /data/local/tmp/loki_flashadb push twrp.lok /data/local/tmp/twrp.lokadb shellsucd /data/local/tmpchmod 777 loki_flash./loki_flash recovery /data/local/tmp/twrp.lokexitexitadb reboot recovery
You would boot into recovery now
How to boot into recovery
To boot into recovery, you will need to first turn off your device.
Hold volume down+power key and switch it on.
Using volume keys, select factory reset data. (I know I know but this isn't a troll)
You will boot into recovery.
How to boot into download mode
To boot into download mode, you will need to first turn off your device.
Hold volume up+ connect it to the PC using a USB.
Change recovery to CWM
1.Download vk810 CWM recovery from the development forum. See Link Below for CWM
2.Flash it using twrp recovery.
To flash twrp.zip from cwm, you might need to toggle loki support in advanced in CWM menu
Special Thanks to @paperWastage for the following guide
ALL FLASHING GUIDE
Please refer to this guide for all other problems.
CLICK HERE
The guide includes amongst many others
*non-booting device
*JB4.2.2 Issues
*KK4.4.2
*LTE not working
Some Useful Links
TWRP RECOVERY
CWM RECOVERY
Click to expand...
Click to collapse
That 4.2.2 DL send me to a Chinese page?
---------- Post added at 10:18 PM ---------- Previous post was at 10:12 PM ----------
Its really not difficult. Just not as easy as ive become a custom too. Dang Verizon and they're bootloaders
TWRP for 5.02
So, if I am already on 5.0.2 and rooted, am I able to install TWRP using stated instructions for 4.4.2?
If your stupid like me :silly: and you blindly follow the [HOW-TO] The Nexus 6 All-In-One Beginner's Guide you may be trying to figure out how to fix your phone.
The beginner guide linked above is amazing to say the least but the OP has not updated it yet to reflect the 6.0 update. If your phone has Marshmallow 6.0 and you follow the instructions you will render your Nexus 6 unusable. Not bricked, just not functional. You will get an error that states Your device is corrupt. It can't be trusted and may not work properly. (seen below) Followed by a blank screen. But don't worry, its very easy to fix with just a few extra steps. :fingers-crossed:
{
"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"
}
If you are here, it is assumed that you have already done the following steps:
Step 0.1 Download and install the Android SDK tools (adb and fastboot), as well as the Google USB drivers. This is step 2 in the beginner guide and there is a great write up here on these tools. [noob-read] adb and fastboot. What is it? How can it help you?
Step 0.2 Unlocked the Bootloader.
Step 0.3 Ran the CF-Root tool. The file name is CF-Auto-Root-shamu-shamu-nexus6.zip
If you watched the CMD window closely this is where the problem happened. There will be a couple errors thrown. You will wait to see the big red Android on your phone but instead you will see the above warning message flash briefly followed by a black screen. If this is the case, proceed to step 1
Please Note: Parts of these steps are copied and pasted from other instructions. Consider this a grouping of other instructions for the purpose of simplification.
Step 1 - Install a Custom Recovery (taken from the original guide)
Go HERE to download the latest TWRP recovery for the Nexus 6. At the time of this write-up, I used 2.8.5.0
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img
Move the recovery.img file to C:\Program Files (x86)\Android\android-sdk\platform-tools
Open command prompt and run the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it.
After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Power off the phone
Step 2 - Install the Modified boot.img (Original steps HERE)
Download the modified boot.img from http://downloadmirror.co/android/sx/shamu-mra58k-boot.zip
Unzip the file and move it to C:\Program Files (x86)\Android\android-sdk\platform-tools
Boot the phone back into bootload mode using Power + volume down.
Open a command prompt and enter the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash boot boot.img
Power off the phone
Step 3 - Flash the SuperSU zip via TWRP Recovery v2.56 beta (original steps HERE)
Downlaod SuperSU x2.56 from http://downloadmirror.co/android/u1/SuperSU-v2.56-20151030013730.zip
Boot your phone into the bootloader mode with Power + volume down
Enter recovery mode. This will open TWRP Recovery
After TWRP Recovery is open, connect your phone to your computer.
Open My Computer where youc an see the C: drive, and other connected drives. You should see your Nexus 6 listed. Open it.
Move the SuperSU zip onto your phone. I placed mine in the TWRP folder.
On your phone, select Install, then navigate to the folder that contains the SuperSU zip. Click on the zip file.
Swipe to Confirm Flash and begin the flash.
Once SuperSU is flashed, select the Reboot System option.
And that's it, your phone should now boot back up to your fresh rooted copy of Android Marshmallow 6.0. You can download a root verification app to confirm the root. :victory:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
simms22 said:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
Click to expand...
Click to collapse
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
For those of us who have been down this road a time or two, this guide will not help them at all. Its really just directed to newbie's who are now stuck because of the beginner guide above.
K!ngpen said:
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
Click to expand...
Click to collapse
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
simms22 said:
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
Click to expand...
Click to collapse
I'm right there with you. My first rooted device was a motorola xt720 sometime in 2010 I think. It was a company phone and like most very young IT folk I was curious lol. New versions of Android started rolling out but the phone wasn't going to get the update. So i was suck on Eclair. I stayed after work and tried the root, and it didn't work to say the least... I stayed at work until 2am trying to get that darn thing to work. 3 days later I got it to flash cyanogen. It was buggy as hell but i didn't care because I didnt have to explain to my boss that I broke my phone by trying to "hack" it lol. That was a win in my book. I later worked up the courage to get it back on a rooted version of Froyo. Pretty bumpy start to my rooting career to say the least. Now I'm a die hard Nexus follower just looking for an excuse to root the next device.
K!ngpen said:
You followed the correct instructions haha...
Click to expand...
Click to collapse
Everyone who is trying to help other users earns respect.
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Noopguy said:
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Click to expand...
Click to collapse
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
K!ngpen said:
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
Click to expand...
Click to collapse
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Noopguy said:
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Click to expand...
Click to collapse
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
K!ngpen said:
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
Click to expand...
Click to collapse
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Noopguy said:
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Click to expand...
Click to collapse
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Noopguy said:
I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp.
Click to expand...
Click to collapse
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
sjgore said:
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
Click to expand...
Click to collapse
That's strange, I sideloaded that for MRA58K, MRA58N and MRA58R and I don't think I was ever prompted to update the binaries. I'm not sure you are being asked to.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
Thanks guys, this really helped. Flashing 2.52 did the trick and i didnt need to update the binaries after i flashed it. I am also on MRA58R
I was going to say as well, SuperSU v2.52 is what needs to be installed via TWRP, not v2.56. I believe v2.56 is for the new systemless root option but it sounds less stable and buggy.
Does this wipe any data? I have been looking to root and actually followed that guide myself, got the same issue and fixed by reflashing a factory image.
EDIT: I'm assuming I don't have to break my phone again to do this correct? Can I just pick up from step 1 to flash the recovery and go from there?
Something weird happened to me after flashing TWRP and I thought I'd share. So my N6 wasn't corrupted at all, but I decided to root my phone and I started by flashing TWRP. I went into boot loader and then recovery to make sure it worked and it did. When I went to reboot the system, I got the the "your device is corrupt screen." I pressed the power button and the screen turned black for a few seconds and then it rebooted normally. I went back into recovery to try and reproduce this and it happened again, Not sure why this happened but everything is functional.
New to rooting and I want to root my Nexus 6
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
atvisic said:
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
Click to expand...
Click to collapse
Lol why break it first. I didn't read through the op here but all you need to do is unlock the bootloader. Flash twrp with fastboot. Reboot to recovery without booting the phone, if you boot the phone before going into twrp it will get overwritten and you will need to reflash it. Flash a custome kernel in twrp, flash SuperSU 2.52 or higher in twrp.
The instructions in the op are more complete naturally. But when it has you flash the boot.img, you can use a custom kernel instead.
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"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"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
Bootloader is open but TWRP is giving ERROR1 when trying to flash Root, and also is unable to mount any partition...
Any help from someone who managed?
***Important Update!*** I am almost sure the problem is with Huawei shipping the P10/P10Plus with different storage chips.
Myself unfortunately got the eMMC chip + LPDDR4 memory. This is why TWRP is unable to mount any partition since the .fstab is different.
I have a working TWRP I ported myself which I was able to rebrand with, root yet to be confirmed. If you need it PM me.
I strongly advise anyone trying to flash TWRP to check their storage chip first using adb command "ls /proc/fs/*".
If you get mmcblk your F******, SD or UFS you are good.
I have an AL00 (rebranded to L29) that I rooted without too much hassle. The key is NOT sliding the first screen in TWRP. You have to click the read only button and then flash the phh nocrypt root zip.
Thanks!
Goronok said:
I have an AL00 (rebranded to L29) that I rooted without too much hassle. The key is NOT sliding the first screen in TWRP. You have to click the read only button and then flash the phh nocrypt root zip.
Click to expand...
Click to collapse
I would kindly appreciate links used and a short walkthrough...sent you a PM.
Thank you so much!
MosquitoByte said:
I would kindly appreciate links used and a short walkthrough...sent you a PM.
Thank you so much!
Click to expand...
Click to collapse
https://www.gizdev.com/root-huawei-p10-p10-plus-install-twrp/
If you follow this guide exactly, you'll be rooted without issues. (you can use their files, they work fine) Two things to watch for :
1. You absolutely cannot slide the first slider in TWRP to allow modifications. You have to click the read only button.
2. It will only work on a fresh install / fresh boot.img. If you've already allowed modifications within TWRP, you're stuck. You have to flash a new boot.img or completely re-install EMUI via update.zip or funkyhuawei.
Hope this helps
Thanks so much for your Info Goronok.
I got the same problem.. No possibility of a full root and system partition is write protected..
One question:
Is ist possible to do a factory reset out of the settings as well?
Or do we have to go for the funkyhuawei method?
How can i update.zip the system if its not possible to make a dload folder in the root folder on system partition?
Can someone uplad the boot.img for VKY-L09C432B130, if that will save the problem too... ?
Ok that wasnt one, that were 4 questions.. but thanks so much in advance
Kind Regards
Dennis
DV87XDA said:
Thanks so much for your Info Goronok.
I got the same problem.. No possibility of a full root and system partition is write protected..
One question:
Is ist possible to do a factory reset out of the settings as well?
Or do we have to go for the funkyhuawei method?
How can i update.zip the system if its not possible to make a dload folder in the root folder on system partition?
Can someone uplad the boot.img for VKY-L09C432B130, if that will save the problem too... ?
Ok that wasnt one, that were 4 questions.. but thanks so much in advance
Kind Regards
Dennis
Click to expand...
Click to collapse
1. No factory reset within the device will help you once you've swiped to allow modifications within TWRP.
2. I did funkyhuawei, so it's the only thing I can speak to. This method will absolutely work assuming you dont mind spending a few dollars and have a router where you can specify DNS.
3. update.zip should (in theory) work from sdcard, though I have not personally tried it. I think most of the people mentioning this method are coming from a P9/Mate9, which does things a little differently.
4. I have not seen a link for VKY-B130 yet, but here is one for B124. The boot.img here should work just the same... http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v82453/f2/full/update.zip
can't figure out what is wrong
First time I tried to root I did slide the "allow modifications"...
I reinstalled stock twice with FunkyHuawei but still can't get TWRP to work.
It seems it doesn't have access to any partition.
Phone boots normally though...
Any ideas?
Please.....
{
"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"
}
http://imgur.com/a/nzog4
Hey Mosquito, i guess we both have the same kinda Problem.
I will do the following steps today and let you guys know, if and how it worked out.
The only problem is, im not at home right now, so i dont have access to a router where i can change the DNS. So no FunkyHuawei method for me.
I will do the following steps today:
1. Donwloading the VKY-L09C432B130 jus now. Trying to flash the original boot.img and do the TWRP and root again, WITHOUT swping the TWRP allow modifications slider
2. If No 1 doesnt work i will copy the download update.app, will create a dload folder on my external sd card and copy update.app in it. Then trzing to freshly install the downloaded firmware.
3. If there is somehow a failure or any error with the automated update i will factory reset the phone via settings and then see whtats going on.
I hope everything will work out fine, even without the possibility of FunkyHuawei Reset.
Keep in mind that there are two types of TWRP online available for the P10Plus Version 3.0.2.2 and version 3.1.0.0.. maybe the root works different with the different TWRPs. At this moment im not quite sure which one i use.. probably the one from gizdev, what Goronok told us to use.
I keep you up to date whats going on!
Thanks guys
Regards
Dennis
Been there..
DV87XDA said:
Hey Mosquito, i guess we both have the same kinda Problem.
I will do the following steps today and let you guys know, if and how it worked out.
The only problem is, im not at home right now, so i dont have access to a router where i can change the DNS. So no FunkyHuawei method for me.
I will do the following steps today:
1. Donwloading the VKY-L09C432B130 jus now. Trying to flash the original boot.img and do the TWRP and root again, WITHOUT swping the TWRP allow modifications slider
2. If No 1 doesnt work i will copy the download update.app, will create a dload folder on my external sd card and copy update.app in it. Then trzing to freshly install the downloaded firmware.
3. If there is somehow a failure or any error with the automated update i will factory reset the phone via settings and then see whtats going on.
I hope everything will work out fine, even without the possibility of FunkyHuawei Reset.
Keep in mind that there are two types of TWRP online available for the P10Plus Version 3.0.2.2 and version 3.1.0.0.. maybe the root works different with the different TWRPs. At this moment im not quite sure which one i use.. probably the one from gizdev, what Goronok told us to use.
I keep you up to date whats going on!
Thanks guys
Regards
Dennis
Click to expand...
Click to collapse
I already did everything you wrote, still no go.
Please update me if you get a different result.
Tried both TWRP versions.
What firmware you had at first?
I have bought my phone 10 days ago.
From T-Mobile Germany.
VKY-L09 6GB Version, Single Sim i guess.
Not sure what Firmware i had when i bought it, cause I immediately tried to root after buying, without checking the FW Version.
But I did a FunkyHuawei Restore before with VKY-L09C432B130 Firmware and it worked.
Only the Full Root is the Problem right now.. damnit.
I Will try everything and let you know.
Later!
MosquitoByte said:
First time I tried to root I did slide the "allow modifications"...
I reinstalled stock twice with FunkyHuawei but still can't get TWRP to work.
It seems it doesn't have access to any partition.
Phone boots normally though...
Any ideas?
Please.....
http://imgur.com/a/nzog4
Click to expand...
Click to collapse
What root zip are you trying to flash?
That from gizdev. Superroot.noverity.nocrypt.zip
Hey Guys i made it ! Yesss Thats awesome !
Im doing a Factory Reset now for a clean install of everything. Just because i want a fresh and new phone
Mosquito what Firmware are you on?
Let me know your Firmware Number and i explain what to do..
Ohhh Great
DV87XDA said:
Hey Guys i made it ! Yesss Thats awesome !
Im doing a Factory Reset now for a clean install of everything. Just because i want a fresh and new phone
Mosquito what Firmware are you on?
Let me know your Firmware Number and i explain what to do..
Click to expand...
Click to collapse
I am now reverting to VKY-AL00C00B123 using FunkyHuawei...Please share what to do next
Ok forget my last post.. sorry!
Here is what to do:
Whoever gets the Error 1 Message when installing the SuperRoot_noverity_nocrypt zip, do the follwoing:
Get your Firmware Number, download the whole Firmware (about 2GB +/-) and download the huaweiextractor from here
https://forum.xda-developers.com/showthread.php?t=2433454
Start the Huaweiextractor exe and unpack the boot.img.
Start your phone into bootloader
Flash boot.img (of your original firmware, the one u unpacked just now) to your phone via fastboot flash boot bot.img
Then start your TWRP Recovery
Clear Cache/Dalvik
then install the SuperRoot_noverity_nocrypt, this time you wont get a error
then wipe cache/Dalvik
reboot
enjoy our FUll root on Your P10plus or P10
Best regards
Dennis
DV87XDA said:
Ok forget my last post.. sorry!
Here is what to do:
Whoever gets the Error 1 Message when installing the SuperRoot_noverity_nocrypt zip, do the follwoing:
Get your Firmware Number, download the whole Firmware (about 2GB +/-) and download the huaweiextractor from here
https://forum.xda-developers.com/showthread.php?t=2433454
Start the Huaweiextractor exe and unpack the boot.img.
Start your phone into bootloader
Flash boot.img (of your original firmware, the one u unpacked just now) to your phone via fastboot flash boot bot.img
Then start your TWRP Recovery
Clear Cache/Dalvik
then install the SuperRoot_noverity_nocrypt, this time you wont get a error
then wipe cache/Dalvik
reboot
enjoy our FUll root on Your P10plus or P10
Best regards
Dennis
Click to expand...
Click to collapse
I think I tried that already,
I will try again..
Where did you get your firmware from and what firmware you were on?
I have the Firmware L09C432B130 and i downloaded from here:
http://www.stechguide.com/download-huawei-p10-plus-nougat-firmware-update/
Just google your firmware and downloaded.
You need the exact 100% same boot.img from your installed firmware.
Then it will work for sure!
DV87XDA said:
I have the Firmware L09C432B130 and i downloaded from here:
http://www.stechguide.com/download-huawei-p10-plus-nougat-firmware-update/
Just google your firmware and downloaded.
You need the exact 100% same boot.img from your installed firmware.
Then it will work for sure!
Click to expand...
Click to collapse
Dennis,
Can you please check for me if TWRP mounts partitions correctly for you?
I suspect the problem for me is incompatibility of the available TWRP with the Chinese version, or some sort of data encryption embedded.
MosquitoByte said:
Dennis,
Can you please check for me if TWRP mounts partitions correctly for you?
I suspect the problem for me is incompatibility of the available TWRP with the Chinese version, or some sort of data encryption embedded.
Click to expand...
Click to collapse
Is your device an AL00?
Goronok said:
Is your device an AL00?
Click to expand...
Click to collapse
Yes indeed.