Database Info

[Q] Trying to Root.

I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!

Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?

arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.

sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?

arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?

sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.

arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.

I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.

sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).

arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.

sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.

Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS

unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance

1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.

Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.

Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx

D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.

arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?

D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.

arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me

[Q] TF700 bricked...?

Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!

Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??

lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo

nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??

lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?

nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/

lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!

Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app

lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays

So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?

First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.

berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery

Hope this worked

s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???

berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?

s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.

OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.

s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?

The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it

s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?

Help softbricked or hardbricked device?

Help softbricked device
well i was running more rom on the device when i droped it then i got the screen and digi replaced
and when the tech tuned it on for the first time after repair we got a udc start screen that says unknown error at the top
i can get to download mode though. but even after trying to restore the bootloader or flash a new modem i cant get to any recovery.
right now this is what it says in download mode.
odin mode
product name : SM-G900P
current binary: custom
system status : custom
knox warranty void 0x1 (4)
i can go to download mode or try and let it boot up to the samsung boot but it says recovery booting in blue and loops there on reboot.
i forget the name of the modem i was on in more rom. i think it was the one be4 ota6
but i want to update to latest version of modem and rom not sure where to start.
i cant seem to get back to stock or custom recovery at all. or even boot up to a rom now. and i honestly have no idea why? =( can someone help?

jackrabbit72380 said:
Help softbricked device
well i was running more rom on the device when i droped it then i got the screen and digi replaced
and when the tech tuned it on for the first time after repair we got a udc start screen that says unknown error at the top
i can get to download mode though. but even after trying to restore the bootloader or flash a new modem i cant get to any recovery.
right now this is what it says in download mode.
odin mode
product name : SM-G900P
current binary: custom
system status : custom
knox warranty void 0x1 (4)
i can go to download mode or try and let it boot up to the samsung boot but it says recovery booting in blue and loops there on reboot.
i forget the name of the modem i was on in more rom. i think it was the one be4 ota6
but i want to update to latest version of modem and rom not sure where to start.
i cant seem to get back to stock or custom recovery at all. or even boot up to a rom now. and i honestly have no idea why? =( can someone help?
Click to expand...
Click to collapse
Follow the instructions from this post. Since you are soft bricked at the moment, you'll need to start at step 4. If you have an extSD in your phone, you might want to pull it until after you're up and running because the "Android" folder from Kitkat needs to be deleted and rebuilt for Lollipop.

That's what I tryed first but it didn't work,
First step.... flash SM-G900P_OA6_FullRestore.
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
sense that didn't work i tryed... SM-G900P_NI3-Full_Restore_Unrooted (Compressed Archive)
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
then i tryed SM-G900P_OA6_FullRestore. again but still no luck im out of ideas
I cant get to any recovery.
please help.

jackrabbit72380 said:
That's what I tryed first but it didn't work,
First step.... flash SM-G900P_OA6_FullRestore.
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
sense that didn't work i tryed... SM-G900P_NI3-Full_Restore_Unrooted (Compressed Archive)
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
then i tryed SM-G900P_OA6_FullRestore. again but still no luck im out of ideas
I cant get to any recovery.
please help.
Click to expand...
Click to collapse
Are you using the wrong terminology? You have to use Odin and a PC to install the .tar. Also, the first boot into Lollipop can take about 20 minutes. You have to be patient. I see you posting in different threads and you seem to be digging deeper into a hole.
Are you using Odin and starting by downloading (to PC) the file in step #4? Then follow the remaining steps "exactly". Re-read those instructions and if you not already downloaded the needed files, do that first.

Ramer said:
Are you using the wrong terminology? You have to use Odin and a PC to install the .tar. Also, the first boot into Lollipop can take about 20 minutes. You have to be patient. I see you posting in different threads and you seem to be digging deeper into a hole.
Are you using Odin and starting by downloading (to PC) the file in step #4? Then follow the remaining steps "exactly". Re-read those instructions and if you not already downloaded the needed files, do that first.
Click to expand...
Click to collapse
Yes I downloaded the files to the pc.
Im using odin3.07
in pda I add the file Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel),
put phone in download mode.
flash file!
ODIN SAYS PASS
next phone reboots to samsung galaxy black screen with with blue letters at the top saying
RECOVERY BOOTING......
then boot loops there.
I CANT GET TO STEP 5
I am not able to boot to the rom or recovery

jackrabbit72380 said:
Yes I downloaded the files to the pc.
Im using odin3.07
in pda I add the file Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel),
put phone in download mode.
flash file!
ODIN SAYS PASS
next phone reboots to samsung galaxy black screen with with blue letters at the top saying
RECOVERY BOOTING......
then boot loops there.
I CANT GET TO STEP 5
I am not able to boot to the rom or recovery
Click to expand...
Click to collapse
Try this: Do a battery pull, then put the phone in Download mode, hook up to PC and then open Odin and then Odin custom recovery, either twrp or Philz. Uncheck auto reboot in odin and once it passes, pull the battery, unplug and boot into recovery. Also, you might update Odin, there's a link to Odin 3.10.0 in my post. Let's see if we can get that far and go from there.

