yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] loserp3:
Hello,

Today i bought the kaiser and wanted to rom flash it to 6.1

My plan is to flash it to L26KDTLB6 (http://xdaforums.com/showthread.php?p=2574491&posted=1#post2574491) i've followed the instructions here : http://xdaforums.com/showpost.php?p=2261226&postcount=2

and the flash was in progress but cancelled after 14% due to communication problems (????)... now when i resettred my kaiser i see this weird red green blue and white screen.

I am terribly worried i might have ruined my kaiser even before really using it.

I am begging you for help.. i would appreciate any kind of help from you guys.

Thank you so much

MIke.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] billcoff:
Wow! Sounds like you are in deep doodoo. I had almost an identical problem last night trying to flash ROMeOS 4.7. I went and read the stickies at the top of this forum and was back up running in no time.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] scotchua:
Sounds like you did not HardSPL. The tri color screen you are seeing is called bootloader. It's not as scary as it might seem at first. When you connect yoru device to your computer does it still show the letters "USB" at the bottom? If so, try flashing the stock rom for your device and see if that will fix your problem. After that be sure to make sure you've properly hardspl'd your device before flashing anything else.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] -888-:
HOW COME YOU KNOW HOW TO WRITE BUT YOU CAN'T READ?

geez...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] TasoM:
I had the same problem once. I remember I solved it that I first flashed it back to the OEM that came with it, and then flashed it again. It worked. Hard SPL and CID unlocker helped being that the phone was locked.

If you dont have OEM OS you can always find one here, just use the Search button.

Secondly, you have to follow the steps exactly as instructed because those are the only way to successful flashing. Are you sure that you didnt overlook one of the steps?

Pay special attentiton to the 2nd Q&A

and also other Q&A being that there are all the answers.

Happy flashing mate.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] loserp3:
Hello all,

I was able to revert back to hTC'S 6.1 rom...So everything was back to normal.

The thing is, i really want to make the kaiser look good with the d3d driver and the touchflo 3d, I'll give the http://xdaforums.com/show...=1#post2574491 rom one more shot this time ill use

SSPL-KAIS.exe (is that ok ?? will that prep my device for rom flashing ??? )

is there another cooked rom that has the touch flo 3d and the d3d drivers ???

appreciate your help

MIke.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] scotchua:
Do NOT flash another rom until you have hard spl'd your device. Make sure you check out the thread at the top of this forum, which you already sited once. You should also consider sim/security unlocking your device as well. You can ONLY use jumpspl to put hardspl on your device. Absolutely do not start flashing roms until you can enter bootloader and next to spl: see "hard spl" somewhere in the title.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] loserp3:
Hi

Ok, here's what i've done to prepare the device

1) i ran kaiser-HardSPL.exe and loaded the nbh that came with it

2) I copied SSPL-KAIS.exe to the kaiser and ran it

thats it... i didn't however see hard spl in the title.. i did see JUMPspl though
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
you are so making this too hard on yourself. Follow these directions to the letter and you'll be fine:

How to Install 3.2x.Hard SPL:

1. Plug the device into your PC

2. Copy Jump/Soft to your device. use JumpSPL If you have the "White Screen" issue, if you don't, you can use SSPL-KAIS.exe.

3. Take out your SD card & SIM Card.

4. Run Jump/Soft SPL on your device

5. Wait for the bootloader screen to appear and "USB" to show.

6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked

7. Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.

8. Run KaiserCustomRUU.exe and flash the SPL

If you have problems with the above process, try this:

1a. download the attached files

1b. pull out the battery and reinsert it (this step *is* important)

1c. connect your PC to phone with a USB cable

2. REMOVE SIM and SD CARDS !!

3. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe

4. after a few seconds "USB" appears on the phone display

5. unplug and replug the usb cable

6. deselect "Allow USB connections" in Activesync connection settings

7. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)

Notes:

With the JumpSPL you should *not* flash radio roms, OS roms or full roms. The JumpSPL is only needed to flash a HardSPL (or SPL)

the link to the thread in which this came from is here:

http://xdaforums.com/showthread.php?t=396922

Having just redone this this morning to revert back to 3.29, I can confirm that it works.

In the future, please don't start a thread for this type of porblem. We all starte out by reading. I've been a part of this forum for 3 years and learned all I have from just reading and asking questions that could not otherwise be answered.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] scotchua:
you did not read the instructions correctly. Try reading them again.

It says:

How to Install 3.2x.Hard SPL:

1. Plug the device into your PC

2. Copy Jump/Soft to your device. use JumpSPL If you have the "White Screen" issue, if you don't, you can use SSPL-KAIS.exe.

3. Take out your SD card & SIM Card.

4. Run Jump/Soft SPL on your device

5. Wait for the bootloader screen to appear and "USB" to show.

6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked

7. Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.

8. Run KaiserCustomRUU.exe and flash the SPL

You are stopping at step 5. Perform steps 6, 7, & 8. After that time you can soft reset the device while holding down the camera button (that will take you to the tri colored bootloader screen) and it will say "hardspl" if you have done it correctly.

If you don't read more closely you WILL break your phone and nobody here will be able to help you. These procedures are easy enough to follow if you take your time and read. I only say this to save you a great deal of frustration when your phone dies later.

Also, remember in the future that all the information you are seeking is readily available if you look for it. Dont' expect someone to GIVE you the answer, and please please please....post your questions in a thread that is already around rather than starting a new one!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wireless_one:
@ Scothua

like the way you think . . . :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] loserp3:
scotchua,

Thank you for your assistance. i've finally upgraded my rom.

thank you all.
[Huawei Y3 Guides, News, & Discussion] applesnake:
Hello World!

I have used Huawei Lua U-22 for somedays & flashed some CR there. I have used 3 rom from this post - Custom Roms For Huawei Y3II. Please kindly go to that post to get the download links.

Here, I am only posting some screenshots of those rom because main post didn't include them. Hope you'll 'njoy! :)

Aosp 5.1​

Android Open Source Project - AOSP. Another clean and responsive rom for Y3 Lua U-22. The only downside of this rom I think is the ringtone section. Existing ringtones are not that good. Consider using from other source.

I can't remember, but the rom is probably not pre-rooted. I have flashed magisk to gain root access.

View attachment 5270503View attachment 5270501View attachment 5270505View attachment 5270507View attachment 5270509View attachment 5270513View attachment 5270515View attachment 5270511View attachment 5270517View attachment 5270519View attachment 5270521View attachment 5270523View attachment 5270525

Thank you ❤
[Huawei Y3 Guides, News, & Discussion] asiricot:
How to install the OS? Can you direct me to any thread
[Huawei Y3 Guides, News, & Discussion] applesnake:
Hi,

First of all, I am really sorry I didn't see you commented. Too late :/

Anyway, unfortunately I couldn't find any thread which will guide you how to install the rom. And there is a reason for this - installing a rom is self explanatory, and very easy. You'll need a custom recovery like TWRP. Then keep the rom file in your phone storage, boot the device in recovery mode, select the rom, & press flash. After finishing the installation, reboot device, you're done!

Here are some video for you to understand the situation:

Before that, you have to root your device of course, and unlock the bootloader. Here's a video for that too, if you didn't unlock your bootloader already:

BTW, don't try to install any rom that is not made for Huawei Y3 Lua U22. It may permanently brick your device. I tried to cross port a rom & flash it myself, and guess what? My device is no more :')

Have a good day! 🎉
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Tenshi2112:
I. About the project:

In terms of "repartition", it is basically re-editing the size of partitions on the hard drive, the same way you can resize partitions on Windows or Linux, but on Android, it's more difficult because of the partition information. the area is stored at /dev/block/by-name, /dev/block/bootdevice/by-name or /dev/block/mmcblk0p48, making it difficult to edit.

So I really need your help to can possibly know the location of partitions that needs to be resized.

II. Why we need to resize the partitions? Does it useful?

Of course yes, because if there is a lot of space for important partitions, it will be easy for ROM builders or porters to port many different ROMs without fear of insufficient partitioning.

III. The direction of the project

The direction of the project is a community project, I need you to help otherwise we will enjoy a lot of benefits on our phones, my goal is to be able to help something small for the community Redmi Note 4/4x

1. First Prepare for this Project​

Because this is really difficult and doing it wrong could result in the device being damaged or even turning it into a piece of paper. So I really wrote code very carefully to avoid all possible mistakes​

​

2. What I need now​

Nothing is easy, I would really thank you if you could provide the location (Ex: /dev/block/bootdevice/by-name/xxx) of the necessary partitions, here is my request table (I will check the location you send soon as possible to can decrease the time of making script).​

​

Partition​

Location​

Correct?​

System partition​

/dev/block/mmcblk0​

100%​

Vendor partition​

/dev/block/mmcblk0​

100%​

Cache partition​

/dev/block/mmcblk0​

100%​

Cust partition​

/dev/block/mmcblk0​

100%​

Userdata partition​

/dev/block/mmcblk0​

100%​

3. Does it dangerous?​

Repartition is quite risky because if the incorrect processes or partitions can turn your phone doesn't work anymore, now it's not as risky as it used to be, but repartitioning is purely do you really need it or not.​

​

​

IV. Final words

Whether you can help me or not is entirely up to you, you can just keep an eye on this thread and I'll try to find the right partition as quickly as possible, but if you can help me it would be A big appreciation for this project, I would appreciate you if you could do something small for me and this community.
[XDA App Bugs and Requests] bitpushr:
When you get a notification that you have been mentioned or a thread you are watching has been replied to, if you click on the notification the app opens on the default screen and not in the thread/post that is mentioned.

Clicking on the notifcation should bring you directly to the thread notified about.
[XDA App Bugs and Requests] bitpushr:
Strangely enough, after I cleaned all data and reset app, the notification I got for this thread brought me straight to the thread. I'll continue to test but wondering if others have this issue?
[XDA App Bugs and Requests] orb3000:
Hola,

Im having same issue with notifications not opening properly plus always I have 1 non existent notification that always there until i go and mark all read.

Cheers team!
[XDA App Bugs and Requests] IamTheBRAVE:
Notifications have been inconsistent for me. If the app is already open it works. But pressing it from the android pull-down menu, the app gets stuck on home tab.
[XDA App Bugs and Requests] woodman:
I face this issue as well but it is happening randomly on my end, I don't have the pattern yet. 😕
[XDA App Bugs and Requests] svetius:
This is a known issue that will be fixed in an upcoming version. Thanks.
[XDA App Bugs and Requests] svetius:
In the latest versions, this is no longer an issue.
[XDA App Bugs and Requests] It_ler:
For me and some other users this issue it back.

See xda-app-beta channel on the xda discord server.
[Huawei Y3 ROMs, Kernels, Recoveries, & Other Devel] applesnake:
Hello World!

I have used Huawei Lua U-22 for somedays & flashed some CR there. I have used 3 rom from this post - Custom Roms For Huawei Y3II. Please kindly go to that post to get the download links.

Here, I am only posting some screenshots of those rom because main post didn't include them. Hope you'll 'njoy! :)

S7 Rom​

Samsung S7 - you may like it, or may not. But this rom is pretty good tbh. Especially it's battery life. I got a long lasting battery backup from this rom(maybe, can't remember). Some problem is:

Reboots every time when you disconnect the phone from PC usb

When the phone is switched off, then if you plug into charge, there is a wired charging logo. You can understand it though, but it's not expected. I believe you can change the charging logo from the root folder, but I didn't dig for it that much.

The rom is not pre-rooted. I have installed magisk to gain root access.

View attachment 5270531View attachment 5270533View attachment 5270535View attachment 5270537View attachment 5270539View attachment 5270541View attachment 5270543View attachment 5270545View attachment 5270547View attachment 5270551View attachment 5270553View attachment 5270555View attachment 5270557View attachment 5270559View attachment 5270561

