yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] chetqwerty:
Recently vibrations have stopped on my LE2125AA. I'm trying to figure out if its hardware or software related. On boot, I get a small hepatic feedback, a very short vibration which is why I haven't just cracked it open and replaced the $3 vibrator. Can anyone remind me if the boot vibration is longer than a very quick soft vibrate please. I just can't recall what it's supposed to feel like. Also can't remember if there is a vibration on shut down. I'm trying to get to the old service screens where your able to run system tests but can't find ca code that works. I've installed the Magisk Engineering Mode enabler but there's not much info returned using the *#*#4636#*#* code. If anyone knows one that can get me to the hardware test screen that would be great too.

Thanks
[OnePlus 9 Pro] chetqwerty:
43 views and no one can help me out by describing the vibration they feel on boot?? Dang, I've answered much stupider questions for people! C'mon this will really help me out!
[OnePlus 9 Pro] Nimueh:
On boot the vibration is really short + weak, just a brief "bsst", but I don't think there is one on shutdown. Never really paid attention though, since I usually don't turn off the device but only reboot it. Plus I hate the haptic feedback anyway and turn it off wherever possible lol 😇

Oh and no idea about that engineering mode at all, never needed it.
[OnePlus 9 Pro] TNSMANI:
I checked and the vibration at boot is really short. On Power Off, it is much longer. The strength of both is normal when compared to other haptic events. I don't have much else to tell you.
[OnePlus 9 Pro] TNSMANI:
Exactly!:)
[OnePlus 9 Pro] chetqwerty:
Thanks you two I appreciate the replies, your comments are just what I needed to determine it's got to be software related. Short bzzzt on boot, no vibration on shutdown. Something gets screwed up after everything loads up, gotta be software. Safe mode doesn't get me vibration back either so good chance it's system related.

Thanks again!
[OnePlus 9 Pro] jfolive:
Some keyboards have their own haptic feedback settings, but have you also verified that haptic feedback is enabled in system settings > sounds & vibration > haptics and tones?
[OnePlus 9 Pro] chetqwerty:
Oh yeah way past that but thanks for the reply. I found a warning for an "illegal effect params" in the vibrator service so trying to figure out where that may lead.
[Touch Diamond, MDA Compact IV General] dervish666:
Orange are not all that likely to go poking around in the insides of the diamond to check every version is stock. I'd ring 154 and tell them the problem, don't mention that it has been flashed or tampered with at all. They will run you through a diagnostic session and probably sort out a replacement for the next day.

If you have an Orange official ROM and Spl you'll be fine, Orange get thousands of returns daily, they are not going to check each and every one for the correct software versions, as long as it has the right numbers somewhere it'll be fine, and I think you have done more than enough to cover that.

If you have any problems PM me.
[Touch Diamond, MDA Compact IV General] evilsheep:
Thanks for your reply. I called Orange earlier, played a little dumb, and they did just as you said. Although the only diagnostic they recommended was to perform a soft reset (no hard reset, no clearing storage - just soft reset).

I got the feeling they've had quite a few returns, as they didn't ask any questions about whether the handset had been damaged/exposed to extreme temperatures/any other potential damage-causing scenarios. They're sending out a replacement handset shell (handset only, minus battery & SIM) tomorrow morning to swap with my faulty one. I've had issues with Orange customer service in the past, so I am pleasantly staggeringly surprised by this unusually competent level of help from them.

Hopefully I'm not counting my chickens on this one, and the new handset works and no questions are asked about any flashing of the old one ...

Thanks again,

:)
[Touch Diamond, MDA Compact IV General] Shaady:
Most phone companies just do a straight swap on the door, so im guessing thats what they are giving you?

If thats the case, then i highly doubt they are going to bother chasing you up on it even if they ever notice. They must have loads of these things coming in everyday, they will probably just ship it back to htc, who might notice, but by then i doubt they will know where its come from.

Though just giving you a new shell seems a bit stingy!
[Touch Diamond, MDA Compact IV General] evilsheep:
New shell arrived at 9am this morning (I may have to temporarily rethink my opinions of Orange CS ...). The only part exchanged was the phone part - I even kept my old batter cover. I suppose it is slightly stingy, but also more convenient. The replacement is clearly a reconditioned model, which is fine with me. The reason I think it's reconditioned is that the screws inside the phone show signs of having been unscrewed, and there are minute marks around the screen which would indicate it's been removed, and probably replaced. The screen also feels different somehow - as if there are two membranes connecting when applying pressure with the stylus. Not an unpleasant sensation at all though.