ramer said:
try this: Do a battery pull, then put the phone in download mode, hook up to pc and then open odin and odin custom recovery, either twrp or philz. Uncheck auto reboot in odin and once it passes, pull the battery, unplug and boot into recovery. Also, you might update odin, there's a link to odin 3.10.0 in my post. Let's see if we can get that far and go from there.
Click to expand...
Click to collapse
ok used odin 10
tryied everything you said exactly phone reboots on samsung galaxy s5 boot logo everytime. Whether i try booting to recovery or the rom.

jackrabbit72380 said:
ok used odin 10
tryied everything you said exactly phone reboots on samsung galaxy s5 boot logo everytime. Whether i try booting to recovery or the rom.
Click to expand...
Click to collapse
Which recovery tar did you Odin? You pulled the battery after Odin said PASS, then unplugged the phone, put battery back in and immediately tried to get into recovery? If so, I'm stumped.

Ramer said:
Which recovery tar did you Odin? You pulled the battery after Odin said PASS, then unplugged the phone, put battery back in and immediately tried to get into recovery? If so, I'm stumped.
Click to expand...
Click to collapse
Yes I tryed
I pulled the battery after Odin said PASS
Yes I tryed
kt_twrp_recovery_boa6_firmware.tar
and
openrecovery-twrp-2.8.4.0-klte
and
philz_touch_6.57.8-klte
NOTHING!
when ever i try and boot the rom the phone vibrates 2 times and resets.
when ever i try to boot to recovery
i get
recovery booting....
recovery is not seandroid enforcing
set warranty bit : recovery
then phone reboots.
then it trys to boot the rom.
and vibrates 2 times and resets.
Im not new to using odin or flashing roms or recoverys i sort of know what im doing. not to sound cocky.
Im Stumped to!

jackrabbit72380 said:
Yes I tryed
kt_twrp_recovery_boa6_firmware.tar
and
openrecovery-twrp-2.8.4.0-klte
and
philz_touch_6.57.8-klte
NOTHING!
Im not new to using odin or flashing roms or recoverys i sort of know what im doing. not to sound cocky.
Im Stumped to!
Click to expand...
Click to collapse
I saw your post count, I knew you knew what you're doing, just wanted to double check everything. Sorry, I'm out of ideas. I did ask @tdunham to take a look at this thread, if he has some other ideas, but he's offline right now. Hopefully he'll check in later.

What about flashing back to an older version of android? Full tar flash.
---------- Post added at 12:38 AM ---------- Previous post was at 12:36 AM ----------
Like ne5, and nothing else, just see if you can get stock to boot, no messing around trying to flash recovery.

This is RWillco12's NE5 stock.. Have the phone in download mode and run the .exe
Thanks TD.

Ramer said:
This is RWillco12's NE5 stock.. Have the phone in download mode and run the .exe
Thanks TD.
Click to expand...
Click to collapse
I tryied ni3 already
but as far as i know you cant downgrade the bootloader.
if i could flash just the bootloader for ota6 maybe that would help.
i will try downloading ne5 now but my last rom was running a nkd modem.
im going to try and flash G900P_NKD_FullRestore.tar in odin if that dont work ill try ne5
and will report back shortly.
well nkd full restore boots up to
unknowen error!
wait..
done!
udc start.
power reset or
unknown
upload mode.
this is the way i got it back from retech after they replaced my bezel and digitlizer and screen
i never had an issue with anything software wize before that.

Have you tried flashing the phone without any sim cards inserted including the sprint card? You are flashing from a powered off state right? You know it wont work unless phone is powered off before going into download mode.
As a last resort attached is the pit file for the 16gb G900P. Unzip and put it into the pit section of odin and flash the stock firmware again. It will repartition the entire phone when it flashes the stock image.

tdunham said:
Have you tried flashing the phone without any sim cards inserted including the sprint card? You are flashing from a powered off state right? You know it wont work unless phone is powered off before going into download mode.
As a last resort attached is the pit file for the 16gb G900P. Unzip and put it into the pit section of odin and flash the stock firmware again. It will repartition the entire phone when it flashes the stock image.
Click to expand...
Click to collapse
Yes I was using the pit file and yes I know to go to download mode from power off state. and no sim card is in the phone.
flashing ne5 stock with fingers crossed.
brb
nope
is there any bootloaders only i can flash?
well tryed everything all it does is vibrate 2 times. same as be4 im dead in the water. i don't know what's wrong or what to do.
I have tryed everything i can think of.
I can boot to download mode and flash anything i want but nothing works.
no recovery. no rom.

