My device is OnePlus 8 IN2010, but currently I'm on OOS13-F15 IN2015. Everything was working fine without any issues. Last Sunday, I found link to a full ROM F15 of EU variant, then I extract the ops file into fastboot images and flash to the device. The flashing was successfully without any error msg. But then, wen reboot, the device won't turn on again till now. I tried many way but its even not recognized by Computer, no port, no EDL nothing at all.
So I really need if anyone used to face this situation pls share the information on why is it so and is there any solution for the current state of the device.
Thanks in advance, guys!
LinhBT said:
My device is OnePlus 8 IN2010, but currently I'm on OOS13-F15 IN2015. Everything was working fine without any issues. Last Sunday, I found link to a full ROM F15 of EU variant, then I extract the ops file into fastboot images and flash to the device. The flashing was successfully without any error msg. But then, wen reboot, the device won't turn on again till now. I tried many way but its even not recognized by Computer, no port, no EDL nothing at all.
So I really need if anyone used to face this situation pls share the information on why is it so and is there any solution for the current state of the device.
Thanks in advance, guys!
Click to expand...
Click to collapse
It takes several tries while using different ports and cables.
Spoiler
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to Windows while still holding the buttons. Done. MSM tool will detect your phone.
rodken said:
It takes several tries while using different ports and cables.
Spoiler
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to Windows while still holding the buttons. Done. MSM tool will detect your phone.
Click to expand...
Click to collapse
I did bro, tried not only few times but whole night ))) Besides, tricks like press and hold ( and keep holding ) 3 buttons and else I also did try. I even open the back cover, but not yet know where's the Testpoin
LinhBT said:
I did bro, tried not only few times but whole night ))) Besides, tricks like press and hold ( and keep holding ) 3 buttons and else I also did try. I even open the back cover, but not yet know where's the Testpoin
Click to expand...
Click to collapse
It seems that your device is a candidate for a replacement if you cannot enter EDL.
rodken said:
It seems that your device is a candidate for a replacement if you cannot enter EDL.
Click to expand...
Click to collapse
In fact I considered its ded already, too. Since I unbricked many kind of devices and when I see its state, I already guessed. But what I wanna know is the reason that make him dead bro
LinhBT said:
In fact I considered its ded already, too. Since I unbricked many kind of devices and when I see its state, I already guessed. But what I wanna know is the reason that make him dead bro
Click to expand...
Click to collapse
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
rodken said:
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
Click to expand...
Click to collapse
This I know, but it applies for 8T more than OP8 since op8 only have one LPDDR4 variant, and also in the ops extracted image, there was only 1 xbl and xbl_config image, none xbl5. Thats why I feel weird.
You're looks like Chinese and I'm pretty sure you're. Why not you just make a call to service center or bring to him and they'll fix it in minutes.
Even you can help us for remote season.
By the way op8 have way bh force goto edl
rodken said:
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
Click to expand...
Click to collapse
Besides, I manually flashed it using fastboot cmd-line, not using MSM. So strange!
LinhBT said:
Besides, I manually flashed it using fastboot cmd-line, not using MSM. So strange!
Click to expand...
Click to collapse
At this point and juncture, it wouldn't matter which method was used to flash the ops file. Something along the way set the voltage too high which possibly damaged the motherboard.
Daniha said:
You're looks like Chinese and I'm pretty sure you're. Why not you just make a call to service center or bring to him and they'll fix it in minutes.
Even you can help us for remote season.
By the way op8 have way bh force goto edl
Click to expand...
Click to collapse
1stly, I MAY look like Chinese since we both Asian, but as in my profile is clarify enough that I'm Vietnamese. Besides, it does not related to the issue that I'm raising.
rodken said:
At this point and juncture, it wouldn't matter which method was used to flash the ops file. Something along the way set the voltage too high which possibly damaged the motherboard.
Click to expand...
Click to collapse
Basically, its the only way for now to explain the situation, but to be honest, Im not so satisfy with it. Point is, I'm not trying to recover the device for myself since personally, I considered its ded ))). But also I want to help all the information which may related to the issue, from there I will have clues to find out what was the reasons that killed it, then share to the community to prevent the same issues since even that Im quite experienced with OP devices but this is the 1st time I face this so it may be the new issue which comes with OOS13 or else.
LinhBT said:
1stly, I MAY look like Chinese since we both Asian, but as in my profile is clarify enough that I'm Vietnamese. Besides, it does not related to the issue that I'm raising.
Click to expand...
Click to collapse
You stil missed My POV. You need to visit service Center the only option left in this case. I can also fix but device need in hand.
Here everyone Provide you file but what if you're Not able to access 9008
Or another option is ufs dump
LinhBT said:
Basically, its the only way for now to explain the situation, but to be honest, Im not so satisfy with it. Point is, I'm not trying to recover the device for myself since personally, I considered its ded ))). But also I want to help all the information which may related to the issue, from there I will have clues to find out what was the reasons that killed it, then share to the community to prevent the same issues since even that Im quite experienced with OP devices but this is the 1st time I face this so it may be the new issue which comes with OOS13 or else.
Click to expand...
Click to collapse
Keep me posted if you are able to pin-point the exact issue.
-- We can always learn from each other with a helping hand.
rodken said:
Keep me posted if you are able to pin-point the exact issue.
-- We can always learn from each other with a helping hand.
Click to expand...
Click to collapse
Sure man, just like before, based on the information I have from our forum, I was successfully restore a dead OP 8T TMO with Testpoint trick after few months after it bricked. That thread, I believe still somewhere at 8T Forum
Daniha said:
You stil missed My POV. You need to visit service Center the only option left in this case. I can also fix but device need in hand.
Here everyone Provide you file but what if you're Not able to access 9008
Or another option is ufs dump
Click to expand...
Click to collapse
Pls kindly re-check my reply at #12
Anyone? Anyone have any information pls!!!
LinhBT said:
Anyone? Anyone have any information pls!!!
Click to expand...
Click to collapse
The device is most likely dead if it cannot enter EDL mode. There have been reports of issues entering EDL mode when using a USB 3 port, so trying a USB 2 port might be another option.
Xryphon said:
The device is most likely dead if it cannot enter EDL mode. There have been reports of issues entering EDL mode when using a USB 3 port, so trying a USB 2 port might be another option.
Click to expand...
Click to collapse
Tks mate, but I already aware of the USB 3.0 issue hence I always use USB 2.0 . And as I mentioned, I already accepted the fact that its dead ( more than dead )) ) Just I want to figure out what was really happened that make it dead so that we can warn the others since I guess that this comes from the smt inside the Ofiicial Oneplus OTA package.
LinhBT said:
Tks mate, but I already aware of the USB 3.0 issue hence I always use USB 2.0 . And as I mentioned, I already accepted the fact that its dead ( more than dead )) ) Just I want to figure out what was really happened that make it dead so that we can warn the others since I guess that this comes from the smt inside the Ofiicial Oneplus OTA package.
Click to expand...
Click to collapse
There is an interesting write-up regarding your issue.
Not to mention that there is the possibility of corrupting the Param Partition that will cause EDL to not function under the MSM Tool with the old param mismatch.
Related
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
@PriPhaze is your device stock(bootloader locked) or modified in any way?
aaycce said:
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
Click to expand...
Click to collapse
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
strongst said:
@PriPhaze is your device stock(bootloader locked) or modified in any way?
Click to expand...
Click to collapse
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
PriPhaze said:
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
Click to expand...
Click to collapse
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
strongst said:
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
Click to expand...
Click to collapse
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
PriPhaze said:
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
Click to expand...
Click to collapse
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
strongst said:
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
Click to expand...
Click to collapse
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
PriPhaze said:
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
Click to expand...
Click to collapse
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
strongst said:
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
Click to expand...
Click to collapse
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
PriPhaze said:
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
Click to expand...
Click to collapse
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
strongst said:
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
Click to expand...
Click to collapse
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
PriPhaze said:
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
Click to expand...
Click to collapse
Yes, everything is on board. It's the worst case for, sadly...
Or you buy a device with broken screen and exchange the board /display. Depends how much you have to spent for this at all.
PriPhaze said:
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
Click to expand...
Click to collapse
Ah yes, the common misconception that power shuts it off. Nope, not this phone. You have to hold power and volume up together to power off the phone when it crashes. Make sure you're using the latest platform tools (adb/fasboot) to unlock your phone. Make sure oem unlocking is enabled in developer settings after you've unlocked, having it disabled for some reason does screwy things. Mine was disabled once when I downgraded to Android 9 using the all in one tool available on xda, I thought I bricked the phone because it wouldn't boot after a reboot. Flash the latest oos twice through the system local upgrade feature, this will put the current oos on all partitions. Use the correct twrp, the unified versions found on xda 3.3.1-75 and 3.3.1-76 work well for me. The installer zip for those can be used in magisk to flash twrp after an OTA update before reboot. So, local upgrade 100% -> magisk modules "+" twrp 3.3.1-75 unified installer zip -> reboot to recovery -> flash magisk 20.3 at least (20.4 is available now). Do this twice so that everything is the same version on all the partitions. Lastly restore apps with swift backup without data, I know it's not ideal but may be necessary because some app's data may be corrupt and causing this. Good luck. Of course at any time you have it running you can reboot in safe mode (touch and hold restart until the dialogue pops up) and see how long you can use it without any third party apps to confirm that it is an app you installed.
Man I had the exact same problem as you and I got it fixed this morning after nights of fastboot commands trial and error found this thread forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Tried a few times before it worked but saved my phone all I had was fastboot mode and no recovery make sure to manually flash all fastboot commands you will then get stock recovery back wipe using all 3 options go 1st 2nd 3rd and then 1st wipe again after reboot phone might hang just force reboot and fixed
I really appreciate all the replies really but hmm im guessing there's a misunderstanding on what im saying.
I do know how to flash and recover one plus devices using MSM tool if neccesary, also to flash the fastboot rom .
The thing here is that everytime i recover the phone and all seems stable and working good , after a2 days more less it will random freeze of death and you cant even reboot holding power button NOTHING! is completely freezed.
So yea, thats pretty much it, i have tried already all that you said so far :c.
Good morning all, I tried relocking my bootloader using the command "fastboot oem asus-csc lk" and at first, it seemed to be a success. However I restarted my device and was met with this error message. "Your device is corrupt. It can't be trusted and will not boot." I've tried searching high and low and it seems that I'm royally screwed, just wanted to confirm that I was though. Thanks for reading my post and any input is appreciated.
If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware
This is becoming a pretty common issue. I think it's time we make a WARNING thread.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com
jhosharath said:
If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware
Click to expand...
Click to collapse
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all
Jdotswift said:
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all
Click to expand...
Click to collapse
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
twistedumbrella said:
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment
Jdotswift said:
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment
Click to expand...
Click to collapse
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.
twistedumbrella said:
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.
Click to expand...
Click to collapse
Well thanks for your help. I admit defeat but learned a very valuable lesson
Jdotswift said:
Well thanks for your help. I admit defeat but learned a very valuable lesson
Click to expand...
Click to collapse
You may still want to contact Asus and tell them you don't know what happened. They may be able to restore it. I wouldn't tell them you unlocked the bootloader, since it's locked if they ask.
As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here
JazonX said:
As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here
Click to expand...
Click to collapse
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.
twistedumbrella said:
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.
Click to expand...
Click to collapse
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas
Jdotswift said:
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas
Click to expand...
Click to collapse
Glad to hear it. Apparently, the issue was people not following instructions...
Hi guys
Please help me to solve my problem. I tried several methods but unfortunately it was not solved. Does anyone have a suitable solution?
My Phone Rog phone 5 ww ver bootloader Locked
Jamshid66 said:
Hi guys
Please help me to solve my problem. I tried several methods but unfortunately it was not solved. Does anyone have a suitable solution?
My Phone Rog phone 5 ww ver bootloader Locked
Click to expand...
Click to collapse
What is the specific problem you are trying to fix?
twistedumbrella said:
What is the specific problem you are trying to fix?
Click to expand...
Click to collapse
My phone (Rog phone 5) turned off and didn’t turn on!!
After connecting to PC, it enters to EDL Mode and doesn’t exit from it!!
Help me that how can exit it from EDL Mode and use my phone again!?
Jamshid66 said:
My phone (Rog phone 5) turned off and didn’t turn on!!
After connecting to PC, it enters to EDL Mode and doesn’t exit from it!!
Help me that how can exit it from EDL Mode and use my phone again!?
Click to expand...
Click to collapse
What were you doing when it started? Did you unlock the bootloader? Was it rooted? Did you flash something?
twistedumbrella said:
What were you doing when it started? Did you unlock the bootloader? Was it rooted? Did you flash something?
Click to expand...
Click to collapse
It went to this state when the mobile phone was finished charging
Jamshid66 said:
It went to this state when the mobile phone was finished charging
Click to expand...
Click to collapse
It's a completely stock phone? You've never unlocked the bootloader or tried to flash anything?
If that's the case, you'd be far better off contacting Asus about it. It is well within the year warranty and you may require a special cable to flash it correctly yourself. It sounds like it may be defective, so even recovering it could only be temporary.
Contact Us | ASUS
twistedumbrella said:
It's a completely stock phone? You've never unlocked the bootloader or tried to flash anything?
If that's the case, you'd be far better off contacting Asus about it. It is well within the year warranty and you may require a special cable to flash it correctly yourself. It sounds like it may be defective, so even recovering it could only be temporary.
Contact Us | ASUS
Click to expand...
Click to collapse
I talked to the support department but did not answer
Is there a way I can do it?
I feel my bootloader is broken
Jamshid66 said:
I talked to the support department but did not answer
Is there a way I can do it?
I feel my bootloader is broken
Click to expand...
Click to collapse
Probably need a deep flash cable, I believe it's called
twistedumbrella said:
Probably need a deep flash cable, I believe it's called
Click to expand...
Click to collapse
It says they are updating the page. You probably won't hear back over the weekend and they take a couple days to reply normally. It is the safest way to restore the phone, though.
Making cables and using software that doesn't come directly from Asus for restoring from a brick is risky. It's a last resort when they say they won't help.
twistedumbrella said:
It says they are updating the page. You probably won't hear back over the weekend and they take a couple days to reply normally. It is the safest way to restore the phone, though.
Making cables and using software that doesn't come directly from Asus for restoring from a brick is risky. It's a last resort when they say they won't help.
Click to expand...
Click to collapse
If I want to do it myself, what do you suggest because I got the phone from another country, I do not think the warranty is included
Jamshid66 said:
If I want to do it myself, what do you suggest because I got the phone from another country, I do not think the warranty is included
Click to expand...
Click to collapse
I suggest looking at how they did it on the ROG Phone 3 and then seeing what, if any, of that has a matching ROG Phone 5 version. This phone is only a couple months old, so there isn't a whole lot of public research yet.
twistedumbrella said:
I suggest looking at how they did it on the ROG Phone 3 and then seeing what, if any, of that has a matching ROG Phone 5 version. This phone is only a couple months old, so there isn't a whole lot of public research yet.
Click to expand...
Click to collapse
Do you mean that I have to use files that referse to Rog phone 3 ?
Jamshid66 said:
Do you mean that I have to use files that referse to Rog phone 3 ?
Click to expand...
Click to collapse
No. That will break the phone much worse.
twistedumbrella said:
No. That will break the phone much worse.
Click to expand...
Click to collapse
So we have to wait for more files For ROG 5
Jamshid66 said:
So we have to wait for more files For ROG 5
Click to expand...
Click to collapse
I honestly don't know. Hopefully someone else will come along that can help.
twistedumbrella said:
I honestly don't know. Hopefully someone else will come along that can help.
Click to expand...
Click to collapse
what is your suggestion?
Jamshid66 said:
what is your suggestion?
Click to expand...
Click to collapse
Wait to hear back from Asus
twistedumbrella said:
Wait to hear back from Asus
Click to expand...
Click to collapse
I speak with a warranty, unfortunately my request was rejected
Jamshid66 said:
I speak with a warranty, unfortunately my request was rejected
Click to expand...
Click to collapse
If the device is under warranty and this happened without you altering anything I don't understand how they can reject it
If the device is only stuck in EDL mode but no hardware damage and has a working bootloader you can try (entirely at own risk):
1 - Make (or buy) a deep flash cable and see if you can snap it out of EDL mode by activating it a few times while the device is connected. (Chances are slim but it does work sometimes).
2 - Disconnect and re-connect the battery pack from the mainboard. The battery connector of ROG 5 is located on the right side between the north battery and the mainboard when looked from the back. You need to remove the top part of the motherboard for access to it. It's not a huge operation but requires some basic tools and some phone adhesive for closing the backcase again. Some cooling paste is also useful to repaste the heat conducting parts before closing it again (optional).
However, if the device doesn't have a working boot and/or it's really damaged then all above is useless.
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with
I am a very experienced ROM enthusiast and owned plenty of Xiaomi/Oneplus devices.. This is my first pixel device. I loved the phone, more than the other mentioned companies. My pixel 7 Pro was my prized possession.. I've came close a couple of times botching a ROM flash, even once with my p7p (installing evo with February firmware instead of Jan, phone would boot to bootloader for a total of 2 seconds before dying again, had to spam flash phone in pixel flasher app until it recognized and luckily it did) but this time, trying to go from latest feb build to jan before flashing evo, my ****ing cable did something in the middle of flashing the second partition (b partition) and was almost to system, the partition it flashes before booting.. it was flashing the product partition.. literally already flashed every other partition except partition and system on the b slot. A slot was fully flashed.. phone literally wont respond to plugging into computer, into charger, holding down every combination of buttons... doesn't matter. I'm stumped how flashing a factory rom could have gone this horribly.. especially so late into the flashing process..
Beware guys; Make sure the cable you're using to flash is stable!
attached in this post is the logs I have pulled from the pixel flasher app.. if someone could bounce some ideas off of me or somehow make this make sense to me, it would be gladly appreciated.
Holding down the down volume button when starting doesn't enter bootloader? If it does, use Google's online Android Flash tool to go back to stock.
Try a different cable.
Try a different USB port.
Try another computer as well.
If any of these prompt some response, I think there's hope. Also try booting into fastboot from bootloader as well as recovery.
Prob hard brick.
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Arealhooman said:
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Click to expand...
Click to collapse
A battery for my desktop PC?
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Google for "uninterruptible power supply" ...
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Yeah, no idea.
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
The real answer to this is why google and the android community as a whole is pushing away from having a supporting third party recovery menu (implementing new partitions like init_boot and vendor_boot for recovery, also no working twrp). Why do you think Evolution ROM pushes so hard to be different and when flashing their newest build you do it not through the usual scary tedious bootloader way (THE SAME WAY WE ARE SUPPOSED TO FLASH OUR FACTORY ROMS) to making their own recovery, which obviously means only flashing one partition, and adb sideloading the rom. its like google wants you to break your phone and they are making it more convenient for third party roms to package theirs the same way. i should have never left evo.. haha.
Oh, and sorry for the late reply. I thought I would leave my phone alone for a little to see if it would help; I'm accident prone and lose things constantly, and what do ya know I just lost my phone that I can't even call to find lmao. Ill keep updated on everyones opinions on what i should try whenever i find it
krakout said:
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
Click to expand...
Click to collapse
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
EtherealRemnant said:
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
Click to expand...
Click to collapse
Ah I see, makes sense.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Oh brother, how often does that actually even happen?
HipKat said:
Oh brother, how often does that actually even happen?
Click to expand...
Click to collapse
Sure, not really often. But when it does..
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
zacattackkc said:
trying to go from latest feb build to jan before flashing....
Click to expand...
Click to collapse
It sounds like you may have tripped some anti-downgrade code.
EDIT: I can confirm that the bootloader version was changed in the FEB image as compared to the JAN image.
96carboard said:
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
Click to expand...
Click to collapse
Well, I use Samsung, so I am assuming fastboot is similar…