Nexus won't Boot after 4.3 OTA Update - Samsung Galaxy Nexus

Hello,
After having waited for SuperSu to support the survival mode, I finally decided to apply the 4.3 update to my Nexus.
It seemed to have gone well just like the other times.
The problem rose after the updated was installed and the phone rebooted. It got stuck onto the "X" screen.
I removed the battery and tried to boot again. Same thing. It gets stuck on boot.
Is there any way out of this? The phone was perfectly fine and I have lots of data on it.
Please let me know if there's any fix to this issue.
Thank you very much for helping.

I found the solution to my problem.
It seems that the only way out of this problem is reflashing.
Here's exaclty what I did. I hope it will help someone in my same situation. I DID perform a backup through TWRP before flashing and pulled it through Galaxy Nexus Toolkit (Found somewhere here on XDA) [It could have been done via the ADB tool found in the Android SDK Toolkit, available on Google].
The stock images were found here and then extracted in "...\adb\sdk\platform-tools"
0) Phone Shut Down;
1) Go to Bootloader by pressing: Power + Vol Up + Vol Down;
2) Run the Galaxy Nexus Toolkit;
3) Select current model (mine was a GSM Model 4.2.2);
4) Input Option 10 ("Boot Custom Recovery Without Permanently Flashing it") --> Option 2 ("Boot to TWRP Touch Recovery...") --> type "yes";
5) On the phone, wait for TWRP to be loaded, then select "Backup" and check all the boxes, set the Backup Name;
6) Swip to Back Up and wait for it to be done (It may take a few minutes). Once done, note down the path where the files where backed up;
7) Then, back on the PC and Galaxy Nexus Toolkit (perhaps it may need to be restarted), select Option 14 ("Pull Files or Folders from the Device". --> Option 2 ("Manually Answer Question") --> type "yes" --> type the full directory you want to be pulled onto your PC (for example, mine was: "/data/media/0/TWRP/BACKUPS/016B7378060040" --> Wait, it will take a while depending on how big the backup is;
8) The files that have just been pulled are inside "...\Galaxy Nexus ToolKit\pulled_files_are_put_here";
9) Still on the PC, we open a console instance, we move to the following folder of the extracted Android SDK: "...\adb\sdk\platform-tools";
---------
We have to make sure that all the .img files we downloaded are exactly in the folder mentioned in point 9), ALL OF THEM (so the ones in the subfolders need to be in the above mentioned SDK folder as well for it to work properly); In my case they were: "bootloader-maguro-primemd04.img", "radio-maguro-i9250xxlj1.img", "boot.img", "recovery.img", "system.img".
Pay ATTENTION: the first two images "bootloader-maguro..." and "radio-maguro..." might be different in name depending on your phone, whereas the othes should be the same. What follows is exactly what I wrote, so the first two images will be the above mentioned: please adjust your command accordingly.
----------
10) On the Phone (still on TWRP) select the option "Reboot", then "Bootloader";
11) On the PC type:
"fastboot flash bootloader bootloader-maguro-primemd04.img" (Again, may be different in your case)
"fastboot reboot-bootloader"
"fastboot flash radio radio-maguro-i9250xxlj1.img"
"fastboot reboot-bootloader"
"fastboot flash boot boot.img"
"fastboot reboot-bootloader"
"fastboot flash recovery recovery.img"
"fastboot reboot-bootloader"
"fastboot flash system system.img"
The last one may take quite a "long" time, so be ready to wait.
[I know it may not be necessary to reboot every time an image is flashed but that's how I did it, plus anything should go wrong we can get to know what didn't work]
11) On the Phone, scroll down the options by pressing Vol Down (or Up), when you see the option "Start", hit the power button to start Android.
That's it.
I hope it's of any help .

Related

[HOWTO]Unlock, Root, and install CWR Galaxy Nexus with Ubuntu Linux or Linux Mint 12

