Was stupid and bricked my phone. Can access Fastboot (+adb) but no Recovery... - Wileyfox Swift

Hey guys, to keep it short:
- Wileyfox Swift, Cyanogenmod 13, Android 6.0.1
- Played around with Titanium Backup Pro and probably broke the OS somehow.
- When I start the phone, after the Wileyfox Swift-Logo, I only get occasional flashes and that's it.
- I can access Fastboot and can give it commands from my PC via adb
- I cannot access Recovery (white flashes again). Starting a recovery-img via adb didn't work either.
Is there still hope?
Thanks for any help.

Blaubart7 said:
Hey guys, to keep it short:
- Wileyfox Swift, Cyanogenmod 13, Android 6.0.1
- Played around with Titanium Backup Pro and probably broke the OS somehow.
- When I start the phone, after the Wileyfox Swift-Logo, I only get occasional flashes and that's it.
- I can access Fastboot and can give it commands from my PC via adb
- I cannot access Recovery (white flashes again). Starting a recovery-img via adb didn't work either.
Is there still hope?
Thanks for any help.
Click to expand...
Click to collapse
if you still have access via fastboot you can restore stock cos12.1 or cos13.0 as follows:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img

Recovery ended up working again after I did this, and I was able to reset my phone.
Thank you!!

where would I get these files?
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
I found the first batch in the CyanogenMod zip, but the above 4 are not present. Are these in the recovery bin or do I need to get a backup from another wileyfox swift?
---------- Post added at 10:07 PM ---------- Previous post was at 09:44 PM ----------
LG-dudey said:
where would I get these files?
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
I found the first batch in the CyanogenMod zip, but the above 4 are not present. Are these in the recovery bin or do I need to get a backup from another wileyfox swift?
Click to expand...
Click to collapse
Flashing the first batch from DiorDNA's guide gives me a new fastboot mode with a number of options. I have a menu that shows:
Reboot to Android
Reboot to Recovery
Reboot to Bootloader
Power down
About the Phone
Reboot to EDL
none of these options help me unfortunately and still put me in boot loop with the Wileyfox Swift Powered by Android screen repeatedly flashing / looping
I suspect its due to the 4 files I am missing

LG-dudey said:
where would I get these files?
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
I found the first batch in the CyanogenMod zip, but the above 4 are not present. Are these in the recovery bin or do I need to get a backup from another wileyfox swift?
---------- Post added at 10:07 PM ---------- Previous post was at 09:44 PM ----------
Flashing the first batch from DiorDNA's guide gives me a new fastboot mode with a number of options. I have a menu that shows:
Reboot to Android
Reboot to Recovery
Reboot to Bootloader
Power down
About the Phone
Reboot to EDL
none of these options help me unfortunately and still put me in boot loop with the Wileyfox Swift Powered by Android screen repeatedly flashing / looping
I suspect its due to the 4 files I am missing
Click to expand...
Click to collapse
The files are all in the "fastboot zip" on this site
https://cyngn.com/support

Blaubart, did you ever resolve that, s I just did the exact same and bricked the phone with Titanium remove system app.
How did you get fastboot to connect, I have 2 stages i tried with "fastboot oem device-info",
turned off and plug in USB cable I get the willeyfox logo (fastboot doesnt care about it yet)
booted to the twrp boatloder but cant go to recovery or os boot (flickerig as you desbribed) (fastboot still doent care about)
I'm not yet prepared to bin the phone

ok for the records if anyone else stumples over this...
you are able to fastboot flash once reaching the bootloader menu. however only 1 of my 10 USB cables (and it was the second last) was actually able to detect / connect the phone properly.
the image files can be obtained from https://cyngn.com/support or rather go straight for lineageOS as I did.
https://www.hacksandgeeks.com/singl...l-Lineage-OS-141-for-Wileyfox-Swift-crackling

the-madman said:
ok for the records if anyone else stumples over this...
you are able to fastboot flash once reaching the bootloader menu. however only 1 of my 10 USB cables (and it was the second last) was actually able to detect / connect the phone properly.
the image files can be obtained from https://cyngn.com/support or rather go straight for lineageOS as I did.
https://www.hacksandgeeks.com/singl...l-Lineage-OS-141-for-Wileyfox-Swift-crackling
Click to expand...
Click to collapse
It would be better to link here
https://download.lineageos.org/crackling
rather than your second link

