yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] fdelente:
Hello.

I have installed the latest U20_2.6.32.61-nAa-06 kernel, then the ROM (CM10-4.1.0-20131231-UNOFFICIAL-mimmi.zip), all went well except that I can't input all characters I need. The device has a physical keyboard that works perfectly with the latest CM7 official ROM issued for it, so I'd like to know if there is a way for me to get it working too on CM10? I tried the azerty.zip file provided in the dev forum for my device, but it didn't solve my issue.

Thanks.
[Nexus 5 Q&A, Help & Troubleshooting] uNb0rN1:
Hello,

Few days ago i got my N5 device,today i unlocked boot and rooted with "root-windows" tool.Then i got the free room manager app and flashed new recovery.I tryd to install cataclysmal room but it fails.i tryd to change recovery with sdk but it also say :"cant open recovery.img"

the wind xp also dont show me the device in my computer.i transfered the room with ts file explorer via lan.(drivers are installed and works).

can someone helf me to fix it pls?thx
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Please provide more details. Please provide errors for flashing rom in recovery.

Also please supply exact error when fastboot flash and also exact command you typed

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
dont use the rom manager app to flash, boot into your recovery and flash your rom there.
[Nexus 5 Q&A, Help & Troubleshooting] uNb0rN1:
When i try to flash room in recovery error:

E:Cant open /data/media/0/download/Cataclysm-Room.zip.

(Bad)

Installation aborted.

Used this tuto to unloock bootloader & root:http://xdaforums.com/showthread.php?t=2510966

Used Room Manager to get custom recovery after rooted the phone.(not to flash room)
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Bad means the zip is corrupt. Needs re-downloading

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Nexus 5 Q&A, Help & Troubleshooting] uNb0rN1:
ill redown direct on device so ill not use tf ecplorer to transfer.any idea why i cant flash recoverys?thx again.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
No idea. Id need a screenshot of your cmd prompt to diagnose..

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Nexus 5 Q&A, Help & Troubleshooting] uNb0rN1:
Ill make an screen shoat in 1 hr after room redownloads bec i have to turn off phone
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
you can flash the recovery via fastboot, or you can use the free flashify app to flash your recovery. the flashify app would be easiest(you need root).
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Cmd prompt is on your computer. If you're not fastboot flashing recovery, how are you doing it? I thought you said win xp?

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
and if you are using rom manager to flash your recovery, dont, it doesnt work.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
...just don't use it for anything ;)

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Nexus 5 Q&A, Help & Troubleshooting] uNb0rN1:
i use fast boot but now i downloading room on phone so if i turn it in boot mode ill cancel my downloading.

what app are you talking about?
[Nexus 5 Q&A, Help & Troubleshooting] uNb0rN1:
it installed me the recovery but not the touch version..it worked.
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
the flashify app can be used to flash your recovery, if you already have root. if not, fastboot will be your friend.

---------- Post added at 01:28 PM ---------- Previous post was at 01:27 PM ----------

good, you got lucky :)

but then why are you saying it wont? or did it just install it for 1 time use?
[Nexus 5 Q&A, Help & Troubleshooting] uNb0rN1:
ah you are talking about sdk tutorial.yea i tryd it but after these commands:cd Desktop/android-sdk-windows/platform-tools

fastboot flash recovery recovery.img

it says cant open recovery.img

i mean the sdk tool dont work to install... not room manager.i thought it dont let me install room bec of recovery.
[Nexus 5 Q&A, Help & Troubleshooting] uNb0rN1:
room worked now
[Verizon Samsung Galaxy S III] phatreno:
For those of you who took the 4.3 ota what is your opinion of the updated ,and did you come from a custom rom.I was thinking of talking official 4.3 just curious to here feedback on it ,I know once I do it bootloader is locked for good .I am on Liquid smooth love it but I miss the Samsung features and having a glitch free phone I know ill get back on the verizon ota, been running custom rom since first week of owning phone think im ready to go back stock as long as official 4.3 is good
[Verizon Samsung Galaxy S III] kieso:
=phatreno;49148087]For those of you who took the 4.3 ota what is your opinion of the updated ,and did you come from a custom rom.I was thinking of talking official 4.3 just curious to here feedback on it ,I know once I do it bootloader is locked for good .I am on Liquid smooth love it but I miss the Samsung features and having a glitch free phone I know ill get back on the verizon ota, been running custom rom since first week of owning phone think im ready to go back stock as long as official 4.3 is good[/QUOTE]