So far, it's working well. Super fast (running Orange's latest ROM & Radio: 1.93.405.1WWE & 1.00.25.05) with an immediate response, so I may resist tampering with software for at least a day or two! Apart from installing MSVC - Cyberon Voice Dialler is a total waste of time in my eyes.

Fingers crossed, this handset will last the distance, and there'll be no flashing repercussions from Orange.

Cheers!
[Touch Diamond, MDA Compact IV General] -PiLoT-:
orange wont check the internal structure of th device

they once tried to tell me the omnia was unable to be debranded from there firmware it took me 10 minutes to do
[Touch Diamond, MDA Compact IV General] kaos_king:
I sent my orange diamond back after the backlight stayed permanently on.

I was worried about them checking, but i still left the hard spl on and the rom - they didnt bother checking
[Touch Diamond, MDA Compact IV General] kamikserg:
would anyone tell me if i send the faulty orange phone to orange service without proof of purchase. Would they check phone or repair it without proof of purchase?

Appreciated for your replies
[Touch Diamond, MDA Compact IV General] Kevlah:
I've never had to provide Orange with proof of purchase when returning a phone to them but every time I did I had Orange Insurance on it which was bought when I bought the phone so they would have the details on the system.

I doubt Orange check these devices when returned. I sent a phone back for a scratch on the screen, they asked me if it affected normal operation to which I replied "Yes". They said "Are you sure because if we exchange and find the device still works you will be charged for it". I said "Yes", arranged the return and promptly tried to damage the screen further to stop it working. I gouged a crater into the screen without it failing and just had to let it go and hope nothing happened. I've never heard back from them and it's been at least 1 year. :)
[Touch Diamond, MDA Compact IV General] zulu7:
i had this issue as well. i have tried everything then i have found that somone mentoned about AZTOR V7 rom. i had it once i remember. since my diamond came back from repair with comment: unauthorised software/unlock voids warranty i have decided to have last try.

AZTOR V7 rom solved the issue for me!!!!!!!!!!

hail AZ
[Xiaomi Poco F1 Questions & Answers] maxsteelvishak:
Hello,

I have tried crdroid and Evox custom roms, but they both trigger init.rc modification in momo and the problem is due to this i cannot run some banking apps, is there a fix or any other customer rom that avoids this.

Thank you.

Max
[Samsung Galaxy S9  Questions & Answers] Nhicolas_:
Hey guys.

I would like to ask for help to solve some problems on my device, I'm trying to flash the stock rom via Odin, but it keeps giving a "Serial COM port" error, I've done everything, reinstalled the drivers, updated Odin to the latest and I can't solve itView attachment 6048149
[Samsung Galaxy S9  Questions & Answers] ze7zez:
A number of errors described perfectly on the Internet, for example: wrong version of Odin, wrong USB cable, incompatibility of the USB port on the PC with the USB port on the phone, no device driver installed, etc.
[Galaxy S 5 Q&A, Help & Troubleshooting] cflyte:
Hi all. Just came across this site via Youtube.

I have a Samsung S5.

I am a complete novice when it comes to tech stuff.

Is it complicated to install Lineage OS for it?

Which version do I need? The phone is an S5 SM900i running android 6.1.

Thank you
[Galaxy S 5 Q&A, Help & Troubleshooting] cflyte:
Thank you

Kind regards
[Android Q&A, Help & Troubleshooting] Starshipv2:
My phone is Samsung Galaxy S8 with custom ROM. Kernel Version 4.4.248-HadesKernel-v2.0-dreamlte, Build nr. HadesRom-Q-OneUI_V1.0FTK3

I have added a second battery 4500mAh in paralel with de original one (now the total is 7500mAh). So now i have to change the battery capacity in root/sys/class//power_supply/battery/charge_full but does not work with root file manager. Phone has TWRP and is Rooted (Magisk).

How can i edit "charge_full" file? Thank you.
[Android Q&A, Help & Troubleshooting] Renate:
You can't. That's in /sys and probably read-only.

Is it 3000 or 0xbb8 currently?

The number that's there probably comes from the dtb.

Pull your dtb and post it. Is it a partition by itself or in the boot image?
[Android Q&A, Help & Troubleshooting] Starshipv2:
Number from Charge_full is 3000000.

Sorry but i dont know what is "dtb".

This guy from youtube changed battery capacity in Charge_full file, but does not explain how.
[Android Q&A, Help & Troubleshooting] Renate:
Post your Magisk'ed boot image.
[Android Q&A, Help & Troubleshooting] Starshipv2:
Easyupload.io - Upload Files and Share Them Easily