LG-dudey said:
where would I get these files?
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
I found the first batch in the CyanogenMod zip, but the above 4 are not present. Are these in the recovery bin or do I need to get a backup from another wileyfox swift?
---------- Post added at 10:07 PM ---------- Previous post was at 09:44 PM ----------
Flashing the first batch from DiorDNA's guide gives me a new fastboot mode with a number of options. I have a menu that shows:
Reboot to Android
Reboot to Recovery
Reboot to Bootloader
Power down
About the Phone
Reboot to EDL
none of these options help me unfortunately and still put me in boot loop with the Wileyfox Swift Powered by Android screen repeatedly flashing / looping
I suspect its due to the 4 files I am missing
Click to expand...
Click to collapse
I'm in this pickle too. I tried to flash the latest TWRP but when trying to get into recovery I am stuck in a bootloop with the same menu as you. Did you end up resolving this issue ? I've tried plugging in a USB cable from my phone to my PC but my PC doesn't seem to recognize it.
I think wiping my lineage OS in TWRP and then not enabling OEM bootlock/USB-debugging has got me in this situation. Any help is much appreciated.

You need to get into fastboot mode, then flash a working recovery.
Install LineageOS on crackling | LineageOS Wiki
wiki.lineageos.org
If you can't enter fastboot mode via adb you can also enter it via hw keys.
Power off your phone, then
either keep holding VOL up and connect USB cable from PC
or keep holding VOL up and power on
Then wait until you see the menu with reboot to android/recovery/bootloader, power down and so on.
From there you can flash a working recovery via
Code:
fastboot flash recovery <recovery_filename>.img

115ek said:
You need to get into fastboot mode, then flash a working recovery.
Install LineageOS on crackling | LineageOS Wiki
wiki.lineageos.org
If you can't enter fastboot mode via adb you can also enter it via hw keys.
Power off your phone, then
either keep holding VOL up and connect USB cable from PC
or keep holding VOL up and power on
Then wait until you see the menu with reboot to android/recovery/bootloader, power down and so on.
From there you can flash a working recovery via
Code:
fastboot flash recovery <recovery_filename>.img
Click to expand...
Click to collapse
Thanks for the reply, I've sorted it now. One unrelated issue I'm having though is that I can flash GApps Pico since there is insufficient space apparently. Do you know how to fix this?
I've seen some people saying that you can cut down the size of GApps by making a config which excludes some installations but I also can't transfer media via USB to my wileyfox swift. All of the USB connection methods are greyed out

AssassinFox said:
Do you know how to fix this?
Click to expand...
Click to collapse
There are only three options: Don't install gapps, strip the gapps package so that it fits or reformat the internal storage. But for the third option you should know what you do as you could completely brick the device.

Related

How to restore Download Mode if all you have is Fastboot

