Develop Bugs

[Q] Phone possibly bricked but it might be saveable!

Hi,
My first phone was rooted and I rooted my second too so I am confident rooting them however my second phone which had been rooted for a while had a space issue on SD card so I cleared out a few things which unfourtunatley included all the backup files ....
It worked fine afterwards but didnt let me change rom (using rom manager) so I just left it in working order for a few months until I wanted to reflash a new rom (as I am sure most people do every few months)
When it didnt let me, I tried to unroot and root options using superoneclick and unrevoked3 however, unrevoked 3 just stayed on "running root" and superoneclick got so far and crashed. When I go into the bootloader, it says something about some filed missing (think might be some nbh files).
At the moment, when normally turning the phone on, it stays on the screen with the pink circle, the first boot screen.
I have tried updating it using the RUU but it takes a long time and then says "use the correct rom for your device" which I am, this method just boots my phone and goes to a htc logo.
I can also get into the bootloader but when I apply update.zip, it says it has failed and something about files not existing/step 7 failure.
The thing is, I can get to fast boot and I am sure there is a way via ADB to force a new image (such as a cyanogen recovery image) on to the device.
Can anyone tell me how to push an image to the phone without using the RUU (as this didnt work for me)??
Maybe my phone is just bricked
Thank you very much!!

It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)

Thanks but I do not have another Desire...

Any card reader

yeah, I got a card reader laying around somewhere, if not ill go get one in Tesco, what where you thinking?

bortak said:
It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)
Click to expand...
Click to collapse
Hi Bortak, I am having similair problems with my phone sticking on the pink circle screen. I cant seem to load a recovery file from Bootloader. Will I need to make a Gold Card, my phone is s-off.
thanks mate

if phone is S-OFF go to my guide, look at advanced boot problems S-OFF.

SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!

Mugube said:
SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!
Click to expand...
Click to collapse
#facepalm#
Translation: I flashed another ROM because my other one didn't boot.

[Q] Rooted Wildfire S 2.3.5 stuck in bootloop...

Hi,
I've got a HTC Wildfire S, rooted and S-OFF.
But it's stuck in bootloop, I messed with the system/apps folder...
So now it's pretty much messed up.
Didn't install ROM-manager, I know it was kinda stupid.
How can I reïnstall a custom ROM?
Can anyone help me?

Go into recovery and flash from there, or if you backed-up then restore the rom. If you don't have any roms then you can also mount your sd card from CWM recovery. If you don't have any custom recovery then you'll have to flash it through fastboot. I would tell you the process but I'm really busy right now, but I'm sure someone will explain it to you.

Hi, thanks anyway... hopefully some other kind guy can help me
I don't have any custom recovery, only a ROM which I want to flash on to the device...

seanw712 said:
Hi,
I've got a HTC Wildfire S, rooted and S-OFF.
But it's stuck in bootloop, I messed with the system/apps folder...
So now it's pretty much messed up.
Didn't install ROM-manager, I know it was kinda stupid.
How can I reïnstall a custom ROM?
Can anyone help me?
Click to expand...
Click to collapse
Don't install custom ROM's from Rom Manager's Download list. None of them are for Wildfire S.
Install CWM Recovery either through Hboot as a PG76IMG.zip or using Eoghan2t7's Windoze tool.
From there you should make a backup of your working ROM before trying any new ones in case of times like this...

Hi,
yes if I install the CWM recovery... can I then install my ROM? It's just a slightly modified Wildfire S Stock Rom...
And, I'm sorry to ask... But how do you install CWM through the boot menu?

seanw712 said:
Hi,
yes if I install the CWM recovery... can I then install my ROM? It's just a slightly modified Wildfire S Stock Rom...
And, I'm sorry to ask... But how do you install CWM through the boot menu?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1431969
Download that and connect your WFS to your PC, follow the steps which are quite easy. Then boot into recovery (volume down + power button, choose recovery by the volume buttons and power button), then choose install zip from SD and you can install the zip file (the rom) by selecting that file.
Let me know if this works

I have the same problem when using OC ROMs.
What am I doing wrong?
Now it's loading for ages or simply stuck in the bootscreen.

I too have the same problem when using OC ROMs. Why?

