Develop Bugs

[Q] stuck at bootloader/odin mode

hey guys,
I sold my galaxy nexus today to my cousin, she picked up the phone, working perfectly and then came back with it half an hour later with the phone permanently in Odin Mode xD
I have experience with rooting, flashing and all of that and I can't seem to find a way of fixing the phone, basically what is going on is that every time the phone is turned on it goes straight to odin mode and from there is not able to boot or do anything, I took out the battery (believe me a lot of times) and still have the same issue, I tried booting into the bootloader but it gets stuck there and the computer does not recognize it either the toolkit or in the command prompt, I flashed via odin the following firmware http://forum.xda-developers.com/showthread.php?t=1827685 with no luck, I was just able to boot into the phone in safe mode, but from there if I reboot I'll encounter the same problem.
for me it seems like the bootloader is damaged?
any suggestions or help will be appreciated.... thanks!!

Oh boy. After reading all that I just see a bunch of errors after another error.
1) Toolkit
2) Odin
First off,
1) Delete all drivers for the Galaxy Nexus
2) Pull battery out of Galaxy Nexus then put it back in
3) Hold Volume Down + Volume Up + Power
4) Plug phone USB in.. computer should make a "BEEP" noise. If not then on the phone reboot back into bootloader and next time around it should come back.
5) http://forum.xda-developers.com/showthread.php?t=1514942 -- download these drivers and manually install the Galaxy Nexus drivers using those.
6) Set up ADB/Fastboot environment (I won't tell you how... just google it) dont use toolkits.... toolkits dont teach you how to get yourself out of these kind of situations. This is why I NEVER EVER EVER EVER endorse usage of toolkits.
7) use command prompt and prompt it towards your fastboot.exe (/sdk/platform-tools/)
8) type: fastboot devices
9) find phone? ok good
10) https://developers.google.com/android/nexus/images#takju (download the respective one. takju for GSM, etc etc -- download the right one, sprint, vzw etc)
11) fastboot flash those files.
12) fastboot oem lock
13) phone should boot
14) give it back to your cousin.
note: this leaves her available to get OTAs etc etc and you wont be responsible for anything root related. if she wishes to root / custom rom / etc (doubt it) then skip #10 and ahead. flash a custom recovery (just incase yours got screwed up) and flash a custom ROM as well as wiping factory, cache, dalvik, and boot into android.
cant boot into android but still want custom? skip #12 and above. fastboot flash those files, boot into android, drag new rom / kernel onto phone and then go back into recovery to flash it (or go into recovery and mount it to your pc and put the rom files etc onto the phone).
if this helps, hit the thank you. thanks. next time, please dont use toolkits and spend the couple of minutes reading this stuff on how it works rather than having it spoon fed to you aka toolkit!

zephiK said:
Oh boy. After reading all that I just see a bunch of errors after another error.
1) Toolkit
2) Odin
First off,
1) Delete all drivers for the Galaxy Nexus
2) Pull battery out of Galaxy Nexus then put it back in
3) Hold Volume Down + Volume Up + Power
4) Plug phone USB in.. computer should make a "BEEP" noise. If not then on the phone reboot back into bootloader and next time around it should come back.
5) http://forum.xda-developers.com/showthread.php?t=1514942 -- download these drivers and manually install the Galaxy Nexus drivers using those.
6) Set up ADB/Fastboot environment (I won't tell you how... just google it) dont use toolkits.... toolkits dont teach you how to get yourself out of these kind of situations. This is why I NEVER EVER EVER EVER endorse usage of toolkits.
7) use command prompt and prompt it towards your fastboot.exe (/sdk/platform-tools/)
8) type: fastboot devices
9) find phone? ok good
10) https://developers.google.com/android/nexus/images#takju (download the respective one. takju for GSM, etc etc -- download the right one, sprint, vzw etc)
11) fastboot flash those files.
12) fastboot oem lock
13) phone should boot
14) give it back to your cousin.
note: this leaves her available to get OTAs etc etc and you wont be responsible for anything root related. if she wishes to root / custom rom / etc (doubt it) then skip #10 and ahead. flash a custom recovery (just incase yours got screwed up) and flash a custom ROM as well as wiping factory, cache, dalvik, and boot into android.
cant boot into android but still want custom? skip #12 and above. fastboot flash those files, boot into android, drag new rom / kernel onto phone and then go back into recovery to flash it (or go into recovery and mount it to your pc and put the rom files etc onto the phone).
if this helps, hit the thank you. thanks. next time, please dont use toolkits and spend the couple of minutes reading this stuff on how it works rather than having it spoon fed to you aka toolkit!
Click to expand...
Click to collapse
thanks for your reply, just a quick question by installing the drivers you mean to do it while in the safe mode of the phone? I can't get the pc to recognize the phone while on bootloader.
when I get to the bootloader the phone is basically stuck. I can't select move or reboot.

