yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] carina77:
USPL with Stock Shipped ROM

This is my first WM device and i'm very interested in flashing one of the cooked roms...Just bought my Touch HD not more than 24 hrs and i'm keen to upgrading the device...

So, is it possible that after i USPL'd my device and upgraded it with a cooked rom, to straight away install the shipped rom later without USPL'ing the device?...(Say, for instance, from a Dutty's ROM 1.7 straight to shipped 1.18.707.3WWE = which is my my originally bought device ROM with SPL 1.14.0000)

Thanks.
[Touch HD Windows Mobile ROM Development] DaveShaw:
If (as you say) it is the ROM from your carrier then yes, your can just install it.

If it has been dumped and re-constructed then you will need to use USPL again.

You can use USPL to upgrade to a shipped ROM if you want to, it won't cause any problems, and might prevent problems if you accidently flash the wrong ROM :)

Thanks

Dave
[Touch HD Windows Mobile ROM Development] Mourmor:
Thanks for that new version-Is it also caompatible with Vista 32??
[Touch HD Windows Mobile ROM Development] stepw:
Same thing as before, it works on Vista with old ActiveSync driver.
[Touch HD Windows Mobile ROM Development] congdan:
Hi Stew,

I received this :

D:\programs\Mobisoft\TouchHD\ROM\uspl>blac_uspl

HTC Blackstone USPL version 2.4, Feb 7 2009

Opening USB port \\?\usb#vid_0bb4&pid_00ce#5&239a3733&0&1#{25dbce51-6c8f-4a72-8a

6d-b54c2b4fc835}...

WARNING: Port \\?\usb#vid_0bb4&pid_00ce#5&239a3733&0&1#{25dbce51-6c8f-4a72-8a6d-

b54c2b4fc835} parameters could not be set

WARNING: Port \\?\usb#vid_0bb4&pid_00ce#5&239a3733&0&1#{25dbce51-6c8f-4a72-8a6d-

b54c2b4fc835} timeouts could not be set

ERROR: No response from device

HTCSBye!>.L.HTCE

D:\programs\Mobisoft\TouchHD\ROM\uspl>

please tell me what can I do?
[Touch HD Windows Mobile ROM Development] Moony1987:
Flashing with Vista? You're not running the old ActiveSync driver.

I've made a quick and dirty guide, follow it and you should be fine! :)

http://rapidshare.com/files/198706883/flashguidev01.pdf
[Touch HD Windows Mobile ROM Development] congdan:
thank you so much. I will try that.
[Touch HD Windows Mobile ROM Development] adamwebb28:
How to Flash a Rom?

Hi

I am new to Windows Mobile and installing new ROMS.

I've read through some threads on here and the WIKI but I just can't seem to get Dutty's new ROM to install.

I'm trying to use USPL, I've followed the instructions on the wiki, but I don't understand what is ment by :

"Execute blac_uspl.exe; current status and any error messages USPL encounters will be displayed in the console window."

Does this mean on my PC??? As that doesn't do anything?

So what am I ment to do?

Thanks!
[Touch HD Windows Mobile ROM Development] MJRL:
Did you read the USPL recomendations?

Did you put your phone in boot loader mode to flash uspl?

If you are in Vista did you install the usb old driver?

If you use WMDC did you disable allow usb connections?
[Touch HD Windows Mobile ROM Development] adamwebb28:
Hi

I turned off the phone, pressed the volume down button and the on button. Then the tri-colour screen came up and said USB at the bottom. Thats where I got a bit lost? I plug the phone back into my pc right? When I do that I get a message that HTC USB Sync has been installed.

Could this be the driver then? I can't work out how to install the driver in that link?
[Touch HD Windows Mobile ROM Development] qai5er:
Flashing a cooked ROM

Hi All,

I'm still failry new to WinMo and attempting my first ever flash of a cooked ROM. I have searched the forums but haven't been able to find the answer to my question! Hoping someone can help...

I am trying to flash Duttys HD V1.8 Xtreme Rom. I have used USPL and can understand the instructions just fine up to:

Execute blac_uspl.exe; current status and any error messages USPL encounters will be displayed in the console window.

If everything goes well, your device will restart and SPL version label should read "1.14.USPL" indicating that USPL was loaded successfully.

However I don't understand the next step:

You can then start RUU update to flash RUU_signed.nbh. Once RUU update is completed, device will restart using regular flashed SPL.