Hi, thanks for the help!
But I'm not quiet through yet... so I downloaded the WFS Manager, then I connected up my phone to the pc.
It was switched on, and just doing the bootloop again, showing the "Quietly Brilliant" sign over and over again.
And then I ran the tool, and it said "Please connect up your device" after I ticked on the first option ("Root And Install Recovery").
I guess this is because the WFS was bootlooping, and so the pc didn't recognise it. I also tried with the HBOOT menu on, but still the pc didn't recognise my phone. Is there anything I did wrong?
My pc (Windows 7 Ultimate x64), showed a popup saying there couldn't be found any driver for "Android 1.0". However it did work before the bootloo

If you have a card reader, or a phone that can take your SD card, then just remove your SD card, place it in an SD card reader or a device which can take your SD card, plug that device into your PC, place the ROM you want to flash onto the SD card, place your SD card back into your Wildfire, boot into recovery and flash the ROM from there.
I had a similar situation where I had an invalid xxxxIMG.zip file on the root of my SD card and a ROM that kept rebooting my device. Naturally, I started panicking, but when I got myself together, I just realized I could remove my SD card and then go into recovery, then reinsert my card and flash a working ROM.
Hope this works for you

Hi, thanks for the help. But I don't think you fully understand my problem.
So I have a stock ROM, rooted. And I messed with the system/app folder.
Now it's stuck into bootloop.
What does recovery mean? is it the menu entry in the HBOOT menu?
Because if I go to "recovery" and click it, after a few seconds I get a phone icon with a red triangle above it.
I tried putting the PG76IMG.zip file on the root of my SD card, but then in the HBOOT Menu, I get the message:
"CID incorrect !
Update Fail!
Press <POWER> to reboot."
What do I have to do?

find the cwm recovery thread and download the PG76IMG.zip then copy it to your sdcard then reboot to hboot. when it asks you if you want to flash recovry press volume up. then when finish instead of rebooting take out your battery. wait for 25 secs reinsert it then boot to hboot then choose recovery see new ui instead of the old one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:16 PM ----------
here you go forum.xda-developers.com/showthread.php?t=1213229

Hi, when I do what you say I get the error:
"CID incorrect!
Update Fail!
Press <POWER> to reboot."
This is my course of actions:
I download the PG76IMG.zip file from the CWM recovery thread.
I place it in the root of my SD-card.
I start my phone pressing the volume-down button.
It automatically finds the .zip file and tries to update, but then I get the error.
What should I do?

I got what you were trying to say, I just didn't realize you had no recovery installed. I had the same error message pop up when I tried to install the recovery. I think it had something to do with the hboot being newer than something, something, blah, blah, bliddity-blah.
Anywho, I think I had the recovery installed along with the root using SuperTool.exe, but that won't work for you, since you obviously can't boot up, so you can't connect to the PC. All I can remember is I had some sort of app on my PC that allowed me to push the CWM Recovery without going through all that hboot stuff, since the S-ON wouldn't let me install PG76IMG.zip. Again, this is useless to you
My best advice is to try another PG76IMG.zip file and just keep trying until you find one that'll work, which you'll place onto your SD card from another device, of course.
EDIT: Link to where I got CWM Recovery from.
In this post there's an auto-installer that I used to flash it onto my device.

The reason you are having bootloop problems with OC roms is because your phone doesn't support OC. Don't worry though it's not just you, even my phone doesn't support OC. The best ROM to go with right now is Alquez's CM7, but I'm sure other developers will make non-OC roms.

Hi, THANKS!
I used the auto installer, and now I have the CWM recovery!
Can someone tell me now which options I should use to install the new ROM?
Maybe an advice of which ROM would be the best one?
I'd like something fast and stable, it would be handy to have one which doesn't have any stock apps installed with it...