Uplaod files easily and share them with your friends and colleagues. File upload solution for everyone. Upload big files and get a link to share effortlesly.

easyupload.io
[Android Q&A, Help & Troubleshooting] Renate:
I can't be bothered to work with lz4 files.
[Android Q&A, Help & Troubleshooting] Starshipv2:
Boot.img is ok? Should i convert it to someting alse? Thank you.

Easyupload.io - Upload Files and Share Them Easily

Uplaod files easily and share them with your friends and colleagues. File upload solution for everyone. Upload big files and get a link to share effortlesly.

easyupload.io
[Android Q&A, Help & Troubleshooting] Renate:
Sigh. Your kernel does not have the dtb in it.

C:\>adb shell
$ su
# dd if=/dev/block/by-name/dtb of=/sdcard/dtb
^D
C:\>adb pull /sdcard/dtb
[Android Q&A, Help & Troubleshooting] Starshipv2:
So, battery capacity is provided by the kernel. Kernel is located in Boot.img (this is my understanding of what i read on internet). I umpacket Boot.img and i get multiple files, the bigest file is boot.img-kernel. I opened it with Notepad++ but i get wierd text.

What app do i need to open this file?
[Android Q&A, Help & Troubleshooting] Renate:
Technically, everything is provided by the kernel, but that's not where the number comes from.

I don't know what you're using to split the boot image, but it seems pretty stupid.

(Notepad++, while a fine editor, is not useful on binary files.)

I had asked you about /dev/block/by-name/dtb

Do you have a dtb partition?
[Android Q&A, Help & Troubleshooting] Renate:
I didn't ask you about mounts. dtbs are not filesystems, so they are not mounted.

$ cd /dev/block/by-name
$ ls -l *dtb*
$ su
# dd if=dtb of=/sdcard/dtb // or dtb_a or dtb_b
^D
C:\>adb pull /sdcard/dtb
[Android Q&A, Help & Troubleshooting] Starshipv2:
Did i mention that i am a noob at this? :giggle:

lhc@DESKTOP-0CAGA3V:~$ adb shell
crownlte:/ $ $ cd /dev/block/by-name
/system/bin/sh: $: inaccessible or not found
127|crownlte:/ $ cd /dev/block/by-name
crownlte:/dev/block/by-name $ ls -l *dtb*
ls: *dtb*: No such file or directory
[Android Q&A, Help & Troubleshooting] Renate:
Sorry. I got all confused with these images.

The first one had no DTB in the image, so it must be in a partition.

This last one does have the DTB in the image. (I don't know how I didn't see it this morning.)

Are you running on this G8441-47.1.A.16.20.img right now?

Does this work for you?

C:\>adb shell
$ cat /sys/class/power_supply/battery/uevent

