Database Develop

[Q] Almost as good as a brick - No wipe, no SBF

Yesterday I had a received a phone call from a friend and upon ending the call I could not hang up. The screen had locked on the call screen. I waited and tried to use the power button to turn the screen off and then on to see if that would clear it but to no avail, so I had to do a battery pull.
I restarted the phone and first thing I noticed was that it was now telling me that I had 5% of my battery remaining, where the phone had been around 80% before the battery pull. Then pretty much everything started force closing, and it rebooted on its own. Upon restart it came up with the dialog box stating that "UIDs on system are inconsistent" and that I should wipe data, and has a button stating "I am feeling lucky". Then it’s endless pop ups of force closes. I finally get it to a point where I can try a factory reset via "Privacy" in settings but nothing changes.
I go into recovery and wipe data and cache partitions and it says it does so successfully, but when you reboot it has not. The phone goes into my "normal" home screen and settings, nothing has been restored back to outta the box state, and it does not prompt you to go through setup.
Other than I used Petes One Click root about 4 months ago the phone is stock, with no new apps installed just before this issue.
If you try to remove any applications, it says they are removed successfully, but when you reboot the phone they are all back as if nothing had happened.
Plug the phone into any computer and it is recognized, but the phone does not seem to know it is plugged into a PC... no "charging" or "mount SD" info.
I tried to do a factory image restore via RSDLite 5.6.4 using
cdma_solana-user 2.3.4 5.5.1_84_D3G-55 110812
It gets to step 3/18 and then tells me:
"Failed Flashing Process: 3/18 flash mbmloader "mbmloader.bin" Phone returned Fail"
I've used RSDL for flashing my OG, D2 and Dx's before with no issues.
RSDL's Flash error log shows:
Line 1041
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlasthThread.cpp
Device ID:0
03/13/12 00:48:51 New Log Started For Software Download.
03/13/12 00:54:21 00001db8 Phone.cpp 1750 0 ERROR GetTechnology failed: ERROR.
03/13/12 00:54:46 The FlashLog key is turned off.
03/13/12 00:54:52 Multi upgrade started for 1 phones
03/13/12 00:54:57 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin"
03/13/12 00:54:58 [Device ID: 0] 2/18 reboot-bootloader
03/13/12 00:55:03 [Device ID: 0] 3/18 flash mbmloader "mbmloader.bin"
03/13/12 00:55:04 ERROR: 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL. - on device ID 0.
03/13/12 00:55:04 [Device ID: 0] 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL.
03/13/12 00:55:04 ERROR: Failed flashing process. - on device ID 0.
03/13/12 00:55:04 Multi upgrade finished.
03/13/12 00:55:04 00001db8 Phone.cpp 514 0 ERROR Generic failure when sending command.
03/13/12 00:55:04 00001db8 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
03/13/12 00:55:04 00001db8 Phone.cpp 514 0 ERROR Generic failure when sending command.
03/13/12 00:55:04 00001db8 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
I then try Petes "One Click" easy unbrick and the command lines go through fine, all stating OK, and then it reboots the phone as it should. However instead of rebooting to the screen with the software box and the android with the yellow install bar, it goes to the white triangle with the exclamation point and little android. It will not go any further from that.
You can reboot the phone and it boots to the home screen, no set up, no removed programs...it looks as it did a few days ago before the issues started. However you will still get the force closes in a matter of minutes, the UID errors, and all the other issues.
Going to phone info shows the following.
System - 5.6.890
Baseband - N03.18.29P
Build - 5.5.1_84_D3G-55
I even tried to flash CM recovery and it will not do it. If you flash CWR through ROM Manager it will say it downloads and flashes successfully but it does not.
It seems as if the system has become unformat/flash/wipeable.
Suggestions? Clues!?

So you're on .890?
I'd try this first:
http://forum.xda-developers.com/showthread.php?t=1339816
File mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip

DoubleYouPee said:
So you're on .890?
I'd try this first:
http://forum.xda-developers.com/showthread.php?t=1339816
File mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
That has already been tried, as noted above.

Ianscape said:
That has already been tried, as noted above.
Click to expand...
Click to collapse
It says you used RSDlite

