Related
is there a way to do this?
Do you mean can you replace the recovery image without a PC, or are you just asking if you can get in to it?
With the phone off: Hold Volume Down and hit power and this will allow you to get in to recovery.
As far replacing it without a PC... not that I know of. Well I mean assuming the use of the world "PC" means any OS (windows / mac / linux).
I dunno, it would seem that all the stuff done could be done through a terminal on the phone instead of ADB (running the exploit, enabling root, and flashing).
jmhalder said:
I dunno, it would seem that all the stuff done could be done through a terminal on the phone instead of ADB (running the exploit, enabling root, and flashing).
Click to expand...
Click to collapse
It's possible but it's a pain. (This isn't tested but I'm not sure that I can see how it wouldn't work...the idea is still similar to get to root and once you're in root, you can do all of it)
Download the files (which should get saved to your sdcard under the downloads folder) and then install a terminal app from the marketplace...run all the commands to escape out into root and you should be able to flash from there (though honestly, it seems easier to download flashrec and just flash a recovery rom that way...that's how I did it )
thecodemonk said:
(though honestly, it seems easier to download flashrec and just flash a recovery rom that way...that's how I did it )
Click to expand...
Click to collapse
You know, if you take the flashrec .apk apart, it has asroot2 in it, so I assumed that flashrec could root the phone in order to make its backup of the existing recovery image.
Was anyone able to back up the existing image? I ended up using adb shell to flash the recovery image since I couldn't get flashrec to back up the image (made me think it wasn't working correctly, and I got paranoid).
<ignore, duplicate>
posguy99 said:
You know, if you take the flashrec .apk apart, it has asroot2 in it, so I assumed that flashrec could root the phone in order to make its backup of the existing recovery image.
Was anyone able to back up the existing image? I ended up using adb shell to flash the recovery image since I couldn't get flashrec to back up the image (made me think it wasn't working correctly, and I got paranoid).
Click to expand...
Click to collapse
Ah, I wasn't aware of that...I only learned that I could unpack the .apk about an hour ago. >.< (I'm still terribly new to android )
The image backup worked fine for me, I have the file it generated saved to my computer. (Why I am saving it, I'm not sure...I'm paranoid like that when it comes to data )
there is a lot for me to learn, many, many thanx
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
EVERYTHING YOU NEED TO RESTORE/UPGRADE THE HUAWEI P8 LITESo i'm making this thread because i noticed many of you had some trouble with your devices. Here you're gonna learn what you can do with your device. Every chapter is something that you can do without the need of the previous chapters (unless told otherwise). I'm also gonna explain what happens to your device (in a simple way so you don't get confused).
WARNING: THIS THREAD IS TOWARDS ALE-L21, ALE-L23, ALE-L02 USERS. IF YOUR MODELNUMBER IS ALE-L04 YOU CAN'T USE ANY OF THE FILES IN HERE.
ALSO I'M NOT RESPONSIBLE FOR SCREWING UP YOUR PHONE, Kevin is.
Note: It will work on the Ale-L02 and the Ale-L23 but you have to settle with some functions that don't work.
Comparison for the modelnumbers ALE-L21, ALE-L23 and ALE-L02
The Chapters:
1. Tools and prepping.
2. Unlock Bootloader.
3. Bootloop/Softbrick.
4. Unbricking.
5. Dual and single sim converting.
6. Upgrading to Marshmallow.
7. Installing TWRP.
8. Getting root.
9. Install Xposed framework.
10. Multiuser account.
11. After word.
Now take your kids and lock them in your basement and put your wife in the kitchen because you're going to learn some stuff and you will get hungry.
Note: If you're a woman take your neighbours wife to make you sandwiches.
Chapter 1: Tools and prepping.
What you need:
Drivers for our phone (Hisuite).
Minimal ADB and Fastboot.
Usb debugging enabled on your phone.
How:
Download and install Hisuite on your pc
Connect your device to your pc and let hisuite detect it.
Close Hisuite.
Download and install Minimal ADB and Fastboot on you pc.
Go to "Settings -> About phone" .
Tap several times on "Buildnumber" until a toast shows where it says "you're now a developer".
Go to settings -> developer options.
And there you will see usb-debugging.
Turn it on.
Congratz on doing this.
Chapter 2: Unlock Bootloader.
WARNING THIS WILL VOID YOUR WARRANTY.
But it doesn't matter. if your phone boots and all the hardware works, everything is fine. The software is something we can fix.
What you need:
This site.
Unlock code(you will get it on the site).
Minimal ADB and Fastboot (see chapter 1).
How:
Just go to the site.
Make a profile.
Wait 14 days.
Fill in their form .
Get a 16 digits code.
Save that code.
Connect your device to your pc.
Open a cmd.
Type this:
Code:
adb devices
It should return a permission request on your phone just accept it.
After that you should see something like this on your computer
Code:
List of devices attached
WXXXXXXXXXXXXX device
That's perfect and you're a good boy or girl or Apache Attack Helicopter.
If it doesn't you're doing it wrong. "STOP KEVIN!!! THAT'S WRONG KEVIN!!! DAMMIT KEVIN!!!"
After that type this
Code:
adb reboot bootloader
Your device will restart into a white screen with the Android puppet (wich name is Andy btw) on it. Beneath Andy it will say "PHONE locked" in green. But not for long .
Wait until Windows installs the drivers.
Remember the 16 digits you got from Huawei?
Yeah whe're gonna need them here.
Next you enter this
Code:
[COLOR="Magenta"]PINK FLUFFY UNICORNS DANCING ON[/COLOR] [COLOR="Red"]R[/COLOR][COLOR="Orange"]A[/COLOR][COLOR="Yellow"]I[/COLOR][COLOR="Green"]N[/COLOR][COLOR="Blue"]B[/COLOR][COLOR="Indigo"]O[/COLOR][COLOR="Violet"]W[/COLOR][COLOR="Red"]S[/COLOR]
No wait, that's wrong. I'm sorry.
This
Code:
fastboot oem unlock xxxxxxxxxxxxx
Where you replace the xxxxxxxxxxx with the 16 digits you got from Huawei.
Now your bootloader screen should say "PHONE unlocked" in red.To be sure you can run this command.
Code:
fastboot oem get-bootinfo
If it returns something like this.
Code:
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
Your good. And your bootloader is unlocked.
Now just reboot with this command.
Code:
fastboot reboot
Congratz, you bootloader is unlocked and your warranty just went down the drain where it shall remain for the rest of its days.
Chapter 3: Bootloop/Softbrick.
Imagine a world where everything went perfect... that would suck, would'nt it? Sometimes our device wont start. This is what we call a "Bricked" Phone. We have 2 kind of bricks. If you encounter them you will sh!t bricks.
No serious... you will!!!
If your phone is bricked we check if we can still charge it and/or try to get something on the screen. If you can't then you have what we called a hard brick and there's nothing we can do about it. "GET OVER IT KEVIN!!!"
The chances are you brokes something.
If we can then HOORA!!! The chance is great whe can restore it. This is what we call a soft brick or a bootloop (for all you smartypants out there. yeah, a bootloop is when you get stuck on your bootlogo/animation).
Chapter 4: Unbricking.
It's very simple we try to push a new image into your phone trough an unlocked bootloader with fastboot (some other devices use special methods, we don't). So make sure your bootloader is unlocked.
Here is an example
Code:
fastboot flash boot boot.img
What happens here is this:
The fastboot calls the fastboot program.
The flash says fastboot i want you to do this.
The boot says on that location on the device that is connected.
The boot.img says with that file.
So for example:
"Hey fastboot you have to flash the recovery partition with the recovery.img".
Becomes:
Code:
fastboot flash recovery recovery.img
We get these "images" with the Huawei update extractor from official updates in the form of UPDATE.APP.
Most of the times we flash 4 images and in this order.
boot.img
recovery.img
cust.img
system.img
So open your cmd in the same folder as the .img files (or put the .img files in the fastboot folder). Connect your phone trough to your pc and press power while holding the volume down button (it will show the bootloader).
And then type this.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
After that just reboot and wait. It can take a long time for the first boot. Now thankfully there are some people, who made scripts for us lazy bastards so we just have to click and be lazy.
What you need:
The unbrick files for the Dual sim.
The unbrick files for the Single sim.
How:
Connect your device in fastboot and press the "flash all" file.
Let the script run.
The first time you're gonna boot you will have no imei's so your device wil register no sim. Just update your damn phone and everything will be fine.
Note: For the people with an Ale-L04. Just replace the .img files in the folder with the files from your stock recovery.
Chapter 5: Dual and single sim converting.
So you want to convert to a single/dual sim? Well good for you.
What you need:
Unlocked bootloader (see chapter 2).
Unbrick files for Dual sim or Single sim (see chapter 4).
Vendor files for Dual sim or Single sim.
Optional:
Dual sim b170 manual update.
Single sim b133 manual update.
How:
If you want to go to dual sim just download the files for dual sim unbricking otherwise download the single sim unbricking software.
Extract them.
Run them.
And here comes the trouble.
After doing this you will notice a few things:
You will notice that none of your sim's is detected.
You will notice you can't upgrade.
And You will notice that it didn't change anything (you don't see the the appereance/dissapreance of the dual sim settings).
At this point you probaly thinking i screwed up and you want to find me, come to my house and kill me slowly in some creepy basement where i shall remain in pain for the rest of my miserable short life. Well... That's to bad for you because i'm not gonna tell you that my name and address is P sherman, 42 Wallaby Way in Sydney.
Ok, so what the F happend to your phone?
1. Your sim detection.
This occurs when you downgrade from Android Marshmallow to Android Lollipop.
It's nothing to worry about. You just lost your Imei and that's the reason your phone won't detect your sim.
It will solve itself once you update.
2. You can't update.
This is a part of the Famous Balong bug.
what happend is, the phone got confused and just spit out some random build (there's a lot more to that but this sums it up). You can detect this bug by going into "settings -> about phone" and check the build number. If you see the word "Balong" in there, congrats, you are a proud owner of the Balong bug.
How to take care of the Balong bug?
Make sure that you walk it 3 times a day.
It also does sleep a lot so don't worry about that.
Please don't be like other people wo just dump it in the woods somewhere.
Be a responsible Balong bug owner.
No seriously. If you have the Balong bug just install the vendor file according your software.
Extract the file.
You will get a folder named "dload" that contains an "UPDATE.APP" file.
Put the folder with the file in it on your sd card or internal memory.
Go to "Settings -> Update".
Press the menu (at the bottom you will see 3 lines, that's the menu).
Choose "Local update".
Select "UPDATE.APP".
Press "Install".
After the install you should be able to upgrade to a higher build. If it doesn't (single sim i had some problems). You have to upgrade manually to the next build.
Same procedure, extract -> put in "dload" folder and manually update. Make sure you delete the vendor file first.
Now you're converted and can update your phone to the latest build from Lollipop trough Updater (OTA). You will also notice that your Imei has returnd and you wil notice the appereance/dissapreance of the dual sim settings.
Chapter 6: Upgrading to Marshmallow.
The upgrade to Android 6.0 doesn't go trough OTA.
You will have to do it manually.
But first... Let your wife make you a sandwich. You should be hungry by now.
It's done? You ate well? Ok then, let's do this.
What you need:
Dual sim b560 build.
Single sim b551 build.
How:
First check that you're build is B170 or higher (dual sim) or B171 or higher (single sim).
If not upgrade first trough OTA or local update.
Extract the file.
You will get a folder named "dload" that contains an "UPDATE.APP" file.
Put the folder with the file in it on your sd card or internal memory.
Go to "Settings -> Update".
Press the menu (at the bottom you will see 3 lines, that's the menu).
Choose "Local update".
Select "UPDATE.APP".
Press "Install".
Some builds are simlocked and wont upgrade.
Just follow the Unbricking chapter and start from there.
After this you can get the next update trough OTA.
Note:Whenever you update trough OTA or local (flashing is'nt updating.) Make sure you don't have root, TWRP or another custom recovery installed. Everything should be stock.
Chapter 7: Installing TWRP.
Congratz you've made it this far. At this point whe're gonna install TWRP.
Now? you ask, What does TWRP do and what does it stand for?
TWRP stand short for Team Win Recovery Project. It's an open-source software custom recovery image for Android devices. It provides a touchscreen interface which allows users to install third-party firmware and backup the current system, which are often unsupported by stock recovery images.
Soooooooowwwww... can you just install TWRP on any device?
NO. TWRP has to be modified to your current chipset in order to work on your device. The provided image we gonna install is TWRP 3.0.2 wich is specially build for our device. Ale-L04, NOT FOR YOU GUYS!!!
What you need:
TWRP 3.0.2 with script.
Unlocked bootloader (see chapter 2).
Usb-debugging enabled (see chapter 1).
How:
Extract the folder from TWRP.
Connect your device.
Just open the Install file and read what's happening on your screen. After it's done you can boot into TWRP by holding the volume down and the volume up button at the same time while powering up your phone. The principle is the same as described in chapter bootloop/softbrick. We just flashed trough fastboot the twrp.img .
If you installed TWRP you can't update trough local or OTA anymore. You first have to flash back the original recovery. You can get them by running Huawei update extractor on your current build UPDATE.APP that you download from the Huawai site and flash them trough fastboot
Code:
fastboot flash recovery recovery.img
Note:It doesn't matter wich build you're on.
Chapter 8: Getting root.
So it has come to this. The most famous feature on Android. The almighty ROOT.
Device manufacturers don't want us to get root because the most of us would screw up the device. So if we gain root acces our warranty is void. But we can restore our warranty with unrooting. Altough if your bootloader is unlocked it's unlikely.
Not that you have anything on your warranty... like, remember that time that you took your phone out of your pocket when it rained? Yeeeeaaaaah, if you send it back they will say it's waterdamage. For warranty on your software it's simple. With root acces, TWRP and the knowledge of XDA we can probarly fix the software issue before they even realize there's an issue.
"Throw your phone against a wall, exactly at 50 M/ph that will solve the problem. Be carefull, because 49 M/ph is not fast enough and 51 M/ph will break your phone." -XDA
Click to expand...
Click to collapse
Please don't try this, this is not a real solution!
So go for the root and f*ck the warranty.
Just be sure that your device boots up and all buttons work before doing anything to it.
DON'T (and i can't stress this enough!!!) ROOT YOUR PHONE WITH KINGROOT!!!You will get root but it also screws up a lot.
For Android 5.0/5.1 Lollipop based
What you need:
Unlocked bootloader (see chapter 2).
Usb debugging active (see chapter 1).
Root file.
How:
Connect you phone to your pc.
Extract the "root P8 file".
Open the "root P8 file".
Follow the instruction on your computer screen.
Your phone is now rooted.
Note: Unroot first with the SuperSu app before trying to upgrade to a newer build.
For Android 6.0 Marshmallow based
What you need:
Unlocked bootloader (see chapter 2).
TWRP installed (see chapter 7).
1.Zip .
2.Zip .
How:
Put 1.zip and 2.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2.zip .
Install it.
Reboot
Your phone is now rooted. But your SuperSu app is still a user app.
If you want to make it into a system app here's how to do it.
What you need:
A root explorer (Es File Explorer).
How:
Go to /data/app folder.
Locate the eu.chainfire.supersu-1 folder and cut it.
Go to the /system/app folder.
Paste it.
Give it these permissions rwx r-x r-x.
Reboot your phone.
After you got root you can delete systemapps that you don't want/need or change a lot of things in your phone.
Chapter 9: Install Xposed framework.
Xposed installer is awesome. it's like a google play store for tweaks than can make your android device just right like you wanted it to.
Note:this version won't need an build.prop edit.
What you need:
Android 6.0 installed (see chapter 6).
TWRP installed (see chapter 7).
Root (see chapter 8).
Install from unknown sources enabled.
Xposed installer.apk.
Xposed installer framework zip.
Optional :
Xposed uninstaller zip.
How:
Enable unkown sources "Settings -> Advanced Settings -> Security -> Unknown sources".
Put the Xposed installer.apk on to your device.
Install the Xposed installer.apk onto your device.
Put the Xposed installer framework zip and the Xposed uninstaller zip into your sd card/internal memory.
Reboot into TWRP.
Install Xposed installer framework zip.
Reboot.
Wait for an hour before deciding that it's bricked. Seriously this will take long like 20 minutes up to 40.
If it's bricked just boot into TWRP again and install the Xposed uninstaller zip. It should work. Otherwise -> unbrick it (see chapter unbrick).
If you have succesfully installed it go to the Xposed installer app and click on "Framework". If it says "Xposed framework version 85.10 is active" in green everything is a gogo.
Chapter 10: Multiuser account.
As you know Huawei did a heavy job theming Android with it's Emui overlay. As so we don't have all the stock features that Android gave us. Here's how to get one back.
What you need:
Root (see chapter 8).
Build prop editor.
How:
Open your build.prop editor.
Locate it to /system/build.prop.
Search for these lines.
Code:
fw.show_multiuserui=0
fw.max_users=1
Change their value into this
Code:
fw.show_multiuserui=1
fw.max_users=3
Save your build.prop (grant your editor root acces).
Reboot your phone.
Then go to "Settings".
There you will see "Users".
Chapter 11: Afterword.
If you're new on XDA remember that the people here do anything in their free time. Be it helping, developing or just testing. Be nice to them and don't spam those people. they may now alot but everything they know is already explained somewhere on XDA and explaining the same thing 1000 times a day is frustrating.
So do a search before asking anything AND READ THE WHOLE THREAD!!! We lost the only 2 developers we had in the P8 lite section this way.
Also if someone helped you press the ":good: Thanks!" button on the right bottom of his/her post. to show your appreciation. The files i enclosed are files that i gatherd over the time at the P8 lite thread or from the Huawei website. I don't remember who made them all but it wasn't me.
Give this guy a thanks @sokkoban for his awesome development on the p8-lite and his site. It learned me a lot about my device. i think most of the files are his. don't know for sure (check out his multitool here). And give this guy @shimp208 a thanks for his awesome work on the Minimal ADB and Fastboot installler and his awesome thread.
Note:for the more advanced people in here who know what they're doing. I know that there are easier ways to do some stuff but i want the people to learn. If you have suggestions, let me know.
I'm in progress of taking control over the world. So i'm not active on this thread anymore. Further questions will be answered by people like @amageek. Give them a thanx for their trouble and send amageek goats, virgins and peanutbutter (he likes that).
Also... Geeky, you will be minister of education in my new world order.
congrats for you amazing tutorial,, i have a question, imagine if my mind turns crazy and i want to lock the boootloader? how can i do?
pl4t!n said:
congrats for you amazing tutorial,, i have a question, imagine if my mind turns crazy and i want to lock the boootloader? how can i do?
Click to expand...
Click to collapse
simple
do the same steps as unlocking but just put in
Code:
fastboot oem relock YOUR CODE
it will say relock and not locked
@pl4t!n little update
Thanks for this tutorial, hopefully this will help many.
riaanck said:
Thanks for this tutorial, hopefully this will help many.
Click to expand...
Click to collapse
I hope so to. i got tired of typing out the same solution 30 times a day now i just have to share a link
Finally
I am very happy because it sets a new developer on the horizon who can explain absolutely correctly and peaceful. Keep the good work bro!
Now moderators should delete 90% of the subjects they are unnecessary, repetitive and full of crap! It is time for this forum to begin to moderate
sokkoban said:
I am very happy because it sets a new developer on the horizon who can explain absolutely correctly and peaceful. Keep the good work bro!
Now moderators should delete 90% of the subjects they are unnecessary, repetitive and full of crap! It is time for this forum to begin to moderate
Click to expand...
Click to collapse
Thx i will do that.
yeah the moderators don't do a lot of work here. there are questions in the general. post's that are the the same... and crap like that. i will try to contact them.
lordy, many many thanks man... nice post... all in one... very much appreciated...
amageek said:
lordy, many many thanks man... nice post... all in one... very much appreciated...
Click to expand...
Click to collapse
Done with typing everything a 1000 times
it was necceserry.
gonna try to update it but...
hi, i f***** my phone with king root. and now o cant uninstall it or unroot. can help me?
Holographik said:
hi, i f***** my phone with king root. and now o cant uninstall it or unroot. can help me?
Click to expand...
Click to collapse
You can use supersu me app or delete the app with a root deleter than start with the bootloader unlocking. Yes, you probarly unlocked it with king root. No, it didn't work.
Good luck dennis, i hope u can fix it
Thumbs up!
Thanks a lot for this useful guide! Finally it's all there together in one place, with good explanations. Just used it to install TWRP and root my device, worked flawlessly!
Edit: now we just need to wait for a nice custom ROM with stock android experience, without the EMUI shell we're stuck with..
THANKS a lot dude, i removed kinguser.
now i want just to update to android 6.0
what i need to unlock/do.
Holographik said:
THANKS a lot dude, i removed kinguser.
now i want just to update to android 6.0
what i need to unlock/do.
Click to expand...
Click to collapse
Just start reading the thread. And pick in where your phone will let you.
wouterbeer said:
Thanks a lot for this useful guide! Finally it's all there together in one place, with good explanations. Just used it to install TWRP and root my device, worked flawlessly!
Edit: now we just need to wait for a nice custom ROM with stock android experience, without the EMUI shell we're stuck with..
Click to expand...
Click to collapse
Their working on it
and what i need to unlock for android 6.0? im a little stupid with huawei
or just put in dload folder the update.app or what is and flash with both buttons and power button?
Holographik said:
and what i need to unlock for android 6.0? im a little stupid with huawei
or just put in dload folder the update.app or what is and flash with both buttons and power button?
Click to expand...
Click to collapse
Chapter 6 everything is explained there. Sorry for the short answers but not much time now
Would it be possible to add some original files or just the rom in case anyone would f*ck things up.
Very good summary!
Where I can find official ROM for asus me375cl based on android 5.1.1?
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
little_pindos said:
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
Click to expand...
Click to collapse
Thank you so much for posting where you found this, this is exactly what I needed!!! You saved my tablet, it is much appreciated! :good:
Flashing Factory Image
The following instructions worked for me when trying to reflash the factory firmware for the ATT Asus MemoPad 7 LTE (ME375CL). I did originally try using the Asus Flash Tool and the raw firmware file (link below) but the tool said it could not unzip the package for some reason or another. So the steps below show how I did it using ADB with fastboot.
I ASSUME NO LIABILITY SHOULD THIS GO WRONG FOR YOU! However, it probably shouldn't matter if you are bricked, I doubt it will make it any worse Either way, I will not replace your tablet or be responsible for troubleshooting it should you mess it up more...
This scenario is based on the tablet stuck on the Asus boot screen and not going any further. I was trying some in depth rooting attempts and bricked it badly. I was then trying to install a custom recovery and that is why I could not reset it and bricked it.
PRE-REQS:
1. ADB installed - Download: https://drive.google.com/open?id=0B0fKccJIuWsna04wMjY1eG9YREU
2. Asus Drivers installed
3. Firmware - Download: https://drive.google.com/open?id=0B0fKccJIuWsnWGhwYzA0Vkluc2s (file is 1 Gb + in size, may take a bit)
SETUP:
If you already have a working ADB setup, do not download the one above. If you are using the one above, I extracted the folder into my C: drive, so the path for ADB would be C:\adb (to keep it simple and less typing).
MAKE SURE THE ASUS DRIVERS ARE INSTALLED! If you have plugged the tablet in to a pc before, they should already be there. Otherwise search, download and install the appropriate drivers.
INSTRUCTIONS:
Extract the firmware zip file to somewhere easily accessible like your desktop. In there, you should see the boot.img, recovery.img and system.img files, copy/paste those files to your ADB folder (for easier typing later on). There are also additional files like these but start with "unsigned_", do NOT use those!
1. Ensure you probably have at least 30% battery charge, I would still recommend more though.
2. Put the tablet in Fastboot mode by ensuring the tablet is completely powered down and then press/hold the VOLUME UP and POWER keys at the same time. When the Asus screen appears, let go of the POWER button but continue to hold the VOLUME UP button. Let go of the VOLUME UP button when the fastboot screen appears.
3. Plug the tablet in to the computer and then open a CMD prompt as administrator.
4. The following uses the ADB downloaded and placed in the folder as listed above, you may need to adjust the location path as needed if you already have ADB installed or located in a different path.
Type in the following without the quotes: "cd c:\adb" (this will change the path to the ADB files for the CMD prompt)
Type in the following without the quotes: "fastboot devices" (you should then see a device listed)
Type in the following without the quotes: "fastboot flash recovery recovery.img" (flashes the factory recovery image)
Type in the following without the quotes: "fastboot flash system system.img" (flashes the factory system image, may take a while to flash)
Type in the following without the quotes: "fastboot flash boot boot.img" (flashes the factory boot image)
5. Once those 3 images have been flashed, you should have seen a message that says "OKAY" after each one. You should be fine as long as you do not have any red error messages on your tablet.
Type in the following without the quotes: "fastboot reboot" (reboots device normally)
6. If all goes well, it should now boot to the Asus screen and then go to the ATT screen. If so, it will stay on the ATT screen for a while, just wait it out. Mine took about 12-15 minutes and then it opened to the new setup screen to set the tablet up as if its new!
This is how I was able to recover my bricked tablet, hopefully it can help someone else that may run into this.
John, thank you for the write-up. Just bought my ME375CL with 4.4.4.4.
When I try to flash the recovery partition, I get the following error:
C:\Users\Myself\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11312 KB)...
OKAY [ 1.047s]
writing 'recovery'...
(bootloader) Official image.
FAILED (remote: flash_cmds error!
)
finished. total time: 2.344s
Click to expand...
Click to collapse
and on the tablet's screen:
FASTBOOT CMD WAITING...
RECEIVE DATA...
E:recovery flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error! )
Click to expand...
Click to collapse
I haven't tried the other commands for system.img or boot.img as I don't want to do anything out of order from the write-up. Ever run into this?
The firmware in the download is 5.1.1, not 4.4.4. That is probably the issue. If you are running good on that, I would try rooting it instead. If you are just wanting to upgrade, you will need to have an active AT&T SIM in the tablet to upgrade over the air. I am not sure if there is a flashable upgrade or not somewhere.
Oh ok John. I misread the title of the thread. I thought it was for updating from 4 to 5.
Quick question then: Is it possible, using the adb / fastboot tools, to backup the current 4.4.4.4 before I allow the tablet to update to Lollipop? After reading around, I understand that Lollipop can't be rooted but I have no real concern for it. But just in case I need the tablet to do something else in the future, I'd like to be able to return it to kit kat to be able to root.
Once you upgrade to lollipop, there is no downgrading for this tablet. There really is not much development for this device. I have kind of been working on a lollipop root when I can. Between my limited time and knowledge of android, I can't promise anything.
Overcoming red messages?
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool:
https://drive.google.com/open?id=0B0fKccJIuWsndXJUa1FEbXVzTjA
johnkirchner said:
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool: ]
Click to expand...
Click to collapse
As a follow up on your question above, Tab restart stalled at a screen (after the Asus logo), presenting some options to do recovery, reboot, factory reset, etc. (factory reset did not help), and red error messages at bottom.
To the GOOD news for anyone interested. I used the Asus Flash Tool and the firmware zip for 5.1.1 (many thanks for the advice).
Note: Tool did not install correctly on Win10 pc, citing error in installing some devcon.exe or similar file (guess that may be a firewall/antivirus issue).
Flash tool took some 15 or so mins unzipping firmware, after which I saw some action on the tab. Another 15 mins, and it rebooted to the At&t logo, stayed here for another 15 mins and unraveled a whole new device on Android 5.1
Glad to hear it worked for you and that I guess you can use this to flash upgrade from kitkat!
There is working way to root our device on lollipop! It is for the other Asus model, but it works for our
http://4pda.ru/forum/index.php?s=&showtopic=640814&view=findpost&p=53047686
I will check this out!
The root works, installed without any issues and verified with a root checker!
Here is a direct download from my Drive folder: https://drive.google.com/open?id=0B0fKccJIuWsnN21ZbnZpc2F6b1E
1. Download the file above.
2. Extract the zip contents.
3. Plug your ME375CL tablet in to pc via usb cable.
4. Make sure you have enabled Developer Mode and allowed USB Debugging first!
5. Open the folder you extracted and double click the "Root-One-Click.cmd" file.
6. It should reboot to fastboot mode and flash the needed files and then reboot again.
You should now have root access. Verify this by installing a root checker app from the play store. Keep in mind, it may say root not installed on the first run. Sometimes it will take a moment for superuser to initially run or prompt for access.
Side note: the root uninstall did not seem to work, got an error...but oh well, the point is to have root!
Thanks go to @little_pindos for finding this file...you are a rockstar!
Anyone get xposed on LP?
ATT Boot Up Sound
Tired of the ATT boot sound? If you used the rooting method above, then you can get rid of the annoying ATT startup sound by doing the following:
1. Install a Root Browser app (I recommend Rom Toolbox Pro, it has a built in file manager)
2. Navigate to the following path:
root/system/media
3. Find the file named "powerup.wav"
4. Simply rename the file by adding .bak to the end (ex - powerup.wav.bak)
5. Make sure it took the name change (some file managers have issues with that)
6. Reboot and see if it got rid of the sound!
You can also use your own startup sounds as long as they are in a .wav format, I believe. Make sure that the name of the file is powerup.wav.
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
TimmyP said:
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
Click to expand...
Click to collapse
I'll have to try that!
AT&T no longer has updates in system for this tablet
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
AT&T removed the last update for this tablet months ago and no longer supports it. ASUS states AT&T has all the updates. Total cluster.
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
doesitburn said:
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
Click to expand...
Click to collapse
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
mrmazak said:
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
Click to expand...
Click to collapse
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
doesitburn said:
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
Click to expand...
Click to collapse
I know you said you have data currently on phone you dont want to loose. But it seems it might be easier to make twrp backup of phone now. then put factory recovery on and restore that back up you have from before , save off it what you wanted, then put twrp back and restore the twrp backup.
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
doesitburn said:
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
Click to expand...
Click to collapse
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
mrmazak said:
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
Click to expand...
Click to collapse
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
doesitburn said:
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
Click to expand...
Click to collapse
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
mrmazak said:
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
Click to expand...
Click to collapse
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
doesitburn said:
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
Click to expand...
Click to collapse
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
mrmazak said:
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
Click to expand...
Click to collapse
ok so for that matter
fastboot boot c:\downloads\recovery.img
that it ? sweet thanks alot.
learning something new every day