Hi friends , i really need some help here
my device have no system/kernel now .. i've been trying to flash a kernel via fastboot but it always tells ( failed - remote : command not allowed )
as for flashtool .. whenever i try to boot into download mode the led turns red then green in a second then disconnects it self by only booting to sony logo .. even tried to charge thinking it's only a charging problem .. but it won't even show the charging animation , do you know how to fastboot flash kernel successfully , ps : am not a noob , just haven't done this for a long time studying high-school .. means you can ask me anything about the process . am on LB BTW
really need your much awaited halp !
and what is it required to fastboot or flashtool ? could be a wrong drivers issue ? , i alredy tried two drivers !
more about the problem .. i was flashing eXistenz 5 black and its superuser fix , which was done successfully then i had to flash a kernel via flashtool which didn't go well , i thought it's because i forgot to check usb-debbuging of dev-option so i had ( deleted data / cache to flash a new rom , tells the cwm recovery ) to flash the eXistenz 4 back , which had formated the whole system/data/cache and everything .. and ever since it won't fastboot or flashtools or even recover into recovery as the kernel should be deleted ! i think the device is gone heart-attack as dead !
Edit : flashtool needs usb-debbuging on which in my case is not
am left with fastboot to flash a kernel and have a recovery , would someone please at least try to help ! ?
Related
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Don't worry have you backup you data?
if you have, just install the driver for qhusb
then your phone should be able to recognises by MIflash then flash any fastboot rom, You phone should be good to go.
I had a similar issue but i tried to hold the power button for like 30 seconds and the phone booted. If it didn't work, you should follow this thread: en.miui.com/forum.php?mod=viewthread&tid=73348&highlight=Mi3%2Bunbrick&mobile=no
partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone
murattiy said:
partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone
Click to expand...
Click to collapse
Did you personally tried that? Because flash all bat do uses fastboot to flash, which can't be accessed.
I wonder whether the other one u poster doesn't use fastboot, cant check the file content atm
I have tried many times
last times tried 3 hours ago, for alpha 5.12.24
my video under explain
http://m.youtube.com/watch?v=fSl9xrR_J4g
@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol
you need to do İnstall spacial flash_all.batt change to in flash_all.batt "cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global"
dont use miFlash .. enough u clik speical flash_all.batt
If your device not boot into fastboot/recovery mode press power button for around 30-40 seconds .
and still not boot into fastboot/recovery mode
battery cable exist than try.. i tried many times))
Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?
Prince Chandela said:
From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
coolkillermax said:
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
Click to expand...
Click to collapse
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?
回复: Bricked Mi3 - Showing QHUSUB Bulk in PC
Prince Chandela said:
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?
Click to expand...
Click to collapse
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4
coolkillermax said:
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4
Click to expand...
Click to collapse
flash miui fastboot rom then
Prince Chandela said:
flash miui fastboot rom then
Click to expand...
Click to collapse
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking
coolkillermax said:
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking
Click to expand...
Click to collapse
can you boot in recovery now?
Prince Chandela said:
can you boot in recovery now?
Click to expand...
Click to collapse
No...
http://forum.xda-developers.com/xiaomi-mi-3/help/mi3w-lost-partition-userdata-img-t3293583
Me_Ashish_ said:
@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol
Click to expand...
Click to collapse
Really need your help..
Can you explain it further?
please..
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
EDIT: Sorry, I post on the wrong section. If someone can move this post on the right section ...
gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
try to use QPST (Qfil) method. This is final method can bring back your phone. If fail, congratulation ! :silly:
I success with QFIL Zui works but it's awful
Unfortunately, I try to install stock cos but I have the same issue.... Bootloop after "App update message".
I don't know why
Try flashing Cyanogen Os using fastboot
I did that...
I flash with the tool via fastboot. But bootloop result...
I also tried to flash CM13 via TWRP but I have an error message...
Do you have any other solutions?
I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice
Here u go, QFIL CM 12 ROM: https://mega.nz/#!RFUw2CbZ!GXS6KeOy_8n2y_rOBJUS5WJSP5kchODcGUF0U1TxYO8
So with the ham version is the same as the QFIL version?
gaara19 said:
I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice
Click to expand...
Click to collapse
READ THIS( use google translate)
BTW, what are the fastboot commands that you are using?
dear friends I am happy to be in this wonderful forum ,,,
i try to root the M android but i get the phone in boot loop , i can asses twrp and fastboot , i try to flash system.img from fastboot but i get always cannot load system.img i try to use official recovery via volume and power button but also i get error massage , why fastboot flash is not working ??? any solution ???
i have found solution
please share your solution. thanks.
found a solution-share it....
tania.k said:
dear friends I am happy to be in this wonderful forum ,,,
i try to root the M android but i get the phone in boot loop , i can asses twrp and fastboot , i try to flash system.img from fastboot but i get always cannot load system.img i try to use official recovery via volume and power button but also i get error massage , why fastboot flash is not working ??? any solution ???
i have found solution :--- but hey... why wont you share it ?
Click to expand...
Click to collapse
Friends i unlocked my bootloader, the oficial way... I had the root, twrp... And i flashed a new rom. Ressurection Marshmellow... the 6.0 android. But it was a bad choice for me because it feelt laggy and ok...
I flashed a lollipop after that ... so i used it a few days, until i noticed that there was another 6.0 rom that i didnt tested. So i wanted to flash it... but, i lost the twrp.. it was booting recovery in CYANOGENMOD Recovery, not twrp, and it didnt worked the isnstall from sd card. So ... i noticed that i lost my root too... and when i tried to king root it said no strategy and failed...
I dont know why i tried to root it on flashtool, following a video tutorial that this guy flashed a new kernel... so i did the same... but... after turning on my z1 .. its stuck on SONY LOGO
PC COMPANION wont work saying that i made some changes on the phone and couldnt repair...
I am so... so lost....
I need to restart again.... but i dont know FROM WHERE... i think im still with my bootloader unlocked... HELP GUYS
- Use Androxyde's Flashtool to flash original firmware ftf. Did you make a backup of TA partition? If so, restore it first. If not flash ftf.
Tool: https://github.com/Androxyde/Flashtool
For files use XperiFirm to download latest firmware or check this thread: http://forum.xda-developers.com/showthread.php?t=2469191
or
- Enter fastboot mode (turn off then vol up + plug usb cable) and then open up cmd or terminal and type fastboot flash recovery twrp-3.0.2-0-honami.img. On Ubuntu it is sudo fastboot flash recovery twrp-3.0.2-0-honami.img
Download twrp from: https://dl.twrp.me/honami/
Then enter your recovery by holding power+vol up together and flash zip of your choice. You can mount your device and then copy files.
solved
Friend, somehow i could fix, i plugged my usb on my pc, power my z1 + volume up... i got into the fastboot mode , the blue light were on... so i used the fastboot to instal twrp recover again.... i could flash the rom again.
edit:
AHAHAHA You saved my life because you said the right thing that i had to do... I thank you more!!
Thank you anyway!!!
LinkRaf said:
Friend, somehow i could fix, i plugged my usb on my pc, power my z1 + volume up... i got into the fastboot mode , the blue light were on... so i used the fastboot to instal twrp recover again.... i could flash the rom again.
edit:
AHAHAHA You saved my life because you said the right thing that i had to do... I thank you more!!
Thank you anyway!!!
Click to expand...
Click to collapse
Use the Thanks Button... And press it a few times :banghead:
Here, let me do it for u too
-----------------------------------------------------
Tapatalked from Sony Xperia Z1
Stock LP 5.1.1 | Root | Deodex | Cam Mods | MX ROM
try with fashtool and rom stock
Hi guys my new victim is Alcatel 1 5033f (1/16).
1. I had opened the bootloader with a pc tool but I didnot think about dm verity... so my phone first going in orange state, with 5sec warning. (i was have fastboot....then)
2 I have tried remove the warning with "lk.bin flashing in fastboot" It wasnot succesful I made some mistakes because my screen is shows only lines... and no fastboot its allways rebooting after a few seconds.
After this I try to restore with sp flash tool, but I didnot finded EXACTLY this rom. Somebody told me that 5033a is also good then I downloaded all necessary files and try to flash but I allways have a "brom cmd fail 00003 and I cant do.
I started this project without any overthinking off course I didnot made any backup.
So I know this is a cheap phone but new... can somebody help me in sp flash progress?
MrWienerberger(brick) said:
Hi guys my new victim is Alcatel 1 5033f (1/16).
1. I had opened the bootloader with a pc tool but I didnot think about dm verity... so my phone first going in orange state, with 5sec warning. (i was have fastboot....then)
2 I have tried remove the warning with "lk.bin flashing in fastboot" It wasnot succesful I made some mistakes because my screen is shows only lines... and no fastboot its allways rebooting after a few seconds.
After this I try to restore with sp flash tool, but I didnot finded EXACTLY this rom. Somebody told me that 5033a is also good then I downloaded all necessary files and try to flash but I allways have a "brom cmd fail 00003 and I cant do.
I started this project without any overthinking off course I didnot made any backup.
So I know this is a cheap phone but new... can somebody help me in sp flash progress?
Click to expand...
Click to collapse
Hi, did you make any progress? I also have Alcatel 1 5033F with vRB3V (11-04) ROM. If you can advise how to make the backup of the ROM, I can send it to you.