Hello guys,
I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU.
The process is super easy:
1) Download & extract the following .zip
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
7) Once done, force reset and Voilà!
There's an alternative as well: MultiportQLoader
I haven't tried it myself, feel free to try it and share the steps.
Im sorry if any details aren't clear, but I'm typing this while driving xD
Good luck and would appreciate a shout-out on insta @Out.Geeked ^^
THANK YOU SIR
To ask a dumb question, but is this only the 6 or for the pro as well?
Works for both
Thank you so much, it work after someone help me erase flash
Outgeeked.net said:
Works for both
Click to expand...
Click to collapse
Yeah I checked the model number against the box it came in and gave it a shot, now it shows the RM logo and then reboots to the bootloader lmao this phone legit hates me
*edit*
So I think either I'm doing something wrong or this phone is actually messed up. Checked the drivers, tried 2 other cables, all my USB ports and still all it does is briefly show the white "System Rebooting" screen and then the RM logo for about 20 seconds and then reboots to fastboot/bootloader.
MiFlash shows "couldn't find flash script" but otherwise looks like it goes through the reflash process completely but QLoader always fails with an error "Unknown chunk type cac2"
Does this unbrick method require the bl to be unlocked?
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Nocturne Seigneur said:
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Click to expand...
Click to collapse
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
CyberWolf92 said:
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
Click to expand...
Click to collapse
loool welcome to the club xD, I didn't found any solution yet, i will tell u once confirmed, for now i can write imei but mobile network still not functioning
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
cannon3025 said:
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
Click to expand...
Click to collapse
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Nocturne Seigneur said:
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Click to expand...
Click to collapse
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
cannon3025 said:
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
Click to expand...
Click to collapse
its gone, forever lol
i just gave my phone to someone else to fix this, if he can.
[Guide] Restore Lost IMEIs / Repair Network or Radio Issues
I accidentally restored TWRP backup of another Zuk Z2 phone on my new pgone and in this process over-wrote the EFS partition. This left me with a phone having no IMEI, no mac for Wifi and Bluetooth. Effectively No Network on phone. Worried, I...
forum.xda-developers.com
this maybe work, havent test it out
Since we have the partition layout & the correct firehose, it should actually be a good practice by anyone wanting to play with their phone (BL unlock, root, dev, etc) to first dump the critical partitions.
That way, you can always restore. Example: EFS, misc, persist, etc.
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Same issue for @CyberWolf92
Alaryani said:
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Click to expand...
Click to collapse
Select the images folder and then hit flash.
Mine is alive again, no more problems.
I think I know why a lot of people have probably bricked their device after flash from CN to Global. If you do a local update, let the device REboot until the end. After the restart it uses the update.zip again. I think a lot of people did a factory reset immediately after the reboot (like me in Recovery) and the system can no longer find the update.zip.
Therefore, let the update run through, reboot until you are back in the system. Then you can do a factory reset.
Outgeeked.net said:
Select the images folder and then hit flash.
Click to expand...
Click to collapse
When I selected images folder shows "couldn't find flash script"
{
"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"
}
And when I go to edl mode my phone disappeard from list devices in MiFlash.
but still showing in driver manger
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
Alaryani said:
When I selected images folder shows "couldn't find flash script"
View attachment 5329645
And when I go to edl mode my phone disappeard from list devices in MiFlash.
View attachment 5329643
but still showing in driver manger
View attachment 5329647
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
View attachment 5329661
Click to expand...
Click to collapse
you must be in edload mode not fastboot
Related
Hi every body, I had reviced a lot of question about how to backup qualcomm devices. So today I will show you how! (test in Obi SF1)
Because if your phone is not root, you can't back up your rom in case brick when you play with the phone. So you will need this!!!
1: Download all necessary files (in my video description) put all of them in the same folder and extract out!
2: in stall the right driver (make sure your usb connect type is MTP)
When your phone and computer are connected and in devices manager you see some thing with a yellow triangle and the QFIL software show “no port available” that mean you need driver!
To install the driver, run qualcomm_Setup as administrator! Restart your computer. If success, no more yellow triangle in devices manager.
3: now put your phone into download mode by: install QPST.2.7.437 to your computer. Then run eMMC Software Download, chose switch device to DLOAD…> chose your phone >ok, now you will see several new hard disks in your computer , and in device manager you will see something like qualcomm emmc or qualcom mmc... in hard disk field! now close the eMMC Software Download software.
4: Run HDDRawCopy1.10Portable, chose Qualcomm MMC Storage USB Device (your phone flash) then click continue > double click on file > browse to pale you want to save the backup file > name the file, in file type field, chose raw img file > save > click continue and wait to complete (it may took along time depend on your memory size)
To wake up the phone out of download mode, just press all three hard buttons same time in 2 minutes !!! (for Obi phone, may different in other phones).
Link to this document in description too!
Attention: this method no need root, and you will have the full rom back up. But be careful if you chose wrong field you may miss your hard disk’s data, and when you apply the back up again to your phone your phone will really hard brick if you break the process. So if you had rooted the phone, use another method for better!!!
Guide video and tool links here:
If read back gets interrupted in between will it brick ?
Demon_king18 said:
Hi every body, I had reviced a lot of question about how to backup qualcomm devices. So today I will show you how! (test in Obi SF1)
Because if your phone is not root, you can't back up your rom in case brick when you play with the phone. So you will need this!!!
1: Download all necessary files (in my video description) put all of them in the same folder and extract out!
2: in stall the right driver (make sure your usb connect type is MTP)
When your phone and computer are connected and in devices manager you see some thing with a yellow triangle and the QFIL software show “no port available” that mean you need driver!
To install the driver, run qualcomm_Setup as administrator! Restart your computer. If success, no more yellow triangle in devices manager.
3: now put your phone into download mode by: install QPST.2.7.437 to your computer. Then run eMMC Software Download, chose switch device to DLOAD…> chose your phone >ok, now you will see several new hard disks in your computer , and in device manager you will see something like qualcomm emmc or qualcom mmc... in hard disk field! now close the eMMC Software Download software.
4: Run HDDRawCopy1.10Portable, chose Qualcomm MMC Storage USB Device (your phone flash) then click continue > double click on file > browse to pale you want to save the backup file > name the file, in file type field, chose raw img file > save > click continue and wait to complete (it may took along time depend on your memory size)
To wake up the phone out of download mode, just press all three hard buttons same time in 2 minutes !!! (for Obi phone, may different in other phones).
Link to this document in description too!
Attention: this method no need root, and you will have the full rom back up. But be careful if you chose wrong field you may miss your hard disk’s data, and when you apply the back up again to your phone your phone will really hard brick if you break the process. So if you had rooted the phone, use another method for better!!!
Guide video and tool links here:
Click to expand...
Click to collapse
Hi ,
Thanks for the video link. I want to use this so that I can get boot image and recovery image so that it can be ported . My phone is Gionee M6S plus Snapdragon chipset with locked boot loader. I would like to ask while In reading mode ,if by unforseen reason the readback gets interrupted ;is there any chance of hard bricking ?
Thanks
Suhi02 said:
Hi ,
Thanks for the video link. I want to use this so that I can get boot image and recovery image so that it can be ported . My phone is Gionee M6S plus Snapdragon chipset with locked boot loader. I would like to ask while In reading mode ,if by unforseen reason the readback gets interrupted ;is there any chance of hard bricking ?
Thanks
Click to expand...
Click to collapse
Nope, in backup process just don't format or delete any any thing in your phone's internal memory, your phone will be ok. But when you restore the phone, if the process broke, your phone maybe brick depen on how many percen had complete!
how to restore?
Hi,
thanks for this tutorial but i have a question, my device is Asus Zenfone 4 Selfie Lite ZB553KL (Sd425), i want to know how to wake my device from download mode before i start this tutorial as i dont want to brick my device
Can we backup full boot.img and system.img with that?
Or does it only backup data partition?
skeleton1911 said:
Can we backup full boot.img and system.img with that?
Or does it only backup data partition?
Click to expand...
Click to collapse
When you using this method, it will backup all of your partition: boot, recovery, efs, system, and user data too!
Rempoiiii said:
Hi,
thanks for this tutorial but i have a question, my device is Asus Zenfone 4 Selfie Lite ZB553KL (Sd425), i want to know how to wake my device from download mode before i start this tutorial as i dont want to brick my device
Click to expand...
Click to collapse
For my device (Obi Sf1) just long press (may up to 3 minutes) all of my 3 hard buttons to wake him up!
irwan_dcp said:
how to restore?
Click to expand...
Click to collapse
Sorry, my phone had lost, so i can't made a guide video for you. But there is a guide here: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Hope usefull!
Nice tutorial but eroor 0x80004005 when pressing download mode
Nice tutorial thanks, but I'm getting error code 0x80004005 after pressing download mode, trying to backup huawei scl-l01 in QC 9008 mode port is visible drivers are ok
Hi @Demon_king18, sorry for bringing this old thread back up but I am having the same problem as @Provokuoji is.
When I open emmc software download app, and I try to switch to DLOAD, I get this message
{
"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"
}
This is the only thing stopping me for now. Might you know what is happening? :crying:
Hi @Demon_king18, sorry for bringing this old thread back up but I am having the same problem as @Provokuoji is.
When I open emmc software download app, and I try to switch to DLOAD, I get this message
This is the only thing stopping me for now. Might you know what is happening? :crying:
Getting the 0x80004005 error also. Any suggestion? The phone shows up as qualcomm device just fine.
find another way to boot into EDL mode. usually you have a timeout ~30 sec
Can we restore userdata with qfil ?
aIecxs said:
find another way to boot into EDL mode. usually you have a timeout ~30 sec
Click to expand...
Click to collapse
There is no other way to boot into EDL if your screen is completely blacked out and all what the computer recognises is a Qualcomm device in Device Manager.
deep flash cable? test point method?
aIecxs said:
deep flash cable? test point method?
Click to expand...
Click to collapse
I have a cable and it doesn't work.
I took my phone apart and did the test point shorting, that doesn't work either.
I have also been told that the phone is already in EDL mode but the problem is me getting that error message!
if it is already in EDL mode, just install Qualcomm HS-USB QDLoader 9008 Driver
aIecxs said:
if it is already in EDL mode, just install Qualcomm HS-USB QDLoader 9008 Driver
Click to expand...
Click to collapse
Done that from the start.
Hello guys,
I have cedric, bootloader unlocked, rooted, etc.. I used some SDcard format app and selected wrong storage to format emmcblk0, so i formated entire phone, now in device manager its detected as "Quectel QDLoader 9008
" cannot power it on as well i think bootloader is bricked, i tryed to flash but cant find anything related to this phone, also cant find blankflash.
Do you guys have any info on how to unbrick this hard-brick, or its just paper weight? I don't get how did moto/lenovo allow bootloader erase option from system, even with root...
Regards
Perhaps search for some driver that enables the transfer of the bootloader for "Quectel QDLoader 9008"?
I've found some results relating to unbricking this, and according to some of them it refers to a chipset, use this search perhaps https://www.google.co.uk/search?q=Q...rome..69i57.2111j0j7&sourceid=chrome&ie=UTF-8
---------- Post added at 11:30 PM ---------- Previous post was at 11:28 PM ----------
found this, it may help http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
Tryed, not applicable for this mode, i need blankflash or some other method, i still have yet to try sdcard flash, but i am loosing hope here, might just accept that its totally bricked and thats it, oh well moving on i guess.
Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted.
Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
And upload me that file, it will be around 160mb, i will try to test it and if it works upload the tutorial. The command above just reads your mmmcblk0 so there is no chance of bricking your device.
No one willing to give away five minutes to help? I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community
magix01 said:
No one willing to give away five minutes to help? I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community
Click to expand...
Click to collapse
Hey Mate i would help you if i could, but i'm on -72, if this would help you tell me, and i will upload the file asap.
@Cubico
We can try, but i don't think it will work tho. Please upload and we will see i guess
Ok guys new update, @Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with JTAG and update you on status.
I have got a similar issue with an X4 that's hard bricked.
I know wrong forum, but I can't find anyone to help.
Trying to use QFIL I get "Download Fail: Switch To EDL Fail: Failed to Switch to Emergency Download mode"
ANY ideas? Thank you anyone that may be able to help!
Try installing this driver, then transfer/flash the bootloader, I can't help you with the actual img though.
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/#
magix01 said:
Ok guys new update, @Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with JTAG and update you on status.
Click to expand...
Click to collapse
Hi, just saw this - I'm on NP25.137-93
Do you still need this dump?
Let me know and I'll get on it
Edit - aww crap!
Really sorry to get your hopes up! Just remembered, my phone's not unlocked or rooted! This is the first phone I've had in years that I've kept unrooted, so I didn't initially realise.
?
Np, i took the phone to service center for JTAG, hopefully they will manage to fix it somehow
Exanneon said:
Try installing this driver, then transfer/flash the bootloader, I can't help you with the actual img though.
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/#
Click to expand...
Click to collapse
This is not related to driver, bot Qualcomm and Quectel 9008 drivers work and allow communication with the phone, patch level is too high so blankflash files dont pass and dont allow bootloader to be flashed. Only solution is JTAG or motherboard replacement if patch level is higher than one in april 2017 i think.
Rip another cedric.
{
"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"
}
This has happened to me and I'm lucky had the assistance replaced the motherboard of the device. Your bootloader was not deleted, it was moved to a temporary partition that the boot script cannot find after pressing to start.
The problem with the manufacture is of the appliance was to have the bootloader on the same chip as the other partitions, causing the device to be easily hardbroken.
Solution? None so far.
I saw a guy who unbricked a potter (G5 Plus), but I've seen nothing from the G5.
Heh, another G5 killer here. A bad attempt at downgrading due to IMEI 0 left it as QLoader 9008. I guess I'll have to go back to my old Nexus 4.
Motorola sucks bad, Google and Xiaomi for instance have tools to recover dead bootloader eg. "Mi Flash", motorola gave developers easy bootloader unlock but no way to recover it, whats the point then, either make it recoverable or make it non erasable easily.
magix01 said:
Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted.
Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
And upload me that file, it will be around 160mb, i will try to test it and if it works upload the tutorial. The command above just reads your mmmcblk0 so there is no chance of bricking your device.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view?usp=sharing
abhimanyuk said:
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view?usp=sharing
Click to expand...
Click to collapse
It doesn't seem to work for me. It might be because I had the latest January update when I killed my Cedric.
These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.
magix01 said:
These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.
Click to expand...
Click to collapse
Yeah, I tried with two different SD*cards, but the device would only blink the notification light while being recognised as Qualcomm Loader.
i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone
testask123 said:
i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone
Click to expand...
Click to collapse
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.
TechnoSparks said:
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.
Click to expand...
Click to collapse
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?
testask123 said:
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?
Click to expand...
Click to collapse
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?
TechnoSparks said:
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?
Click to expand...
Click to collapse
bootloader is not unlocked
testask123 said:
bootloader is not unlocked
Click to expand...
Click to collapse
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
edit: also because i totally forgot that unlocking the BL will definitely wipe the device, which defeats the purpose of this thread!
TechnoSparks said:
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
Click to expand...
Click to collapse
is there no trustworthy program that could back it up?
testask123 said:
is there no trustworthy program that could back it up?
Click to expand...
Click to collapse
With what i knew so far with [AOSP] Android, no, because there needs to be a user confirmation on the screen. I suppose maybe Xiaomi have some proper backup tools? (I guess)
Oh yeah, maybe an external display could work. Please wait while I try to gather some limited information
After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
Could you go into details as to how to modify boot.img to enable adb?
I tried searching a bit but nothing came up
It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.
Renate said:
It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.
Click to expand...
Click to collapse
Ahhh I see , but why boot.img? It's rather difficult to modify for you gotta unpack ramdisk and all? ( I tried doing this long time ago but got stuck on how to repack properly x: )
System.img / vendor.img should be better targets for u can unsparse them ( make rw ) on PC and easily edit .prop files
It's a rly good idea
It's easier to pack something if you never unpack it.
imgutil.exe in my sig lets you modify boot images without taking it all apart.
Warning: Android moves on and many busy bees are working to make our lives more difficult.
If you have problem with imgutil.exe contact me about it.
Code:
C:\>imgutil.exe /v /x boot.img prop.default
C:\>my-fave-editor.exe prop.default
C:\>imgutil.exe /v /r boot.img prop.default
Just don't use some ignorant Windows editor like "Notepad" that uses \r\n.
I like Notepad++.
Also, with a boot image you can try booting it without flashing it.
TechnoSparks said:
After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?
Click to expand...
Click to collapse
it's hard to tell, maybe i should try to see if i can pull it of, but don't know the exact position of the usb setting in the dropmenu.
if someone could provide some screenshot, it might give me an idea where to tap.
Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
i remember turning on wifi debugging, but dont know if that's still the case or even useful
testask123 said:
i remember turning on wifi debugging, but dont know if that's still the case or even useful
Click to expand...
Click to collapse
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)
Renate said:
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)
Click to expand...
Click to collapse
the ip from the phone?
sorry i'm not so knowledgeable about these things and wanted to make sure
{
"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"
}
Yeah, the IP of your phone.
If you're on your own router you can log in and see if your phone is there and what IP.
Now you know that my cheap Walmart tablet is on (local) IP 192.168.1.4
Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)
mdve123 said:
Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)
Click to expand...
Click to collapse
Sorry to hear that, please share your steps to disaster to let others know how to avoid this.
I assume that you used default Windows installer that broke your ufs gpt, instead of the installer you should have been used dism.
At this stage only a service may help you, they will put the device in edl mode and flash a stock firmware.
I think the only way to bring it back to life is to get it into EDL mode and force flash stock rom.
but to get to EDL first have to get to fastboot, i dont think it will work, also tried...
mdve123 said:
but to get to EDL first have to get to fastboot, i dont think it will work, also tried...
Click to expand...
Click to collapse
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.
serdeliuk said:
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.
Click to expand...
Click to collapse
Very useful info thank you! Just ordered a deepflash cable, hopefully i will find a workaround to flash in EDL.
If not, i'll try to get it done under warranty. I do not want to risk a keylog or a scam.
I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked
RoyPH9903 said:
I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked
Click to expand...
Click to collapse
You should download the latest MIUI Stable Fastboot update corresponding to your region (global, eeaor other) from this thread https://forum.xda-developers.com/t/miui-updates-tracker-xiaomi-pad-5-nabu.4328591/ , decompress the tgz file with 7zip or another software, and then, with your device in fastbboot mode, execute the flash_all.bat file within the folder you extracted. This should work even with a locked bootloader.
Good luck
I get this error
{
"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"
}
RoyPH9903 said:
I get this error
View attachment 5883229
Click to expand...
Click to collapse
Well, maybe I was wrong and you need an unlocked bootloader for this method to work. You could try to unlock it again with MiUnlock https://en.miui.com/unlock/download_en.html . Otherwise, I am out of idea.
I tried it and it didn't work, it tells me that I have to enable my miui account.
RoyPH9903 said:
I tried it and it didn't work, it tells me that I have to enable my miui account.
View attachment 5883255
Click to expand...
Click to collapse
Well, then I'm out of ideas. Maybe you should see what the seller's support can do.
Dear Experts,
I'm trying to rewrite lost IMEI after flashing stock rom (No backup). Tried everything in my sleeve. I am trying to find out how to enter in Meta mode so I can use the SN write tool or Modem meta. Tried following things:
adb reboot meta - nothing happening except reboot.
Vol button combo - nothing but fastboot and recovery.
Root - bootloader/oem can't be unlocked
Tried verity of tools nothing happening.
Brom mode - TP needs to be connected all the time (This is how I flashed the Rom).
Does any of you guys know how to activate Meta mode in this device. Seems nobody shared that detail over internet. Please help..
Thanks in advance.
eb60700 said:
Dear Experts,
I'm trying to rewrite lost IMEI after flashing stock rom (No backup). Tried everything in my sleeve. I am trying to find out how to enter in Meta mode so I can use the SN write tool or Modem meta. Tried following things:
adb reboot meta - nothing happening except reboot.
Vol button combo - nothing but fastboot and recovery.
Root - bootloader/oem can't be unlocked
Tried verity of tools nothing happening.
Brom mode - TP needs to be connected all the time (This is how I flashed the Rom).
Does any of you guys know how to activate Meta mode in this device. Seems nobody shared that detail over internet. Please help..
Thanks in advance.
Click to expand...
Click to collapse
Please head on to download the official tool
mvikrant97 said:
Please head on to download the official tool
Click to expand...
Click to collapse
I did it from the same website, but still not detecting.
eb60700 said:
I did it from the same website, but still not detecting.
Click to expand...
Click to collapse
Please make sure you have all the required drivers installed. If not please just install HMD Device Kit and it will install all the necessary drivers or you can manually install drivers from here.
Hi mvikrant97,
Sorry for the belated reply, I have installed HMD Device Kit drivers as per your link. but still its not detecting by Modem meta or SN Writer tool. While I connect the switched off phone this shows up in device manager.
{
"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"
}
Thanks for the helping hand mate.
eb60700 said:
Hi mvikrant97,
Sorry for the belated reply, I have installed HMD Device Kit drivers as per your link. but still its not detecting by Modem meta or SN Writer tool. While I connect the switched off phone this shows up in device manager.
View attachment 5822495
Thanks for the helping hand mate.
Click to expand...
Click to collapse
Were you able to connect device before when it was in working condition?
It also seems like the cable you are using is malfunctioned or the device USB port itself.
I'm sorry but I will have to ask you questions to diagnose the problem.
mvikrant97 said:
Were you able to connect device before when it was in working condition?
It also seems like the cable you are using is malfunctioned or the device USB port itself.
I'm sorry but I will have to ask you questions to diagnose the problem.
Click to expand...
Click to collapse
As I have mentioned before, I flashed this device with stock ROM using the same usb cable by triggering Test point in Brom Mode, So I highly doubt this is because of the faulty usb cable. Thereafter I lost my IMEI, but fortunately I had one IMEI noted down beforehand. I am trying to rewrite that IMEI so that I can use my SIM. Seriously what is this Meta Mode? This means nokia G10 doesn't support Meta Mode?
Please feel free to ask any question or suggestions mate.
eb60700 said:
As I have mentioned before, I flashed this device with stock ROM using the same usb cable by triggering Test point in Brom Mode, So I highly doubt this is because of the faulty usb cable. Thereafter I lost my IMEI, but fortunately I had one IMEI noted down beforehand. I am trying to rewrite that IMEI so that I can use my SIM. Seriously what is this Meta Mode? This means nokia G10 doesn't support Meta Mode?
Please feel free to ask any question or suggestions mate.
Click to expand...
Click to collapse
You will need Pandora Tool to fix up the IMEI.
But as much I know you need to have the backup beforehand to fix the issue.
You may refer to the video below
Thanks for the heads up. Looked up the tool, seems expensive than the G10 itself. Still wondering why the phone is not detected though.
eb60700 said:
Thanks for the heads up. Looked up the tool, seems expensive than the G10 itself. Still wondering why the phone is not detected though.
Click to expand...
Click to collapse
Maybe because the phone does not support Meta mode