Related
Greetings fellow GNex owners and enthusiasts!
I've been trying to root my Galaxy Nexus unsuccessfully for the past week.
Here's what I've done so far:
1. I Unlocked the bootloader as per Droid-Life's instructions using an old method with the cmd prompt. (The complete How-To guide on their website) I installed the SDK on a windows 7 64-bit machine and went ahead with the process. This worked fine.
(*Note: My Gnex is stuck on 4.0.2 and it won't pull an update. I've tried the method of clearing the data from the framework app and resetting the clock to 1969 multiple times without success. probably 10-15 times.)
2. Since that I've tried uninstalling/reinstalling drivers, rebooting, and then rebooting some more. I've tried every available "noob-proof" method out there and i can't get it to work.
Tried Galaxy Nexus Tooklit v5.6
With and without the included drivers. tons of reboots and re-tries. root always fails.
Wugfresh's Toolkit 1.3
with and without the included drivers. tons of reboots and re-tries. root always fails.
Manually pushing CWM Recovery and SU to the phone with cmd promt via other tutorials floating around the internet, etc. Pushing CWM Recovery fails. Can't even get the temporary flash going to install SU
NOTHING works.
Is it because I unlocked the bootloader manually using an older method first?? I'm pretty sure I've been following the various instructions with each method accurately.
Can someone shed some light on me? I don't necessarily want to mess with kernels and custom ROMs. I just want to be able to wirelessly tether like I could with my OG and D2.
Thanks in advance,
Thanassi
Check my sig and try my method?
Haha.
But I'm guessing driver error.
The simplest method for getting drivers is to download and install pdanet on your PC. Then simply try again.
http://junefabrics.com/android/
I've had to root my phone 3 times and each time took 3 tries before it took. As mentioned before also make sure your drivers are good. And su files.
bow chicka wow wow.
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
shohratshankar said:
I'm a noob too.
I followed the following method:
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
familyguy59 said:
As I am most likely NOT going to watch this video; Does it contain any Rundll32 commands?
If not, then the tutorial can't be all that good...
Because you need to tell Windows, that it should NOT always search Windows Update, for drivers. They're mostly crap, to be as nice, as I can...
Click to expand...
Click to collapse
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
shohratshankar said:
U don't need to watch the Video, you can read the details given in the site with the screenshots. Totally simplified.
No SDK, no rundll32 .... just installing of drivers and using command prompt
Click to expand...
Click to collapse
Yes. You don't need the SDK, as a matter of fact
The Rundll32 part, is a fact, when installing the drivers...
It has the following effect:
You have installed ADB drivers (no Rundll32). You are flashing away, and all of a sudden. BANG! Everything stoppen. Phone's bricked... Why? Windows thought it is being smart, and installed new drivers, whilst you were working. However, with the RunDll32 command, you can tell Windows, that YOU want to install the drivers manually, and check manually. Of course, you can turn this off, if you want. No prob. but I personally recommend leaving it off
It's saved many phones' lives ^^
so you are having trouble with the adb or fastboot drivers? is so i had this problem too and sometimes even have to reinstall those drivers after flashing a rom.
i had to manually install the drivers using device manager, just select the android device and go to update driver. Choose "Browse my computer for driver software" then pick "Let me pick from a list of device drivers on my computer" then choose Google in that list.
Error
familyguy59 said:
Check my signature. Try that out.
TADA!! You're rooted, and you can flash stock 4.0.4 (And root it, at the same time ^^)
LG familyguy59\Beatsleigher
Click to expand...
Click to collapse
I get an error message with this application whenever I attempt to do something.
tried that
shohratshankar said:
I'm a noob too.
I followed the following method:
After Step 6 when I went to step 7 I was unable to see "Android ADB Interface", so I re-installed the drivers and repeated step 6. It worked and the rest of the steps went like Clockwork.
See if this method works.
Click to expand...
Click to collapse
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
thanassi44 said:
Yea I tried that one too. Didnt work. pushing CWM Recovery always fails
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
GSM only??
efrant said:
http://forum.xda-developers.com/showpost.php?p=24360114&postcount=10
Click to expand...
Click to collapse
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
thanassi44 said:
Just followed that link but the CWM Recovery is for GSM. My nexus is LTE Verizon. Will this work?
Thanassi
Click to expand...
Click to collapse
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
FINALLY! Have Root.
efrant said:
No, just replace the recovery with the late version. Look for it in the dev section. It has its own thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for all your responses and suggestions. I finally got something to work. After some more driver swapping and rebooting, now on an XP machine, I got wugfresh's toolkit 1.3 to flash cwm recovery and I was able to install su. The program then ran an automated script to allow permanent flashing of cwm recovery. Got my titanium backup and from manager back, as well as wireless tether. Thank you all for your attention and patience!
Had such a hard time with this phone that I was beginning to have buyers remorse. Now its been set free.
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Sorry, but I've tested this program, over and over. I use it, myself. I never habe any problems...
But, I'm in the making, of a Youtube video. I'll post it, in my thread Then maybe you can see, what you did wrong
thanassi44 said:
I get an error message with this application whenever I attempt to do something.
Click to expand...
Click to collapse
Hang on... Did you install the scnd. file, within the ISO? If not, there's your problem...
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
I have adb and fastboot installed, and using rumrunner, I am trying to s-off/root my HTC One M7. Is anyone else having issues with it getting stuck on the first pouring <1>... message? Mine has been sitting here for about an hour with no change. I made sure to go in an disable 'verify apps by adb' in the phone's settings, and started again, and yet it still gets stuck on this first pour.
Any ideas?
MReprogle said:
I have adb and fastboot installed, and using rumrunner, I am trying to s-off/root my HTC One M7. Is anyone else having issues with it getting stuck on the first pouring <1>... message? Mine has been sitting here for about an hour with no change. I made sure to go in an disable 'verify apps by adb' in the phone's settings, and started again, and yet it still gets stuck on this first pour.
Any ideas?
Click to expand...
Click to collapse
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Okay so my first question: Is it a VERIZON One?
Second question: Did you properly install the drivers for fastboot on the phone?
1st suggestion: Add an exception in your firewall for soju.exe
2nd suggestion: open a command window in your platform tools folder of your adb installation and type adb devices to see if it comes up
Sent from my One using XDA Premium 4 mobile app
cstrife999 said:
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Click to expand...
Click to collapse
Ok maybe I missed that, where is verifying apps off?
Never mind, found it under developer options.
sanjeeva7 said:
Ok maybe I missed that, where is verifying apps off?
Never mind, found it under developer options.
Click to expand...
Click to collapse
Under security. It's a 4.2 and up thing to prevent malware from being installed on the phone.
Ok still not working.
I am on VZW with stock. Zero mods made to the phone. I just got it a few days ago. I am on the .10 version.
adb works:
C:\miniadb_m7>adb reboot bootloader
C:\miniadb_m7>fastboot devices
FA37K------- fastboot
C:\miniadb_m7>fastboot reboot
rebooting...
finished. total time: 0.044s
C:\miniadb_m7>adb devices
List of devices attached
FA37K------- device
C:\miniadb_m7>
Loaded the HTC only drivers for Windows 7. Run as admin directly from the program, and in DOS which was run as admin. At first I was getting the "WTF" error. I have disabled my antivirus and added the "soju.exe" to allow in my firewall settings. So then I rebooted. I am using the OEM cable and usb 2.0 port.
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (36/120)
Waiting for device
Waiting for device
pouring (1)...........
.................................
Waiting for device
pouring (2)...........
.................................
Waiting for device
pouring (3)...........
.................................
Waiting for device
pouring (4)...........
................................
Waiting for device
pouring (5)...........
................................
Waiting for device
pouring (6)...........
................................
Waiting for device
pouring (7)...........
................................
Waiting for device
pouring (8)...........
.................................
Waiting for device
pouring (9)...........
.................................
Waiting for device
pouring (10).....
...
If you're getting the pouring (10) error, run the .08 software. that fixed it for me.
What worked for me was to right click soju.exe and run as administrator. After that it worked like a charm.
Sent from my HTC6500LVW using Tapatalk 4
Wow, 10 pours? With all these random numbers of pours I'm reading (mine was 3), I'm thinking this exploit keeps trying until it works and I imagine theres a bit of timing or trial and error involved?
skiman10 said:
What worked for me was to right click soju.exe and run as administrator. After that it worked like a charm.
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
Make sure debugging is check marked every time the phone reboots during the process.
I had to manually mark it the first few times.
Sent from my HTC6500LVW using Tapatalk 2
My suggestion is to use Linux to do the process , I did it first attempt . Just make sure you sudo get adb and fastboot and you are good to go . If you don't have linux I suggest dual booting it will get the job done .
Sent from my HTC6500LVW using Tapatalk now Free
kookahdoo said:
Make sure debugging is check marked every time the phone reboots during the process.
I had to manually mark it the first few times.
Sent from my HTC6500LVW using Tapatalk 2
Click to expand...
Click to collapse
It seems when you turn that fast boot option OFF it kept USB debugging on. At least it did for me.
I'm not sure why it would make any difference, but I wiped adb and fastboot from Windows, then reinstalled both of them. After that, everything went perfectly fine, and now I just have to figure out what ROM to put on this thing.
Any suggestions for the Verizon version?
USB ports
I was having the exact same problem, dumping out to a WTF error on Pouring 1. I tried everything on the planet, but what eventually fixed it for me was switching USB ports.
Ironically, it was a USB 3.0 port that worked for me. But my tower has, easily 10 USB ports on the backside. Try different ports. That's the only change I made, and it went from that exact failure to a first try success.
MReprogle said:
I'm not sure why it would make any difference, but I wiped adb and fastboot from Windows, then reinstalled both of them. After that, everything went perfectly fine, and now I just have to figure out what ROM to put on this thing.
Any suggestions for the Verizon version?
Click to expand...
Click to collapse
I am running VANIR and liking it so far. I'm sure I'll try them all eventually. Never had much luck with PAC on any of my previous devices and Liquid was always good but lacked some features I wanted. CM is always another option as well. Whatever you pick now, you will probably change as now that we have a simple S-Off my guess is we will have a LOT more choices soon. What I'd really love to see is a Team Sourcery ROM but doubt it will happen.
I really like Blinkfeed, so I went with BoneStock.
cstrife999 said:
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Click to expand...
Click to collapse
Where did you get the stock recovery to flash?
Verizon HTC One software version & rumrunner
Prior to implementing any Rumrunner S-OFF mod, I notice that Verizon pushed a "minor" OTA upgrade last week. It might have been .8 prior to the OTA and is now showing a long string for the ID; both revs are being shown.
When I query my software on the phone now, I see: "...1.10.605.10-1.10.605.8_R2". I'm not sure what it showed prior to receiving the OTA push...
Question, which version of the software should be downloaded, at least initially? The .10 or the .8? I assume the .8_R2 implies the tweak to .8 and the .10 means the push is applied... Any recommendations?
Thanks, bj
clivusmul said:
Prior to implementing any Rumrunner S-OFF mod, I notice that Verizon pushed a "minor" OTA upgrade last week. It might have been .8 prior to the OTA and is now showing a long string for the ID; both revs are being shown.
When I query my software on the phone now, I see: "...1.10.605.10-1.10.605.8_R2". I'm not sure what it showed prior to receiving the OTA push...
Question, which version of the software should be downloaded, at least initially? The .10 or the .8? I assume the .8_R2 implies the tweak to .8 and the .10 means the push is applied... Any recommendations?
Thanks, bj
Click to expand...
Click to collapse
if i were you, i'd try .8
Aggies1288 said:
Where did you get the stock recovery to flash?
Click to expand...
Click to collapse
I provided a .zip somewhere
let me find it
http://d-h.st/sdg
use fastboot.
Hello,
First of all, Thanks for this great community. It has been helping me with my S4 for a long time.
Almost a year ago, I bought a fire phone for my younger brother. Today I tried to install the Custom Rom CM11 (which I successfully did), but, among the files in the proper thread, are 2 more files, the Google apps and also, a "flash wipe out". I did this in the end, expecting that just cleaned everything without touching the OS. Huge and novice mistake from miself. After almost 5 hours of looking for a solution, I realized that I don't have an OS and can only enter to "Fire phone recovery mode". I have downloaded almost 5 or 6 stock firmwares that are available to donwload here in XDA. Tried to download the OTA for an unlocked phone from amazon and tried to upload it to the phone via ABD tools. In the end, I always get the same errors: Not-signed and can't install it in the phone.
I'm going to be honest: I'm desperate.
In conlcusion:
1) No OS in a fire phone.
2) No custom TWRP.
3) I just have recovery mode
4) Been trying to install through ADB tools without any success the stock OTA update (the last one, since I had the 4.6.6 version)
Anything that can help will be well received.
Thanks in advance
Hello,
Have you tried ADB sideload when you go into your phone's recovery? And if you did, what did it say when you tried installing it? Try using this to sideload your phone.
Thanks for your answer @mechasnyper but I have tried that out as well
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
lordofra said:
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
Click to expand...
Click to collapse
Try sideloading using this file. https://www.androidfilehost.com/?fid=24052804347783512 I found this somewhere else and this is the file I used when I screwed up my ROM installation.
When I get home I'll try using that file that you have posted.
I'll update the results.
lordofra said:
When I get home I'll try using that file that you have posted.
I'll update the results.
Click to expand...
Click to collapse
Success?
Sorry for the delay. Been talking with centurylink because since yesterday I have no Internet service (Answering from the phone). No, no success at all.
lordofra said:
It says unable to load.
Click to expand...
Click to collapse
Your need free RAM on computer bigger than .bin size.
Hey, thanks for the answer.
I'm doing it on my laptop that has 8 Gb of ram. Just in case, I'm going to try it on my brother's laptop that has 16 gb of ram to test this out. But I doubt this will make a difference, since I've tried already many .bin files (all of them are unable to load an their size its 1.2 GB max. Many zip files as well where I have obtained 100% load but the firephone aborts the installation due to signature verification failure.
This is really strange. I have screwed up installing Cyanogenmod onto my phone, yet I was able to revert back to the stock ROM with just the stock recovery. I will have to look more into this. I will post again soon for updates. Have you wiped the data and cache?
EDIT: I am not sure if this will work, but try using this bin file. http://androidhost.org/o120v
@lordofra
Try (with quotes)
adb sideload "full_path_and_name_of_the_bin.bin"
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!