Related
hi everyone,
i am having a really bad day.
I had incredible s stock 4.0.4 installed, unlocked, s-on, hboot 2.002
I've tried to download the latest 4.4.2 rom i found in the forum, the device showed the update is completed, then the device restarted and froze on HTC screen.
I've tried to install other roms and it didn't work as well, moreover, the device can not be detected by pc without a reason.
I've cleared all caches by the way.. any one can help !
install this Hboot
[/COLOR]http://forum.xda-developers.com/showthread.php?t=1270589
OR
flash boot manual
what if my USB slot is broken into my pc, can i do this using an SD card?
micho119 said:
what if my USB slot is broken into my pc, can i do this using an SD card?
Click to expand...
Click to collapse
No.
072665995 said:
No.
Click to expand...
Click to collapse
Since you are telling device is not detected in PC,
I can safely assume that you are not flashing boot.img through fastboot from PC.
If you are S-ON, you need to flash boot.img file of ROM you want to install through fastboot command...
fastboot flash boot boot.img
google it for more info.
And connect your phone, go to fastboot mode and check with command
fastboot devices
your device should be listed in fastboot mode
and if still not detecting by PC, then must be driver issue and it should have nothing to do with phone.
RmatriX1218 said:
Since you are telling device is not detected in PC,
I can safely assume that you are not flashing boot.img through fastboot from PC.
If you are S-ON, you need to flash boot.img file of ROM you want to install through fastboot command...
fastboot flash boot boot.img
google it for more info.
And connect your phone, go to fastboot mode and check with command
fastboot devices
your device should be listed in fastboot mode
and if still not detecting by PC, then must be driver issue and it should have nothing to do with phone.
Click to expand...
Click to collapse
I just reread his post. Then reread yours. And I realized that the other guy's post doesn't really make much sense. I don't know if he is saying if his computer's USB port is broken. If so then use another one. Then I could also read it as His phone's USB port is broken, and in that case, he really is out of luck.
072665995 said:
I just reread his post. Then reread yours. And I realized that the other guy's post doesn't really make much sense. I don't know if he is saying if his computer's USB port is broken. If so then use another one. Then I could also read it as His phone's USB port is broken, and in that case, he really is out of luck.
Click to expand...
Click to collapse
Hey, lt's lot of guess work here and we need to hear from actual victim...
but let me put my basis..
from 1st post, I can assume that he doesn't know of fact that he need to flash boot image through fastboot.
Hence, I believe that he may even doesn't know what if fastboot.
And without any ROM installed, device can only be detected in fastboot.
So, I strongly believe, he need to try to detect device in fastboot mode and very less chances USB is broken.
Now lets wait to hear from OP guy.
in htc sunsation 4ext recovery there is a way to flash boot.img
try it :
1- go to 4ext recovery
2- select Tools
3- the last one is ( enable smart flash)>> click it once then flash ROM
I don't know if our 4ext recovery support this feature or not
yep. because this is development and all that.
I have a problem with my phone ... i unlocked bootloader,flashed boot.img via fastboot, installed custom rom.
Then i installed windows 10 on my pc and when i try to install adb fastboot drivers,i turn off phone,press power + volume up,light turns blue but after that it skip to Sony logo screen and device is on after. So my problem is i can't put my phone in fastboot mode.. I did it in past, a few times when i tried several custom room and needed to flash img via fastboot,but now it seems it won't work. Anyone know how to solve this?
VladHD said:
I have a problem with my phone ... i unlocked bootloader,flashed boot.img via fastboot, installed custom rom.
Then i installed windows 10 on my pc and when i try to install adb fastboot drivers,i turn off phone,press power + volume up,light turns blue but after that it skip to Sony logo screen and device is on after. So my problem is i can't put my phone in fastboot mode.. I did it in past, a few times when i tried several custom room and needed to flash img via fastboot,but now it seems it won't work. Anyone know how to solve this?
Click to expand...
Click to collapse
1. Disable driver signature verification.
2. Reinstall adb fastboot drivers
Yeah ... i did that again and now is working ... dunno what was the problem from the begging. Thanks
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:
id start with a flash all of the latest stock firmware to clean it up. then start over
edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:
Anyone?
vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699
I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.
Hello guys. I accidentally wiped out my xiaomi mi 5 including the internal storage from TWRP . Whenever I try to connect phone to PC through fast boot mode , device redirects to TWRP .
Also , another issue I'm encountering is that my device, despite using numerous USB c cables , doesn't get recognized by my PC, I've even tried a different system still the same issue .
Therefore , with the PC not detecting my phone , and no USB otg being detected by TWRP ,I'm not able to copy rom into internal storage and hence I'm doomed and helpless . I've tried everything I could , adb fastboot miflash , but no solution for me.
It will be so nice of any of you to guide me and help me with this situation . Thank you
Try to connect it on different PC ? Unistall all drivers and see if PC detects it in fastboot mode ? Maybe see if charging port is damaged ? Sometimes data pins has some issues.
If nothing works, you need to open up your phone and short boot point, which will make it go in Qualcomm 9001 mode, I am not sure which mode is in mi5, could be edl. You can find videos on YouTube, and 4pda mi5 forum has details guide, but it's Russian you need to use Google translate.
https://in.c.mi.com/thread-387857-1-0.html
I found this link , please check it and let me know that is this how I should do it ?
About that you mentioned before , I have tried 3 different devices for this phone and none of them detects the device , although I have windows running in macbook I havent tried on that. Thank you
mi tool v2
Xiaomi mi tool v2
xiaomitool com V2
try the tool worked for me.
last solution would be adb.i hope you have a good cable
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash cache cache.img
-fastboot flash modem NON-HLOS.bin
-fastboot flash sbl1 sbl1.mbn
-fastboot flash dbi sdi.mbn
-fastboot flash aboot emmc_appsboot.mbn
-fastboot flash rpm rpm.mbn
-fastboot flash tz tz.mbn
-fastboot flash LOGO logo.bin
-fastboot reboot
something like that ^
eddieim3000 said:
Xiaomi mi tool v2
xiaomitool com V2
try the tool worked for me.
last solution would be adb.i hope you have a good cable
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash cache cache.img
-fastboot flash modem NON-HLOS.bin
-fastboot flash sbl1 sbl1.mbn
-fastboot flash dbi sdi.mbn
-fastboot flash aboot emmc_appsboot.mbn
-fastboot flash rpm rpm.mbn
-fastboot flash tz tz.mbn
-fastboot flash LOGO logo.bin
-fastboot reboot
something like that ^
Click to expand...
Click to collapse
The thing is whenever I connect the phone to my computer , it isn't recognized. It doesn't show up on device manager and first and foremost, it doesn't make the *ping* sound whenever a new device is connected.
So I'm not sure whether mitool will work although I'll give it a try .
I've already tried adb with nice cables (samsung). Since my problem is that it doesn't get detected , so adb is already no use
Flash rom via otg. Thats all
ali.f said:
Flash rom via otg. Thats all
Click to expand...
Click to collapse
Otg not detecting on twrp. From the instructions I was supposed to go to mount > select USB otg but it doesn't get selected and even after connecting the otg , it shows 0MB .
I even bought another otg just to make sure
try to flash zip with adb sideload method ? i dont know in your sitution but i use this method often when i wanna clean flash in my device. sorry maybe it cant help you but i just want to help you.
burakmi5 said:
try to flash zip with adb sideload method ? i dont know in your sitution but i use this method often when i wanna clean flash in my device. sorry maybe it cant help you but i just want to help you.
Click to expand...
Click to collapse
Thanks , but since I cant get to see my device on PC, so doing it through adb sideload doesn't even come near
What did yo do with your phone? I had same problem before. I try to switch to f2fs, cache and data only. I lost verything. And i revert back to ext4. Lucky me i still can flash rom using otg.
ali.f said:
What did yo do with your phone? I had same problem before. I try to switch to f2fs, cache and data only. I lost verything. And i revert back to ext4. Lucky me i still can flash rom using otg.
Click to expand...
Click to collapse
I wanted to install a new rom , and without taking a backup I wiped out everything before even copying the rom . Honestly I dont know what's causing this , before the wipe my otg was always working in twrp. Is it because of the twrp ; I use zcx twrp 3.0.2 by XM (while booting to twrp it shows an alien logo)
Thats the problem. Any chance you replace your twrp to official twrp?
ali.f said:
Thats the problem. Any chance you replace your twrp to official twrp?
Click to expand...
Click to collapse
Can you guide me ? I'm not able to copy anything into the mobile.
mirzaarslaan said:
The thing is whenever I connect the phone to my computer , it isn't recognized. It doesn't show up on device manager and first and foremost, it doesn't make the *ping* sound whenever a new device is connected.
So I'm not sure whether mitool will work although I'll give it a try .
I've already tried adb with nice cables (samsung). Since my problem is that it doesn't get detected , so adb is already no use
Click to expand...
Click to collapse
Firstly samsung most likely wont give you a good data cable.i meant a edl cable .i should have said so .doesnt matter if windows shows it or not.launch cmd as admin and try to flash something... fastboot flash recovery recovery.img .does it take any time at all or doesnt do anything?try an other cable if nothing s happening
eddieim3000 said:
Firstly samsung most likely wont give you a good data cable.i meant a edl cable .i should have said so .doesnt matter if windows shows it or not.launch cmd as admin and try to flash something... fastboot flash recovery recovery.img .does it take any time at all or doesnt do anything?try an other cable if nothing s happening
Click to expand...
Click to collapse
I never got the idea of using edl cable. I'm probably gonna make my own edl cable by following online and then let's see. I really hope this does the trick
eddieim3000 said:
Firstly samsung most likely wont give you a good data cable.i meant a edl cable .i should have said so .doesnt matter if windows shows it or not.launch cmd as admin and try to flash something... fastboot flash recovery recovery.img .does it take any time at all or doesnt do anything?try an other cable if nothing s happening
Click to expand...
Click to collapse
I wanted to give an update. I tried the test point method and it didn't work . The device isn't detecting on my PC
sunilromy said:
Try to connect it on different PC ? Unistall all drivers and see if PC detects it in fastboot mode ? Maybe see if charging port is damaged ? Sometimes data pins has some issues.
If nothing works, you need to open up your phone and short boot point, which will make it go in Qualcomm 9001 mode, I am not sure which mode is in mi5, could be edl. You can find videos on YouTube, and 4pda mi5 forum has details guide, but it's Russian you need to use Google translate.
Click to expand...
Click to collapse
Nothing worked for me . I even opened up my phone and did the short boot point , after 5 seconds or so , it goes to charging. Can it be that i should get a new usb c port or is it time to put an end to this dead phone :/
mirzaarslaan said:
I wanted to give an update. I tried the test point method and it didn't work . The device isn't detecting on my PC
Click to expand...
Click to collapse
1 windows 10 are in test mode
2 xiaomi tool is installed
3 exit aps like bluestacks
4 you have a good data cable
5 you have adb and in the same folder unpacked the recovery.
6 power and volume - to enter fastboot mode
fastboot flash recovery recovery.img
try to flash the recovery even its not recognized at the time.does it take any time at all ?or does it just waits ?
eddieim3000 said:
1 windows 10 are in test mode
2 xiaomi tool is installed
3 exit aps like bluestacks
4 you have a good data cable
5 you have adb and in the same folder unpacked the recovery.
6 power and volume - to enter fastboot mode
fastboot flash recovery recovery.img
try to flash the recovery even its not recognized at the time.does it take any time at all ?or does it just waits ?
Click to expand...
Click to collapse
Is it necessary to enable test mode , my PC is not allowing test mode to be enabled.
Although what you've mentioned , I have already tried , when I run the command flash recovery.img it says 'waiting for any device' and within 15 seconds , phone reboots to charging mode with a battery logo
mirzaarslaan said:
Is it necessary to enable test mode , my PC is not allowing test mode to be enabled.
Although what you've mentioned , I have already tried , when I run the command flash recovery.img it says 'waiting for any device' and within 15 seconds , phone reboots to charging mode with a battery logo
Click to expand...
Click to collapse
without test mode you can not install xiaomi tools2 therefore no correct drivers
cmd run as admin
bcdedit -set TESTSIGNING on
restart