DoubleYouPee said:
It says you used RSDlite
Click to expand...
Click to collapse
And then after it says I did the Fast/Easy unbrick
Ianscape said:
...I tried to do a factory image restore via RSDLite 5.6.4 using
....
I then try Petes "One Click" easy unbrick...
Click to expand...
Click to collapse

Did you try removing the ones that give you error from the .bat?

did you started in the correct flash mode?
power + M
ap fastboot??
Use the one in my signature, its also psouza but is different (the one in psouza thread never worked for me)
this one (post by chaoticweaponry file by roots wiki) works in the mode i ssaid
the multiupload link is dead i think, but in the last posts there is a dropbox
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip

Pete's One Click Easy Unbrick sounds like a mash-up of his root tool and the quick unbricking script. Just to clarify, it was the MS DOS looking window that comes up after clicking "CLICK HERE TO FLASH etc."?

Hold "X" and power. When u get the triangle press both volume up and volume down @ the same time. Wipe data a couple times followed by wipe cache a couple times. Pull the battery, then use the easy unbrick method in fastboot. You will want to find a way to have a good if not full charge before you unbrick. Should do the trick.
~SU!C!D3~ \,,/.(*_*).\,,/
Sent from my UnLocked XT862 Droid 3 with full XT883 2.3.6 on Straight Talk GSM

I have bricked my phone numerous times recently and have found a very simple way to recover from it, without even having to plug it in to the computer. The OTA leak found here: http://forum.xda-developers.com/showthread.php?p=23223061 can be put on the root of your SD card and installed using the stock recovery. Power + x followed by volume up/down, wipe data, wipe cache, install zip from sd and selecting the OTA zip. I have recovered several times with this and it is pretty handy to be able to do it where ever you happen to be. Of course you will still have to root and reinstall your other goodies, but it works.
Side note: This OTA leak can NOT be rooted with the standard D3 root methods. You must use the D4 root method to gain root privileges.

gierso said:
did you started in the correct flash mode?
power + M
ap fastboot??
Use the one in my signature, its also psouza but is different (the one in psouza thread never worked for me)
this one (post by chaoticweaponry file by roots wiki) works in the mode i ssaid
the multiupload link is dead i think, but in the last posts there is a dropbox
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
Yes it was in ap fastboot. I will give the one in your sig a shot, as I have been using psouza's original zip. Maybe it will work *crossfingers*
redsox958 said:
Pete's One Click Easy Unbrick sounds like a mash-up of his root tool and the quick unbricking script. Just to clarify, it was the MS DOS looking window that comes up after clicking "CLICK HERE TO FLASH etc."?
Click to expand...
Click to collapse
Yes, it' the psouza Fast/Easy unbrick, using the moto-fastboot files, etc.
queberican351 said:
Hold "X" and power. When u get the triangle press both volume up and volume down @ the same time. Wipe data a couple times followed by wipe cache a couple times. Pull the battery, then use the easy unbrick method in fastboot. You will want to find a way to have a good if not full charge before you unbrick. Should do the trick.
Click to expand...
Click to collapse
That has been done several times, with no changes to the system. While Recovery states that it completes the wipe, it does not appear to wipe anything. I'm going to try the link gierso posted to see if this helps.
mikedyk43 said:
I have bricked my phone numerous times recently and have found a very simple way to recover from it, without even having to plug it in to the computer. The OTA leak found here: http://forum.xda-developers.com/show...php?p=23223061 can be put on the root of your SD card and installed using the stock recovery. Power + x followed by volume up/down, wipe data, wipe cache, install zip from sd and selecting the OTA zip. I have recovered several times with this and it is pretty handy to be able to do it where ever you happen to be. Of course you will still have to root and reinstall your other goodies, but it works.
Side note: This OTA leak can NOT be rooted with the standard D3 root methods. You must use the D4 root method to gain root privileges.
Click to expand...
Click to collapse
Good to know that you can try it from the SD. I may give that a shot as well. I have bricked my D2 over and over F'ing with it and have always been able to recover from it easily...figures that the first time my D3 does it and it tells me to go pound sand.
Thanks on the D4 note.
-
I'm setting this thing down for a day I need to take a step back so I can try the other file that gierso posted without throwing this thing against a wall.