That "split.png" you posted of the CRB: was that really G8441-47.1.A.16.20.img?
[Android Q&A, Help & Troubleshooting] Starshipv2:
Nothing to be sorry about, because i f***et up:(. There is no point explaining how i manage to f*** up, but i did and i am truly sorry.🥺

The boot.img i gave you is from StockRom (Android 9), i give you that one because i cant find boot.img from HadesRom.

This split.png is from Lineage 18 Rom boot.img (Android 11). Its not even for my phone.🤯

I flashet Lineage 20 Rom (Android 13) on my phone this morning because i cant find boot.img for HadesRom (Android 10).

This is the Lineage 20 Boot.img

PS C:\Users\Space\Downloads\platform-tools_r34.0.5-windows\platform-tools> ./adb shell
dreamlte:/ $ cat /sys/class/power_supply/battery/uevent
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_STATUS=Charging
POWER_SUPPLY_CHARGE_TYPE=Fast
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_ONLINE=4
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_VOLTAGE_NOW=4058000
POWER_SUPPLY_VOLTAGE_AVG=4056000
POWER_SUPPLY_CURRENT_NOW=358
POWER_SUPPLY_CURRENT_AVG=424
POWER_SUPPLY_CHARGE_FULL=3000000
POWER_SUPPLY_CHARGE_NOW=1
POWER_SUPPLY_CAPACITY=39
POWER_SUPPLY_TEMP=296
POWER_SUPPLY_TEMP_AMBIENT=296
POWER_SUPPLY_TIME_TO_FULL_NOW=12944
POWER_SUPPLY_CHARGE_COUNTER_SHADOW=4
POWER_SUPPLY_CHARGE_OTG_CONTROL=16
POWER_SUPPLY_CHARGE_UNO_CONTROL=17
POWER_SUPPLY_CHARGE_COUNTER=1171965
dreamlte:/ $
PS C:\Users\Space\Downloads\platform-tools_r34.0.5-windows\platform-tools>
[Android Q&A, Help & Troubleshooting] Renate:
Well, I wanted to get my bearings which direction is up.

So, G8441-47.1.A.16.20.img is the only thing we're talking about?

And that's the one you were running when you did the cat /sys/class/power_supply/battery/uevent?

The "dtb" in that has four dtbs in it and I have to know which one is the real one to know which one to patch.
[Android Q&A, Help & Troubleshooting] Starshipv2:
Sorry but i am really confused about this "G8441-47.1.A.16.20.img", there is no such file on my computer or phone.

This is the boot.img i extracted from Lineage 20 Rom, and currently running on. I run this "cat /sys/class/power_supply/battery/uevent" using the curent Lineage 20 Rom.
[Android Q&A, Help & Troubleshooting] Renate:
Sorry, then I'm mixing everything up. When I try to help multiple people sometimes my brain gets crosstalk.

(I finally figured which thread that G8441 came from.)

So I downloaded your boot.img and there is no dtb packed in it.

All modern systems use dtbs, so where is it?

Did you do a ls -l /dev/block/by-name on this image?
[Android Q&A, Help & Troubleshooting] Starshipv2:
PS C:\Users\Space\Downloads\platform-tools_r34.0.5-windows\platform-tools> ./adb shell
dreamlte:/ $ ls -l /dev/block/by-name
total 0
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 BOOT -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 BOTA1 -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 BOTA2 -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 CACHE -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 CP_DEBUG -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 DNT -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 HIDDEN -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 KEYREFUGE -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 MISC -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 NA -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 NAD_FW -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 NAD_REFER -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 OMR -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 PERSISTENT -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 RADIO -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 RECOVERY -> /dev/block/sda8
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 STEADY -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 SYSTEM -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 TOMBSTONES -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 2023-12-31 11:19 UP_PARAM -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 2023-12-31 11:19 USERDATA -> /dev/block/sda24
lrwxrwxrwx 1 root root 14 2023-12-31 11:19 sda -> /dev/block/sda
lrwxrwxrwx 1 root root 14 2023-12-31 11:19 sdb -> /dev/block/sdb
lrwxrwxrwx 1 root root 14 2023-12-31 11:19 sdc -> /dev/block/sdc
lrwxrwxrwx 1 root root 14 2023-12-31 11:19 sdd -> /dev/block/sdd
dreamlte:/ $
[Android Q&A, Help & Troubleshooting] Renate:
Nope. Not there.

I finally figured it out.

What the heck knucklehead built that image with version 0?

It should be version 2 if you want to put dtb at the end.

Ok, I'll let you do the honors.

Take your boot.img and make a copy.

C:\>modfile copy.img 1ea0040 00 00 1d 4c
[01ea0040] 00 00 0b b8 => 00 00 1d 4c

Now go to fastboot and try this out before flashing it.

C:\>fastboot boot copy.img

Then do as above and check that:

POWER_SUPPLY_CHARGE_FULL=7500000

modfile is here
[Android Q&A, Help & Troubleshooting] Starshipv2:
Comand above did not work with "C:\>" i used "./" and it worked 😁

./modfile copy.img 1ea0040 00 00 1d 4c

My phone does not have fastboot. So i just flashed "copy.img" and its all good. It worked. Thank you 🤗

127|dreamlte:/ $ cat sys/class//power_supply/battery/charge_full
7500000
[Android Q&A, Help & Troubleshooting] Renate:
Short instructions for somebody who wants to duplicate this:

Get your boot image

Extract the DTB (maybe using ImgUtil.exe)

Dump a listing of the DTB (maybe using DtbView.exe)

Search for fuel_gauge or fg_ for "capacity" or similar

Get the address for the parameter block

Hex view the DTB to get the address where the actual hex value is

Add this offset to the offset in the boot image where you found the DTB.

Make a copy of your boot image

Modify the file using the combined offsets and your new value
[Android Q&A, Help & Troubleshooting] aqvyx:
Sorry for necro bumping, Im trying to do the same I can use my 5000mah battery in the Poco F3, but I cant seem to find any hint of fuel_gauge or battery capacity in my kernels dtb. Anyone know what I could do?

I tried modifying the sys charge full file through a kernelsu module but that simply doesnt work and still gives me the old value. Im attaching a file of my dtb.

Had to rename the dtb to dtb.img so XDA lets me upload
[Android Q&A, Help & Troubleshooting] Renate:
Sorry, I missed this.

I don't see anything off-hand.

Is there a dtbo somewhere?
[Samsung Galaxy A54 5G] durjoyPoseidon:
I bought samsung a54 mobile in USA. Now i am in Bangladesh but mobile carrier locked by tracfone.

Any solution to unlock this??
[Samsung Galaxy A54 5G] h0miemaru:
being a USA galaxy A54 (a546u), you can't unlock the bootloader, but you can still flash another stock USA rom, such as the A546U1, which is a carrier unlocked rom. I flashed the A546U1 rom on a phone that was originally A546U.

But since you're in Bangladesh, you probably won't be using a USA-based service provider. Hope some of that is insightful for you.
[Touch Diamond, MDA Compact IV Themes and Apps] bmancell:
How can I limit the amount of apps in the recent area of the start menu?

I tried searching, couldn't find anything.
[Touch Diamond, MDA Compact IV Themes and Apps] jolas:
If you move all shortcuts from '/windows/start menu/programs' into another subdirectory, e.g. '/windows/start menu/main', then you will have no list with recent used apps.

I know this is not exactly what you want, but maybe you' ll find it useful:)
[Xiaomi Mi A1 Questions & Answers] Gibbron1:
Hello I was running PixelExperience on my Mi A1 (tissot) and wanted to tired Nusantra OS so I tried to install it on my phone. I tried to format but it didn't work as the error is specified in the title. So i did a mistake and installed it without wiping and formatting and even ****ed it up more. So i need help of you guys

EDIT - I think everything is encrypted leaving my SD card. So how do I decrypt it? There's no OS currently installed on my phone.
[OnePlus Nord 2 5G] thambu28:
how to use sp flash tool on one plus nord 2 (a.11 software). my Nord 2 doesn't turn on anymore. any guidance is appreciated
[OnePlus Nord 2 5G] Klangerzeuger:
What did you mean with doesn't turn on anymore?

Did you try Volume - and powerbutton to get into fastboot? If this work, you can wipe and reboot via terminal.

Did you try MTK Tool and Volume - & +? If this work, you can flash an Backup.
[OnePlus Nord 2 5G] thambu28:
i tried fastboot but it doesnt work

mtk tool returns with a handshake error but im on a.20 software
[OnePlus Nord 2 5G] jis251:
HI. SP Falsh Tool (SP_Flash_Tool_v5.2316_Win) You need scatter file. Link below.

https://xdaforums.com/attachments/mt6893_android_scatter-txt.5439391/

And you need authentication file but I have no idea where to get it. I hope you can find it or if someone here has it or knows where to get it. That would be helpful.

Good luck
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fuenbry:
my kraiser is bricked i think?? i already hard spld it and its 3.56 when i try to update a rom it just goes to the lading menu and stays at zero then gives me an error
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Cal-El:
Are you using XP or Vista! Have you tried going into the bootloader then flashing! Most importent, have you read the flashing for new users section? I recomend you read that all the way through! It should have answers for everything!:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fuenbry:
im using vista its the first time i have flashed on vista i know how to flash on xp with my wing but never my kraiser on vista..im confused
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Cal-El:
Its ok, I have Vista! Your hard spl 3.56 right? Did you Cid Unlock or just hard spl! Because you need to be CID unlocked to flash on kaisers! I used to see you alot on the wing threads, thats where I started! Kaisers are alot different to flash than wings!:)

P.S. the mods will most likely close this thread! PM me if you need to!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
You don't need CID unlock, the Kaiser Hard SPL's have the CID check removed.

If you have flashed HardSPL, just re-flash the ROM from the bootloader.

A little more info would help, what HardSPL (if any), ROM, radio.

Ta

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fuenbry:
no i didnt do that how would i do that no since its just on the tricolor screen showing the spl
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
Have a look at my guide here on getting out of the tri-color screen?

What is the SPL version?

Ta

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fuenbry:
how do i do that cause im not sure if i have ever used bootloader... lol.. i have tried to re-flash it does everything correctly but when it gets to that screen where it says it will take approx 10 minutes for operation to complete, the status doesn't move from zero.. i have also tried the other flashing method by using the micro sd card. i format it to Fat32 i copy the rom to the sd card and when i put it on the phone and reset it all it does is say "Loading..." it doesnt do anything else
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Cal-El:
Are you stuck at the rainbow (bootloader) screen or can you soft reset your phone!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fuenbry:
the spl is 3.56