Why take the OTA when you can just flash the stock Rom? I personally like it but I've always liked TW roms
[Verizon Samsung Galaxy S III] phatreno:
Why take the OTA when you can just flash the stock Rom? I personally like it but I've always liked TW roms[/QUOTE

I know that there' one out there you can flash and maintain a unlocked bootloader but reading the thread sounds like there's a lot of issues with it I use my phone for work so need something 100% eliable Liquid is almost there but still have to do battery pulls get f/c's ,I did have another phone so it didn't matter now this is my only phone

let me rephrase that didn't mean take the ota but flash the official 4.3 which would lock boot loader to take the ota I would have to revert to stock then take the ota easier just flashing 4.3
[Verizon Samsung Galaxy S III] buhohitr:
After a long time flashing custom rom and kernel on my wife S3 and always hear complaints about issue, I decided to flash stock 4.3. Now she's happy with her phone, everything is working smoothly and the phone is pretty fast and snappy, battery life is the best. I have to say, 4.3 is a great improvement over 4.1.2. My recommendation is if you like to play around with flashing custom rom and ok with all the bugs hear and there then it would be fine, but if you want a daily driver, stable phone then stock 4.3 is the way to go. While she's on custom rom, many times when we at a party and when she tried to take picture the camera FC, or displayed weird color, the gps acting up, phone lockup needed to pull the battery to reset etc...Again, if you want a stable, good battery life, go with stock 4.3 and with just root.(I need root to install wifi tethering). Now she has a perfect phone and no more complaints.
[Verizon Samsung Galaxy S III] phatreno:
that sounds like what I needed to here,did you flash 4.3 or revert to stock and take the ota not sure if there's a difference I already downloaded the stock 4.3
[Verizon Samsung Galaxy S III] bobAbooE:
I've had zero issues on the 4.3 rom.

Make a backup and give it a run.
[Verizon Samsung Galaxy S III] buhohitr:
It's depended on what apps you installed on your phone, most of them should be fine with 4.3. When ever I upgrade to a new version, I like a clean install. Do a factory reset (this will wipe all your installed apps and reset your phone back to factory condition, make sure you have a backup of your apps), then let the upgrade run. Once done use saferoot to root.
[Verizon Samsung Galaxy S III] goldsmitht:
from crack flasher to stock

i've been a crack flasher since my DX days, having flashed just a couple days after getting my S3. I've been on Hyperdrive, Synergy, AOKP, OSE, stock and various versions of CM to include the best, Mastamoons unofficial.

had to get a replacement phone, and as i was setting it up, the damn thing updated to 4.3 itself.

now... i still get that crackflashing urge, but i will admit, i like having the phone stock. i can make it look like its on any of the other roms, just with minor alterations.

antenna's on the latest is the best i've ever seen, everything works great, and don't see the lag on 4.3 TW as on others.

guess i can live with this for a while, and i do have faith in the DEV community that someone will break the latest, just as in previous versions. But for now, i can live with stock as everything works great!

:victory:
[Verizon Samsung Galaxy S III] phatreno:
ok thanks
[Verizon Samsung Galaxy S III] Naddict:
Please go here for any further...http://xdaforums.com/showthread.php?t=2575661
[Motorola Droid 4] Angel_x19:
UPDATE: I also use RSD Lite to install the original Stock Rom but the problem continues.
[Motorola Droid 4] Angel_x19:
Second update

I flash again with the RSD lite and the stock rom but this time I put out the microSD card and I finally get back access to my internal storage but I can't still get access to the Micro-Sd card and when I put it on the droid 4 I get the message "Sd card is unmounted"

Also If I restart the device with de microSd card In, I lost the access to both memories again.

Please I need some help.

PD: Sorry again for my english, Also Im speak spanish.
[Motorola Droid 4] kwyrt:
I've never run into an issue like this but if your internal storage works when your microsd card is not inserted, maybe it's a problem with you microsd card? Have you tried reformatting it?
[Motorola Droid 4] Angel_x19:
Yes, actually the microsd card is formated to ntfs, I also try formating the micro-sd to FAT-32 but i can't mount both memories.

If I connect the micro-sd to my PC I can see my files. So I think the problem is with the void.fstab file I can't mount properly the external sd card.
[Motorola Droid 4] Angel_x19:
New Info