Thank you ❤
[OPPO Find X3 Pro] pete23:
Hi,

has anyone tried to get 120Hz in some Games?

I tried WOT Blitz and Wild Rift but I can only choose 60Hz in the Game Options..

In the Phone Settings I have the 120Hz activated.

Has someone a hint what im doing wrong here?
[OPPO Find X3 Pro] Garunix:
Hi

ColorOS block 120Hz in games

Stupid manufacturer
[OPPO Find X3 Pro] deraiz12:
Hi, have you solved your problem ?
[OPPO Find X3 Pro] Thorgoth:
have the phone about 1 day and even in games like Pokemon Go the framerate seems choppy at best...really dissapointed ....
[OPPO Find X3 Pro] Thorgoth:
please delete , browser stuck :P
[Touch Diamond, MDA Compact IV Themes and Apps] El_Mariachi:
Hi guys, I want to start developing for PPC, I do quite a bit of programming at work with a language similar to C++, but I'm still an amateur.

What I want to do is create some apps, probably using the GSensor, can anyone point me in the right direction??
[Touch Diamond, MDA Compact IV Themes and Apps] 3asaleya:
nice idea !!!!
[Touch Diamond, MDA Compact IV Themes and Apps] hdzsound:
check the Wiki section of the XDA website
[LeEco Le Pro3 Questions & Answers] bareckxda:
Hi there,

I just got my X720 shipped from China and try to flash EONS/openpilot on it,

I have done the following:

Have ADB/Fasboot tools on your computer

Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device

Make sure adb can see your device when you run "adb devices" --> will show my device

Run "adb reboot bootloader" --> reboot into fastboot

Run "fastboot devices" to make sure you see your device --> nothing show here!!

I had also try the "All in one tool" but get same result.

Any advice?
[General Topics] vkrf88:
Please Support anyone after new software update not able to lock LTE band in MediaTek Device even MTK engineering mode is not working. This code is also not working *#*#3646633#*#*

Please support anyone and suggest some new way to lock LTE band without Root
[General Topics] lexloc:
same problem. seems there's no solution to this
[Android Head-Units] explorer_200:
I had the Google account login issues that many had in here, after contacting Joying they sent me a link to two changed files to copy onto their original firmware update. I updated with this new "firmware" and my Google account worked.

Then 2 days later (March 16th 2021) my Google account was compromised for the first time in 15 years. I only use this password for my Google account so I don't know how it was hacked but the Google Admin audit logs say the hacker just input my password.

They opened up a Google Adwords account and started selling fortnight ads, then attempted to get into my brokerage account, then logged into a dormant Etsy account and tried to do something with Square before I caught on (40min total in my account). They were quickly deleting any account change emails that came in so I wouldn't receive notices of changes.

I am highly suspicious of this new update to my head unit. The timing is spot on, and I haven't used my Google account anywhere other than my Pixel phones, Nvidia Shield, Laptop and this Joying unit.

I am very concerned now about the security of this device. I also don't understand the claim by Joying that "Google updated their servers" and that's why their firmware wasn't working with Google accounts. Smells very fishy to me, and I hope somebody that knows more about device security can help figure this out. I still have copies of the update that they sent me, but I will not be using this brand new head unit anymore with my Google Account.

I posted this thread because I have seen other comments about Google accounts being hacked and concerns about third party device security and thought it would be best to consolidate them here in one thread rather to take other threads on a tangent.
[Android Head-Units] gamer765:
Just be aware that Joying in particular didn't have anything to do with it, they are just resellers and pass on software given to them by the actual manufacturer of the hardware, FYT. Also be aware, that data breaches are happening very often nowadays so that is also a possibility. I'm not defending the manufacturer in any way, but there's too many variables in order to single out the headunit itself. You did mention that you use this google account on your phone as well. It could be that you installed an app on your phone that stole your account information as well. Also a new "virus" has been discovered that disguises itself as a system update that can steal your info. Info here: https://www.androidpolice.com/2021/...retends-to-be-a-system-update-for-your-phone/