warnning: any damage you do to your phone following these directions is your responsibility. Assume you warranty is void if your are rooted.
I used the information koush provided here and info birdman provided here and adopted it in Ubutnu Linux 11.10. I hit some bumps along the way using my Linux box so I decided to write this for those of us not using OS's made by the darkside This should also work with Ubuntu 12.04 LTS just fine.
All this should work with Linux Mint 12 also.
1- Set up Android SDK, adb, and fastboot in Ubuntu Linux using the links in my signature. I can't stress how useful and easy it is to set adb and fastboot in your "path" so you can easily use it from any prompt. The links explain it. Take your time with that and it will payoff for all your devices. Here is the guide I wrote http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
2- on your phone, go to settings/Developer Options and check the box for USB Debugging
3-connect your phone, fire up a terminal, and type:
Code:
adb devices
You should get the serial number of your device appear. If not, unplug, reboot phone, re-attach the phone to your computer and try again. If you still do not get your device's serial number, go back to step 1 and make sure everything is setup correctly.
4- Now download Clockwork Recovery from here
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img
(make sure it's the CDMA one (toro). The GSM one is called maguro and steps should be the same)
and su.zip from here
http://download.clockworkmod.com/test/su.zip
5-Turn the phone off, hold both Volume up and Volume Down and press the power button. You should come to a screen that has a big arrow and some writings at the bottom (fastboot). Last line should say Locked state.
6- Connect your phone to your computer, fire up a terminal and type:
Code:
fastboot devices
your phone and its serial number should appear just as it did using adb above. adb will not work here of course. If you don't see your device, go to step one. I guess you can download the fastboot for linux and cd to that directory and do it but I like to have it setup on my computer.
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
7- Now for the stuff that voids your warranty: Type
Code:
fastboot oem unlock
and enter. Look at your phone now, use the Volume up to choose YES and press the power button to accept. It should say that you are unlocked and fastboot is in good state.
9-use the volume up to change the value appearing in the arrow to recovery and press the power button to accept. You are taken to laying down android with a red triangle. This is the stock recovery. Now carefully press the volume up, volume down, and the power button to get to a menu. Choose wipe data and factory reset. 2 things: I had a hard time getting to the menu. Do it a few times and try pressing the power button JUST a fraction of a second earlier than the 2 volume buttons. Also wiping and resetting takes a few minutes, be patient.
10-you are now unlocked. Turn the phone off ( I pulled battery), go to fastboot screen by holding volume up, down and power button. Connect your phone to your computer and make sure it is recognized by typing:
Code:
fastboot devices
If it is, change directory to where you downloaded clockwork recovery. If you didn't change it, it should be the Download directory (remember it's case sensitive):
Code:
cd Downloads
11- Time to re-write your recovery:
Code:
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
Please make sure you use common sense here when it comes to file names. If the file you downloaded has a different name or version, change it in the code above. I guess you can put the fastboot file in that location also to be used if you do not have it setup as in step 1. I'm not positive how and if that would work. Downloading and installing the wrong file is a mistake that may cause harm to your phone.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Code:
adb push su.zip /data/media
this will put the su.zip file in the root of your virtual sd card.
You are still in recovery, reboot into recovery to refresh the file list by typing this
Code:
adb reboot recovery
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
13- Download Rom Manager and flash the recovery again (top choice). This will erase the install-recovery.sh file and keeps your CWR at each boot. You do not have to do step 14 if you do this. I will leave step 14 here just in case someone needs it.
14-When you are back in the fastboot screen. DO NOT reboot the phone here. There maybe a file that re-writes the recovery to stock if the phone is rebooted. Your phone may or may not have this file. of the two GN I have, one did and one did not at this step(may have been erased). The file is reovery.sh and is located in /system/etc/ . You need to either rename it or delete it.
While in fastboot and after you flashed CWR, use the Volume up and Down to change the arrow's value to recovery and press the power button. You should now see the familiar Clockwork recovery. In recovery, you can use adb (you can't in fastboot of course). You need to rename that file, use these steps in terminal: (If you see no file/folder found message, you know you do not have this file)
Code:
adb shell
Code:
mount -o rw,remount /system
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
step 1 fires up adb, step 2 allows you to change permissions and read and write, and step 3 renames it. You can now unplug the phone.
Again, you can also get rid of this file by flashing the clcokwork recovery in Rom Manager or using the paid app root explorer to rename the file.
Once again referrence links:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
https://plus.google.com/103583939320326217147/posts/1Jsh9xPwnQP
thank you so much this is exactly what i was looking for. cant believe im the only one to comment on this. it is very detailed even some one new to Ubuntu could figure this out.
I've been using it too for a while but never posted so THANK YOU! Very easy to follow. Great work.
you're welcome. I find it ironic that a Linux based OS such as Android has so many HOWTOs for Windows but not enough for Linux. #powerofmonoply
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
ual4720 said:
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm not sure. How did you setup your adb and fastboot? I did not have to sudo for fastboot commands. What OS are you running?
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
AndroidSparty said:
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
Click to expand...
Click to collapse
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
loveubuntu said:
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
Click to expand...
Click to collapse
3, 6, & 9...check.
I rebooted my phone by pulling the battery and I still can't get adb to see the device. The install-recovery.sh? I don't remember reading anything about that.
In step 12 it says to let the phone reboot into the Android OS, but it's now back at factory reset, as that's what we did earlier in the instructions. As soon as it boots into the Android OS, adb lists the device.
At that point, since I'm in the AOS, I downloaded Astro File Manager and tried to put su.zip in the /cache folder, I think that's the folder that the clockwork recovery mod folder sees, and I don't have permission. I was hoping I could cheat and just drag & drop instead of pushing it. BUT...I did try the command adb push su.zip /media/play and I get permission denied. I'm guessing I don't have permission, even as sudo, to move the file to /data/media.
Okay I finally got it!
I didn't wait long enough for the Android OS to boot up. I finally was able to move the .zip file, but I couldn't find where /data/media was. So I let the OS boot up, removed the battery, went back into recovery, moved the zip file, and it was finally listed.
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Forceflow said:
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Click to expand...
Click to collapse
>Windows guides are confusing
>Windows guides
>Windows
Root of the issue
But agreed, this was a good supplement to follow for Ubuntu.
Sent from my Galaxy Nexus using xda app-developers app
Thank you for this guide. Some how I like the Linux method better than the Windows ones.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Click to expand...
Click to collapse
This step is confusing. While in recovery should be replaced by "Hit Power button to enter ClockworkMod Recovery"
Otherwise people may mis-interpret by "Stay in fastboot and position the big arrow on top to Recovery Mode"
In my case (GNex GSM stock JB 4.11):
adb push su.zip /data/media
or
adb push su.zip /sdcard
did copy su.zip successfully but could not be listed by ClockworkMod Recovery menu when selecting "choose zip from sd card". I had to do this:
Code:
adb push su.zip /sdcard/Alarms
And, within the ClockWorkMod Recevery menu, select "choose zip from sd card"
Land on another screen where I could navigate to Alarms folder and see the su.zip there.
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
Click to expand...
Click to collapse
Sorry for being picky but personally, it is NOT self explanatory for me. I was expecting a menu item in CWM Recovery menu to say "Install su.zip". Actually you must navigate in the file system and select the su.zip yourself. Ok, may be that seems obvious now that I know what to do. But on the moment, I was worried I screwed up something because I needed to do some extra manipulations while you said that should be "self explanatory".
4- Now download Clockwork Recovery from here
Click to expand...
Click to collapse
You may want to up date the link, ClockWorkMod now has a Recovery program which is touch sensitive:
GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-maguro.img
Sprint: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toroplus.img
VRZ: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toro.img
Step 12 finishes with
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
Click to expand...
Click to collapse
Therefore what is the need of doing #13 and 14?
Furthermore, Step 13 starts by
13- Download Rom Manager and flash the recovery again (top choice)
Click to expand...
Click to collapse
What is that top choice? Do you mean restart from the top at step #1? If you need to reflash again CWN, would it be simpler to restart from Step 10 instead of going back to the top?
And BTW, what is the reason to reflash the CWM Recovery again just after you have successfully flashed it at Step 12? Could that be #13 and #14 are some steps of an older guide which no longer apply now but you forgot to remove?
Sorry for the silly question but I am rather lost. After all that hardwork, when I attempt to Update SuperUser, it failed on the line "Gaining root access ..." What is the reason and how to fix that? FOUND ANSWER: the su.zip given in the post is Superuser 3.07 which is outdated, It is probably buggy. Replaced it by SuperSU 0.94 and it works perfect: http://download.chainfire.eu/204/SuperSU/
Thanks
worked like a charm.. if you have problem using fastboot, just cd to the folder with fastboot and run it like this:
Code:
sudo ./fastboot "command"
it will require your password and then work normally, seems like it need super user permissions.
Also for new user: to avoid writing a command or a folder name manually just push the TAB button, it will autocomplete the word if it's unique in that folder

