Database Users

[Q] Help, stuck in bootloader

I have two Defys. One flashed ok and works fine. But not the other one. I flashed stock 2.2 (can't remember which exactly), but on the second phone it was somewhat unstable, slow, throwed UUID inconsistency errors... It was rooted just after flashing, so I don't know exactly if it was problem of sbf or root. And I couldn't get into recovery menu to wipe. Since on the first phone everything worked fine, I thought something went wrong and re-flash will help. So I flashed the same sbf, and it didn't boot at all =| It always boots into bootloader, which says
Code:
Bootloader
09.10
Code Corrupt
Battery OK
Ok to Program
Transfer Mode:
USB
Tried other firmwares, but RSD Lite says
Code:
Phone[0000]: Code Group 32 checksums match.
Phone[0000]: Error verifying Code Group 33 checksums. File: 0x9D6, Phone: 0x4805
[...]
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
While on the phone's screen there is the following message:
Code:
SW Update
In progress...
Tried to flash just bootloader, same errors... Tried to change cable and even computer — no luck =[
So I'm pretty confused =| Is it software or hardware problem? Can I send it back to seller to fix it? What can be done?

Hey me too!
I'm also stuck in here...
I hope that there are some method to solve this ploblem

If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz

ifu said:
If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
Click to expand...
Click to collapse
nothing happens here pressing vol+/- at the same time... if I tap the lower right corner I see the normal recovery, it's what you're referring to?
ifu said:
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz
Click to expand...
Click to collapse

ifu said:
If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz
Click to expand...
Click to collapse
This act I know...but not in this case
Firstly I can't go to recovery mode moreover..(even I hold vol down + power how long..)
Then I can't go on the step as you listed...
I just stuck in Bootloader mode automatically when i put in the battery..
Is there any reset solution or some method to fix the "Error verifying Code Group xx checksums"?
Thanks

kix_k9 said:
This act I know...but not in this case
Firstly I can't go to recovery mode moreover..(even I hold vol down + power how long..)
Then I can't go on the step as you listed...
I just stuck in Bootloader mode automatically when i put in the battery..
Click to expand...
Click to collapse
Exactly. It does not boot, going straight to bootloader and no futher, regardless of the buttons I'm pressing.
But one day the miracle has happened I routinely connected the phone to my laptop, preparing to flash it one more time. Inserted half-charged battery from my second phone, just as usual. But before I started RSD I was shocked by vibration meaning my "bricked" phone had booted just fine!
I launched Clockwork recovery and installed its recovery system. However, when I tried to boot into it, it didn't and booted as usual. I tried once more with the same result. Then I tried to boot into default recovery menu (power + volume down) and succeded. As I had those UID errors messages, I decided to wipe as those messages suggested. After that completed and my phone booted successfully (being a triumph as I considered it to be dead), I still got those UID errors =\
I booted into bootloader to see if there is still "Code corrupt" error, and to my pleasure, it wasn't. Nothing to lose, I thought, and tried to flash 3.4.3-11 SBF. And... now I'm back in bootloader with "Code corrupt" error and without any idea what's happening =| But at least I know the phone can boot (and can't figure out how to make it do so =)) Will do more research soon.
P.S. Curiously, RSD couldn't detect "resurrected" phone unless in bootloader (my second phone is deteted even being not in bootloader), and I don't remember exactly, but I think I couldn't turn it into USB mass storage mode — it just reverted back to Motorola Phone Portal mode.
Any ideas?

Hi Shevchuk
I had the same problem a couple of weeks ago that my defy stuck on that screen and I wasn't able to flash it.
As my Defy was rooted I tried it to fix it at my own. I tried a lot, different PCs with different OS and different versions of RSD but nothing worked. So I decided one day to call the motorola support hotline and told them that it got stuck on that screen without mentioning that it was rooted and that I tried to flash it. Finally, they told me to send it in.
After two weeks I got my Defy back and it was working. They said that something was broken and exchanged that part

Code Corrupt is not a pds problem... but a simple "bad flash" problem
pds one will reboot the device after logo...
for pds problem :
if you have 2 defys you can maybe do it...
first you need to flash the same SBF on both devices
then with adb shell (as root) you need to extract the fully working system partition (with the signature flag) :
dd if=/dev/block/system of=/sdcard/CG39.ext3.smg
this image will be mountable (and modifiable) on a linux machine :
mkdir ~/system
mount -o loop -t ext3 CG39.ext3.smg ~/system
cd ~/system
you will be able to install bootmenu inside the image, then repack a sbf with this "tuned" CG39... and to lock boot before the /pds check, which can reboot device
and with bootmenu, you can flash cm7 with the recovery

I have the same problem code corrupt but nothing to ay

crub55 said:
I have the same problem code corrupt but nothing to ay
Click to expand...
Click to collapse
Did anyone of you ever find a solution I have the exact same problem.

I have same problem
Epsylon3 said:
Code Corrupt is not a pds problem... but a simple "bad flash" problem
pds one will reboot the device after logo...
for pds problem :
if you have 2 defys you can maybe do it...
first you need to flash the same SBF on both devices
then with adb shell (as root) you need to extract the fully working system partition (with the signature flag) :
dd if=/dev/block/system of=/sdcard/CG39.ext3.smg
this image will be mountable (and modifiable) on a linux machine :
mkdir ~/system
mount -o loop -t ext3 CG39.ext3.smg ~/system
cd ~/system
you will be able to install bootmenu inside the image, then repack a sbf with this "tuned" CG39... and to lock boot before the /pds check, which can reboot device
and with bootmenu, you can flash cm7 with the recovery
Click to expand...
Click to collapse
I have same problem and i can't slove it please help me follow this quote.
I have one defy and I don't know how to do it.

Please ask all questions in the Q&A section. Thread moved there.

Worked For Me
Shevchuk said:
I have two Defys. One flashed ok and works fine. But not the other one. I flashed stock 2.2 (can't remember which exactly), but on the second phone it was somewhat unstable, slow, throwed UUID inconsistency errors... It was rooted just after flashing, so I don't know exactly if it was problem of sbf or root. And I couldn't get into recovery menu to wipe. Since on the first phone everything worked fine, I thought something went wrong and re-flash will help. So I flashed the same sbf, and it didn't boot at all =| It always boots into bootloader, which says
Code:
Bootloader
09.10
Code Corrupt
Battery OK
Ok to Program
Transfer Mode:
USB
Tried other firmwares, but RSD Lite says
Code:
Phone[0000]: Code Group 32 checksums match.
Phone[0000]: Error verifying Code Group 33 checksums. File: 0x9D6, Phone: 0x4805
[...]
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
While on the phone's screen there is the following message:
Code:
SW Update
In progress...
Tried to flash just bootloader, same errors... Tried to change cable and even computer — no luck =[
So I'm pretty confused =| Is it software or hardware problem? Can I send it back to seller to fix it? What can be done?
Click to expand...
Click to collapse
I know i might sound stupid. But i had the same problem, i kept my phone untouched for a few days. And after that i usually came to try another SBF file but my phone Turned on magically, I still dont know how it happened, but it did. There is some way to fix it, but cant figure out how.

Did anyone find a solution to this problem??

I need a help!! milestone 2 A953

Hello, i'm a big problem for my motorola milestone 2 A953, I apologize for my language and my mistakes.
Hello, I recently purchased from eBay Milestone 2 has an English menu and is purchased in the UK, I wanted to upload to the new software CM9 best unless it can not be CM7, and right now I have a problem namely
I have bootloader 70.13, upload the file to the memory card from the CM9 and GAPPS bootloader fires (up arrow + power) via USB to the PC turn on RSD lite version 5.x choose the file with the extension *. SBF and then kicks me out of 100% and I turned on the phone once again turn to the new bootloader and shows the pass. My next step holds the power and turn off phone and then I hit 'x' + power and shows me a screen with an exclamation point in a triangle and android humanoids press volume + camera and then a magnifying glass on the keyboard and nothing happens no fires are no menu is the same I'll do it but as I press the @ button on the keyboard or anything, no menu: (
I did everything the instructions that I found on forum
http://forum.xda-developers.com/show....php?t=1338183
1) Install Bootstrap Recovery Droid2
2) Boot into recovery
3) OPTIONALLY: create a backup of your data
4) Choose Install zip from sdcard -> Choose zip from sdcard and select downloaded ZIP file.
5) OPTIONALLY: install Google Apps the same way
6) Wipe data / factory reset
7) Wipe cache partition
8) Reboot and enjoy
9) OPTIONALLY: use attached Baseband app switcher if you have troubles with phone signal.
all worked out, but when I went passed the phone rebote motorola logo and nothing else happens. I do not know how to solve this problem.
I can not run the recovery menu. I can only enter the bootloader version is 70.13.
I would like to upload the software from the Polish language.
Thanks for help.