In short, can someone advise the steps I need to take to flash the ROM. I have copied the file BLACIMG.NBH into the root dir of my storage card and gone into bootloader mode. My device displays the tri-color screen but then immediately displays white screen with blue writing "Loading...".

If I remove battery and power the device back on, it comes on as normal with the stock rom.

Thanks
[Touch HD Windows Mobile ROM Development] cb8rwh:
I am getting the same problem as qai5er, anyone got any ideas what we are doing wrong?

Is it down to phone being locked to a network - I don't think mine is but, perhaps this is the problem?

Cheers

Rich
[Touch HD Windows Mobile ROM Development] DaveShaw:
I think you might have missed this bit from the 1st post...

If you want to flash from SD card instead, make sure your SD card is not inserted when you enter the bootloader originally.

SPL will try to install it and would fail if blacimg.nbh is not signed by HTC. Insert the card after "USB" label comes up in SPL but before running USPL.

If you're flashing from SD Card, check the text I posted above. If you want to flash via USB, then just run the RUU Prorgam that came with Dutty's ROM when the USPL is loaded.

Thanks

Dave
[Touch HD Windows Mobile ROM Development] qai5er:
Thanks

Dave,

Thanks so much. Flashing Dutty's ROM as I write this. Seems to be going well. I appreciate your help and the contributions of so many individuals on here who make this place a great community.

This community makes it worthwhile buying WinMo.

Thanks Again

*Hate being a "NOOB"

Qas
[Touch HD Windows Mobile ROM Development] cb8rwh:
Ditto what Qas said, thanks for your help. Worked perfectly. I can imagine now I have flashed one I will continue flashing regularly!

Cheers

Rich
[Touch HD Windows Mobile ROM Development] skyli91:
Can i use uspl under Windows7?
[Touch HD Windows Mobile ROM Development] stepw:
You can try it... If it doesn't work, you won't harm your device.
[Touch HD Windows Mobile ROM Development] Black Antitoon:
Please tell us if it works, I am interested too.:D
[Touch HD Windows Mobile ROM Development] nightszeli:
Does somebody know perhaps what reason for this mistake is? When I am connecting usb to the device are installing it oneself drivers and later it is turning out USB on the white belt and next I am starting. exe on a computer of VISTA wines and a mistake is jumping out.

Mistake more low

HTC Blackstone USPL version 2.2, Dec 26 2008

Opening USB port \\?\usb#vid_0bb4&pid_00ce#5&236...

ERROR: USB port could not be oened!

Verify that device is connected and SPL boot mode is
[Touch HD Windows Mobile ROM Development] skyli91:
Now i updated the driver with the 2004 one and did that f8 thing when startup. It think it should work. Maybe i'll flash later.

When to put the card with the blacimg in? After uspl or i can copy blacimg before everything and just simly not take out the card?
[Touch HD Windows Mobile ROM Development] civilization:
i run uspl_2.4 on xp sp3 and everything gone fine

now i got spl 1.15, does this add any thing new to the device?
[Touch HD Windows Mobile ROM Development] civilization:
SPL 1.14 OliNex appears again when i access the boatloader?
[Touch HD Windows Mobile ROM Development] Blessed HD:
Hi,

I've been trying to use USPL on my HD, but every time I connect the USB to the device on Bootloader, the "USB" label does not appear AT ALL as it should !

Bootloader screen by the way only takes less than a second & then moves on to the white screen where I'm asked to press the VolUp button to confirm the reset..

I followed the instructions carefully, but I'm not sure where I went wrong :confused:
[Touch HD Windows Mobile ROM Development] sjoerd_t_B:
I installed duty's extreme rom using uspl from my sd-card. But i want to go back to my stock rom again. Can someone explain how go back to original stock rom? I have no experience with these things so a clear explanation is needed
[Touch HD Windows Mobile ROM Development] stepw:
You still have HSPL flashed, you don't need to use USPL at all.

USPL is meant for the situation when you want to keep your original SPL and flash cooked ROMs.
[Touch HD Windows Mobile ROM Development] stepw:
Re-plug the USB cable after USPL loads to your device without touching any keys. If you get a reset prompt, then volume up key must be stuck.
[Touch HD Windows Mobile ROM Development] stepw:
Download the official ROM you want to install and do the same as you did with Dutty's.
[Touch HD Windows Mobile ROM Development] Blessed HD:
Actually, I did re-plug the USB cable but didn't work!

