Screwed up my phone - Asus ZenFone Zoom

I have a Zx550 version of this phone which i bought in japan. The SKU of the firmware is in JP and so is the recovery. I tried to follow a guide so that i can switch the SKU but it turns out the things i downloaded were not for my asus zoom. I have the boot.img and the droidboot.img of the official ww marshmallow update for the phone. I just need the recovery because right now my phone is stuck in fastboot and i cant boot into recovery mode. Will downloading a stock rom allow me to get the required recovery.img back or is my phone screwed for life? Please reply i dont wanna turn this thing into a paper weight. Thanks

Related

Possible Brick HTC M8

Hello All,
I think I may have possibly bricked my m8.
I was using cyanogen 11, when I decided to try and flash the GPE rom that is available.
However I did not flash the latest firmware. I am not able to get into fast boot. When I press Power + Volume Down, it takes me too bootloader but no options are available other then press power to reboot.
When it reboots I do get into the rom however, wifi, and service are unavailable for obvious reasons. My Stupidity may have costed me this phone :/ I wasn't able to get s-off with my t mobile variant. It is unlocked, and had TWRP installed.
Any help would be greatly appreciated!
Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.
BerndM14 said:
Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.
Click to expand...
Click to collapse
Okay maybe not bricked but I messed it up quite badly, Im not able to get it into the recovery or have it be detected via fastboot. I did try and do a ruu to have it be put back to stock but Im not sure how to go about doing that since ruu cannot see it since it isnt in fastboot... :/
Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop
subarudroid said:
Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop
Click to expand...
Click to collapse
I did get the latest one from the official site, I was able to use it perfectly fine last night. Now however when I try adb shows the device offline, even if I kill and start the server, and disable and renable the debugging, try different ports etc. I can get it to show the device name, but it says offline next to it, I get no prompt on the device. I was reading the gpe doesnt use fastboot, ( I may be wrong) But that would explain why I dont see anything at the bootloader screen, other then press power to reboot the device.
Good news everyone! I was able to fix it in the most impractical way ever.
So why nothing else worked, I did still have access to the rom which of course had no wifi or service. So what I did was install the terminal emulator via browsers onto my phone, from there I was able to type reboot recovery and restore my backup that I had! and wala, whatya know, now it works, and I dont have a useless phone anymore

Softbricked M8 please help

I was originally on kitkat 4.44 and this is my first time dabbling in flashing roms. I tried flashing to lolipop 5.0. After booting up, there was a OTA update that is unskippable and even if I tried to download and install the update I'm still stuck at the same update page even after rebooting. It's my main phone and I need it back asap. Is there a way to get pass the page or can I just revert back to 4.44? Please help.
What's your current firmware no. ?
If not sure, post fastboot getvar all result without serial & imei no.

How to fix LG G Pad 10.1 stock on version logo

i root my phone with kinggo root after root me install supersu . The supersu need me update binary after update phone will restart . But now phone is can't start
Stock on version logo
LG G Pad 10.1
LG-VK700
Any one please help me ?????????? thanks
fixing a hole
Do this: http://forum.xda-developers.com/showthread.php?t=2590185. Same procedure, only you need is property kdz file from https://mega.nz/#F!fgskmDSB!GANW9PaJ0dW3lvHCWBzscQ.
Hi but now see you reply my phone ready flash but i flashing wrong now my phone can't turn on can you me thk for answer
fixing a hole
If you f**ed up the download mode, y'u must try flash via fastboot nicely. I don't have much time now, but y'u find this method on xda, it's work for this models probably. You also need the kdz extractor to unpack firmware: http://forum.xda-developers.com/showthread.php?t=2600575. Remember to use the Verizon version of firmware.
I can wait you it you free time because i don't try by myselt the flashboot not recognising my phone i feel my phone is hard brick thk for answer

Downgrade MM to LP from sd CARD, NO more bricks :D video

