Develop Bugs

ZE551ML Bootloader Keeps Rebooting

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!

bricked Lumia 550 (RM-1127) seen as Lumia BootMgr by Windows Device Recovery Tool

A Lumia 550 (RM-1127) phone in bootloop is recognized by Windows Device Recovery Tool as "Lumia BootMgr"
{
"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"
}
Besides pressing the Install software button, which will delete all content, is there anything else it can be done?

most likely not, data is lost. but the wdrt should be able to recover
i assume you bootet it manually into blink/flashmode,selected my device doesnt get recognized and chosed the 550? thats the right way to recover it
if even the blink/flash modus doenst work its not bricked then its physically defect cause that flashmodus part is located in a place of storage which isnt and cant be touched by any update

tofuschnitte said:
i assume you bootet it manually into blink/flashmode,selected my device doesnt get recognized and chosed the 550? thats the right way to recover it
Click to expand...
Click to collapse
Yes, otherwise it's not detected. When powered on, the phone displays the Microsoft text, the logo and then the screen goes black.

w.bogdan said:
Yes, otherwise it's not detected. When powered on, the phone displays the Microsoft text, the logo and then the screen goes black.
Click to expand...
Click to collapse
Whats the status now, bro. You get it working?

mabry said:
Whats the status now, bro. You get it working?
Click to expand...
Click to collapse
It's not my phone and I was waiting for some other suggestions. It's still under warranty and the owner might want to take it to an authorized service. It strange because the phone was not messed with, likely wasn't even connected to the Internet when it stopped working.

either the os itself ****ed up or its damaged
but the internal data is lost. no way to get them. just use the wdrt. you wont risk the warranty with reflashing it with the wdrt and if the device itself is not damaged it will work like it did before. if the wdrt isnt able to recover it -> rma it

I've got a little more info: the phone was running 10.0.10586.420 (version taken from Microsoft account - Devices) and crashed while starting the camera. It has been succesfully restored with WDRT to 10.0.10586.107 then OTA upgraded to 10.0.10586.545. For now, it looks good.

why was it stuck in 420 at all? that version is ooooooooooooooooold and should have got 494 and 545 in the last weeks.
and good that it worked (expected nothing else), and its normal that it flashed the .107. MS doesnt build images for every cumulative update (or lets say they never done it only for the 950 devices which were released with the .0 got updated images for the 107. maybe the 550 too? dunno if it was released that early together with the 950 devices)

tofuschnitte said:
why was it stuck in 420 at all? that version is ooooooooooooooooold and should have got 494 and 545 in the last weeks.
and good that it worked (expected nothing else), and its normal that it flashed the .107. MS doesnt build images for every cumulative update (or lets say they never done it only for the 950 devices which were released with the .0 got updated images for the 107. maybe the 550 too? dunno if it was released that early together with the 950 devices)
Click to expand...
Click to collapse
Some people actually use their phones to make phone calls and don't care for 1 hour OTA update every three weeks. Besides, it’s good to be able to call 911/112 if an emergency occurs and not wait for Microsoft to finish installing bloatware. Personally, I still use an eight-year-old Symbian phone which never fails me. My Lumia is just for fun, not like a real phone.

sure, thats why those updates autodownload and prepare and get itself installed in the night when you sleep
just wanted to say with that: something was borked with the os, cause it hasnt itself updated to newer versions (or was never connected to wifi in the last two months...)

tofuschnitte said:
sure, thats why those updates autodownload and prepare and get itself installed in the night when you sleep just wanted to say with that: something was borked with the os, cause it hasnt itself updated to newer versions (or was never connected to wifi in the last two months...)
Click to expand...
Click to collapse
It's possible that it hadn't connected to wifi, it had a data plan. But what if the problem was caused by a failed update? Just starting the camera app doesn't break all hell loose on the OS, doesn't it?

Lumia 550 android
Hi everyone
Can somebody help me for flash Android on a lumia 550
my question is, can i set a rom of android in a .ffu file for flash my lumia win phone 10 to android 6.0
hope somebody can help me

How to get rid of the "Your device is corrupt message"?

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

Return to stock issue - "bootloader is already unlocked"

Hi Everyone,
I'm trying to re-lock my bootloader but the OEM Unlock toggle is stuck to the left position whilst displaying the message "Bootloader is already unlocked".
If I try to switch the toggle to the right position, the device will factory reset and then when it powers back up, the toggle is in the left position again.
Is this a result of knox being tripped?
In DL mode it displays both FRP and OEM lock as OFF.
Thanks for the help!
{
"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"
}