I found a lot of info about my problem in the CheckRom forums.

It's from the member "Spider"

So it's says the I need go back to ICS or GB .. but I found that Its not possible do that once you upgrade to JB :(
[Motorola Droid 4] Angel_x19:
I don't know What tha hell I did but

Finally after a lot of flashing process with diferrente roms I get my sd card an internal memory back :victory: :victory:

I do not know exactly how to solve the problem, but is related to repair the mount point of the internal or external memory

I think that flashing with the lastest rom available in motorolas sites fix the problem because I saw a file named "emmc flash" inside of the zip so I think that fix the mount points. And that file was not available in previous versions.

So thanks to all especially kwyrt for trying to help me :highfive:
[HD2 General] andrejazzz:
Hi everyone!

I am very sorry for such a n00b-post, but I really cannot find a solution.

The problem:

I recently got a HD2 of a friends who did not use it anymore, because Android suddently stopped working. Now it's stuck at a black screen [A] saying:

aMAGLDR V1.13

Build: Feb 1 2011 03:46:07

by Cotulla 2011

I tried resetting the phone using the red button near the battery, but it did not solve the problem. I am able to boot the HD2 into recovery-mode (colory screen) but then, after connecting to a pc it does not change from "serial" to "usb".

I have installed WMDC on my W7 64-bit system. I have also tried to use "RUU_Leo_HTC_NLD_1.66.404.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship" (from the 4shared "shipped LEO roms"), but none of them recognises my HD2 neither in Recovery nor in the black screen [A].

Is this phone useless? What can I try to revive it?

What might be helpfull: when normally booting, the phone vibrates once during the HTC-screen and 5 times after the black screen [A] appears.
[HD2 General] Shadow_Nexus:
Since you're unable to connect to PC, then you can't re-flash HSPL.

HSPL needed to force flash any shipped WM6.5 ROMs to HD2.

Then the only way is to flash original WM6.5 ROM for your device from uSD.

If you're not sure what CID, just download any HD2 shipped ROMs and try to flash from uSD.

Just be careful not to flash EU's ROM on T-Mobile device!

Extract the ".exe" file, then rename the ".nbh" file into "leo.nbh", copy that to root of uSD.

Power up your device while pressing vol down button.

Don't worry if the ROM refuse to flash, it's just a wrong CID.

But to make sure, connect your device to another clean PC (without android drivers inside, just WMDC), preferably a PC sets for syncing WP7/WP8 devices.

And make sure your device turns on by itself when charger is connected (auto turn on from off state).

That's just to make sure that usb connector is not damaged.

HD2 vibrate 1x at power on, it's normal.

Vibrate 5x after magldr shows up, I suspect something wrong with magldr or the ROM itself (corrupted or something).

Another possibility is some NAND bad blocks.

But if it's vibrate 5x at power on, then you have a bad luck. :D

The point is, flash the original ROM first.

If it's success, then flash HSPL.

After that, the rest is up to you.. :)
[HD2 General] andrejazzz:
Firstly, I want to thank you very much for your quick and extensive answer!

But I have only one tiny question: are these the ROMS which I can find at http: //www . 4shared . com/dir/22189940/b8552fa0/Shipped_Leo_ROMs.html#dir=MGRa1Cen ? And you mean I should just pick one and try?
[HD2 General] Shadow_Nexus:
You can also find HD2 shipped ROMs here. :)

Anything that has "TMO" are T-mobile ROMs, otherwise it's EU.

Again,

don't flash

EU's ROM on TMO devices!

The first 3 digit are the ROM version (1.66, 1.48. etc.), 3.14 is the latest WM6.5 ROM.

The next 3 digit are CID code (207, 404, 707, etc.).

Like I've said, if you don't know which CID for your HD2, then just download all ROMs from different CID then flash it one-by-one using uSD. :D
[HD2 General] andrejazzz:
Thanks!

So far I have tried the 404 and 162 (edit: and 161, 911), but so far without luck. I'll keep you posted!

Tiny question: is it normal that I cannot shutdown in Recovery Mode?

Perhaps some useful info shown in Recovery:

PB81100 HX-BC

SPL-2.08.HSPL 8G XE

0x05

CotullaHSPL 0x40
[HD2 General] Shadow_Nexus:
Correct me if I'm wrong, but it looks like an EU HD2, TMO HD2 are rarely using hynix nand, made around late 2009 or early 2010.

