Getting Mismatched image error in fastboot when trying to flash stable/developer ROM. - Xiaomi Redmi Note 4 Questions & Answers

Hello..
Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error..
tried flashing from mi flash tool, flashed in 1sec issue..
Please help , how am i suppose to flash stock rom via fastboot or miflash tool..
My bootloader is already unlocked..
is their any proper guide or youtube video or something and proper download link. i am sure i downloaded the right file but don't know why getting these errors..
My Phone is Redmi Note 4 (mido) , currently on STable Global Version
Thanks..

Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck

For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing

Hello..
i have redmi note 4 and i am installing stock rom but it says that rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
Now waht i do
can you please explain me.
pls
Thanks

Thanx
ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
It worked. Thanks !!

ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
Worked for me. Thank you!! Truly thought I bricked my phone.

Beast gamer said:
Hello..
i have redmi note 4 and i am installing stock rom but it says that rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
Now waht i do
can you please explain me.
pls
Thanks
Click to expand...
Click to collapse
Had this problem, outcommented the variantchecks (in the flash_all_except_data.bat and other 3 bat files). Now Miflash prompts not this but subsequent [] problem :
$for /F "tokens=2 delims=: "%in (fastboot -s [MY 7 char-DEVICENO.] getvar anti 2>&1
Probably I am apart from your problem, as Fastboot commands give no responds: for e.g.
fastboot getvar boot-mode, answer is:
< waiting for any device >
Only "success" I had:
fastboot reboot
but still in bootloop
Any help appreciated, I am a beginner...

ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
I didn't understand no -3 point????

i am flashing redmi note 5 and i am also getting mismatch error. i tried the following method but now it is displaying 'flash xbl error' and partition table doesn't exist.
any help will be highly appreciated

Shadow505 said:
For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing
Click to expand...
Click to collapse
I created an account on xda just to thank you.
this really saved my phone, I have been spending well over 12 hours trying to get this fixed
It worked as soon as i switched over to my intel powered laptop
THANK YOU

Shadow505 said:
For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing
Click to expand...
Click to collapse
I have my ryzen and this is the solution after few hour struggling with this error. Thank a bunch!

Yep, I've just been struggling to install stock 'n' lock via miflash, and it turned out the problem was my Ryzen CPU. Have dug out an old intel laptop, which doesn't connect to wifi, the battery is dead, and half the screen isn't viewable, but it does manage to install firmware via miflash. Thanks so much for this thread, which probably saved me several hours of fiddling.

Related

[RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.13 ||

{
"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"
}
DISCLAIMER
I will not be held responsible if this damages, bricks, ruins, destroys, or sets your phone on fire. Proceed at your own risk and make sure to follow instructions. For the love of God, do not try to use this on a phone other than the HTC EVO 4G LTE for Sprint or you WILL brick your phone.​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Q: What is VipeRUU?
A: An alternative way to flash an RUU, basically it flashes it through a special mode in the bootloader. This will put you back to complete unrooted stock and update your bootloader to the latest! Instead of using HTC's .exe to do it, I created this way for numerous reasons.
Click to expand...
Click to collapse
Q: What reasons?
A: Well, there are a few. The first reason (and most important) is to protect the people that get these files for us. While I do not know these people, I would like to keep seeing these files around.
The second reason is that I believe you won't see RUU's around much anymore. HTC has made it clear that they are OK with the RUU's out there, but they have not showed any intention of making more publicly available. This means that any future files that become available, HTC may be tracking them. I have no idea, but just my personal belief, and I'd like to be safe about it - hence using decrypted and unsigned rom.zips and VipeRUU to flash it.
Lastly, because I believe you will see a reduction in RUU's (but possibly not official ROM files) I wanted to make a way that any device can utilize VipeRUU to still flash the rom.zip files just like you would run an RUU.
Click to expand...
Click to collapse
Q: Whatever, what are the requirements to use this?
A: You must be S-OFF to use this tool, unlike when you use an RUU. The reason why is because the rom.zip files have been decrypted via RUUVEAL unpacked, and repacked, which means that it no longer has HTC's signature, so an S-ON bootloader won't accept it. Again, this is just for any sources security.
There are 2 tools to gain S-OFF and they're easy to use, please check them out - Facepalm or DirtyRacun. Note: Facepalm doesn't appear to work on 3.16. You can try BabyRacun and then Facepalm and it might work, but I didn't try that.
You also need a Windows PC. This was tested on both Win7 and Win8 x64. I was going to write a Linux version, but I don't know if there is a big need for it or not. If there is, please let me know.
Click to expand...
Click to collapse
Q: OK cool, how do I use this?
A: It's very simple! Download the file below and unzip it. Double-click on VipeRUU.bat. If you get an error complaining about security, right-click, properties, unblock. Then run it again. You need to be booted into Android (aka, your phone turns on and boots to Sense/CM/whatever) to use this.
Click to expand...
Click to collapse
Q: But what if I can't get into Android?? Surely there is something I can do!?
A: Yes, I designed a "backdoor" to allow you into VipeRUU. However, BE CAREFUL! This skips important checks that VipeRUU does when it start (most importantly, if your phone really is an EVO 4G LTE!) but it will allow you to do this procedure from the bootloader. All you have to do is create a text file in the "files" folder called "bypass.txt" and then start the program. You'll be alerted with a few warnings when doing this.
Click to expand...
Click to collapse
Q: Why don't you just release the RUU since I'm S-ON?!
A: I do not have the RUU, sorry. Just do an S-OFF procedure I talked about above, it's not that hard
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Sharing
The use of this tool is open for anyone to use. I just ask that you leave everything as it is and change only the needed lines in the code for other devices. I will have information below on how to adapt this for other devices. If you have any fixes or suggestions, please send them my way.​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Download
VipeRUU_jewel_3.16.651.3​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Credits
Indirect for helping with the code
IRC testers - jocarog (I forget the others, please let me know so I can credit you!)​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Here is the code:
Code:
@ECHO off
color 0c
mode con:cols=80 lines=35
::VERSION
SET VERSION=v1.0.0
::PROGRAMS
SET ADB=files\adb.exe
SET FASTBOOT=files\fastboot.exe
SET MD5SUM=files\md5sum.exe
::INFO
SET DEVICE=HTC EVO 4G LTE (jewel)
SET RUUVERSION=3.16.651.3
::FILES
SET ROMZIP=files\rom.zip
SET ROMZIPMD5=9f95e8c2c8c9d3ae6834ea081434ac62
SET ROMZIPMD5CHECK=files\md5.txt
::eek:THERS
SET BYPASS=files\bypass.txt
SET LOG=files\log.txt
SET UNLOCKCODE=files\Unlock_code.bin
ECHO.
ECHO Initializing...
del %LOG% 2>NUL
del %ROMZIPMD5CHECK% 2>NUL
%adb% kill-server > NUL
%adb% start-server > NUL
ECHO.
ECHO Getting device information...
ping 127.0.0.1 -n 3 > NUL
IF EXIST %BYPASS% (
GOTO forceBypass
) ELSE (
GOTO initVipeRUU
)
:forceBypass
ECHO.
ECHO *** BYPASSING NORMAL CHECKS ***
ECHO.
ECHO I hope you know what you're doing... please confirm.
ECHO.
pause
SET BYPASS=1
SET STATUS=UNKNOWN
GOTO MENU
:initVipeRUU
%adb% shell getprop ro.product.device > %LOG%
find "jewel" %log% > NUL
IF %ERRORLEVEL%==0 SET ISADB="YES" && SET STATUS=Connected (adb) && GOTO verifyDevice
IF %ERRORLEVEL%==1 GOTO noDevice
:verifyDevice
SET /p CHECKDEVICE=<%LOG%
IF %CHECKDEVICE% == jewel GOTO MENU
IF NOT %CHECKDEVICE% == jewel GOTO wrongDevice
:noDevice
CLS
ECHO.
ECHO Your device wasn't detected. Please make sure the device is plugged in and
ECHO booted into Android.
ECHO.
ECHO Please also make sure that you have installed the drivers located in the
ECHO "files\drivers" folder and try again.
ECHO.
pause
EXIT
:wrongDevice
CLS
ECHO.
ECHO Device isn't an %DEVICE%!
ECHO.
ECHO This would have bricked your phone, exiting...
ECHO.
pause
exit
:MENU
CLS
ECHO ===============================================================================
IF %BYPASS% == 1 ECHO. && ECHO *** BE ADVISED, RUNING IN BYPASSED MODE! ***
ECHO.
ECHO VipeRUU %VERSION%
ECHO by -viperboy-
ECHO and Indirect
ECHO.
ECHO Device: %DEVICE% RUU Version: %RUUVERSION%
ECHO.
ECHO Status: %STATUS%
ECHO.
ECHO ===============================================================================
ECHO.
ECHO 1) Start RUU Process
ECHO.
ECHO 2) Unlock bootloader
ECHO.
ECHO 3) Flash Recovery (do after step 2)
ECHO.
ECHO 4) Toggle Security Flag (S-OFF to S-ON)
ECHO.
ECHO 5) Exit
ECHO.
SET /P CHOICE=Please choose an option:
IF %CHOICE% == 1 GOTO flashRUU
IF %CHOICE% == 2 GOTO unlockBootloader
IF %CHOICE% == 3 GOTO doRecovery
IF %CHOICE% == 4 GOTO doSecurityFlag
IF %CHOICE% == 5 EXIT
IF NOT DEFINED %CHOICE% GOTO ERROR
:flashRUU
CLS
ECHO.
ECHO Rebooting to bootloader...
%adb% reboot bootloader 2>NUL
ECHO.
ECHO Starting RUU mode...
%FASTBOOT% oem rebootRUU 2>NUL
ECHO.
ECHO Checking MD5 before flashing...
ECHO.
%MD5SUM% %ROMZIP% > %ROMZIPMD5CHECK%
find "%ROMZIPMD5%" %ROMZIPMD5CHECK% > NUL
IF %ERRORLEVEL%==0 ECHO MD5 matches! Proceeding...
IF %ERRORLEVEL%==1 GOTO badMD5
ECHO.
ECHO Performing pre-update...
%FASTBOOT% flash zip %ROMZIP% 2>NUL
ECHO.
ECHO Flashing...
::Keep fastboot from crashing
ping 127.0.0.1 -n 6 > NUL
%FASTBOOT% flash zip %ROMZIP% 2>NUL
ECHO.
ECHO ROM.zip flash sucessful!
ECHO.
SET /P STAYINBOOTLOADER=Stay in bootloader? (y/n):
IF %STAYINBOOTLOADER% == y %FASTBOOT% reboot-bootloader 2>NUL && ECHO. && ECHO Rebooting to bootloader...
IF %STAYINBOOTLOADER% == Y %FASTBOOT% reboot-bootloader 2>NUL && ECHO. && ECHO Rebooting to bootloader...
IF %STAYINBOOTLOADER% == n %FASTBOOT% reboot 2>NUL && ECHO. && ECHO Rebooting to Android...
IF %STAYINBOOTLOADER% == N %FASTBOOT% reboot 2>NUL && ECHO. && ECHO Rebooting to Android...
ECHO.
pause
GOTO MENU
:unlockBootloader
IF EXIST %UNLOCKCODE% (
GOTO hasUnlockCode
) ELSE (
GOTO getUnlockCode
)
:hasUnlockCode
CLS
ECHO.
%FASTBOOT% flash unlocktoken %UNLOCKCODE% 2>NUL
ECHO Please continue the steps from your phone.
ECHO.
pause
GOTO MENU
:getUnlockCode
CLS
ECHO.
ECHO Please copy the code below...
ECHO.
%FASTBOOT% oem get_identifier_token
ECHO.
ECHO See http://bit.ly/116rKCs if you are unsure what to copy.
ECHO.
ECHO You can continue the process at http://www.htcdev.com/bootloader/
ECHO When you get your Unlock_code.bin, please place it in the
ECHO "files" folder and run this step again to unlock your
ECHO bootloader.
ECHO.
pause
GOTO MENU
:doRecovery
CLS
ECHO.
ECHO Your device needs to be unlocked.
ECHO.
SET /P RECCHOICE=Are you sure you want to do this? (y/n):
IF %RECCHOICE% == y GOTO flashRecovery
IF %RECCHOICE% == Y GOTO flashRecovery
IF %RECCHOICE% == n ECHO. && ECHO Cancelled! && pause && GOTO MENU
IF %RECCHOICE% == N ECHO. && ECHO Cancelled! && pause && GOTO MENU
IF NOT DEFINED %RECCHOICE% ECHO. && ECHO Cancelled! && ECHO. && pause && GOTO MENU
:flashRecovery
%fastboot% flash recovery files\recovery.img 2>NUL
ECHO.
ECHO Recovery flashed!
ECHO.
pause
GOTO Menu
:doSecurityFlag
CLS
ECHO.
ECHO This needs to be done IMMEDIATELY AFTER you flash the RUU! IF you have a
ECHO custom HBOOT, it WILL brick your device!!! You must be completely stock!
ECHO.
ECHO You will have to completely go through an S-OFF process if you
ECHO ever wish to have S-OFF again. This is NOT RECOMMENDED, unless you
ECHO are returning your phone for warranty work.
ECHO.
SET /P SECUCHOICE=Are you sure you want to do this? (y/n):
IF %SECUCHOICE% == y GOTO writeSecureFlag
IF %SECUCHOICE% == Y GOTO writeSecureFlag
IF %SECUCHOICE% == n ECHO. && ECHO Cancelled! && pause && GOTO MENU
IF %SECUCHOICE% == N ECHO. && ECHO Cancelled! && pause && GOTO MENU
IF NOT DEFINED %SECUCHOICE% ECHO. && ECHO Cancelled! && pause && GOTO MENU
:writeSecureFlag
%fastboot% oem writesecureflag 3
pause
GOTO menu
:badMD5
ECHO.
ECHO Bad md5 when checking rom.zip! Please redownload VipeRUU, as flashing
ECHO a file with a bad md5sum can brick your phone!
ECHO.
pause
exit
:ERROR
ECHO.
ECHO Invalid option, please try again!
ECHO.
PAUSE
GOTO MENU
I just realized there are a few more places in the code that you need to change things to make it work for another device. I will clean that up at a later point, but if you follow the below information, you can make it work on any Android device. Make sure you're rom.zip is named "rom.zip"
Change these at it applies to your device/files:
Code:
SET DEVICE=HTC EVO 4G LTE (jewel)
SET RUUVERSION=3.16.651.3
SET ROMZIPMD5=9f95e8c2c8c9d3ae6834ea081434ac62
Change "jewel" to whatever your device name is when running getprop ro.product.device
Code:
:initVipeRUU
%adb% shell getprop ro.product.device > %LOG%
[COLOR="Red"]find "jewel" %log% > NUL[/COLOR]
Change "jewel" here as well to your device name found via getprop ro.product.device
Code:
:verifyDevice
SET /p CHECKDEVICE=<%LOG%
[COLOR="red"]IF %CHECKDEVICE% == jewel GOTO MENU
IF NOT %CHECKDEVICE% == jewel GOTO wrongDevice[/COLOR]
The above 2 I will make easier to edit later, but for now, this will work.
Feature list:
Code:
MD5 check
Device check
Ability to toggle s-on
Flash any rom.zip to upgrade / downgrade your device.
Flash recovery after RUU to get right back into flashing custom roms
Changelog:
Code:
1.0.0 - Initial release
If I can think of anything else to add to it, I will
Awesome Job Viper!!
This Looks Sick!
Re: [RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.12 ||
Nice, thanks for sharing viper!
What is the use of RUU? Is this a stock unrooted ROM? Is this to be used to unroot? Or is this for developers only? Can I flash this as a stock rom?
Re: [RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.12 ||
JManekia said:
What is the use of RUU? Is this a stock unrooted ROM? Is this to be used to unroot? Or is this for developers only? Can I flash this as a stock rom?
Click to expand...
Click to collapse
An RUU is a ROM Update Utility. It's how HTC updates devices officially. It can flash everything in this mode, the ROM, radios, firmware, etc. This will take you back to complete stock 3.16, bootloader and all.
For the end user, it's just a way to recover the phone if something major went wrong.
Sent from my EVO using Tapatalk 2
Thanks fellaz :good:
Re: [RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.12 ||
But it wont unroot the phone and lock the boatloader correct?
Sent from my EVO using xda app-developers app
Re: [RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.12 ||
JManekia said:
But it wont unroot the phone and lock the boatloader correct?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
"Back to complete stock" would mean it does all of that, yes. I would encourage you to Google RUU and read up on it a bit.
Sent from my EVO using Tapatalk 2
Re: [RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.12 ||
Thanks viperboy. Check the date on OP, though. It says 3/19/12, I thought , wow, this is old, lol.
Then realized this device wasn't available yet as of 3/19/12
Sent from my EVO using xda premium
Re: [RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.12 ||
Why would HTC stop releasing RUUs? I thought they built them as a way to restore borked phones. Kind of like Samsung and Odin. I could be off, honestly, I've never used an RUU, this was just my impression from reading over the years.
Sent from my EVO using xda premium
Re: [RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.12 ||
If you used this, it would be like going to sprint and picking up a new phone... This is the ultimate "i screwed my phone up fix".. Pretty awesome!
Sent from my EVO using xda premium
Re: [RUU]VipeRUU Jewel 3.16.651.3 || Updated 3.19.12 ||
^^^^^^^^^^^
Doesn't fix QHUSBDLMODE bricks though, right ?
Sent from my EVO using xda premium
scottspa74 said:
Thanks viperboy. Check the date on OP, though. It says 3/19/12, I thought , wow, this is old, lol.
Then realized this device wasn't available yet as of 3/19/12
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Christ lol sorry, fixed.
scottspa74 said:
Why would HTC stop releasing RUUs? I thought they built them as a way to restore borked phones. Kind of like Samsung and Odin. I could be off, honestly, I've never used an RUU, this was just my impression from reading over the years.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
They never released them, they were always being leaked
tonyevo52 said:
If you used this, it would be like going to sprint and picking up a new phone... This is the ultimate "i screwed my phone up fix".. Pretty awesome!
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yup!
scottspa74 said:
^^^^^^^^^^^
Doesn't fix QHUSBDLMODE bricks though, right ?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Nope!
So, apparently I used CWM to flash an older rom not compatible with TWRP 2.4.1, and I broke my miscellaneous partition. Will flashing this restore my partition, just as flashing an RUU would?
______________________________
HTC Evo 4G LTE
I Dont think so (don't quote me). But you asked in the right place. Viperboy had the fix for that posted in viper ROM thread a while back. I'm sure he can help you.
Sent from my EVO using xda premium
Freakin awesome! Thank you.
via eVo.
aarsyl said:
So, apparently I used CWM to flash an older rom not compatible with TWRP 2.4.1, and I broke my miscellaneous partition. Will flashing this restore my partition, just as flashing an RUU would?
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
Yes it will fix that. This is literally the same thing as running an RUU, just with a few extra features.
Sent from my LG-LS970 using Tapatalk 2
-viperboy- said:
They never released them, they were always being leaked
Nope!
Click to expand...
Click to collapse
Wait, so does HTC not provide a recovery tool?
Sent from my EVO using xda premium

Stock boot.img problems from the factory

I have an Alcatel Pixi3 4.5 4G model 5017O and I'm working on development for this phone.
I did a hexdump on the stock boot.img and was quite surprised to see this:
00004b80 |.......... -- Sy|
00004b90 |stem halted.Atte|
00004ba0 |mpting division |
00004bb0 |by 0!...Uncompre|
00004bc0 |ssing Linux.....|
00004bd0 |decompressor ret|
00004be0 |urned an error..|
00004bf0 | done, booting t|
00004c00 |he kernel...inva|
00004c10 |lid distance too|
00004c20 | far back...inva|
00004c30 |lid distance cod|
00004c40 |e...invalid lite|
00004c50 |ral/length code.|
00004c60 |incorrect header|
00004c70 | check..unknown |
00004c80 |compression meth|
00004c90 |od..invalid wind|
00004ca0 |ow size.invalid |
00004cb0 |block type..inva|
00004cc0 |lid stored block|
00004cd0 | lengths....too |
00004ce0 |many length or d|
00004cf0 |istance symbols.|
00004d00 |invalid code len|
00004d10 |gths set....inva|
00004d20 |lid bit length r|
00004d30 |epeat...invalid |
00004d40 |literal/lengths |
00004d50 |set.invalid dist|
00004d60 |ances set...inco|
00004d70 |rrect data check|
00004d80 |....Out of memor|
00004d90 |y while allocati|
00004da0 |ng output buffer|
00004db0 |....Out of memor|
00004dc0 |y while allocati|
00004dd0 |ng input buffer.|
00004de0 |Out of memory wh|
00004df0 |ile allocating z|
00004e00 |_stream.Out of m|
00004e10 |emory while allo|
00004e20 |cating workspace|
00004e30 |....Not a gzip f|
00004e40 |ile.header error|
00004e50 |....read error..|
00004e60 |uncompression er|
00004e70 |ror.............|
Does anyone else have an Alcatel, or any MediaTek based phone with a stock boot.img, that they can check to see if all of the phones they release are like this?
You can run a hexdump and check for yourself in Linux and let me know, or post your phone specs (MediaTek based only) here as well as a link to download your stock unmodified boot.img.
To do the hexdump cd into the dir with your stock boot.img and run the following command (in Linux):
hexdump -C "boot image name" | tee boot_dump.txt
where "boot image name" is the name of your boot image (without the quotes) that you made during a readback in SP Flash tools when you did your backup of you stock rom. The hexdump will be saved to a file named boot_dump.txt.
(You may have to run "sudo apt-get install hexdump" (without the quotes) in Ubuntu if you don't already have hexdump installed.)
If this is in the wrong section, please let me know.

Unspecified error

Hi All
Successfully got my RN3 stuck on MI logo, so no boot. Having tried many suggestions, the nearest I got to fixing it was with MIFlash. I believe I've connected the right file paths and on 'flash' I got this response...any thoughts please?
I was using: kenzo_global_images_V8.0.1.0.LHOMIDG_20160805.0000.29_5.1_global_5e65360aff
[000015F8]CreateManagedObject(1392): Unspecified error(0x80131604)
[000015F8]GetFactoryObject(1436): Unspecified error(0x80131604)
[000015F8]CreateManagedObject(1392): An attempt was made to load a program with an incorrect format.(0x8007000b)
[000015F8]GetFactoryObject(1436): An attempt was made to load a program with an incorrect format.(0x8007000b)
[000015F8]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[000015F8]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[000015F8]StartFlash(13): The parameter is incorrect.(0x80070057)
[00001404]YPVSLBORPZEE5DZ9 0.00 execute E:\Users\Trev555\Downloads\kenzo\kenzo\flash_all.bat
[00001404]YPVSLBORPZEE5DZ9 0.03
[00001404]YPVSLBORPZEE5DZ9 0.03 $fastboot -s YPVSLBORPZEE5DZ9 getvar product 2>&1 | findstr /r /c:"^product: *kenzo" || echo Missmatching image and device
[00001404]YPVSLBORPZEE5DZ9 0.30 Missmatching image and device
[00001404]YPVSLBORPZEE5DZ9 0.30
[00001404]YPVSLBORPZEE5DZ9 0.30 $fastboot -s YPVSLBORPZEE5DZ9 getvar product 2>&1 | findstr /r /c:"^product: *kenzo" || exit /B 1
[00001404]YPVSLBORPZEE5DZ9 0.36
[00001404]CScriptReport:oWork(433): Unspecified error(0xffffffff)
[00001404]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00001404]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
........thanks in advance for any useful advice
What is your OS? Make sure it's 64 bit..
Did you installed all the driver/requirements correctly?.. You flash it via fastboot or EDL?
The model checking parameter is returning error. Check if you have Mediatek / Snapdragon model of Redmi Note 3.
Thanks for your reply
To offer more information I'm on Windows 8.1 x 64. The error (posted earlier) was when the phone was in Fastboot mode.
In device manager the only thing to note is Android Bootloader Interface but nothing shown in 'other devices'.
When in recovery mode I see Android ADB interface but nothing shown in 'other devices'.
When I type cmd/adb devices the i/d comes up with the word 'sideload' alongside. This I don't understand.
I hope this may give you some ideas Thanks.
I meant to say my phone is running on snapdragon.

Mi 10 softbrick?

Good day,
I need advice. I have a Mi 10 and until recently I had V12.0.6.0.QJBEUXM on Android 10, my phone offered me an update to android 11 V12.2.4.0.RJBEUXM. Some things stopped working so I then found out according to Google that this is a beta version (I probably had my updates enabled, my stupidity) anyway when I wanted to get V12.0.6.0.QJBEUXM back to my phone so I'm stuck on the fastboot screen. I had the bootloader locked, but when I found out that it was a beta version, I unlocked the bootloader and wanted to load back the previous version with android 10 via flash, but the flash tool throws me one error after another, first "sparecrclist error" and then " missmatching image and device "which is bull**** because I have a 100% correct version. I have the bootloader unlocked, but I can't flash any rom on it beacuse mi flast tool throw erros. Can you advise what to do with it?
Solution to Miflash crclist error / failed.
1: Download OFFICIAL MIUI ROM and unzip this ROM to any folder.
2: Open this folder , you'll find 3 files named "flash_all.bat""flash_all_except_storage.bat""flash_all_lock.bat" , create a copy and back them up to another folder for safe.
3: Open and edit the file according to your needs (for example , you need to edit flash_all.bat if you want your phone leaves no files.), Find the listed code:
fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Add "REM"before the two lines , like this:
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Save and exit after this done.
4: Launch Miflash , flash this ROM like usual
if it shows "FAILED" after flash complete and your phone exit fastboot and go dark , congratulations ! you have successfully flashed this ROM !I can't send a connection, just look at it
Problem solved, i have to flash twrp and install Xiaomi.eu rom then via twrp flash global rom with android 10 a then reset and flash via mi flash and lock bootloader.

How To Guide [ROM][MIUI][mojito/sunny] Xiaomi.eu ROM for Redmi Note 10

How to install Xiaomi.eu ROM for Redmi Note 10
We will release fastboot ROM versions until TWRP for mojito/sunny is released
UPDATE:
- TWRP for mojito/sunny is RELEASED
- From now, we will release RECOVERY version of ROM for install via TWRP, so this guide is obsolete
Steps to install xiaomi.eu ROM for first time from China ROM via fastboot (All your data and files on internal storage will be deleted!)
- Update Global ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
{
"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"
}
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
@ingbrzy Will be Xiaomi.Eu version for sweet?
got stuck at fastboot - bootloop after ran the bat file.
sweat...
redmi note 10 - sunny
Edit: managed to flash it after removed _ab in the script.
abc9999 said:
got stuck at fastboot - bootloop after ran the bat file.
sweat...
redmi note 10 - sunny
Click to expand...
Click to collapse
which ROM did you had before?
ingbrzy said:
which ROM did you had before?
Click to expand...
Click to collapse
global rom
Edit: managed to flash it after removed _ab in the script.
abc9999 said:
global rom
Edit: managed to flash it after removed _ab in the script.
Click to expand...
Click to collapse
ok.. flashing by windows or linux?
ingbrzy said:
ok.. flashing by windows or linux?
Click to expand...
Click to collapse
windows
abc9999 said:
windows
Click to expand...
Click to collapse
Did you cd to unzipped folder and execute script from there? Seems fastboot.exe wasn't used from our folder..
Shermo1208 said:
@ingbrzy Will be Xiaomi.Eu version for sweet?
Click to expand...
Click to collapse
@ingbrzy any comments about that? Thanks
Shermo1208 said:
@ingbrzy any comments about that? Thanks
Click to expand...
Click to collapse
yes..
ingbrzy said:
yes..
Click to expand...
Click to collapse
I really look forward to it, man. Didn't have a Xiaomi since the Redmi Note 2 and even back then you were there. Thanks for the effort. I still have 5 days left to be able to unlock the bootloader, so I have to wait anyway. Will sweet get a TWRP support? I don't know, if they still work on TWRP, the latest posts I saw were from end of 2020
ingbrzy said:
yes..
Click to expand...
Click to collapse
When?
abc9999 said:
global rom
Edit: managed to flash it after removed _ab in the script.
Click to expand...
Click to collapse
So please tell us your experience with the rom? Is it stable, are there any performance or lag issues with the rom?
Is network and radio working properly? Is call recording working?
ingbrzy said:
How to install Xiaomi.eu ROM for Redmi Note 10
We will release fastboot ROM versions until TWRP for mojito/sunny is released
Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on internal storage will be deleted!)
- Update Global ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file xiaomi.eu_multi_HMNote10_V12.0.2.0.RKGMIXM_v12-11-fastboot.zip
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..
Click to expand...
Click to collapse
What about Redmi Note 10 Pro India? Will this work in that phone which has 64MP Cam and SD732G?
njaya95 said:
What about Redmi Note 10 Pro India? Will this work in that phone which has 64MP Cam and SD732G?
Click to expand...
Click to collapse
Note 10 Pro and Pro Max(india) are same and same ROMs work on those device, but Note 10 is different.
Is there a way to revert back to global MIUI after flashing the Xiaomi eu version?
ahmedwaseem said:
Is there a way to revert back to global MIUI after flashing the Xiaomi eu version?
Click to expand...
Click to collapse
https://bigota.d.miui.com/V12.0.2.0.RKGMIXM/mojito_global_images_V12.0.2.0.RKGMIXM_20210226.0000.00_11.0_global_06f2a9e26b.tgz
Use official xiaomi flash tool to flash it via fastboot.
I'm having error when flashing the fastboot file. it says "platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mojito" || echo Missmatching image and device"
my unit is sunny ( as per mi unlocker )
but there is no file specified for MOJITO or SUNNY.
thank you.
SSEFIROSU said:
I'm having error when flashing the fastboot file. it says "platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mojito" || echo Missmatching image and device"
my unit is sunny ( as per mi unlocker )
but there is no file specified for MOJITO or SUNNY.
thank you.
Click to expand...
Click to collapse
open .bat file and replace content by this code and save
Bash:
@echo off
cd %~dp0
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" goto END
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *sunny" || echo Missmatching image and device
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *sunny" || exit /B 1
platform-tools-windows\fastboot %* flash dsp images\dsp.img
platform-tools-windows\fastboot %* flash xbl_config images\xbl_config.img
platform-tools-windows\fastboot %* flash boot images\boot.img
platform-tools-windows\fastboot %* flash modem images\modem.img
platform-tools-windows\fastboot %* flash vbmeta_system images\vbmeta_system.img
platform-tools-windows\fastboot %* flash tz images\tz.img
platform-tools-windows\fastboot %* flash vbmeta images\vbmeta.img
platform-tools-windows\fastboot %* flash bluetooth images\bluetooth.img
platform-tools-windows\fastboot %* flash abl images\abl.img
platform-tools-windows\fastboot %* flash dtbo images\dtbo.img
platform-tools-windows\fastboot %* flash vendor_boot images\vendor_boot.img
platform-tools-windows\fastboot %* flash keymaster images\keymaster.img
platform-tools-windows\fastboot %* flash uefisecapp images\uefisecapp.img
platform-tools-windows\fastboot %* flash qupfw images\qupfw.img
platform-tools-windows\fastboot %* flash xbl images\xbl.img
platform-tools-windows\fastboot %* flash cmnlib images\cmnlib.img
platform-tools-windows\fastboot %* flash cmnlib64 images\cmnlib64.img
platform-tools-windows\fastboot %* flash devcfg images\devcfg.img
platform-tools-windows\fastboot %* flash hyp images\hyp.img
platform-tools-windows\fastboot %* flash imagefv images\imagefv.img
platform-tools-windows\fastboot %* flash aop images\aop.img
platform-tools-windows\fastboot %* flash cust images\cust.img
platform-tools-windows\fastboot %* flash super images\super.img
platform-tools-windows\fastboot %* set_active a
platform-tools-windows\fastboot %* erase metadata
platform-tools-windows\fastboot -w
platform-tools-windows\fastboot %* reboot
:END
thank you, after flashing it says not play protect certified. i can't access playstore to install apps.

Categories

Resources