Had this happen to my wife's Droid 3 and saw 1 post on another forum about a user it has happened to. After conversing with Motorola regarding my "Groundhog Day" issue (ie - no matter what you do, nothing changes on the phone... kinda like the movie Groundhog Day starring Bill Murray), the tech support reps came to the conclusion that somehow the NAND because write-protected. Neither RSD nor the Fast-FBZ nor Safe Mode would let me alter the phone in any way. I had to have the handset exchanged out under manufacturer's warranty...

Try on "AP Fastboot" mode
moto-fastboot -w
moto-fastboot erase system
moto-fastboot erase preinstall
moto-fastboot erase cache
moto-fastboot reboot-bootloader
now use the Psouza Fast/Easy unbrick.
If this does not help. than it would be better to go for a replacement.

[Q] Dell S10 Pro - Need help in Updating

Hi,
Sorry for posting in this as I couldnt find any thread for S10.
I have a S10 Pro with the following version of ROM installed.
Android 3.2
Build Version : 201107271412 (This is a strange as I couldnt find this in any other....)
Kernel Verrsion : 2.6.36.3-00055-gdb0a63d
Is it possible to update it to 569 or any custom ROM?
Thanks and Regards,
manakun

Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.

TheManii said:
Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.
Click to expand...
Click to collapse
Thanks for you prompt reply.
The OEM Version is GALLO1A155111
I havent used nvFlash but I shouldnt have problem using it. Will make a backup. I dont mind if it cannot be restored.
Awaiting your instructions.
Thanks,
manakun

I am yet to update S10.
Help appreciated.

Things you'll need to know:
How to use the command line
How to install drivers on windows
Windows vista or newer
Download usbNvidiaBootdriver.zip
Download NVflash.zip
Download 568 bootloader.bin
Put Device into APX mode
Hold down power and reset button
Install apx driver
Extract nvflash
Boot device into APX mode
Command to do so: "nvflash --bl <path to bootloader.bin> --go"
<path to bootloader.bin> is whereever you saved bootloader.bin to
Begin dumping each partition
Command to do so: "nvflash -r --read <N> <filename>"
<N>: number of partition to dump
Partition List - XDA wiki
Partitions we need to dump 551: 2, 3, 4, 6, 7, 8, 11
Filename is whatever you wish to name file, recommended to name them after their partition number, eg p2, p3, p4, etc
After you have it dumped please 7zip and upload somewhere
Updating to a different rom uses similar steps if you cannot use "check for updates" from inside rom
If you do not know how to use the command line, there are tutorials on the internet.
If you are using a x64 version of windows, you will need to put your device in "test signing mode" or "disable driver signature verification mode", there are also instructions on the internet.

Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.

manakun said:
Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.
Click to expand...
Click to collapse
Yes, try readimg here: http://forum.xda-developers.com/wiki/Dell_Streak_7/Flashing_Guide
Woops! This is for a S10 not S7!

the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear

TheManii said:
the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear
Click to expand...
Click to collapse
Thank you. I have entered into APX and able to get the content of the partition.
I have sent the uploaded link in PM.
I would appreciate if you guide me in flashing the official PKG.

Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.

TheManii said:
Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.
Click to expand...
Click to collapse
Thanks for the instructions. However I was not able to enter into recovery mode. Tried couple of times.
Advice appreciated.
BTW, is it possible to flash all the partitions manually using nvflash?

