Related
Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC
Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).
Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here
Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.
the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.
It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system
If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader
bump? Did anyone end up getting a system image? Thanks.
Nader
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.
ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.
bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.
Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with
I am also not able to flash this system.img file. I get the same error.
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.
Hi guys
I need help about MiFlash!
In MiFlash I have the following problem message:
"The system can not find the specified file (0x"80070002: execute [my path] flash_all_except_storage.bat)"
What am I supposed to do? Maybe I'm a bit stupid, but I followed the guide step by step *thread* ...
Hope you guys can help me fastly, and have nice evening!
Prolution said:
Hi guys
I need help about MiFlash!
In MiFlash I have the following problem message:
"The system can not find the specified file (0x"80070002: execute [my path] flash_all_except_storage.bat)"
What am I supposed to do? Maybe I'm a bit stupid, but I followed the guide step by step *thread* ...
Hope you guys can help me fastly, and have nice evening!
Click to expand...
Click to collapse
Hi,
there are 3 methods to update the rom:
Method 1 - Phone's Updater app
Method 2 - From Recovery mode
Method 3 - From Fastboot mode
Method 1 & 2 use "update.zip" file.
Method 3 uses "update.tgz" file.
Using MiFlash should be method 3
Perhaps you can download the generic tgz file from:
http://en.miui.com/thread-14641-1-1.html
Or you can spend some time to look for a tgz file
that is specfic to your country and language.
Click Thanks if this helps.
Error description
Prolution said:
Hi guys
I need help about MiFlash!
In MiFlash I have the following problem message:
"The system can not find the specified file (0x"80070002: execute [my path] flash_all_except_storage.bat)"
What am I supposed to do? Maybe I'm a bit stupid, but I followed the guide step by step *thread* ...
Hope you guys can help me fastly, and have nice evening!
Click to expand...
Click to collapse
There are three batch (.bat) files in the .tar or .tgz file you chose for flashing :-
1)flash_all.bat
2)flash_all_except_storage.bat
3)flash_all_except_data_storage.bat
Therefore, the error simply meant that file no.2 (as above) is missing from the archive. So you can try the other two options or redownload the flashing archive.
My HTC One M7 (UK O2) was prompting me to update to the latest operating system.
Eventually I succumbed and installed the update. The phone is stock although I had unlocked the bootloader in preparation for experimenting with new operating systems (I'm a noob but curious about experimenting).
After installing, the phone rebooted and wound up on a screen with a red exclamation mark in a picture of a phone.
Sometimes it boots into the white Android startup screen, then shuts down and goes throught the whole startup cycle in a loop
I can get it into bootloader mode but none of the options presented there such as factory reset seem to do anything.
I don't think it's a hardwear problem as it seems to be a direct result of trying to install the update.
I would send it in for a warranty repair but I think that as I have unlocked then relocked the bootloader and it shows a 'relocked' flag then that voids the warranty, is that right?
Any help to sort this mess out would be appreciated.
Thanks
jimbobly
During unlocking bootloader some files deleted and during update ota checks file integrity so file found missing and update stops
So basically you have to restore that files
Or RUU update can be found here
But it will delete your all data photo songs contact apps so backup them
http://forum.xda-developers.com/showthread.php?t=3053944
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
jimbobly said:
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
Click to expand...
Click to collapse
this file: https://www.androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
RUU
Seanie280672 said:
this file androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
Click to expand...
Click to collapse
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
jimbobly said:
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
Click to expand...
Click to collapse
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
alray said:
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
Click to expand...
Click to collapse
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
First is the Md5 good?
RUU
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
jimbobly said:
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
Click to expand...
Click to collapse
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
alray said:
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
Click to expand...
Click to collapse
Unfortunately, this is a bit advanced for me. How can I do this?
jimbobly said:
Unfortunately, this is a bit advanced for me. How can I do this?
Click to expand...
Click to collapse
http://www.winmd5.com/
alray said:
http://www.winmd5.com/
Click to expand...
Click to collapse
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
jimbobly said:
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
Click to expand...
Click to collapse
you need learn flashing RUU zip
reboot your phone to fastboot mode (same as you posted pic )
setup adb folder find miniSDK HERE and Here
Download htc fastboot HERE copy it adb folder rename it fastboot.exe (rename old fastboot to other name)
open adb folder put your RUU zip there rename it RUU.zip
connect your phone with PC
your phone should be locked/relocked
at adb folder open CMD (shift + right click)
type command below
Code:
fastboot devices
(will show attached phone to PC match serial no)
Code:
fastboot oem rebootRUU
(reboot phone to flashing ruu mode)
Code:
fastboot flash zip RUU.zip
(wait it will take time 8-10 minutes it will show successfully at last if not repeat same command immediately)
Code:
fastboot reboot-bootloader
( it is last and important step of flashing)
now see new version showing at phone details
reboot to system
RUU
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
jimbobly said:
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
Click to expand...
Click to collapse
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
yatindroid said:
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
Click to expand...
Click to collapse
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
jimbobly said:
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
Click to expand...
Click to collapse
check md5
fastboot flash zip ( pressing tab will show files in fastboot folder press tab until you got ruu.zip )
Already checked the md5 and it's ok.
What is the best thing to do? Just try a new RUU?
If uou dont know what you are doing,dont ask me
i will try to explain as far as i can.but dont ask stupid questions
-------------- Responsibility for your bricks I do not take over. Everyone does at their own peril and risk .--------------
Click to expand...
Click to collapse
Download this
1) Install the driver for the phone (download);
2) Install a special driver, find it in the Unlock_BootLoader \ Driver for Winwos \ DriverSetup.exe folder;
3) It is necessary to unwind the phone, remove the cover;
4) Open application and press start
5) Test point and connect the phone
6) it will start flashing then stop the proces in betwin the flash
7) wait for 30 sec your device will be in temporary unlocked bootloader mode
8) then flash TWRP (link ) by this command
Code:
fastboot flash recovery_ramdisk XXXXX.img
fastboot flash erecovery_ramdisk xxxxx.img
9) Done. Now you have TWRP_Mod installed in the Recovery section.
10) Then within twrp open adb connect phone to pc
11)type
Code:
adb shell
rm data -r
12)restart device
13) then type
Code:
adb pull /dev/block/sdd4
14) alternatively you can take nvme backup from twrp if u can extract that
you have the NVME file
Reference of nvme
Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern
S0bes said:
Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern
Click to expand...
Click to collapse
Remove the attachment. Dont nake it public. Its harmful
Check the refence try if that work
rajit said:
Remove the attachment. Dont nake it public. Its harmful
Is this twrp backup? Or u pulled via adb?
Click to expand...
Click to collapse
It's not mine and have been already published on 4pda for someone to find the spot in img file
I don't know how it had been pulled. I guess the person bought the code, unlocked the phone and made twrp backup
S0bes said:
Code: JH3KZQA0XD7G2KOZ
File from unlocked by the code phone is attached
Now somebody should look through binary code I guess trying to find the code or something pattern
Click to expand...
Click to collapse
An idea: How about backing up your nvme, then flashing this nvme and unlock the bootloader using this code, then restoring your backup
mehdi554 said:
An idea: How about backing up your nvme, then flashing this nvme and unlock the bootloader using this code, then restoring your backup
Click to expand...
Click to collapse
The img has been taken from another huawei device. not honor play
@rajit have you tried to force unlock boot? Without code just editing nvme file?
https://forum.xda-developers.com/9-lite/how-to/unlock-bootloader-code-t3859685 - step 5
please help me !
please help me !
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_Mod.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.700s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.712s
Where is the test point?
And can i flash magisk file after unlocked bootloader temporar?
mohad2399 said:
please help me !
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_Mod.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.700s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.712s
Click to expand...
Click to collapse
Do you connect the test point??
What's the point of unlocking bootloader if there aren't custom rom for this device yet
devilyuri said:
What's the point of unlocking bootloader if there aren't custom rom for this device yet
Click to expand...
Click to collapse
Custom rom isnt issue if you know how to what! Besides who asked you to take some interest here??
You can ignore! :fingers-crossed:
then how did this end? anyone managed to root using nvme honor play COR-L29 EMUI 9.1 ????
rajit said:
If uou dont know what you are doing,dont ask me
i will try to explain as far as i can.but dont ask stupid questions
Download this
1) Install the driver for the phone (download);
2) Install a special driver, find it in the Unlock_BootLoader \ Driver for Winwos \ DriverSetup.exe folder;
3) It is necessary to unwind the phone, remove the cover;
4) Open application and press start
5) Test point and connect the phone
6) it will start flashing then stop the proces in betwin the flash
7) wait for 30 sec your device will be in temporary unlocked bootloader mode
8) then flash TWRP (link ) by this command
9) Done. Now you have TWRP_Mod installed in the Recovery section.
10) Then within twrp open adb connect phone to pc
11)type
12)restart device
13) then type
14) alternatively you can take nvme backup from twrp if u can extract that
you have the NVME file
Reference of nvme
Click to expand...
Click to collapse
This is really work ?
[/COLOR]
Neverhopless said:
This is really work ?
Click to expand...
Click to collapse
It works but there's no code inside nvme
This method works on Emui 9 ?
What do you mean by "Unwind the phone"?
I have made a simple windows program to help parse a file to possibly find an unlock code.
You simply put exe with the file in the same dirrectory and run.
The program will ask for the file name to parse and then will show any character sequences that follow the pattern rules:
*Length >=16
* A-Z, a-z, 0-9 symbols
See pic example
In case of missing MSVCR120.dll error install https://www.microsoft.com/en-US/download/details.aspx?id=40784
.cpp file is just a source code
Can you fix the tools ?. Google Drive is not available
Link not working
Recently by accident I downgraded the operating system on my Moto G7 Plus device (XT1965-3) and hard bricked my phone. :crying:
It took me some days on checking different threads to come to a solution. I managed to create a blankflash file that finally recovered my bootloader so that I could get into fastboot mode and flash the latest OS.
For those who are faced with the same problem, I'd like to share my solution and hope it works for you as well.
When the phone is hard bricked, it do not boot, it stays in black screen. The good thing though is that by default it goes into Qualcomms EDL (Emergency DownLoad) mode.
When connecting your phone to the PC (e.g. Windows 10) you should see in the device manager under COM the following device:
Qualcomm HS-USB QDLoader 9008 (COM..)
If this do not show up, unplug the phone, press Power + VolumeDown for about 30 seconds and connect the device again.
If it still not works, you might search for the correct drivers.
Assuming you see the device as mentioned above, then you can do the blankflash.
Open a cmd window (ideally with Administrator rights)
Unzip the blankflash.zip View attachment blankflash.zip
Run blank-flash.bat
This should download the bootloader and your phone should get back to live (in fastboot mode)
After you have fixed the bootloader you can flash the latest OS with fastboot mode.
Download the latest version from: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the ROM and add the following files to the same directory View attachment FastBootAddOnFiles.zip
Connect the phone in fastboot mode
Run flashfile.bat from a cmd window
Now the ROM is flashed to the phone
Hope this helps recovering your phone!
Does it work for the power of Moto g7?
Anyway this works on unlocked g7? I need a blank flash or something to revive my hard bricked device
is it possible to restore previously unlocked phone to out-of-the-box software and behaviour? specifically I would like to get rid of the bootloader warning and verity disabled message at boot. I wouldn't mind locking again
"Waiting for device"
Hi WinnieH.
First off, i would like to thank you for explaining the necessity of the blankflash to recover the bootloader.
But when i try the steps you suggested, nothing happens. I get stuck in the message "Waiting for device..."
I noticed that the main command in the bat file is just: ".\qboot.exe blank-flash %*".
Wouldn't be necessary a reference to the singleimage.bin file in this command? Or maybe is a file missing in the zip.
I appreciate some suggestion.
Thanks,
Marcos
mrufino said:
Hi WinnieH.
First off, i would like to thank you for explaining the necessity of the blankflash to recover the bootloader.
But when i try the steps you suggested, nothing happens. I get stuck in the message "Waiting for device..."
I noticed that the main command in the bat file is just: ".\qboot.exe blank-flash %*".
Wouldn't be necessary a reference to the singleimage.bin file in this command? Or maybe is a file missing in the zip.
I appreciate some suggestion.
Thanks,
Marcos
Click to expand...
Click to collapse
Sorry for late response.
if the message "Waiting for device ..." comes, then your phone is not recognized correctly. Your device when bricked should connect in Emergency Download (EDL) mode. You could see this when you go to the Windows Device Manager. Under the COM devices your phone should show up with the Qualcomm. If not, disconnect the phone for a minute and try it again.
If you have the driver not installed it, the installation video might help: https://www.youtube.com/watch?v=ezQJlBKN9hk
PS: The blank-flash.bat is fine. It will automatically use the singleimage.bin file
Hope you get your way
Thank you WinnieH for the response. (that was not late at all!).
I will try to install the driver; I was unable to connect in Emergency Download Mode.
mrufino said:
Thank you WinnieH for the response. (that was not late at all!).
I will try to install the driver; I was unable to connect in Emergency Download Mode.
Click to expand...
Click to collapse
Well, first of all thanks to WinnieH for this useful thread. It worked fine for my phone.
@mrufino Maybe you have to install the moto drivers. Or try a different pc. The phone was not detected on my first pc, on my other pc it was detected immediately.
WinnieH said:
Recently by accident I downgraded the operating system on my Moto G7 Plus device (XT1965-3) and hard bricked my phone. :crying:
It took me some days on checking different threads to come to a solution. I managed to create a blankflash file that finally recovered my bootloader so that I could get into fastboot mode and flash the latest OS.
For those who are faced with the same problem, I'd like to share my solution and hope it works for you as well.
When the phone is hard bricked, it do not boot, it stays in black screen. The good thing though is that by default it goes into Qualcomms EDL (Emergency DownLoad) mode.
When connecting your phone to the PC (e.g. Windows 10) you should see in the device manager under COM the following device:
Qualcomm HS-USB QDLoader 9008 (COM..)
If this do not show up, unplug the phone, press Power + VolumeDown for about 30 seconds and connect the device again.
If it still not works, you might search for the correct drivers.
Assuming you see the device as mentioned above, then you can do the blankflash.
Open a cmd window (ideally with Administrator rights)
Unzip the blankflash.zip View attachment 4810965
Run blank-flash.bat
This should download the bootloader and your phone should get back to live (in fastboot mode)
After you have fixed the bootloader you can flash the latest OS with fastboot mode.
Download the latest version from: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the ROM and add the following files to the same directory View attachment 4810964
Connect the phone in fastboot mode
Run flashfile.bat from a cmd window
Now the ROM is flashed to the phone
Hope this helps recovering your phone!
Click to expand...
Click to collapse
Great post. Where did you find the singleimage for your phone? i've tryed to do with my G7 RIVER bricked, but unsuccessful need some help!
diegovmsouza said:
Great post. Where did you find the singleimage for your phone? i've tryed to do with my G7 RIVER bricked, but unsuccessful need some help!
Click to expand...
Click to collapse
Hello,
I did the image by myself. I used a older image of a G6 device and replace a number of elements in the image from the stockrom. With "star" you can delete and add files to the "singleimage.bin" archive. It took me some trials. Check on the latest STOCK ROM "XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" from https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/ and you should find the most important files (such as partition table: gpt.bin).
Hope it works for you
Regards
Winnie
WinnieH said:
Hello,
I did the image by myself. I used a older image of a G6 device and replace a number of elements in the image from the stockrom. With "star" you can delete and add files to the "singleimage.bin" archive. It took me some trials. Check on the latest STOCK ROM "XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" from https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/ and you should find the most important files (such as partition table: gpt.bin).
Hope it works for you
Regards
Winnie
Click to expand...
Click to collapse
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
diegovmsouza said:
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
Click to expand...
Click to collapse
Just use "star list bootloader.img" and you get all the relevant file.
Code:
star list ..\..\XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\bootloader.img
1 339968 md5:e4c77bb1f8862444bedb908067d5063d abl.elf
2 519296 md5:4b8eaa75b77eae4981604f7893bf7279 cmnlib.mbn
3 519296 md5:ac35656340c5f87037a64ce4f937b16c cmnlib64.mbn
4 2722 md5:d3ee34bff4d352a045b7e42b447666a7 default.xml
5 126080 md5:4590a7b21b0d70d4403fa95ad23a6e9d devcfg.mbn
6 38400 md5:27ba16d71e0d16c86423192d5615a25c gpt.bin
7 519296 md5:0582b648798303e0441930fd84a39b9a hyp.mbn
8 519296 md5:2686fd49e16e78a0e9ef2335104e96bc keymaster.mbn
9 125 md5:c3a63b25166c5fcac0cc1426bf44a271 pkg.xml
10 519296 md5:1437d90bab43816d4a3541b18edac61c pmic.elf
11 257152 md5:5e3b6f2cf09747bd3bac33023c2014a7 prov64.mbn
12 519296 md5:31ab4015a996f2ad6dd61c94076fea98 rpm.mbn
13 126080 md5:5054d3c7863d09d6333c509003548e4d storsec.mbn
14 2092160 md5:44a6f561bab5d2822066574e3d0116eb tz.mbn
15 3665024 md5:a2a5945cf2ae44cd95da3ee180480662 xbl.elf
16 172 md5:1fd033214e7e36c4134a927f1ce944f0 index.xml
17 606400 md5:4b6e1345d3fb9b347ce7fc6357def85a programmer.elf
Extract the files from the bootloader and replace them on the singleimage.bin and thats it.
e.g.
Code:
star delete abl.elf
star add abl.elf
Pressing thumbs
WinnieH said:
Just use "star list bootloader.img" and you get all the relevant file.
Code:
star list ..\..\XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\bootloader.img
1 339968 md5:e4c77bb1f8862444bedb908067d5063d abl.elf
2 519296 md5:4b8eaa75b77eae4981604f7893bf7279 cmnlib.mbn
3 519296 md5:ac35656340c5f87037a64ce4f937b16c cmnlib64.mbn
4 2722 md5:d3ee34bff4d352a045b7e42b447666a7 default.xml
5 126080 md5:4590a7b21b0d70d4403fa95ad23a6e9d devcfg.mbn
6 38400 md5:27ba16d71e0d16c86423192d5615a25c gpt.bin
7 519296 md5:0582b648798303e0441930fd84a39b9a hyp.mbn
8 519296 md5:2686fd49e16e78a0e9ef2335104e96bc keymaster.mbn
9 125 md5:c3a63b25166c5fcac0cc1426bf44a271 pkg.xml
10 519296 md5:1437d90bab43816d4a3541b18edac61c pmic.elf
11 257152 md5:5e3b6f2cf09747bd3bac33023c2014a7 prov64.mbn
12 519296 md5:31ab4015a996f2ad6dd61c94076fea98 rpm.mbn
13 126080 md5:5054d3c7863d09d6333c509003548e4d storsec.mbn
14 2092160 md5:44a6f561bab5d2822066574e3d0116eb tz.mbn
15 3665024 md5:a2a5945cf2ae44cd95da3ee180480662 xbl.elf
16 172 md5:1fd033214e7e36c4134a927f1ce944f0 index.xml
17 606400 md5:4b6e1345d3fb9b347ce7fc6357def85a programmer.elf
Extract the files from the bootloader and replace them on the singleimage.bin and thats it.
e.g.
Code:
star delete abl.elf
star add abl.elf
Pressing thumbs
Click to expand...
Click to collapse
thanks for listening. When I list the bootloader.iso file it returns me the following error: "Failed: simg_open () -> IO error". already extract the rom stock again, already downloaded it from scratch and the result is the same. When I extract the bootloader.iso file the same error occurs. what could it be? Can you help me extract these files? I am attaching the bootloader file of moto g7 river, if you can help me I will be immensely grateful.
diegovmsouza said:
thanks for listening. When I list the bootloader.iso file it returns me the following error: "Failed: simg_open () -> IO error". already extract the rom stock again, already downloaded it from scratch and the result is the same. When I extract the bootloader.iso file the same error occurs. what could it be? Can you help me extract these files? I am attaching the bootloader file of moto g7 river, if you can help me I will be immensely grateful.
Click to expand...
Click to collapse
Hello,
you are right. I should have written down how I created the singleimage.bin file. I replaced the following files in the singleimage.bin from the river stock rom version: XT1962-6_RIVER_RETEU_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (loaded from: https://mirrors.lolinet.com/firmware/moto/river/official/RETEU/)
gpt.bin
And changed the index.xml to the right CPU 632
You might to play around with the board id if it do not work (board id="204"). I hope the programmer file is the same for the G7 (processor type is slightly different: Snapdragon 632 instead of 636).
Give it a try with attached blankflashRiver.zip
WinnieH said:
Hello,
you are right. I should have written down how I created the singleimage.bin file. I replaced the following files in the singleimage.bin from the river stock rom version: XT1962-6_RIVER_RETEU_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (loaded from: https://mirrors.lolinet.com/firmware/moto/river/official/RETEU/)
gpt.bin
And changed the index.xml to the right CPU 632
You might to play around with the board id if it do not work (board id="204"). I hope the programmer file is the same for the G7 (processor type is slightly different: Snapdragon 632 instead of 636).
Give it a try with attached blankflashRiver.zip
Click to expand...
Click to collapse
Thanks for the help. the Programmer file isn't the same. After to work arround and beat my head over and over on the wall, I've took my phone to an authorized Motorola. For my surprise, as my phone shows oem_lock, they accepted on warranty. LOL. Now it's on repair and I'll catch tomorrow or another. Thanks for all. Thumbs up!
Rooting with patch security agost 2019
Hello
does this method work for the security patch of august 1, 2019?
does it works in moto g7 power? or others ways that qualcomm port not send error
I tryed in windows 7x64,10x64 without response, it shows me an error port just every time, qualcom usb drivers are shows correct ,
I cant continues with the fastboot part, people any advice?
diegovmsouza said:
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
Click to expand...
Click to collapse
Greetings Winnieh !, thanks for all the time and good information that you post,
I have doubts I would appreciate some advice, I have a motorola g7 power (ocean) tha's in hardbrick mode, I have already installed the correct qualcom drivers, the com port recognizes my device, but I cannot get the file blankflash.bat to load the phone to the moment executing it gives me an error:
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 2.218] ReadFile() failed, GetLastError()=0
[ 11.019] ERROR: sahara_greet_device()->device_open()->error opening device
[ 11.019] Check qboot_log.txt for more details
[ 11.019] Total time: 11.019s
FAILED: qb_flash_singleimage()->sahara_greet_device()->device_open()->error open
ing device
I realize that the blankflash.bat for the motog7 + version (river)
based on the blankflash file that you attached
I extracted the bootloader.img files from the stockrom of the motog7 power (ocean) XT1955-2 XT1955-2_OCEAN_AMX_9.0_PPO29.80-79_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml , so also delete and add all the files to the singleimpt.bin file - the gpt.bin file from stock rom copy and replace the one I saw in singleimage.bin
what you notice that index.xml refers to as "cpu.name: msm8953"
it also appears the same in the gpt.bin file, finally with the new singleimage.bin file compiled try to run the blankflash.bat again
unsuccessfully....
Could you tell me what are the mistakes that I can't solve?
i'm not a programmer just a bad lucky pal. if by chance have you a blankflash.bat for ocean version?, i'll really appreciate
Thank you! for your time
Hi WinnieH, I have a similar problem with a Moto G7 Power, can you tell me how I can create a blankflash for my specific model?
Lupask said:
is it possible to restore previously unlocked phone to out-of-the-box software and behaviour? specifically I would like to get rid of the bootloader warning and verity disabled message at boot. I wouldn't mind locking again
Click to expand...
Click to collapse
I have this exact same situation. did you find a solution to it?