Related
Here We have the Root And CWM for Nexus 4 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 4.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 4
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 4
Step 6 - Download CWM 6.0.2.3 (recovery-clockwork-touch-6.0.2.3-mako.img) and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 4 How? Press Volume Down + UP + Power keys for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
fastboot flash recovery recovery-clockwork-touch-6.0.2.3-mako.img
Click to expand...
Click to collapse
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 4 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 10
Root and CWM for Nexus 7
Thanks i need this
Reserved...
AW: [How-to]Root Android 4.2.2 And Install CWM v6.0.2.3
Fastboot download ist down
Gesendet von meinem Nexus 4 mit Tapatalk 2
nekbreak said:
Fastboot download ist down
Gesendet von meinem Nexus 4 mit Tapatalk 2
Click to expand...
Click to collapse
link updated
Fastboot download link still not working for me. Configured as http://*******/BLr6S, which goes nowhere
You should also mention that macs use ./fastboot-Mac and Linux ./fastboot
I'm quite shocked that I updated my phone and super user was not deleted.
I did revert back to stock recovery though before trying to update.
quick question regarding CWM touch vs non-touch pros/cons of each
pda12 said:
quick question regarding CWM touch vs non-touch pros/cons of each
Click to expand...
Click to collapse
Same thing. 1 uses volume keys the other is touch control.
thanks for the reply. I guess touch CWM is the way to go as it saves the buttons from abuses
thanks, this is what i need
failed locked
new to the nexus 4(delivered today) but have experience on xperia play
just followed your very useful info and got this
C:\Android>fastboot flash recovery recovery-clockwork-touch-6.0.2.3-mako.img
sending 'recovery' (7808 KB)...
OKAY [ 0.484s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.484s
got green robot with loys of info and at bottom says locked
is there a point i need to do first
on 4.2.2
thanks in advance
yuki71 said:
C:\Android>fastboot flash recovery recovery-clockwork-touch-6.0.2.3-mako.img
sending 'recovery' (7808 KB)...
OKAY [ 0.484s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.484s
got green robot with loys of info and at bottom says locked
is there a point i need to do first on 4.2.2
Click to expand...
Click to collapse
You have to unlock the device before you can root it. There are tools and guides here to spell out the details, but you'll first need to get into bootloader mode and then execute a command along the lines of
Code:
fastboot oem unlock
Only after the phone is unlocked can you proceed to flash custom recovery and super user files, etc. to root the phone. That's from memory, though. Make sure to look around here for a guide that spells out all the details before doing the rest.
Unlocking your phone will delete any data you may have accumulated in the short time you've had the phone, so after you've done that, the phone will be as it was when you opened the box (unless it came with 4.2.1 and you updated to 4.2.2, then it'll still be 4.2.2), other than that it's unlocked.
maigre said:
You have to unlock the device before you can root it. There are tools and guides here to spell out the details, but you'll first need to get into bootloader mode and then execute a command along the lines of
Code:
fastboot oem unlock
Only after the phone is unlocked can you proceed to flash custom recovery and super user files, etc. to root the phone. That's from memory, though. Make sure to look around here for a guide that spells out all the details before doing the rest.
Unlocking your phone will delete any data you may have accumulated in the short time you've had the phone, so after you've done that, the phone will be as it was when you opened the box (unless it came with 4.2.1 and you updated to 4.2.2, then it'll still be 4.2.2), other than that it's unlocked.
Click to expand...
Click to collapse
many many thanks for that information
Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:
TheTigerDeveloper said:
Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:
Click to expand...
Click to collapse
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:
shubham1120 said:
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:
Click to expand...
Click to collapse
i know, but with this one any type of user can follow the guide (especially linux user)
my phone keep restarting, i have try this method, no works, helpppppppp
it stuck on honor logo
Hi Guys,
i got the same problem here with my H60-L12
After flashing Beta Lollipop 5.1.1 i tried to go back to 4.4.4.
Now it's stuck in bootloop and now it keeps flashing the honor logo.
Tried to unbrick it with Multi-Tool and different stock roms but i cant get into recovery or the 3 button install method, only thing working is fastboot mode.
Any suggestions?
Thank you!!
ok, now i'm desperate.
Got different Stock Roms (4.4 5.8.1;4.4 B119;4.4 B310; 4.4 B316, tried TWRP in different versions, even tried to reinstall fastboot drivers , same problem on Windows 10 and 7.
Only think working is Fastboot&Rescue Mode (White Screen, Phone UNLOCKED), but only when plugged in on PC with USB cable.
When plugged in charger, it just reboots and reboots i can't switch to Recovery or Fastboot mode and doesn't even charge the phone.
Maybe someone got any idea, did i use wrong stock roms? Do i have to use Rollback/Revert versions?
Any way to back to stock rom without unlock bootloader?
I've made a horrible mistake.
I was on 5.9.16, tried to downgrade by flashing system, recovery, cust and crc.
Unfortunately I've done it with B316, which is 4.4.4, so i got this annoying bootloop, in which i can't access recovery, bootloader or use the 3 buttons method.
It seems as if the phone tries to forcefully boot into system ignoring everything I do.
I tried draining the battery to turn it off, which worked, but when i charged it it tried to system boot as soon as there's enough battery.
Any ideas?
and where can I find update.app?
This worked for me! I switched from CM11 to the stable 5.1.1 release using your guide. Flashed B370 and then did a local update for the stable lollipop rom. Thanks a ton.
i need help
I extract listed file and open cmd.
I was able to reboot into bootloader.
I writing "fastboot.exe flash boot BOOT.img" and here is the result:
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s
Whats now?
I have rooted H60-L04 with cyanogenmod 11-20150822 KitKat
Thanks
Michal
yeah, very easy guide
i did to my H60-L04 CM11
thanks for sharing
error
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s
i couldnot flash stock recovery because of the fail command not alowed,
i couldnot flash stock recovery because of the fail command not alowed,
Thank you so much! Now my phone is bricked... How about not sharing ur help when u don't know what could happen?
My phone shows Rescue Mode
Attention! Please update system again!
Error!
FuncNo (FUNC_BOOT_KERNEL)
Error NO: 2
i couldnot flash stock recovery because of the fail command not alowed,
i couldnot flash stock recovery because of the fail command not alowed,
thalaraj1992 said:
i couldnot flash stock recovery because of the fail command not alowed,
Click to expand...
Click to collapse
are you on a boot loop?
make sure your device is recognized by your computer.
download universal-adb-driver for windows and install
I have a locked bootloader, and want to restore my phone to stock ROM so I can download OTA updates. I have downloaded the restore to 5.0.2 windows tool, but I need the correct firmware for my phone. Where can I download from. Could you provide a download link? My system version is 22.41.24.thea_retgb.retgball.en.GB retgb
Build number is LXB22.99-24. My phone is XT1072 I am running android 5.0.2
Many thanks.
This will work fine unless you want 5.0.2
Just a note, DO NOT USE that bat script from the general forum, is not complete, everything you need is in my sign, script and mfastboot
Thanks for the links. Where can I find the script and mfastboot?
orbitingful said:
Thanks for the links. Where can I find the script and mfastboot?
Click to expand...
Click to collapse
Look at my sign.
Found it. Is your BAT file compatible with my XT1072 GB phone, because it says RETLA? Also, do I just place the contents of the ROM zip in the same folder as your script?
Thanks.
orbitingful said:
Found it. Is your BAT file compatible with my XT1072 GB phone, because it says RETLA? Also, do I just place the contents of the ROM zip in the same folder as your script?
Thanks.
Click to expand...
Click to collapse
Those bats are made for XT1072, so yes, they should work on any moto g gen2 i think.
I don't know where you read retLA, i have linked you the latest builds of 5.0.2 retGB and 6.0 retGB
Follow this simple step-by-step guide
1- Check if you have MotoDeviceManager installed for the usb drivers
2- Download this XT1072_THEA_RETGB_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml.zip (GDrive mirror from Hemphiz) or from Filefactory
3- Download this https://mega.nz/#!flMFxT7a!uKLcNK_Ge6CsVxjSFDU06YRO3GMZFj39Zl-vVNbEVzo
4- Download the script for MM https://mega.nz/#!Od1i0I4a!3Oz4Wp4iYf_w5C0NLK438h-Ea1mXvUkHTDFzl7ie7cc
5- Extract the content of the rom zip in a folder (ex c:\rom)
6- Extract the content of Fastboot&mastbootV2.zip in the same folder of the rom files
7- Move the bat script in the same folder as step 5-6
8- Now you should have 22 files and 0 folders in c:\rom
9- reboot to bootloader and connect the phone
10- Doubleclick the bat script and wait for the phone to flash, it will self-reboot once done
First boot on 6.0 can take 20/25 minutes, so unless it's bootlooping don't panic and wait.
I know you asked for 5.0.2 but 6.0 is not bad, if you want 5.0.2 at step 2 dl this zip and on step 4 use XT1072 *.bat Flash Script for LP(5.0.2)
Hello, can you help me?
I did everything in the order to downgrade to 5.0.2, but the script tells me following:
Code:
C:\rom>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261758 KB)...
OKAY [ 8.254s]
writing 'system'...
[B](bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)[/B]
finished. total time: 8.633s
My phone is atm on 6.0 24.41.34.thea_retde
dasgnu said:
Hello, can you help me?
I did everything in the order to downgrade to 5.0.2, but the script tells me following:
Code:
C:\rom>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261758 KB)...
OKAY [ 8.254s]
writing 'system'...
[B](bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)[/B]
finished. total time: 8.633s
My phone is atm on 6.0 24.41.34.thea_retde
Click to expand...
Click to collapse
Assuming you have the same model as the OP (XT1072 )
You used the retDE fw ? I'm not aware of any troubles downgrading this phone from MM to LL
XT1072_THEA_RETDE_5.0.2_LXB22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
XT1072_THEA_RETDE_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml.zip
dr.nic said:
Those bats are made for XT1072, so yes, they should work on any moto g gen2 i think.
I don't know where you read retLA, i have linked you the latest builds of 5.0.2 retGB and 6.0 retGB
Follow this simple step-by-step guide
1- Check if you have MotoDeviceManager installed for the usb drivers
2- Download this XT1072_THEA_RETGB_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml.zip (GDrive mirror from Hemphiz) or from Filefactory
3- Download this https://mega.nz/#!flMFxT7a!uKLcNK_Ge6CsVxjSFDU06YRO3GMZFj39Zl-vVNbEVzo
4- Download the script for MM https://mega.nz/#!Od1i0I4a!3Oz4Wp4iYf_w5C0NLK438h-Ea1mXvUkHTDFzl7ie7cc
5- Extract the content of the rom zip in a folder (ex c:\rom)
6- Extract the content of Fastboot&mastbootV2.zip in the same folder of the rom files
7- Move the bat script in the same folder as step 5-6
8- Now you should have 22 files and 0 folders in c:\rom
9- reboot to bootloader and connect the phone
10- Doubleclick the bat script and wait for the phone to flash, it will self-reboot once done
First boot on 6.0 can take 20/25 minutes, so unless it's bootlooping don't panic and wait.
I know you asked for 5.0.2 but 6.0 is not bad, if you want 5.0.2 at step 2 dl this zip and on step 4 use XT1072 *.bat Flash Script for LP(5.0.2)
Click to expand...
Click to collapse
Thanks for your step by step guide. I wanted to know your opinion on the success of a dirty flash. This would involve editing the script so that:
"mfastboot erase userdata"
and "mfastboot flash recovery recovery.img"
are removed.
hello,excuse me for my english but i have an problem with my mate s.firmware installed is b145 europe and after i unlock the bootloader and frp i have root and installed twrp.after this operation i have disable option developer in setting and i reboot in twrp for advanced wipe without internal storage.
my phone is in bootloop logo huawei.i have put the dload directory but not work in the recovery stock..return Always on twrp recovery.volume+ ,+ vol- and power go into fastboot mode but not accept command for flash boot.img recovery.img and etc etc because frp is locked!
i'm desperate...please help me..i have used twrp 2.8.7.0 and supersu 2.49..memory of internal storage is 24.7 gb free..i think the system is intact!!thanks
can you reach twrp?
if so, then reboot into bootloader through twrp..then in bootloader you can flash the stock boot.img and recovery.img of the b145..
after that you should be able to reboot normal..
Gesendet von meinem Mate S CRR-L09 B321
Thanks for your support..yes i can reach in twrp and in the bootloader..but My answer is :must i do flash of stock boot.img and recovery.img through fastboot e rescuemode?if so i made it yet and it doesnt work because frp is locked and i have return error with adb fasttool!!
SuperSU 2.42
frisko76 said:
hello,excuse me for my english but i have an problem with my mate s.firmware installed is b145 europe and after i unlock the bootloader and frp i have root and installed twrp.after this operation i have disable option developer in setting and i reboot in twrp for advanced wipe without internal storage.
my phone is in bootloop logo huawei.i have put the dload directory but not work in the recovery stock..return Always on twrp recovery.volume+ ,+ vol- and power go into fastboot mode but not accept command for flash boot.img recovery.img and etc etc because frp is locked!
i'm desperate...please help me..i have used twrp 2.8.7.0 and supersu 2.49..memory of internal storage is 24.7 gb free..i think the system is intact!!thanks
Click to expand...
Click to collapse
Try flashing SuperSU 2.42 from TWRP and see if you´re able to boot. When I installed versions newer than 2.45 I ended up in bootloop.
Edit: Sorry, I mean 2.62 is the right one and over 2.65 will end up in loop. Anyway, try 2.62.
ok..i try this way to install supesu 2.62..this screenshot is result when i reboot into bootloader trought twrp..i not understand because i have this error :command not allowed
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>fastboot flash boot bo
ot.img
target reported max download size of 471859200 bytes
sending 'boot' (23552 KB)...
OKAY [ 0.632s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.632s
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>fastboot flash recover
y recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31372 KB)...
OKAY [ 0.855s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.865s
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>
excuse me but i not post an image!
i have tried to install supersu 2.62 but return message error no os install and the device not have supersu do you want to install??i already installed supersu and i have this message after?..i tried to install supersu 2.75 and i have only the message no os installed..but the phone are same in bootloop....can i search an tool for erase frp tool?for Samsung exist and for sony experia..for huawei?
hello,i verified only method for resume device is use dc unlocker for price 15credit... ...but i have an other idea..i have an other huawei mate s,original stock recovery..can i try to unlock bootloader and developer option , install twrp and try backup for use in the other device ???..is same firmware b145 eu...it could be right way for resume my device?thanks
Hi
I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:
Code:
fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s
and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.
Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....
I'm out of ideas.
to-bu said:
Hi
I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:
Code:
fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s
and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.
Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....
I'm out of ideas.
Click to expand...
Click to collapse
Obviously, you did something wrong.
Try renaming the recovery that you downloaded to "recovery" with no quotation marks
Place the file in the platform tools directory
For example: C:\Android\platform-tools\
Then use these commands.
fastboot flash recovery recovery.img
fastboot boot recovery.img
The commands above will flash the recovery.image to the recovery partition, then reboot then phone to recovery, you will then need to flash root.
If that doesn't work just use the Tool all in One
It seems that i "holding it wrong" but in fact it doesn't work eather.
I'm original on linux but to ensure that it's working i switched to the windows system:
* downloaded and installed "Tool all in One"
* choose correct device
* ensure device allows ADB Access to PC
* ensure unlock status in tool
* use "Recovery Flasher and Rooter"
* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options
* flashed... and nothing again....
So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....
So definitly something is wrong
to-bu said:
It seems that i "holding it wrong" but in fact it doesn't work eather.
I'm original on linux but to ensure that it's working i switched to the windows system:
* downloaded and installed "Tool all in One"
* choose correct device
* ensure device allows ADB Access to PC
* ensure unlock status in tool
* use "Recovery Flasher and Rooter"
* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options
* flashed... and nothing again....
So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....
So definitely something is wrong
Click to expand...
Click to collapse
Are you sure that you have developer options setup? ADB debugging is enabled?
If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.
once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.
The latest Orange Fox is here: https://files.orangefox.tech/OrangeFox-Beta/dipper/OrangeFox-R10.1_002-Beta-dipper.zip
Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)
I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.
If that is not an option:
A lot of people have trouble flashing TWRP, so dont get discouraged. After flashing recovery you must immediately boot to recovery and flash root then choose reboot to recovery. You may see check boxes asking to install TWRP manager, choose yes and reboot to TWRP.
A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?
If your phone doesn't reboot in TWRP it may be overwritten by the ROM's recovery.
Unplug Your phone then Manually boot it into recovery
PS: Welcome to XDA, good manners when someone takes their time helping is to give thanks by clicking the thanks button. Don't say thanks click the button. See the signature. good luck.
Hi,
tsongming said:
Are you sure that you have developer options setup? ADB debugging is enabled?
Click to expand...
Click to collapse
Yes, I am. This is not the first time i switched to lineage /cyanogen mod. I already customized a Nexus 4 (mako), Motorola Moto G (falcon), Samsung Galaxy S4 (jfltexx), Samsung Galaxy Tab S2 (gts210vewifi)
and LG V20 (h990ds). So I'm not new to this.
tsongming said:
If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.
once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.
Click to expand...
Click to collapse
I see this in this subsection and i marked it already, since you suggest it i will try it as soon the flashing is working.
tsongming said:
Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)
I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.
Click to expand...
Click to collapse
Sorry, Germany
tsongming said:
A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?
Click to expand...
Click to collapse
I don't see the point why the image must have a name with only characters, but i renamed the image to twrp.img and tried:
In Android with developer options enabled (and pc allowed):
Code:
adb reboot fastboot
Now i'm in fastboot and using my zsh on linux, im on my home directory located the twrp.img:
Code:
~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.279s]
Writing 'recovery' OKAY [ 0.118s]
Finished. Total time: 1.402s
Now the command to upload and boot to the same image:
Code:
~ fastboot boot twrp.img
Sending 'boot.img' (42044 KB) OKAY [ 1.236s]
Booting OKAY [ 0.067s]
Finished. Total time: 1.341s
On device: bank screen (about 5 sec) > mi logo with unlocked symbol/text (about 3 sec) > mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.
Second try manual:
Code:
adb reboot fastboot
Flashing...
Code:
~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.248s]
Writing 'recovery' OKAY [ 0.107s]
Finished. Total time: 1.360s
Unplug the phone, pressing now together VOLUME-UP and POWER until device going black and mi logo showing and devices vibrates. => mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.
Similar issue
I have the exact same issue. Did you manage to find a solution?
dojabato said:
I have the exact same issue. Did you manage to find a solution?
Click to expand...
Click to collapse
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.
I found the solution
to-bu said:
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.
Click to expand...
Click to collapse
Hello,
I was in the same case like you, to resolve this issue you must install this TWRP : TWRP-3.3.1-1031-XIAOMI8-Q+Version-CN
Sorry I'm new and can't post links...
I installed with the TOOL ALL IN ON => Erase all data => recovery flasher (check only automatic TWRP...) => POWER+Volume down => POWER+Volume up very quickly => Enjoy it !