I assume you have a working recovery, you may need to be make sure the battery has enough charge.
I'm not positive, but the S10 might be like the S7 wherein it wont go into recovery mode if the battery is below 60%. Even if it is charged entering recovery takes multiple tries even if you're doing it correctly.
If you can boot into android, you can simply use adb.
Enable "android adb debugging" from settings, install the adb drivers (fastboot+adb.zip from the dev subforum) and do "adb reboot recovery" from the command line.
Adb.exe is included in the mentioned zip.
Then try again, if the recovery does not want to do a pkg update, i'll upload the 568 recovery and we can try after flashing that.
If that still doesnt work I'll keep providing more files until it does, i would like to avoid having the user (ie anyone else attempting to repeat this in the future) do a full flash.
I would strongly prefer figuring out the minimum steps needed to force update a S10, as fullflashes did far more damage then they helped for the S7 due to someone providing a fullflash including their device specific data and nuking dozens of devices that way.
Just as much I'm not sure you can flash bootloader.bin from nvflash on the S10, i've attempted it and it didnt stick. It could be user error and fastboot may be able to flash it, the rest should either be flashable or not relevent.
If it were not for the bootloader, I could simply provide 569 as an update.zip flashable with CWM/S10, but I dont know offhand if the 551 bootloader is compatable with 569 as it's android 3.1 vs 3.2.

I was able to reboot to recovery from adb.
I get "Version check not allow update" error when I try to update from 568/9 pkg file.
Is it possible for you send me the 568 recovery img? And would appreciate on guiding me on how to flash using nvflash.
BTW, The 551 I have is Android 3.2.

i will upload the 568/9 recs, if that still doesnt work ill upload 569 as an update zip and you can flash with cwm
edit:
568
bootloader.bin
recovery.img
569
bootloader.bin
recovery.img
to flash a recovery (or any file in general)
boot into apx mode
nvflash -r --download <N> <filename>
<N> is the partition number
<filename> is the path to the file being flashed
flash the 568 rec and try using the 569 rec, you can attempt to flash the bootloader if you wish.
Keep in mind that flashing the bl is seperate from using it to boot in step 1, that step only loads it into memory and is lost on reboot.
the partition numbers are in the wiki.
if none of these work i'll provide more files until it does

Thanks for the upload.
Didn't have any luck with 568/9 recovery.
Strange behaviour with S10...still getting the Version mismatch Error...
I have flashed Clockwork Mod 6.0.1.2 . Would really appreciate if you could upload the update.zip.
It should work with CWM(hopefully). Worst case scenario..should try manually flashing the required partitions.

I'll upload 569 as an update.zip, it wont help you for new released roms in the future, but who knows when dell will release another update.

Thank you. Thats alright. But I guess Dell wont be releasing another update for S10.

update-S10-Stock-569-1.zip
I do not have the original update script, though I believe I have a close approximation.
If there's any issue installing it let me know, you'll need either CWM or TWRP to install it, install those in the same manner as the stock recovery. Links are in the dev subforum, make sure you grab the S10 ones and not the S7 ones.

Thanks for the upload.
I have installed the CWM and flashed the zip as specified in the following link.
http://forum.xda-developers.com/showthread.php?t=1780133
However, the system doesnot load after the flash.
I get the Dell Logo and it doesnot boot.
Would appreciate your support.

Try these in order until something works:
Did you try fac resetting from CWM?
If that doesnt work, try flashing the 569 bootloader.bin again.
If that still doesnt work try flashing CM9mod (and fac resetting) (to see if anything boots)
If it still doesnt work after those, I'll upload an nvflash dump as a last resort
How far does the bootlogo go? Does it blink once? Does it go to the animated swirl?
Initial dell logo: cpu works
1st blink, to dell logo: kernel is loading
Animated swirl: android userland is loading

