Develop Bugs

what does this mean?

can anyone tell me why my htc desire is stuck at this screen when i put in the battery?
-- 1 minute later --
well, i can't post a pic since not allowed to link until after 8 posts
it looks like a boot screen with 3 android dudes on the bottom.
any ideas?

Your stuck at the bootloader. Means that there is no boot.img. You've done something to it. Just flash a rom and it'll be fine. Don't forget to wipe data.

ok, thats positive news so far
the things is, i think its water damage but not much water at all really. just a bit from snowing while skiing.
the power and volume buttons do not seem to respond AND the ohone turns on by itself when i insert the battery.
is it still just a case of 'flash a ROM'? or is there more?

oh, and here is the image..... finally,
{
"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"
}

You don't have root or a custom recovery, correct? You just want to go back to the stock Froyo?

I think if the power buttons don't work it may be a bit of a problem selecting options in that menu, since the power button works as "select" in that menu.
I think you could boot to recovery using command prompt, but I am not 100% sure about that.
Also, are you rooted? Do you have a custom recovery installed?

What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?

sonoftobit said:
What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?
Click to expand...
Click to collapse
--- confusion ensues ---

my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help

liquidmonkey said:
my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help
Click to expand...
Click to collapse
Do you have a note of which rom was installed in your device? Is it carrier locked? Branded?

Select the newest RUU that fits your phone & carrier from http://shipped-roms.com/shipped/Bravo/. Extract the ROM, rename to PB99IMG.zip, place in root dir of sd-card and reboot. Should do everything else automatically.

don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.

and i should add that i am sweden if that matters.

The file you download from shipped roms is an exe file. When you execute the file it will extract a couple of files to your harddrive. Among those is a file named ROM.zip. That's the one you're looking for.
When I extracted it the file was here C:\Users\*User Name*\AppData\Local\Temp\{722DC7D5-7B69-4EBC-B6FB-B63AE38C01DE}\{50F2F878-636A-496F-A7CB-544C067E0C4B}
The ROM on shipped ROMs are all the standard carriers version that are unmodified.

liquidmonkey said:
don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.
Click to expand...
Click to collapse
Yeah but there are different versions of 2.2 depending on carriers etc, thats why I was asking!
I *think* any of the ROMS here with RUU at the beginning & WWE in the filename should work. (I am not 100% sure about this, as I have not had an official rom installed for AGES).
You will then have to follow sonoftobit's instructions I think, don't ask me how to extract the ROM though, as I don't know how to do it!
PS sonoftobit - Ignore this liquidmonkey!
If you go to the CM7 nightly thread and go to the 2nd post, Kali has a script for enabling Apps2SD. That is what I am running, tried to use S2E but it screwed things up royally and I had to restore a Nandroid!

Yeah, I had the same problems with S2E. I'm using DarkTremor App2SD now which has worked flawlessly ever since (both Sense Froyo and CM7). Also there's A2SDGUI for DarkTremor now which makes it even better.

StuMcBill said:
PS sonoftobit - Ignore this liquidmonkey!
Click to expand...
Click to collapse
why on earth would you write that?

so check it out!!!
i have had the phone off for a few more days and then put in the battery and BANG, it started up after a little while.
problem was that my battery only lasted 10 seconds so i was not able to fully test things.
then i put the battery in again and i was back where i started, crappy boot screen.
is there something in the phone that keeps memory of the boot screen and then disapates after a day which would explain why it started today.... or?

Red "F"

I dont know how, but a red F has appeared at my screen, and dont know how to removed it, has anyone had the same problem? any idea how to remove it? (is it a malware/virus? is it from an application ?)
thanx
{
"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"
}

Is it only on your lockscreen, or always visible?

if i remove lockscreen(disable pattern) is always, with lockscreen it remains at lockscreen
Petrovski80 said:
Is it only on your lockscreen, or always visible?
Click to expand...
Click to collapse

tabon said:
if i remove lockscreen(disable pattern) is always, with lockscreen it remains at lockscreen
Click to expand...
Click to collapse
Never saw something like this. Did it occur out of the blue or after flashing a ROM?
(judging from your non-stock battery icon I take assume you're on a custom ROM)

it just appeared, also i did a full clean new rom flash(wiped everything), but i restored my data (only the data from my apps/apk) and when someone called me,it appeared again,its weird
Petrovski80 said:
Never saw something like this. Did it occur out of the blue or after flashing a ROM?
(judging from your non-stock battery icon I take assume you're on a custom ROM)
Click to expand...
Click to collapse

tabon said:
it just appeared, also i did a full clean new rom flash(wiped everything), but i restored my data (only the data from my apps/apk) and when someone called me,it appeared again,its weird
Click to expand...
Click to collapse
Does it happen on stock ROM/kernel?

i have the stock kernel, my rom is stock,just deoxeded

tabon said:
i have the stock kernel, my rom is stock,just deoxeded
Click to expand...
Click to collapse
In that case I don't have any advice I'm afraid. I even googled it because I never saw something like it, doesn't yield any useful info. Could be some samsung driver causing Android to display this red f, but that's just speculation.
If it remains, I'd return to factory images, relock the bootloader and claim warranty.

yeah, i googled it too,and couldnt find a single post, the only reasonably thing is that it may be a virus or something, and it came back with the data restore, i cant think of something else, thank you for your time though
Petrovski80 said:
In that case I don't have any advice I'm afraid. I even googled it because I never saw something like it, doesn't yield any useful info. Could be some samsung driver causing Android to display this red f, but that's just speculation.
If it remains, I'd return to factory images, relock the bootloader and claim warranty.
Click to expand...
Click to collapse

you have an app doing that.

Try going through each of your backed up apps, to see if you can find the app that's causing this.

i killed each running app in the backround, and i found it, its an app named "Android lost" , never had a problem with it, dont know why it just happended (also it had long to time to do an update, so to say that was something in the update)
weird.

Glad you got it sorted out.

Petrovski80 said:
Glad you got it sorted out.
Click to expand...
Click to collapse
thank you guys, i ll monitoring it for 1-2 days

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!

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

One plus 5t root issue on new phone that son has buggered up!

Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?

{
"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"
}
brickedmum said:
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
Click to expand...
Click to collapse

tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012

Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
nguyenlucky said:
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse

brickedmum said:
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
Click to expand...
Click to collapse
You should let him experiment again, this time with some more reading here on the forum before though. He can learn a great deal about how different systems are built and the working parts of them.
And mostly since it's really fun, these days its really hard, close to impossible to mess up the phone bad.

Yes - He should be allowed to root it again - He needs practice

fkofilee said:
Yes - He should be allowed to root it again - He needs practice
Click to expand...
Click to collapse
I'm also in that opinion. He should be allowed to root again.
I may have an idea why this happened: Instead of an Oneplus 5T Firmware, he may have flashed a Oneplus 5 Firmware..
you mentioned an upside down turned Screen... well, the normal oneplus 5 had their Display assembled upside down and oneplus thought it would Fixing it by turn the Display Output by 180° by Software configuration. Your son should be Aware of that Oneplus 5 and 5T are different devices.

First step is using fastboot adb tool to flash some custom recovery first such as twrp,then download the latest oxygen system from oneplus official website(should be about 1.6gb) flash it inside and reboot. U will get a official system with official recovery set everything up. Then flash the custom recovery again and flash custom kernals such as bluespark or franco. goto the google pay or other root blocked app to set up everything.
Now you can flash the magisk to get root and activate magisk hide immediately right after u reboot. Remenber to tick the apps you need to hide the root for.
Wish u success:good: