yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] culleyps:
Tri-Color multiple flashes from SD

Hi everyone.

I have been flashing for about a yr now and have never, ever had a problem until now. I followed all the instruction to a tee in this thread and I am still stuck at the Tri-Color with Serial/USB showing at the bottom. The rest is as follows:

KAIS130 MFG

SPL-1.0.oliPof

CPLD-8

Details of what got me here:

Flash Dutty's latest ROM June 14th I believe. Anyway working fine but needed to up SPL for WM6.1. Started to go through the process of flashing the the upgrade to HARD SPL 3.29 and that is when some of the trouble started. After that, my PC would not recognize the device saying it had malfunctioned. Tried this on several other machines running XP and Vista, smae thing. Started to work on that issue but got caught up with work and just synced w/bluetooth. Btw the I never got the SPL to take.

So the phone is working fine just the occasional screen freeze. Then I receive a call, call ends, phone goes to partial white screen but still shows graphics at the bottom for received calls, missed calls, etc.

And so I am here.......when the phone comes on and I hold down power/camera keys, tri-color shows then 'No Image' msg flashes then tri-color. I have tried flashing SPL 3.29, will not take. Goes through the process, says it worked but soft reset takes place I end up at the tri-color again. Same thing happens when flashing a ROM image. I have tried WM 6.1s and WM 6, all cooked. I am having a hard time finding a 'Shipped' ROM that is a .nbh file.

Here are the details of my environment:

TyTN II

Vista 32

laptop w/vista 32

Work Laptop XP

3 dogs

Girlfriend

etc.

Anyone have any ideas and suggestions?

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] P1Tater:
Open up the .exe file of the "shipped" rom with winrar. There you will se an .nbh file. Just extract it and then run as normal.

However, in reading your comments, it seems as though you are trying to upgrade the SPL via flashing it with your SD card method. AFAIK it is not possible to flash an SPL via the SD method. If I misunderstood your comments, I apologize.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] culleyps:
P1Tater you read correctly I was trying to upgrade my SPL via SD card. Ok so now I know that is not possible. With the old SPL that is on there shouldn't a WM6 shipped ROM flash to the phone? For some reason it is not booting the image after it says is flashed it and update success.

Any ideas?

Thanks again.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jm373:
Thanks for the info.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bartimeus:
I am having trouble doing this I have been working all day and with ATW's help but still can't figure out why it won't work.

AT&T Tilt with 1 gig Sandisk micro SD card formatted Fat32, and 3.56 SPL, I have tried 2 different roms(L26 V9 and Garmin V1.2) I have double and triple checked to make sure that they were named KAISIMG.nbh and that they were in the root folder of my card. I have also checked to make sure that they weren't named KAISIMG.nbh.nbh like some other people noted theirs were. When I try to enter the bootloader it goes to tri-color then quickly flashes to bootloader but says "no image found" or something of the sort and then goes back to tri-color...I then soft reset and try again. I even flashed the old fashioned way to a new rom then tried this and it still didn't work. I did about 4 hard resets today.

My only theory could as to why this isn't working could be that it is because I am copying the files to my card while it is still in my phone, I don't have an SD card reader so I couldn't use that. I don't know why doing it this way would make the file unreadable....
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bartimeus:
no one?

bump
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] profjekyll:
Reverting to original SPL via microSD card

Can anyone tell me if it is possible to use the microSD card method to flash the SPL from H-SPL 1.56 to the original? Perhaps using S-SPL will detect the NBH in the same way the H-SPL does...

(I have a broked USB socket and need to return the phone to HTC)

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] schizo:
Might be valid. But I remember once I did copy the nbh through activesync, not via card reader for the reason that I was being sloppy and couldn't find my microsd card reader. But it worked nevertheless. Lately I've been very much sdcard flasher, thanks to this thread :D

Hey, just an idea, might worth a try. Try to reformat your microsd card to FAT32 on OTHER computer, if possible, WinXP one. And if also possible, use command prompt to do the formatting, instead of using explorer. Do Start -> Run -> Cmd. On the prompt, use command like this (change X: with your card reader drive letter):