lukasz0318 said:
Hello, i'm a big problem for my motorola milestone 2 A953, I apologize for my language and my mistakes.
Hello, I recently purchased from eBay Milestone 2 has an English menu and is purchased in the UK, I wanted to upload to the new software CM9 best unless it can not be CM7, and right now I have a problem namely
I have bootloader 70.13, upload the file to the memory card from the CM9 and GAPPS bootloader fires (up arrow + power) via USB to the PC turn on RSD lite version 5.x choose the file with the extension *. SBF and then kicks me out of 100% and I turned on the phone once again turn to the new bootloader and shows the pass. My next step holds the power and turn off phone and then I hit 'x' + power and shows me a screen with an exclamation point in a triangle and android humanoids press volume + camera and then a magnifying glass on the keyboard and nothing happens no fires are no menu is the same I'll do it but as I press the @ button on the keyboard or anything, no menu: (
I did everything the instructions that I found on forum
http://forum.xda-developers.com/show....php?t=1338183
1) Install Bootstrap Recovery Droid2
2) Boot into recovery
3) OPTIONALLY: create a backup of your data
4) Choose Install zip from sdcard -> Choose zip from sdcard and select downloaded ZIP file.
5) OPTIONALLY: install Google Apps the same way
6) Wipe data / factory reset
7) Wipe cache partition
8) Reboot and enjoy
9) OPTIONALLY: use attached Baseband app switcher if you have troubles with phone signal.
all worked out, but when I went passed the phone rebote motorola logo and nothing else happens. I do not know how to solve this problem.
I can not run the recovery menu. I can only enter the bootloader version is 70.13.
I would like to upload the software from the Polish language.
Thanks for help.
Click to expand...
Click to collapse
From the bootloader you can flash the original firmware again and get your phone back to life.
Get your firmware from here: http://sbf.droid-developers.org/umts_milestone2/list.php
Keep in mind that you need to have a fully charged battery before flashing, and you can only flash a firmware that is the same version or newer that the original in the phone (newer is always better)

