Related
im having trouble trying to root my phone again after it crashed and had to start from beginning. When i try fastboot flash boot Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img it gives me fails and says FAILED <Remote: command not allowed> does any body know what im doing wrong? I managed to root it teh first time no problem.
Cheers
sturtz1987 said:
im having trouble trying to root my phone again after it crashed and had to start from beginning. When i try fastboot flash boot Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img it gives me fails and says FAILED <Remote: command not allowed> does any body know what im doing wrong? I managed to root it teh first time no problem.
Cheers
Click to expand...
Click to collapse
Is you bootloader unlocked?
krabappel2548 said:
Is you bootloader unlocked?
Click to expand...
Click to collapse
yes the bootloader is unloack but i had my phone rooted before then had to use pc companion to repair it, ive unlocked it again to be sure.
It seems driver problem.
I met the same problem as well as others yesterday, when I unlock, relock, re-unlock, root locked, root unlocked, flash recovery... for some crazy reason.
Try these:
Connect to flashtool (beta2 or beta4) with device power-on debug off, to see if flashtool can recognize it, and how much it can recognize.
Connect to flashtool with device power-on debug on , to see if flashtool can recognize it.
Connect to flashtool with device in fastboot mode, to see if flashtool can recognize it.
Connect to flashtool with device in flashmode, to see if flashtool can recognize it.
Flashtool may fix some driver error. I just succeeded after hours of bungling like that.
Good luck.
orc.x.lei said:
It seems driver problem.
I met the same problem as well as others yesterday, when I unlock, relock, re-unlock, root locked, root unlocked, flash recovery... for some crazy reason.
Try these:
Connect to flashtool (beta2 or beta4) with device power-on debug off, to see if flashtool can recognize it, and how much it can recognize.
Connect to flashtool with device power-on debug on , to see if flashtool can recognize it.
Connect to flashtool with device in fastboot mode, to see if flashtool can recognize it.
Connect to flashtool with device in flashmode, to see if flashtool can recognize it.
Flashtool may fix some driver error. I just succeeded after hours of bungling like that.
Good luck.
Click to expand...
Click to collapse
Thank you i got it by turning of debugging mode, strange it worked but cheers
I have this problem as well, tried doing above things, uninstalling drivers, reinstalling - help appreciated.
and Phone is working normal but after 5 second reboot and FC 's
Plz Help
same issue...
Has anyone found a sure fix for the issue presented by the original post? I am having this issue and I have tried different drivers, ftf's, computers, adb/fastboot/versions and flashtool versions. I have unlocked and relocked. Is rooting status "unknown" normal after bootloader unlock? -Z Ultra 6833 EU
Still no solution?
With my C6603 it does not allow to write boot aswell. Any final solutions?
edit: solution found: bootloader was not unlocked
Error flashing kernel
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
aravindjr said:
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
Click to expand...
Click to collapse
This is the wrong forum to ask this. This is the Xperia Z section.
Despite that, you need to unlock your bootloader to flash kernels via fastboot.
Sent from my C6603 using Tapatalk
After months using stock everything I decided to flash CM11 yesterday, I'm doing exactly same step as I was doing when on 4.1/4.2 but it seems like it doesn't works, I'm not even sure that my BL is unlocked despite success message, when trying to reboot after unlock BL I had a bootloop and when trying to recover with Sony's Flashtool it says 'device not unlocked'. So I repaired with PCC and restarted from scratch but same results today.
I'm totally lost as like I said I was doing exactly same thing on the same PC.
Edit : Now my XZ doesn't even start! I have the red led blinking while connected with usb, power+ Vol+ doesn't do anything, no vibrations at all!
I was on latest sony official ROM
Edit2 : Tryied again to recover with Sony's Flashtool but it says "Mobile Locked" that's crazy!
aravindjr said:
I use an xperia M..
I was trying to install custom rom in it.. and every time i try to flash a kernel using any flashtool, it says FAILED (remote: Command not allowed)
what should i do?? please, someone help me..
Click to expand...
Click to collapse
Check PM
Relax!
4.3 introduced a new security feature. Look up "unlock bootloader 4.3 xperia z" for help :good:
babylonbwoy said:
After months using stock everything I decided to flash CM11 yesterday, I'm doing exactly same step as I was doing when on 4.1/4.2 but it seems like it doesn't works, I'm not even sure that my BL is unlocked despite success message, when trying to reboot after unlock BL I had a bootloop and when trying to recover with Sony's Flashtool it says 'device not unlocked'. So I repaired with PCC and restarted from scratch but same results today.
I'm totally lost as like I said I was doing exactly same thing on the same PC.
Edit : Now my XZ doesn't even start! I have the red led blinking while connected with usb, power+ Vol+ doesn't do anything, no vibrations at all!
I was on latest sony official ROM
Edit2 : Tryied again to recover with Sony's Flashtool but it says "Mobile Locked" that's crazy!
Click to expand...
Click to collapse
BatteryAidFree said:
4.3 introduced a new security feature. Look up "unlock bootloader 4.3 xperia z" for help :good:
Click to expand...
Click to collapse
I know I'm late but thanks anyway, just updated to 4.4.4 today, I'll look to your advice, thanks for replying, you're the only one that took time to write few words to help.
Hope it goes well!
babylonbwoy said:
I know I'm late but thanks anyway, just updated to 4.4.4 today, I'll look to your advice, thanks for replying, you're the only one that took time to write few words to help.
Click to expand...
Click to collapse
You're welcome! The only thing I can think is if you want to install/rate 5 stars my app, would be greatly appreciated! ("Battery Aid" - I can't post the link apparently, "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!")
use flashtool to writ kernel
fastboot remote command not allowed Xperia Z3
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
stevenmanzano said:
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
Click to expand...
Click to collapse
Look in the service menu to confirm if your bootloader is unlocked.
Enter *#*#7378423#*#* in the dialler, then look in Service info -> Configuration. It will say "Bootloader unlocked: Yes" if it's unlocked.
Sent from my C6603
solved remote command not allowed
stevenmanzano said:
I unlocked my boatloader, but have no way to confirm that it is still unlocked. I'm running Windows 7. Fastboot used to work just fine before I unlocked my bootloader. FLASHTOOL works fine. But if I try to flash anything with fastboot I get the remote command error. Can't flash recovery. Can't flash boot image.
Click to expand...
Click to collapse
By installing FLASHTOOL by Sony I was instantly notified that my bootloader was not unlocked, even though I had already unlocked it three or four times without any errors. So I unlocked it again. Then fastboot flashed my images just fine.
I read through many threads and have followed the official Sony bootloader unlocking instructions. I have requested and received the unlock code from Sony via email. I have downloaded the inf file and placed it in the correct folder in Android SDK (which I also updated). But I am cannot access fastboot mode, I hold down Vol + and plug in the USB cable but the device shows a red led and goes into charging mode. Also the PC never prompts me to install fastboot driver it simply loads the SP as Sony mass storage device (in device manager).
I have read that some people seem to think that the SIM lock affects the ability to access fastboot but this SP is SIM unlocked. Sony's official guide to unlocking the bootloader says I need to access fastboot mode to enter the unlock code but how can I unlock the bootloader if I can't get into fastboot mode?
hmmm... don't know really... i once entered fastboot mode by mistake, while trying to root stock rom. wasn't reading instructions and put device in a fsatboot mode instead of debugging... was on stock rom so don't know if custom rom would let me do that. should check myself... if anything i know it is possible to get me that blue light shining.
To enter fastboot mode in Xperia SP just power down the phone and hold down the volume up key while pluging your phone into your pc
If you need flashmode do the same thing but with the volume DOWN button held down.
I´ve got the same problem. I can´t enter in flashmode neither in fastboot mode. I´m on windows 8 32bits and I installed the .245 Deodexed ROM with a problem on root and without CWM. I don´t know what to do now, please help me.
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
jackaros said:
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
Click to expand...
Click to collapse
Thanks for trying to help, but I understand that flashmode and fastboot are accessed using the phone. Actually the phone needs a piece of software like flashtool to keep it in flashmode otherwise it drops into charging mode. I didn't mention my computer so I don't know where you got that from.
As I explained, I am unable to access fastboot with stock ROM (1.257) and a custom ROM (based on 2.245) so it can't be a ROM bug or the flashing process having gone wrong.
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Ze Tolas said:
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Click to expand...
Click to collapse
It may be a flashtool problem you are right because 2 incidents with different Roms that both use flashtool to flash those roms.....
its pretty much self explenatory.
skojevac said:
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Click to expand...
Click to collapse
Interesting. Ok, I've read up on the process. So I use the various stock .ftf files and flashtool with the phone in flash mode? Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. If I do it, I will nandroid backup first, of course, but I think I remember reading in one thread that someone managed to soft brick their XSP doing this very thing.
Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. [/QUOTE said:
that's why you need to complete rooting procedure. root stock 1.257 kernel, than back to stock 2.245 with root preserved, and before you would install CWM try to put device in a fastboot mode, this assuming you still have a UB.
Click to expand...
Click to collapse
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
SuicideFlasher said:
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
Click to expand...
Click to collapse
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
skojevac said:
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
Click to expand...
Click to collapse
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
gandalf_grey91 said:
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
Click to expand...
Click to collapse
I said before, it's new firmware (maybe RU) with a Windows Flashtool issue. Today i did flash kernel to my SP using Linux client.
Same issues
gandalf_grey91 said:
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
Click to expand...
Click to collapse
Hi, I have some similar issues. I've also been flashing some stuff and whenever I try to go to fastboot it just boots into CWM. Very annoying to say the least. The dark blue light goes on when i hold down volume up and for a short moment I see the fastboot driver installing on my computer. But before it completes it's already in CWM.
Not sure what to do from here on wards, maybe some advice on which kernel to flash? I am pretty sure the latest kernel I flashed is the .254 root kernel from doomlord.
Ps. I really would like to flash CM when it becomes available as nightly :angel:
Thanks in advance!
Fast boot mode for xperia ion hspa???
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
I had already installed cm10.1 jb for my xperia ion.
Now i tried to install cm11 kitkat for my xperia ion.
Every thing is gone good.
But now got stuck up with a problem.
fast boot mode is active only for 5 seconds while connecting my xperia ion to System with flash tool.
help me to do the need ful.
Guide me to download compatible drivers and flash tool for fast booting process.
If you have UNLOCKABLE bootloader, then you dont have a FASTBOOT mode on your phone. Its just pure luck. some phones dont have it... kind of a sony crap... I also happen to be one of those LUCKY ppl. no unlock, so stuck with Stock kernel forever.
When you connect your phone to Flashtools in FLASHMODE...
See for a string BOOTLOADER: NOT_ROOTABLE.... it means you belong in the lucky group...
If it says rootable, then you're doing something wrong.
Pardon me if i read something incorrect. i skimmed through all the posts before posting.
hello, my xperia sp has been soft-bricked! im trying to get it back to normal, but i can't!
i downloaded the stock firmware for my phone c5306( .205 ) and im trying to flash it via flashtool.
a hundred times i have got the system.sin error! drivers updated, tried with different pcs, different cables! no result, same error!
i also tried excluding system.sin from the right column, all other files are flashed normally! but when i try system.sin, error!
also, my phone shows green light after sometime after i plug it into the charger! when i remove it and hold power button for 2sec, the red led flashes and goes off, if i hold it it keeps flashing!
also it will only show sony logo after flash mode has been exited!
please help me! i have spent 3 days on it(day and night) but still no solution!:crying:
i just got this phone 1 week ago!
i have also attached the image of the error!
please help devs! i will be very greatful!
the reason i think is that when the system.sin is almost done, the phone is exiting flashmode? this might be the reason?
if yes please give solution!
( i checked by disconnecting phone while the flashing was halfway through, same error!)
Firstly, try flashing some different FTF files, as this is most likely the problem.
If that doesn't work and you are already on unlocked bootloader, you can try the following:
1. Flash everything in the .ftf file using the latest Flastool, except system (system.sin).
2. Open the .ftf file using 7zip and extract the system.sin.
3. Flash the system.sin using fastboot: fastboot flash system system.sin.
The above method has worked for others with similar problems. Again, only for unlocked bootloader.
If that fails you might also have corrupted or broken NAND memory. Hardware issue is surely a probability.
Other might have other suggestions...
Gamm86 said:
If you are already on unlocked bootloader, you can try the following:
1. Flash everything in the .ftf file using the latest Flastool, except system (system.sin).
2. Open the .ftf file using 7zip and extract the system.sin.
3. Flash the system.sin using fastboot: fastboot flash system system.sin.
The above method has worked for others with similar problems. Again, only for unlocked bootloader.
If that fails you might also have corrupted or broken NAND memory. Hardware issue is surely a probability.
Other might have other suggestions...
Click to expand...
Click to collapse
somehow i flashed ftf! but now the phone reboots only after flash/fastboot mode, first it used to show only sony logo, but now it shows sony,xperia, xperia bootanimation, off!
if i flash system.sin through fastboot, where should i place the file?
moosa27 said:
if i flash system.sin through fastboot, where should i place the file?
Click to expand...
Click to collapse
In the folder where you extracted fastboot.
Fastboot is a program on it's own. I'm not talking about the fastboot mode in flashtool. (http://forum.xda-developers.com/showthread.php?t=2588979)
Again, ONLY FOR UNLOCKED BOOTLOADER.
If you haven't unlocked it, this methode won't work.
Try flashing a different FTF, as I mentioned after editing my post.
Gamm86 said:
In the folder where you extracted fastboot.
Fastboot is a program on it's own. I'm not talking about the fastboot mode in flashtool. (http://forum.xda-developers.com/showthread.php?t=2588979)
Again, ONLY FOR UNLOCKED BOOTLOADER.
If you haven't unlocked it, this methode won't work.
Try flashing a different FTF, as I mentioned after editing my post.
Click to expand...
Click to collapse
now whats happening is, when i press power button for 2 or more secs, the red led flashes! when i connect the phone to wall charger, red led stays on.
i took device into fastboot mode and rebooted into device via flashtool......
then the device booted normally and showed android id upgrading......... app 49 of 179 then off!
does this mean i should charge it? as far as i know, i have 70-80% battery.......
Leave phone in charging overnight and stay calm
Sent from my C5302 using XDA Free mobile app
moosa27 said:
then the device booted normally and showed android id upgrading......... app 49 of 179 then off!
does this mean i should charge it? as far as i know, i have 70-80% battery.......
Click to expand...
Click to collapse
Your battery is dead, but since android said it was upgrading apps, this means your problem is most likely fixed.
Let it charge for a few hours.
Gamm86 said:
You battery is dead, but since android said it was upgrading apps, this means your problem is most likely fixed.
Let it charge for a few hours.
Click to expand...
Click to collapse
Thanks.for all your efforts my phone was back normal yesterday
moosa27 said:
Thanks.for all your efforts my phone was back normal yesterday
Click to expand...
Click to collapse
Glad you got everything sorted.
Unless an Xperia SP has hardware problems, i'm quite sure it cannot get fully bricked.
I have exactly the same problem
Could you give me the steps to fix this problem? I have exactly the same problem when i try to install android with flashtool. No matter the version:
"24/017/2014 23:17:58 - ERROR - Processing of system.sin finished with errors.
24/017/2014 23:17:58 - INFO - Ending flash session
24/017/2014 23:17:58 - ERROR - 31 : A device attached to the system is not functioning.
24/017/2014 23:17:58 - ERROR - Error flashing. Aborted"
And when i try to power up a red led is blinking. If i connect the charger the red led stays on. Also, its hard to enter flashmode (green led) and fast boot (blue led) doesn't seem to work in Flashtool (in order to select system.sin to Flash). Despite the blue led is on, Flashtool doesn't let me to reboot into fastboot mode.
You got yourself a driver problem. Reinstall the drivers
i have the same problem. any solution for locked bootlader?sir please help i always get system.sin error when i flashed the stock rom.
ohmygel said:
i have the same problem. any solution for locked bootlader?sir please help i always get system.sin error when i flashed the stock rom.
Click to expand...
Click to collapse
you cant be hard bricked on locked bootloader . it hapenned to me. solutions:
1. get another ftf files, sometimes ftf can get damaged.
2. install custom drivers.
3. try different pcs (My Solution )
4. charge the phone 1 day (24hrs)
5. unlock bootloader and flash custom kernel and flash a rom, then u can flash stock and relock bl
6. change ur cable.
if no one of this solutions fix ur problem u are so bad
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
MAAAN!!! this worked!! I was spending many days and nights wondering WHY??? Thank you!!! :laugh::laugh:
I could flash 4.4.4 normally with the latest flashtool but no 5.x.x version would work!
If this is important enough maybe Androxyde will take a look into that...
Anyways , I am happy now^^
knauji said:
MAAAN!!! this worked!! I was spending many days and nights wondering WHY??? Thank you!!! :laugh::laugh:
I could flash 4.4.4 normally with the latest flashtool but no 5.x.x version would work!
If this is important enough maybe Androxyde will take a look into that...
Anyways , I am happy now^^
Click to expand...
Click to collapse
Lol its not a known problem and please do not notify Androxyde about it. Version post 0.19.8.6 but prior to 0.19.9.1 uses a template file called fsc to accommodate new xperia devices. This breaks support for older xperia devices that doesn't have the fsc template. The template can be created of course, but it seemed no one from the xperia sp community want to contribute lol.
So the versions that will make ftf flashable again is 0.19.8.6 and 0.19.9.1+. You could have solve this by yourself if you read the note given on the website properly.
TechnoSparks said:
Lol its not a known problem and please do not notify Androxyde about it. Version post 0.19.8.6 but prior to 0.19.9.1 uses a template file called fsc to accommodate new xperia devices. This breaks support for older xperia devices that doesn't have the fsc template. The template can be created of course, but it seemed no one from the xperia sp community want to contribute lol.
So the versions that will make ftf flashable again is 0.19.8.6 and 0.19.9.1+. You could have solve this by yourself if you read the note given on the website properly.
Click to expand...
Click to collapse
Well, I don't know what FSC is and the changelog on the website says the new version is compatible with all xperia devices....so that is what I used. How could I know..?
but it works now, that's all I need^^
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
Thanks button is broken but THANKS ! It was driving me crasy !!! :highfive:
BTW, the version is 0.9.18.6
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
I seach like crazy and ask Questions w/out an answer! THX a lot!!! It worked!!!
StanFear said:
hey, I had the same problem, system.sin not beeing flashed (everything else was)
the second of three error message (where the reason for the failure to install system.sin) was "ERROR - " so ... not very helpfull ^^
so after trying pretty much every solutions offered in this thread with no success I tried changing flashtool version going from 0.9.19.1 to 0.18.6 and ...
it worked, I was able to flash the full ftf file and start my phone again !!
Click to expand...
Click to collapse
can you provide me the download link of flashtool 0.18.6
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that
thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go
I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!
Cannot get into recovery. Device seems to be bricked.
After Sony logo there is nothing else other than black screen. Please help me recover my device.
Don't Panic, this can easily be recovered. However the data that was inside I'm afraid is gone forever. Maybe it can be recovered maybe not, anyway I'm giving you some easy steps you can follow to recover your device.
1. Download Flashtool
2. Download the Firmware you want to load into the phone. (Search in the forum for .ftf ---make sure it is for Xperia Z --- files or you can download Xperifirm and make them on your own)
3. Once you have the .ftf file ready click on the Flash (Lightning) icon and select the firmware (.ftf) [Mode to flash is FLASHMODE]
4. When the phone is just one second from booting up (I know you are now in a cycle - loop but try as many times until you get it right), with the VOLUME DOWN button pressed connect it into the PC.
5. Wait for flash - About 10-15 min and you are done.
For any questions ask here. Good luck
I recovered my phone via Sony PC companion. Succesfuly managed to flash dual recovery again. Flashed ROM and Gappps.
This time Phone didnt start after reboot. There is not even a sony logo. No reboots at all and now it seems bricked ?
If anyone is reading please help me out.
I tried using Flashtools getting into Fastboot mode (Blue light flashing), but Flashtoool responded saying needs to installl drivers. I did that as well, but now the flashtools wont start at all.
I am trying via pc companion, Its stuck on a step where its asking me to remove my battery.. How do I recover ? Please help. Thanks in advance.
ProudRed said:
I recovered my phone via Sony PC companion. Succesfuly managed to flash dual recovery again. Flashed ROM and Gappps.
This time Phone didnt start after reboot. There is not even a sony logo. No reboots at all and now it seems bricked ?
If anyone is reading please help me out.
I tried using Flashtools getting into Fastboot mode (Blue light flashing), but Flashtoool responded saying needs to installl drivers. I did that as well, but now the flashtools wont start at all.
I am trying via pc companion, Its stuck on a step where its asking me to remove my battery.. How do I recover ? Please help. Thanks in advance.
Click to expand...
Click to collapse
Can you get to the point where the phone lights up the GREEN LED (flash mode) ?
Also what version of windows are you using?
aaronkatrini said:
Can you get to the point where the phone lights up the GREEN LED (flash mode) ?
Also what version of windows are you using?
Click to expand...
Click to collapse
Hi, Flash mode is working for me. I have recovered couple of times using flashtools in flash mode. But fastboot mode is not working for me. It says drivers are missing though I have installed drivers..
I went through tthe threads and could find a workking method to unlock the bootloader. Sony has too many appps which I do not need, I want to get rid of them as it consumes a lot of batttery. Hence a custom Rom with basic stuffs arre the soolution.
If you can help me unlock my BL I'd be thankful
And one more question, does TWRP's Latest version only works for Unlocked BL ?
ProudRed said:
Hi, Flash mode is working for me. I have recovered couple of times using flashtools in flash mode. But fastboot mode is not working for me. It says drivers are missing though I have installed drivers..
I went through tthe threads and could find a workking method to unlock the bootloader. Sony has too many appps which I do not need, I want to get rid of them as it consumes a lot of batttery. Hence a custom Rom with basic stuffs arre the soolution.
If you can help me unlock my BL I'd be thankful
And one more question, does TWRP's Latest version only works for Unlocked BL ?
Click to expand...
Click to collapse
First, Try to do things in order!!!
You are very messy, first you needed to unbrick the device, now you want to unlock its BL and want to know if you can install TWRP!
Install a stock firmware, make sure you can unlock the phone (by checking in the settings menu)...
And post some info...
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
aaronkatrini said:
First, Try to do things in order!!!
You are very messy, first you needed to unbrick the device, now you want to unlock its BL and want to know if you can install TWRP!
Install a stock firmware, make sure you can unlock the phone (by checking in the settings menu)...
And post some info...
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
Device unbricked, stock rom running with Root access and dual recovery installed. Fastboot drivers cant be installed, what to do ? And how to do ? OS Windows 10
All issues solved. On custom ROM now. Thank You to those who tried to help.
ProudRed said:
All issues solved. On custom ROM now. Thank You to those who tried to help.
Click to expand...
Click to collapse
Good for you, for anyone who needs to install fastboot driver on windows 10, when they cannot install they need to disable windows driver signature:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Also for some who is in the same situation please post your solution, it helps the community.
P.S.: you can always hit that thanks button instead of thanking
I would like to know if there are custom kernels available for battery saving ? I flashed Zomie kernel and it was repeatedly booting my device into multirom recovery.
Right now I am on mokee, can I use any custom kernel with it ? If yes what ? I couldnt find many custom kernels for the device and what about Roms ? Not many custom Roms as well, only found RR and Mokee. Slim LP does not have a working link and couldnt find other popular roms too for this device.
I never tried new kernels, only thing install Kernel Adiutor and underclock, also change the governor mode.
As for the rom I use the modified stock rom by @androidexpert35, it provides good balance between performance and battery life. For any Rom you should write in their dedicated post. Keep experimenting but do it in a reasonable way and don't try to ask for everything, search and read others. Good luck