Related
Hi,
I bought a faulty Nexus one from ebay, thought I can fix it, as I did buy a faulty desire from ebay and was able to fix it. This time im not so lucky I guess.
So here it is:
The phone is stuck at X when booting normally.
I can access HBoot (But not Hboot USB Plug, because USB debugging is not enabled) and Fastboot USB. I unlocked Hboot. Fastboot in PC recognizes the phone but ADB does not as usb debugging is not enabled.
The phone is not Rooted
Here are my ideas so far:
Get somehow debugging on with some commands (No luck from reshearching in google)
Reflash stock rom with PASSIMG.ZIP in sdcard, but my phone does not recognize the file from my sdcard (I'm pretty certain im doing something wrong or my idea is somehow wrong)
Flash new images through FASTBOOT, but every time Signature check fails (Shipped-roms.com).
Root with superboot, but signature check failed here too.
Flash a recovery, signature check fails.
I will reguraly update my tries
Please suggest correction to my ideas or suggest new ones!
Help will be much appreciated!
I admit it, the phone might be briked, but I want to make sure that I have tried everything before I abandon this project.
And ofcourse I have no Warranty.
What file are you using for passimg.zip? Make sure it's not a zip inside a zip.
What images are you using via the fastboot flash command?
Sent from my Nexus One
You didn't unlock the bootloader, it seems - because if you did, it wouldn't be checking signatures, and you'd be able to flash anything.
First of thanks to both of you for helping.
I'm pretty sure that i do not have zip inside zip and I downloaded them from shipped roms.com -> android -> Passion-> PASSIMG_Google .... .ZIP, (Then renamed it ofcourse) Is there a difference what version of android i use?
The issue with this is, it checks the SD CARD and does not find anything. I have seen from google that the most common issue is that it starts to check the .zip file but then aborts. Does the SDCARD have to be a goldcard (I do have a goldcard but it might be faulty, right?)
I tried fastboot flash PASSIMG_Google.... .ZIP; Fastboot Flashall ( With having boot, recovery, system in my fastboot folder)
Maybe I should try to flash everything the .zip has in it seperately because that succeded for boot, system and recovery but I was too afraid to flash every partitation (Like Radio which seems to be the scariest and the most easiest way to brick phone)
For the third answer, I have ***UNLOCKED*** in bootloader in purple and top on the screen.
Once again thanks and keep suggesting!
Unpack the ZIP and flash each image separately.
Leave the radio as is, if it's updated enough (5.08 or 5.12). In any case, fastboot won't allow you to flash bad radio - and the risk of bricking the phone using fastboot is near 0.
For passimg.zip, you need to download the FRG33 shipped ROM from shipped-roms.com then EXTRACT the zip file that is inside the zip that you downloaded. Rename that file to passimg.zip
For fastboot, flash boot and system seperately.
When you boot the device normally, do you see the lock icon below the four colored x?
Sent from my Nexus One
Okay,
Did it one by one (PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip):
Succeeded:
Boot, Recovery, System and Userdata (that was only 3Kb)
Failed with signature check (Remote:Signature check failed):
Splash1, spcustom,
Did not do:
Radio
I'm going to post more details:
When booting up, it displays the X normally with the unlocking badge on the bottom of the screen and vibrates once. Then it goes black for a second or even less, the same images comes on and then it vibrates 6-7 times.
now that you successfully flashed the stock recovery, cam you boot into it?
Sent from my Nexus One
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
http://forum.xda-developers.com/showthread.php?t=710937
Thanks, Well thats it then for now, just have to figure out what to do now
Sounds like you need to get the PASSIMG.zip method to work, or unlock and flash a new recovery like amon ra, and flash a full rom with sig checks off.
siimplangi said:
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
Click to expand...
Click to collapse
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
any solution?
efrant said:
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
Click to expand...
Click to collapse
hi guys.i have exactly same situation.
does anyone have a solution fir this?
kobi_eidelman said:
hi guys.i have exactly same situation.
does anyone have a solution fir this?
Click to expand...
Click to collapse
Did you try all the solutions suggested above (passimg, fastboot flash, etc)? If yes then no I don't think so.
A quirk of the Advent Vega (also Tegra) that allows you to enter fastboot mode also applies on the 2X (Thanks Bumble-Bee for the tip!)
Basically, if you wipe the boot partition (e.g. 'dd if=/dev/zero of=/dev/block/mmcblk0p5') then reboot, the device drops to fastboot.
Handy testing feature for devs.
P
That sounds great!
Does fastboot boot work? Does fastboot flash work? Any other lockdowns there?
maxisma said:
That sounds great!
Does fastboot boot work? Does fastboot flash work? Any other lockdowns there?
Click to expand...
Click to collapse
Fastboot boot did, didn't try anything else yet!
P
Fastboot flash works, ish.
I could flash recovery, but not boot. What would be nice is a radio in .img format so I don't have to backup and restore the bastard thing when a new one is out.
Ahh this would be so awsome.. since i Smartflash can't detect my P990
(so i can't flash the latest basebands or revert them)
Gief Radio in .img format !
Would anyone Know how to get the radio as .img ?
Would this work on the T-Mobile LG G2X?
Good question.
I expect the boot partition is different, so don't blindly follow the command here.
Rusty! said:
Good question.
I expect the boot partition is different, so don't blindly follow the command here.
Click to expand...
Click to collapse
I did follow the command blindly with my P990, but no boot for me. Luckily there's an escape with the NVflash stock ROM.
It's fine on the P990, it's meant to 'not' boot, it's not broken at that stage, it's in fastboot. You can fastboot boot your way out of it.
Is this a safe option to try on my v10D? Fastboot decreases boot time by how much really?
That's not what fastboot means, to be honest, this isn't going to be for you
Hey All,
I was trying to install GingerStreak 2.4.4 from GingerStreak 2.4.3.
http://forum.xda-developers.com/show....php?t=1333010
According to the instructions, I flashed
amss.mbn - http://mirror2.streakdroid.com/amss.mbn
and
dsp1.mbn - http://mirror2.streakdroid.com/dsp1.mbn
(got both the files from the first link above)
Then when I tried to reboot into Bootloader (Power+Vol Up+Vol Down) but nothing happens apart from the Dell logo being displayed.
I try to boot normally, still stuck at the Dell logo. The phone never even reaches the boot animation.
I try to go boot into fastboot (power+camera key)mode, but the phone never even boots. The screen stays off, so do the LED lights.
I figured out that the files downloaded above were incomplete(due to slow speed Chrome showed incomplete files as download complete).
amss downloaded: 111KB. Actual Size: 15.41MB
DSP1 Downloaded: 250KB. Actual Size: 8.94MB
So, I flashed the wrong files.
Now, I guess, the phone is bricked big time.
I need big time to get into fastboot mode (to flash the correct files) or anyhow get my phone working.
Guys, need help. Please help me out and get this issue sorted out.
You should maybe consider the Streak forum...
Sorry, my bad. I just searched for my problem an found this thread. Poured out all my worried without bothering to check on the device name.
Thanks anyhow!
I love my bionic, and it has plenty of life left in it. Except for the fact that I screwed it up. Here's what happened: I had it rooted, had bootstap installed, backed up my system using the bootsrap recovery, and then tried to install a CM 10.1 zip file I found from somewhere on these forums. It gets to the load screen and then I see the blue CM wheel that NEVER stops turning (at least not within the 4 hours or so I let it run). No problem I say, I'll just reload my backup. Oh wait, you need a working system to do that. DOH!! So now, if I let it boot normally I get the perpetual CM boot screen. I've downloaded several other ROMs and tried to use the stock recovery to install them but it keeps saying "signiture not verified" or some such other nonsense which leads me to believe that's not an option. I've spent quite a bit of energy googling and going through forums on how to fix this, but all I can find are how to's with old outdated links.
If someone has a current link to whatever .xfz file I need or some other magical way to fix this, I would be indebted to you. As I said, I love this phone (it still looks and functions like new otherwise) and it seems like in it's current state I should be able to fix it somehow but I may be on my way to the Verizon store a little earlier than planned if I cant figure this out. Any takers?
Sounds very similiar to my issue.. no response to mine yet either.
Here's a link for your RSD
http://sbf.droid-developers.org/cdma_targa/VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip
Use RSD Lite to restore your phone. Google is your friend. Read & follow all instructions. I am in no way responsible for what you do to your phone.
Best of luck!
Low battery when trying to program bootloader.
Ok, I made somewhat of a noob mistake here. I read somewhere that there was an ICS ROM that could be flashed on the safe side using Bootstrap. Thing is, I couldn't remember or find the one I'd read about. Long story short, I flashed Icarus 1.8.3 on safe side using Bootstrap, which didn't work. I wiped everything there is to, including System. Big No No. Phone no likey Icarus on safe side (I know, the instructions said Safestrap 3.11 only). My question, other than buying a spare battery charger to charge the battery without the phone, can I charge it using the phone? I can boot into stock recovery, bootloader, and the screen where you select Normal Boot, Fast Flash, etc. I'll buy the charger if need be, but I'd rather not shell out the $50 or so for it if I don't have to. Thanks in advance.
:thumbup:
Edited to reflect personal unbrick success:
For those of you looking for a way to flash the SBF/FXZ file from within a Linux environment:
There's a "manual" method suggested at a different site using fastboot; unzip the zip archive (SBF file) and flash the listed/pertinent files/images individually to the device. It's still written up with windows-users in mind, but I don't see why it wouldn't work in Linux. Hope that helps someone.
Here's the jist of the commands that were involved in succesfully unbricking my Droid Bionic using the appropriate SBF file for my Android version:
Code:
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash mbmloader mbmloader.bin
fastboot flash mbm mbm.bin
fastboot reboot-bootloader
fastboot flash cdt.bin cdt.bin
fastboot erase cache
fastboot erase userdata
fastboot flash lbl lbl
fastboot flash ebr ebr
fastboot flash mbr mbr
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cdrom cdrom
fastboot flash preinstall preinstall.img
fastboot flash webtop grfs.img (skip this step if you are using a JB fxz)
fastboot flash radio radio.img
fastboot reboot
Obviously, don't forget that you have to be in fastboot mode to use the `fastboot` command (Hardware keys: VolUp +Power)
**Once again, I was lucky enough to stumble upon a posting by someone else on androidforums. Feel free to check it out at the above-mentioned link, perhaps you could adapt it to your own situation in times of despair.
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Mr. HQ said:
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Click to expand...
Click to collapse
Yup...they have a neatly organized list view of the SBF files, for all of the different android versions for the Droid Bionic (XT875), as well as a huge number of other devices.
Here's the section for the Bionic: http://sbf.droid-developers.org/cdma_targa/list.php
I can't exactly speak for how to solve the original problem, but for others who may search here. I use safestrap on my phones (3 between the kids and I all Bionics) and I put a newer version of Cyanogenmod on one phone just yesterday and I had the same problem. after trying a few things and still having the stuck boot, I deleted the ROM1 (this was the ROM slot I was using) slot and re-created it. Next I reinstalled CM10.1.3 and it booted. Safestrap is a great way to flash custom ROMS in my opinion I would recommend it highly!
Thanks for this one
Mr. HQ said:
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Click to expand...
Click to collapse
Glad I read this post....
Xt875 hard brick
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery
SPheDaGhost said:
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery[/
are you sure your battery is good? you need to externally charge your bat, sometimes when phone is not functioning properly the bat will rapidly discharge, i dont know how clever you are but you can cut the end off an old charger and achieve a recharge by cleverly connecting the cut off leads to the bat
Click to expand...
Click to collapse
Have a external battery charger
hugh a said:
SPheDaGhost said:
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery[/
are you sure your battery is good? you need to externally charge your bat, sometimes when phone is not functioning properly the bat will rapidly discharge, i dont know how clever you are but you can cut the end off an old charger and achieve a recharge by cleverly connecting the cut off leads to the bat
Click to expand...
Click to collapse
I have a external batter charger (see attachment) already, although I do know how to make one myself. It was less time consuming to go to the store and buy one. Plus it was only 5 bucks which isn't that bad. This external battery charger also displays the percent of battery life remaining. But I'll do what you suggest and see if that works out. Another strange thing is that if I plug the usb cord without the battery the charging (white) light comes on, which before it never did.
I know that the bionic droid xt875 uses the targa firmwares. I crashed my device flashing the spyder given to me by a source here on this forum. I was trying use my bionic with a gsm network so I follow this other guide. before I had followed this guide I had run through the proper proceedures of edit build.prop and radiocomm nv edit...etc.etc.. I was only managing to get no service on the HWB so I found an article pertaining to my particular model and tried it and subsequently it failed and now I'm stuck with a nice little paper weight.
Any other suggestions with this matter would be greatly appreciated. I'll keep you posted if the conditions changes.
Click to expand...
Click to collapse
How to repair my bricked moto x xt 1052
Hi everybody...
Im new here.
I hope someone resolve it.
My moto x xt 1052 is bricked, means it is not powerup normally, no any screen displayed, no boot image, boot animation, but goes into fastboot mode sometimes on trying to go in it using hardware key pressing i.e. Power and volume down keys.
Here is the brief description what was happened......
My moto was on stock kitkat 4.4.4 for upgrading it to lollipop On 19th jan i was tried to flash cm12 over cm11 nightly as described in that thread , for that i was unlocked my bootloader, rooted it, flashed CWM touch recovery, flashed superSu zip file and flashed cm12 nightly over cm11 as described. But my device was stucked at boot logo. For resolving that issue i was flashed boot.img of prev nightly release(i.e. 1/15) through command promp using commands '' cd Downloads... cd fastboot... fastboot flash boot boot.img.
It flashesh image file successfully and device is booted successfully. I was used it till last 4days and regularly updated cm12 nightly via cmupdater.
But 4days back i was tried to remove warning message of device is ulocked bootloaded which was irritated me using same flash method and logo.bin files which was given in another thread by other members. But my BOOTLOADER IS DAMAGED and no any display was seen. I read many threads to repair it but no anyone give easy step by step guide. I was tried to repair it using motoflasher given in 1 thred. But as shown there no my device was not shown in device manager asQUSB****9** THERE is only adb interface in device manager. Also it says in motoflasher that no device was connected and output was incorrect COM port, which was refused to flash bootloader. Another thred of rescurrection of bootloader is not so easy and also download links are not useful,shows item was removed.
There is no another way, i thought bootloader is a kernel, so i was flashed zwiel kernel by same flashing method by cmd.
The problem remaims same, moto care told thay it will cost 6k for repairong which is too high. The descreltion is given in details for anyone who finds my mistakes and tell me angd give me suggestion. Xda is big deveopers forum, i know someone will help me.. So plzzz help me.
HOW CAN I REPAIR MY BOOTLOADER AND SAVE MY MOTO which will not useful then usable as a paperweight.
Have you tried to simply re flash your stock 4.4.4 firmware via fastboot since you say you can get into fastboot mode? Or rsd your 4.4.4 firmware. If you can get into fastboot mode I think you should be able to fastboot your stock 4.4.4 and be back up and running.
When in fastboot mode and phone plugged in and you type "fastboot devices" does it display a string of numbers for your device? If yes then you are good to go.
I am having a similar issue with a Sprint Moto X (1st Gen). I am able to get to fastboot mode and I have flashed the stock image for 4.4.4 using mfastboot (also re-did it using RSD lite as the boot.img gave errors using mfastboot) but the phone only still boots to a dark screen and vibrates roughly every 15 seconds.
Anyone have an idea on what else I can try? I've been scouring the boards and youtube, but haven't really come across anything on this type of issue.
Has been RDS flashing process totally completed without any errors?
The flash finishes with no errors when it goes to reboot the phone I end up at the same spot of a black screen that vibrates like its powering on then repeats every 15 seconds like its stick in a loop. Odd... I never get the smallest hint to a picture on the screen.
chousue said:
The flash finishes with no errors when it goes to reboot the phone I end up at the same spot of a black screen that vibrates like its powering on then repeats every 15 seconds like its stick in a loop. Odd... I never get the smallest hint to a picture on the screen.
Click to expand...
Click to collapse
Your symptom I'm quoting is what I've seen when a bad logo.bin has been flashed to the phone.
Can you try another? Some are in http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Thanks for the suggestion.
I tried a dew different logos but the end result is still the same. Vibrates on power up, no display at all and repeats until I hold the volume down and count to like 10 when the next buzz cycle would happen so I can get into fastboot mode again. I should note that I can't see anything in this screen as well. I was starting to wonder if it was the screen that was the issue but the bootloop has me thinking otherwise.
I have another one with a bad screen and a replacement is on the way. I guess I can test it on this one as well but I'm sure the result will be the same.
I took a gamble on this one thinking I could bring i back to life, I figured the last owner just soft bricked it and flashing the latest stock would override what mess they did. I'll tinker around some more if there are some other options otherwise I can just flip it for parts i guess.
If I run the fastboot getvar all I get all the phone info so it gives me hope that something can be done, I just don't know what, it seems like I keep cycling through the same few processes hoping for a different result. I even tried the power + Volume down for two minutes thing that's supposed to bring up the "other" recovery menu, but with no display, i don't know what happening.
In a last ditch effort I did a tear down and connection check for all the parts so everything has been removed and firmly re-attached, certainly was nice to do that there instead of on the one I know will work once I replace the screen, but it sucks to still come up empty handed. Sorry for the long rant, it's just been a long few days of trying to find ways to bring this phone back to life.
Solved with downgrading
Sorry for bad english.
I had same issue.
But solved prev saturday hole day.
Using manual method instead of rsd.
Make sure u properly installed adb and mfastboot. For that open cmd and type adb. It shows command lines and then mfastboot. It also shows command lines then you are ready to go. If not, google it for how to install adb and also for mFastboot
Then download proper stock firmware for ur device. unzip it, u will get files of system, boot etc. Copy all this files and paste into mfastboot folder. Open command prompt in that folder by pressing shift and right key of mouse.
Then boot your moto into fastboot mode by pressing power and volume down key for a seconds. If u will not get in to fastboot mode try for many times unless u get it. I will get it after trying half hour.
Connect ur device to pc and run commans given in the following link. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
End with-- fastboot adb reboot. It will reboot ur device.
Enjoy.
Thanks for the steps, I feel like I have done that already save for the few end steps with the oem commands.
So I flashed the print image using that guide and it still vibrates every 15 seconds and no display. I grabbed the retail file from the motorola site (oddly enough they only have TMO on the file name for some reason) and I flash this and it doesn't vibrate every 15 seconds, but still no display... Maybe in the end the display is bad after all...
Like mentioned before, I already have one coming in black for the one that works for sure...so I guess I'll test it on this one as well. Just wish it was as easy to disconnect/connect as my Nokia Lumia was, that took less than 10 minutes!
So, in the end it was the display afterall. I ended up getting another replacement screen as I really did not feel like attaching it and detaching it (yeah, I'm lazy sometimes). After setting up the new screen I plugged it in to charger and what do you know, battery at 0% then the motorola bootloader unlock screen after 5 or so minutes.
Now I have two phones, lol. One screen came without the speaker on the to fro some reason... And I think I just messed up my main phone removing the frame to add in that piece so lint and such doesn't get into the phone so easily... Dang it!
Edit - Yep, now it has a nice rainbow line display across the bottom where the navigate soft button would be... Guess I have to get one more screen!
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
sadik2112009 said:
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
Go to the General Forum there's a dedicated thread with official roms for your particular model. Use download the ROM and flash through rsdlite. Always make a backup since it will wipe your internal storage clean.
Sent from my XT1058 using Tapatalk
sadik2112009 said:
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
If you installed 5.1 by using one of the TWRP backups, and did NOT flash the leaked OTA zip files, then you should have only touched /system and /boot partitions.. in that case, it would be safe to flash 4.4.4.
thank u so muchh......
KidJoe said:
Your symptom I'm quoting is what I've seen when a bad logo.bin has been flashed to the phone.
Can you try another? Some are in http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Click to expand...
Click to collapse
thank you so much... this post saved my moto x...... i am facing this issue from last 15 days. so many pages visited but nothing help, but, after doing this it rebooted. may god bless you!:angel::angel::angel::angel:
Having same problem.
Please help if anyone can!
I can't resolve it by Fastboot in cmd.
I also tried typing mfastboot in all commands.
Having same problem.
Please help if anyone can!
I can't resolve it by Fastboot in cmd.
dont display anything
not charging not boot not start anything
Travisdroidx2 said:
Have you tried to simply re flash your stock 4.4.4 firmware via fastboot since you say you can get into fastboot mode? Or rsd your 4.4.4 firmware. If you can get into fastboot mode I think you should be able to fastboot your stock 4.4.4 and be back up and running.
When in fastboot mode and phone plugged in and you type "fastboot devices" does it display a string of numbers for your device? If yes then you are good to go.
Click to expand...
Click to collapse
I have a moto x of my friend xt1053, dont not what he has done with it.
but
it is in Encryption Unsuccessful Condition.
When I connect to pc. Windows show that motorola xt1053 is connected. device manager shows MTP device under portable devices.
Mototrola USB drivers have been installed successfully.
I can not boot xt1053 into fastboot mode or recovery. Neither by adb/fastboot nor by buttons. (volume down + Power).
adb devices command does not show any numbers as it normally does when device is connected.
how get it back to working condition. any expert to help or happen to be in the same boat?
...and I thought it had worked but as it turns out, it did not. I found out it did not when I tried to root to which the phone proceeded to tell me it was lock.
Now, when I go into Recovery Mode, the phone does not come up in ADB even when trying to unlock after using the ASUS unlocker tool... Is the ADB bridge fried forever? How do I reinstate it to be able to root? I don't mind wiping, I just want to recover the possibility to root. Any way to do that? God I feel dumb right now...
Edit: I've gotten ADB to recognize the phone in Recovery Mode by installing the exact Manufacturer and Model ADB drivers but the second I get into Fastboot mode, it's like the side USB-C suddenly becomes non-existent, same goes for the bottom one. Feels like a kill.switch from ASUS to me :/
Edit 2: Is there a way to flash while in Recovery? Or in normal OS operations? (sounds like a bad idea but I'm out of ideas as of now)
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
dennis96411 said:
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
Click to expand...
Click to collapse
Exactly, the bootloader is also unlocked after using ASUS's tool .apk, I am on 1910.44 WW, I tried different ADB's while in Windows, tried to copy DeviceID, it all works when in normal boot OR in recovery mode but the second I am in fastboot mode, both USB's stop working. As if ASUS locked the access when I mistakenly tried to gain root while the bootloader was locked. Maybe if I could lock it back but that would require me being in fastboot afaik.
Can I lock it back while in recovery? If so, what would be the prompt?
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
dennis96411 said:
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
Click to expand...
Click to collapse
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
WhyKlwd said:
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
Click to expand...
Click to collapse
Is there an option to apply a full OTA from the stock recovery?
dennis96411 said:
Is there an option to apply a full OTA from the stock recovery?
Click to expand...
Click to collapse
Before anything, thanks for helping, it's greatly appreciated!
So, no sadly, when I get in Recovery Mode my options are:
Reboot system now
Reboot to bootloader
Wipe data/factory reset
Power off
As anyone would, I tried kicking into bootloader from recovery hoping that it would trigger something different to give me fastboot but to no avail, I wiped a couple of times as well, that didn't pan out.
Edit: I feel like my best chance at this point is when ASUS releases a new WW firmware update, that it HOPEFULLY brings Fastboot Mode to it's original value... But according to a thread somewhere on XDA, it does not install a full partitioned recovery so I'm not having my hopes up...
The other thing would be to butcher a USB-C cable and see if I get a response when connected on the orange USB-C but that's also a risk to take. So that doesn't work, that USB-C gets no response whatsoever.
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
HomerSp said:
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
Click to expand...
Click to collapse
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
WhyKlwd said:
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
Click to expand...
Click to collapse
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
HomerSp said:
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
Click to expand...
Click to collapse
Yeah it works, or at least it did long enough for me to be able to root. I haven't tried it since but I would assume that it fixed it, tomorrow I'll most likely do a RAW flash to fix all potential risks as well as try the latest CN firmware. EDL never worked, that's what got me in that situation in the first place... well that and me not paying full attention.