This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Artifesto said:
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Click to expand...
Click to collapse
How would one go about repairing a broken download mode when all I can do is boot into a broken recovery? I cannot issue any fastboot commands as the device is only recognized as an ADB Bridge device. Are there ADB equivalent commands to accomplish the same things as you have detailed here?
SPRINT LS980 (was on Rooted Stock C and borked phone with D OTA) and a broken TWRP 2.7.1.0 Recovery
natefuhr said:
How would one go about repairing a broken download mode when all I can do is boot into a broken recovery? I cannot issue any fastboot commands as the device is only recognized as an ADB Bridge device. Are there ADB equivalent commands to accomplish the same things as you have detailed here?
SPRINT LS980 (was on Rooted Stock C and borked phone with D OTA) and a broken TWRP 2.7.1.0 Recovery
Click to expand...
Click to collapse
well you should never install any OTA with a custom recovery install. you should always keep at least one backup on your phone to restore to in these events. but i would try downloading a rom and installing via sideload before nuking any partitions. which is easy with TWRP. the sideload menu should be in Advanced then ADB Sideload and the command is adb sideload filename.zip and it will take awhile depending on the file size. make sure the file name is simple and it is placed in the folder you are running the sideload from.
Artifesto said:
well you should never install any OTA with a custom recovery install. you should always keep at least one backup on your phone to restore to in these events. but i would try downloading a rom and installing via sideload before nuking any partitions. which is easy with TWRP. the sideload menu should be in Advanced then ADB Sideload and the command is adb sideload filename.zip and it will take awhile depending on the file size. make sure the file name is simple and it is placed in the folder you are running the sideload from.
Click to expand...
Click to collapse
Yes yes I know... it was a moment of weakness late at night and I didn't think before telling the girl to go ahead and upgrade. That being said... Part of the problem now is that the one backup she made just up and disappeared. The ADB sideload option just hangs and never actually does anything. The original Stock Rooted file I had still on the sd partition doesn't fix the issue when I flash it... it looks like it flashes ok but on the next boot it just drops me back into TWRP right where I began. And download mode is still borked.
So let's talk thermonuclear resolution on this motherlover.... where do I begin?
Sent from my SM-N900P using Tapatalk
natefuhr said:
Yes yes I know... it was a moment of weakness late at night and I didn't think before telling the girl to go ahead and upgrade. That being said... Part of the problem now is that the one backup she made just up and disappeared. The ADB sideload option just hangs and never actually does anything. The original Stock Rooted file I had still on the sd partition doesn't fix the issue when I flash it... it looks like it flashes ok but on the next boot it just drops me back into TWRP right where I began. And download mode is still borked.
So let's talk thermonuclear resolution on this motherlover.... where do I begin?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
hmmmmm.... I've been able to get my G2 into fastboot by holding Volume + and Pwr after it setting for awhile turned off.. may be stupid but have you tried that button combo or Volume + and Volume - with Pwr
Could u tell me the command cause i went adb sideload filename.zip and it comes up file not found and i put it in my platform-tools folder any ideas i have adb version 1.30...it was above the version that they said you need on the twrp site
whatsamatta u alumni 1990-2011
Fastboot???
Artifesto said:
This is for the people [myself earlier] who cannot boot into Android (bootloop or worse), have no download mode, no recovery and can only boot into Fastboot. Download the file below, I have included fastboot (for windows) and the appropriate files to flash, all you have to do is run the commands in order below, then boot into download mode.
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
It is best to use the CMD.exe file in the folder provided so you will already be running the commands from that folder without having to change directories. If you're on Linux then make sure you have Fastboot installed then run Terminal from the folder and run the same commands. This will restore the STOCK download mode and recovery partitions not TWRP or CWM.
Download Here
Click to expand...
Click to collapse
How do I get to fastboot. I can get to recovery but that's it. Download is not working. The Vol+/- and Power just gets me to key controls.
deathsquad737 said:
Could u tell me the command cause i went adb sideload filename.zip and it comes up file not found and i put it in my platform-tools folder any ideas i have adb version 1.30...it was above the version that they said you need on the twrp site
whatsamatta u alumni 1990-2011
Click to expand...
Click to collapse
i would try to rename your rom to something simple, like rom.zip. there cannot be any spaces in the name and it does need to be in the same folder you run the command from like you seem to be doing.
gelito81 said:
How do I get to fastboot. I can get to recovery but that's it. Download is not working. The Vol+/- and Power just gets me to key controls.
Click to expand...
Click to collapse
did you try vol+ and power together? When a functioning rom is installed it asks to do a factory reset but it may get into fastboot if you nuked that partition. i haven't tried this yet but if you're in adb sideload in twrp maybe the command
Code:
adb reboot fastboot
might help
Artifesto said:
i would try to rename your rom to something simple, like rom.zip. there cannot be any spaces in the name and it does need to be in the same folder you run the command from like you seem to be doing.
did you try vol+ and power together? When a functioning rom is installed it asks to do a factory reset but it may get into fastboot if you nuked that partition. i haven't tried this yet but if you're in adb sideload in twrp maybe the command
Code:
adb reboot fastboot
might help
Click to expand...
Click to collapse
Tried all of the above.... they all just send me into recovery or broken download mode
damn
I'm screwed. I gave this a try and now all I get is a black screen. The phone will connect to my computer but I can't send any commands to it through the command prompt. When it connects to the computer it opens a bunch of different drives and says I need to format them. I can't get into download mode and when I try to send a command in the prompt it just says waiting for device. Any ideas?
Edit: It shows up in device manager like this: http://i.imgur.com/NXGxpcX.png
http://forum.xda-developers.com/showthread.php?t=2582142 try that
Sent from my VS980 4G using XDA Free mobile app
how i can enter in FASTBOOT mode ?
I'm not sure if you can help me here. I have a Verizon G2 and am trying to reset to factory for a repair. I am trying to get into download mode, but only get fastboot when pressing volume up while powered off and plugging in my USB cord. Any help would be greatly appreciated.
razer_ins said:
how i can enter in FASTBOOT mode ?
Click to expand...
Click to collapse
Flash xdabbbeb 24a bootstack zip
WHATSAMATTA U ALUMNI
---------- Post added at 08:46 PM ---------- Previous post was at 08:45 PM ----------
Crossxcalibur said:
I'm not sure if you can help me here. I have a Verizon G2 and am trying to reset to factory for a repair. I am trying to get into download mode, but only get fastboot when pressing volume up while powered off and plugging in my USB cord. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Read 2 post above yours i answered your ?
WHATSAMATTA U ALUMNI
For everyone who is having issues with drivers see the video below to get fastboot to work:
https://www.youtube.com/watch?v=NaK5OxUeDKM