I'd go with Jikantaru's ROM, if I wanted a more Sense-ish experience (which I, personally, don't). It does away with the bloatware, but it keeps Sense UI. I couldn't use this one, since my SD card is only 2 gigs and I can't partition it correctly :\
Therefore, my pick would be Cyanogenmod 7, which gives you a pure Android experience (no trace of HTC's bloatware, spyware or crapware). It takes away everything you don't need or most likely don't use and keeps it all clean and speedy, since there's no Sense, MotoBlur, TouchWiz or any other company-created user interface, leaving you to run everything right on top of the Android system. However, I've had some trouble with this one. First I had no mobile data connection or WiFi, and when I finally fixed that problem, I noticed I had no phone app -.-
So, now I'm using m1ndh4x8r's ROM, and I'm pleased enough with it. It lets me overclock and stuff, though I fear I might have effed something up while reverting to it from my non-fully-working CM7 flash, and now I can't install most apps :\
Now I'm pretty much waiting for a fully-operational CM7 build to come out so I can finally use my phone's full potential.

white htc screen
Hey hey =)
I installed the cm7 by alquez (already tried the RC and the nightly build) and I'm stuck at a white boot screen - I don't know if this is the boot loop error - I only see the green HTC sign with white background
Yesterday, I unlocked the phone, rooted it and today, I installed the CWM and from there, resetted the phone, data, and installed the zip.
Now, the white screen doesnt go away, even after 15min or so
Is there a thing i'm missing?
Thanks in advance!

Saftpackl said:
Hey hey =)
I installed the cm7 by alquez (already tried the RC and the nightly build) and I'm stuck at a white boot screen - I don't know if this is the boot loop error - I only see the green HTC sign with white background
Yesterday, I unlocked the phone, rooted it and today, I installed the CWM and from there, resetted the phone, data, and installed the zip.
Now, the white screen doesnt go away, even after 15min or so
Is there a thing i'm missing?
Thanks in advance!
Click to expand...
Click to collapse
Wipe all data and cache including dalvik from within clockwork mod

ok, shall I also format boot?
because I read it's pretty nasty deleting it if you don't install a new one, is that right? ^^
Dunno what has changed but thank you for your tip, it worked now!! =)
PS: didnt format boot ;-)

[Q] Flash failed and now stuck with "waiting for device" in cmd

Hi guys,
I just bought my One X today. Since it is my first android i am quite noob in all the issues regarding flashing/rooting.
I already unlocked the bootloader, install the clock recovery and then when I try to flash the new rom, i forgot not to extract the zip file so things start to mess up.
Now I am stuck at the HTC boot up screen. I have tried all the methods at:
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
Click to expand...
Click to collapse
but it doesn't work.
The problem is that when i type a command into cmd it keep showing waiting for device
So I don't know what to do now. I really appreciate your help if you could provide step by step.
Thank you so much

OK so as a noob you thought you'd try too root your 1st android phone after having it just one day??? oops! Lesson learned, next time read up loads first and maybe get used to the phone first before trying too root it. Anyway. . .
After installing Clockworkmod did you (as instructed in all the manuals I have read!) do a backup? If so just remove the usb, turn your phone off and go to the cwm boot menu and select restore. Fixed

recovery?
i see you have flashed recovery..
can you get to it??
Press POWER + VOL DOWN until it reboots and keep holding until u get to HBOOT..
from there select recovery and see if that shows up..
if you can get to Recovery, then you can either flash a CUSTOM ROM, or go back to STOCK recovery and then run RUU (a program provided by HTC that will restore you phone to stock) but you also have to relock the boot loader..
based on your choice more info may be required to help you
My best guess is that you have a messed up kernel...

[Q] HTC One x Bricked