Format X: /FS:FAT32

If still not working, try Rotohammer's way above (http://xdaforums.com/showpost.php?p=2232071&postcount=124). Although it's more difficult, if you're not familiar with Linux.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
Answered in your other post.

Please give people time to answer before double posting. Thanks.

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] profjekyll:
Sorry bout that, although I've been using internet / pcs for ages am still a forum noob! (Think I understand a bit more now, all the latest posts are displayed on the fron page... ahhhh - I see!)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
Some people (like myself) subscribe to the posts and are notified when new post happen. It's the easiest way to follow what's going on.

I was subscribed to both the ones you posted one, thats how I spotted the double post. :)

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lousk:
Please help with "Loading..." screen never ending

I have been reading for days, but I still can't figure out why can my screen not go pass "loading..."

The problem began when one day it displayed the tri-color out of nowhere and the USB port stopped being properly recognized by Vista and XP - using 3different cable, still no go.

This is what the bootloader shows:

KAIS1*0

SPL-3.56.0000

CPLD-8

... trying to use the SD method in order to make it come alive again, but at this point I am at a total loss. All I get is a display "loading..." even after I press the power button to get it to start, no way it does. I tried 3 and 4 different sd card. The screen just sits there.

No matter which ROM I try and rename from RUU_Sign.nbh, to KAISIMG.nbh - just cannot get beyond the (loading...) screen.

I am wondering if it has something to do with not having HardSPL. Will I be able to do without a fuctional and recognized USB port - like using the SD method.

Please help
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] konefatp:
my phone is doing the same thing can anyone help i need this phone to work i will donate.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Did you format your card using the right method? What type of card do you have?

What SPL do you have?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ahassouna:
reformat it again to FAT 32, i think the problem is because it's not FAT 32

then it should work normally, also make sure u only have 1 file KAISIMG on the root of the sd card AND do not rename the file to KAISIMG.nbh as it would actualy be KAISIMG.nbh.nbh

so by just renaming to KAISIMG it would be seen as KAISIMG.nbh only.

hope this helps
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] konefatp:
yes when its in the drive i right clicked and hit format then went to fat32 and format it. change name and copy to sd card.

in bootloader it says spl-1.56.0000

but when i first did it it was hardspl 3.29
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nando223:
I was trying everything

I can't restore oryginal ROM, or any other ROM

I have colors with:

KAIS1*0

SPL-1.93.0000

CPLD-8

I put microCD with KAISIMG.nbh and i have Loading all the time.

Tried pressing the power button but it stays at "loading..."

Any ideas would be gratefully appreciated
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
You need Hard SPL first.

Check the sticky guide by mskip on how to flash a custom ROM.

Ta

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shawnl61489:
it stays in the tri-color screen, it wont go to the next menu
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sraksinn:
I have the same problem as the above poster. I have tried to follow mskip step #3 by hard flashing first before flashing the rom but to no avail. Can anyone point out a way to do this or test this? I am about to pull me my hair out because active sync isn't working. I have NATF rom on my Tilt right now, but would like to switch back to original ATT rom.

TIA
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Totomirov:
Not working with 2G Kingston and 2G SanDisk

Come on guys,

I'm really on the edge to jump through the window :). How many SD cards I should buy till I have a success flash !?!?!?

If it is not a problem somebody to made a video step by step procedure please upload it somewhere, because ......

Thanks in advance and let the Power be with you :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] deepthroat:
it is not too difficult than to make video on You Tube :D well ...there is some card than can work, others cannot. I have 4 microSD but only 1 to work. General guideline is to purchase low capacity, below 1GB if possible (I know it is rarity now) and format it with FAT32 (under XP is possible). If you can do this both then greater chance you will succeed.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] raiisak:
I never purchased over 3G on kaiser and never used other than scandisk. Never been bugged either :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] momo254:
It's been a while since I've messed with HTC devices and I want to flash my dads Tilt with the Solace v3.1 (http://xdaforums.com/showthread.php?t=516142) rom. The phone's usb port works, but for some reason doesn't get recognized by my pc (no activesync). What would be the steps to follow to flash this specific rom to this phone from the sd card? I'm fairly sure this phone has an OEM ATT Rom already on it. Thanks in advanced
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Pisca:
Please don't do it, since you are unable to read the 1st post :cool::cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] SoberGuy:
+1 QFT

(Stupid character limit)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] weasel5i2:
Having problems flashing from MicroSD?