Work?
Enviado de meu MotoA953 usando o Tapatalk 2

[BRA] Giovani said:
Work?
Enviado de meu MotoA953 usando o Tapatalk 2
Click to expand...
Click to collapse
it works, I've done first so I have uploaded the rds lite software on this page sbf.system-ready.org/umts_milestone2/?C=M;O= D Unfortunately, it was the android version 2.3.6 but went to decorate it root, then I have uploaded to the sD card CM9 with google alikacjami droid2bootstap installed and I have uploaded to the card-v2 Bootmenu_v0.8.6 phone then ran again and continue with bootmenu it's instructions. works great thanks for your help. :good:

Same problem for me: would appreciate help
Hello !
It seems like I am having the same problem as lukasz0318, but I don't know how to solve it, even based on what has been said before. That's why I am posting here.
To summarize it : I am not able to boot into Recovery Mode anymore on my Milestone 2, so my phone is soft-bricked. I am able to boot into Bootloader Mode.
I already posted my problem on the Android StackExchange (android.stackexchange.com/questions/27553/how-do-i-enter-recovery-mode-on-my-motorola-droid-2-global-to-unbrick-it), but as I have had no answer there in 8 days, I suppose XDA-Developers will be a more appropriate forum. Anyway, let me recap the problem. Hold on, since it is quite an explanation. You may jump to the last paragraph.
I own a Motorola Droid 2 Global, also called Milestone 2. It used to have Android 2.3 with Motoblur middleware. I don't know what firmware version it had, but it was updated earlier this year by the manufacturer. I bought my phone in France independently from any phone carrier (so it was not bought from Verizon for instance). I rooted it, installed ROM Manager, Droid 2 Global Recovery Bootstrap and ClockworkMode Recovery. From ROM Manager, I could successfully reboot my phone into Recovery mode, allowing me to back-up my data for instance. Until this stage everything went fine.
What lead to my problem : I also wiped the cache and installed CyanogenMod 7.2 and the Google apps from ZIP files and from the Recovery Mode interface. But now my phone is broken. When it now boots, it shows the stylised M logo, but then switches to an entire black screen. The phone is still on so I have to pull the battery to shut it down.
I would like to reboot into Recovery Mode but this doesn't work : I am never able to see the Recovery Mode logo (a warning sign with a little android). How should I do it ?
What I have tried : I tried to boot while holding the Power and the 'X' button, as adviced on different forums. This still leads to the black screen. At this state, pressing the Search hardware button does nothing. Holding the Power and the Volume Up button has no more effect. I am able to enter Bootloader Mode by holding Power and Up Arrow. Procedure suggested by Verizon
I also tried to use a Slitaz live CD with ezSBF on it, that I*downloaded from www droidforums net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html#post1726853. But I get errors in the process and then my phone reboots in Bootloader mode and shows the following error:
Code:
Critical Error:
FEBE 0047
After that I still cannot get to Recovery Mode.
I also took a look at Caesarivs' link (sbf.droid-developers.org/umts_milestone2/list.php) but I don't know which SBF to pick and I don't understand lukasz0318's answer to it. Which is a pity since the link was successful to him.
Could you please give me some details on the procedure to follow ? Additionaly, could you post me a link to your favorite and up-to-date tutorial on how to restore the Recovery Mode ?
Thank you very much !