On 551 Z00A or AD the official downgrade version of LP WW-52.20.40.196 firmware from any M stock firmware - via sd card
https://www.youtube.com/watch?v=_1T6SMJiUSg&feature=youtu.be
Success -- Downgrade of MM to LP works with the downgrade firmware above , works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , it detected .134 and ..144 and .184 MM update packages and now also should detect .223 latest firmware if on ext SD if written like mentioned and shown in the video !
The above LP downgrade version is detected in .223 latest M firmware after a reboot.
Some pics
Seeing a lot of people bricking their devices downgrading to LP from M .
There is now no need for all these bricks when we can downgrade via M recovery to LP via ext sd card .
If you are on a stock rom MM bl and rooted TWRP ..you just need to flash stock boot.img and recovery for the MM build you are on . Reboot to stock M recovery. Follow above procedure.
If you are on M bl custom Rom and rooted TWRP but have no stock M back-up , flash back boot.img and recovery for.134 , sideload .134 stock. Then downgrade
That above applies to 551 Z00A .
Merry Xmas to all at XDA --Still seeing people looking to downgrade from M to LP even after posting this method above via ext SD card - WOW
So , my present to you is a video of the above process
Say NO to anymore bricks Say NO to ever having to use xFSTK downloader again
This makes our phones fully , changeable forwards and backwards via SD card (for good)
The process will go from .184 M to .196 LP on the 551 Z00AD or Z00A
If you Have MM bl custom rom - use giovix`s Modder tool to `return to stock option` flash boot.img - flash recovery option in Modder . Follow process.
Video Coming Soon ...........
Ps, i assume the process will be exactly the same for Z008 from the latest Stock M to LP but using the relevant downgrade version(whatever that is) from official ASUS site for Z008
I dont have a Z008 so if anyone wishes to attempt it and give me your results here , that would be great for others
pps, i decided to do the video due to either people dont trust this method or people are extremely shy about hitting the thanks button . Whichever -- help others
Yup, using the Asus files to downgrade from MM to LP bricked my brother's phone. I've tried a few methods with xFSTK to fix it but nothing has worked so far. Looks like the phone will be recycled Oh well, he seems pretty happy with his Samsung Note 3 for now
audit13 said:
Yup, using the Asus files to downgrade from MM to LP bricked my brother's phone. I've tried a few methods with xFSTK to fix it but nothing has worked so far. Looks like the phone will be recycled Oh well, he seems pretty happy with his Samsung Note 3 for now
Click to expand...
Click to collapse
Yup , even tho i can unbrick in xFSTK in less time it takes to downgrade (everytime success btw) -- pay attention to the video... on the edited files i show in file manager
timbernot said:
Yup , even tho i can unbrick in xFSTK in less time it takes to downgrade (everytime success btw) -- pay attention to the video... on the edited files i show in file manager
Click to expand...
Click to collapse
Thanks, I'll give it another go when I have a chance.
audit13 said:
Thanks, I'll give it another go when I have a chance.
Click to expand...
Click to collapse
You need to have a working device to downgrade via SD :good:
Okay, I was able to restore stock MM to the phone which is what it has before it bricked. Problem now is that I can't verify the Google account I tried both of my google accounts without success. I'll have to find some other method.
audit13 said:
Okay, I was able to restore stock MM to the phone which is what it has before it bricked. Problem now is that I can't verify the Google account I tried both of my google accounts without success. I'll have to find some other method.
Click to expand...
Click to collapse
But you was bricked a moment ago - no comprehendi ?:laugh:
If you used xFSTK you wouldnt need to downgrade , you would be in LP already.
If done on another device try later , maybe a reboot :good:
I was bricked and was able to iFSTK to get into the bootloader. I then used the Asus Flash tool to flash an MM raw file to at least get the phone booted. I was happy until I was stuck at the set up screen with no way to verify the google account.
Now its time to party vid coming soon .
All the very best wishes to each and all
audit13 said:
I was bricked and was able to iFSTK to get into the bootloader. I then used the Asus Flash tool to flash an MM raw file to at least get the phone booted. I was happy until I was stuck at the set up screen with no way to verify the google account.
Click to expand...
Click to collapse
MM raw file Hey , please share here ?
If there even is a MM raw file that is
Flash 5.0 raw for 5.0 then you wont need to downgrade btw
And this is nothing to do with downgrading via SD card btw - off topic
I believe I used the MM ww raw file from here: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
audit13 said:
I believe I used the MM ww raw file from here: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Do you know what you are doing ?
Saying , posting ?
Do you have a zenfone ?
Let me know which one of my posts is confusing and I'll try to clarify.
On 551 Z00A or AD the official downgrade version of LP WW-52.20.40.196 firmware from any M stock firmware - via sd card
https://www.youtube.com/watch?v=_1T6SMJiUSg&feature=youtu.be
OP updated
Merry Xmas to all at XDA --Still seeing people looking to downgrade from M to LP even after posting this method above via ext SD card - WOW
So , my present to you is a video of the above process
Say NO to anymore bricks Say NO to ever having to use xFSTK downloader again
This makes our phones fully , changeable forwards and backwards via SD card (for good)
The process will go from .184 M to .196 LP on the 551 Z00AD or Z00A
If you Have MM bl custom rom - use giovix`s Modder tool to `return to stock option` flash boot.img - flash recovery option in Modder . Follow process.
Video Coming Soon ...........
Ps, i assume the process will be exactly the same for Z008 from the latest Stock M to LP but using the relevant downgrade version(whatever that is) from official ASUS site for Z008
I dont have a Z008 so if anyone wishes to attempt it and give me your results here , that would be great for others
pps, i decided to do the video due to either people dont trust this method or people are extremely shy about hitting the thanks button . Whichever -- help others
audit13 said:
Let me know which one of my posts is confusing and I'll try to clarify.
Click to expand...
Click to collapse
Hi , I understand where you went wrong , you flash raw again in boot loader ,where it stays on ' RESULT=OK ' a couple of mins into flash in on screen cmds , you close flash tools . Force close it...restart flash tools .put all stuff in again ...then press vol+ once.
Leave connected to PC from first part flash all the way through closing flash tools and restarting flash ..do not touch fone apart from vol + before second flash.
Serial will be corrected and you will boot into system.
There is a vid of this exact process in my unbrick thread.
Enjoy
Ps , I never let the first flash finish , due to knowing above process to correct serial..
So if you run into probs , you may need to re flash in xfstk again.
timbernot said:
Hi , I understand where you went wrong , you flash raw again in boot loader ,where it stays on ' RESULT=OK ' a couple of mins into flash in on screen cmds , you close flash tools . Force close it...restart flash tools .put all stuff in again ...then press vol+ once.
Leave connected to PC from first part flash all the way through closing flash tools and restarting flash ..do not touch fone apart from vol + before second flash.
Serial will be corrected and you will boot into system.
There is a vid of this exact process in my unbrick thread.
Enjoy
Ps , I never let the first flash finish , due to knowing above process to correct serial..
So if you run into probs , you may need to re flash in xfstk again.
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU! It worked.
This is what I did to cause the loss of serial #:
used the sd card method to downgrade from MM based on instructions from another forum (i.e. not XDA);
phone got stuck at the erasing portion of the process and stayed there for about 45 minutes so I powered off the phone;
used xFSTK to successfully flash the bootloader
successfully flashed MM raw file with Asus Flash Tool;
tried to downgrade to LP again and bricked again;
used SFSTK again but serial # was now abcde... in bootloader so I used Asus Flash Tool again. AFT never finished flashing a ROMand the phone was stuck on the bootloader screen with "Result: okay" so I just shut down the phone and left it off until I saw your post this morning.
Edit:
I set up the phone ran software update option from settings but the Android Version is 5.0? Also, when I boot into fastboot, I see the serial # as abcde... but I can get the proper serial # by pressing the volume up and down keys a few times. Lastly, my SD card is not seen in recovery but is seen in the ROM. When I boot to recovery from the bootloader, I see this:
Android system recovery <3e>
LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user
E:file path/tmp/last_install
E:file path /cache
E:file path /tmp
Finding update package
Opening update package
E: file path:/sdcard/MOFD_SDUPDATE.ZIP
E: failed to map file
SD installation aborted.
E: Installation failed with status 1
I'm not too worried as these things are cosmetic. The important thing is the phone now works
Just to clear things up.
You never bricked your device using the method in the OP regarding downgrading via sd card. So not to scare people off .
Mofd sdupdate method is for adb sideload using a cable.
In the video it shows how files must be written when downloaded for each stock firmware in file manager in the first few mins. To be recognised from ext sd
Lastly , 2.20 in firmware or raw = LP
4.21 = M which doesn't have a raw yet unless I missed it coming about