I figured out that you must hold the camera button for a couple of seconds after poking the reset hole. Also, the "Kingston cards don't work" is not necessarily true. I switched to an unidentified card ("SD-C02G" is on it) and it works! Funny thing is, I googled that and it turns out it's a Kingston card, likely of Japanese origin. That may have something to do with it..

Just my $0.02.

--Weasel
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] HRUDKA:
Please, delete this post.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] someguy124:
Help!

My phone is stuck on the bootloader screen, and it isn't recognized by USB.

It also doesn't have HardSPL, how can I fix it? I tried flashing it via SD, but it is stuck on the "Loading..." screen.

Any suggestions? I will donate if you guys can help me out! Thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] batterlove:
Great suggest.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] batterlove:
My canon camera settings

I have a canon Powershot SX10 is. It is a new camera bought for me and I am not a professional photographer.

I want to be able to take good photographs of a carnival procession which consists of 40′ floats covered in 70,000 – 120,000 bright lights and moving parts..

Last time I took photographs of this carnival I ended up with a mass of streaks.

Can anyone advise me please, on the best settings I should set my camera to for this event.Who tell me,thank you!!
[Your Portfolio] epiclapser:
This is an app I made because I was very bored, check it out on github if you wanna contribute to it by all means go ahead.:D

https://github.com/epiclapser/AwkwardScilence
[Meizu MX] privatezs:
Hello XDA

i Have M1 Metal Device and have a pin on it

i forget it how can i remove it

the device has no flyme account as i guess

when trying to clear data from bootloader it asks for pin too

and only system update via update.zip works but didn't clear userdata

i have the access to fastboot too but

fastboot -w

did clear cache but permission denied for userdata

can i create a modified script-updater in update.zip and sign it to be able to flash via stock recovery and clear data with?

i don't know if it possible

any help :confused:
[Meizu MX] mps5566:
Hi i have same problem did u fix ur phone? i have flyme account on phone and i can not bypass

is there any way i can find phone imei no thru fastboot?
[Meizu MX] privatezs:
No i didn't solve it yet

And about getting imei number from fastboot

Use

fastboot getvar all

If it return the partition table, try this

fastboot oem ?

It will list all available commands from phone's fastboot

Look around it
[Meizu MX] mps5566:
Hi i try fastboot getvar all but dont show imei and SN show all other info

any other way i can try to find out?
[Meizu MX] privatezs:
[MENTION=4269253]mps5566[/MENTION] Try

fastboot oem ?

And post the result.
[Meizu MX] mps5566:
Hi no lucj with fastboot oem as well

if i can find imei i can unlock flyme account
[Motorola Droid 4] drfsupercenter:
OK, so I've had my Droid 4 since it came out in 2012, and finally replaced it with a Galaxy S7 and the keyboard case.

I wanted to play around a bit with RSD Lite and flash all the different firmware versions, as part of a wallpaper dump project I'm doing. I knew at the time that once you updated to ICS, you could not go back to Gingerbread. But it's now four years later, and I'm just curious what the technical reason for this is... it just tells me "flash failed"

With the original Droid you were able to go from 2.0 to 2.3 and vice versa easily, it was just a matter of putting the phone in flash mode and using the .sbf. Is it possible to use the 2.3 system.img with the newer baseband or whatever?
[Motorola Droid 4] eragon5779:
The Droid 4 has a locked bootloader. It prevents older firmware from being flashed, kind of how on newer Samsung devices, you can't downgrade the version because of KNOX and a qfuse trip. I'm not sure of the specifics on the Droid 4, but it should be a similar concept.
[Motorola Droid 4] drfsupercenter:
Don't the other Droids (1 and 2) have locked bootloaders too? It's a GOOD thing so you don't perma-brick by trying to flash garbage code to it.
[Motorola Droid 4] eragon5779:
The Droid 2 and Droid 2 Global had locked bootloaders, but the OG Droid didn't. It had a fully unlocked bootloader. I have two of them, and it was nearly impossible to brick them. As long as you don't mess with the bootloader, then you have one way to restore it, even if the system and recovery become corrupted (fastboot, or RSD Lite in this case).
[Motorola Droid 4] drfsupercenter:
Ah yeah, I noticed that.

