Asus Android 11 Beta semi-bricked my phone - Urgent help needed - ASUS ZenFone 7 / 7 Pro Questions & Answers

My phone is pretty much bricked. I cannot do anything with it.
So I installed the new update & now my phone keeps resetting to "No service" every second, then going to my Local carrier Telstra (Australia) 5 bars of reception, then resetting to "No service" again every second and repeats this non-stop.
On top of this, phone overheats so much and when I try to turn off the phone, it turns right back on again!
I can no longer call, message, use my data. I urgently need my phone back for work tomorrow morning.
com.android.phone keeps stopping error also appears at the start when I boot up my phone.
Before the update, I never had any issues.
So I guess the only way for me to fix my phone is to revert back to original asus stock firmware?
Ive tried asus own asus recovery using power button and volume up:
ive tried putting update.zip inside internal storage, but mount sdcard error shows up.
so, i try adb method, works and starts flashing and then.. it says the update.zip is older than the current firmware, and stops it halfway.
what are my options/how I can return to the stock original global rom from this nightmare android 11 beta to android 10 firmware? i have the official asus android 10 firmware already and unlocked bootloader..

try flash raw firmware you can find in google. tries to flash raw firmware. you can find it on google i think. Use the file flashall_AFT.cmd

when i google raw firmware, this shows up the drivers and firmware from official asus zenhelp shows up.
is this correct? i have downloaded it, however not clear as to what steps and additional programs are needed from here.