Question Steps to root

I have a WW version of ROG Phone 6. I have had it since mid-July.
Previously, I had ROG 2 but it died on me unexpectedly and I switched to Pixel 6, which was very underwhelming. I pre-ordered ROG 6 as soon as it became available.
I have not seen a concise guide to rooting ROG 6. I think it should be the same as ROG 2 but just in case, I read guide to rooting ROG 5.
Are the steps to rooting ROG 6 the same as ROG 5?
Asus ROG phone 5: unlock bootloader and root guide
Asus rog phone 5 guide note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas. bootloader unlock: ! note that unlocking...
forum.xda-developers.com
Thank you!
I sure hope so. . . I cant find much material online but I'm going to try to just run this tool from asus https://rog.asus.com/phones/rog-phone-6-model/helpdesk_download/ and then flash magisk via recovery.
Sorry extract boot.img move it to phone, patch it with magisk and then run
Code:
fastboot flash boot magisk_patched.img
and that should do it. Although you may want/need to flash the official files first by running the flashall_AFT.cmd file.
Found this all on https://forum.xda-developers.com/t/...e-6-can-be-used-for-cn-ww-converting.4474383/ and https://forum.xda-developers.com/t/...-guide-you-should-read.4474241/#post-87255303
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
leathan said:
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
Click to expand...
Click to collapse
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
ausaras said:
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
Click to expand...
Click to collapse
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
leathan said:
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
Click to expand...
Click to collapse
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
You should be done. I just fully updated and then rooted and set up my phone.
The firmware flash would have been to swap over to CN or WW. If you do that then yes you would re-factory reset + re flash stock boot.img. Then afterwards repeat the boot.img patch to obtain root + repeat setting up your safteynetfix + any other magisk modules.
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
Hi, I am sorry the last answer I gave you was just wrong. I totally forgot when we root we wont get automatic OTA updates. Which for me is a really good thing anyway. But to get the OTA updates we need to download the firmware files from ASUS website. The same place we downloaded the unlock app but its under firmware. Download every WW firmware and put them one by one in order from oldest to newest on the /sdcard and boot up and it will detect an update. I'm pretty sure we cannot just skip to the latest update like we can with custom rom otas so I am going in order.
I left root, and when done updating will again patch the boot.img and flash it over.
Over the weekend I helped a guy root and set up safteynet and if it helps others I might just write up a tutorial.
Cheers!
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strage (or are least I think It strage):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
i need fastboot driver for win 64
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
can anyone provide the patched boot image to have root? Tried looking and asking in other areas but no luck. Or is there a way to patch a bot image that contains root already?

Categories

Resources