Only way to know for sure if it was the headunit itself is to use a new dummy Google account on it and see if it gets taken over as well. Also, I don't see the purpose of needing to login to Google on these devices anyways since we're not using them like phones and, me in particular, I don't consume streaming media on it so i don't give it network access at all. These new units have spotty GPS reception at best and sometimes i find myself forced to use Android Auto anyways so the only streaming media consumed is straight from my phone.

What I can recommend you do is install a firewall app on your headunit and monitor where it tries to connect and determine if it needs to access it or not. To put yourself at ease, I would change your password and enable 2 step authentication on your account.

Let us know if you decide to sideload a firewall app and post your results. With that info, we can take this concern up to Joying/Teyes/etc and have them press their supplier for information. I can assure you that with the proper evidence, the resellers will put some effort into fixing this wrongdoing, since they wouldn't want to tarnish their reputation and possibly lose out on some sales.
[Android Head-Units] 6KayZee9:
I was also hacked in mid March soon after installing a joying unit and connecting to my google account. The hacker opened a google ads account and used a credit card associated with my google account to charge 260 dollars to my visa. They would have charged more but my limit on the card is low for just this reason. Visa had to cancel my card and send me a new one. I never even connected the hack in my mind to the joying head unit until explorer_200 happened to post his experience, but this seems like far to much of a coincidence given that we both have had the same experience at the same time and all we have in common is the joying unit.

I agree that it may not be something joying knows about, but its probably a good idea to see how many have been affected by this hack. For now I will be setting up a locked down google account just for the joying box and my head unit will only be connected to apps that are no real risk to my passwords and personal data.

I need to login to google to use voice commands and google assistant as well.
[Android Head-Units] ludditefornow:
Could you please link to these other comments. Right now there is just your say so which is a sample size of one. Not doubting what you are saying, but correlation is not necessarily causation.
[Android Head-Units] ludditefornow:
That is flawed logic.

Allow me to use similar thinking in another way.

I notice that everytime I go outside when it is raining, there are people with umbrellas. I deduct that it is too much of a coincidence to see people with umbrellas when it is raining to think they are not linked. I don't see these same people carrying umbrellas when it is not raining. I can only conclude that the umbrellas are causing the rain.

You say that you and one other have the same head unit and have been hacked therefore it is the headunit's fault. DO a survey on how many people with Samsung phones were hacked yesterday and get back to me to let me know if the number was greater than two.

We can then move on from there.
[Android Head-Units] blackhawk:
Once bitten, twice shy... learn or get burned.

If you had a secure password that you managed well until 2 days ago that should narrow down your list of suspects substantially.

Time to take out the trash...

Results are all that matter; take out anything that might have been involved. The napalm method.

Overkill yes, but it's effective.

Breaching your Google account is completely unacceptable and I go nuts on anything/one that was potentially involved.
[Android Head-Units] marchnz:
If you're not using MFA/2FA on your account(s) expect it be a matter of time until your account(s) be compromised again.

The joying update is what I would call purely coincidence and post hoc (Post hoc ergo propter hoc.)
[Android Head-Units] gamer765:
Exactly this, without hard evidence that the Joying/Teyes/etc update is the cause of your Google account getting hacked, this is all pure coincidence. So far I'm aware of only 2 reports of accounts getting hacked, @explorer_200 and @6KayZee9. I've been lurking "the other" forum and i haven't seen any reports there either. Get some evidence to back up your claims and then start pointing fingers and have fyt (the software comes from them) be held accountable.
[Android Head-Units] blackhawk:
It's not so much as proving anything as it is plugging the most probably source(s) of the leak to prevent it from ever happening again for the user.

If that means never using the software even the hardware, it's a small price to pay.

An OS reload may also be good idea at this point on all potentially infected devices and another password reset. Go nuts... this could get real messy if it's in the data drive and gets into the backups.

The perp may only target high value targets and leave the smaller fish be giving the illusion the site, software or whatever is safe.