Few days ago my device got bricked, when I press the power button it gives me a red light (2 times) when I plug it in to a wall charger, light keeps constant... I've charged the device for 12 + hours and then tried to reflash stock roms 4.1 and 4.3 (CE/AU/GE) using latest flash tool. It gives me an error at the end of processing System.sin. I changed data cables, try different pcs but nothing did work. Then I tried to update the phone using PC Companion but it didn't worked. Then someone told me to flash the files without System.sin using flashtool and then extract System.sin using 7zip and flash it using Fastboot software. (command line software) when I try to flash from there it says FAILED : File size is too large. Please help me out. I'm really pissed off right now because there are no sony care centers in our country. Someone please help me out. I really appreciate your help. Thanks loads :crying:
PS : I can unlock/relock bootloader.
Gihan Zami said:
Few days ago my device got bricked, when I press the power button it gives me a red light (2 times) when I plug it in to a wall charger, light keeps constant... I've charged the device for 12 + hours and then tried to reflash stock roms 4.1 and 4.3 (CE/AU/GE) using latest flash tool. It gives me an error at the end of processing System.sin. I changed data cables, try different pcs but nothing did work. Then I tried to update the phone using PC Companion but it didn't worked. Then someone told me to flash the files without System.sin using flashtool and then extract System.sin using 7zip and flash it using Fastboot software. (command line software) when I try to flash from there it says FAILED : File size is too large. Please help me out. I'm really pissed off right now because there are no sony care centers in our country. Someone please help me out. I really appreciate your help. Thanks loads :crying:
PS : I can unlock/relock bootloader.
Click to expand...
Click to collapse
If you wish this will take some quite amount of time. And above all theoretically constructed. But I do wish it could help you. Now lets get dirty!
REQUIREMENTS:
DoomLord's Advanced Stock Kernel
An unlocked bootloader!
Flashtool
A .ftf of your desired firmware
I am assuming your device is now capable of turning on (battery juice present).
Overview
You will create a flashable zip of the stock ROM with Flashtool. Afterwards flash it through recovery
Procedures
Whilst having a stock ftf in hand, follow MrSteve's handy guide on how to create a stock ROM .zip (Post doesn't tell you how to extract an ftf! Its easy, rename the file extension to .zip and extract the contents (.sins (lol)) to an another folder. If otherwise your zip manager support ftf extraction, then proceed on your own method)
Flash DoomLord's kernel via fastboot in flashtool
Connect your phone in fastboot mode (hold down vol up while device is powered off then connect to your computer. you can release vol button once phone is detected)
Flash DoomLord's advanced kernel by selecting the Lightning icon in the toolbar, select Fastboot mode, then select "Select Kernel to Flash". Navigate to and choose your downloaded DoomLord's kernel
Unplug your phone upon completion.
Turn the phone on, while on LED light, press volume up key repeatedly until your phone gets into recovery.
Wipe your phone clean! Please wipe /system, /data, /cache and dalvik. You are encouraged to also factory reset through the recovery.
Flash your self-made stock zip.
Reboot and lots of prays
Thank you so much, I followed your instructions and managed to flash it... Then I got offline charging error. Then I relocked my bootloader and and flashed stock rom 4.3. It flashed... Now phone works but offline charging is not working. Any solution :crying:
Gihan Zami said:
Thank you so much, I followed your instructions and managed to flash it... Then I got offline charging error. Then I relocked my bootloader and and flashed stock rom 4.3. It flashed... Now phone works but offline charging is not working. Any solution :crying:
Click to expand...
Click to collapse
Have you tried specifically flashed stock ROM through flashtool after successfully flashed the zip you created earlier? In fact this problem shouldn't happen. And from what I remember, this might have to do with Kernel.
Please flash again the stock ftf. If is still fails, please get me to know it. You can untick DATA APP etc under the WIPE section in Flashtool when you are selecting a firmware. This will preserve your data and everything.
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!
I tried to root with sp flash tool . While opening recovery mode by pressing vol up and down it is not even switching on. It is saying tool dll failed. Some help me
lol no replies till now
I faced the same issue. Just flash the stock rom with sp flash tool, important dont forget to Check Da All Sum in Options Tab. After flashing your phone will be booted normally, and then if you wish, you could change your rom..
Hi everybody
I need to find an update.zip to flash it on stock recovery and attempt to repair the phone system.
Long story short..
I restore my D415 (previously with Lineage 14.1) to stock firmware (KK) via KDZ file and LG flash tool, then update it to LP with LG Mobile Support Tool and everything was good, then i tried to root the device with the LG OneClick Root (which i used several times before to root my phone without problems) but i don't know what happened during the batch process and now Download Mode has been replaced with Fastboot mode and the device hangs on the T-Mobile startup screen, so i can't flash a KDZ file again to restore the phone without a Downlaod Mode. The fastboot mode throws "remote: unknown command" with every command i tried (except fastboot getvar all; which shows "unlocked: no") even reboot doesn't work.
Tried everything even booting on Qualcomm Qdload mode (shorting the phone with test points) to reflash the firmware files but couldn't succeed because QFIL, QPST Software Downloader and BoardDiag they all threw errors.
I can access the stock recovery mode by pressing home button when the "erasing" screen appears after selecting "yes" on factory reset menu, so i need an official update to try to fix this phone, don't know if its gonna work or if this is a hardware issue but at least i want to try. Buying a new one is very difficult for me right now.
Thanks for any help.
Hi all, I've had a few problems so I've downloaded miflash tool but I need some help using it.
When I start the program it pops up flash script not found. So when I try to flash the phone it just gives me a error.
Any ideas what I'm doing wrong? All I think it could be is when mi flash first starts it opens a driver window. I click on and it hangs a bit and pops up a window with something in Chinese in it?
The selected firmware folder is not a fastboot firmware folder. For the miflash to be able to flash a firmware, it must be in fastboot format.
Regarding the driver popup window, it's somehow a problem with older versions.
Try and use this one http://www.mediafire.com/file/a6gpxjwi9jgpjsp/MiFlash20191206.zip/file
It worked for me.