Related
Phone was fine, rooted, flashed roms,
Today flashed a rom and was a bad flash, now im stuck in bootloader screen, and try to select recovery twrp is gone.
tried to select factory reset from there just kicks me back to same fastboot/bootloader screen.
Anyway to restore to stock and redo everything? Was able to force twrp on last time but laptop isnt recognizing phone right now.
Thanks in advanced
solved, thank you.
nitty917 said:
Phone was fine, rooted, flashed roms,
Today flashed a rom and was a bad flash, now im stuck in bootloader screen, and try to select recovery twrp is gone.
tried to select factory reset from there just kicks me back to same fastboot/bootloader screen.
Anyway to restore to stock and redo everything? Was able to force twrp on last time but laptop isnt recognizing phone right now.
Thanks in advanced
solved, thank you.
Click to expand...
Click to collapse
I am going through the same mess right now. Flashed a ROM, bad flash...lost TWRP, so I thought to use hasoon's tool...well I relocked like a moron and still stuck so if anyone would like to chime in that would be awesome...
hooover said:
I am going through the same mess right now. Flashed a ROM, bad flash...lost TWRP, so I thought to use hasoon's tool...well I relocked like a moron and still stuck so if anyone would like to chime in that would be awesome...
Click to expand...
Click to collapse
If you relocked then you gotta unlock while you are in fastboot mode with your Unlock_code.bin. The other option is to flash the Stock RUU and use that, but I'm sure you rather have a Custom Rom. I'm going thru the same thing atm. Anyway use hasoon's tool to unlock your phone again.
yea just start from scratch now. RUU and return to stock
TygerByte said:
If you relocked then you gotta unlock while you are in fastboot mode with your Unlock_code.bin. The other option is to flash the Stock RUU and use that, but I'm sure you rather have a Custom Rom. I'm going thru the same thing atm. Anyway use hasoon's tool to unlock your phone again.
Click to expand...
Click to collapse
Unfortunately, I am being told not found by the tool now, and being stuck in boot loader it won't detect the device....I feel like a heel, I have been around for a while and never had an issue like this!
Yea, you guys are correct...Unlocked boot loader again via Hassoon's tool [Many thanks to this guy], question...where did my TWRP originally go? OP sorry I came in and jacked the thread, I just figured we were fighting a common battle.
hooover said:
Unfortunately, I am being told not found by the tool now, and being stuck in boot loader it won't detect the device....I feel like a heel, I have been around for a while and never had an issue like this!
Click to expand...
Click to collapse
it has to be "FASTBOOT USB" in order for the tool to unlock your phone again. i would check your htc drivers and possibly restart your computer if you haven't done so already.
TygerByte said:
it has to be "FASTBOOT USB" in order for the tool to unlock your phone again. i would check your htc drivers and possibly restart your computer if you haven't done so already.
Click to expand...
Click to collapse
Yea, I got it...THANK YOU! Patience is something I lack at times.
Used the Multi tool to unlock, then it booted right back to my custom ROM...I had to reflash TWRP, which boggles me...
I read through many threads and have followed the official Sony bootloader unlocking instructions. I have requested and received the unlock code from Sony via email. I have downloaded the inf file and placed it in the correct folder in Android SDK (which I also updated). But I am cannot access fastboot mode, I hold down Vol + and plug in the USB cable but the device shows a red led and goes into charging mode. Also the PC never prompts me to install fastboot driver it simply loads the SP as Sony mass storage device (in device manager).
I have read that some people seem to think that the SIM lock affects the ability to access fastboot but this SP is SIM unlocked. Sony's official guide to unlocking the bootloader says I need to access fastboot mode to enter the unlock code but how can I unlock the bootloader if I can't get into fastboot mode?
hmmm... don't know really... i once entered fastboot mode by mistake, while trying to root stock rom. wasn't reading instructions and put device in a fsatboot mode instead of debugging... was on stock rom so don't know if custom rom would let me do that. should check myself... if anything i know it is possible to get me that blue light shining.
To enter fastboot mode in Xperia SP just power down the phone and hold down the volume up key while pluging your phone into your pc
If you need flashmode do the same thing but with the volume DOWN button held down.
I´ve got the same problem. I can´t enter in flashmode neither in fastboot mode. I´m on windows 8 32bits and I installed the .245 Deodexed ROM with a problem on root and without CWM. I don´t know what to do now, please help me.
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
jackaros said:
Sorry for that i dont think that it is your computers fault because you enter fastboot (and flashmode) using your mobile phone NOT your PC
So i would roughly assume that this is a Rom bug or something in the flashing proccess went wrong.
Click to expand...
Click to collapse
Thanks for trying to help, but I understand that flashmode and fastboot are accessed using the phone. Actually the phone needs a piece of software like flashtool to keep it in flashmode otherwise it drops into charging mode. I didn't mention my computer so I don't know where you got that from.
As I explained, I am unable to access fastboot with stock ROM (1.257) and a custom ROM (based on 2.245) so it can't be a ROM bug or the flashing process having gone wrong.
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Ze Tolas said:
Same problem here, i can't do anything using flashtool after flashed 2.245. I did with SUS, maybe is some flashtool issue.
Click to expand...
Click to collapse
It may be a flashtool problem you are right because 2 incidents with different Roms that both use flashtool to flash those roms.....
its pretty much self explenatory.
skojevac said:
if it's not too much of a trouble for you, go and flash .245 stock, than .257 stock kernel only. like you are trying to root it for the first time, complete rooting procedure, and than proceed on to installing CWM, but instead of connecting device in debugging mode to install CWM, try and see if you can put it in a fastboot. this was exactly the moment when i accidentally put mine SP in fastboot. of course, i'm not saying to go ahead and install anything if you score, but only to confirm if you can put your device into a fastboot mode since installing anything without CWM will likely soft brick your device.
Click to expand...
Click to collapse
Interesting. Ok, I've read up on the process. So I use the various stock .ftf files and flashtool with the phone in flash mode? Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. If I do it, I will nandroid backup first, of course, but I think I remember reading in one thread that someone managed to soft brick their XSP doing this very thing.
Bear in mind that kernel didn't allow fastboot when I used it with the stock .257 ROM the device came with. [/QUOTE said:
that's why you need to complete rooting procedure. root stock 1.257 kernel, than back to stock 2.245 with root preserved, and before you would install CWM try to put device in a fastboot mode, this assuming you still have a UB.
Click to expand...
Click to collapse
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
SuicideFlasher said:
have you tried to boot into android, open a root terminal and type
exec reboot bootloader
that should bring you straight into fastboot
Click to expand...
Click to collapse
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
skojevac said:
i just placed my in a fastboot mode, no problems whatsoever. do you have drivers for the device installed? you will find these in flashtool installation folder.
Click to expand...
Click to collapse
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
gandalf_grey91 said:
Yes. The fastboot_with_android_usb_file.rar package specified on DooMLoRD's bootloader unlocking/relocking appears to have been removed and there are no new links in that thread. So, I found and installed the drivers included with the flashtool. But it seems to be the device that is the problem. It is acting like a carrier locked model. I am rapidly starting to believe that this one has a locked bootloader.
Click to expand...
Click to collapse
I said before, it's new firmware (maybe RU) with a Windows Flashtool issue. Today i did flash kernel to my SP using Linux client.
Same issues
gandalf_grey91 said:
All that happens is that the terminal session ends and closes (not FC) the terminal app. Using the same command via adb just does a standard reboot.
Click to expand...
Click to collapse
Hi, I have some similar issues. I've also been flashing some stuff and whenever I try to go to fastboot it just boots into CWM. Very annoying to say the least. The dark blue light goes on when i hold down volume up and for a short moment I see the fastboot driver installing on my computer. But before it completes it's already in CWM.
Not sure what to do from here on wards, maybe some advice on which kernel to flash? I am pretty sure the latest kernel I flashed is the .254 root kernel from doomlord.
Ps. I really would like to flash CM when it becomes available as nightly :angel:
Thanks in advance!
Fast boot mode for xperia ion hspa???
gandalf_grey91 said:
As I explained in the first post, I understand how to access fastboot mode (and flash mode). I got root and backed up the TA partition, the stock apps (from 1.257) and backed up the stock ROM. Then, after I wasn't able to get into fastboot, I have installed CWM for LB and flashed a custom ROM based on 2.245. I am able to enter flash mode but not fastboot. As I said before, the phone is SIM unlocked but is acting like it came from a carrier, with locked bootloader and fastboot disabled. How can Sony disable fastboot? I don't get it. Any one want to take a guess how long I will have to wait until some clever dev finds an exploit?
Click to expand...
Click to collapse
I had already installed cm10.1 jb for my xperia ion.
Now i tried to install cm11 kitkat for my xperia ion.
Every thing is gone good.
But now got stuck up with a problem.
fast boot mode is active only for 5 seconds while connecting my xperia ion to System with flash tool.
help me to do the need ful.
Guide me to download compatible drivers and flash tool for fast booting process.
If you have UNLOCKABLE bootloader, then you dont have a FASTBOOT mode on your phone. Its just pure luck. some phones dont have it... kind of a sony crap... I also happen to be one of those LUCKY ppl. no unlock, so stuck with Stock kernel forever.
When you connect your phone to Flashtools in FLASHMODE...
See for a string BOOTLOADER: NOT_ROOTABLE.... it means you belong in the lucky group...
If it says rootable, then you're doing something wrong.
Pardon me if i read something incorrect. i skimmed through all the posts before posting.
Hi Guys.
So recently I posted about resetting nexus 6 to factory default so I can send it off for a warranty repair.
In the mean time. I've dropped it about 20 times.
The glass is cracked and the screen is broken too.
I want to back everything up before sending the device off for a repair but there's a problem.
The device has a pin at boot and I can't get in because the digitizer is dead.
Whenever I try to use adb it just says "offline".
Is there any way I can get around this and make a backup??
please help thanks
can i dirty flash something from bootloader? i don't care if it breaks all the apps because I just want to boot the device and pull /sdcard/ via adb. Any help pleeeeeeeeaaaaase
joncy92 said:
can i dirty flash something from bootloader? i don't care if it breaks all the apps because I just want to boot the device and pull /sdcard/ via adb. Any help pleeeeeeeeaaaaase
Click to expand...
Click to collapse
first off, question and need for help gets posted in the q&a/help section, ill ask a mod to move your thread there. and secondly, you can flash the factory img via fastboot, via your bootloader
Use an otg cable and mouse to punch in the pin? Or will that not work that early in the boot process?
btw, you can boot into the recovery and use adb.
thanks for replies. I can't get into recovery it asks for a password. When I try to access the device through ADB it says "device offline"
If I flash factory through bootloader will it wipe all the pictures n stuff?
joncy92 said:
thanks for replies. I can't get into recovery it asks for a password. When I try to access the device through ADB it says "device offline"
If I flash factory through bootloader will it wipe all the pictures n stuff?
Click to expand...
Click to collapse
if you unlock the bootloader, it will. if its already unlocked, you can flash a certain way, to keep your data.
simms22 said:
if you unlock the bootloader, it will. if its already unlocked, you can flash a certain way, to keep your data.
Click to expand...
Click to collapse
hi thanks.
Bootloader is unlocked and device running chroma rom and twrp recovery. i think forced encryption is on but I didn't decrypt the device.
Please advise how to flash and keep data. If I reflash will the pin disappear so i can backup??
joncy92 said:
hi thanks.
Bootloader is unlocked and device running chroma rom and twrp recovery. i think forced encryption is on but I didn't decrypt the device.
Please advise how to flash and keep data. If I reflash will the pin disappear so i can backup??
Click to expand...
Click to collapse
itll probably ask you for your code again. and if you could get into recovery, you could make a nandroid backup of your rom, then restore it onto another n6 later. anyways, i *think* you just avoid flashing the userdata.img, but i could be wrong. see if you can google it.
simms22 said:
itll probably ask you for your code again. and if you could get into recovery, you could make a nandroid backup of your rom, then restore it onto another n6 later. anyways, i *think* you just avoid flashing the userdata.img, but i could be wrong. see if you can google it.
Click to expand...
Click to collapse
how will I get into recovery after flashing? Won't it still be asking for a password?
joncy92 said:
how will I get into recovery after flashing? Won't it still be asking for a password?
Click to expand...
Click to collapse
you will have a stock recovery after flashing the factory.img, youd have to flash twrp again, via fastboot via your bootloader. if you will still have that issue, i dont know.
joncy92 said:
Hi Guys.
So recently I posted about resetting nexus 6 to factory default so I can send it off for a warranty repair.
In the mean time. I've dropped it about 20 times.
The glass is cracked and the screen is broken too.
Click to expand...
Click to collapse
How could this be a warranty repair?
Hi,
Well as I said I'd dropped in after logging a warranty repair with Motorola. The problem was with the volume rocker getting stuck when I pressed the up or down buttons.
I was just giving some background
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.
Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??
WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?
TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !
WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.
Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times
When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?
...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.