Hello everyone, a couple of months now are also thanks to you in the world of modding. Yesterday (i have a Xiaomi Mi A2 Lite) during the installation of a custom ROM using ADB, typing in the fastboot command "erase system", I wrote erase a_boot for error because before I was reading a post about it and I wrote it. Yes I know, I was too stupid. Result? The phone does not start up either in recovery or in fastboot mode, and from the PC it is recognized as COM port. I have already documented about it and tried to flash everything with the Qualcomm tool after installing the drivers but nothing. I tried the EDL by activating it manually to unlock port 9008, but still during the flash gives me error. I tried everything, do it all over again in a newly formatted and clean PC from any other driver, but nothing. During the flash, even if I put the firmware in the same directory, it still gives me error. Guys I'm desperate please. I do not know what else to do. I hope to receive your answers :crying::crying::crying:
I also have same problem.. if you find some solution then tell me also.. my device is different.. but problem is same.. device basically dead & can be recognised in com port
Related
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
Hello Guys!
I was trying to go with a Custom Rom (Cynogen 12.1) on my Xiaomi Mi4i device. Rooted the phone and also installed TWRP recovery. Got everything like Rom Zip file and GApps on the device including a special file recommended for Miui 7 users. Then I tried to flash them after factory resetting from TWRP recovery. The special file (dont know what it is called) was flashed successfully everytime..but when flashing Rom file...it failed showing "Unable to extract zip".
So I tried again..and quite a few times more but it always failed. Therefore, instead of Factory Resetting...I went to Advanced reset...And ended up in SOFT BRICK of the device accidently removing everything.
But this is not the end...I knew how to repair a soft bricked Device. So, I went for MiFlash...But in that...instead of Mi4i fastboot rom...I flashed Mi4 fastboot rom..and this resulted in HARD BRICK of my device. Now, it doesnt show any thing...No notification light when charging...Not entering fastboot mode..nothing.
So, I tried a few ways..to repair my hard bricked device..but none of them worked. When I initially connected it to my PC it showed "Qualcomm HS-USB Diagnostic 9008" in the PORT section of Device Manager and Showed as COM11 in MiFlash...but when flashed it showed error "End of code" or something like this. So, I restarted My PC...But since then WINDOWS is showing error "Unable to recognise device (Code 43). I have tried many things but none of them seems to work as PC is not detecting the Connection.
So... Plz..help...Get Me out of this...I want to see my Mi4i alive again...
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
privateriem said:
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
Click to expand...
Click to collapse
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : https://www.androidfilehost.com/?fid=24591000424940129
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
HParra97 said:
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : snip
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
Click to expand...
Click to collapse
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
privateriem said:
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
Click to expand...
Click to collapse
Read this thread : http://en.miui.com/thread-91415-1-1.html
Make sure that you've disabled driver verification signature, your path to the image folder does not contain any spaces, and also the flash all data except data and storage option.
Hello, I have the mentioned phone, a few days ago it went into brick mode( stuck in boot screen ).
So I proceed to flash it, everything seems ok but this time the phone it's not recognized in fastboot mode
I spent the whole day yesterday trying to find a solution, I think it's because of the drivers(maybe).
If I open the fastboot option while having it pluged in, the flash tool recognizes it just for a second when it's loading the fastboot and then it won't recognize it again.
Shown in this recording: streamable . com/1v0kt
I used this tutorial for ZTE Blade A452 (delete spaces) :
getdroidtips . com/stock-rom-zte-blade-a452/
I used the same tools and files the guide has, I tried downloading many drivers for A452 but none made any diference.
I don't know if I'm doing something else wrong.
I'd appreciate any help, thanks
After installing some roms I decided to flash the stock rom using Mi flash tool, but the flash tool gave many errors, I tried many times to flash it, and then I decided to reboot the phone in fastboot mode to see if that solved something, but from that moment the phone did not turn on again, and it did not enter fastboot or recovery mode.
After a moment I connected the phone to the pc and saw that a device appeared "Qualcomm HS-USB QDLoader 9008".
Then I looked for solutions on the internet and when I tried some of those solutions, I realized that the flash tool sometimes when I clicked the "flash" button did nothing, when you clicked it again it showed errors, but if you clicked the "flash" button and then the "refresh" button the flashing progress appeared, so I thought that's why my redmi note 10 was hard bricked, because I closed many times the flash tool when it was flashing.
I thank you in advance for any help. Any idea how to fix it?
ajanco said:
After installing some roms I decided to flash the stock rom using Mi flash tool, but the flash tool gave many errors, I tried many times to flash it, and then I decided to reboot the phone in fastboot mode to see if that solved something, but from that moment the phone did not turn on again, and it did not enter fastboot or recovery mode.
After a moment I connected the phone to the pc and saw that a device appeared "Qualcomm HS-USB QDLoader 9008".
Then I looked for solutions on the internet and when I tried some of those solutions, I realized that the flash tool sometimes when I clicked the "flash" button did nothing, when you clicked it again it showed errors, but if you clicked the "flash" button and then the "refresh" button the flashing progress appeared, so I thought that's why my redmi note 10 was hard bricked, because I closed many times the flash tool when it was flashing.
I thank you in advance for any help. Any idea how to fix it?
Click to expand...
Click to collapse
have to get someone with authorized account to fix it using edl flash tool, from next time dont use miflash and just extreact the rom zip and flash it with the bat file.
ajanco said:
After installing some roms I decided to flash the stock rom using Mi flash tool, but the flash tool gave many errors, I tried many times to flash it, and then I decided to reboot the phone in fastboot mode to see if that solved something, but from that moment the phone did not turn on again, and it did not enter fastboot or recovery mode.
After a moment I connected the phone to the pc and saw that a device appeared "Qualcomm HS-USB QDLoader 9008".
Then I looked for solutions on the internet and when I tried some of those solutions, I realized that the flash tool sometimes when I clicked the "flash" button did nothing, when you clicked it again it showed errors, but if you clicked the "flash" button and then the "refresh" button the flashing progress appeared, so I thought that's why my redmi note 10 was hard bricked, because I closed many times the flash tool when it was flashing.
I thank you in advance for any help. Any idea how to fix it?
Click to expand...
Click to collapse
hey
I brought mi phone for my aunt and she is facing similar issues too. If you find any solutions do let me know.
ScarletSkies1234 said:
have to get someone with authorized account to fix it using edl flash tool, from next time dont use miflash and just extreact the rom zip and flash it with the bat file.
Click to expand...
Click to collapse
Yes, today, I have been looking for solutions and I see that paying someone with authorized account is the only way to get my phone back. :C ....I didn't know you could flash without the Mi flash tool, thanks, I will try in the future....
msgranger12 said:
hey
I brought mi phone for my aunt and she is facing similar issues too. If you find any solutions do let me know.
Click to expand...
Click to collapse
Hi, I told you that I fixed my phone with the "Xiaomi Pro Tool" (it's paid but cheap). Good luck!
ajanco said:
Yes, today, I have been looking for solutions and I see that paying someone with authorized account is the only way to get my phone back. :C ....I didn't know you could flash without the Mi flash tool, thanks, I will try in the future....
Click to expand...
Click to collapse
My friend tried to flash fastboot image using official android platform tools from google, build march 2022, it didn't work. Always failed when flashing the super partition. Fortunately, he decided to flash it with mi flash build 2020 (forgot which one), and it succeeded. I didn't believe it at first. Weird indeed. I believe xiaomi put something else to their fastboot binary in the mi flash.
ajanco said:
After installing some roms I decided to flash the stock rom using Mi flash tool, but the flash tool gave many errors, I tried many times to flash it, and then I decided to reboot the phone in fastboot mode to see if that solved something, but from that moment the phone did not turn on again, and it did not enter fastboot or recovery mode.
After a moment I connected the phone to the pc and saw that a device appeared "Qualcomm HS-USB QDLoader 9008".
Then I looked for solutions on the internet and when I tried some of those solutions, I realized that the flash tool sometimes when I clicked the "flash" button did nothing, when you clicked it again it showed errors, but if you clicked the "flash" button and then the "refresh" button the flashing progress appeared, so I thought that's why my redmi note 10 was hard bricked, because I closed many times the flash tool when it was flashing.
I thank you in advance for any help. Any idea how to fix it?
Click to expand...
Click to collapse
Xiaomi Flash tool support EDL flashing too...try this version....and also install the Qualcomm driver.