[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!

Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
PLEASE SEE "TROUBLESHOOTING" AT THE END OF THE GUIDE FIRST IF YOU HAVE PROBLEMS IN THE PROCESS BEFORE ASKING!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
VIDEO GUIDES
FOR LINUX METHOD CLICK HERE - Credits to @bx2_nero
Windows Method
Requirements:
Bypass Tools Pack - (SPFLASH TOOL, DRIVER AND BYPASS FILES)
Decrypted OFP (OPPO FIRMWARE PACKAGE) Files:
FULL FIRMWARE - INCLUDES THE "USERDATA" PARTITION, HENCE LARGER.
B.53 - Mega - Google Drive - Mirror3
B.37 - Mega - Google Drive 2
B.23 (First RUI Update for the device) - Mega - Google Drive - Mirror3
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
NOU (NO USERDATA) FIRMWARE - FOR PEOPLE WITH LIMITED DATA PLAN.
B.53 - Google Drive - Mirror 2
B.37 - Google Drive - Mirror 2
B.23 - Google Drive - Mirror 2
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
Please read an explanation of what is userdata partition and how different is this from other firmware here.
Note: All files with available links above are tested.
Python (Must add to PATH during installation, see screenshot if you don't understand)
libusb-win32 - Having Issues? Use this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure to choose the last option.
1)Open command prompt by running cmd,
enter
python -m pip install pyusb pyserial json5
After the installation, you can re-run the command. If it looks like the screenshot above you're ready to go to next step.
after the installation leave CMD.
2) Go to driver folder, find the .inf file right click and press install.
3)Download this file and install it, after installing plug your phone to PC by connecting your phone to PC while doing Vol+- . You might need this driver as well if it's not detected.
Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off) and you will see the mtkdriver down below. Install it.
Choose MediaTek USB Port and install it.
4)Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.)
If you had a problem here, please check the end of the guide for it's fix.
5)Go into Flash Tool folder and open the SPFlash tool, after that choose scatter file and also if not set, set your download -agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
After flashing it should look like this. Download has been complete. Enjoy!
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
Spoiler: TROUBLESHOOTING - FAQ AND FIXES
POSSIBLE ERROR: "Verified boot enabled."
There are 2 fixes to this.
1st Method (DIRECT FIX):
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
2nd Method (WORKAROUND):
If you're getting this error, and you are SURE you used "Download Only" mode, there's a way to get rid of this. First, load the scatter then untick/deselect partitions listed below.
opporeserve2,
cdt_engineering,
my_custom,
special_preload,
userdata,
super,
After running brom.bat and flashing all partitions except the ones listed above, your phone will be able to reboot to stock recovery. Now select " Power Off" option then go run brom.bat, bypass authorization and then flash partitions listed below from SPFlash Tool.
super,
dtbo,
userdata
Your device will be able to boot into system after this if you have followed steps correctly.
POSSIBLE ERROR: Issues while disabling protection;
Power off your device Restart the process from 2nd step.
POSSIBLE ERROR: Issues while flashing;
Power off your device, you will need to do the bypass again. Check your USB Cable, there might be a disconnection. If not, start from 3rd step and make sure you did everything right.
Spoiler: FOR PEOPLE WHO WANT TO DOWNGRADE AND FOR PEOPLE WHO WERE ON EU VERSION
So, welcome to hell(!).
For people who want to downgrade:
If you want to downgrade to any version you would like, just use the B23 file as it is the oldest ofp file i could find for extracting process. If you were on EU version before (Any version starting with A) download ozip from here(for EU) , here(for Global) and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
For people on EU who want to unbrick:
So, you can use any version starting with B and it should work. It works in my case, i was on A.48, i flashed B53 and over that flashed B23. No probs at all. If you want to return to EU rom (starting with A) download ozip from here and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
Thanks --
https://github.com/bkerler/oppo_decrypt for decryptor.
https://github.com/MTK-bypass for creating the tool.

Thank you for your efforts. Can you add the decrypted A34 file?

mercan01 said:
Thank you for your efforts. Can you add the decrypted A34 file?
Click to expand...
Click to collapse
Hello! I wasn't able to find factory package (ofp) files for any version that makes sense for versions starting with A. (EU). There are A11 and A08 which according to update trackers, did never exist and the A.11 package is %50 larger than all the other files weirdly. I have contacted owner of some sites that do upload files like these and they asked for money. If it's a resonable price i will get it, decrypt it and upload here! If you were able to find any versions starting with A, feel free to message me on telegram (@ctivity) or email me!

Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.

mercan01 said:
Hi, I have a website that publishes A24 version only. https://www.getdroidtips.com/realme-6-software-update/. It gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello again. According to the site you have just sent, A.11 is the first update to EU version. I was thinking it was a mistakenly uploaded file, since userdata partitions are for some reason 9gb with this one instead of 3. If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work. Unfortunately, these files you sent in the link are ozip files and update packages while ofp files are firmware packages and they include everything. There are only 2 ofps -decrypted and not decrypted- available for now starting with A(EU), A08 (first ever firmware for EU) and A11(first update to EU version).