Hello guys,
Yesterday I bricked my One x, I followed this section down here.
---------------------------------------------------------------------------------------------------------------------
Let's begin.
Download my toolkit from here.
http://forum.xda-developers.com/show...php?p=24972527
Extract the FOLDER to your C: drive or to your desktop.
MAKE SURE YOUR DIRECTORY DOES NOT HAVE A PERIOD OR SPACE.
Open One X.exe
So now you have my program open. Great.
On your phone, go to Settings -> Developer Options and Enable USB Debugging.
From my toolkit, Click 1. Install HTC Drivers.
After the drivers install, restart your computer.
After your computer loads up, open my toolkit and connect your phone to the computer. Your phone should now be recognized.
Now, click 2. Register at HTCDev. Register with a VALID email address and LEAVE the web browser open.
Now, under the commands section of my toolkit, press Boot into Bootloader.
You should have a nice, white, shiny screen that says FASTBOOT USB.
Click 3. Get Token ID. Look at the pop up and it will tell you how to get the Token ID.
Highlight where it says < < < < Identifier Token Start > > > > all the way to < < < < < Identifier Token End > > > > > and right click and it will automatically copy it.
Now, click Submit Token ID. Your web browser should now open a new tab. Scroll down and in the empty box, paste your Token ID. Press submit. HTCDev now emailed you your unlock token.
Your phone should still be in the bootloader. Now, go to the email address you registered to HTCDev and DOWNLOAD your unlock_code.bin. Press 5. Unlock Bootloader. Locate your unlock_code.bin and it will flash it to your phone.
READ the warning. THIS WILL WIPE ALL YOUR DATA FROM THE PHONE.
When you agree to it, press the volume up button and press the power button to accept it. Your phone will now restart.
When your phone loads up, go through the set up wizard. Then, on your phone, go to Settings -> Developer Options and Enable USB Debugging.------------------------------------------------------------------------------------------------------------------------------------
So far so good!
After that I try the permroot \/ only it wouldn’t work.
----------------------------------------------------------------------------------------------------------------------------------
Under the Extras section, press Perm Root. It will push SuperSU.zip to your phone.
Under commands, press Boot into Bootloader once again.
Now, it is time to flash a recovery.
TWRP (Team Win Recovery Project) is a custom recovery that will allow you to flash custom ROMs, Mods, etc.
CWM (ClockWorkMod) is a custom recovery that will allow you to flash custom ROMs, Mods, etc.
I recommend TWRP and we will use it for this tutorial,
Select TWRP and press Flash Recovery.
After it flashes, remove the USB cable and have HBOOT selected in bootloader. Press the power button and it will reload to another screen. Press the Volume Down button until you get to Recovery. Press the power button to select it.
Go to Backup and back up your boot and system partition. Always have a back up before you flash or do anything.
After that, go to Install and locate SuperSU.zip. Click it and slide the screen on the bottom to flash it. After it flashes, reboot the phone.
In your app drawer (your menu with all the apps), open SuperSU. If it says the binary needs to be updated, then update it. If it doesn't, then you are fully rooted!-------------------------------------------------------------------------------------------------------------------------------
So I Googled to antoher solution and found a UNROOT tool, stupid is I was, I tried id.
Now my phone only startup in the bootloader so this is maybe a good thing?
Is there anyone how has an idea to solve this problem? I hope someone can help me out .
Phone info:
***UNLOCKED***
Endeavoru PVT SHIP S-ON RL
HBOOT-1.39.000
Radio-5.1204.162A.29

Well if you can access the bootloader, then go into fastboot and run
fastboot earse cache
then flash the recovery (CWM Touch) again, make sure it's the latest version for your phone, so
fastboot flash recovery recovery.img
now reboot into recovery and do a factory reset/wipe data and dalvik and reboot...
if it boots up you are good to go, if not than try to restore your nandroid from recovery.
Now find and download the latest SuperSU.zip and move it is your sdcard.
Now once more go into your recovery and click on install zip and find supersu.zip, install and reboot

You can't brick hox that easy, relax and try to reflash recovery, boot.img and reset cache. If problem not solved you need to wipe data or even reflash rom one more time
Sent from my HTC One using Tapatalk 4

genocide_ru said:
You can't brick hox that easy, relax and try to reflash recovery, boot.img and reset cache. If problem not solved you need to wipe data or even reflash rom one more time
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
The only good thing in being S-ON...
You can't f**k anything up.
Everything is easily fixable.

Thanks guys,
I'm a bit further at the moment, now looking for the right backup.

Same Problem, please HELP !!!
Good day Friends of the Forum
I have a problem and do not know how to fix it , I have navigate a lot in the network and I could not get my phone to work . I have HTC One X from AT&T. By playing around with the phone, accidentaly I delete the O.S. so right now my phone is locked . I can't load Origanal or Custom ROMS . The only thing I can do is enter the bootloader and install recovery ( TWRP ) I installed several versions of TWRP to install a custom rom or I locked the bootloader to install the original RUU and everything has been WITHOUT SUCCESS .
Right now I have S -ON , my HBOOT is 2.14 and I can install TWRP Recovery 2.6.0.0 or 2.6.3.0 .
I have read in many places that I have to make an S -OFF to install a Custom ROM , but all I get Tips that I need an OS runing to finish the installation (or modified to do the S -OFF) . What can I do if my S.O. is actuall blocked (brick). Only screen I got when I turned on or reboot my is the white screen " HTC quietly brillant" .
My friends , I request help from the wise in this range. Since I ran out of ideas. I attached pictures with my phone information
regards