Messed up, looking for a bail out

Was running MMuzzy, tried Omni, decided to go back (no statement on Omni, just didn't want to deal with new, setting up and such) and the only backup I have is in TWRP... but I switched to CM to install Omni... and like an over eager cleaner, I deleted the install files for everything last time I was in Omni... then I went into recovery, wiped and realized I need TWRP to restore my backup (no files found in CW)
All I can do is boot into recovery and I cannot figure out how to set up windows so I can put an install file on there to run so I can get back to TWRP and clean this mess up. I tried installing the Samsung drivers on an XP workstation but the computer doesn't find drivers when plugging in the phone... I pointed to the samsung/drivers folder in programs but no luck.
Bail a ding bat out?
Bump
Can anybody explain how to get this thing viewable in windows? (With no phone control)
Please.... and thank you in advance!!!
I am ready to pay someone for help on this
Help me get this back to life... name a reasonable price
Use efrant's guide in the stickys to flash the factory image and use his link for Windows drivers. It always works and his fastboot tutorial has saved my device more than once.
Link:
http://forum.xda-developers.com/showthread.php?t=1626895
For my instructions, download these, you will end up using them:
1. Android drivers for windows, I would prefer Universal Naked Driver (UND):
http://forum.xda-developers.com/showthread.php?t=1766220
2. Android debugging tools (ADB), I would prefer minimal ADB:
http://forum.xda-developers.com/showthread.php?p=42407269
3. TWRP recovery image: http://www.teamw.in/project/twrp2/90 download the last version you remembered using or just use the latest openrecovery-twrp-2.6.3.2-maguro.img
Install 1 & 2 in order. You may need to have the phone boot to recovery to install #1. Installing the drivers in Windows XP/7 will be easier, Windows 8/8.1 requires an advanced step to disable unknown driver enforcement.
For #2, if you have ADB/Fastboot already, skip this step. If you don't, then you may need to install it while in recovery too. Install it to a folder you are familiar with, I would choose C:\ and make an Android folder.
After you have both installed, boot your phone to bootloader mode. When it is shut off, hold VOL + and - at the same time then press the power button for all 3 simultaneously. It will boot into bootloader mode, where you see the android and your Galaxy Nexus revision/software details.
Move the TWRP recovery img file to the location of your ADB folder. For my example, I will assume #2 (adb tools) are installed in Local Disk (C and the android folder, so C:\Android
From here you would use the command prompt/terminal start > run > cmd or start, find program Command Prompt.
In the terminal type cd\foldertoTWRPimgfile\ or in my example, cd\android\
Next, type fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
my example would look like:
C:\android\ fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
it will show a progress indicator, then OK'd when it is finished.
You can then manually boot to recovery in fastboot, hit a volume button on your phone a few times until you see RECOVERY, then hit the power button to load it. You should now be in TWRP and be able to restore your backup, hope it is still there. Since it is likely that you were last using an older version of TWRP for MMuzzy, you might notice differences if you flash a newer version of TWRP.
kaijura said:
For my instructions, download these, you will end up using them:
1. Android drivers for windows, I would prefer Universal Naked Driver (UND):
http://forum.xda-developers.com/showthread.php?t=1766220
2. Android debugging tools (ADB), I would prefer minimal ADB:
http://forum.xda-developers.com/showthread.php?p=42407269
3. TWRP recovery image: http://www.teamw.in/project/twrp2/90 download the last version you remembered using or just use the latest openrecovery-twrp-2.6.3.2-maguro.img
Install 1 & 2 in order. You may need to have the phone boot to recovery to install #1. Installing the drivers in Windows XP/7 will be easier, Windows 8/8.1 requires an advanced step to disable unknown driver enforcement.
For #2, if you have ADB/Fastboot already, skip this step. If you don't, then you may need to install it while in recovery too. Install it to a folder you are familiar with, I would choose C:\ and make an Android folder.
After you have both installed, boot your phone to bootloader mode. When it is shut off, hold VOL + and - at the same time then press the power button for all 3 simultaneously. It will boot into bootloader mode, where you see the android and your Galaxy Nexus revision/software details.
Move the TWRP recovery img file to the location of your ADB folder. For my example, I will assume #2 (adb tools) are installed in Local Disk (C and the android folder, so C:\Android
From here you would use the command prompt/terminal start > run > cmd or start, find program Command Prompt.
In the terminal type cd\foldertoTWRPimgfile\ or in my example, cd\android\
Next, type fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
my example would look like:
C:\android\ fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
it will show a progress indicator, then OK'd when it is finished.
You can then manually boot to recovery in fastboot, hit a volume button on your phone a few times until you see RECOVERY, then hit the power button to load it. You should now be in TWRP and be able to restore your backup, hope it is still there. Since it is likely that you were last using an older version of TWRP for MMuzzy, you might notice differences if you flash a newer version of TWRP.
Click to expand...
Click to collapse
Wow... I really do not know where to begin to thank you... that REALLY saved my bacon as it is my work phone as well as personal cell too. Please send me a PM with a donation addy and an amount if you have one or I would be happy to send you a Christmas present...
Merry CHRISTmas everyone!!!!

[Q] Unfortunately, Google Keyboard Has Stopped

A few months ago I decided to try and root my Nexus 7 (2013) tablet. At this time I simply cannot remember what process I used but all I know is that everytime I try to power it on the system start screen comes on where it asks what country you're in and so forth. But I also get the following Pop Up Error message "Unfortunately, Google Keyboard Has Stopped" and an "OK" button. When I click on OK the error message simply pops back up in a never ending loop. It stops at the SELECT WI-FI screen and won't let me input the access code because of the Pop Up Error message.
Does anyone have any idea how to completely wipe the system and bring it back to stock or just to the point I can do "anything"?
Thank you in advance for your assistance!
Boot into fastboot by holding volume down and power while the tablet is off. Scroll through the options with volume keys. When you see the option recovery mode at the top of the screen, press power. This will boot you into recovery. From there, there will be several option. One of which should be a hard reset. navigate using the volume keys. You should be OK from here.
sent from my nex7
Thank you for your reply but unfortunately this doesn't work. It puts me right back to where I always end up and still get the Error Message stated above.
I've been working on this for a few hours now and nothing! It basically says I don't have a Keyboard installed after I do anything. If I Factory reset it I get the same Error Message about no keyboard.
Any ideas? PLEASE HELP!
That is really weird. Do you have a custom recovery installed? Custom ROM? Does the computer find it? because flashing a stock image may be the way to go from here.
sent from my nex7
mugzylol said:
That is really weird. Do you have a custom recovery installed? Custom ROM? Does the computer find it? because flashing a stock image may be the way to go from here.
sent from my nex7
Click to expand...
Click to collapse
Thank you for your reply. I greatly appreciate you taking the time. I am at wits end at this point and simply need it to run again. Can you talk me through loading whatever to get it back to new? I'll take anything at this point. Everything is backed up so I have nothing to lose. How can I load the original image? (non rooted)
Thank you!
I AM NOT RESPONSIBLE FOR ANYTHING IF IT GOES WRONG (it should not go wrong though)
First you will need an image. Search for a stock 2013 nexus 7 image. Than you will need to download google USB drivers :
http://developer.android.com/sdk/win-usb.html
Than install them by opening the device manager program which is installed by default on any windows computer. Plug your tablet in, right click it in device manager and press update driver software and browse for the driver you downloaded. Than install it.
Now that that is done download the android SDK.
http://developer.android.com/sdk/index.html
Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on
"open new command window here"
Now put your tablet into fastboot mode. Type
"fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Now type "fastboot OEM unlock" in the command window. Select yes on your tablet with volume keys and click power on your tablet. Than it will run through the unlock bootloader practice. This will erase all content on the tablet. It may take a bit.
Once that is done, put your image in the tablets internal storage.
Now download the latest twrp for your device.
http://teamw.in/project/twrp2/193
Press download latest .img
Now, put your twrp image in the platform tools folder and name it something easy to type. Now, in the command window type:
Fastboot boot (name of your twrp here).IMG
This will boot into twrp. It will not install it.
Now, in twrp press install and browse for your image (must be a .zip file) and flash it. If all goes well than reboot your system. If there is a problem try another image.
You do not need to unlock bootloader or install drivers again. Just boot back in to twrp and flash another image (if it goes wrong)
Stuck
mugzylol said:
I AM NOT RESPONSIBLE FOR ANYTHING IF IT GOES WRONG (it should not go wrong though)
First you will need an image. Search for a stock 2013 nexus 7 image. Than you will need to download google USB drivers :
http://developer.android.com/sdk/win-usb.html
Than install them by opening the device manager program which is installed by default on any windows computer. Plug your tablet in, right click it in device manager and press update driver software and browse for the driver you downloaded. Than install it.
Now that that is done download the android SDK.
http://developer.android.com/sdk/index.html
Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on
"open new command window here"
Now put your tablet into fastboot mode. Type
"fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Now type "fastboot OEM unlock" in the command window. Select yes on your tablet with volume keys and click power on your tablet. Than it will run through the unlock bootloader practice. This will erase all content on the tablet. It may take a bit.
Once that is done, put your image in the tablets internal storage.
Now download the latest twrp for your device.
http://teamw.in/project/twrp2/193
Press download latest .img
Now, put your twrp image in the platform tools folder and name it something easy to type. Now, in the command window type:
Fastboot boot (name of your twrp here).IMG
This will boot into twrp. It will not install it.
Now, in twrp press install and browse for your image (must be a .zip file) and flash it. If all goes well than reboot your system. If there is a problem try another image.
You do not need to unlock bootloader or install drivers again. Just boot back in to twrp and flash another image (if it goes wrong)
Click to expand...
Click to collapse
OK, a couple of things;
1. I'm using a MacBook Pro. Does this make any difference? (It says I don't have to download any drivers using a Mac but other than that is there any differences?)
2. I'm stuck at ..... Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on "open new command window here". Now put your tablet into fastboot mode. Type "fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Everything I do doesn't work. When I hold down Shift and Right-Click on the Platform Tools Folder I do not see "open new command window here". Is this the "platform-tools folder under the SDK folder?
Do you have any windows computers because this will not work without one
sent from my nex7
---------- Post added at 08:27 AM ---------- Previous post was at 08:25 AM ----------
This is because Mac computers do not execute batch scripts and the fastboot commands are made to execute through a command prompt rather than a Linux terminal
sent from my nex7
I honestly made this way too complicated. Just run through setup without using the keyboard. Find an unprotected network (like McDonald's) that works and find a way to get your hands on an apk of any keyboard and install it. I'm not quite sure how you can get a download link to a keyboard with no account (yet) and no keyboard but there must be a way. Its a simple issue that causes so many problems. So in a nutshell, if you can find a way to install an apk of any keyboard, your good
sent from my nex7

[GUIDE] Root and unbrick steps for ASUS ZenPad C 7.0 (P10Z - Z170C)

Hi all! It took me a lot of time to finally being able to root this tablet. It's old, slow and practically unusable, but with some tricks it can be made much, much better. I'm going to explain what you need to do to root this tablet, and in case of brick (which happened to me many, many times) how to unbrick it. I even got to a point where I could not even boot into recovery mode, and only fastboot was working, that was scary, but I managed to get out. Every single file I will use will be bundled in a ZIP you can download, and I'll try to make sure this link stays up, because there's nothing more frustrating than wanting to make these things in the future only to find out the link is dead, along with all your hopes. Before we begin, a little disclaimer:
Code:
#You, and only you are responsible for everything that you do or happens to your tablet.
#If you screw up, I have a number of backups to help you recover, but if that's not enough don't point a finger at me.
#I will not be babysitting anybody to help restore their tablet or recover lost data.
#This process WILL wipe all of your data, do a backup before beggining.
#YOU HAVE BEEN WARNED!
1. ENABLING USB DEBUGGING
This is a very basic step, but it's needed if you want to even begin to do this. You'll need to go to "Settings -> About Phone". There, look for a line that says "Compilation Number" (or something like that) and tap it multiple times. You will see a message pop up saying "You are now a developer" (I wish it was that easy). Go back to the settings screen, you will see a new option appeared called "USB Debugging". Enable it, and make sure "Developer Options" are enabled too at the very top of the screen. Now, connect the tablet to your computer. You will see a message pop up asking for permission, tap "Always allow from this computer" and press "Allow".
That's it for this step.
2. SETTING UP ADB TOOLS AND MAKING SURE THEY WORK
Now that we have USB debugging enabled, and we have allowed our PC to access the tablet, we can begin setting up ADB. The required files are attached in the zip.
Extract the "platform-tools" folder and move it somewhere nice. Then open it, hold shift and right click in a white space and select the option "Open command window here". CMD will pop up, now type:
Code:
adb devices
It will probably say something about a server followed by a list of attached devices. If you see a serial number there, then great! ADB is working as it should. If not, make sure the tablet is connected, that USB Debugging is on, and if all else fails, try with another cable.
Now for the juicy part.
3. UNLOCKING THE BOOTLOADER
We will have to unlock the bootloader if we want to do anything here. Here's what to do. Type:
Code:
adb reboot fastboot
Wait until the tablet reboots into fastboot. Once there type:
Code:
fastboot oem unlock
fastboot oem unlock confirm
This should unlock the bootloader.
NOTE: This method of unlocking is reported to not work anymore, but I listed it anyway just in case, as it doesn't hurt to try. If this is not working for you, don't panic, it's normal, use the following code instead:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
This should work, and the bootloader should be unlocked now.
4. INSTALLING THE REQUIRED FIRMWARE
Now, your tablet may or may not have the required firmware for the procedure, but just in case we will flash one that's sure to work. If you followed along, you should be in fastboot mode right now. Type:
Code:
fastboot reboot
Your tablet should boot as normal, without any changes (unless the first bootloader unlock method worked for you, in which case it probably wiped all of your data). Now we can access ADB once again, so type:
Code:
adb reboot recovery
The tablet will reboot into recovery mode and you should see an image of wasted android with an open belly (if you don't see this it doesn't matter). You should see a list of options with blue text, you must use the volume keys to navigate this menu. If you don't see any options, press any volume key and they should appear. If instead of getting into recovery mode, the tablet just turned off, then go to the "Fixing recovery" section.
In this menu, you must select "Wipe data/factory reset". This will, obviously, wipe all of your data. Once that finishes, select the "Install update through ADB" option. Once that's done, make sure the "updated_firmware.zip" file is in the same directory as the "adb.exe" file, then type:
Code:
adb sideload updated_firmware.zip
This will install the firmware, it will take about 20 mins. Once finished, reboot the device. You may think it got bricked at this point, fear not, the first boot really takes this long (about 10 mins).
Once everything is done, the device should boot up and everything should be exactly as it was when you took it out of the box, meaning, it doesn't even remember your wifi password. Do a quick (but proper) set up and enable USB Debugging again, make sure to allow the PC again (and check the "always allow" box). Also, scroll down a bit more in the developer options section and look for one that says "Verify apps installed through USB" or something of that kind. Make sure it's unchecked. Now, we gotta install root.
5. ROOTING
The all holy root, finally here. Type this into the terminal:
Code:
adb reboot fastboot
You should be familiar with this process by now. Once in fastboot mode, type:
Code:
fastboot boot root.img
Once finished, reboot. You should boot up as a rooted user, hooray! Only one final step, we gotta give ourselves some means to control this new power, that's where the SuperSU app comes into play.
6. INSTALLING SUPERSU
Apparently, not every single SuperSU apk file works... but lucky for you, I managed to scout and bundle one that does, so use that one. Make sure the apk file is in the same folder as "adb.exe" (as with all of the previous files) and type:
Code:
adb install supersu-2-82.apk
Leave it a few mins, and you should see a "success!" message when it's finished. Open the SuperSU app and it will tell you that you need to update the binaries. Say yes to that, and when asked wether to do a "Normal" update or "TWRP" update, select normal. It should be successful and prompt you to reboot, do so.
That's about it, you now have root access in the ASUS ZenPad C 7.0.
NOTE: Every single attempt I made to make the SuperSU app a system app resulted in the app crashing and I needed to reinstall it again, do as you please.
Why would you even want to do this you might ask? Well, I personally used this to make a few tweaks with Kernel Auditor and L Speed, two apps that will let you customize the performance of the machine to its maximum... sacrificing battery of course. You can search online for the best configuration for you for these apps. With the right tweaks, it transforms from **** to usable, and you need root for all of this.
As a quick note, you might notice that the SuperSU pop up that prompts you wether to grant or deny root access to an app is delayed, that's just how life is with this machine, it's slow. As a tip, when an app is trying to acquire root access, go back to the home screen and open the SuperSU app, then go back to the app you were trying to give it access to, it should appear quicked that way. Sometimes it's so slow that the app says I don't have root, only to have the pop up appear 10 seconds later. Now... to a final chapter.
7. UNBRICKING
This would be the end of the story if nothing went wrong, you have a rooted tablet and you can now do whatever you want with it, but that's not how life is. **** happens, things can go wrong, and when they do, you better have a backup plan. I don't know how to get back your ex, but I know how you can unbrick your tablet if that should happen. Follow these steps if you want to recover this machine...
Code:
#This process will wipe all data, but you shouldn't care about that since you can't access it anyway.
So, if the tablet doesn't turn on and gets stuck at the boot up screen, what can we do? Well, let it sit at the boot up screen for a few mins, and then type in the terminal:
Code:
adb devices
If it's recognized, then type:
Code:
adb reboot recovery
If it's not recognized, press the power button and the volume down key until the tablet turns off. Once that happens, press the power button and the volume down key, when the logo appears, let go of the power button and keep the volume down key pressed, that should boot the tablet into recovery mode. If you got into recovery mode, skip to 7.2
7.1 FIXING RECOVERY MODE
Sometimes, (it happened to me), recovery mode is broken.... it just doesn't appear, no matter what you do you can't get into it. To fix this, we gotta flash it again. We gotta enter fastboot mode. One option is to boot up the device until it gets stucked and wait a few mins, then adb should be able to recognize it and you type:
Code:
adb reboot fastboot
If that's not the case, turn the tablet off and press power and volume up, that should get you to fastboot. Once there type:
Code:
fastboot devices
And the tablet should appear there, if it doesn't... well it better do. I don't really know what to do if it doesn't appear there, but there shouldn't be a reason for it not to. I guess you can try to enter fastboot once again, with the tabler connected from the beggining or something like that, let's just assume it does, and if it doesn't then I'm sorry to tell you that's homework you will have to do.
Once here, we must format the cache and the data partition, for that type the following:
Code:
fastboot format cache
fastboot format userdata
Now, we need to get the recovery files, grab them from the zip I gave you. The files in question are "recovery.bin" and "vrl.bin". We will start with vrl. Once the two formats are finished, type:
Code:
fastboot flash vrl vrl.bin
Followed by:
Code:
fastboot flash recovery recovery.bin
Once that's done, press the power button and volume down keys until the tablet turns off. Then, press them again until the logo appears, and when that happens let go of the power button, that should get you (finally) into recovery.
7.2 UNBRICKING (FOR REAL THIS TIME)
Well, now that everybody is on the same page, and we could get to recovery mode, it's time to repeat some steps really... Follow the procedure from step 4 onwards (from the part that tells you to go to recovery). So, wipe data and apply that damn zip with sideload, the tablet should work now.
That's all I have to offer guys. I'm not a developer, I'm just a guy with a bunch of free time on his hands, so I was able to gather all of this information and (most importantly) files so you can root and fix this god damn tablet. Until the next one!
FINAL NOTE: In the files I included, there's a TWRP.img file. This is the TWRP custom recovery. As far as I know, this version should work with this tablet, but I was unable to flash it and make it work. IF YOU WANT TO TRY THIS DO SO AT YOUR OWN RISK, IT'S HIGHLY PROBABLE THAT THIS WILL RESULT IN BRICKING YOUR TABLET AND BREAKING THE STOCK RECOVERY, IN WICH CASE YOU WILL NEED TO FOLLOW THE STEPS STATED IN THIS GUIDE.
I couldn't upload the files as an attachment directly... sorry.
The "updated_firmware.zip" file is added as a separate download because it's a bigger file, and I prefer to let people decide if they even want it in the first place.
updated_firmware.zip
Everything else
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
neghvar said:
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
Click to expand...
Click to collapse
Make sure you enable usb debugging, no driver will work without that enabled.
tralph3 said:
Make sure you enable usb debugging, no driver will work without that enabled.
Click to expand...
Click to collapse
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
neghvar said:
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
Click to expand...
Click to collapse
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
tralph3 said:
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
Click to expand...
Click to collapse
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
neghvar said:
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
Click to expand...
Click to collapse
Yeah I never could get around it either. I never could install a custom recovery on this tablet, it just wasn't made for it. But hey, root is cool.
Work?
Still working?
jerryspring said:
Still working?
Click to expand...
Click to collapse
Why wouldn't it? This tablet ain't gonna change. Everything should work no problem.
Hi, any custom rom for this device to make it useful ?
It is in my drawer for more than 2 years and I just do not know what with it
Also how to play with settings in root mode so I can make it faster ?
Hey folks,
I recently followed this guide and a couple of issues.
First, I had expected all my data to be gone, which is fine. But it wasn't. I seemed to have gotten all the way through without it being reformatted, and this makes me suspect I never really achieved all the goals.
One thing I should note, in recovery boot, I had to use the volume button to select a source. No big deal, but it had not worked until I guessed I needed to do that.
Oh, and another thing is I had to install the driver package, and then after, once it was rebooted into fastboot, manually guide the device manager to select from list.
It seems after complete shutdown and then a fresh bootup, my SuperSU software was gone. So, is this only a tethered root boot? Is there a completely untethered?
After rebooting again, it seems my device will not complete booting, but I will give it some more time. I may have bricked it, though I have no idea how lol. All I did was enable USB debugging again and issued the reboot command.
I know this is an old guide, and probably long forgotten by most participants, but I recently got one of these tablets online, open box but new or like new, for around $20, and I would like to get it rooted because otherwise, it is extremely sluggish and the battery drains very fast. I read online it is google play services at fault, but I do not know for sure.
Anyway, if anyone has any updated info or alternative method to achieve full root access untethered, please advise. Unless this guide is that, in which case I just need to try again. Just out of curiosity, what is the TWRP.img for?

Id like to beg for help with rooting my RN 8 Pro

Basically I have rooted my old Redmi Note 4 but that was past guarantee so I did not care that much.
My current RN 8 Pro is still 1 year in guarantee so I literally do not have the balls to do it on my own.
Is there any good soul who would help me out with rooting it, pretty please? Thanks very much in advance
btw. I do know stuff about Unlocking Boot Loader, installing TWRP trough Command Window and Flashing Magisk...that should be potentially enough but as I said above no balls and do not want to F things up and brick it.
Redmi Note 8 Pro Guide [Firmwares | ROOT CN/GLOBAL | TWRP Recovery]
Redmi Note 8 Pro [Begonia] [Global Version Only] WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT...
forum.xda-developers.com
A great guide is here :3
Not sure you need my help for that but yeah if ya run into any problems, ill be here to help ya
Ty for responding. I read that but Im still not sure about what TWRP use on my phone (im not sure if i have to use special one or just latest version) and because I want to only root my phone Im also not sure, if I need to get a different ROM or I can do that on this STOCK ONE I have.
I bought my RN 8 Pro in EU. Im gonna try to give you more information about my phone, if you would be able to link me TWRP what I need and other files to root it...that would be awesome (its not like i cant read or im lazy f**k, its more like i dont want to F things up).
Version of MIUI: MIUI Global 12.0.5; Stable 12.05.0(QGGEUXM)
Version of Android: 10 QP1A. 190711.020
Android Level of Security: 2021-04-01
Thank you very much
1. UNLOCKING BOOTLOADER :
- Download the Mi Unlock app to PC, and sign in with your Mi Account;
- Enable Developer Option in your phone by tapping the "Build Number" 7 times
- Go to Developer Options "Settings > Additional Settings > Developer Options
- Enable USB Debugging and OEM Unlocking
- Aslo add account in Mi Unlock Status (Can be found in Developer Options
- Install all the required drivers (adb drivers, vcom drivers etc.) In your PC [I'll link these below]
- Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot mode
- Connect your phone to PC using USB cable and click "Unlock". In Mi Unlock Tool
- You will be given a specific time (168 hours mostly)
- Wait until that and redo Unlock process
- Your device’s bootloader is unlocked
2. FLASHING TWRP :
- Install Minimal ADB and fastboot on your PC [Link will be provided below]
- Download LR Team TWRP [This work for now, I'll provide link below and will update it after we have another proper TWRP]
- Put that TWRP in the file location of ADB and Fastboot (Right click on Minimal ADB and Fastboot icon on desktop and click on Open file location)
- rename that recovery to "twrp" for convenience (optional)
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode
- Type
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type
Code:
fastboot flash recovery twrp.img
- When it's done, Remove cable and Hold Power + Vol. Up when phone starts turning on leave the power button but keep pressing Vol. UP until TWRP splash Screen shows up.
- Done
3. ROOTING :
- In TWRP mount System
- Go to Advanced > file manager
- then go to system_root > system and delete "recovery-from-boot.p"
- Go home and again go to advanced and Select "Close AVB2.0" swipe to confirm.
- Go back and select "Install Root"
- Here you go magisk 19.4 will be installed (U can chose any other versions afterwards.)
- Reboot the device to system.
- Done!
LINKS
1. Mi Unlock tool
2. Minimal ADB and Fastboot
3. ADB Drivers for MTK
4. MTK USB Drivers
5. LR Team TWRP
Hello once again...I might need some help
I was following these steps but after flashing this TWRP I cant enter into the TWRP...so far Ive tried holding power button then pressing Volume +; holding power button and then holding Volume+; even holding them both but still without any result...any chance you might help me here, please?
*EDIT: Im flashing stock ROM
Go to the system then do
adb reboot recovery
I flashed TWRP recovery once again, then I went for "adb reboot recovery". This is what happened after I used "adb reboot recovery" (attached picture). There is no sign about TWRP. What am I doing wrong? I literally followed the guide the flash of the recovery TWRP is successful. Is there any chance that Im flashing wrong TWRP recovery? Or that Im doing it on stock ROM? Usually its problem between chair and keyboard but I dont know :-/.
So Ive tried to boot TWRP through after flashing it with "fastboot boot twrp.img". It went through but it booted like normal so I ended up in system like when you turn on your phone normally.
Anybody, anything please?
N00B92 said:
Anybody, anything please?
Click to expand...
Click to collapse
First: what version of miui?
If you're on miui 12.5 this method will cause reboot.
If your phone is < 12.0.X its okay.
It looks like flashing recovery worked.
Instead of trying to adb reboot recovery after flashing recovery try this:
- When it's done, Remove cable and Hold Power + Vol. Up when phone starts turning on leave the power button but keep pressing Vol. UP until TWRP splash Screen shows up.
Version of MIUI: MIUI Global 12.0.5; Stable 12.05.0(QGGEUXM)
Version of Android: 10 QP1A. 190711.020
Android Level of Security: 2021-04-01
I was already trying that, if I do it how you typed the screen is gonna keep blinking with MIUI logo.
I was looking for the answers and I found smth about "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable android verified boot, but dunno if its my case on stock ROM or not.
N00B92 said:
I was looking for the answers and I found smth about "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable android verified boot, but dunno if its my case on stock ROM or not.
Click to expand...
Click to collapse
First you need to enter recovery, i think you didn't flash boot.
Follow the method below exactly.
Original post and files can be found here.
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
I dont have any boot.img in my folder so I cant flash the boot.img. Having stock ROM and I have no clue where to get it.
My current ROM is MIUI Global 12.0.5; Stable 12.05.0 (QGGEUXM) and I think I just found it here on this link:
https://xiaomifirmwareupdater.com/miui/begonia/stable/V12.0.5.0.QGGEUXM/
Can anybody experience confirm that Im suppose to copy out the boot.img out of it and then copy&paste it into Minimal ADB and Fastboot in C: of my PC and then going for the "fastboot flash boot boot.img" as the last msg from Donkyshot says?
Tyvm
Id appreciate any help
Everything I did try is above.
N00B92 said:
My current ROM is MIUI Global 12.0.5; Stable 12.05.0 (QGGEUXM) and I think I just found it here on this link:
https://xiaomifirmwareupdater.com/miui/begonia/stable/V12.0.5.0.QGGEUXM/
Can anybody experience confirm that Im suppose to copy out the boot.img out of it and then copy&paste it into Minimal ADB and Fastboot in C: of my PC and then going for the "fastboot flash boot boot.img" as the last msg from Donkyshot says?
Tyvm
Click to expand...
Click to collapse
madsponge26 said:
Redmi Note 8 Pro
[Begonia]
[Global Version Only]​
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Firmwares
Global Stable
V10.4.1.0.PGGMIXM
V10.4.2.0 to V11.0.10
V11.0.1.0 PGGMIXM
V11.0.3.0 PGGMIXM
V11.0.4.0 PGGMIXM
V11.0.6.0
China Stable
V10.4.4.0.PGGCNXM
V10.4.6.0.PGGCNXM
V10.4.8.0.PGGCNXM
V10.4.9.0.PGGCNXM
V10.4.10.0.PGGCNXM
V10.4.11.0.PGGCNXM
V11.0.1.0QGGCNXM
China Beta
V9.9.25
V9.10.17
India Stable
V10.4.3.0.PGGINXM
V11.0.1.0 PGGINXM
Europe (EEA)
V10.4.5.0.PGGEUXM
Indonesia
V10.4.2.0.PGGIDXM
V11.0.1.0PGGIDXM
Russia
V10.4.2.0.PGGRUXM
USB Drivers
Download
Unlock Bootloader
Enable OEM Unlocking
Unlock Here
Installing TWRP Recovery and ROOT
Enable USB Debugging - Goto Settings / Additional settings / Developer options / USB Debugging & USB debugging (Security settings) - Enable (If you have not activated Developer options, then Goto Settings / About phone / tap MIUI version 7 times - now developer options enabled.
Global Version
GLOBAL firmware V10.4.5.0.PGGEUXM only
Drivers installed properly
Enabled USB Debugging (enabled developers menu)
1. Turn Off
2. Go to Fastboot mode (Volume - + Power)
3. Connect to the PC
4. Download and extract in C drive, "Run as administrator" and execute "ifelixit+FLASHER+TOOLKIT+Begonia.bat".
5. Choose 1 (TWRP recovery) and enter or Choose 2 (Root Only)
Immediately disconnect the phone from the PC, otherwise it will go to reboot on command and the stock recovery will be restored.
6. Put the Minimal ADB and Fastboot in C: of your PC.
Transfer the Recovery.img in Fastboot folder
Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
7. Type fastboot flash recovery recovery.img and enter (TWRP will be installed)
8. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Stock boot IMG for V10.4.5.0.PGGEUXM just in case bootloop
TWRP for Begonia
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Proof of Video that Redmi Note 8 Pro Rooted
Contributors
Nikas
esleer
Xakep1993
SPIRITic
m3lbrunton
Lyelik74
@topjohnwu
TWRP Community
XDA Community
Xiaomi Community
Click to expand...
Click to collapse
Well look here.
This is the original post the person above put soooo
Yeah the boot.img is in there.
Kenora_I said:
Well look here.
This is the original post the person above put soooo
Yeah the boot.img is in there.
Click to expand...
Click to collapse
Thanks. I used the boot.img and I was following the guide which "donkyshot" sent. But I got stucked right after I did those commands in command Window. I disconnected the phone went for the power button hold and then when it was blank I stopped holding power button and I started holding the Volume+ button. The phone was bootlooped on Xiaomi logo...I was waiting several times but nothing. At the end I had to flash the phone with stock ROM I downloaded through MiFlash...I really dont know what I was doing wrong.

Categories

Resources