Hello again. Yes, I noticed there was an ozip file and deleted it.

daeSundae said:
If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work.
Click to expand...
Click to collapse
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?

cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
Hello! I'm sorry for the inconvenience I have tried flashing A11 file and it caused several problems just like in your case, however if you didn't select "Format All+ Download" mode you should be able to recover your phone. So, I had the exact same issue today and due to that I will be removing the A11 file from the links. Also, never forget to select Download Mode only! Several people bricked today and their IMEIs, Serial Numbers are all gone! Never select anything else than Download Mode!
So the solution is to download B53 decrypted files, load the scatter and untick listed partitions
opporeserve
,cdt-engineering,
mycustom,
special-preload,
userdata,
super
and then start the flashing in download mode. Now, you might be wondering "How am I going to go into the download mode again?" It's very simple. All you have to do is to keep pressing on Power and Vol- for some time and then, connecting to the pc with both volume buttons pressed while brom.bat is running. If you get an error, just reinstall device filters and that should fix the problem, then you can start downloading. After downloading these partitions to the phone, you will be able to see a boot animation and as well as a realme logo. Reboot to recovery, power of your device and then go into download mode again and flash userdata, dtbo and super partitions this time around. It should boot into system. However, the version will be B.53 but you can use the latest ozip (A.48), flash it from recovery and then format your data. It will bring you back to EU version.

cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
So, i just read your reply again.
"Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device."
i dont think it's an issue caused by the device. Can you install oppo drivers from this link and let me know what happens afterwards? Or if you're fast enough you might prefer going into device manager by right clicking on Windows button and uninstall it's driver? I will also request you to start from step 2 to ensure installing drivers. I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.

mercan01 said:
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello! I have uploaded B23 files both on google drive and mega. It should work for you, it is working for me at the moment. I also was on A48 firmware and both B23 and B53 versions worked without a problem.

daeSundae said:
I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
Click to expand...
Click to collapse
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.

cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt. Do you know if your phone has any charge or not? Can you try different volume and key combinations? A broken firmware shouldn't make the BROM Download mode inaccessible.

cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to
use "fastboot reboot" command. Please keep pressing vol - button if you can while rebooting if it works. That should, if possible reboot you into recovery.
Also as you said, keeping pressing on power and vol+ buttons don't work in this state. In fact, in this state nothing visually works, there is no screen output and I'm actually pretty sure it's the same for begonia (RN8 PRO). You will need to ~ if it's detecting it as a fastboot device need to use minimal ADB and fastboot tools to get rid of that state. I didn't have the same issue as you though. While I was in same state, I kept on pressing on Vol - and Power buttons for around 30-40 seconds (obviously without a response from the device) and after that pressed both volume buttons and connected device to PC. Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.

MTK Bypass Universal
My screenshots were used in this post. I don't mind

MEGAFON929 said:
MTK Bypass Universal
My screenshots were used in this post. I don't mind
Click to expand...
Click to collapse
I'm sorry for not letting you know Dinolek. I tried to create a guide but my Windows is Single Language and since it's not global version or something I cannot change its language. I had to find an English screenshot. If it's a problem, I'll just remove them.

No, I'm not Dinolek. I just talked to him and he accepted my instructions. Let the screenshots lie, I don't mind.

Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt.
Click to expand...
Click to collapse
Sounds reasonable and I hope it's true.
daeSundae said:
Do you know if your phone has any charge or not? Can you try different volume and key combinations?
Click to expand...
Click to collapse
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
daeSundae said:
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to use "fastboot reboot" command.
Click to expand...
Click to collapse
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
daeSundae said:
Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
Click to expand...
Click to collapse
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...

cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Can you try ADB reboot command on Linux? As it is identifying as a fastboot device?