MystikMan97130 said:
try flash raw firmware you can find in google. tries to flash raw firmware. you can find it on google i think. Use the file flashall_AFT.cmd
Click to expand...
Click to collapse
Hy, I flash raw firmware (https://mega.nz/folder/PzpVnQIQ#GPIFAeG8ntvFb6vGfcDTTQ) with the file "flashall_AFT.cmd" and now i'm unrooted and lock bootloader. PERFECT & THANKS YOU ALL

Do you know if ZS670KS (Zenfone 7) raw firmware works on ZS671KS (Zenfone 7 Pro)? I have the Pro maybe the post author too

Hey OP, where did you purchase it from? I'm from Australia too and just got my Zenfone 7 Pro delivered. And how did you receive the Android 11 update? OTA? I'm reluctant to OTA update as the last one on a new Zenfone 6 I bought bricked it too!

MystikMan97130 said:
Do you know if ZS670KS (Zenfone 7) raw firmware works on ZS671KS (Zenfone 7 Pro)? I have the Pro maybe the post author too
Click to expand...
Click to collapse
I have 7 pro too, and on the Asus Website under the firmware tab they say this:
Version WW-29.12.18.16
2020/09/142.56 GBytes
ZenFone 7 / ZenFone 7 Pro (ZS670KS / ZS671KS) software Imageļ¼šWW_29.12.18.16 for WW/EU only*
(https://www.asus.com/Phone/ZenFone-7-ZS670KS/HelpDesk_BIOS/)

Related

Tricked into buying an 'official' modified phone?

Can anyone help me? I have an ASUS Zenfone 6, I checked my device settings and everything from the 'about' menu at settings and it says I have a 1.16 WW firmware. When I downloaded the newest 1.18 WW firmware from support.asus.com and tried to flash it says:
Device image SKU: CUCC
OTA image SKU: WW
And the update fails
I am honestly confused to what's going on here. I thought I have WW with gapps and everything working but suddenly when I try to update I have CUCC? Oh and what's weird is that when I just got the phone SuperSU was synced from my previous phone and I just wanted to check out what happens if I open SuperSU without rooting but when SuperSU opened it asks me whether I want to update the binary normally or from CWM/TWRP! This mind you only happens if you had rooted the phone and ran SuperSU for the first time, surprisingly according to root checker I have root! JUST BY INSTALLING SUPERSU! So I was wondering if my phone was tampered before I bought it? I legally bought it new from a nearby mall with it still complete with the packaging and warranty card, so I'm really confused to what is going on.
Can anyone please please help me, do anyone else who has the WW firmware has anything like this happen when you want to flash the firmware update? I tried to force the firmware update using fastboot, nothing changed, but now my phone won't detect my SD Card and every time I open settings the phone would restart. The only way I can think of to fix this is by flashing a fresh ROM but so far I cannot find a link that has Zenfone 6 stock ROM, only the firmware. I've thought of returning the phone with the reason that I got tricked into buying a CUCC Zenfone instead of the WW that is sold on my region.
Note: I bought the phone in Indonesia and basically there are 2 warranty. One from the official ASUS and another from 'distributor', because the distributor is cheaper I bought that one thinking I'm only having a different warranty and a lack of support from ASUS officials but is it possible this distributor actually sell a modified CUCC SKU that is changed to WW? I've seen some articles/video to switch from TW/CN to WW and it kind of raised my suspicion.

GUIDE: How to FLASH and RESTORE your STOCK firmware on the TA-1054 (and others)

It seems like there are a few people having trouble going back to stock and getting everything working.
As always, this requires an unlocked bootloader. If you don't have an unlocked bootloader then search google for a $5 service that does. It is what I did.
I flashed Project treble on my TA-1054. It worked great except it kept saying "insert SIM" when there was already a sim card inside, so I could not use it.
I tried to go back to stock but that firmware file on that google drive thread was corrupted, bad upload. Took me a few days to source this original firmware.
There is a tool called OST ( around 115MB), and a patch that comes with it (the smaller file less than 1MB)
The firmware is almost 2 GB
Download everything, including firmware.
1. Install the OST tool.
2. Replace the EXE file in the program files with the patch file you downloaded.
3. Delete the Onlineupdatetoolexe.config file. If you don't do this, the program will not start correctly.
4. Put phone into download mode ( either by powering it off, pluging into USB cable and immediately hold power and volume down. Or if you can boot into android with ADB debugging, just do a adb reboot bootloader.
5. Pick firmware file and click next.
THe first 2 times I tried this, It hanged at the last second. Third time was a charm. Give it time. Use a good USB cable.
I assume that this is the same way to flash other firmware files for other devices.
As soon as i get my hands on a android one firmware, I will flash it.
Or if anyone can guide me on how to extract the firmware on my TA-1045 USA version and flash it to my TA-1054 Chinese , let me know. Cheers.
Google drive folder with all the files I uploaded.
https://drive.google.com/open?id=1NbzO6lfSGacjM2wqrtBg3jMpljsZswne
Thanks bro...I am downloading it.
PL2-2380-0-00WW-B01.NBx.zip is global firmware name. firmware size is 4gb.
thanks! for extract is with nb0 tools FIH Mobile v3.4
https://drive.google.com/open?id=1cSgjrZUxIsN7oLbo7AP-RnILDZdswmB-
its android one firmware. I have no tool for flash...plz try and let me know
Flashing now. Will report back after flashing is done. thanks!!
Edit: Looks like the version I have for OST does not read NBX files. Will try to update that and report back. I have ntool but no working username password
I cannot flash the NBX file. I changed it to nb0 but OST LA says cannot read firmware. Is there any other way to flash?
EDIT: I went ahead and purchased a bunch of credits for NTOOL.
I will flash and see if it works!
It fails with the mdtp.img partition (no such partition) . I would think that it would just skip that partition but it did not. I will later try to extract and flash separately
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
stealthj said:
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
Click to expand...
Click to collapse
can u flash my chinese rom which is nbo format via ntool. I have have ntool but i dont have user name,password, i downloaded rom which u provide.my device still cant connect to mobile data.
NBX format only works on Ntool. but Ntool needs working user name and password to works. OST cant read or flash Nbx format.
if u get Ntool with working user id .. then plz flash my device also via remote mode like teamviewer.
Ntool Bricked my device. the only real restore you can do is by using ost with the stock chinese firmware. edit your apn. why is your data not working?
Global rom cant flash via ntool in Ta1054..showed error in partition. if it will be solved then china to global will be easy process..
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
safron35 said:
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
Click to expand...
Click to collapse
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
stealthj said:
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
Click to expand...
Click to collapse
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
TheImpulson said:
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
Click to expand...
Click to collapse
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
stealthj said:
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
Click to expand...
Click to collapse
How to flash it?
Edit: Also OnlineUpdaterTool in your 1st post asks for a password. What's the password?
nooby_pls said:
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Click to expand...
Click to collapse
I put the original chinese firmware on the first post.
There is an option to install google play store, but that would make your rom unable to receive updates.

Unable to get back to A 10 after Oneplus flashed A9 to device

I am trying to get my phone back to the original A10.
I had an issue whereby the fingerprint sensor would not work properly and assistant wouldnt respnd to teh the wake wordand I was constantly resetting the phone to get it to work properly so I contacted oneplus support who said that it was best for them to flash the phone and in doing so they have flashed Android 9 and are now saying they cannot flash to Android 10 for me and I have to wait for an update on EE to get back to Android 10 which is stupid
having spoken to EE say have said this is a oneplus issue
oneplus support has been shocking what can you advise me
I have already tried the local upgrade process where I have downloaded the Android 10 file and copied it to the root of my device but when I go to system updates the phone will not see the file no matter what I do
I have already tried the local upgrade process where I have downloaded the Android 10 file and copied it to the root of my device but when I go to system updates the phone will not see the fine no matter what I do
I have also tried to get the phone to force an OTA update but that does not work either
please help
bartjunited said:
I am trying to get my phone back to the original A10.
I had an issue whereby the fingerprint sensor would not work properly and assistant wouldnt respnd to teh the wake wordand I was constantly resetting the phone to get it to work properly so I contacted oneplus support who said that it was best for them to flash the phone and in doing so they have flashed Android 9 and are now saying they cannot flash to Android 10 for me and I have to wait for an update on EE to get back to Android 10 which is stupid
having spoken to EE say have said this is a oneplus issue
oneplus support has been shocking what can you advise me
I have already tried the local upgrade process where I have downloaded the Android 10 file and copied it to the root of my device but when I go to system updates the phone will not see the file no matter what I do
I have already tried the local upgrade process where I have downloaded the Android 10 file and copied it to the root of my device but when I go to system updates the phone will not see the fine no matter what I do
I have also tried to get the phone to force an OTA update but that does not work either
please help
Click to expand...
Click to collapse
Flash OOS via MSM
Would this void my warranty
Does my device news to be rooted
I have the official 10 update O too
Just had a look can't find OOS rom which one is it please
https://forum.xda-developers.com/on...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Google it next time a litlle bit..and btw wrong thread

Question How do you change/update stock firmware (downgraded after recovering via EDL)?

I recently bought a ROG Phone 5s here in Japan, and it came on the WW-18.1220.2111.164 firmware.
I got into a bootloop trying to mount as readwrite, and the problem got worse until I was at a seeming brick with black screen. But I saved my phone using johhny886's guide here.
Upon flashing the firmware he provided, my phone is now back to normal but on WW-18.1220.2109.126.
System update checks and says "Your system is up-to-date." I tried a factory reset and interestingly it keeps me on WW-18.1220.2109.126.
WW-18.1220.2111.164 is downloadable from ASUS's website here and it comes in a zip file. How do I manually install this? Or can I?
There is also a newer WW-18.1220.2112.175, but it says "This firmware is only for ROG Phone 5S/5S Pro ID version". I thought about going to this newest version but that message scares me since I don't know what ID is here. WW-18.1220.2111.164 listed as "WW-18.1220.2111.164 for WW/EU/TW/JP version only." Device's country is listed as JP so I figured it's safer to go back to this.
Place that zip file you have downloaded in your phone internal storage (not inside any folders). Once you have placed it in the root of your internal storage just restart your phone. After restart unlock your phone and it will automatically detect that update file within a minute and ask you to update.
The ID version is Indonesian version. So choose JP version for you always.
I just did that and successfully updated as you posted. Somehow as soon as I go to post online I figure stuff out lol.
Thank you for the assistance, I was afraid and wanted to be careful.

Question OnePlus 9 cannot update from 2113_11_C.60

Hi all,
I have a weird issue - I have updated my OnePlus 9 EU last year over Oxygen Updater, but managed to install India-only update on EU phone and now in settings it shows 2113_11_C.60.
After scouring internet I found that C.60 was India only update.
Now, I haven't received a single auto update since May 2022.
I have tried downloading incrimental updates to C.62 both for 2113 and 2111, but neither local upgrade nor special oneplus app was not able to update.
Also tried full install of C.62, no success.
Even tried full upgrade to latest EU build LE2113_11_F.75 - same result..
The local upgrade through settings constantly shows "verification failed" no matter what file I choose.
OP's System Update app would fail after showing system updating for a minute, with 0% progress.
As I understand, I somehow managed to install Indian version of incrimental update on EU phone, but now I am stuck on it.
What are other reinstall options on OnePlus 9?
Can I somehow force install if I connect over PC?
Many thanks for the help!
EDIT:
Forgot to attach screenshots...
Index of /list/Unbrick_Tools
Find the one compatible for your device whatever stock would be and run the msm recovery tool. This will get you back where you need to be to be able to update to latest software.
Otherwise you can try editing the file payload_properties.txt inside the update zip and changing oplus_update_engine_verify_disable to 1. This way your phone should skip the verification process entirely. Keep in mind that this could still result into bricking your phone because of this unintended update path but since the alternative would be using MSM tool why not trying anyway.

Categories

Resources