hey there, people.
well, i installed Mur4ik's 2.3.3-Cyanogenmod-7 and now i want to restore my mobile to the original 2.1 ROM. anybody can explain me what i have to do? i saw this post, but i didn't understood how i do the thing: http://forum.xda-developers.com/showthread.php?t=971899 .
anyway, if u are going to ask what rom i want to put on my mobile, the rom is the portuguese V20A_00.
hope you can help. thanks in advance!
cheers,
Manuel
http://forum.xda-developers.com/showthread.php?t=1119531
Tutorial
To do that follow the steps bellow:
KDZ Updater method
1. Boot in fastboot mode and execute the commands bellow:
- "fastboot -w"
- "fastboot erase system"
- "fastboot erase boot"
2. Reboot from fastboot directly to download mode (Power + Volume Down key)
3. Connect your phone to your PC and open KDZ Updater
4. Select any fastboot ROM
NOTE: YOU CAN NOT FLASH A NORMAL ROM!!! YOU MUST USE A FASTBOOT ROM!!!
5. Flash your rom in "Emergency Mode"
6. When finished the phone will reboot automatically
Recovery method using my brother's recovery file
1. Boot into Recovery mode
2. Wipe your user data (Factory reset)
3. Choose the update.zip file from your SD Card. You can download it here
4. After the update is done, reboot the phone
The ROM is V20A, so it supports Portuguese language.
Hi,
I have the same problem here.
I have upgraded to SwiftDroid 2.3.7 using fastboot command, because there is no boot logo and no recovery in my gt540, after updated with clockwork recovery rom.kdz. But the rom worked just fine.
I had problem the day after. My GT540 won't boot, it only vibrated and when I plug it to PC, Pc recognized fastboot mode. So I downgraded to frenchV20C.kdz without using fastboot -w fastboot erase boot and else.
Now, my gt540 is bricked, it only vibrates when I hold power button, and nothing happen. Can't boot into fastboot mode now.
Any help would be appreciated.
Ok, I've bricked my ZF 5 and have gone through many tuts to unbrick it but unfortunately I can't get into recovery mode. I can enter the droidboot mode by pressing Vol down + power button but when I click on Recovery there, it gets stuck at the boot screen mode(the one we see before entering into droidboot mode) and stays there forever. The adb shell does detect this and I did try to flash a recovery img through it but still no use. Can anyone get me out of this please?
Akhil916 said:
Ok, I've bricked my ZF 5 and have gone through many tuts to unbrick it but unfortunately I can't get into recovery mode. I can enter the droidboot mode by pressing Vol down + power button but when I click on Recovery there, it gets stuck at the boot screen mode(the one we see before entering into droidboot mode) and stays there forever. The adb shell does detect this and I did try to flash a recovery img through it but still no use. Can anyone get me out of this please?
Click to expand...
Click to collapse
download firmware from asus site, unzip them and you will see some folders and: recovery.img droidboot.img and boot.img
so, download and 1.0.32 and put recovery.img to folder with adb files.
boot Zf5 to fastboot/droidboot plug in computer ( you need asus drivers ) open cmd window in adb folder (SHIFT+ RIGHT CLICK) and then write : fastboot flash recovery recovery.img
press enter and wait, now try boot to recovery
you can try flash droidboot.img and boot.img too
kihope12 said:
download firmware from asus site, unzip them and you will see some folders and: recovery.img droidboot.img and boot.img
so, download and 1.0.32 and put recovery.img to folder with adb files.
boot Zf5 to fastboot/droidboot plug in computer ( you need asus drivers ) open cmd window in adb folder (SHIFT+ RIGHT CLICK) and then write : fastboot flash recovery recovery.img
press enter and wait, now try boot to recovery
you can try flash droidboot.img and boot.img too
Click to expand...
Click to collapse
Thanks for the reply but as I mentioned I've already tried this and I do get a FLASH Complete messages as well. However, when I click on recovery now, it gets stuck at boot screen.
kihope12 said:
download firmware from asus site, unzip them and you will see some folders and: recovery.img droidboot.img and boot.img
so, download and 1.0.32 and put recovery.img to folder with adb files.
boot Zf5 to fastboot/droidboot plug in computer ( you need asus drivers ) open cmd window in adb folder (SHIFT+ RIGHT CLICK) and then write : fastboot flash recovery recovery.img
press enter and wait, now try boot to recovery
you can try flash droidboot.img and boot.img too
Click to expand...
Click to collapse
btw I cant find droidboot.img file inside the firmware
Akhil916 said:
btw I cant find droidboot.img file inside the firmware
Click to expand...
Click to collapse
droidboot=fastboot
in 4.4 kitkat is fastboot
in 5.0 lollipop is droidboot, but it is same
try relock bootloader
in my experience if you have flashed all three droidboot, recovery and boot image. still cant entering recovery. it is hardware issue..
dont waste ur time,, go to nearest service center
hey guys i have the same issue with Asus Zenfone 6 (A601CG), i am able to go into fastboot but when ever i select recovery only "USB logo" is showing.....
iam having problem entering to recovery mode on after adb flash.i jst stucked with fastboot and on press recovery ,phone's displaying asus logo and stucks to proceed furthur.
pls help me as i tried the above mentioned method too.
SriChinnu said:
iam having problem entering to recovery mode on after adb flash.i jst stucked with fastboot and on press recovery ,phone's displaying asus logo and stucks to proceed furthur.
pls help me as i tried the above mentioned method too.
Click to expand...
Click to collapse
Do one thing when you get into fastboot and tap on recovery an asus logo is seen.
Then kindly hold your power button and then your device will switch-on to twrp easily.
The actual problem is because of your device unable to get into twrp automatically so herein the above method you are manually getting into device.
Regards
Janus
Bricked phone doing factory upgrade to B04. Stuck in EDL mode, but wont connect
Device manager shows QUSB_BULK but no tool will see the phone. Any ideas guys.
I have installed quailcom drivers etc , no difference
You can try this tool:
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Hi , I did try that. The port manager in the app does not show anything. It as if the phone is not connected. Even though it is listed in windows device manager as QUSB_BULK
Wait until batterry fully discharged, try enter edl mode again and flash using edl tool or miflash
the_hoho said:
Wait until batterry fully discharged, try enter edl mode again and flash using edl tool or miflash
Click to expand...
Click to collapse
Hi,
I waited till the battery discharged. Went into EDL mode. They only success I had is with axon7tool.exe
Miflash will not detect the phone. As seen believe I can read and write with axon7tool.exe
Is there any recovery I can put back on the phone that will run? The bootloader is unlocked. Thanks
H:\TRWP AXON 7>axon7tool -r recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Reading recovery ...
Success!
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
> H:\TRWP AXON 7>axon7tool -r recovery
Your command with option "-r" (for read) only backuped the existing recovery to your PC.
There was no effect on the phone. It read your phone recovery and downloaded (=backuped) to your PC (probably with name recovery-backup.bin).
Since your booloader is unlocked, you can write official but unsigned TWRP recovery to the phone. This official but unsigned TWRP recovery
will run correctly (since bootloader is unlocked). So you need to 1) download latest official TWRP recovery, then 2) write it to the phone.
1)
On your PC:
Go to https://eu.dl.twrp.me/ailsa_ii/
Download the recovery twrp-3.3.1-0-ailsa_ii.img (14 897 152 bytes, md5 0d57b791c6b7c7d979ea70b0951c519d) with the link:
https://eu.dl.twrp.me/ailsa_ii/twrp-3.3.1-0-ailsa_ii.img.html
Copy the file to the directory containing your axon7tool.exe ("H:\TRWP AXON 7").
Then copy twrp-3.3.1-0-ailsa_ii.img to recovery.bin (command: "copy twrp-3.3.1-0-ailsa_ii.img recovery.bin")
(this means you have a new recovery.bin file which is exactly the same as twrp-3.3.1-0-ailsa_ii.img file).
Explanation: this to prepare to write TWRP recovery to the phone, the axon7tool.exe syntax "-w recovery" requires a file named recovery.bin
which has the content of the recovery you want to put (in your case, latest official TWRP recovery twrp-3.3.1-0-ailsa_ii.img).
On your PC, go to H:\TRWP AXON 7 directory:
H:\TRWP AXON 7>
type "dir" command, you should have files: axon7tool.exe, recovery.bin (identical to twrp-3.3.1-0-ailsa_ii.img), twrp-3.3.1-0-ailsa_ii.img and other files.
2)
Put you phone in EDL mode as you did before.
On your PC, type the following command to write TWRP recovery to the phone:
axon7tool -w recovery
(Explanation: the above command will write (-w) the recovery to the phone using the file named recovery.bin (= twrp_rec_tenfar.img) found in your PC.
You can then boot to recovery, using menu in bootloader at start (use Vol-Up, Vol-Down for selection, Power to Confirm selection).
Other way: if phone is power off: Vol-Up + Power to get into TWRP recovery.
Afterwards, with TWRP you have total control on the phone, custom ROM etc...
Hi Friends,
I have decided to create a new post, since I researched and it seems that my issue is not covered exactly by any previous thread.
I have Sony F5321, used years with Stock ROM. While playing a game, it turned off randomly, but when I play the same game while charging with USB cable (with AC charger or connected to a laptop), the phone was working fine. I have unlocked the bootloader and flashed LineageOS 16 (Android 9) in case a battery issue was solved better with LineageOS than with stock ROM. After some weeks with same (supposedly) battery issue, I decided to go back to Stock ROM. I have flashed OK with Flashtool (no errors), but phone is now stuck in Sony boot logo.
The status is:
1) Boot into Stock Rom: doesn’t work
2) Boot into recovery: doesn’t work
3) Force shut down (3 vibrations): works
4) Force reboot (1 vibration): doesn’t work, it stops at Sony boot logo
5) Charging while powered off: doesn’t work (no battery logo appears, red light)
6) Flashtool into flashmode: doesn’t work (it’s not detected)
7) Flashtool into fastboot mode: works, but I cannot do anything with that.
Please, your help, how can I get the phone works again? Preferably with Stock ROM, or any other stable ROM, but working! Thanks!
Nobody will help?
jayeffpee said:
Hi Friends,
I have decided to create a new post, since I researched and it seems that my issue is not covered exactly by any previous thread.
I have Sony F5321, used years with Stock ROM. While playing a game, it turned off randomly, but when I play the same game while charging with USB cable (with AC charger or connected to a laptop), the phone was working fine. I have unlocked the bootloader and flashed LineageOS 16 (Android 9) in case a battery issue was solved better with LineageOS than with stock ROM. After some weeks with same (supposedly) battery issue, I decided to go back to Stock ROM. I have flashed OK with Flashtool (no errors), but phone is now stuck in Sony boot logo.
The status is:
1) Boot into Stock Rom: doesn’t work
2) Boot into recovery: doesn’t work
3) Force shut down (3 vibrations): works
4) Force reboot (1 vibration): doesn’t work, it stops at Sony boot logo
5) Charging while powered off: doesn’t work (no battery logo appears, red light)
6) Flashtool into flashmode: doesn’t work (it’s not detected)
7) Flashtool into fastboot mode: works, but I cannot do anything with that.
Please, your help, how can I get the phone works again? Preferably with Stock ROM, or any other stable ROM, but working! Thanks!
Click to expand...
Click to collapse
Sounds like hardware failure to me, happened to me before... However, if you can get into fastboot, just go ahead and flash back to a custom kernel and recovery, and see if you can boot to recovery. That will tell you if it's not a hardware issue, then you can figure out how to get back to stock...
levone1 said:
Sounds like hardware failure to me, happened to me before... However, if you can get into fastboot, just go ahead and flash back to a custom kernel and recovery, and see if you can boot to recovery. That will tell you if it's not a hardware issue, then you can figure out how to get back to stock...
Click to expand...
Click to collapse
I tried a lot of things now. To confirm, I tried to use Flashtool in fastboot mode, but not sure where I get a custom kernel file to use with Fastboot menu option "select kernel to flash" but I have downloaded again lineage-16.0-20200511-UNOFFICIAL-kugo.zip file, should I take "boot.img" from unzipped directory? and how to flash the twrp-3.3.1-0-kugo.img file with Flashtool? which is the option to flash recovery using Flashtool in fastboot mode?
jayeffpee said:
I tried a lot of things now. To confirm, I tried to use Flashtool in fastboot mode, but not sure where I get a custom kernel file to use with Fastboot menu option "select kernel to flash" but I have downloaded again lineage-16.0-20200511-UNOFFICIAL-kugo.zip file, should I take "boot.img" from unzipped directory? and how to flash the twrp-3.3.1-0-kugo.img file with Flashtool? which is the option to flash recovery using Flashtool in fastboot mode?
Click to expand...
Click to collapse
Don't need Flashtool for fastboot. If you have the drivers installed, use your computer, and connect with the power off, holding the volume up button, and let go of the button when you see the blue led light, (if you don't get a blue led light, could be further evidence of a hardware issue). Now you're in fastboot mode.
Open a command prompt, and type "fastboot". If fastboot / adb is installed on your computer, and is set in the path, you will get a fastboot reply, if not, you will get, "fastboot is not recognized as a program or command...", or something like that. In that case, you need to either install fastboot, (look it up - it takes about 30 seconds), or, in the case of Linux or if you have the fastboot / adb files on your computer, but it's not in the Windows path, just change directory in your terminal to the directory where the files are, then try the command again.
Once you have fastboot working, just copy whatever you want to flash to the same directory you're in, and the commands are:
Kernel -
Code:
fastboot flash boot [name of file].img
Recovery -
Code:
fastboot flash recovery [name of file].img
ROM -
Code:
fastboot flash system [name of file].img
OEM (needed for recent AOSP -based roms) -
Code:
fastboot flash oem [name of file].img
Curious - how did you flash Lineage last time?
levone1 said:
Don't need Flashtool for fastboot. If you have the drivers installed, use your computer, and connect with the power off, holding the volume up button, and let go of the button when you see the blue led light, (if you don't get a blue led light, could be further evidence of a hardware issue). Now you're in fastboot mode.
Open a command prompt, and type "fastboot". If fastboot / adb is installed on your computer, and is set in the path, you will get a fastboot reply, if not, you will get, "fastboot is not recognized as a program or command...", or something like that. In that case, you need to either install fastboot, (look it up - it takes about 30 seconds), or, in the case of Linux or if you have the fastboot / adb files on your computer, but it's not in the Windows path, just change directory in your terminal to the directory where the files are, then try the command again.
Once you have fastboot working, just copy whatever you want to flash to the same directory you're in, and the commands are:
Kernel -
Code:
fastboot flash boot [name of file].img
Recovery -
Code:
fastboot flash recovery [name of file].img
ROM -
Code:
fastboot flash system [name of file].img
OEM (needed for recent AOSP -based roms) -
Code:
fastboot flash oem [name of file].img
Curious - how did you flash Lineage last time?
Click to expand...
Click to collapse
If I remember correctly, I have flashed the LineageOS (and also stock ROM downloaded by XperiFirm) with Flashtool in "flashmode", but then when I got the logo bootloop, it didnt work anymore. Only fastboot works. Not even booting in recovery mode seems to work.
I have already tried with fastboot in windows 10 cmd prompt (now called PowerShell).
fastboot flash boot boot.img --> works OK
fastboot flash recovery twrp-3.3.1-0-kugo.img --> works OK
fastboot flash system [system file].img --> there's no other IMG file inside LineageOS zip file besides boot.img, if you could provide another custom ROM zip file which includes both boot.img and system.img, please let me know
in addition. after flashing recovery OK, I tried "fastboot boot recovery" and the phone boots into bootloop again.
after shutting it off, there's no way to get into recovery mode. Only sony logo and red light (or no light)
jayeffpee said:
If I remember correctly, I have flashed the LineageOS (and also stock ROM downloaded by XperiFirm) with Flashtool in "flashmode", but then when I got the logo bootloop, it didnt work anymore. Only fastboot works. Not even booting in recovery mode seems to work.
I have already tried with fastboot in windows 10 cmd prompt (now called PowerShell).
fastboot flash boot boot.img --> works OK
fastboot flash recovery twrp-3.3.1-0-kugo.img --> works OK
fastboot flash system [system file].img --> there's no other IMG file inside LineageOS zip file besides boot.img, if you could provide another custom ROM zip file which includes both boot.img and system.img, please let me know
in addition. after flashing recovery OK, I tried "fastboot boot recovery" and the phone boots into bootloop again.
after shutting it off, there's no way to get into recovery mode. Only sony logo and red light (or no light)
Click to expand...
Click to collapse
So you tried to hold power and volume down to get into recovery? Also, if the only file in the LOS zip is a boot img, then the zip is incomplete. Try one of the Omni roms from the roms thread here. I've used them for N, O, and P, and they all work fine. There's a link to the Sony OEM files in the first post...
levone1 said:
So you tried to hold power and volume down to get into recovery? Also, if the only file in the LOS zip is a boot img, then the zip is incomplete. Try one of the Omni roms from the roms thread here. I've used them for N, O, and P, and they all work fine. There's a link to the Sony OEM files in the first post...
Click to expand...
Click to collapse
Yes, I tried vol+down while power on, and it stuck in sony logo white screen. Also tried from fastboot mode with "fastboot boot recovery" and "fastboot boot twrp.img" and it says "rebooting" but it only disables fastboot mode (windows' typical unplug drive sound), but phone get stuck with blue light.
its really strange. Is it possible that the phone has a battery HW issue that avoids it to charge (sometimes the empty battery big icon black screen appears), and that issue avoids recovery or reboot process?
jayeffpee said:
Yes, I tried vol+down while power on, and it stuck in sony logo white screen. Also tried from fastboot mode with "fastboot boot recovery" and "fastboot boot twrp.img" and it says "rebooting" but it only disables fastboot mode (windows' typical unplug drive sound), but phone get stuck with blue light.
its really strange. Is it possible that the phone has a battery HW issue that avoids it to charge (sometimes the empty battery big icon black screen appears), and that issue avoids recovery or reboot process?
Click to expand...
Click to collapse
Maybe specific to battery, but any issue with the main board is going to caused general wackiness... Could be what's happening. Maybe it would be worth it to try a new battery. Have you already tried different cables?
levone1 said:
Maybe specific to battery, but any issue with the main board is going to caused general wackiness... Could be what's happening. Maybe it would be worth it to try a new battery. Have you already tried different cables?
Click to expand...
Click to collapse
yes, I have 2 USB 3.0 cables. Both works perfectly with my other phone Moto G6 plus, in fast charge mode. it I can flash anything in fastboot mode, but cannot reboot into recovery, do you have other option to try? I downloaded and flashed the Sony OEM file (8.1/9/10) and flashed with fastboot normally. Then I have downloaded the Omni WEEKLY zip file, but in the Omni XDA thread, it says that the zip file must be flashed from Recovery (copied into the SD card), but I cannot access Recovery. I really want to revive this phone.
jayeffpee said:
yes, I have 2 USB 3.0 cables. Both works perfectly with my other phone Moto G6 plus, in fast charge mode. it I can flash anything in fastboot mode, but cannot reboot into recovery, do you have other option to try? I downloaded and flashed the Sony OEM file (8.1/9/10) and flashed with fastboot normally. Then I have downloaded the Omni WEEKLY zip file, but in the Omni XDA thread, it says that the zip file must be flashed from Recovery (copied into the SD card), but I cannot access Recovery. I really want to revive this phone.
Click to expand...
Click to collapse
Oh right - I forgot about that... Try AOSP https://androidfilehost.com/?fid=1899786940962592899 Unzip it and there should be a system img in it...
PHP:
levone1 said:
Oh right - I forgot about that... Try AOSP https://androidfilehost.com/?fid=1899786940962592899 Unzip it and there should be a system img in it...
Click to expand...
Click to collapse
Thanks for the link! I have downloaded and flashed all the IMG files inside with fastboot, everything OK. But the phone is still not rebooting to system nor to recovery mode. same behaviour. Stuck in sony logo.