I was trying to collect SBF files recently and wanted to verify all the ones I had... on the original Droid I was able to go back and forth between the original 2.0 and the latest 2.2.3 update; on my Droid 2 anything older than the most recent would leave me with a "MEM_MAP Blank" error in the bootloader.

However, the part that I don't understand... isn't the "OK to Program, Connect USB Data Cable" part of said bootloader? If it was fully unlocked, you could write a bunch of zeroes to it and you'd be left with a brick you couldn't recover from. That, to me, is the benefit of the locked bootloaders...

Similarly, you can flash ClockworkMod to both the D1 and D2, but on the D2 it requires a "bootstrap" which I imagine is similar to Safestrap on the Droid 4. I assume the custom recovery on the original Droid replaces the stock recovery, but it leaves that bootloader intact so you can flash back to 100% unrooted stock. So how is that any different than what the D2 bootstrap and D4 Safestrap do?

And furthermore... even using the bootstrap/Safestrap, if you try to flash a nandroid backup from an older version, it won't boot, you'll just get a black screen. I don't get that part either, because the bootloader is left intact during that process, wouldn't that be like live-booting Windows XP on a Windows 7 computer by plugging in an external hard drive? (Especially so with the Droid 4 and Safestrap, where you literally store all the partitions as files on the internal storage)
[Motorola Droid 4] eragon5779:
Technically, yes. You could brick it by doing that. But I never once touched the bootloader, or even used RSD Lite, until I got to the Droid 2 Global. Even then, I never touched the bootloader. You shouldn't ever have to (unless you unlock it through an exploit on a device, like some newer phones).

I don't remember how the Droid 2 worked in terms of exploits, but I know that the Droid 4 uses kexec, or kernel execution. Check here for some info on kexec (for regular Linux).

Untouched systems require the corresponding bootloader or older. The Galaxy S5 could run a newer system on an older bootloader, but not vice versa. Even Cyanogenmod requires a specific bootloader sometimes (Droid 2 Global, for example).
[Motorola Droid 4] drfsupercenter:
I used RSD Lite even back then, because I had rooted my phone and wanted to unroot it for something. Also if I recall, before ROM Manager had a nice recovery install feature, the only way to do it was to flash a .sbf file with the recovery partition to the phone.

Either way, I see people complaining about locked bootloaders and it makes me wonder why that's a bad thing. With the Droid 2 and 4 (and I assume 3 as well, I don't have one), you can only really "soft brick", it's always repairable via RSD Lite, and that's what Motorola themselves would do too. If you somehow bricked an original Droid by corrupting the bootloader, I don't think even THEY could fix it! Never hurts to have some sort of brick recovery.

I guess I'm fundamentally mis-understanding what exactly a bootloader does, then. You would think if the encryption changed, the older versions would still work but NOT the newer versions.

Would this be of any use?

https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[Motorola Droid 4] eragon5779:
Not really. The bootloader always has been and always will be locked on the Droid 4. Once kexec was achieved, unlocking wasn't looked at anymore.

And in terms of what a bootloader is, read around on XDA. There are plenty of threads on it.
[Motorola Droid 4] drfsupercenter:
Just an idea, I'm thinking there's a difference between a bootROM and the bootloader on a phone.

I'm thinking of the Nintendo 3DS as an example because I've done a bit of 3DS hacking. The 3DS has a bootROM, which means it cannot be overwritten and as a result Nintendo cannot update it even if they wanted to. They update other bits of code, but the bootROM is and always will be the same because it's readonly memory.