Phone has no fastboot.

Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.
maciek90 said:
Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.
Click to expand...
Click to collapse
The phone HAS RECOVERY does NOT HAVE BOOTLOADER
Read entire message. I wrote that this tool probably can be used to flash fastboot too.
You can also try "dd" command from busybox. Check sticky section in Zenfone General forum how to use it.
xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
You shouldn't mess with stuff you don't understand
If you have recovery, can you get to recovery menu?
Droid on back with error underneath and where you have to hold power then up volume to get to recovery menu.
Ok, here is link to flash_image tool.
http://forum.xda-developers.com/showthread.php?t=902493
I used it to flash recovery on HTC Sensation, but it should work with fastboot on Zenfone too. The command should be "flash_image fastboot /path/to/droidboot.img"
I'm not sure if it will work, but you already have messed up fastboot so this shouldn't make it worse
The second option is "dd if=/path/to/droidboot.img of=/dev/block/by-name/fastboot" or "dd if=/path/to/droidboot.img of=/dev/block/mmcblk0p3" as fastboot is the third partition. You can execute this even in terminal emulator on phone. Of course I haven't check it, but it's listed in general section to flash recovery (fastboot is just another partition, so it should work too).
About going to recovery maybe you can type " reboot recovery" in terminal emulator or from pc "adb reboot recovery". I'm not sure if it uses fastboot to boot into recovery but it's worth trying.
xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
Find Your Solution Here

[551ml] flashboot FAILD (remote: flash_cmds error!) Im stuck in fastboot

HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site
Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.
timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[
quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.
Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.

ZE551ml "continue the fastboot process" prompt in fastboot,can't boot into recovery

ZE551ml "continue the fastboot process" prompt in fastboot,can't boot into recovery
I tried to go back to stock rom from CM 14.1 Unofficial following this youtube tutorial : https://www.youtube.com/watch?v=inzG5MLS2y4
I downloaded 2.20.40.196(Latest Android L) but couldn't find appropriate recovery for it.So I searched xda and got one.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post.
Should use Asus flash tool. http://forum.xda-developers.com/showthread.php?t=3452082
Sent from my Zenfone 2 using Tapatalk
debopriyobasu said:
I tried to go back to stock rom from CM 14.1 Unofficial following this youtube tutorial : https://www.youtube.com/watch?v=inzG5MLS2y4
I downloaded 2.20.40.196(Latest Android L) but couldn't find appropriate recovery for it.So I searched xda and got one.
I followed this sequence:
1.) fastboot flash recovery (name of recovery).img
2.) fastboot flash boot boot.img
3.) fastboot flash fastboot droidboot.img
the boot.img and droidboot.img being extracted from the stock rom itself.
But after flashing, it shows "continue the fastboot process" in blue and selecting recovery option reboots the phone and brings it back to fastboot.
I CAN ACCESS FASTBOOT MODE,MY DEVICE IS RECOGNIZED BY MY PC.
But there is no recovery.
Kindly suggest what to do in relevance to my post.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B72QQTXqZSRwcXlwS0s5emlaOVk
down load zip file and extract it. place extracted files in adb fastboot tool folder. in empty place right click and open command window here. now run the following commands
fastboot flash splashscreen black_splashscreen_551.img
fastboot flash token bom-token_ze551ml_2.20.40.184.bin
fastboot flash dnx dnx_ze551ml_2.20.40.184.bin
fastboot flash ifwi ifwi_ze551ml_2.20.40.184.bin
fastboot flash fastboot droidboot_2.20.40.184.img
fastboot reboot-bootloader
after it reboots to boot loader run the following command
fastboot flash recovery recovery_sign.bin for stock recovery
or
fastboot flash recovery TWRP-3.0.2-Z00A.img for TWRP
after flash now use volume key to navigate options at top of the screen and select recovery mode and reboot to enter recovery mode. ( you may see android logo with error. When you see that screen. Press and hold power button then click volume up of down button and release both button)
now you can update stock via adb sideload
sukhwant717 said:
https://drive.google.com/open?id=0B72QQTXqZSRwcXlwS0s5emlaOVk
down load zip file and extract it. place extracted files in adb fastboot tool folder. in empty place right click and open command window here. now run the following commands
fastboot flash splashscreen black_splashscreen_551.img
fastboot flash token bom-token_ze551ml_2.20.40.184.bin
fastboot flash dnx dnx_ze551ml_2.20.40.184.bin
fastboot flash ifwi ifwi_ze551ml_2.20.40.184.bin
fastboot flash fastboot droidboot_2.20.40.184.img
fastboot reboot-bootloader
after it reboots to boot loader run the following command
fastboot flash recovery recovery_sign.bin for stock recovery
or
fastboot flash recovery TWRP-3.0.2-Z00A.img for TWRP
after flash now use volume key to navigate options at top of the screen and select recovery mode and reboot to enter recovery mode. ( you may see android logo with error. When you see that screen. Press and hold power button then click volume up of down button and release both button)
now you can update stock via adb sideload
Click to expand...
Click to collapse
Why go through all of this when you can just use the flash tool and reboot into stock?
Sent from my Zenfone 2 using Tapatalk
kenbo111 said:
Why go through all of this when you can just use the flash tool and reboot into stock?
Sent from my Zenfone 2 using Tapatalk
Click to expand...
Click to collapse
cool down buddy. it was for informational purpose only. he was already using commands to do so. i just told him the correct way.
second for using AFT he have to download raw firmware. which is more than 1 Gb of data which will be costly if he is using mobile data to download. as he mentioned he already downloaded LP firmware from asus. with above method. he will be able to install the earlier downloaded zip file without any additional firmware download.
third as he mentioned he was on CM. i doubt installation with AFT might not be successful. he may have to flash stock ifwi and recovery and boot etc...
sukhwant717 said:
cool down buddy. it was for informational purpose only. he was already using commands to do so. i just told him the correct way.
second for using AFT he have to download raw firmware. which is more than 1 Gb of data which will be costly if he is using mobile data to download. as he mentioned he already downloaded LP firmware from asus. with above method. he will be able to install the earlier downloaded zip file without any additional firmware download.
third as he mentioned he was on CM. i doubt installation with AFT might not be successful. he may have to flash stock ifwi and recovery and boot etc...
Click to expand...
Click to collapse
It was just a question.
Sent from my Zenfone 2 using Tapatalk
I can't thank you how much you helped me!!! I just recovered my half-dead phone!!!
You are awesome man! Thanks a lot! My device is alive again and can boot into recovery! I'm adb sideloading now
debopriyobasu said:
I can't thank you how much you helped me!!! I just recovered my half-dead phone!!!
You are awesome man! Thanks a lot! My device is alive again and can boot into recovery! I'm adb sideloading now
Click to expand...
Click to collapse
Good to know that was helpful.

TWRP for Realme 3 [Working][Updated:21-Aug-2019]