davidquesada said:
thanks for your reply, just a quick question by installing the drivers you mean to do it while in the safe mode of the phone? I can't get the pc to recognize the phone while on bootloader.
when I get to the bootloader the phone is basically stuck. I can't select move or reboot.
Click to expand...
Click to collapse
That's not a good sign that you can't move using volume up/down keys in bootloader. You need the PC to detect your phone's ADB (ensure that USB debugging is enabled).
I never been to safe mode but try going into about phone -> and tapping "build #" 10 times (if you're on 4.2.X) to enable dev options and check usb debugging.

zephiK said:
That's not a good sign that you can't move using volume up/down keys in bootloader. You need the PC to detect your phone's ADB (ensure that USB debugging is enabled).
I never been to safe mode but try going into about phone -> and tapping "build #" 10 times (if you're on 4.2.X) to enable dev options and check usb debugging.
Click to expand...
Click to collapse
so.... bad news
I was able to flash again Jelly bean via odin an I was able to boot into android in safe mode (the only way it does), then using the command prompt I send it to bootloader and it got stuck and windows does not recognize it
my question is how my cousin bricked the device in like 30 minutes... because when I gave it to her it was perfectly working....

Nokia N1 bootloop

My N1 suddenly reboot and then it can't start, just continuosly bootloop and can't boot into droidboot or recovery by pressing Power+ Vol-. Any help!!!

anyone help me!

same problem

We need to know more to be able to help. What did you do before updating? root? update? nothing?

syddd said:
We need to know more to be able to help. What did you do before updating? root? update? nothing?
Click to expand...
Click to collapse
I followed this instruction http://forum.xda-developers.com/showpost.php?p=60925623&postcount=44. Root has been established successfully, then installed GApps and after the tablet does not boot

Shvonder said:
I followed this instruction http://forum.xda-developers.com/showpost.php?p=60925623&postcount=44. Root has been established successfully, then installed GApps and after the tablet does not boot
Click to expand...
Click to collapse
That's it, now it not work anymore, just reboot and play bootanimation then reboot

alan_greece said:
My N1 suddenly reboot and then it can't start, just continuosly bootloop and can't boot into droidboot or recovery by pressing Power+ Vol-. Any help!!!
Click to expand...
Click to collapse
I have same problem
Help me!!! Please

help us!

For me its working flawlessly.... may be u have done something wrong. Had u turned off mpt mode ? Did u format and cleared catch before installing gapps ?

still waiting for solution...

( help me

When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.

soondin said:
When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.
Click to expand...
Click to collapse
but when i run adb reboot bootloader, it said my device was unauthorized

soondin said:
When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.
Click to expand...
Click to collapse
i cant use ADB now, always unauthorized device....

Anyone who had a way to fix it? I tried but my N1 dont connect with the PC..

plz help us!

i can not open recovery by pressing vol- + power. I got a bootloop N1,too.

kaikool said:
i can not open recovery by pressing vol- + power. I got a bootloop N1,too.
Click to expand...
Click to collapse
Iam russian... Use the phone flash tool intel v444. connect you device via usb. reboot rebooot rebooot.... when programm detect your device. check in "custom flash" option fastboot or adb. and flash ifwi file. wait min 15.... WHEN YOU DEVICE TURN ON BOOTLOADER CANCEL FLASH (PULL USB CABBLE!!!) volume - to recovery. open recovery menu and factory reset and cache clear. update with sideload and wipe data/ reboot!

@Andreko777 thank you, ill try it. Hope it works! But i think it doesnt work because, when i plug my usb cable to my computer and run Intel flashtool, it can not regconize my device. So i cant do anything else,........
@alan_greece i have found another method in a Chinese forum, but i dont have my device here to do. you can try this.
1. Tools required:
1, Nokia N1 ROOT tools:
link: http: //pan.baidu.com/s/1c0i1KU8 Password: c7i3
2, Nokia ROM package:
link: http: //pan.baidu.com/s/1c06OrhI Password: zfg3
above package Zhongguancun Forum "installed Daitou", "expect Dawn c466469156" offer. Some pictures cut from below "expectations dawn c466469156" rescue brick tutorial (need only be able to enter the official REC tutorial) Step:
Prerequisite: There is a station has already authorized under the USB debugging mode N1 computer; N1 boot card after death, in The computer's device manager can see Android Composite ADB Interface device.
1, the N1 is turned on, connected to the computer.
2, download IntelAndroid-FBRL-05-16-2015-PTR.rar, unzip it into a directory in the root directory of the disk,
Right-click launcher.bat, choose Run as administrator.
Follow the onscreen prompts for capital ACCEPT OK. (Must be capitalized, because LINUX is case-sensitive)
viewing screen, if the device is connected, a blue-green word, if the word is red, was not connected, carefully check the above-mentioned process is correct.
3. After the device is connected, press the T1 diagram interface, Enter. N1 will restart, and N1 official BOOTLOADER screen appears, and writes in execution. Until an error message. Stop.
4, according to N1 volume keys, select the recovery, press the power button to confirm. Reboot into official REC. Then select Options apply update from adb and even computers.
5, put the package before downloading rename the file update.zip pulled platform-tools folder unzipped. Open a command indicator cd into this folder.
6, in the command prompt, type adb sideload update.zip Enter.
7, prompted reboot the N1.

kaikool said:
@Andreko777 thank you, ill try it. Hope it works! But i think it doesnt work because, when i plug my usb cable to my computer and run Intel flashtool, it can not regconize my device. So i cant do anything else,........
@alan_greece i have found another method in a Chinese forum, but i dont have my device here to do. you can try this.
1. Tools required:
1, Nokia N1 ROOT tools:
link: http: //pan.baidu.com/s/1c0i1KU8 Password: c7i3
2, Nokia ROM package:
link: http: //pan.baidu.com/s/1c06OrhI Password: zfg3
above package Zhongguancun Forum "installed Daitou", "expect Dawn c466469156" offer. Some pictures cut from below "expectations dawn c466469156" rescue brick tutorial (need only be able to enter the official REC tutorial) Step:
Prerequisite: There is a station has already authorized under the USB debugging mode N1 computer; N1 boot card after death, in The computer's device manager can see Android Composite ADB Interface device.
1, the N1 is turned on, connected to the computer.
2, download IntelAndroid-FBRL-05-16-2015-PTR.rar, unzip it into a directory in the root directory of the disk,
Right-click launcher.bat, choose Run as administrator.
Follow the onscreen prompts for capital ACCEPT OK. (Must be capitalized, because LINUX is case-sensitive)
viewing screen, if the device is connected, a blue-green word, if the word is red, was not connected, carefully check the above-mentioned process is correct.
3. After the device is connected, press the T1 diagram interface, Enter. N1 will restart, and N1 official BOOTLOADER screen appears, and writes in execution. Until an error message. Stop.
4, according to N1 volume keys, select the recovery, press the power button to confirm. Reboot into official REC. Then select Options apply update from adb and even computers.
5, put the package before downloading rename the file update.zip pulled platform-tools folder unzipped. Open a command indicator cd into this folder.
6, in the command prompt, type adb sideload update.zip Enter.
7, prompted reboot the N1.
Click to expand...
Click to collapse
Now i cant authorized my device anymore

Zenfone 2 bricked. Cannot access Recovery Mode.

Hello All,
I would like to start by saying that I am a novice when it comes to rooting phones so ANY help received here will be greatly appreciated. I have come across a few people within the various forums who have a very similar issue to the one I am having, but nothing exact. Now to the point.
Phone: Zenfone 2 (Model: ZE551ML-23-4G64GN-BK) came unlocked from amazon.com
Carrier: Metro PCS.
PC used to root: Win 7 64 bit / AV: Avast Free.
Issue: About 1 month ago I rooted my phone. Last night I received a prompt to do an OTA update, and selected install. I realized after that I shouldn't have done that, but it was too late. My phone would not load past the black and white ASUS loading screen.
I then proceeded to do some research online, and try to "unbrick" my phone myself. I figured out how to hold the power button + volume up key, select Recovery Mode with the power key, and press power + volume up again to get into the Recovery Mode. I was following some instructions online that didn't really make sense, which led me to choosing Wipe Cache Partition. This didn't work, so I had to manually reboot the phone (Hold the power key, and turn it back on). From that point forward I have been unable to get back into the Recovery Mode. Once I get to the sleeping android with the red triange I have tried holding power + volume up (which got me into recovery mode the first time), power + volume down, power + both volume up and down, I've rebooted my phone several times to make sure I was doing this as soon as the little android appeared and nothing happens. The android just pulses in and out and nothing happens. This is the first of my many problems as I have never flashed a ROM before, and I am a novice. Also my PC does not recognize my phone at all at this point. I'm using the same cable and port that I always use when transferring files. The port has been tested with a tablet and iPhone, which works. My questions are as follows:
1. Am I screwed? lol.
2. Is there a way/trick to getting into recovery mode again?
3. Can I still unbrick my phone without getting into recovery mode? Is there something I can do with my phone connected to the PC perhaps?
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089

For anyone who may have found this thread I think I found a fix here. I will let you know after I test this if it works:
http:
//valuestuffz.blogspot.com
/2015/10/fix-zenfone-2
-stuck-in-recovery-wipe-cache-partition.html?m=1
Sorry. I had to break up the link in order to post it.

Clavin0089 said:
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
Click to expand...
Click to collapse
i was in same sit with a brick of sorts and used this guid to help me:
> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html *** I used this to go from the 168/174 ( 174 didnt fix issue that 168 caused ) back to 160
> http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html *** How to enter recovery if you dont know how
make sure the phone is plugged into a usb2 port and not a 3.0
what got me is when i installed adb, it put adb files in a default directory on my hdd, so i just copied the files to the folder where where i had all files at See below
i used the .160 file to restore my phone and it worked..
now if phone isnt detected yet, you may still need files. have you tried iSocUSB-Driver ?

I followed the steps outlined in the link:
http
://valuestuffz.blogspot.com/2015/10/fix-zenfone-2-stuck-in-recovery-wipe-cache-partition.html?m=1
And everything appeared to have gone smoothly, however, now my phone just loads, and will not enter the home screen. I just have that ASUS IN SEARCH OF INCREDIBLE screen now. I was able to get into the recovery mode, but it doesn't appear to have worked. I also received the "Permission denied" errors mentioned in the link. Any suggestions?
My phone is now detected by the PC for the record.

didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time

Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
I did push over 3 files, but when I downloaded the .160, it only had droidboot.img,and boot.img. I tried both .168 (Which may have been totally wrong, but had all 3 files) and .160 from the asus website where you can select firmware. I did the .160 most recently. I put the recovery.img, droidboot.img, and boot.img into the adb folder, and ran the following CMDs:
Fastboot erase cache
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
I then used adb sideload CMD to load the .160, and it reached 100% and said successful. I attached a screenshot of what the "permission denied" CMD looks like.

Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
Tonight after work I will try the links you suggested to me once more, and let you know the results. I sincerely appreciate all of your help here! Thank you very much!

anytime...
i never seen/encountered that error message before... try adb kill-server command if you run into any issues. when you start again it will load automaticaly... have you tried different usb ports? stay on usb2.0 when connected and try original oem cable that came with the phone. if you dont have it, try different micro-usb cables ( i had issues when i had my lg g3 being on a usb3 port, so i made sure mine was plugged in a 2.0 port )

Currently i am on beanstalk, and want to go back to stock.
I flashed the stock recovery via fastboot, but when i enter into Stock Recovery mode, it gives me Error icon.
The whole process is to flash the stock zip via sideload, but i am not able to enter the stock recovery.
The stock version i am trying to flash is 2.20.40.160.
I flashed all three files, Droidboot.img, recovery.img, boot.img.
And then turned the phone off, and now it is stuck on Asus screen. Urgent Help!!

btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file

Pu$$nBooT$ said:
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Click to expand...
Click to collapse
Yeah, i looked it up, power + volume up. That did it. Thanks!

np...

Phone might be bricked. Need help to find a solution!

Hello everyone! Complete dumbass here!
I was following the guide to root my razer phone. I've had it for a couple months, and decided to root it. I followed the guide here https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137
After a couple bumps in the road, such as fastboot commands not working, not being recognized, etc. I finally was able to unlock bootloader and install twrp. But it was #9 that got me stuck again.
"9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip."
In recovery, adb devices and fastboot devices yielded no devices attached. Doing a search, I came across another forum post where it states the sdcard is encrypted and can't be accessed in twrp, and the fix is to do something like "Wipe>Wipe Data> Type Yes" and that should factory set the card. I did this and rebooted the device. I waited for a half hour for the animated PixelFloatingInACircle logo to be done with it's floating in a circle, but ended up going to bed and letting it die. Woke up this morning, plugged it in, got the razer logo splash screen with the orange text telling me of my impending doom, then went back to the animation. I let my dog out and came back and it was still on. I unplugged it and am letting it die again to see if there's another solution.
I'm wondering if anyone else came across this issue, and if so, how did they fix it? Any help would be appreciated.

Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk

waiflih said:
Use the factory images in the developer portal. You have to manually install the fastboot driver or you won't see the phone in fastboot devices. After that you can flash_all.bat.
PS: if you just want root you can use magisk installer to patch the boot image (from the factory images) and then flash the patched_image.img. That's it, now you have root via magisk
Click to expand...
Click to collapse
The problem is when I try to enter download/recovery mode after charging the battery a little, it doesn't go to that menu. Instead, it skips right to the particle logo, and that's where it hangs.
The only guide I saw was the one I listed. Is there a guide for this magisk installer?(Ya know, in case I figure the first problem out, so I might try my hand at potentially creating another)

i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons
Click to expand...
Click to collapse
Tried this originally after I let it die the first time. It still boot to the animation logo.

Bloodeagle said:
Tried this originally after I let it die the first time. It still boot to the animation logo.
Click to expand...
Click to collapse
Read the edit, I found that the trigger is having the usb cable connected to the pc. Try that, or you can also try to adb while the device is booting (particles logo). Sometimes adb is responsive even when booting. There you can try to adb reboot bootloader

waiflih said:
i think there is a way to hard reboot the phone, so you can do that and then hold the vol- key to start in bootloader mode when it reboots.
gonna check the correct buttons.
Edit: the button combination is power+vol+ for about 10-15 seconds, and the phone will reboot. You have to connect the phone via usb cable (before rebooting) to the computer (the only thing i'm not sure is if you have to have the fastboot drivers in the pc installed previously or if you can do it after entering fastboot) and just after the screen goes black while hard rebooting you have to release all the buttons and then press and hold the vol- button. The combination of vol- and the usb cable on boot seems to trigger fastboot mode.
I think the guide is in the guides forum, but the way it worked for me was without twrp:
- install magisk manager from this link -> https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
- push your boot.img (the easiest way is getting it from the factory image corresponding to the firmware you are using) to the sdcard
- open magisk manager -> install -> patch image only -> boot.img
- this will generate a patched_boot.img in /sdcard/MagiskManager
- copy that file to your pc
- go to fastboot and flash that patched image: fastboot flash boot patched_boot.img
- enjoy root, and you can use magisk hide for apps that don't like root
Regards
Click to expand...
Click to collapse
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?

Bloodeagle said:
Progress! Got it into download mode. I have the boot.img I got from razer, should I push that and see if it boots normally?
Click to expand...
Click to collapse
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition

waiflih said:
As you already wiped the data partition, you should use the flash_all script. But yes, you can try flashing each partition
Click to expand...
Click to collapse
I moved the flash_all script into the tools folder and after a little while, the phone booted up into setup! After a couple taps, I've realized the wifi isn't working, which I know is a known issue. I'm gonna let it sit for the night and finish it in the morning!
EDIT : Soooo, I know I said I was going to bed, but I decided to fix the wifi issue, which in turn, also rooted my phone. I've downloaded the root checker, and it confirms it! Thanks so much Waiflih! You rock!

Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.

saberhashemi said:
Hi guys, it seems I'm having the same problem and basically after unlocking my bootloader and flashing twrp to both of my slots I'm stuck on "Your device has been unlocked and can't be trusted" booting up infinitely.
The USB plug in and holding the volume - button doesn't bring up "download mode" and no matter what buttons I try and press on my phone my computer doesn't recognize ANYTHING connected to it anymore.
Bloodeagle, how did you manage to get "download mode" back onto your phone? it seems like mine refuses to do anything like download mode.
Click to expand...
Click to collapse
Have you tried holding few combinations of different butt9ns for a minute or two to see if that results in you getting in downl9ad mode?

Bsod after twrp update ?

I tried to update twrp (i flashed zip file from twrp ) and now i'm stuck at boot logo, no recovery mode, download mode (odin doesn't see my phone) but my pc see it with internal storage. Any suggestion ?

see my video for more information. Thanks.

lobisfondati said:
I tried to update twrp (i flashed zip file from twrp ) and now i'm stuck at boot logo, no recovery mode, download mode (odin doesn't see my phone) but my pc see it with internal storage. Any suggestion ?
Click to expand...
Click to collapse
Push volume up + down simultaneously while connecting the USB cable from the pc to the phone. That will put the phone in download mode.

Hi, i solved the problem with this instructions:
On windows i opened command prompt
2) adb devices
3)adb reboot system
And the my phone working again.
Thank you all the same.