From what I gather, since the Motorola phones have had updates that reprogram (and update) the bootloader, meaning it has to be flashable somehow. What people have done with the 3DS is actually solder some wires to the NAND which lets you read/write it like an SD card. Could something like that be done on a Motorola phone? Even if the fastboot stuff isn't the full code, you could probably dump the oldest version of the bootloader from a phone that hasn't been upgraded (if there even are any out there in the wild...) and others could use it on theirs.

Given that you can buy a Droid 4 on eBay for like $40 it's probably not even a big deal, but it would be an interesting undertaking nonetheless. Especially for those who know how to solder. I don't know if phones actually use a NAND or not, but given "nandroid" I was assuming.
[Motorola Droid 4] eragon5779:
That's a process called JTAGing and is used on a lot of phones. But at this point, doing so is kind of pointless. All ROMs are made using kexec, and unless you can a) figure out the pin layout for the JTAG without killing the phone and b) build a kernel that doesn't use kexec, then there isn't much point to it at this point. We have working 6.0 ROMs, and I can deal with the extra boot time that kexec takes (which is, in my opinion, the only thing that would be improved from unlocking the bootloader).
[Motorola Droid 4] drfsupercenter:
Yeah, JTAG is basically the same thing I'm talking about, just that on a 3DS the pinout is such that it can be read/write like an SD card instead of needing a parallel connection.

I was thinking more for being able to flash any SBF (or in the case of the Droid 3/4, the XML and image files) to the phone. There probably aren't many people interested in actually downgrading, since the newest OTA update can be rooted and you can use kexec, but I'm more of a hobbyist and it was something I was interested in doing.

Plus, you could probably redo the SBF/XMLs to not update the bootloader (if it really can run newer code as you said) so that way you can just go back and forth between the first version of the OS to the newest freely, instead of being locked to the newest as you are now.
[Xperia Z3 Q&A, Help & Troubleshooting] Hussain_Salam:
Hey,

So as best to my knowledge i believe we get 2 years warranty which is supported by my Sony Account in which they say the warranty expires on 29/10/2016

So i've noticed a issue which i took lightly however it's gotten worse and beginning to bother me in which there's a light spot on the screen, Usually noticeable on Black/White backgrounds, I've attached an image of the issues, i was wondering will sony replace it or not?

EDIT: The device has been dropped once or twice, however this was around a year before this issue began occuring.
[Note Edge Android Development] and2:
only for 915F/FY DPC7

I played a bit with the new Marshmallow for our Edge to get more stuff. Also i like the S6/Note 5 style with f.e. the SSID under the wifi qs tile. I thought i share this fun with the community.

Before you flash the mod, please make a backup or at least save the files corresponding to the files in the zip. And if you are still odexed like me delete the oat folder under system/priv-app/SystemUI or rename the SystemUI.odex.xz to SystemUI.odex.xz.bak.

Features:

S6 Notification style including Edit

S6 recent style

Multi user

33 toggles

6 visible toggels in portrait and 10 in landscape (thats why is the Edit panel a bit disorded)

secondary symbols on keyboard

show/ hide S Finder and Quick Connect

Ultra data saving mode in toggles and Smart Manager

Toolbox

Notification colors and divider like Android N

S7 Lockscreen (nothing special)

S6/ Note 5 Power menu

Disabled Storage Notification

Album Art on Lock Screen

The contacts are a bit disorded at the header so i use the one from S7. I will also attache this one.

With this mod you will also install two apps, Potato Clock and All in one Gestures. The Gesture app is important because until now i did not find a way to get the menu button back. So i use this app.

Fixes:

disorded action bar in clock and contacts fixed

If you like that mod say thanks and have fun, if not go on.

Bug:

no response of the OK button at sim pin

Download:

here

Thanks to sagitt67 for power menu icons and the fix for the disorded action bar in clock and contacts
[Note Edge Android Development] Naoufalstitou:
Nice. Thank you very much my friend. :) :) :)
[Note Edge Android Development] kfasheldon:
Thank you..will play..
[Note Edge Android Development] catalyst05:
Itworks great.... thanks mate
[Note Edge Android Development] and2:
I had to upload the mod again because i had a little disalignment with the right clock (to close to the Battery). So if you have that issue please download again.

In the Album Art UI it's already fixed.

Thanks!