Just ignore it, it causes no problems and others have had the same problem since unlocking theirs

*Detection* said:
Just ignore it, it causes no problems and others have had the same problem since unlocking theirs
Click to expand...
Click to collapse
Yeah I know that it's not technically an issue but I want to sell the phone and would like to lock the bootloader before doing so.
Is there no way to re-lock it?
If not... would it stop the phone from passing safetynet/google pay checks?
Thanks
EDIT: I've just tested and google pay won't work on it in this state.

You tripped KNOX, many things won't work on it again anyway

*Detection* said:
You tripped KNOX, many things won't work on it again anyway
Click to expand...
Click to collapse
I'm quite aware of that. What i'm specifically trying to ascertaine is whether or not the bootloader is re-lockable.
If need be I'll just install magisk on stock and put the info in the eBay listing.
Thanks for the assistance anways!

As I said, other members have already posted about the same problem, I have not seen a solution yet, although you could read through a few of those threads and see if they were updated

Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!

Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?

MadSilence said:
Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!
Click to expand...
Click to collapse
why in gods green earth would you actually WANT Citrix? Kidding, i use it 40 hours a week and its abysmal, as if you didnt already know that.
naztam said:
Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?
Click to expand...
Click to collapse
So, the bootloader is unlocked, have you guys tried flashing the Odin files with a newer revision of the bootloader?

Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.

naztam said:
Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.
Click to expand...
Click to collapse
what firmware version are you on currently? if your bootloader is revision 5, flash a rev 6 and see what happens

I am in the last firmware
I have the rev6, I can only flash the firmware of July and August

naztam said:
I am in the last firmware
I have the rev6, I can only flash the firmware of July and August
Click to expand...
Click to collapse
[email protected] then. maybe a ver 7 will release soon?

HTC One E9 plus - dotview

Hello Dears,
kindly help me as my phone after hard reset stuck on dot view mode automaticly and i can't exit it or even setup my phone like gmail or lang ,
after five seconds after make har resest dot view mode apper and i can't exit it ,
{
"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"
}
Best Regards ,

Redo the hard reset and try again. Also, I suspect that your screen is frozen (watch for changes in dot view mode, like time and battery percentage). It might also be that your tactile screen isn't working anymore and requires a change.

sharvyngunga said:
Redo the hard reset and try again. Also, I suspect that your screen is frozen (watch for changes in dot view mode, like time and battery percentage). It might also be that your tactile screen isn't working anymore and requires a change.
Click to expand...
Click to collapse
Thanks Dear for your replay ,
but the screen is not freezed as i can check my call history and time and battary status ,
also i made har reset and change all frim as i made new flash but problem still exist ,
Regards

Can you share a video of the boot process?
I'll try my best to help you, but I can't guarantee success.

sharvyngunga said:
Can you share a video of the boot process?
I'll try my best to help you, but I can't guarantee success.
Click to expand...
Click to collapse
Thanks Dear ,
i don't have another phone , but i will try to get new one ,
Thanks

Sorry, this is completely unrelated from the current topic but I reallly need help..I tried to flash a rom on my HTC but thr preloader got corrupted xo my phone go hard bricked. Pluging the phone into a computer just shows a red led and the computer shows nothing in device manager.
I tried uninstalling the MTK Preload VCOM driver and reinstalling it but that still didn't work.
Even pressing volume keys while connecting still gave nothing.
I also tried disconnecting the battery and reconnecting the phone to the computer but still nothing.
If there is anyone, please help me.....
I need to unbrick my phone................... I am begging, please help me.

When my E9 got hard bricked, I sent it to a repair shop. They took a long time, but they brought it back to life.
Now, I had a hard brick issue with a Lenovo P1M Vibe (also a MTK device). I solved it using SP TOOL and the proper files. I don't know why the app suddenly decided to detect my phone after dozens of tries. But, during my research, I found interesting articles:
How to get a PC detect and MTK device after flashing wrong ROM/Firmware (Test Point method)
Download the latest & updated stock rom firmware of popular phones like samsung, tecno, itel, infinix, etc with flashing & upgrade tools & instruction
www.romkingz.net
As for the software part of the solution:
[Guide/Info] [How To] Unbrick your Bricked MTK Devices (Dead Brick)
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc) THIS IS FOR INFORMATION ONLY. Q. How Phone gets Bricked? Ans : Basically, phone get bricked during the installation of Android OS (flashing)...
forum.xda-developers.com
You will need additional files for your phone during this process. You can find them online.