All Praise and All Thanks To God
Things Required: Unlocked bootloader, TWRP file, Disable_Dm-Verity_ForceEncrypt.zip file, External SD card, adb and fastboot drivers installed in pc
Steps to flash TWRP:
Note: This will erase all your data, so please backup important things like photos,contacts etc , before following this procedure
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/guide-bootloader-unlock-guide-realme-3-t3999463
2. Copy Disable_Dm-Verity_ForceEncrypt.zip in your External SD Card. Power off your phone by pressing power button, after your phone is powered off ,hold volume down + power button to boot into fastboot mode
3. Commands to execute:
fastboot flash recovery twrp.img
fastboot -w
fastboot oem reboot-recovery
4.Touch will not work for 40 seconds, just wait until touch starts to work.
5. Now very Important part, take full twrp backup in your external sdcard and keep it safe in your pc (This backup will be helpful in future incase you soft brick your device or have some issues in your phone such as network or volte or some other **** not working)
6. Install the Disable_Dm-Verity_ForceEncrypt.zip using twrp
7 .Reboot, Done!
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Please Note:
1. There will be red blinking notification due to flashing Disable_Dm-Verity_ForceEncrypt_Quota_.zip, you can just ignore it. If you don't like the red bliking notification, just restore your nvdata, vendor and system from twrp backup.
2. Don't relock bootloader after flashing twrp, it might brick your device. (Don't use fastboot flashing lock)
3. You cannot restore preloader_a and preloader_b partitions using twrp, only you can backup the two partitions, so always uncheck these two partitions before performing a twrp restore.
4. Please don't use minimal adb and fastboot tool, use Latest ADB and Fastboot Installer tool , link is provided below.
Features:
1. You can directly flash ota zip from twrp, but you have to decrypt it first using ozipdecrypt from here:
https://github.com/bkerler/oppo_ozip_decrypt
2. Fstab includes all the partitions to backup and restore
Links:
TWRP : https://github.com/fawazahmed0/android_device_Realme3_RMX1821/releases
Disable_Dm-Verity_ForceEncrypt.zip: https://zackptg5.com/android.php#disverfe
Latest ADB and Fastboot Installer: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Device Tree: https://github.com/fawazahmed0/android_device_Realme3_RMX1821
How to boot to recovery:
A. From adb:
adb reboot recovery
adb shell reboot recovery
B. From fastboot mode:
fastboot oem reboot-recovery
C. There is no way to boot to recovery using power + vol down button after unlocking your bootloader. Only above two methods will work. (Don't relock bootloader after flashing twrp, it might brick your device)
Warning: if you did not follow the steps properly, either the twrp will be blank or you will be in endless recovery mode bootloop or you will revert back to stock recovery next time you try to boot to twrp.
Contributors:
@chankruze for his device tree and stable twrp:
https://github.com/N00bTree/android_device_realme_spartan
Blackcat: Got to know verity can be disabled by modifying vendor partition
@haditriw: For testing and verifying vendor can be modified in this phone
@ashu7073 for fixing screen issue and for his device tree
@jeffalaiza for making twrp ports
@Zackptg5 for his Disable_Dm-Verity_ForceEncrypt.zip
@osm0sis for his system_root mount support in AK3 which Disable_Dm-Verity_ForceEncrypt.zip uses
Nice Work
I will test soon
---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------
KSUBROTO said:
It didn't work
Click to expand...
Click to collapse
dont be stupid nova customizer you dont have rm3 phone all developer from realme device they know you scammer !!
Will we still see blank screen after 2 minutes of loading, or anything else?
Sounak Biswas said:
Will we still see blank screen after 2 minutes of loading, or anything else?
Click to expand...
Click to collapse
When twrp boots, it will be blank screen, so don't panic.
you have to wait for atleast 2 minutes before executing the next commands
Has anyone been able to flash supersu.zip through shell yet?
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Jion This https://t.me/joinchat/HrjmCBBex1F5cy9q0m7cQg
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Use magisk, https://forum.xda-developers.com/realme-3/how-to/rooting-guide-realme-3-t3927028
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Superuser on magisk .
I need scatter file
Make scatter file for realme 3 my rm3 is deadboot
johncedd said:
Make scatter file for realme 3 my rm3 is deadboot
Click to expand...
Click to collapse
Please Download The Stock Rom inside You Get Scatter File Ok
johncedd said:
Make scatter file for realme 3 my rm3 is deadboot
Click to expand...
Click to collapse
If it's soft brick or bootloop see this guide:
https://forum.xda-developers.com/realme-3/how-to/realme-3-recover-soft-brick-boot-loop-t3920401
if it's hard brick go to service center.
I am not sure how scatter file will help you recover from hard brick.
Here is the scatter file for mt6771 chipset:
https://drive.google.com/file/d/1pjIkb9xuq4WRFVh72V3V6eNfzdhRTk8L/view
Thanks Sir
jeffalaiza said:
Thanks Sir
Click to expand...
Click to collapse
Welcome sir
Work on ROM A.18 sir ?
hi sir, wolud you help me
what step should i do I got HARDBRICK realme 3?
I'm a newbie
Hello. I've recently tried to install TWRP on my RMX1821, and followed all the instructions but hurdled when I tried to format userdata. It says:
CreateProcess failed: the system cannot find the file specified. (2)
error: Cannot generate image for userdata
Click to expand...
Click to collapse
Any advice or solution to rectify this problem?
TwelveMoon said:
Hello. I've recently tried to install TWRP on my RMX1821, and followed all the instructions but hurdled when I tried to format userdata. It says:
Any advice or solution to rectify this problem?
Click to expand...
Click to collapse
Use adb platform tools..
I want to unlock the bootloader but in the application step I have waited more than 1 hour and the server has not shown success.
Can you share a link of video tutorial please.
fawazahmed0 said:
All Praise and All Thanks To God
Features:
1. You can directly flash ota zip from twrp, but you have to decrypt it first using ozipdecrypt from here:
https://github.com/bkerler/oppo_ozip_decrypt
2. Fstab includes all the partitions to backup and restore
Steps to flash TWRP:
Note: This will erase all your data, so please backup important things like photos,contacts etc , before following this procedure
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/bootloader-unlock-realme-3guide-t3920394
2. power off your phone by pressing power button, now hold volume down + power button to boot into fastboot mode
3. Commands to execute:
fastboot flash recovery twrp-3.3.1-0-RMX1821.img
fastboot -w
fastboot oem reboot-recovery
4.Touch will not work for 40 seconds, just wait until touch starts to work.
5. Now very Important part, take full twrp backup in your sdcard and keep it safe in your pc (This backup will be helpful in future incase you soft brick your device or have some issues in your phone such as network or volte or some other **** not working)
6a. Copy and install Disable_Dm-Verity_ForceEncrypt_Quota_.zip in your phone using:
adb push Disable_Dm-Verity_ForceEncrypt_Quota_.zip /
adb shell twrp install Disable_Dm-Verity_ForceEncrypt_Quota_.zip
or
b. copy the Disable_Dm-Verity_ForceEncrypt_Quota_.zip in sdcard and install using twrp touch interface, then wipe dalvik, cache, data and format data.
6. Done!
There will be red blinking notification due to flashing Disable_Dm-Verity_ForceEncrypt_Quota_.zip, you can just ignore it. If you don't like the red bliking notification, just restore your nvdata, vendor and system from twrp backup.
Disable_Dm-Verity_ForceEncrypt_Quota_.zip: https://www.androidfilehost.com/?fid=6006931924117924278
or download the latest version from here: https://zackptg5.com/android.php#disverfe
TWRP : https://github.com/fawazahmed0/android_device_Realme3_RMX1821/releases
Device Tree: https://github.com/fawazahmed0/android_device_Realme3_RMX1821
How to boot to recovery:
From adb:
adb reboot recovery
adb shell reboot recovery
From fastboot mode:
fastboot oem reboot-recovery
If you want to boot to recovery using power + vol down button, then you have to lock the bootloader using:
fastboot flashing lock
Warning: if you did not follow the steps properly, either the twrp will be blank or you will be in endless recovery mode bootloop or you will revert back to stock recovery next time you try to boot to twrp.
Contributors:
@chankruze for his device tree and stable twrp:
https://github.com/N00bTree/android_device_realme_spartan
Blackcat: Got to know verity can be disabled by modifying vendor partition
@haditriw: For testing and verifying vendor can be modified in this phone
@ashu7073 for fixing screen issue and for his device tree
@jeffalaiza for making twrp ports
@Zackptg5 for his Disable_Dm-Verity_ForceEncrypt.zip
Click to expand...
Click to collapse
ROM manager shows that TWRP is my current recovery but I can't boot into TWRP recovery, I don't understand the issue.

Categories

Resources