Power & vol down no longer loads bootloader after flashing

Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help

Fireflynj said:
Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help
Click to expand...
Click to collapse
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372

andybones said:
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372
Click to expand...
Click to collapse
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.

Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
Download the .exe and click open. Follow directions on the screen. It doesn't get easier, trust me you'll be fine. Wouldn't steer you wrong.

Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk

dottat said:
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:

Fireflynj said:
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:
Click to expand...
Click to collapse
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.

dottat said:
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.
Click to expand...
Click to collapse
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.

Fireflynj said:
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.
Click to expand...
Click to collapse
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk

dottat said:
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yup , that was it, the older one worked.
So dumped the idea of getting KitKat back and I flashed the Marshmallow custom s-off RUU with TWRP that you provided. so far good now I just need to re-root it.
Thank you

Bootloop in my S8 Plus, where to download Stock Firmware?

Hi,
I have S8 Plus SM-G955F in Germany.
Dont knwo what exactly happend, but my phone was just still running fine (bootloader is unlocked) and I rebooted but then was stuck at "Installing system updates" screen which appear before getting into recovery. However, it does not enter into recovery and reboots after few seconds into "installing updates" mode which then fails.
It does not boot up into Android.
All I can access to is Download Mode.
I flashed "BL_G955FXXU1AQF7_CL11544126_QB13847503_REV00_user_low_ship.tar" Bootloader and rebooted and now it is stuck in Samsung boot logo. If I press Vol up + Bixpy Button + Power nothing happends, it does not even start to load Recovery mode.
I now downloaded following stock firmware through SamFirm: "SM-G955F_1_20171214140840_hlcm4r582t_fac.zip.enc4" (3332 MB)
but when trying to flash it in odin I get FAILED !!! Also if I try to flash TWRP recovery "twrp-3.1.0-1-dream2lte.img" I get FAILED in Odin I now also tried to flash "AP_G955FXXU1AQH3_CL12050265_QB14545623_REV00" firmware using this tutorial: https://www.youtube.com/watch?v=2y0ZZxcNVnE which also FAILED. I think I am completely bricked !!
Please help, phone is completeley useless now
Thanks!

tobyffm said:
SM-G955F_1_20171214140840_hlcm4r582t_fac.zip.enc4" (3332 MB)
Click to expand...
Click to collapse
I had the same problem with downloading stock firmware. My problem was that I couldn't download from SamMobile because of server maintenance. So I downloaded from here. An with this tool there's the option to decrypt the file automatically. I forgot to tick this option and had a .enc4-file like you have there. The problem could decrypt this file and then I could unzip it and use it with odin.
So that's your problem: you are trying to use an encrypted file. But you have to use an decrypted file.

Maltonator said:
I had the same problem with downloading stock firmware. My problem was that I couldn't download from SamMobile because of server maintenance. So I downloaded from here. An with this tool there's the option to decrypt the file automatically. I forgot to tick this option and had a .enc4-file like you have there. The problem could decrypt this file and then I could unzip it and use it with odin.
So that's your problem: you are trying to use an encrypted file. But you have to use an decrypted file.
Click to expand...
Click to collapse
Hi,
thank you! But its actually not my problem. Samfirm decrypted and I got the zip with the BL, AP, CSC, CP files in it. But ODIN fails everytime anyway and I have no idea what I could still do now.

tobyffm said:
Hi,
thank you! But its actually not my problem. Samfirm decrypted and I got the zip with the BL, AP, CSC, CP files in it. But ODIN fails everytime anyway and I have no idea what I could still do now.
Click to expand...
Click to collapse
But you flashed all four files at the same run together?

Maltonator said:
But you flashed all four files at the same run together?
Click to expand...
Click to collapse
Yes, like the howto video described.

tobyffm said:
Dont knwo what exactly happend, but my phone was just still running fine (bootloader is unlocked) and I rebooted but then was stuck at "Installing system updates" screen which appear before getting into recovery.
Click to expand...
Click to collapse
But this happens with my phone to if I press volume up.
tobyffm said:
If I press Vol up + Bixpy Button + Power nothing happends, it does not even start to load Recovery mode.
Click to expand...
Click to collapse
But you have to press Vol down

Maltonator said:
But this happens with my phone to if I press volume up.
But you have to press Vol down
Click to expand...
Click to collapse
Usual behaviour was this: Vol up, bixpy and Power -> Recovery mode which fist starts with "Installing update..." then failed and then it goes into some black recovery mode where you can choose Apply update.zip etc. right? However, in my case this black screen with more commands did not show up, before it was rebooting again by itself.
Now I cannot even get into this "installing updates" mode before recovery, because "Vol up, bixpy and Power" does not bring any action.
Vol down, Bixpy and Power still works and brings me to Download Mode. But it doesnt help me, because once I tr to flash any firmware in Download Mode, it FAILS in Odin, so I am completely stuck, hope you understand