Just try to flash ROM with CID for your friend's country first.

If failed, then try another CID.

There should be one or two info about CID number vs. country somewhere around.

Good luck!
[HD2 General] andrejazzz:
At this moment I have tried all the NLD roms with no result. Also I have tried roms from several european countries, but none of them works:/ Might it help if I give the serial number?

And what might be worth saying: my phone turns on when connected to AC power / wall-charger; when connected to charger the "serial" disappears...

Thanks for all your help!!!
[HD2 General] Shadow_Nexus:
Have you try connect to other PC?

When flasing ROM from uSD and failed, what error message you got?

If it's "CID mismatch" or something like that, than it's definitely a wrong CID.

If it's "ROM update error bla bla bla", it's most likely corrupted flash image or the uSD itself (use a small sized uSD, 1gb would be fine).

Even if you flash the correct CID, without removing HSPL first, it would still throw an error message "ROM update error bla bla bla" during flashing Radio.

Then it will restart and retry to flash again on it's own.

By the way, I don't know if there are ways to flash HSPL from uSD.

Or guide on how to make a "gold card".

I sugest you search it.

Worth to try if you couldn't find the correct CID for your device.

CID from serial number?

Yes, back in 2010/11 HTC site provides s/n checking for download the correct ROM.

But now it's gone.
[HD2 General] andrejazzz:
Thank you very, very much for helping such a newbie ^^

At this moment, I am able to get into the update-menu: I changed the filename to LEOIMG.nbh. The only problem is that all the Dutch images give the same error: 00018003 : Radio (V2) - FAIL.

What could I do to solve this error? Use the freezer-trick or wouldn't it make any sense?

edit: it does boot when I connect to another W7 pc with WMDC (replies " Not connected" ), only it automatically starts the update-procedure (which fails).
[HD2 General] Shadow_Nexus:
There are no such thing as newbie, that's why we need to learn. :)

Error 00018003 during Radio flash?

I have no idea what error is that.

But first, are you sure that your friend bought the phone on local shop?

I mean, not imported, or when he/she travel overseas, or has the mainboard swapped at HTC service center.

It happens to me when my second HD2 suddenly has no signal, about 2 years ago.

Brought it to local service center and they swapped the mainboard without telling me.

And the swapped mainboard has CID from 404 (europe), the original was 707 (indonesia).

Okay, back to error something.

WMDC won't recognize the phone unless it's a working WM6.5 device, or a working WP7 device with WP7 SDK + Zune installed on your PC.

Just put the phone into bootloader screen (3 color screen), then connect it to a clean PC.

Does the "Serial" changed to "USB"..?

If it does, reflash HSPL 2.08 using HSPL4 package.

Then flash Radio ROM only, 2.15.50.14 is a good one.

Again, an EU HD2 can use either EU's Radio ROM or T-Mobile's Radio ROM.

But a T-Mobile HD2 can only use a T-Mobile's ROM..!

If the "Serial" doesn't change to "USB" but on your PC makes sound like something is plugged in, open device manager and look for an unknown device (no drivers loaded).

Expand it, what does it says?
[HD2 General] andrejazzz:
To be honest: I am not 100% sure that it is an European (Dutch) phone. What I saw when I opened the phone's back was that the warranty-seals on the screws were molested. I don't think he got the motherboard replaced: way to expensive in relation to a new phone...

The bootloader screen gives now the following text:

RUUNBH

PB81100 HX-BC

SPL-2.08.HSPL 8G XE

0X05

CotullaHSPL 0x40

Upgrade ROM error

Please try again

When I connected it to a clean pc, the phone booted and gave another upgrade-error, only this time on a black screen (I got the uSD out the phone).

After booting the phone and connecting to a pc the "serial" does not change to "usb"...

When I tried to install WMDC I get the error "Installationpackage not supported by processor". Seems like bullcrap, but there it ends. No yellow exclamation marks in Device Manager...

I have yet not tried to flash a T-Mobile ROM to the phone. I have tried all the NLD ROM's: 1.66.404 ; 1.48.404 ; 1.66.404 ; 3.14.404 ; 1.66.404 ; 1.43.404

I have yet not tried the other ROMs I downloaded, but I will tomorrow. To start 161 does not work.