1) A Milestone 2 is not the same as the D2G. If you bought your phone in france, its a Milestone 2.
2) You flashed the ZIPs on moto's recovery, not ClockworkMod recovery.
Try this:
1) Flash this SBF: http://sbf.droid-developers.org/umt...MILE2GBRTFR_P012_A006_HWp2a_Service1FF.sbf.gz You can flash it with RSDLite on windows or sbf_flash in linux.
2) Root it with Doomlord's one click root.
3) Download droid2bootstrap (NOT the global one) bootstrap recovery, and flash bootmenu (attached to this post)
4)Reboot once normally, reboot again, and press the volume down key when the LED flashes blue.
5) Flash CM7.2, the google apps, wipe data/factory reset.
6) Fix baseband (if you have problems with 3G or signal) with Milestone2 Baseband switcher v2: http://forum.xda-developers.com/showpost.php?p=29580375&postcount=696
Hope it helps you :good:

Lean946 said:
1) A Milestone 2 is not the same as the D2G. If you bought your phone in France, its a Milestone 2.
2) You flashed the ZIPs on moto's recovery, not ClockworkMod recovery.
Try this:
1) Flash this SBF: sbf.droid-developers.org/umts_milestone2/MILS2_U6_4.1-22_SIGNED_UCAMILESTONE2B1B80E1014.0R_USXMILE2GBRTFR_P012_A006_HWp2a_Service1FF.sbf.gz You can flash it with RSDLite on windows or sbf_flash in linux.
Click to expand...
Click to collapse
Thank you very much, Lean946. I didn't know there was a difference between Milestone 2 and Droid 2 Global. My mistake.
As I use Ubuntu 12.04, I tried to use sbf_flash but this brought up an error:
Code:
SBF FLASH 1.23 (mbm)
opticaldelusion.org
=== MILS2_U6_4.1-22_SIGNED_UCAMILESTONE2B1B80E1014.0R_USXMILE2GBRTFR_P012_A006_HWp2a_Service1FF.sbf ===
Index[1]: Unexpected chip 32
Index[2]: Unexpected chip 32
Index[3]: Unexpected chip 32
Index[4]: Unexpected chip 32
Index[5]: Unexpected chip 32
Index[6]: Unexpected chip 32
Index[7]: Unexpected chip 32
Index[8]: Unexpected chip 32
Index[9]: Unexpected chip 32
Index[10]: Unexpected chip 32
Index[11]: Unexpected chip 32
Index[12]: Unexpected chip 32
Index[13]: Unexpected chip 32
00: RDL03 0x82000000-0x8204CFFF F8E4 AP
01: CG31 0xB0280000-0xB02847FF 9EAD AP
02: CG32 0xC7B00000-0xC7B207FF 65A6 AP
03: CG33 0xB2100000-0xB2EC07FF 437B AP
04: CG34 0xB0700000-0xB07047FF 46C7 AP
05: CG35 0xB1100000-0xB18FFFFF 27C9 AP
06: CG39 0xB3400000-0xC7AC07FF 097D AP
07: CG42 0xB0800000-0xB083FFFF AC60 AP
08: CG45 0xB0C00000-0xB0F007FF 2254 AP
09: CG47 0xB1900000-0xB20FFFFF 0EAB AP
10: CG61 0xB0B00000-0xB0B7FFFF 87CD AP
11: CG64 0xB0000000-0xB00047FF 0841 AP
12: CG65 0xB0180000-0xB01847FF 130F AP
13: CG66 0xD4400000-0xE43FFFFF BB26 AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG31: 100.0%
-- OK
>> uploading CG32: 100.0%
-- OK
>> uploading CG33: 11.8%usb_bulk_read 0
!! unexpected response
-- ACK ADDR
RX ADDRB22A0000A7 B22A0000A7
>> uploading CG33: failed at b22a0000/b2ec0800
!! failed
>> rebooting
usb_bulk_read 0
My phone now shows the Bootloader Mode with
Code:
SW Update
In progress…
It has been so for several minutes. I'll wait a little longer and if there is positive evolution I will edit my post.
Anyway, is this the expected behavior*?

