Database Develop

Flash the Android 4.3 Build [Clean FLASH or Keep Data /w Flash] Root Available

*I'm not responsible for anything you do with this. I'm just trying to contribute back to the community*
Prerequisites
1. YOU MUST BE ON THE FACTORY IMAGE (NO MODIFICATIONS that means no custom recovery, kernels, radios, etc)
**User Impo5sible says its possible with custom recovery and kernels I'm not 100% sure so YMMV*** *ANOTHER EDIT - USERS REPORT GETTING STUCK ON NEXUS LOGO if you have a custom rom/kernel and not using the -w command to wipe DATA)
2. YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
SDK /w adb & fastboot Link: http://developer.android.com/sdk/index.html
PDAnet Link:http://pdanet.co/
3. ENABLE USB Debugging via Developer settings
(press the build button 7 times to activate it the "settings --> about phone --> Build Number --> go back --> Developer Settings --> Check USB Debugging)
4. Android 4.3 Image can be obtained from Google
Image Link: https://developers.google.com/android/nexus/images
When you have all of this installed... you may proceed
Step 1: Use 7zip or compression program equivalent to extract the stock image file that is .TGZ
Step 2: You should see a stock image file that is .TAR...extract this once again with any compression program (you should see a butt load of flash files)
Step 3: Plug your device in the computer (USB debugging should be enabled & I recommend switching the transfer type to PTP/Camera)
Step 4: Launch command prompt (start --> run --> "cmd")
Step 5: type in command prompt "cd directory where you have the adb & fast boot"
for example here is mine "cd C:\Users\MC704\Desktop\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\platform-tools"
Step 6: Verify that it is detecting your device by typing in command prompt "adb devices" (YOU SHOULD SEE YOUR DEVICE HERE ) if not recheck usb debugging & camera ptp... unplug and replug the phone back into your comp
**take a breather we are almost done**
Step 7: Turn your device off and go into fastboot mode (Hold Power Button + Volume Up & Down)
Step 8: Unlock your bootloader by typing in command prompt "fastboot oem unlock" [THIS WILL DELETE ALL YOUR DATA]
It will prompt you to unlock the Device
Step 9: Remember all those files you extracted from the ".TAR"? Copy them to the same folder where your adb and fastboot files are
Step 10: ****************VERY IMPORTANT************* DO THIS IN ORDER
I got these commands from the flash-all.sh file
Type in the command prompt each step one at a time and wait for it to complete
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot -w update image-occam-jwr66v.zip"
***NOTES FOR THIS STEP***
*REMOVE the -w from the last step if you want to keep your data (assuming your bootloader was already unlocked)*
***User chrisjcks noted you can use the flash-all.bat file that was in the zip to make life easier***
Step 11: Enjoy! If you do not plan on putting any custom roms or rooting etc. I recommend rebooting into fastboot mode (Hold Power Button + Volume Up & Down) when the phone is unlocked and type in the command prompt "fastboot oem lock" (you have to have USB debugging & PTP camera enabled)
If I missed out on any steps, please do let me know I will update the OP.
MISC info.
1. People who are using custom recoveries & root & would like to KEEP ROOT... Check this post out it should help you fellars
http://forum.xda-developers.com/showpost.php?p=43917716&postcount=56
2. STUCK ON BOOT LOGO? Check this post out for the fix
http://forum.xda-developers.com/showpost.php?p=43920888&postcount=85
3. NEW ROOT BY CHAINFIRE
http://forum.xda-developers.com/showthread.php?t=2025274

mc704 said:
*I'm not responsible for anything you do with this. I'm just trying to contribute back to the community*
FIRST
1. YOU MUST BE ON THE FACTORY IMAGE (NO MODIFICATIONS that means no custom recovery, kernels, radios, etc)
2. YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
3. ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
4. 4.3 Image from Google (https://developers.google.com/android/nexus/images)
When you have all of this installed... you may proceed
Step 1: Use 7zip or compression program equivalent to extract the stock image file that is .TGZ
Step 2: You should see a stock image file that is .TAR...extract this once again with any compression program (you should see a butt load of flash files)
Step 3: Plug your device in the computer (USB debugging should be enabled & I recommend switching the transfer type to MTP/Camera)
Step 4: Launch command prompt (start --> run --> "cmd")
Step 5: type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\MC704\Desktop\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\platform-tools"
Step 6: Verify that it is detecting your device by typing in command prompt "adb devices" (YOU SHOULD SEE YOUR DEVICE HERE ) if not recheck usb debugging & camera mtp... unplug and replug the phone back into your comp
* take a breather we are almost done
Step 7: Turn your device off and go into fastboot mode (Hold Power Button + Volume Up & Down)
Step 8: Unlock your bootloader by typing in command prompt "fastboot oem unlock" [THIS WILL DELETE ALL YOUR DATA]
It will prompt you to unlock yadda yadda
Step 9: Remember all those files you extracted from the ".TAR"? Copy them to the same folder where your adb and fastboot files are
Step 10: ****************VERY IMPORTANT************* DO THIS IN ORDER
I got these commands from the flash-all.sh file
Type in the command prompt each step one at a time and wait for it to complete
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot -w update image-occam-jwr66v.zip"
Step 11: Enjoy! If you do not plan on putting any custom roms or rooting etc I recommend rebooting into fastboot mode (Hold Power Button + Volume Up & Down) when the phone is locked and type in the command prompt "fastboot oem lock" (you have to have USB debugging & MTP camera enabled)
If I missed out on any steps, please do let me know I will update the OP.
Click to expand...
Click to collapse
or you could just unzip it, and double click the Flash All bat file. :laugh:

My bootloader is already unlocked so I would skip step 8. In this case, would it still wipe all of my data since this is not an OTA or will it just upgrade my OS leaving the apps/data/etc intact? I've done this process many times before with the factory images, but I thought it always wiped the system.

chrisjcks said:
or you could just unzip it, and double click the Flash All bat file. :laugh:
Click to expand...
Click to collapse
I'm old school I'm not too familiar with it . If you want to write a mini guide to consolidate all of this for everyone, I'll update the OP.
mbwelch said:
My bootloader is already unlocked so I would skip step 8. In this case, would it still wipe all of my data since this is not an OTA or will it just upgrade my OS leaving the apps/data/etc intact? I've done this process many times before with the factory images, but I thought it always wiped the system.
Click to expand...
Click to collapse
It wipes the system. or atleast it did for me

If you remove the "-w" from the last step it won't wipe data
Sent from my Nexus 7

mc704 said:
.... no custom recovery, kernels, radios, etc)
Click to expand...
Click to collapse
I had custom kernel and recovery - still Im able to flash factory image from google with no problem, at all..

Is there a easier alternative?
Sent from my HTC One using Tapatalk 4 Beta

chrisjcks said:
or you could just unzip it, and double click the Flash All bat file. :laugh:
Click to expand...
Click to collapse
Impo5sible said:
I had custom kernel and recovery - still Im able to flash factory image from google with no problem, at all..
Click to expand...
Click to collapse
There are always exceptions but I'll note that in the OP for people to see. I'd wrote the guide with the intention of a no failure rate or possible errors.

mc704 - in most cases that would be true - but the Flash-All.bat file is inside the ROM itself.
its as safe as you can get.

I'm on stock 4.2.2, but with custom recovery and kernel.
If I want to get those back to stock, can I just connect my device in fastboot mode, go to command prompt and type:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
?
I have the JDQ39 factory image, and will make sure everything is in the right directory.

LOVE ME PLEASE said:
Is there a easier alternative?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
They are pushing the OTA I believe for a short time
chrisjcks said:
mc704 - in most cases that would be true - but the Flash-All.bat file is inside the ROM itself.
its as safe as you can get.
Click to expand...
Click to collapse
Sure thing I'll update it in the OP:good: thanks for the contribution

To avoid losing data, unzip image-occam-jwr66v.zip with 7 zip.
Now use fastboot to flash bootloader, boot, radio, recovery and system. everything except userdata.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
dan in la said:
I'm on stock 4.2.2, but with custom recovery and kernel.
If I want to get those back to stock, can I just connect my device in fastboot mode, go to command prompt and type:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
?
I have the JDQ39 factory image, and will make sure everything is in the right directory.
Click to expand...
Click to collapse
yup. and system.img if you want to remove root

delete - misread the previous question.
(sure i used to be able to delete my own posts.....)

how can we check which radio version is currently on device

mangomonkey00 said:
how can we check which radio version is currently on device
Click to expand...
Click to collapse
Settings > about phone > baseband version (last 2 numbers)
Sent from my Nexus 4 using xda app-developers app

Look in Settings => About

easy way
For me, All i did was extract the package and edit the .bat file and remove the -w in the code. Then ran it under fastboot. It updated my apps and updated to 4.3, no data wipe.

thanks OP got mine updated to 4.3 without -w

vickpick said:
To avoid losing data, unzip image-occam-jwr66v.zip with 7 zip.
Now use fastboot to flash bootloader, boot, radio, recovery and system. everything except userdata.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
yup. and system.img if you want to remove root
Click to expand...
Click to collapse
Who would like to remove root?
And to summarize:
If someone has stock rom, rooted, with custom kernel, all he has to to do in order not to lose his data and rooting is to flash everything except: system.img and userdata.img?
After that, he will have the update with all data still available?

otariq said:
Settings > about phone > baseband version (last 2 numbers)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
mine says 84 i suppose the latest was 83 have i done something wrong and also in quick system info pro in properties its opengl es cm 1.1 which i think should be 3.0
what should i do
checked it has to be 84 but what about opengl es

cannot flash TWRP recovery...

I wanted to run a 4.4 KitKat GE rom on my HTC One, therefore I decided to unlock my bootloader, install twrp, and flash the rom. So far all i did was unlock my bootloader. Then I proceeded to flash twrp recovery via a command prompt? on my desktop. But I kept getting an error message. I attached a picture of the message I am receiving. I read on the twrp recovery teams site that I need to have S-off before flash TWRP soooo I thought this is what was causing the error. I proceeded to change my S-On to S-Off using rumrunner but then I got an error message there saying I need to be rooted. SOOOOOO now I'm at a standstill and I don't know how to get TWRP recovery onto my device. I'm new to this device and this whole unlocking/rooting thing...Please help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BTW I have USB debugging on and the fast boot option under power settings checked off. I have tried clearing cache also via cmd prompt 'fastboot clear cache'
Sent from my HTC One using xda app-developers app

cloud628 said:
I wanted to run a 4.4 KitKat GE rom on my HTC One, therefore I decided to unlock my bootloader, install twrp, and flash the rom. So far all i did was unlock my bootloader. Then I proceeded to flash twrp recovery via a command prompt? on my desktop. But I kept getting an error message. I attached a picture of the message I am receiving. I read on the twrp recovery teams site that I need to have S-off before flash TWRP soooo I thought this is what was causing the error. I proceeded to change my S-On to S-Off using rumrunner but then I got an error message there saying I need to be rooted. SOOOOOO now I'm at a standstill and I don't know how to get TWRP recovery onto my device. I'm new to this device and this whole unlocking/rooting thing...Please help! View attachment 2429761
Click to expand...
Click to collapse
First to clarify things:
you don't need to be s-off to flash a custom recovery just need unlocked bootloader
you need a custom recovery to root
you need root to s-off
so you need a custom recovery first in order to achieve s-off
The picture you attached tells me fastboot isn't finding the file ''twrp,img'' from your command line ''fastboot flash recovery twrp.img
in most cases because:
your recovery.img file is not in the ''platform-tools'' folder that contain adb.exe and fastboot.exe
the file name of your recovery is not twrp.img
Code:
fastboot flash recovery ''name_of_your_recovery_file.img''
fastboot erase cache
fastboot reboot-bootloader

i'll just leave this here: "cannot load" means the filename is WRONG!!! that's all
cya

okay I'll will give it a go with the suggestions tonight and update this thread with my results
Sent from my HTC One using xda app-developers app

So did I set this up correctly now? And I just open the CMD prompt window up from inside this domain and type "fastboot flash recovery "paste file name here" ? View attachment 2431242

So I just tried again....same error

I downloaded the newest SDK batch files and attempted again. Now I get a different error message.

cloud628 said:
I downloaded the newest SDK batch files and attempted again. Now I get a different error message. View attachment 2431302
Click to expand...
Click to collapse
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!

nkk71 said:
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!
Click to expand...
Click to collapse
Sorry about the screenshots, But where is there a double .img.img extension.....I only have it there once. I literally downloaded the image file from team wins website, saved it into the same folder containing the adb and fastboot files. I didnt change anything in the file name. Then i proceeded to Enter into the CMD window "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7" and I also tried "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" Both do not work.

C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot devices
FA-----10153 fastboot
C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot flash recovery openrecover
y-twrp-2.6.3.3-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.3-m7.img'
C:\Users\dshi----\Desktop\sdk\platform-tools>fastboot flash recovery C:\Users\ds
hi----\Desktop\openrecovery-twrp-2.6.3.3-m7.img
error: cannot open 'C:\Users\dshi----\Desktop\openrecovery-twrp-2.6.3.3-m7.img'
C:\Users\dshin---\Desktop\sdk\platform-tools>fastboot flash recovery openrecover
y-twrp-2.6.3.3-m7
error: cannot open 'openrecovery-twrp-2.6.3.3-m7'

nkk71 said:
Please no more screenshot! Just copy/paste command prompt (only the text)
Anyway, u have a .img.img (double extension)
Again, cannot load means filename is wrong!
Click to expand...
Click to collapse
OHHHHH!!!! It worked!. Now I get it! Jeeeze that was absolutely frustrating but now I know. Thank You SOOOOO Much!

cloud628 said:
Sorry about the screenshots, But where is there a double .img.img extension.....I only have it there once. I literally downloaded the image file from team wins website, saved it into the same folder containing the adb and fastboot files. I didnt change anything in the file name. Then i proceeded to Enter into the CMD window "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7" and I also tried "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" Both do not work.
Click to expand...
Click to collapse
It's not about about the screenshots, just reading them on a phone, is not easy! Anyway:
1- have u placed the recovery.img I'm ur adb folder?
2- did u do a"dir" to see the full filenames?
Sent from my HTC One using Tapatalk

thanks a ton!
nkk71 said:
It's not about about the screenshots, just reading them on a phone, is not easy! Anyway:
1- have u placed the recovery.img I'm ur adb folder?
2- did u do a"dir" to see the full filenames?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
So it's December 2016 and I was running into a very similar error. Doing the dir command showed I had a double ".img" on my file as well. Fixed that, and I'm back in business. Thanks so much!

Hi Guys, just an FYI, i'm leaving here the link to download the current versions of TWRP IMG
SITE: https://twrp.me/
Regards!

asmallmammal said:
So it's December 2016 and I was running into a very similar error. Doing the dir command showed I had a double ".img" on my file as well. Fixed that, and I'm back in business. Thanks so much!
Click to expand...
Click to collapse
please tell how you fix that i have the same problem

Just rename the file without typing in ".img" at it should be ok.
So in explorer, rename the file simply "twrp" and hit enter. There will be a ".img" extension on the file, but you won't see it. To make sure it's been corrected, run the dir command and it should show "twrp.img" even though the file doesn't have the ".img" when you look at it in explorer.
Does that make sense?

How to show/hide file extension
For Windows Vista, Windows 7, and Windows Server 2008
Start Windows Explorer, you can do this by opening up any folder.
Click Organize.
Click Folder and search options.
Click the View tab.
Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box.
Note To hide file name extensions, check this line.
Click OK
For Windows 2000, Windows XP, and Windows Server 2003
Start Windows Explorer, you can do this by opening up any folder.
Click Tools, and then click Folder Options.
Scroll down and then click Folder and search options.
Click the View tab.
Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box.
https://support.microsoft.com/en-us/kb/865219

what is it for htc at play?

[Q] need help to get my phone working again

hey guys.
My M7 is stuck in the bootloop. I tried to install a new rom like 2 years ago and it didnt worked out, but i already had a new phone, so i didnt care too much. now id like to reactivate my old m7 but dont know how.
here is a link to a picture of my fastboot
imgur.com/tzQe7Xi
Im running Windows 10 on my computer
thanks in advance

zuppiger said:
hey guys.
My M7 is stuck in the bootloop. I tried to install a new rom like 2 years ago and it didnt worked out, but i already had a new phone, so i didnt care too much. now id like to reactivate my old m7 but dont know how.
here is a link to a picture of my fastboot
imgur.com/tzQe7Xi
Im running Windows 10 on my computer
thanks in advance
Click to expand...
Click to collapse
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Boot into recovery and connect your phone to the PC.
Download any ROM from the forum, transfer it to the phone and flash it. Don`t since we don`t know anything about your previous ROM wipe cache, dalvik, data and system before flashing your chosen ROM.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.

proone said:
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Boot into recovery and connect your phone to the PC.
Download any ROM from the forum, transfer it to the phone and flash it. Don`t since we don`t know anything about your previous ROM wipe cache, dalvik, data and system before flashing your chosen ROM.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
Click to expand...
Click to collapse
No need to extract anything. S-on doesn't matter for kernel flashing on this phone. So, flash ROM.zip and enjoy

proone said:
Boot into fastboot mode and install the latest version of TWRP, which is 2.8.7.0. You can download it from the TWRP official website.
Code:
fastboot flash recovery recovery-file-name.img
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-file-name.img
fastboot erase cache
fastboot reboot-bootloader
Always erase the cache and reboot the bootloader after flashing a recovery to avoid problems booting the recovery.
Download any ROM from the forum
Click to expand...
Click to collapse
"any ROM" from the forum won't work on his phone. For example, his actual firmware is way to old to run roms based on Sense + Lollipop. With this firmware version (2.24.401.8), he is limited to JellyBean or Kitkat Roms.
Since you`re S-On, extract the boot.img file from the ROM zip and flash it manually in fastboot mode
Code:
fastboot flash boot boot.img
Reboot phone and enjoy.
Click to expand...
Click to collapse
Won't hurt but not needed on the M7 (unlike some other HTC phones). The kernel partition isn't secured and is flashed with the rom from twrp.
@zuppiger
If you want the phone back to stock and be able to intall ota updates (or if you want to install a custom lollipop + sense rom), flash this rom using twrp recovery. Select "yes" for stock recovery and stock radio, select "no" to root. then reboot the phone to the OS, install all the ota updates (a lot) until your version is 7.19.401.30. Then you can use the phone like this or you'll be ready to flash a lollipop custom rom. Otherwise you can go like suggested above but with older (JB or KitKat) Sense rom or any CM/AOSP roms.

Thanks guys.
but i think i might need some more help.
i downloaded the sdk manager to install TWRP, but when i try to write "adb reboot bootloader" it says "is not recognized as an internal or external command, operable program or batch file" (not entirly sure if this is the correct translation, in german it says the command is either wrong or could not be found)
i think it could be because of some driver issues.
any advice??

zuppiger said:
Thanks guys.
but i think i might need some more help.
i downloaded the sdk manager to install TWRP, but when i try to write "adb reboot bootloader" it says "is not recognized as an internal or external command, operable program or batch file" (not entirly sure if this is the correct translation, in german it says the command is either wrong or could not be found)
i think it could be because of some driver issues.
any advice??
Click to expand...
Click to collapse
Download the android sdk tools:
https://developer.android.com/sdk/index.html#Other
Make sure you have the latest htc drivers installed:
http://www.mediafire.com/download/2lyl151pt5pah2v
Make sure you don't have HTC Sync installed on your computer, if yes, uninstall it since it will interfere with fastboot/adb commands
To use adb or fastboot commands, open a command window from the same folder where adb.exe and fastboot.exe are located on your computer (C::\Programs\Android SDK Tools\platform-tools). To start a command window from this folder, hold your left "shift" key and right click a blank space in that folder, then in the contextual menu, select "open a command window here".
Don't forget that adb commands can only works when the phone is booted in the OS with "USB debugging" turned on from the developer option menu or from a custom recovery. Fastboot commands only works from the bootloader (in the fastboot menu).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

alray said:
Download the android sdk tools:
https://developer.android.com/sdk/index.html#Other
Make sure you have the latest htc drivers installed:
http://www.mediafire.com/download/2lyl151pt5pah2v
Make sure you don't have HTC Sync installed on your computer, if yes, uninstall it since it will interfere with fastboot/adb commands
To use adb or fastboot commands, open a command window from the same folder where adb.exe and fastboot.exe are located on your computer (C::\Programs\Android SDK Tools\platform-tools). To start a command window from this folder, hold your left "shift" key and right click a blank space in that folder, then in the contextual menu, select "open a command window here".
Don't forget that adb commands can only when the phone is booted in the OS with "USB debugging" turned on from the developer option menu or from a custom recovery. Fastboot commands only works from the bootloader (in the fastboot menu).
Click to expand...
Click to collapse
Thanks. I installed everything like explained.
It worked better this time, but now I get "waiting for device".
On the phone itself it says "FASTBOOT USB"

zuppiger said:
but now I get "waiting for device".
Click to expand...
Click to collapse
When using what command?

alray said:
When using what command?
Click to expand...
Click to collapse
"fastboot flash recovery c:\twrp.img"

zuppiger said:
"fastboot flash recovery c:\twrp.img"
Click to expand...
Click to collapse
what is the output of "fastboot devices" ?

alray said:
what is the output of "fastboot devices" ?
Click to expand...
Click to collapse
Nothing.
I made the command again in the platform-tools folder

Anyone some more help? :good:

zuppiger said:
Anyone some more help? :good:
Click to expand...
Click to collapse
Well without any connectivity to the phone there is nothing we can do unfortunately. Might worth to try on another computer. Otherwise if you are 100% sure that the problem isn't the usb cable, the drivers or the computer then the phone usb port might be broken. This can be replaced (probably the "easiest" part to replace on that phone), you'll need to open the cover and replace that small usb/front mic board.
But the fact that your phone says FASTBOOT USB when in bootloader makes me believe its more a driver/computer problem since it would only says FASTBOOT if there were no connection detected...

thanks a lot for your help. I don't think I will get it working again anytime soon.
But i will look for a way

Trying to flash twrp recovery...getting error "target reported max download..."

Trying to flash twrp recovery...getting error "target reported max download..."
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!

DoritoKing said:
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!
Click to expand...
Click to collapse
1) how are you trying to install TWRP?
2) You are using the most recent version from our official TWRP maintainer?
January 12, 2017
twrp-3.0.3-0-Mod_01-quark.img
https://www.androidfilehost.com/?fid=745425885120699982
3) And you are showing known file extensions in Windows? Do you know what that means?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have a jpg or pdf, and you see a file name -- do you also ALWAYS, ALWAYS see the extension like jpg or pdf? Default in Windows -- for idiotic reasons -- is to "hide known file extensions".
Make sure that box is UNchecked in your Windows settings. Because otherwise you are re-naming TWRP as TWRP.img(.img). You do NOT have to type the .img part, it's ALREADY an .img file.
That may or may not be your issue, but it messed up a lot of people in the past. ADB couldn't find TWRP.img because they had unknowingly called it TWRP.IMG.img -- because they couldn't see the file extension and thought they needed to add it to the file name.

1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!

Just tried with the changes....still getting same error messages.

DoritoKing said:
1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!
Click to expand...
Click to collapse
When you unchecked the extension box, what is now the visible name of your TWRP file? Does it say TWRP.img.img or just TWRP.img? Besides unchecking the extension box, you also need to make sure you are typing the actual name of the file. IF you had typed "TWRP.img"(.img) before, you now need to re-name it just "TWRP".img.
If you confirm that's not the issue, then we'll get @bhb27 involved over in the Quark TWRP thread.

I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great

DoritoKing said:
I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great
Click to expand...
Click to collapse
OK, just as a test, do this. Forget the name TWRP. That's just a convenience. Call it something else. Rename it box or chair. I'm not joking. Then, in your PC, what file name do you see? IF you renamed it "box", you should see box.img. You do NOT type .img. It's just the extension that should already be there!
then flash: fastboot flash recovery box.img
I'm suggesting this because somehow, somewhere it seems your file name is messed up?
Also you have done all this too? Permissions and stuff?
Enable USB debugging on your device:
Open Settings on your device.
Go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and you’ll see Developer options there, open it.
Tick the USB Debugging checkbox.
Connect your device to the PC. And type the following into the command window we opened to boot your device into bootloader/fastboot mode:
adb reboot bootloader
└ If you get a permission dialogue on your device to “Allow USB debugging”, tap OK.
Click to expand...
Click to collapse
Maybe revoke those permissions and re-enable them?

Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...

DoritoKing said:
Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...
Click to expand...
Click to collapse
I was just suggesting you revoke the USB permissions and re-enable them in Developer Settings, just to make sure. That's the only thing I'm aware of you need to do on the phone side... If anyone knows something different, feel free to correct me!
@bhb27 is our TWRP maintainer for our official TWRP. So, I'm mentioning him here so he'll see this issue. Maybe he'll have some ideas?
Also, you you can post this issue over in the Quark TWRP thread. You can put a link to this thread in your post, so people can see what all we've tried.
[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://forum.xda-developers.com/mo...recovery-twrp-2-8-7-0-touch-recovery-t3180308

I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img

bhb27 said:
I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img
Click to expand...
Click to collapse
Here are the screenshots...if this isn't what you were looking for, just let me know.

DoritoKing said:
Here are the screenshots...if this isn't what you were looking for, just let me know.
Click to expand...
Click to collapse
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:

bhb27 said:
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:
Click to expand...
Click to collapse
Didn't recognize that command...here is the screenshot

You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.

DoritoKing said:
Didn't recognize that command...here is the screenshot
Click to expand...
Click to collapse
did you download the file I share?

TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.

TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
Right. His screenshot is showing other extensions, like .exe, .txt, .dll -- so his TWRP extension should be .img. It's missing.
What I cautioned him about was double naming the extension -- TWRP.img.img, which can accidentally be done if you have your Windows settings to hide known file extensions. Since his file extensions are no longer hidden, his TWRP file should say TWRP.img.
But naming it TWRP is just a convenience instead of using the regular file name like "twrp-3.0.3-0-Mod_01-quark.img". It's easier to type TWRP.img in the Windows command box than that long official file name. You could easily also re-name it "chair.img" or "box.img" as long as you were re-naming the correct file. I even suggested he do that because he seemed hung up over the TWRP name.
At this point, he probably needs to also re-download the TWRP file and re-name it. Now that he can see file extensions, it should automatically have the .img extension.

Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?

DoritoKing said:
Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?
Click to expand...
Click to collapse
I'm going to hazard a guess here that you also flashed SuperSu in TWRP and you are running the new Marshmallow update. (Yeah, confirmed, I just checked your first post. You took Marshmallow update.) In which case, it sounds like you flashed the wrong version of SuperSu. You have to flash an older version for initial root or your phone will stick at the bootloader warning screen. This has been discussed in all the Marshmallow threads.
What version SuperSu are you using? If on stock Marshmallow or stock-based Marshmallow ROM, the one required is BETA-SuperSU-v2.62-3-20151211162651). You can boot into TWRP, plug your phone into a PC and drag it over like a flash drive. It will show up in the root folder. Flash it, wipe all caches, reboot.
I've attached it to this post.
AFTER initial root, and after you successfully boot, then you can update to newest version of SuperSu. You just need it for initial root and to successfully boot the first time.
PREDICTION: Your next question will be how to get rid of the unlocked bootloader screen. Because you will see it every time you reboot your phone. When you do, here's your answer. But first, you need to flash the correct SuperSu to get past the bootloader screen.

DoritoKing said:
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.
Click to expand...
Click to collapse
Congratulations on installing TWRP.

How To Guide [GUIDE] Beginner's guide on how to root Redmi Note 10 Pro (sweet) without TWRP

I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader (if you don't know how to unlock it, search "How to unlock bootloader Xiaomi"
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Select patch a file, then find and select boot.img.
-Tap "let's go".
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Q: Phone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).

usernamenotrequired said:
I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
View attachment 5474787
-Select patch a file, then find and select boot.img.
-Tap "let's go".
View attachment 5474793
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
View attachment 5474801
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Qhone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).
Click to expand...
Click to collapse
Very good but easier with unlocked bootloader and flashing twrp via adb flash recovery "name of twrp file". Afterwards you can flash directly magisk (I prefer 23 canary debug apk) to root.

if i may add to the troubleshooting: if it says magisk.img isn't found, just type this (after confirming connection with fastboot devices command:
fastboot flash boot
then drag and drop the patched magisk file onto the cmd window/line where you typed the command above. worked for me.

Tanks you

For beginners, "assuming bootloader is unlocked if not click here" should be mentioned.

hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?

Bastio001 said:
hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?
Click to expand...
Click to collapse
I've searched around, and it seems to be caused by a VPN. If you use a VPN, turn it off and try again. If not, it could be that the Xiaomi unlocking API is down temporarily.

When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
I thank You very much.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
then what is the solution bro...still i cant install some custom roms showing error 1...please help me.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
bro am facing this erros 1. will u pls help me.

THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.

While unlocking the bootloader I'm having the issue linked below, thanks in advance for all and any responses. https://forum.xda-developers.com/t/mi-unlock-country-code-broken.4572339/

r4nchy said:
THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.
Click to expand...
Click to collapse
AGREE 100%!!!