this is regarding the NAND flash of x1
after loading the LK loader, den my mobile restarted
it loads,
then it stops with this
ENTERING FASTBOOT MODE
fastboot_init<>
starting_usb<>
udc_start<>
den nothing will happen,
whats the remedy for this
Everything is all right
Now you have do install the fastboot binarys on your computer.
Then you have to put the boot.img on your device
just follow these steps or this
still it doesnt work, i have run the recovery img, my device cant be detected
llycester said:
still it doesnt work, i have run the recovery img, my device cant be detected
Click to expand...
Click to collapse
you have to install the usb driver of your x1 in computer, before flash recovery.img
you can use a kind of pc-side android management software, in China we got a soft. named iMolo, which can detect the device n install the driver automatically.
good luck
So I think i did something stupid.
I was trying to get MIUI working see (http://forum.xda-developers.com/showpost.php?p=58366462&postcount=159).
Changed the kernel modules and firmware of the rom but I kept aboot.bin to be flashed to my device.
MIUI didnt boot just black screen.
Used TWRP to recovery my system/boot and so on.
Phone still doesnt boot screen black.
I put the device in boot mode but my laptop doesnt detect a usb device. Neither in windows or linux (lsusb).
So I cant manage to use FashBoot none of the versions. I downloaded the tot and the kdz. But without my device being detect I cant do anything with it.
Is there another way to get stock back?
* Edit:
So I figured I look a bit into the G2 forums to find for solutions.
I discovered if i erase my boot partition dd if=/dev/zero of=boot
The devices automaticly boots in fastboot mode.
From fastboot mode i managed to flash to correct aboot.img again and after that boot mode worked again.
grimpy said:
So I think i did something stupid.
I was trying to get MIUI working see (http://forum.xda-developers.com/showpost.php?p=58366462&postcount=159).
Changed the kernel modules and firmware of the rom but I kept aboot.bin to be flashed to my device.
MIUI didnt boot just black screen.
Used TWRP to recovery my system/boot and so on.
Phone still doesnt boot screen black.
I put the device in boot mode but my laptop doesnt detect a usb device. Neither in windows or linux (lsusb).
So I cant manage to use FashBoot none of the versions. I downloaded the tot and the kdz. But without my device being detect I cant do anything with it.
Is there another way to get stock back?
* Edit:
So I figured I look a bit into the G2 forums to find for solutions.
I discovered if i erase my boot partition dd if=/dev/zero of=boot
The devices automaticly boots in fastboot mode.
From fastboot mode i managed to flash to correct aboot.img again and after that boot mode worked again.
Click to expand...
Click to collapse
Glad you're sorted & posted the solution.
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!
My Lenovo K3 note bricked and now it boots up to spash logo and says dl image error or something. Downloaded the stock rom and tried the spflash tool but it doesnt seems to work. Please help.
e
Download the rom and tool from here- https://www.youtube.com/watch?v=mzN1q0h_YKM&ab_channel=Techjunkie
Hey,
I just uploaded BAD stuff from a BAD folder ...
preloader
ik
logo
secro
system
userdata
No life whatsoever. Tried as I realized after flash is done that I did a big fail to go into recovery (vol + & - & power) but nothing.
Even SPFlashtool is not seeing the phone nor adb.
Please help me unbricking this brand new phone.
/I wanted to make it full Hungarian language.../
I did the same. I tried to install another rom the tool and flash my phone died.
I did the firmware backup and now I am unable to restore the file Scatter.bin by Droid Tools.
I must have firmware.bat file but it was excluded.
someone could help me with this file. if there is a site to download and there is no way to reverse this? Please help me solve. Thank you
Do this
First Sorry for my Bad English
Try to do these steps:
Install all the drivers (including lephone and others)
Open Device Manager on Windows PC
Now plug in your SWITCHED OFF
And notice the hardaware changes
If you find a hardware named "MTK 675XXX Preloader" or something like that, then your mobile can be easily unbricked
if you notice a small triangle under it then the preloader drivers might not be installed
just click on it (be fast because it will only stay for a 10 seconds or less)
and click "Update Driver"
Now, Try to flash using SPF tools
If the above method dosent work then try to boot into bootloader. if not able, then YES, YOU HAVE HARD BRICKED YOUR PHONE
https://imgur.com/GXUGtPd
i got this screen
Im trying to flash the stock ww rom to my rog 2 , but does not start for some reason
the phone stays in the asus logo , does not boot , so i cannot enable or disable USB debugging
I had root , magisk and unlocked bootloader , i done a factory reset in the recovery , and now my phone does not start
i can get to the fastboot mode , connect the cable to the side port , win 10 does make a sound when connecting the cable
i copied the raw file folder to the root of C drive , double click on the flashall_AFT and does nothing
i need help plz.
You have a log file in the same folder. Post the content here.
You won't see any progress in the command line window. Only the flashboot log file
joluke said:
You won't see any progress in the command line window. Only the flashboot log file
Click to expand...
Click to collapse
hi , i did some research and found out i didnt had the asus bootloader drivers installed on my pc, all good now , managed to flash the raw file to the phone