Problem finally solved by re-entering to Bootloader over & over again until the "USB" label was in the white part of the colored bootloader screen.. Now I'm enjoying my newly flashed cooked ROM :D

Many thanks stepw for the cool tool .. ;)
[Touch HD Windows Mobile ROM Development] davenash:
I read the first few pages and searched the rest of the thread for windows 7 to no avail...

I can't get this utility to work on Windows 7 (official MS beta release), the cmd window popus up for 0.2secs and disappears, no chance to even printscreen whatever is printed in the window.

Tried running as an admin (same results) and in vista compatibility (window opens for about 2 secs then crashes).

@stepw: Should this tool work with Win7?

Anyone else: Have you managed to get this to work with win7? Did you have to take any special steps?

Thanks!

edit: Obviously I already have WMDC 6.1 installed
[Touch HD Windows Mobile ROM Development] davenash:
Okay here's a screenshot. I warn you, it is the world's worst screenshot. For some reason I can't get a screenshot when the window is fully open - even when I can move my fingers in 0.2secs - this is because the whole screenshot comes out black presumably because of some cmd compatibility issue with the process or something.

Well anyway on this screenshot I caught the cmd window just as it was fading out of view so by that point Windows was probably handling a transparent image rather than the actual cmd window and thus it was possible to take this screenshot. Phew...

I think it's just about legible...
[Touch HD Windows Mobile ROM Development] Moony1987:
davenash - USPL doesn't work with the current activesync drivers that are installed in Windows 7 and Vista.

Vista it is fixable by installing the old drivers, and then rebooting so you allow the unsigned drivers to work.

Windows 7 does not allow unsigned drivers at all so currently it's not usable there.

For Vista i've made a very dirty guide which you can find at

http://rapidshare.com/files/198706883/flashguidev01.pdf
[Touch HD Windows Mobile ROM Development] ilj:
Stuck on the white loading screen, help

Hey everyone. First off all, big HI to everyone and thanks for helping.

I'm pretty much a beginner with these things, and yeah... I messed up bad apparently but I was thinking I was following instructions.

I decided to try and flash Dutty 1.9b after reading so much about it and looking at the screens. I decided to do it via USPL since I reckoned it much less invasive and doesn't change anything on my HTC permanently.

Anyways. I got the USPL, I got Duttys, copid the file to my SD card, read all the instructions...

So i thought, hey, let me see that loading screen once before I try change anything, so I pressed volume down and Power button. I didn't have my USB cable in, I didn't start USPL program on my HDD, but Duttys file was on the SD card, and the SD card was IN the device.

So I saw the tri-colour screen for a brief moment, and before I could even look at it clearly and react to anything, a white screen showed up, it says "Loading..." and nothing is going on for 15min now, and quite frankly, I'm scared for my device. I tried holding down on the power button but nothing is happening.

In short.... yah... I'm an idiot, but someone please, please help, and fast :(

EDIT: well, I counted my prayers and after a while pressed the soft reset button. And I cheered when I saw the old version come up, loading screen, my device's old ROM started up, and all the works. In short... nothing happened? So.... ugh.... now that I'm past the heart attack phase.... is there any chance to at least wait awhile on that tri-colour screen, see what the hell is going on, have time to react or anything, any more recomendations or instructions for the begginner, or just "Son, consider this a warning, forget the whole deal" :))) I just love my HD device, but I'd like to experiment with all those interesting ROMs, programs, and all the stuff, but heck, this gave me a scare. I know I'm more or less spamming the board, and sorry for that, but... any words of wisdom? :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
Device:- Mi 11x (android 13)

Custom Rom :- Pixel Experience Plus latest-1 version on android 13

What has worked for me :

1. Enable Zygisk

2.0. Select all the app inside Configure Deny list

2.1. Make sure that the bar above the app u selected is full (all the toggles for the app are selected)

2.2. Enable Enforce Deny list

2.3. Also select GOOGLE PLAY STORE and GOOGLE PLAY SERVICES aslo.

2.4. Install Magiskhide props config Module latest version

3. Install Safety net fix v2.4.0-mod_1.3 (just search google for this version, u will get it)

4. Reboot

5. Safety net should pass

5.1. Also, now in Configure Deny list Google Play Store and GOOGLE PLAY SERVICES will not be selected. IT'S ok. It means that the Safety net fix and Magiskhide props config have worked!!!