eL_pIt said:
Good day Friends of the Forum
I have a problem and do not know how to fix it , I have navigate a lot in the network and I could not get my phone to work . I have HTC One X from AT&T. By playing around with the phone, accidentaly I delete the O.S. so right now my phone is locked . I can't load Origanal or Custom ROMS . The only thing I can do is enter the bootloader and install recovery ( TWRP ) I installed several versions of TWRP to install a custom rom or I locked the bootloader to install the original RUU and everything has been WITHOUT SUCCESS .
Right now I have S -ON , my HBOOT is 2.14 and I can install TWRP Recovery 2.6.0.0 or 2.6.3.0 .
I have read in many places that I have to make an S -OFF to install a Custom ROM , but all I get Tips that I need an OS runing to finish the installation (or modified to do the S -OFF) . What can I do if my S.O. is actually. Only screen I got when I turned on or reboot my is the white screen " HTC quietly brillant" .
My friends , I request help from the wise in this range. Since I ran out of ideas. I attached pictures with my phone information
regards
Click to expand...
Click to collapse
Unfortunately, you are in the wrong forum my friend.
This is the forum for the quad core version htc one x (endeavoru)
and yours sais evita in the bootloader.
Do not flash ANYTHING of these forums as they might brick your phone!!!

Stefan0vic said:
Unfortunately, you are in the wrong forum my friend.
This is the forum for the quad core version htc one x (endeavoru)
and yours sais evita in the bootloader.
Do not flash ANYTHING of these forums as they might brick your phone!!!
Click to expand...
Click to collapse
Thanks.
Have a nice day

:thumbup:
Sent from my HTC One X using xda app-developers app

