Related
I'm having an issue running the over clock command from this thread http://forum.xda-developers.com/showthread.php?t=1594804. When I run the CPU command, after I type /proc/overclock/ it creates a new line as I finish with the /mpu_opps, and it thinks I'm starting the command from the > /proc . It doesn't continue my command in one whole line. I don't know why when I get to the end of a line in the terminal window it jumps down to a new one. Can anyone shed some light?
Just to clarify you are doing the following and its going to a new line after the > symbol?
su (enter to get into rootspace note that it will change from app_********* to [email protected]*******)
echo 3 1200000000 62 > /proc/overclock/mpu_opps (enter)
echo 384000000 > /proc/overclock/gpu_opps (enter)
Whenever I do it it will continue to type on the same line and push back the echo like in the video.
Yes, that is correct.
All you have to do is permanently mod the file that starts the overclocking - see my posts on this page:
http://forum.xda-developers.com/showthread.php?t=1594804&page=3
Once you do that it automagically starts in overclocked mode every time without you having to mess with the terminal window or hooking up a USB-to-PC (ADB) session.
My htc One is going to need to go in for repair, and i have many images that i dont want to lose, but i know that it is very likely that a factory reset is very likely. Can someone tell what is the easiest and most effective way of saving/storing my wallpapers/photos from the phone back to the phone when it comes back from repair?
Any advice would be very much appreciated, as i am a complete novice when it comes to this sort of thing.
dibdin said:
My htc One is going to need to go in for repair, and i have many images that i dont want to lose, but i know that it is very likely that a factory reset is very likely. Can someone tell what is the easiest and most effective way of saving/storing my wallpapers/photos from the phone back to the phone when it comes back from repair?
Any advice would be very much appreciated, as i am a complete novice when it comes to this sort of thing.
Click to expand...
Click to collapse
What's broken that needs repair?
dibdin said:
My htc One is going to need to go in for repair, and i have many images that i dont want to lose, but i know that it is very likely that a factory reset is very likely. Can someone tell what is the easiest and most effective way of saving/storing my wallpapers/photos from the phone back to the phone when it comes back from repair?
Any advice would be very much appreciated, as i am a complete novice when it comes to this sort of thing.
Click to expand...
Click to collapse
Drag and drop to a folder on your computer, then when the phone comes back drag and drop back into the same place.
dibdin said:
My htc One is going to need to go in for repair, and i have many images that i dont want to lose, but i know that it is very likely that a factory reset is very likely. Can someone tell what is the easiest and most effective way of saving/storing my wallpapers/photos from the phone back to the phone when it comes back from repair?
Any advice would be very much appreciated, as i am a complete novice when it comes to this sort of thing.
Click to expand...
Click to collapse
Here is my little tool to save the whole SDCard, it should be able to do the work... simply follow the instructions:
http://ul.to/0skv8966
Source code, if you think it's a virus:
Code:
::===========================================
::This is Version 1.0 of Android SDCard to PC
::===========================================
@echo off
title Android SDCard To PC
:startProcedure
echo ===============================================================================
echo Willkommen bei Android SDCard To PC
echo Instruktionen: -Shut down your phone into recovery
echo -This tool is only tested on CWM and TWRP, but it should work
echo for all recoveries
echo -It's impossible that this tool damages your phone! But I'm not
echo responsible for any kind if **** that happens
echo -NOW, mount the /data partition from your recovery!
echo ===============================================================================
echo\
cd resources
dir
echo\
echo ===============================================================================
echo Now if you want to continue, press: J
echo If you want to leave, press: N
echo ===============================================================================
set /p pfadUserChoice=
if %pfadUserChoice% == J goto fileCopying
if %pfadUserChoice% == N goto beenden
goto beenden
:beenden
echo Closing programme:
pause
goto ende
:fileCopying
echo ===============================================================================
echo Write here your directory where you want to store the backups
echo (z.B. D:\Users\Name\BackUps )
echo ===============================================================================
set /p computerDirectory=
set backUpDirectoryFinal=/data/media/0
echo Data will be copied if you accept the next request:
echo Von: %backUpDirectoryFinal%
echo Zu: %computerDirectory%
pause
adb remount
adb pull %backUpDirectoryFinal% %computerDirectory%
echo If there were no errors, the process should have worked fine
echo Killing!
pause
:ende
LibertyMarine said:
Here is my little tool to save the whole SDCard, it should be able to do the work... simply follow the instructions:
http://ul.to/0skv8966
Source code, if you think it's a virus:
Code:
::===========================================
::This is Version 1.0 of Android SDCard to PC
::===========================================
@echo off
title Android SDCard To PC
:startProcedure
echo ===============================================================================
echo Willkommen bei Android SDCard To PC
echo Instruktionen: -Shut down your phone into recovery
echo -This tool is only tested on CWM and TWRP, but it should work
echo for all recoveries
echo -It's impossible that this tool damages your phone! But I'm not
echo responsible for any kind if **** that happens
echo -NOW, mount the /data partition from your recovery!
echo ===============================================================================
echo\
cd resources
dir
echo\
echo ===============================================================================
echo Now if you want to continue, press: J
echo If you want to leave, press: N
echo ===============================================================================
set /p pfadUserChoice=
if %pfadUserChoice% == J goto fileCopying
if %pfadUserChoice% == N goto beenden
goto beenden
:beenden
echo Closing programme:
pause
goto ende
:fileCopying
echo ===============================================================================
echo Write here your directory where you want to store the backups
echo (z.B. D:\Users\Name\BackUps )
echo ===============================================================================
set /p computerDirectory=
set backUpDirectoryFinal=/data/media/0
echo Data will be copied if you accept the next request:
echo Von: %backUpDirectoryFinal%
echo Zu: %computerDirectory%
pause
adb remount
adb pull %backUpDirectoryFinal% %computerDirectory%
echo If there were no errors, the process should have worked fine
echo Killing!
pause
:ende
Click to expand...
Click to collapse
Nice idea :good:
Just make sure he's on 4.2.2+ ROM, otherwise if it's still 4.1.2 then it will be in /data/media
LibertyMarine said:
Here is my little tool to save the whole SDCard, it should be able to do the work... simply follow the instructions:
http://ul.to/0skv8966
Source code, if you think it's a virus:
Code:
::===========================================
::This is Version 1.0 of Android SDCard to PC
::===========================================
@echo off
title Android SDCard To PC
:startProcedure
echo ===============================================================================
echo Willkommen bei Android SDCard To PC
echo Instruktionen: -Shut down your phone into recovery
echo -This tool is only tested on CWM and TWRP, but it should work
echo for all recoveries
echo -It's impossible that this tool damages your phone! But I'm not
echo responsible for any kind if **** that happens
echo -NOW, mount the /data partition from your recovery!
echo ===============================================================================
echo\
cd resources
dir
echo\
echo ===============================================================================
echo Now if you want to continue, press: J
echo If you want to leave, press: N
echo ===============================================================================
set /p pfadUserChoice=
if %pfadUserChoice% == J goto fileCopying
if %pfadUserChoice% == N goto beenden
goto beenden
:beenden
echo Closing programme:
pause
goto ende
:fileCopying
echo ===============================================================================
echo Write here your directory where you want to store the backups
echo (z.B. D:\Users\Name\BackUps )
echo ===============================================================================
set /p computerDirectory=
set backUpDirectoryFinal=/data/media/0
echo Data will be copied if you accept the next request:
echo Von: %backUpDirectoryFinal%
echo Zu: %computerDirectory%
pause
adb remount
adb pull %backUpDirectoryFinal% %computerDirectory%
echo If there were no errors, the process should have worked fine
echo Killing!
pause
:ende
Click to expand...
Click to collapse
Liberty - I've never heard of this, but it seems to use adb pull which was going to be one of my suggestions.
is it a ui for these commands?
--
ALSO, dibdin, make sure you have Debugging enabled in Dev Options in settings, and definitely mtp enabled and Fastcharge disabled (if your kernel allows it.)
---------- Post added at 11:16 AM ---------- Previous post was at 10:57 AM ----------
dibdin said:
My htc One is going to need to go in for repair, and i have many images that i dont want to lose, but i know that it is very likely that a factory reset is very likely. Can someone tell what is the easiest and most effective way of saving/storing my wallpapers/photos from the phone back to the phone when it comes back from repair?
Any advice would be very much appreciated, as i am a complete novice when it comes to this sort of thing.
Click to expand...
Click to collapse
if its a cracked digitizer/glass but touch still responds and you can see what youre doing, then you can upload any of them to online storage like Google Drive, Box, Drop Box, etc. the list goes on.
in fact g+ has an auto update feature, if you have used it, it may have already backed up your images..
as for backing up apps: if youre rooted then Titanium Backup (should be "duh!" but in case you didn't know) available on the playstore
or if youre not rooted, theres a relatively new app from Clockwork Mod entitled Helium (also on the playstore) that requires a pc, but not root, and worked great for me since I was afraid to root my One (afraid to brick it like I had with my sgs3 and had to send to jtag (a near 100$ learning experience )
both have premium versions, but if youre into dev or flashing different roms, you'll want to look into either one.
nkk71 said:
Nice idea :good:
Just make sure he's on 4.2.2+ ROM, otherwise if it's still 4.1.2 then it will be in /data/media
Click to expand...
Click to collapse
Oh, okay didn't know that.. thanks, i am gonna update the program so that this guy won't have any troubles if he has Android 4.1.. Do you know if it's possible to determine the Android Version by using ADB and making a CMD check, so the input variable is set automatically? I mean that it changes the directory to /data/media
---------- Post added at 10:26 PM ---------- Previous post was at 10:22 PM ----------
DaringDomino3s said:
Liberty - I've never heard of this, but it seems to use adb pull which was going to be one of my suggestions.
is it a ui for these commands?
Click to expand...
Click to collapse
Yeah.. but it might be easier for him to use a tool instead of working with adb commands.. no there isn't a UI, it's simply a guide.. it does all the work for you... But it simply is a stupid tool.. it's so easy.. but it helps and if you make backups more often, you can let this tool do the work
LibertyMarine said:
Oh, okay didn't know that.. thanks, i am gonna update the program so that this guy won't have any troubles if he has Android 4.1.. Do you know if it's possible to determine the Android Version by using ADB and making a CMD check, so the input variable is set automatically? I mean that it changes the directory to /data/media
---------- Post added at 10:26 PM ---------- Previous post was at 10:22 PM ----------
Yeah.. but it might be easier for him to use a tool instead of working with adb commands.. no there isn't a UI, it's simply a guide.. it does all the work for you... But it simply is a stupid tool.. it's so easy.. but it helps and if you make backups more often, you can let this tool do the work
Click to expand...
Click to collapse
How about using /sdcard, shouldnt that symlink to the correct one?
I'm not thinking straight right now so I better get back 2 u tomorrow...
Sent from my HTC One using Tapatalk
Edit: it's not a stupid tool !
nkk71 said:
How about using /sdcard, shouldnt that symlink to the correct one?
I'm not thinking straight right now so I better get back 2 u tomorrow...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I once had mounting issues on my recovery.. but yeah, I'll try this option once my HTC One is repaired.. *hoping they'll do it on warranty*
Ok, that's very nice
Updated 7.30.20
I have a server up and running and thought it would be perfect to go back to this. I noticed some problems with the original code. After a while, the oem unlock command would hang, so I made it reboot the bootloader ever 1024 keys. I also added an initial oem unlock check because the first time you do the command it asks are you sure. This script should work forever.
I did notice that the screen will get burn in if left on for a long time. I cannot seem to find a way around this, no fastboot command can turn the screen off and keep fastboot running. I figured a $40 screen is worth reviving a $700 phone. This phone has been sitting in a box for years because verizon's anti everyone policies on bootloaders. I will be running this until it cracks the bootloader.
There is an automatic saving/restoring feature in case the computers gets turned off or I need to restart it. I also made the script not repeat characters more than 3 times in a row. I know chances are this won't work, but to me it's worth a try considering I don't have to do anything.
Code:
#!/bin/bash
restore() {
echo "Restoring Previous Session..."
crunch 20 20 ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 -d 3 -s "${file}" | while read line; do
iter=$((iter + 1))
echo "Testing key ${line} - ${iter}"
line2=$((sudo fastboot oem unlock "${line}") 2>&1)
check=$(echo "${line2}" | sed -n 2p)
echo "${check}"
if [ "${check}" != "(bootloader) Code validation failure" ]; then
echo "${line}" >> key
finished
fi
echo "${line}" > current
if [ $iter -eq 1024 ]; then
echo "--------------------"
echo "Rebooting to bootloader"
echo "--------------------"
sudo fastboot reboot bootloader
echo "--------------------"
echo "Sleeping 5 seconds"
echo "--------------------"
sleep 5s
iter=0
echo "--------------------"
echo "Running initial oem unlock"
echo "--------------------"
sudo fastboot oem unlock aaaaaaaaaaaaaaaaaaaa
fi
done
}
new() {
echo "Running New Session..."
crunch 20 20 ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 -d 3 | while read line; do
iter=$((iter + 1))
echo "Testing key ${line} - ${iter}"
line2=$((sudo fastboot oem unlock "${line}") 2>&1)
check=$(echo "${line2}" | sed -n 2p)
echo "${check}"
if [ "${check}" != "(bootloader) Code validation failure" ]; then
echo "${line}" >> key
finished
fi
echo "${line}" > current
if [ $iter -eq 1024 ]; then
echo "--------------------"
echo "Rebooting to bootloader"
echo "--------------------"
sudo fastboot reboot bootloader
echo "--------------------"
echo "Sleeping 5 seconds"
echo "--------------------"
sleep 5s
iter=0
echo "--------------------"
echo "Running initial oem unlock"
echo "--------------------"
sudo fastboot oem unlock aaaaaaaaaaaaaaaaaaaa
fi
done
}
finished() {
echo ""
echo "------------------------------------"
echo ""
echo "A different output was given, probably bootloader key found"
echo "Last checked key was"
echo "${line}"
echo "Key is also stored in a file called key"
echo "${line}" >> key
chmod 555 key
echo ""
echo "------------------------------------"
echo ""
echo "Press enter to close the terminal"
read var
exit 1
}
testresult() {
if [ -f "current" ]; then
file=$(cat current)
if [ "${file}" == "" ]; then
rm current
new
else
restore
fi
else
new
fi
}
testkey() {
if [ -f "key" ]; then
file=$(cat key)
if [ "${file}" == "" ]; then
chmod 775 key
rm key
testresult
else
echo "Key from last run was found, it is"
echo "${file}"
echo "Backing up to key.old"
chmod 775 key
cat key >> key.old
rm key
testresult
fi
else
testresult
fi
}
iter=0
sudo fastboot oem unlock aaaaaaaaaaaaaaaaaaaa
testkey
Knuxyl said:
I wrote a script for linux to bruteforce the bootloader unlock key on the Verizon model Motorola Moto Z2 Force.
Since I do not use my Force I figured I would run a bruteforce on the bootloader to hopefully one day get it unlocked. I am using an ASUS Tinkerboard with Debian 2.0.7 to run this code.
Requirements
Linux (Ubuntu do sudo apt-get install crunch sed, if your using anything else get crunch and sed)
Time
What it does
Generates alpha-numerics keys 20 characters long in order starting at AAAAAAAAAAAAAAAAAAAA.
It creates a file called "current" that will save your spot in case you want to resume later.
It will stop when bootloader response does not says validation failure and save the last used key to a file called "success"
Code (create a .sh file with this, do chmod +x thisfile.sh, then run it with ./thisfile.sh)
Code:
restore() {
crunch 20 20 ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 -s "${file}" | while read line ; do echo "Testing key below ${line}" && line2=$((sudo fastboot oem unlock "${line}") 2>&1) && check=$(echo "${line2}" | sed -n 2p) && echo "${check}" && if [ "${check}" != "(bootloader) Code validation failure" ]; then echo "${line}" >> success && finished ; fi && echo "${line}" > current ; done
}
new() {
crunch 20 20 ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 | while read line ; do echo "Testing key below ${line}" && line2=$((sudo fastboot oem unlock "${line}") 2>&1) && check=$(echo "${line2}" | sed -n 2p) && echo "${check}" && if [ "${check}" != "(bootloader) Code validation failure" ]; then echo "${line}" >> success && finished ; fi && echo "${line}" > current ; done
}
finished() {
clear
echo "A different output was given, probably bootloader key found"
echo "Last checked key was"
echo "${line}"
echo "Key is also stored in a file called success"
echo "${line}" >> success
echo ""
echo "Press enter to close the terminal"
read var
exit 1
}
if [ -f "current" ]; then
file=$(cat current)
if [ "${file}" == "" ]; then
rm current
new
else
restore
fi
else
new
fi
I am running this now, I will post back if I ever get the key. Started 1700 on 23-July-2018.
I am on AAAAAAAAAAAAAAAAAUAA as of 1743 for a time/speed reference.
Click to expand...
Click to collapse
If it works, it might one day, unlock bootloaders for other phones as well. Good luck, first person I found to even try such a thing...
You'd have much better odds winning the lottery than getting a brute force answer in your lifetime. It is really folly. Let's assume you are doing just numeric characters instead of alpha numeric. That gives you 10 to the 20th power number of combinations instead of 36 to the 20th power. So if you wrote really optimized code and could go through 1 billion combinations a second, that would be 10 to the 9th power. I billion seconds later you would have gone through 10 to the 18th power or just one percent of the possible combinations. A billion seconds is a little more than 31 years. So in 3100 years you would have gone though just the strictly numeric solutions. As I've said before, brute force isn't going to get you the answer and shouldn't even be considered a viable answer.
kingstu said:
You'd have much better odds winning the lottery than getting a brute force answer in your lifetime. It is really folly. Let's assume you are doing just numeric characters instead of alpha numeric. That gives you 10 to the 20th power number of combinations instead of 36 to the 20th power. So if you wrote really optimized code and could go through 1 billion combinations a second, that would be 10 to the 9th power. I billion seconds later you would have gone through 10 to the 18th power or just one percent of the possible combinations. A billion seconds is a little more than 31 years. So in 3100 years you would have gone though just the strictly numeric solutions. As I've said before, brute force isn't going to get you the answer and shouldn't even be considered a viable answer.
Click to expand...
Click to collapse
What's your solution? You seem to have all the answers.
Find an exploit.
Try
Code:
fastboot oem unlock nowait
This worked for the Moto 360 on Marshmallow, it MIGHT work.
To find an exploit would be quicker than brute forcing.
doubledragon5 said:
What's your solution? You seem to have all the answers.
Click to expand...
Click to collapse
I don't have all the answers but buying a bootloader unlockable version is what I would recommend. By showing how long it would take I save someone from waiting and waiting for a task that won't complete in his lifetime...
So the phone died like a day later while running the bruteforce. I have the powerpack moto mod so I'm going to have to plug that in to a charger, put it on the phone, and plug usb to phone and pc/tinkerboard... when I get around to it. But I will keep up with this thread.
I tried the nowait fastboot and Code Validation Failure.
Is it even possible for a mobile device to go through 1-billion combinations a second? What if the code was split up over like 10 devices, and the code had each device only working on a smaller section for the unlock code......
azreark1 said:
Is it even possible for a mobile device to go through 1-billion combinations a second? What if the code was split up over like 10 devices, and the code had each device only working on a smaller section for the unlock code......
Click to expand...
Click to collapse
The unlock has to be tested on the specific device so splitting the processing among multiple devices won't solve the problem since each has its own unique code. Just buy a device with an unlockable bootloader since if it was that easy to decode the device wouldn't be very secure and that would have me more worried...
Oh so it's not a generic unlock code, it would still only be device specific?! Yeah thats pretty useless.
The method was initially a failure, why was it laid out here?
08sv80 said:
The method was initially a failure, why was it laid out here?
Click to expand...
Click to collapse
this is really only for people who have a verizon moto z2 force that they do not use and a pc they keep running 24/7. the method is not a failure, it just takes a long time. this is the only solution we have so far, so its better than nothing, but if u dont like it then move on, dont waste time posting useless comments.
for anyone that was interested in this, i must note that while phone is on the bootloader (fastboot) the screen stays on at like max brightness the whole time, so it can easily cause screen burn in. until i find some fastboot command to turn the screen off this is highly not recommended. Mine started burning in so I stopped the process.
you write nonsense and make people believe it? take it easy. your method is initially a failure. Believe on 4PDA, we know all the working methods.
If it hasn't been done, I believe the only way to unlock these bootloaders is exercising some consumer rights through a legal battle, and good luck with that, not worth wasting the time and money. I would be happy to just have temp-root, even if I have to do it every time I boot the phone. That would be more productive to chase, but I believe all exploits have been tried.
Could somebody use IBM's quantum computer
What if somebody could rewrite the script and use IBM's quantum computer. I am not a developer or a script Kitty or anything but that idea crossed my mind. Could it be possible or is it possible. I do know IBM lets people use their old quantum computer so it's just an idea.
Fastlane81 said:
What if somebody could rewrite the script and use IBM's quantum computer. I am not a developer or a script Kitty or anything but that idea crossed my mind. Could it be possible or is it possible. I do know IBM lets people use their old quantum computer so it's just an idea.
Click to expand...
Click to collapse
It's the phone's response and process that takes time, not the computer running the script.
m4f1050 said:
It's the phone's response and process that takes time, not the computer running the script.
Click to expand...
Click to collapse
Ok I figured that there was so many combinations that the normal computer couldn't figure out the combinations that fastso I figured with a quantum computer it can do it in days instead of months or years. That is what I was thinking.
Fastlane81 said:
Ok I figured that there was so many combinations that the normal computer couldn't figure out the combinations that fastso I figured with a quantum computer it can do it in days instead of months or years. That is what I was thinking.
Click to expand...
Click to collapse
Trust me, even an 8-bit Atari can create random numbers fast enough for this task (not saying you can use one, because you need to store the numbers and compare the newly created one with the ones already used, which I would use SQL server for this and not memory.) It's the phone itself the one slowing this down when entering the number and waiting for the phone to respond and starting the process again.
Kindly give instructions.
If someone can kindly give me instructions on how to initiate this code that would be awesome I have Ubuntu 20.04.1 installed on my desktop. And I just need to know how to initiate this script. If you can email me at [email protected] that would be awesome thank you very much
Hello,
i just get a Redmi Note 10s a few days ago. I unlocked it using this tutorial and it worked perfectly.
Then i wanted to root it (because those ads are so annoying). So i used this guide but i had some issues during step 3. After "fastboot.exe reboot" the MIUI setup did not appeard. Then i tried a few things, looking for informations on this web site. But i guess i made a total mess on my phone because now he just turn on and turn off without stopping. It does not even start. I think i destroyed the boot partition using the wrong commands like a n00b ... I'm just abble to get the fastboot mode but not the recovery mode. I can still using fastboot on my computer but adb does not recognize it.
Any idea how i can do a hard/factory reset ?
Thanks a lot !
Ok ...
I tried this : https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
But after 10 minutes of flashing i get a time out error :
[2022-06-03 19:34:57:101:101999 UOMJZXHEHIZHBIBQ]:MiFlash 2022.2.18.0
[2022-06-03 19:34:57:101:101999 UOMJZXHEHIZHBIBQ]:vboytest index:0
[2022-06-03 19:34:57:109:109999 UOMJZXHEHIZHBIBQ]:Thread id:10 Thread name:
[2022-06-03 19:34:57:109:109999 UOMJZXHEHIZHBIBQ]:image path:C:\Users\Operateur\Downloads\rosemary_eea_global_images_V12.5.16.0.RKLEUXM_20220208.0000.00_11.0_eea
[2022-06-03 19:34:57:109:109999 UOMJZXHEHIZHBIBQ]:env android path:"C:\Users\Operateur\Downloads\MiFlash20220218\Source\ThirdParty\Google\Android"
[2022-06-03 19:34:57:109:109999 UOMJZXHEHIZHBIBQ]:script :C:\Users\Operateur\Downloads\rosemary_eea_global_images_V12.5.16.0.RKLEUXM_20220208.0000.00_11.0_eea\flash_all_except_data_storage.bat
[2022-06-03 19:34:57:122:122000 UOMJZXHEHIZHBIBQ]:Physical Memory Usage:3334144 Byte
[2022-06-03 19:34:57:125:125999 UOMJZXHEHIZHBIBQ]:start process id 6044 name cmd
[2022-06-03 19:34:57:555:555330 UOMJZXHEHIZHBIBQ]:info1:$fastboot -s UOMJZXHEHIZHBIBQ getvar product 2>&1 | findstr /r /c:"^product: *secret" || fastboot -s UOMJZXHEHIZHBIBQ getvar product 2>&1 | findstr /r /c:"^product: *rosemary" || fastboot -s UOMJZXHEHIZHBIBQ getvar product 2>&1 | findstr /r /c:"^product: *maltose" || echo Missmatching image and device
[2022-06-03 19:46:37:124:124248 UOMJZXHEHIZHBIBQ]:error: flash timeout6044
[2022-06-03 19:46:37:124:124248 UOMJZXHEHIZHBIBQ]:timeout kill cmd: 6044
It seems totally stucked :'/
Update :
This method https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool did not work either.
The program was not able to connect to the phone.
What's wrong with just reflashing using a relevant stock Xiaomi rom from the official site using their official software?
https://c.mi.com//miuidownload/detail?device=1900397
stuntdouble said:
What's wrong with just reflashing using a relevant stock Xiaomi rom from the official site using their official software?
https://c.mi.com//miuidownload/detail?device=1900397
Click to expand...
Click to collapse
Hi,
thanks, I'll try this as soon as possible and i'll come forward.
EDIT : that's pretty such the same thing i did mention on my second message : https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
So, i did what you told me.
That was almost exactly what i did yesterday, except for two points :
1 - The Xiaomi Flash Tool was older
2 - The ROM was more recent.
It exactly happened the same than yesterday, which is :
After 2 minutes it's 100% complete but it continues, and after 15 minutes my phone reboot.
But i realized something. When the phone is usb-plugged, every 5 or 10 seconds i can hear the windows sound that you hear when you plug or unplug the phone. I hear this sound only when it is on fastboot mode, not when when it is booting again and again.
I checked the Device Manager and every time i hear the sound, it does a refresh.
So i tried to do the same on another computer with another cable and i got exactly the same problem.
Here are the logs :
Code:
[15:57:27 UOMJZXHEHIZHBIBQ]:MiFlash 2020.3.14.0
[15:57:27 UOMJZXHEHIZHBIBQ]:vboytest index:0
[15:57:27 UOMJZXHEHIZHBIBQ]:idproduct: 0 idvendor: 0
[15:57:27 UOMJZXHEHIZHBIBQ]:Thread id:10 Thread name:UOMJZXHEHIZHBIBQ
[15:57:27 UOMJZXHEHIZHBIBQ]:image path:C:\Users\Operateur\Downloads\rosemary_eea_global_images_V12.5.17.0.RKLEUXM
[15:57:27 UOMJZXHEHIZHBIBQ]:env android path:"C:\Users\Operateur\Downloads\MiFlash2020-3-14-0\Source\ThirdParty\Google\Android"
[15:57:27 UOMJZXHEHIZHBIBQ]:script :C:\Users\Operateur\Downloads\rosemary_eea_global_images_V12.5.17.0.RKLEUXM\flash_all_lock.bat
[15:57:27 UOMJZXHEHIZHBIBQ]:Physical Memory Usage:3469312 Byte
[15:57:27 UOMJZXHEHIZHBIBQ]:start process id 14596 name cmd
[15:57:27 UOMJZXHEHIZHBIBQ]:info1:$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *secret" || fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *rosemary" || fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *maltose" || echo Missmatching image and device
At the end of the tutorial you gave me i read this : If the flashing guide could not help you, please download Mi PC Suite here
But i have the same problem with this app : it tries to connect to the phone (Checking for updates) but the phone is 'unpluging' and 'pluging back' again and again and the app show me this : Reading device information failed.
If i click on 'Connect to device' i just get this window saying : Connect your device via USB.
I really do not know what to do :/
extract firmware and download platform tools ,place both files in 1 same folder and now hit flash all to flash firmware
i will write complete guide later
Hey,
thanks for the answer, i'm at work right now so i will not be able to do anything for a few hours.
And i did not understand everything from your message
zuhaibsarwar said:
extract firmware and download platform tools ,place both files in 1 same folder and now hit flash all to flash firmware
i will write complete guide later
Click to expand...
Click to collapse
Hey,
thanks for the answer, i'm at work right now so i will not be able to do anything for a few hours.
And i did not understand everything from your message
So i'll wait a bit for your complete guide ...
After 2 minutes it's 100% complete but it continues, and after 15 minutes my phone reboot.
Click to expand...
Click to collapse
That part is normal for flashing a stock rom, it takes a while. No idea why it likes to say 100% when it's nowhere near complete as yes it's confusing but that's just the way it is.
When the phone is usb-plugged, every 5 or 10 seconds i can hear the windows sound that you hear when you plug or unplug the phone.
Click to expand...
Click to collapse
It sounds like you might not have all the necessary ADB tools correctly configured for fastboot to work properly. It could also be the windows power saving feature on your usb hub causing that issue, or an incorrect or missing driver.
stuntdouble said:
That part is normal for flashing a stock rom, it takes a while. No idea why it likes to say 100% when it's nowhere near complete as yes it's confusing but that's just the way it is.
It sounds like you might not have all the necessary ADB tools correctly configured for fastboot to work properly. It could also be the windows power saving feature on your usb hub causing that issue, or an incorrect or missing driver.
Click to expand...
Click to collapse
Hey,
I check all the drivers and the ADB tools, they are all installed correctly. I change the USB power savings : USB selective suspend settings ==> Disabled.
And ... That was it ! I was able to flash it.
Thanks a lot !
nwaab said:
Hey,
thanks for the answer, i'm at work right now so i will not be able to do anything for a few hours.
And i did not understand everything from your message
So i'll wait a bit for your complete guide ..
Click to expand...
Click to collapse
download original firmware for your device and now extract the firmware for your device in 1 folder and now download platform tools
and also extract it and now move both folder files and in 1 folder and make sure you have adb and fastboot installed now from firmware folder click on flash script to installed firmware in your device and also before clicking in flash script put device on bootloader mode
nwaab said:
Hello,
i just get a Redmi Note 10s a few days ago. I unlocked it using this tutorial and it worked perfectly.
Then i wanted to root it (because those ads are so annoying). So i used this guide but i had some issues during step 3. After "fastboot.exe reboot" the MIUI setup did not appeard. Then i tried a few things, looking for informations on this web site. But i guess i made a total mess on my phone because now he just turn on and turn off without stopping. It does not even start. I think i destroyed the boot partition using the wrong commands like a n00b ... I'm just abble to get the fastboot mode but not the recovery mode. I can still using fastboot on my computer but adb does not recognize it.
Any idea how i can do a hard/factory reset ?
Thanks a lot !
Click to expand...
Click to collapse
stop messing with device by unlocking bootloader .dont get your device hard brick
Hi to all,
found a phone and I had a choice : put it in trash or keep it, I decided the 2nd choice,
1st. attempt: Formatted whole phone (with spflash tool), flashed global_rom, IMEI blank, open wifi, mi-verification lock device back again
2nd & 3rd. attempts: Fixed Imei, with original and not original (modem-meta), mi-verification lock device back again
I guess Mi-verification read not IMEI for locking, but serial number ?
Question is, should I trhow this device to trash or is there a way to be used, by then removing Mi-verification ?
I read along the forum, and the solution seems to be to change the serial-number :
Code:
adb shell "getprop | grep serial"
[ro.boot.serialno]: [050505050505]
[ro.serialno]: [050505050505]
[vendor.gsm.serial]: []
to change it :
Code:
adb shell "setprop ro.serialno 060606060606"
adb shell "setprop ro.boot.serialno 060606060606"
but it return not possible, I guess read only
Is there a way to change serial number, and change configuration of build.prop ?
very good question !
It seems to be a dead argument !! not so much interest on it ..
Pulled build.prop but no trace of ro.serialno or ro.boot.serialno inside,
on a post of 2 years ago, I read that after android 10 there is no possibility to change S/N, is it real ?