6. For all the apps Mentioned above

7. Need not follow Enable Enforce Deny list

8. Need not follow Select all the app inside Configure Deny list that is not working

8. Need not follow, Make sure that the bar above the app u selected is full (all the toggles for the app are selected)

9. Reboot

10. Clear cache and data of Google Play Services and Google Play from setting>app

11. Your app should open.

🥳🥳🥳

EDIT:

Sometimes it won't work... in such case, See if u have a TWRP folder in your internal storage , DELETE it.

EDIT 2:

After some tinkering, I had to change the Sequence of steps... They are now in italics for the steps changed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
Weirdly the official one from github does not work.

I searched and found this and it did work. Strange.

Universal SafetyNet Fix 2.4.0-Mod 1.2 (Zygisk).zip | by KuronosuKami for OnePlus 8 Pro

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
Here i have attached version 1.3 that i used
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] laid1995:
How to Pass safetyNet and use GooglePay, phonepay, any banking or trading app on Mi11x, redmi k40 and or poco f3 :

Steps :

1- Flash kernel that supports KernelSU. (unroot magisk if rooted).

2- .. That's all.. no more steps.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
Interesting!

However, I need Magisk root to use some apps

namely vanced youtube and SwiftBackup
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] laid1995:
Yeah. I use those. You can flash them.

Once you flash the KernelSU supported kernel.

you install root manager called KernelSU app.

This app will manage your modules and root permissions.

Root is undetectable in this root method. No need to flash anything to hide root.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pegasoc:
POCO F3, I use Xiaomi.eu v.14.0.70 can I follow this guide?

Which kernel should I use?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] laid1995:
Try No Gravity kernel. it supports KernelSU + MIUI.

https://xdaforums.com/t/kernel-overclocked-no-gravity-2023-08-28-protonclang.4531517/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
U can follow my steps... just have a data backup... or follow any other persons...

disclaimer... i wont be responsible for ur data loss... always keep backups
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Gaalpos:
ill try this and report if it worked for me
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bozinsky73:
Following info provided in KSU method, I'd like to add those steps for when GPay app and/or other banks app that may have detected root/unlocked bootloader in your devices. This also means that PlayStore consider your device has NOT CERTIFIED (it doesn't meet BASIC integrity evaluation type)

This may happen when a magisk/KSU module is installed in KSU app and environment results has modified.

1) flash Zgysk on KernelSU ( from GitHub) in KSU app as an addon

2) flash, same way, (the latest and better working module to fix safetynet): Play Integrity Fix (from chiteroman dev, also from GitHub) (today's version is 12.1). This one is constantly updated to the latest fixes available.

Also:

- if you are coming from a NonCertified Playstore state, after flashing those 2 zips you only need to delete PlayStore app's data and wait since it will be updated and ready to work again.

- device status (meaning certified or not certified) will take a variable amount of time to be visible again, but GPay and bank apps will start working fine immediately
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
Thanks Guys.

Today i Changed my rom and thus tried KSU... Its Freaking Easy
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] bozinsky73:
this is, based on my experiments that involves 12 different KSU enabled kernel - for both MIUI and AOSP roms - the best one for stability, performance and battery backup.

It is updated frequently (actually in beta version but you can consider it as stable version..), like once every 10 days.

It's usually provided as AOSP variant, but in his telegram channel the developer provides the dtbo file for MIUI roms, that you just need to replace inside the kernel.zip to get its MIUI flashable variant.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Mother_Teresa:
What works for me is the following (no kernel stuff etc);

(you are rooted and using Magisk)

Open Magic to update to the latest version, as should be highlighted upon opening the app. This means 'app' update and after that 'magisk' update.

Now we are up to date.

I used a Magic module 'safetynetfix', which no longer works since recently, so I uninstalled it and rebooted.

After the reboot (into the now un-tinkered system), do the following;

Go to settings->manage apps

Enable the viewing of system apps by selecting it via clicking the 3-dots on the top-right

Find the apps listed below and select 'force stop' and next select 'clear data --> clear cache'

apps: "Google Play Services", "Google Play Store", "Google Wallet"

(Maybe an inbetween reboot helps purging cache leftovers and after a reboot you can do the 'force stop', 'delete cache' for those apps again, to be sure?)

The new Magic module that I installed and tested is available via the following link;

https://github.com/chiteroman/PlayIntegrityFix/releases/latest