tobyffm said:
Usual behaviour was this: Vol up, bixpy and Power -> Recovery mode which fist starts with "Installing update..." then failed and then it goes into some black recovery mode where you can choose Apply update.zip etc. right? However, in my case this black screen with more commands did not show up, before it was rebooting again by itself.
Now I cannot even get into this "installing updates" mode before recovery, because "Vol up, bixpy and Power" does not bring any action.
Click to expand...
Click to collapse
But why do you boot in recovery mode?
tobyffm said:
Vol down, Bixpy and Power still works and brings me to Download Mode. But it doesnt help me, because once I tr to flash any firmware in Download Mode, it FAILS in Odin, so I am completely stuck, hope you understand
Click to expand...
Click to collapse
Download mode is the only mode you need for restoring stock firmware.
Try this guide. (Spoiler "Flashing Standard Firmware:")
Yesterday I did it with this one too and it worked flawlessly. But I used Odin v3.12.3 not as said in the guide V3.12.7.

Maltonator said:
But why do you boot in recovery mode?
Download mode is the only mode you need for restoring stock firmware.
Try this guide. (Spoiler "Flashing Standard Firmware:")
Yesterday I did it with this one too and it worked flawlessly. But I used Odin v3.12.3 not as said in the guide V3.12.7.
Click to expand...
Click to collapse
it automatically loaded into recovery before, I was not able to boot into Android, it loaded recovery (but without black screen with more commands) automatically by default and rebooted, loaded recovery again and rebooted, loaded recovery againd and rebooted etc...all I could to to interrupt this was loading download mode.
However, thanks for the link, but it does describe what I did already. And yes, I also used Odin 3.12.3 already because in the video tutorial I linked some posts before they said also, I need to use that version.
However, it simply does not work. Odin FAILS everytime
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.

tobyffm said:
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
Click to expand...
Click to collapse
Yes that's the only thing that comes on my mind too if you think everything else is right. Download another firmware file maybe from a different provider than SamMobile.
Or try using different USB-Port, USB-Cable and/or different PC.

Maltonator said:
Yes that's the only thing that comes on my mind too if you think everything else is right. Download another firmware file maybe from a different provider than SamMobile.
Or try using different USB-Port, USB-Cable and/or different PC.
Click to expand...
Click to collapse
Did already, did not help. I think maybe there is something realldy bricked, so flashing stock firmware wont be possible at all anymore?! Is this possible somehow?
btw: Just managed to load into TWRP, randomly it does load twrp, dont know how, because if I press the keys for loading into recovery, it actually does not do anything, but currently I see twrp.
Is see anything I can try from there? btw: formated data (incl. internal storage) earlier already, but it did not change anything.
But any idea what I can try to flash from TWRP maybe? Is there a way to flash stock firmware from TWRP somehow?
I found a backup in twrp, I am currently trying to restore it...

tobyffm said:
But any idea what I can try to flash from TWRP maybe? Is there a way to flash stock firmware from TWRP somehow?
I found a backup in twrp, I am currently trying to restore it...
Click to expand...
Click to collapse
Google found this. But I don't know if this works. I only flashed custom ROMs via TWRP. Stock ROMs always via Odin.

Maltonator said:
Google found this. But I don't know if this works. I only flashed custom ROMs via TWRP. Stock ROMs always via Odin.
Click to expand...
Click to collapse
Puuuuh, I was able to fix phone with hat TWRP backup I found!
Thanks for your efforts anyway, much appreciated!

tobyffm said:
Puuuuh, I was able to fix phone with hat TWRP backup I found!
Thanks for your efforts anyway, much appreciated!
Click to expand...
Click to collapse
Glad it worked! :good:

tobyffm said:
it automatically loaded into recovery before, I was not able to boot into Android, it loaded recovery (but without black screen with more commands) automatically by default and rebooted, loaded recovery again and rebooted, loaded recovery againd and rebooted etc...all I could to to interrupt this was loading download mode.
However, thanks for the link, but it does describe what I did already. And yes, I also used Odin 3.12.3 already because in the video tutorial I linked some posts before they said also, I need to use that version.
However, it simply does not work. Odin FAILS everytime
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
Click to expand...
Click to collapse
My mistake, sorry - I posted in the wrong place- sorry. (I do hope you find a way to get t his fixed) good luck

I just ran into this thread: https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
It looks like you're not the only one...

You know, you might want to try and remove the more current apps you installed and see if that is causing the loop, and if that does not work, just dirty flash over what you have. For me, a lot of time a dirty flash will solve the issue, as it overwrites the OEM software, and in that manner, takes my phone OS back to normal/new state, while leaving my data.