Also: I cannot shutdown when in bootloader or MAGDLr, is that correct?
[HD2 General] Mister B:
What colour are your call & end key buttons !

if white you have standard EU type model. T-Mobile EU models are same as any EU model & can flash any ROM/Radio

If green & red you have a T-Mobile USA model (TMOUS) & need correct ROM (found in HD2 Wiki)

T-Mobile USA model needs care as if flash wrong radio version you can brick it.

Flashing via SD card should be last choice as first stage of a SD card flash is install of the SPL to standard SPL from the nbh which means you have no CID bypass as HSPL gone.

ideally you need a Windows 7 32bit machine with a known working WMDC setup & try flashing a suitable rom once decided on EU or TMOUS device.

As you have HSPL on your HD2 already it will bypass CID if flash via PC so you can flash any CID code rom.

Try connecting device to PC (with known good WMDC) and use reset button on HD2 to boot to bootloader & see if get any luck in running ROM installer from PC.

If lucky the USB flash issue is PC & drivers rather than hardware on HD2.

I would suspect you have nand issues on HD2 or perhaps worse, if nand sometimes you can get it back if persistent & get something to flash completely.
[HD2 General] Shadow_Nexus:
Thanks MisterB for adds up.

So am I, suspected a nand issue.

The reason I want him to revert back to original SPL & Radio is to make sure that it's a nand related problems, not radio hardware problems.

If he managed to find the correct CID for his phone, he could easily reverts back in case somethings wrong in the future after playing with custom ROMs.

This also happens to my friend's phone a couple months ago.

But in her case, the bad blocks are definitely located where magldr resides, and many more on data partition.

She can flash shipped ROMs completely, but it refuses to boot.

Can't flash a WP7 ROM because magldr freezes when it's loading, can't even bring the menu screen.

She can run a native sd android build for a couple weeks, but then it acting strange again.

Then finally she just gave up and bought another phone.

[MENTION=4606502]andrejazzz[/MENTION]:

You can't shutdown on bootloader (3 color) screen.

Remove the battery is the only way to shutdown, or press the reset button to restart.

But you can shutdown/restart or anything else on magldr menu screen.

Press & hold power key right when magldr loads up (before it's start to "go go go").

In addition, you can download WMDC x86 version here, and x64 version here.. :)
[HD2 General] Mister B:
He may indeed need try SD flash but I would exhaust all options of USB cable flash via PC first as retaining HSPL will be useful to start with as any generic HTC ROM could be used for the USB cable flash.

If that is not possible then flashing via SD is only viable option & indeed many times only way get over bad boot/nand issues but with all the CID versions for HTC regions & operator branded regions you have a hard job knowing the right one, you could even try the right ROM & as it does not flash overlook it for further testing.

I see he has tried SD flashing but still has HSPL so either SD card is not best suited for nbh flashing or nand/hardware that bad even first stage of flash is not possible.

If I was testing this device & trying recovery I would probably try freezer test to cool device prior flashing & make good effort on USB flash before going on to SD card.

Most well used Android HD2s these days have nand or bga issues to some degree as android works the hardware so much harder than WM6.5.

You really need be sure PC & driver are known good for flashing & if going to SD flashing that SD card is suitable or you will waste a lot of time & effort.

Loads of links & tips for all the software & some threads are in the HD2 Wiki
[HD2 General] andrejazzz:
I apologize for replying so late, but I have had no time: I had a few tests at school :(

[MENTION=337456]Mister B[/MENTION]: I have a black HD2 with white icons, so I have a european model.

I have installed installed the X86 on a clean 32-bit system, but it does not recognize the phone. I have reinstalled the WMDC on my W7 64-bit system, but still it does not recognize the hd2. I have no other Windows Phones, so I am not able to verify the WMDC-installations.

When I connect to a pc, the phone boots and shows: "Software update failed! Please try again"

[MENTION=1720126]Shadow_Nexus[/MENTION]: Correct, that is exactly what happens. I do not completely understand what you mean with "Press & hold power key right when magldr loads up (before it's start to "go go go")", could you please explain?

[MENTION=337456]Mister B[/MENTION]: How could I check if the SD-card might be the problem? It is a 16GB Class 4 Kingston SD. I have tried all the NLD-roms and other versions (random countries, not TMOUS). I have tried the freezer trick with a NLD-rom on a mSD, but it did not work.

Thanks for all your help!