This looks like a pretty hard nut to crack. I don't know exactly what caused it. I was rooted for a few days and was just reflashing Magisk (messing about you could say) when it turned up. Previously, I just had the warning with yellow text which is what everyone gets after unlocking the bootloader. So here goes the overview, please bear with me:
===> I reset the phone by flashing OnePlus5TOxygen_43_OTA_006_all_1712062242_69a5125fb2eb4d87.ZIP (OxgengenOS 4.7.4). <===
Exact steps on how I did that:
1) I flashed the stock recovery image via fastboot ( I got it from Oneplus's website)
2) I booted into the stock recovery I flashed in step 1 and flashed the entire ZIP (the one with the long name above). Probably flashed the recovery twice but yeah.
But no dice. It will absolutely not go away. The zip does not contain any other IMG's apart from boot.img and recovery.img so I can't really flash other partitions like system via fastboot. I CAN flash system via my nandroid backup, and I did, but that still did not help.
Here is the error I got. It's from a google search but it resembles the error on the OPO5T very nicely. So can the experts chime in please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not used to posting my own answer but maybe this will help someone. You need a full reflash with the Qualcomm tools. OPO support can do this, or anyone with the flashing tool, the correct firmware image, and drivers (the latter being easy to find).
There are tutorials online to do this, the only thing missing is the correct firmware image.
To summarise the requirements:
1) Qualcomm drivers (easy to find)
2) Qualcomm Flash tool MsmDownloadTool V4.0.exe (fairly easy to find)
3) The correct *.ops firmware image (hard to find and you need the password)
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Bradl79 said:
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Click to expand...
Click to collapse
I can tell you its lenght if that helps? That should narrow down the amount of combinations. Unless its different per download link they send.
Yes please that would cut down a lot
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
If we already have the opt file someone could just set up a keylogger on their machine and have op support do the remote flash and thus capture the password from them lol
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
Jeroen1000 said:
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
Click to expand...
Click to collapse
Has any one had any luck with the password? I'm in the same soup as well!
randallstevens said:
Has any one had any luck with the password? I'm in the same soup as well!
Click to expand...
Click to collapse
still going... only on 4th character out of 10 been running for a couple days
Bradl79 said:
still going... only on 4th character out of 10 been running for a couple days
Click to expand...
Click to collapse
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
randallstevens said:
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
Click to expand...
Click to collapse
It is Bruteforcing meaning I started with 10 characters
1111111111
And it's still trying to decrypt, I am at something aroun
111111gw7&
So it's going one by one going through each character
Related
Hi i folling this guide http://forum.xda-developers.com/showthread.php?t=2634196
I got problem att step #3 "Flash SO-02F_14.1.H.1.281_docomo.ftf (WIPE: select all, EXCLUDE: select none)"
SO-02F_14.1.H.1.281_docomo.ftf IS located in flashtool/firmware folder
Flashtoool is open , i click ón flash but the file does not show up as on option to use.
Verison 14.3.A.0.681
Kernel 3.4.0-perk-g8c33725
What is it im doing wrong?
Or am i supposed to use flashmode at step 3?
i see to have problem starting that too for some reason, i start phone while pusing volume down, but it starts normaly, No flahsing Led etc.'
'
Anyone care to post a dummie guide fo fix root? All i really want is to increase volume with headphones
fuzz321 said:
Anyone care to post a dummie guide fo fix root?
Click to expand...
Click to collapse
If you struggle with the existing guides, give up now.
XperienceD said:
If you struggle with the existing guides, give up now.
Click to expand...
Click to collapse
Wouldt say i struggle, But buttom line is i cant get 'SO-02F_14.1.H.1.281_docomo.ftf' to show up in flashtool, im trying and it feels ridiciouls its not like im sitting at a computer for the first time, but there someting im missing.
Im new to android, never had problem like this unlocking other OS in the past.
fuzz321 said:
Im new to android, never had problem like this unlocking other OS in the past.
Click to expand...
Click to collapse
Welcome to Sony. Reboot your comp and if it still doesn't show up then god knows.
Have you got latest version of flashtool installed?
Not near my pc, but am sure theres the option to browse for the ftf file in flashtool? Just make sure source folder is pointed to the firmware folder your ftf is in and flash.
Sent from my D5503 using xda app-developers app
Restarted alread, yes should be latest version. Heres a screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fuzz321 said:
Restarted alread, yes should be latest version. Heres a screen
Click to expand...
Click to collapse
have you checked for rom hashes ?
see http://forum.xda-developers.com/showthread.php?t=2642081, it is in question section
"Flashtool does not recognize the firmwares, even though I put it into the correct folder?"
autobanned said:
have you checked for rom hashes ?
see http://forum.xda-developers.com/showthread.php?t=2642081, it is in question section
"Flashtool does not recognize the firmwares, even though I put it into the correct folder?"
Click to expand...
Click to collapse
How do i check it? If its wrong, what do i do? Find another mirror? :S
fuzz321 said:
How do i check it? If its wrong, what do i do? Find another mirror? :S
Click to expand...
Click to collapse
http://lmgtfy.com/?q=check+file+for+hash
If the hash is wrong, you simply redownload the file.
As the title says, I installed the ASUS Official Unlock tool (and didn't really read it, as you should) and it attempted a boot unlock without SU. The funny thing is, it did exactly what it said it would do and rebooted into the Bootloader. The Bootloader said (and still does) it was a success and that the phone will reboot in 5 seconds. Which is fine, except it's doing that every single time I enter the Bootloader. I can't get it to stop doing that so I can actually do the root and re-do the unlock. The phone still functions perfectly fine otherwise.. any advice? (Yes, I can get it into recovery mode) Hopefully that didn't ban me from OTA.
EDIT: It also turned my boot screen white, and I also tried to use the sideloader, but I already have the latest ASUS firmware so that didn't help. However, in my loader I noticed some weird stuff showing about a MOD_SDUPDATE.ZIP not being found.. I don't know what's that about. It was doing that before I tried to use the sideloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dunno what exactly happened, but you can do " Using Stock.zip from ASUS site:" from here, that should fix basically everything: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
P.S.: your data won't be lost, however your app ache will be cleared, meaning you'll be logged out everywhere. So if you have some game and no account, that game state will be lost.
So I tried that, first with the ROM that's installed on the phone the .97 version. Then with the original version. It appears to actually install the .97 version, but that does absolutely nothing for the phone and if I try an older version it just tells me it can't flash an older version. Should flashing the same version over-top have taken care of the problem? Doesn't look like it did anything. The boot loader is probably unlocked, but I can't keep it in ADB mode long enough to do anything useful and you can't sideload a recovery to my knowledge.
EDIT: I named the file wrong in my tiredness. I did it again and loaded in recovery...
EDIT2: That did not work.
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
ultramag69 said:
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
Click to expand...
Click to collapse
I don't actually know what you mean by that? With the ASUS unlocking tool causing it to reboot in the bootloader improperly or the booting of the file from Recovery?
The phone isn't actually "broken" but now... I can't do anything to it without the use of ADB.. Which blows.
EDIT: Also, can you point me to these threads?
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
m3t4lw01f said:
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
Click to expand...
Click to collapse
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
bewaffled1 said:
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
Click to expand...
Click to collapse
Yep. We're hoping @ASUS_Khang gets a solution from HQ next week to get us back on track!
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
WhiteReign said:
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
Click to expand...
Click to collapse
i just use the factory images
https://developers.google.com/android/ota
Here's the OTAs. I've circled the right one. Maybe you were downloading the UK one?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 2 XL using Tapatalk
I can only get the DEC 5 To work. When I do it wont let me up grade to the newer version. kinda stuck here.
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
sharkie405 said:
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
WhiteReign said:
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
Click to expand...
Click to collapse
There are multiple step-by-step guides here on how to do just this. Suggest you take a step back and read one or two. There are two separate unlock commands to use and from your photo you did not complete that. Secondly, it looks like you may be using an outdated version of the adb/fastboot binaries. Lastly you don't flash an OTA with flash-all. If you are attempting to sideload an OTA, you use the "adb sideload" command with the phone in Recovery, not flash-all in fastboot mode. At this point, you should probably update your adb/fastboot binaries, download the full factory image (not OTA) and flash it instead. Slow down and read more.
Damn Sir! Thank you very much for the help!
WhiteReign said:
Damn Sir! Thank you very much for the help!
Click to expand...
Click to collapse
Not blaming anyone but instead just using your post for calling out there are what seems like dozens of variations for doing the same few tasks on this device. There are a couple really good tutorials that are either 100% or were until something like TWRP of magisk changed something. At the end of the day there are a few givens that will eventually shake out into something like the Heisenberg thread over on the 6P device.
For anyone reading this, unlock critical if you have not, install a custom kernel if you have touch issues in TWRP, really really really read up on the few custom roms that just hit as they add a few variables that most of us have never experienced, make a list of things you install as you do it. All too often people spend countless time and effort helping someone with a boot loop only to find out something not mentioned was in play. Poor steps were attempted from some other thread only to not help or made it worse or different. Examples of this would be xposed, custom kernel, any zip file mods you flashed, viper, Dolby, substratum, you get the idea. We all wanna help and we all need help at some point. Let us try to make the game as easy to play as possible. Flash on brothers and sisters!!
Hello there community,
Im here to ask for your amazing support cause am stuck on the very last step of SP Flash, i've done everything as recommended on different guides but all of 'em guide me to this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance,
---------------- UPDATE -------------------------
Now am getting this other message, been lookin' in other threads but no answer... i've been trying to fix my phone for 6 hours straight now... i really do need help
Taltor said:
Hello there community,
Im here to ask for your amazing support cause am stuck on the very last step of SP Flash, i've done everything as recommended on different guides but all of 'em guide me to this error:
View attachment 5413501
Thanks in advance,
Click to expand...
Click to collapse
Try this:
Compass.
Compass Linux said:
Try this:
Compass.
Click to expand...
Click to collapse
Followed this guide, everything just exacly and it didnt work idk tf why or if am doing something wrong to get the same error every single time "STATUS_EXT_RAM_EXCEPTION".
Taltor said:
Followed this guide, everything just exacly and it didnt work idk tf why or if am doing something wrong to get the same error every single time "STATUS_EXT_RAM_EXCEPTION".
Click to expand...
Click to collapse
https://telegra.ph/Installing-Redmi-Note-8-Pro-firmware-via-SP-Flash-Tool-01-21
This is another guide which has YouTube videos too.
Compass.
Compass Linux said:
https://telegra.ph/Installing-Redmi-Note-8-Pro-firmware-via-SP-Flash-Tool-01-21
This is another guide which has YouTube videos too.
Compass.
Click to expand...
Click to collapse
Thanks a lot for your follow on my problem but thats the very first guide i tried and didnt work, then i moved to the previous one u showd me and also saw another one from "Vikram something" channel and am always getting the same error at the last step when trying to flash it on flashtool.
Taltor said:
Thanks a lot for your follow on my problem but thats the very first guide i tried and didnt work, then i moved to the previous one u showd me and also saw another one from "Vikram something" channel and am always getting the same error at the last step when trying to flash it on flashtool.
Click to expand...
Click to collapse
https://telegra.ph/UNBRICK-BEGONIA-NO-AUTH-01-23
Yet another unbrick guide.
I think you should try using another PC.
Compass.
Taltor said:
---------------- UPDATE -------------------------
Now am getting this other message, been lookin' in other threads but no answer... i've been trying to fix my phone for 6 hours straight now... i really do need help
View attachment 5413521
Click to expand...
Click to collapse
Join Telegram group and some can teach you. Try open both new bypass and sp flash tools. After finish bypass, quickly press Download button. If still error, try press Power+Volume Up for 10s, then connect to cable, after finish bypass, quickly release button and press Download.
When I click on all the erase options, the client only recognizes them but cannot save me back to the phone. The volume and power buttons are not responding. Please help me!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you were backed up(read partition) every partition using mtkclient, than you just can recover your device through backup.
I had done recovering my device this way
Maybe there are other ways, but i have not tested them.
MrMiyamo said:
If you were backed up(read partition) every partition using mtkclient, than you just can recover your device through backup.
I had done recovering my device this way
Maybe there are other ways, but i have not tested them.
Click to expand...
Click to collapse
seems i didnt do that before my phone turn into brick. is there any possible to recover my devices through other people's back up?
all I want to do is make my devices open again, wipe data is fine, since having no any important data on the devices.
MrMiyamo said:
If you were backed up(read partition) every partition using mtkclient, than you just can recover your device through backup.
I had done recovering my device this way
Maybe there are other ways, but i have not tested them.
Click to expand...
Click to collapse
am i can also use this function now even my devices cant open. any suggestion for next step?
it does not work could you mind share your .bin file to me for getting out of brick?
I cannot write any partition now
logforjj said:
it does not work could you mind share your .bin file to me for getting out of brick?
Click to expand...
Click to collapse
I can, but my device is 32 GB
And i doubt you will break imei (i guess)
MrMiyamo said:
I can, but my device is 32 GB
And i doubt you will break imei (i guess)
Click to expand...
Click to collapse
anything is welcome as long as i can boot my phone and using it as normal.
Thank You!
And... How should I do?
logforjj said:
And... How should I do?
Click to expand...
Click to collapse
Well, i guess we can try this way, but since our device different, you can get firmware from here.
I will check the topic and i will try to help
(Preferably from Telegram or Discord)
If we success i will open a new thread about unbricking Realme C21, if we fail we will try other suggestions unless you gave up or ideas are over.
log4jj#2016
I can not use telegram at all, because I cannot receive sms message verify code, soory for your no convenient conversation.
logforjj said:
log4jj#2016
I can not use telegram at all, because I cannot receive sms message verify code, soory for your no convenient conversation.
View attachment 5570395
Click to expand...
Click to collapse
Can you describe what exactly lead you to this stage, device not booting at all?
And are you trying to use mtk-client? I ask this because I'm seeing that you also are using mtk-bypass too, so, what for are you using mtk-bypass tool? To bypass what?
SubwayChamp said:
Can you describe what exactly lead you to this stage, device not booting at all?
And are you trying to use mtk-client? I ask this because I'm seeing that you also are using mtk-bypass too, so, what for are you using mtk-bypass tool? To bypass what?
Click to expand...
Click to collapse
I have trying to root my Realme C21 Android 11recently, am I using MTK client, and my devices became brick after erase flash and other thing. So now I gonna save my phone through approach @MrMiyamo give.
SubwayChamp said:
Can you describe what exactly lead you to this stage, device not booting at all?
And are you trying to use mtk-client? I ask this because I'm seeing that you also are using mtk-bypass too, so, what for are you using mtk-bypass tool? To bypass what?
Click to expand...
Click to collapse
My own device has not been hard-bricked before, so I am not sure how to unbrick it.
My aim is to try methods that can be a solution(hopefully),
If you have experience please help us(so @logforjj) so we can quickly unbrick.
Now I cannot bypass.
Using Python 3.9 from win store.
Which Bypass.bat should I use, Topic's or MTK Bypass by Dinolek. FULL GUIDE ?
logforjj said:
Which Bypass.bat should I use, Topic's or MTK Bypass by Dinolek. FULL GUIDE ?
Click to expand...
Click to collapse
Are they different?
I reset my laptop every time I start follow the steps, I have seen CMD show my devices had has been bypassed successfully like figure show in that topics. Should I go to next step?
p.s. I actually do not know how to do next, how can I get scatter txt. and other needed file in one's @MrMiyamo given, any decrypted needed?
MrMiyamo said:
Are they different?
Click to expand...
Click to collapse
I cannot tell so I retry and reset my laptop so many times
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
Full Guide's