I'd try waiting a few more minutes, if sbf_flash is still frozen, try unplugging and pulling the battery out and trying again, if it still won't work i'd take it to a windows pc, I never had any issues flashing with RSD, and I tried Milestones, Milestone 2s and Defy's.
Good luck.

Lean946 said:
I'd try waiting a few more minutes, if sbf_flash is still frozen, try unplugging and pulling the battery out and trying again, if it still won't work i'd take it to a windows pc, I never had any issues flashing with RSD, and I tried Milestones, Milestone 2s and Defy's.
Good luck.
Click to expand...
Click to collapse
Thank you very much ! I found a Microsoft Windows machine, found a download of RSD Lite (which was not very easy) and finally installed the SBF you pointed at. It worked very well to unbrick my phone ! It is now back to Motorola's ROM.
I will now try your following points in order to install CyanogenMod. Whether everything works fine or not, I will post an update.

Lean946 said:
1) A Milestone 2 is not the same as the D2G. If you bought your phone in france, its a Milestone 2.
2) You flashed the ZIPs on moto's recovery, not ClockworkMod recovery.
Try this:
1) Flash the right SBF. You can flash it with RSDLite on windows or sbf_flash in linux.
2) Root it with Doomlord's one click root.
3) Download droid2bootstrap (NOT the global one) bootstrap recovery, and flash bootmenu (attached to this post)
4)Reboot once normally, reboot again, and press the volume down key when the LED flashes blue.
5) Flash CM7.2, the google apps, wipe data/factory reset.
6) Fix baseband (if you have problems with 3G or signal) with Milestone2 Baseband switcher v2
Hope it helps you :good:
Click to expand...
Click to collapse
I think I did exactly what was indicated here: step 1 to successfully unbrick the phone, then step 2 to 4.
Step 4 lead me to an interface called "Android Bootmenu" (different from the Bootloader Mode). From there I could not flash any ZIP, but I could launch the Custom Recovery. In my case, ClockworkMod Recovery. From there I wiped data/factory reset, then I flashed CM7.2 and the Google Apps, and rebooted.
But now my phone doesn't boot properly anymore. The stylized M logo keeps appearing and disappearing. As the LED regularly becomes blue, I can enter the Android Bootmenu, and then the two Recoveries (ClockworkMod Recovery and Android Stock Recovery).
What should I do now to finish the install of CM7.2 ?

Might the reason be that I installed the wrong ROM (or the wrong Gapps) ?
I tried the following ROMS :
cm-7.2.0-droid2we.zip from get.cm/?device=droid2we&type=stable
cm-7.2.0-umts_sholes.zip from github.com/nadlabak/android/downloads
The first one gave me no error output during its installation in ClockworkMod Recovery.
The second one gave me an error :
Code:
E:Error in /sdcard/update.zip - (Status 7)
.
Do you have any suggestion or a link to your favorite tutorial ?

Finally, the following ROM did work, with the same procedure as I used to do :
CM9-NIGHTLY-120815-milestone2-eu.zip from forum.xda-developers.com/showthread.php?t=1623385
I ran into another final small problem (I could not close the Setup Wizard), but that was easily solved with the "Four corners method".
Thank you for your help and wish me good luck on my new operating system !

Need HelP - ODIN gets stucked while flashing

Hello guys,
I need extremely technical help as no longer know what to do.
I have a Galaxy S7 Edge device, which installed the rom BobCat and everything went well until then.
Later I decided to install another rom to test KingRom that left me unsatisfied, because I thought it had some bugs. Had the TWRP 3.0.0 recovery and decided to upgrade to 3.0.2, everything went well.
At one point I do not remember when or how if was when install back, downgrade to TWRP3.0.0, I do not remember if it was via Odin or TWRP, it happens that the installation stopped halfway. Then unplug the device, restarted in recovery mode and got the following message "E: falied to mount EFS (Invalid Argumen)", I could not restart the device (Boot Loop, and stucked at Samsung Logo) except in Recovery Mode, which also made to stay without IMEI number and Serial Number.
I googled until I came to this tutorial:
http://forum.xda-developers.com/s7-e...ssues-t3379516
I followed all the steps explained, I back up EFS_backup and RADIO_bakcup partitions.
Installed FACTORY BINARY G935, everything went well. After restarted, already had the correct IMEI number but still did not present the S / N.
After all that, i tried to install Stock Firmware via Odin, from here started the problems that could not solve.
In the first attempt Odin stucked in "System" (also used the PIT file with the same CSC ... .i do not know if I was right using PIT?). Restarted the device forcibly, entered the stock Recovery, did a complete wipe and always get this message "E: falied to mount System (Invalid argument), I returned to install Factory Binary, then reboot in Recovery and the same message no longer appeared.
Again I try to install the Stock Firmware and Odin always stucks in System, or NAND writing, or Partition, etc. I've tried various Stock Firmware, with and without PIT files, always without success.
Only Factory Binary that successfully installs. The TWRP via Odin also but when device restarts to enter Recovery Mode always get the message at the top of the display:
"Recovery image signature check Fail"
"Reboot to avoid Warranty bit set."
1. Does the partitions are in good shape? how can I check it?
2- I did good or bad using PIT file?
3- Does the problem is running Windows XP through a Virtual Machine?
4 What else can I do?
In all actions used and am using a Macbook 4.1, OsX Lion 10.7.5, Odin 3.11 Windows XP Professional 32bit through Oracle VM VirtualBox 3.4.38
Device:
Galaxy S7 Edge (SM-G935F) CSC = SWC SwissCom
1st Original Firmware: (I guess was 1?) G935FXXS1APG5_G935FVFG1APF3_SWC
Need help Please
Thank you so very much!

I think I brinked my phone. Please help [SOLVED!]

Hello. I tried downgrading from the latest ASUS firmware to Android 6.0.1
I used this tutorial to install the raw firmware: http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html
Went all the way to the last step when the app hanged. ASUS Flash tool went all the way saying
Code:
Run flash image script ...
It was hanged there. And as per this video, went all the way to the end where it showed the "code bar" on the right (https://www.youtube.com/watch?v=P8xg7A-P7Ak)
This is when the "Android" uninstalled driver showed up in Windows. This is under "Other devices - Android". I tried updating this driver using the ASUS_Android_USB_drivers_for_Windows found here: https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ but it wouldn't install the drivers.
Note that I used these ASUS USB drivers to get the ASUS ADB Interface installed. As per the tutorial I showed in the very first paragraph, I never got the "ASUS Android Bootloader Interface". This is what I think this "Other devices - Android" is found under Computer - Manager - Device Manager.
Most tutorials on the internet shows that the "ASUS Android Bootloader Interface" should be installed using these drivers found on ASUS website, the ASUS_Android_USB_drivers_for_Windows.
Now of course because I unplugged the phone, it will continously stay on the Android splashpage showing the loading circle infinitely.
As a last attempt I tried installing the "stock", not "raw" firmware (the one I wanted to install WW_13.16.5.49 but ASUS would not let you downgrade using the recovery "power+volume down" and using "Apply update from microSD card". It would give the
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
)
Well, after it brinked, I tried it again and this time it DID install WW_V13.16.5.49. Was succesfull. But after the ASUS splashscreen it's still stuck in the booting process.
I am very sorry if my post is convoluted but I tried explaining everything I did. Any way to un-brink it? I think maybe if I figure out how to properly install the ASUS Android Bootloader Interface, I can try again ASUS Flash tool and install the raw image and maybe that will fix it?
Please help. Any questions if my thread is too confusing, please let me know and I will answer it. I can't even turn off the phone. While it's stuck into the load splash screen, if I press the power button it just restarts, not turn off.
I still have access to fastboot (pwr + volume up) or recovery (pwr + volume down)
EDIT: Phone won't get recognized anymore in ASUS Flash Tools. Serial number won't show up to select

Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.

wang1chung said:
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
Click to expand...
Click to collapse
Thank you, this actually worked!!
Aaaand, it's actually on the version 13.16.5.49!!!! THIS IS EXACTLY WHAT I WANTED!
So apparently by brinking my latest nougat 7.0 update from ASUS via the ASUS Flash Tool trying to flash the .RAW 13.20.10.137, the standard recovery system (power+volume down) allowed me to install the 13.16.5.49 version. Then I assume remnants files didn't allow to properly boot, and your idea to wipe cache and factory reset fixed that!
What is so great is that I was scared that because the .RAW firmware was newer than the version I needed (13.16.5.49), I wouldn't have been able to install it. It was the same problem initially, when I tried to install 13.16.5.49 directly via recovery over the latest nougat 7.0 version from ASUS, but it was giving me
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
I think this error was due to the fact that ASUS won't allow older firmwares to be installed over newer ones, as per their webpage
https://www.asus.com/support/faq/1009748
Code:
You can not change the SKU from one to another, e.g., WW -> TW, and also can not downgrade your firmware, e.g., V2.20.40.13 -> V2.19.40.18
So in the end, what allowed the 13.16.5.49 stock firmware to be succesfully installed? The installer not detecting a proper firmware anymore because of the damaged update due to ASUS Flash Tools hanging because my computer won't install ASUS Android Bootloader Interface?

Glad you got it going :good:

Need help returning to stock, have constant issues, please HELP!!!

Hi,
I initially had G935FXXS3ERHD_G935FXEO3ERG2_XEO installed and flashed Glamour ROM S9+ port some time ago, now i need to return it to stock but no luck...
Using latest odin i flashed:
G935FXXU3ERL3_G935FXEO3ERKF_XEO
and
G935FXXU3ERJE_G935FXEO3ERJF_XEO
(i need to remain on 3 bootloader)
after each flash i receive the NO COMMAND screen, and cannot boot into stock recovery... only way to boot the phone is to install TWRP... I have noticed when i plug the phone is it comes up as GALAXY S9+ so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
i have no idea what else to try

Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try