After a reboot I first opened Google Play Store to update any apps and rebooted to feel in control.

Next boot I opened Google Wallet and my bank app and it showed my linked card.

Even better, it worked again when I tried to pay in a store.

As I did not bother to remove the card to reregister it after, I was somewhat suprised that I did receive a 'new' confirmation email that I succesfully enrolled Googe Pay, so the opening of the apps after these steps may be mandatory.

Source that brought me to this solution -->

https://www.reddit.com/r/Magisk/comments/17qosjz
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Gr1mw00d:
are you using old version ROM or a new one? can you please specify the ROM you are using?

becuase i cant get it to work.

also, do you have gapps included in your ROM or did you use nikgapps?

EDIT:

the playintegrityfix got updated a few hours ago and now its working. thanks for the solution!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Gaalpos:
Im going to try this because nothing is working for me.

Edit: seems like its not working for me still :(
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
I have moved on from the above method to the one mentioned here!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Mother_Teresa:
It seems it is cat-mouse this week.

2 times these days I failed to be able to pay where it worked a day before.

Look for available updates in the Magik module as it seems to get updated when it gets broken.

Currently at v13.

Not sure if you need to redo the preperations of the apps, like 'force closing/clear cache/reboot'.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chinmoy_mi_11x:
i moved back to safety net fix and after my previous msg it seems to have broken!
[General Questions and Answers] WeiCheng Su:
After succeeded enter TWRP, I tried to use ADB sideload to flash custom ROM but it didn't work so that I forced power off the phone

However, while boot again, the phone directly skiped bootloader list and enter fastboot mode

even if I flash TWRP and sand command "fastboot reboot recovery", it still stuck at fastboot mode
[General Questions and Answers] WeiCheng Su:
I tried to flash TWRP again, but it still enter Fastboot mode
[Upgrading, Modifying and Unlocking] Dandelion228475:
Posted this in general questions as well but I could use more eyes on the issue if possible. If it doesn't fit here then please feel free to remove the post!

Hey there. I recently purchased an unlocked Umidigi A11S for rooting purposes, but I'm running into an issue very early in the process. After putting the phone into developer mode and enabling OEM unlock and USB debugging, the phone registers properly as a connected device in ADB and in fastboot mode after rebooting to the bootloader. Unfortunately, after trying to run the "fastboot oem unlock" command, it gives the error below.

FAILED (remote: Unlock bootloader fail.)

I have searched and attempted practically any solution I could find here on XDA for Umidigi phones but still haven't had any luck. Drivers are updated and I've tried multiple different versions of ADB with no success. Any help at all would be very, very appreciated.

--

Info from the other post:

adb shell "getprop ro.oem_unlock_supported" returns an output of 1

adb shell "getprop ro.boot.flash.locked" also returns an output of 1.
[WebOS Software and Hacking General] Mary1989:
Hi

I have trouble finding Open Source Apps in "LG Content Store".

Maybe I am too stupid for a web search.

I only know and use daily https://github.com/jellyfin/jellyfin-webos

Are there any other?
[WebOS Software and Hacking General] Mazda77:
Homebrew Channel - альтернативный магазин приложений : Телевизоры LG - Приложения

Как оказывается, есть жизнь за пределами официального LG Content Store. С помощью удобного альтернативного магазина приложений Homebrew Channel от команды можно ознакомиться с неофициальными версиями ...

webos-forums.ru

webosapp.club
[Tilt, TyTN II, MDA Vario III General] nubsauce:
Hey everyone,

I just purchased a used tilt off the hofo forum and after reading up as much as possible to get a general idea on how everything works in general, phone, roms, sync, etc.

I noticed a few bugs that I'm not sure what area to focus on to fix. If anyone could give some directional guidance into what area (rom, radio, wm6.1 issues, etc.) i'd have to look into for fixing these issues it'll be greatly appreciated. :)

Keyboard lag/unresponsive. Sometimes when texting after knowingly pressing the correct button it doesnt show on the screen and my words get cut off or the space takes appear etc.

After i tilt the phone to use the keybard to enter in info into fields such as wifi passwords, all fields with text show up as blank but after i close the tilt it all reappears again.

Not really a bug, but I was curious if using google maps, does it cost me data, even if i dont have a data plan because if i'm not mistaken if i use tomtom or other gps software i should see a blue light to indicate that gps is being used and not data?

Below is the device info that came installed with my tilt