Stuck in fastboot. No recovery... no bueno :(

So I had my ze551ml / Z00A rooted, was loving life, all was great. Then I tried getting XPosed access and didn't read up on it prior. Anyways, now my phone is stuck in fastboot, I'm able to flash partitions and all, including recovery partition, yet I cannot enter any mode but the hung ASUS logo, or fastboot. I weas even able to load CM's "upgrade to MM bootloader" package, but still the same thing only with green letters where they once were blue..... Please help, I need my beloved phone back.....

I'm not a pro but if you can access fastboot it is just a soft brick and I'm sure many people can point you on the right thread to recover it.

I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....

joecost85 said:
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
Click to expand...
Click to collapse
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?

timbernot said:
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
Click to expand...
Click to collapse
0094.0183

joecost85 said:
0094.0183
Click to expand...
Click to collapse
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link

timbernot said:
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
Click to expand...
Click to collapse
So I've yet to try your solution, but I do have an update, I was able to, one by one, flash all the stock files (stock as in the stuff I downloaded from asus site) and was almost able to boot to recovery, but when I got to the red triangle android, I couldn't get it to go further. I've heardf alternate key combos for proceeding from there, and tried them all, but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**

joecost85 said:
So I had my ze551ml / Z00A rooted, was loving life, all was great. Please help I need my beloved phone back.....
Click to expand...
Click to collapse
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
joecost85 said:
So I've yet to try your solution,
but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
Click to expand...
Click to collapse
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108

timbernot said:
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
Click to expand...
Click to collapse
Here's the thing. I'm super stubborn, and I think I know everything (cuz I do....) so of course I decided that I could figure something out, so I tried my way first............ didn't pan out.... anyway, I'm finding any time I flash a TWRP file, I have no access to recovery mode. Regardless if I do it manually through fastboot, or CM upgrade/downgrade or even the giovix fix (yes I tried it). My question is this, Where is there a return to stock option? of the giovix DLs I could find, I see a 'magisk root' 'TWRP' 'bootloader unlocker' and 'Xposed' tools, nothing else.... Am I missing something? or am I just skimming over that part?
I do appreciate all the help, seriously. Even if it seems like I'm not taking suggestions very well. It's moreso I don't have access to a computer most of the day, and it's not a huge priority since I went and bought a zfone 3 max a few days ago (decent phone for what it is....crazy battery life)

https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
Functions:
1- Check connection status
2- Bootloader Unlocker
3- Flash TWRP 3.0.2-0 M1
4- Full-auto xposed flasher!
5- Full-auto root flasher!
5B- Full-auto root (Magisk+Phh's) compatible with 184!
6- ADB Shell
7- Return back to stock
8- Erase /system, /data and /cache for a clean upgrade
9 (HIDE)- Auto-reboot to bootloader
10- More functions inside!

well then forgive me for not downloading the correct option. I nowhere see this list among anything I downloaded, so maybe specify which is which ('full' or 'auto')....... I'm already downloading both of them again, because I'm not sure which I already had. But yea, one of the 2 only has the 4 options I mentioned.

Its not rocket science

timbernot said:
Its not rocket science
Click to expand...
Click to collapse
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?

joecost85 said:
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
Click to expand...
Click to collapse
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )

timbernot said:
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
Click to expand...
Click to collapse
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.

joecost85 said:
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
Click to expand...
Click to collapse
EDIT"""" because i got it wrong too , i dont even think about , i just do it
It`s ->
From powered off position
Press Power and Vol +
at two vibes, release power
at boot up screen ,release vol+
in bootloader ,scroll vol up or down to and then select(press power) at recovery selection.
At dead android guy -> press vol + and power for 4 seconds -> release Vol +
You should be in recovery.

i am replying in this post since i have a similar problem, and I am as stubborn as OP. Me posting here is a big step in acknowledging my defeat at last. Hours of digging through the internet didn't solve my problem
I have changed my ifwi and dnx more times than i can remember. (my clean slate is mostly using xFSTK downloader with xFSTK_ZE551ML-sal358-amtech.vn files)
Using the above mentioned method (giovix`s modder tool) to go back to stock i still boot into fastboot, not recovery mode.
trying to unlock bootloader it says on the phone "unlock fail"
Using asus flash tool with raw files i get "gpt command failed"
Using a manual method i get the "gpt command failed" on the "6. fastboot oem partition /tmp/partition.tbl" step
in my opinion as soon as i get some kind of recovery my problems are solved. But have been working four hours on this problem with all possible solutions i could think of, nothing but frustration.
info: current ifwi 0094.0183 (wich should be M)
serial 01234........EF
and using the toolkit on "https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293" i found out my device firmware version is 198 (wich is probably not good in combo with the ifwi)
little update in a certain config (android 5 / ifwi 0094.177 / stock recovery) i can boot up untill the dead android icon, but with whatever key combo can't get past it... (vol up + power) / (vol down + power)
fastboot flash boot recovery.img (yep i am really desperate to get into recovery) doesn't even give me the dead android.
thank you beforehand!

Last paragraph with android 5 ifwi 0094.0177
Is your serial correct ?
Press vol + once is it correct?, if not you will have to xfstk first again and flash raw (twice) with temp bootloader 0094.1069
See my unbrick video for help

First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?

Speybrouck said:
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Click to expand...
Click to collapse
Did you get this device in this condition ?
If not, what happened so that you lost serial ?
Anyway , i have never tried this because i have ALWAYS succeeded flashing raw (twice) to correct serial BUT it may work for you.( i am not sure you have a device that can have the serial corrected due to whether its been tampered with previous ) which affects recovery and IMEI.
Usually , xFSTK is used to install temp bootloader - Its supposed to be the lowest level form of unbricking procedure and restores temp bootloader so you can fastboot after-- flashing raw in fastboot via AFT(twice) restores serial -- 1st flash approx 3mins is with incorrect serial and temp bootloader.
After a couple of mins, cmds on phone pauses on RESULT=OK on phone.
You close AFT and open AFT again , input raw and set AFT up -- press Vol+ on phone -> once, serial will be corrected and 2nd flash can be started and left until it boots into android 5 by itself.
If GPT trouble , that link may help.
There is other programmes for starting to create serial and restoring .
Usually people who use these , have to dig deep into buildprop stuff which if tampered with can end up with problem such that you have.
Good luck
see if anything here helps
https://forum.xda-developers.com/showpost.php?p=70223946&postcount=8