Develop Bugs

back to sense from gpe

hello
i want the same ruu stock version :
{
"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"
}
in the box saye (Nordic certified phone) my phone is unlocked
bootloader unlocked and s-off
i want reback to this version
pls help me to get it right

So that's on your device at the mo, or you want to go back to 4.16.401.10? Can you post your current getvar output?

EddyOS said:
So that's on your device at the mo, or you want to go back to 4.16.401.10? Can you post your current getvar output?
Click to expand...
Click to collapse
mo what mean ? all informations i given when my device is stock just unlock bootloader

Mo = Moment, e.g. 'So that's on your device at the moment?'
Are you saying the picture(s) you've posted are what is running on your device right now, or are you using a GPe ROM? Your OP isn't that clear

EddyOS said:
Mo = Moment, e.g. 'So that's on your device at the moment?'
Are you saying the picture(s) you've posted are what is running on your device right now, or are you using a GPe ROM? Your OP isn't that clear
Click to expand...
Click to collapse
for now i use GPe ROM. and this getvar
the pic's on the top for my old stock senes and clear when i buy the device
and i want it

That's fine. You need to:
1. Change CID to Super CID
2. Flash the ZIP in the 'Back to Sense' thread
3. Once back to the Sense bootloader change CID to HTC__001
4. Flash the 4.16.401.10 RUU available here - https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/

How to remove demo mode

So I work at a phone retailer and was fortunate to get our HTC One M8 display. Have gotten some things before and they were real easy to fix to become "standard units".
The HTC was not as straight forward though.
I tried to delete the demo App but that could not be done
{
"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"
}
I tried to just factory reset it but that could not be done as the Ok button was greyed out like so:
I then read up on a guide to flash it with Hasoon2000's AIO Toolkit, but when I tried that I could not do the step 3 "Get token ID".
I only got up "error: device not found", so I tried to reinstall the HTC drivers a few times to no avail.
I though this might be due to the fact that developer mode can't be turned on but it seems like USB debugging is active.
View attachment 3406822
At this point I'm not sure what to do.
Any advice would be greatly appreciated.

The only thing it seems you can do is s-off and use a RUU.

LarryBoyG said:
The only thing it seems you can do is s-off and use a RUU.
Click to expand...
Click to collapse
Thank you for the reply. I will try this out

And change the CID once you obtained s-off. It's now in the line of HTC__002 (only used for demo devices)
1: S-OFF
2: change cid to HTC__001 (for example. Any wwe cid will do)
3: run the wwe RUU

Yes, change your CID. Your RUU will fail until you change it. Changing it to 11111111 will open up your options of which one you can use. If you have a CDMA device use a Verizon or WWE depending on bands your wanting to use. If you phone is GSM capable you can't go wrong with the dev addition.

NJ1 safe to flash??

So I was plagued with the task of rooting an s3...
I managed to root and flash twrp. However I want to make sure before I flash a rom. Is the bootloader locked on NJ1 firmware?
SANSUNG-SGH-I747
VERSION 4.4.2
I747UCUFNJ1
it's probably been asked already but I haven't been able to find an answer. Thanks

The bootloader cannot be locked if the phone was successfully flashed with twrp.
The bootloader on the att s3 has never been locked, unlike many other phones from att.

audit13 said:
The bootloader cannot be locked if the phone was successfully flashed with twrp.
The bootloader on the att s3 has never been locked, unlike many other phones from att.
Click to expand...
Click to collapse
Awesome thanks! Would you happen to have any insight on why the phone would be stuck in factory mode? And would flashing a new rom take it out?

What do you mean by factory mode? What message appears on screen when you boot the phone?

{
"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"
}
Looks like this..
Sent from my HTC One M9 using XDA-Developers mobile app

You have the international version of the s3? The North America version is either i747 or i747m?

audit13 said:
You have the international version of the s3? The North America version is either i747 or i747m?
Click to expand...
Click to collapse
No it's the I747. At&t
I just grabbed that pic off of the internet to show as an example.
Sent from my HTC One M9 using XDA-Developers mobile app

What my firmware??

My system is AT&T and model is H810 on system configs of Android...
But on SALT he says LG LS991 and Carrier says "SPR" (Spring variant)
What's my device model??
LG LS991 or H810 AT&T?
{
"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"
}

wmsouza said:
My system is AT&T and model is H810 on system configs of Android...
But on SALT he says LG LS991 and Carrier says "SPR" (Spring variant)
What's my device model??
LG LS991 or H810 AT&T?
Click to expand...
Click to collapse
The firmware (rom) installed is not a determinant of what your phone really is. I suspect this is a frankenphone. If you bought it this way, I would try and get your money back asap.
The only way to be absolutely sure as to what the phone really is and what firmware should have been installed on it, is to open it up and see what is stamped on the motherboard. Unfortunately with the firmware installed now, you have most likely, with an ARB of 4, negated any chance of unlocking your device unofficially if it is still bootloader locked or doing much else with it for that matter.

sdembiske said:
The firmware (rom) installed is not a determinant of what your phone really is. I suspect this is a frankenphone. If you bought it this way, I would try and get your money back asap.
The only way to be absolutely sure as to what the phone really is and what firmware should have been installed on it, is to open it up and see what is stamped on the motherboard. Unfortunately with the firmware installed now, you have most likely, with an ARB of 4, negated any chance of unlocking your device unofficially if it is still bootloader locked or doing much else with it for that matter.
Click to expand...
Click to collapse
I bought it on aliexpress ... it was sold as H810 but on SALT it shows LS991 and SPR on Carrier

SALT show ARB 4

Android 6 and on Developer Options I enable BootLoader Unlock but after enable he still disabled

S20 Ultra on Android 10 won't update.

Recently I bought an s20 ultra from Ebay and I can't get it to upgrade. It says the operating system is up to date. I know I can do it manually if necessary. My question is why can't it do it automatically?
{
"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 AT&T locked or that (ATT) is just a coincidence? Maybe it really is the latest version for AT&T locked devices.

Deses said:
Is it AT&T locked or that (ATT) is just a coincidence? Maybe it really is the latest version for AT&T locked devices.
Click to expand...
Click to collapse
Thanks for the reply. Yes, it's locked to AT&T and I have checked on sammobile and there doesn't seem to be an update available for my specific model number but for the SM-G988U1 there are, also for other model numbers of the S20 Ultra, why would mine be left out, do you have any ideas?

Galaxyuser75 said:
Thanks for the reply. Yes, it's locked to AT&T and I have checked on sammobile and there doesn't seem to be an update available for my specific model number but for the SM-G988U1 there are, also for other model numbers of the S20 Ultra, why would mine be left out, do you have any ideas?
Click to expand...
Click to collapse
Because your mobile carrier can't be arsed to validate the update and distribute to its locked devices. I've heard a lot of grief over the years over locked devices and updates and being unable to tinker with the phone because the bootloaders are all locked.

Deses said:
Because your mobile carrier can't be arsed to validate the update and distribute to its locked devices. I've heard a lot of grief over the years over locked devices and updates and being unable to tinker with the phone because the bootloaders are all locked.
Click to expand...
Click to collapse
Thanks I guess the best thing to do would be to have it unlocked and then hope it gets updated. or do it manually.