cmfan said:
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Click to expand...
Click to collapse
If it's detecting a fastboot device, the device isn't dead. What I'm guessing is that your device is working, and on fastboot mode but since there's no display output in this state it will only show a black screen. Can you do ADB devices command? Im guessing adb reboot requires authorization though, but it's worth trying. What I will be requesting from you is to try pressing (and keep pressing on) different key combinations while device is in that state for like a minute or so, for example keep pressing on Vol- and power for a minute then switch to Power and Vol+ for a minute and then keep pressing on both volume buttons and connect device. Can you also see the results after plugging your device into charge and letting it stay for around a minute? I know these might make no sense technically, but in my opinion randomness is your best friend to get rid of situations like this..

cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Hello. again. So, i have asked few people about your situation. Conclusion is, if none of these work you will need to wait until battery wears off and device turns itself off, i'm afraid. I will ask you to not use your phone for like a day and not to keep it connected to a computer for a long time. After making sure it powered off (which, i'm guessing there is actually no way to do that) make sure to prepare the brom.bat file plug in your device with VOL+ - combo and go on. Before doing this make sure to Device Manager > Action > Add Legacy Hardware > Next > Install the hardware that I manually select from a list (Advanced) > Show All Devices > Have Disk > Choose the cdc-acm.inf > Choose Mediatek USB Port and install it to not waste time. I hope your problems will be fixed. I have confirmed that BROM mode shouldn't fall into an inaccessible state because there's no efuse.ini blown. It must be there, but you're probably stuck in a mode that doesn't allow doing anything for some reason.

How To Guide Full recover to stock - If things went really bad :)

Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper

Do you believe this could help with the ram dump issue?

There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip

Blumi511 said:
Do you believe this could help with the ram dump issue?
Click to expand...
Click to collapse
I have no idea, but I think it can't get worse by trying it.

Flashing the firmware (so called "RAW"-firmware) that allows one to turn back to A11 on the A12 beta page, should get back every device back to a working condition if the problem isn't hardware or extremely messed up in the few partitions that the raw doesn't flash.

I tried using this method to get back to stock from OmniROM, but after several reboots, the phone is stuck in fastboot mode. I tried booting normally and recovery mode, and it immediately goes back to fastboot mode. Any ideas?
/Edit: Got it to boot by flashing Lineage recovery, rebooting into it, and doing a factory reset from there.

HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...KS-30.11.51.115-MR0-user_20210826-release.zip
Turn of your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
# Thanks to NisseGurra for the link to the latest RAW image.
Click to expand...
Click to collapse
Thank you very much! This safed my phone! I stupidly flashed the boot image from a different build and wasn't able to boot. Only your flash.cmd worked! I hat to comment out the hardwareid check though, because mine was 0 somehow.

I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.

amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This could also be just an issue with the fastboot drivers. Try reinstalling them, also clearing up orphaned devices in device manager could help.

amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This is a known issue with Windows 10 computers. They have some sort of signature check where even if you install the correct drivers, they don't really get "installed" because of this check. There is a workaround for this though, I'm not sure how.
However, if you have a Win 7, Vista / 8 PC, adb and fastboot will both work flawlessly with no hassles (experienced personally).

NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Where do you get latest RAW links from?
I could not find them via Asus site.

HyperCriSiS said:
Where do you get latest RAW links from?
I could not find them via Asus site.
Click to expand...
Click to collapse
A12 beta page. The firmware that allows you to go back to A11

NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.

Yippee38 said:
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Click to expand...
Click to collapse
Works for me.

is there a newer image out?

it would be good if there is a full raw android 12 image posted...since android 12 is released now.

Hi there,
Installed LineageOS 18.1 yesterday because my phone was having awkward moments, I want to go back to RAW stock, but I can't finalize the install.
I followed OP's instructions, but I never could find the flashall_AFT.cmd from the extracted archive.
Anyway, i managed to use LineageOS Recovery, but it requires signature at 47% , and when I press Yes, it says :
E:error: 21
Installing update...
E: Package is for product ASUS_I006D but expected sake.
Installation version
Installation tried : UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip.
When I tried WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, it required signature after 0.2 seconds, with following message :
E:footer is wrong
update package verificationtook 0.2 s (result 1).E:Signature verification failed
E:error: 21
Installing update...
E:Open failed: /metadata/ota: No such file or directory
E:Couldn't mount Metadata.
E:Failed to find update binary META-INF/com/google/android/update-binary.
I resetted before launching above operations, everytime.
What can I do to go back to Asus RAW Rom ?
Forward thanks and best regards.
EDIT : OK, found it, I just had to extract the .zip file. I thought I had to flash it like any image.
My bad.

HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thank you so much! You saved my phone! The only thing is that I couldn't find the flashall_AFT.cmd file in the new image, I had to use the WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, and it worked perfectly. After I flashed the boot.img trying to get root on android 12 several times, my phone was in a ram dump state.

HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thanks! This helped me after I got into a ramdump situation. I flashed a rom and a boot image through the bootloader instead of fastboot and got things corrupted.

On my Asus Zenfone 8, I upgraded from Lineage OS 18.1 to 19.1.
When I wanted to flash gapps and did a reboot into recovery, since then the device no longer works.
I can't get into recovery and I can't get into fastboot mode.
When I turn off the device and turn it on again, the following appears on the screen.
Waiting for flashing full ramdump...
PLS help me

Question Motorola Edge 20 - "Confidential Property" Device Boot Loop Issue after Flashing Recovery

Hello XDA Community,
I recently purchased a Motorola Edge 20 for just 150€, which seems like a great deal. However, there's a catch: the display shows "Motorola confidential property, not for sale." The device had developer mode on and an open bootloader by default, and some features were still buggy. Since all the hardware components matched the retail version, I decided to try and flash the retail OS to get a more stable system.
I first tried to flash the system via a ZIP file, but I encountered a signature issue, which I now realize was due to my limited knowledge and inexperience in flashing ROMs. Next, I attempted to flash a recovery file that I found online by running the command "fastboot flash recovery recovery.img." The process seemed successful, but it resulted in my device getting stuck in a boot loop.
After more research and troubleshooting, I found a script on XDA forums that I ran with firmware that was supposed to be original, and that got my device back into a boot loop. The recovery.img is not present in that firmware. When I try to boot the phone now, it displays "booting into recovery mode" at the top and then reboots (possibly because the recovery file is broken). I tried other firmware files such as LineageOS and PixelExperience recovery, but I always encountered errors while attempting to upload the recovery file.
While attempting to flash the PixelExperience recovery, I encountered the following error message:
Code:
C:\Users\marti\platform-tools>fastboot.exe flash recovery PixelExperience_Plus_berlin-13.0-20230112-1838-OFFICIAL.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 100663296).
Sending 'recovery' (98304 KB) OKAY [ 2.377s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
It appears that the bootloader reports an "Invalid partition name recovery" error. I suspect this might be related to the device being a "confidential property" version of the Motorola Edge 20, which might have a different partition layout or naming convention. The bootloader is still unlocked.
With all this information, I hope that someone can help me understand what went wrong and how to fix this issue. I would appreciate any guidance on flashing the retail OS to my Motorola Edge 20 without causing further problems or finding a compatible recovery file that will allow me to boot the device successfully.
Thank you in advance!

Hi, this problem was because there is no sector named "recovery" in Edge 20. I followed the LintageOS instructions again and got the phone into LintageOS recovery. However, after installing and updating the phone via ADB, I got the phone hard-bricked. Honestly, I don't know why, but I might have broken something much earlier in the process. Tip for future me: prepare in advance.

Sounds like you got your hands on a dev device of some sort. Try making your own update script, follow these instructions (you will need to add a few more script lines depending on your system version):
If for some reason you cannot boot into recovery mode at all, there is a Qualcomm recover tool that I found out about the hard way after bricking my device too. If you plug your phone into your computer and the computer makes a sound that it recognizes a new device then you can probably recover it. I don't remember where to find it since I too found it by chance after desperately searching the internet, so you're on your own for that.
I forgot to mention you can get ROMs on sites like lolinet but I can't guarantee integrity. Also, if it is a dev device then the IMEI might not be valid, so it might be illegal to use or it might not be functional with any SIM card, so careful what you do with it. I don't know how to check for IMEI. Maybe try the RSA tool and input your IMEI there and see if it gives you a software to download (the IMEI can be found on the inside of your SIM tray).