yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 ROM Development] ordinary:
dead XDAIIS (in bootloader mode) please help..

Dear Guys,

My XDAIIs is in bootloader mode (it shows serial--> at top and V 2.07--> at bottom, and doesnt turn to usb when i plug into my usb port). Does anyone know how to fix it? Please help....
[MDA II, XDA II, 2060 ROM Development] RAGOv:
hi ordinary...

haven't u said it worked!!!so what happened next???!!

plz explain more,for the mean while try changing the USB port ur using,check ur cable,and try to change the computer(desktop/laptop)... :D

if it doesn't work plz explain more what happened,so we can help u find the solution... :D

@arcquisumbing:u are not clear in ur post my friend...what same problem(are u in bootloader mode???!!),how did it happened after installing item from the extended rom????and u want a solution for what???!!!

sorry i couldn't help u my friend but plz try to explain more so we can undestand ur problem... :D

RAGO :lol:
[MDA II, XDA II, 2060 ROM Development] arcquisumbing:
stuck in splashscreen

i'm sorry.

i was referring to the stuck in splash screen.

after the hard reset, autorun was initiating installations for the contents of the extrom. i installed each and every item and at the end of it, it required resetting. i just clicked on yes to reset, then when it did, it just stops at the splash screen. i tried waiting for an hour or so, maybe it would just come, but still to no avail. i tried re-installing everything, but still the same thing. but when i tried NOT TO INCLUDE the ARABIZER, everything worked just fine.

now, i'll just pray for two things, 1-that you can help me solve this problem, and 2-that the light at the end of the tunnel is not a train.

thanks. more power to you.
[MDA II, XDA II, 2060 ROM Development] RAGOv:
hi arcquisumbing

now if u still have a 2003 OS on ur device,wich i doubt it,(i've read ur post in the thread How can I increase Storage memory in WM 2005),then ur problem can be solved inchallah :wink:

*if ur device is i-mate,do the following:

1-remove arabizer from Ext ROM,so ur device can enter OS

2-install arabizer cabs after being in the OS

download arabizer cabs from here http://xdaforums.com/download.php?id=6292

*if ur device is not an i-mate,then u have to wait untill my no brand arabizer succeeds.... :wink:

RAGO :lol:
[MDA II, XDA II, 2060 ROM Development] ramram:
Re: splash

Hey bro since you have an Imate! Download this file from clubimate http://www.clubimate.com/support/PPC/ROM/RUU172810WWE_CDL_SKU2.exe and flash it.

I'm sure your problem will be solved for sure ;)

Ps : RUU172810WWE_CDL_SKU2.exe is just the Arabic Extended Rom
[MDA II, XDA II, 2060 ROM Development] ordinary:
dead XDAII and XDAIIs

Hi RAGOv,

THank you for your willingness to help my problem

1. The one I said worked is for my xdaII, but only to pass the MODEL ID error (it runs well, after i use your attachment file. I upgrade it to O2 ROM upgrade 1.66 WWE). However, After finish upgrading, It still stuck on O2 splash screen.

2. Now, Im facing the other thing. "the dead XDAIIs". Its screen only appear O2 splash screen when i put on the battery(even i already did a hard reset). Then I tried to change mode into bootloader mode (by pressing power button, record, and reset).in the end, after I did an upgrading. it also stucks on O2 splash screen.

Please help...I dunno what to do anymore..:(
[MDA II, XDA II, 2060 ROM Development] RAGOv:
Re: dead XDAII and XDAIIs

Hi ordinary,ur welcome anytime bro :D

now concerning ur xdaII,i think ur extended ROM is not compatible with ur OS version,that's why ur device cannot enter windows...

here what u have to do:

1-go to ftp ,download ER2003Edit,it's a ROM editor

2-open any Himalaya ext ROM(ms_.nbf) with the software mentioned above

3-go to files tab in ER2003Edit,and remove all the files(empty the extended ROM)

4-save the ms_.nbf file

5-now go to ftp again,and download 1.72.00WWE ROM version from Himalaya folder

6-put no_id.exe i gave u before with the ms_.nbf in one folder then flash ur device by running the .exe file(u will have an empty ext ROM device)

7-after the flash of ext ROM is complete,hard reset ur device,if u still cannot enter windows,then replace ms_.nbf file with the NK.nbf file of the 1.72 OS version in the folder u made on ur desktop/laptop,then flash..

now concerning ur XDAIIs,do the same but with it's specific ROM files..

good luck and keep in touch bro... :wink:

RAGO :lol:
[MDA II, XDA II, 2060 ROM Development] arcquisumbing:
Re: splash

thanks for the info. however, does this work with WM2k5?

thanks again.
[MDA II, XDA II, 2060 ROM Development] RAGOv:
Re: splash

unfortunately it don't,but read this thread,it didn't work to me,but maybe ur luck is better :wink: http://xdaforums.com/viewtopic.php?t=23709&highlight=arabizer

RAGO :lol:
[MDA II, XDA II, 2060 ROM Development] arcquisumbing:
RAGO....as always....

as always my friend, you have an answer to a question......

my praises to you........

keep up the good work..........

thanks again.................
[MDA II, XDA II, 2060 ROM Development] ordinary:
Stuck on O2 splash screen (both my xdaII and xdaIIs)

Hi RAGOv,

I already followed your instructions, but it still remains the same. Do you know why? Still stuck on O2 splash screen. I use the ver1.66 WWE. I did erase all the files in extended ROM. and replace the NK files from ver 1.72WWE. In the end, it remains the same without change.

Please all my bro...help..help.
[MDA II, XDA II, 2060 ROM Development] RAGOv:
hi ordinary....

beware my friend,my bag is almost empty....i am sorry bro i couldn't help u,but u can always ask help from people in this forum much more advanced than i am :wink:

my last advice will be to get a shipped ROM containing the 3 files(ms_.nbf,NK.nbf,radio_.nbf),just replace HimaUpgradeUt.exe with the no id one,and reflash.....if it still doesn't work,then am sorry bro...i tried my best :( .Try posting a new thread,describe in it everything,so maybe u can solve ur problem....good luck :D

hi arcquisumbing...

now my friend u r doing a big mistake!!!!!

after reading ur PM,i have to tell u many things:

1-magneto doesn't have extended ROM like in 2003,u don't have ms_.nbf,so stop trying to install u friend's ms_.nbf into ur magneto coz it's not gonna work.

2-if u wan't the arabizer on magneto....so i'm sorry to tell u that there's still no official version that runs on magneto.Now if u have read the thread i've gave u,Rabia was trying hard to install arabic on magneto,and he did it(as u can notice from the pictures in his thread).The problem is that i followed his instructions,but couldn't get what he reached.All i could get is to let my magneto MDA2 read arabic,but without having the keyboard in arabic :wink: (if ur interested,try Rabia procedures,and if it doesn't work,i will help u :D )

so my friend stop trying installing ext ROM on ur magneto,and if Rabia method didn't satisfie u,then u have to downgrade to 2003 or 2003 se,and install an arabic ext ROM(only here it can work).

if u still wan't magneto on ur device,and u miss the automatic installation of the softwares that exists in 2003 & 2003 se once u hard reset ur device(the extended rom),then u can solve this problem,there is the 2577 method....i won't explain it unless U HAVE READ IT AND SOMETHING WASN'T CLEAR(this was explained 1000 times before,just go where i've guided u,and plz READ :wink: ) http://www.buzzdev.net

Now i hope i've answered ur questions,and ur always welcome my friend :D

RAGO :lol:
[MDA II, XDA II, 2060 ROM Development] ordinary:
Is there anyone ever experienced the above problem?

Please help...:(
[MDA II, XDA II, 2060 ROM Development] arcquisumbing:
now i find light at the end of my tunnel.......

RAGO, my teacher.....

now that you explained, i now have a better understanding of what 2k5 is. i've used the 2577 procedure. i tried opening an extendedrom using the rom editor and simply dragging the files i need and dropping it to the zip file of 2577.

now, the next thing i'll try to learn is how to produce an ms_.nb file. i'm planning to try the SD back-up procedure. since i don't have a card reader........then i'll just try to find another way.

NOW, i find light at the end of my tunnel.......and thank GOD it's not a train......it's RAGO holding a flashlight...... thanks for your guidance my friend....
[MDA II, XDA II, 2060 ROM Development] RAGOv:
hi arcquisumbing...

if u want to make ur own ms_.nbf,then u will need ER2003Edit...

using this software,u can open Himalaya ms_.nbf,and edit them...

*download it from here ftp://xda:xda@ftp.xda-developers.com/Tools/ER2003Edit_1_4_26.zip

*read about it from here http://wiki.xda-developers.com/index.php?pagename=ER2003Edit

*and learn more about ext ROM by reading the wiki http://wiki.xda-developers.com/inde...c.Extendedx20.ROMx5c.x20.thingx2c.x20.thenx3f.

RAGO :lol:
[MDA II, XDA II, 2060 ROM Development] arcquisumbing:
thanks........

what else can i say......but thank you......again......

you really are a big help.....
[MDA II, XDA II, 2060 ROM Development] hdubli:
Hello Everobody,

I too did face the same problem.What I think is this is due to the fault in the Back up battery and not in the ROM.I didm try to flash by putting it in B/L mode, but flash failed in the first step itself...

One can also try removing moisture by blower, and then let xda2 cool down to room temperature, then put the battery.

Also, pls check if the RED LED glows when one connects the charger to the XDA2 with no battery inserted.If yes, then yr piece is not dead...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] gameriot:
Hey guys,

Right now I'm on a custom GPe rom (i9505G). I need to get back to Touchwiz.

You're probably wondering ... why...? Well, last night I bought a Fitbit Flex, and it's supported by GS4 (wireless syncing), http://www.fitbit.com/devices. Could it be because I'm on a custom rom?

Any feedback is appreciated.

Thanks,

gameriot
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Yes, it doesn't work because you're on a custom Rom. Fitbit doesn't support it. You can flash the stock firmware in Odin.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] xBeerdroiDx:
Those fitbit's only work on stock or stock-based roms. There's some good ones in the Android Development section. Cheers
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] gameriot:
I have a Mac, so I can't get Odin.

I'll check it out. Could you link it?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jeffreii:
Best Touchwiz-based ROM, in my opinion, right here:

http://xdaforums.com/showthread.php?t=2313469
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] markbc01:
#1. The TW rom that I find best for me is Shostock2.1 It's already very mature, stable and zero issues.

Here's the link if you want another option:

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

#2. As to the Mac and no Odin thing. . . . I use a Mac (a couple of them, actually) and found that Heimdal can be made to work, but some folks feel it is not as user friendly/easy to use as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)

I have used it, but maybe it's just my experience, there have been sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!).

Anyway, the newer versions seem better, please check out the current version of Heimdal and the Heimdal front end package?

Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/.

The site should have instructions on how to get your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .

Also, here is another very good, informative thread of someone's experience restoring his i337 using Heimdal! It might be helpful (and it is just a few posts down from yours :o

http://xdaforums.com/show....php?t=2374441

#3. But even on a MAC you CAN use Odin! Odin generally works well and if Heimdal seems to complicated or you can't get it working, then you could open your options up significantly if you can either:

(1) use bootcamp and boot into a windows OS, or

(2) use Parallels/VM Ware Fusion and use windows in a virtual window.

Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...:svetius:

If you can do this, then you can use Odin and work on phone with all the tools that most folks here have and use to good effect.

Good Luck!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] gameriot:
I already tried hiemdall. It kept coming up with error whatever I did. Also my TWRP keeps failing when I'm trying to flash. I'm trying goomanager.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] markbc01:
OK, I have been there! If Heimdall does not work, then:

a) find a windows machine for a while or

b) use your machine with bootcamp (if you're on a MBP) or

c) use your machine but install/open a virtual desktop (Parallels or VMware Fusion) to get a windows or linux environment.

Please BE CAREFUL when using goomanager (or Rom Manager, for that matter). These apps are useful, but they also are prone to suddenly creating havoc on the phone - usually when least expected :(. I have used both -but only very carefully and for limited functions. (I recently used GM to update my TWRP to the latest (I think 2.6?) -no issue --so try that at least!)

But for loading roms, initially loading recoveries or the like it is better to use the "manual" processes that we have available here.

Good Luck!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] gameriot:
Thanks for the help. I got Touchwiz on my phone and got the sync to work but I just hate Touchwiz and went back by restoring my nandroid. Can't wait till they get Bluetooth 4.0 on custom roms, then it'll work.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] markbc01:
Great..and if you still need a TW Rom, you still can switch launchers to Nova or something like that...

Then you hardly see the Samsung footprint...yet have the TW needed for the device..
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] drkPu1se:
Hi all! I just received an update message from AT&T to update the software of my phone. I am one of those people who is really paranoid and won't update unless I know it'll be beneficial and won't affect anything else at all. I am currently on version i337ucuamdl. I tried looking up the update and I'm not getting to much information. I don't even know what the version is on the update... Can anyone clarify or concur with me?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
If you ever want to put a custom recovery and rom on your phone don't take it.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] scott14719:
There is plenty of information about the update in the "General" section if you are serious about learning what it is.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Agent:
http://xdaforums.com/search.php?searchid=213864485

Here's a search you use to see a lot of things about the MF3. I would recommend staying away from it, I had many problems with it myself with it.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] drkPu1se:
So it turns out this post was made irrelevant because last night when I was asleep my phone updated itself without my permission. Now I have seen ways to Odin down to AMDL, but I think I'm gonna hold off just a wee bit longer. Lemme tell you though.. I'm pretty upset about the fact I didn't get the chance to approve or deny.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Just so you know, you can not Odin back to mdl. If you try you'll at best soft brick your phone. Worst case, damage it so it won't be functional.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] drkPu1se:
So you are telling me I'm screwed at this point...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AJ Newkirk:
Pretty much, yes.

You can root your phone, but you cannot change the ROM or the recovery anymore.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jeffreii:
People should be forced to read the "Beginner's Info Thread", which is stickied in the General forums, at least once before they're allowed to read anything else, IMO.

Right at the top is the method to block OTA updates from happening:

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

Once it's done, it's done. MF3 is a mofo. No possible way to downgrade, no way to install custom recovery or custom ROM. You can root...but no way to unroot...so not worth it for most people.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] drkPu1se:
Fuuuuuu..... Whelp maybe I should send in my phone and ask for a replacement ha
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jeffreii:
You're not likely to get a replacement, at this point, that isn't already on MF3. Since the update has been out for over 6 weeks...chances have grown slim.

Personally, I'm planning on switching to the Note 3 in about a month...and this is actually a good situation for me as my non-MF3 S4 should fetch a bit of a premium on Ebay! You could go that route to get what you want I guess (sell yours on ebay and buy an MDL one).
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Febby:
And if the note 3 comes even worse in state of firmware than the s4? :p
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jeffreii:
Haha yeah that is definitely my big worry. Doubt I'll pull the trigger on that until I see an exploit published.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] drkPu1se:
So it turns out that there is a method to root, but not safely from what it sounds like. Now I'm determined to dig into exploiting Android. This will be a new thing for me. So any tips on how one does this will be very helpful and I will be very grateful.

Thank you everyone who has replied to my thread.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
You can root it safely and there is a safe way to unroot it too. What you need to be careful with is what you do to it when it is rooted. Because there is no way to odin a stock firmware if you mess something up your stuck with it. (It appears that best buy now has the ability to flash the stock mf3 firmware so you have a little more room for error).

With root, most people want to remove bloatware. If you do, use titanium backup and freeze the apps, don't delete them. That way if you get over zealous you can just unfreeze them.

Good luck.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] drkPu1se:
The thing is I want to have a custom recovery and go to town with ROMs and mods. As for the Best Buy thing, I am gonna have to check that out.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
You never took the mf3 upgrade?

Edit, start here. http://xdaforums.com/showthread.php?p=42320391
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] deron37129:
Dnt update ull b bored
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Are you drunk?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] drkPu1se:
Lmao no I tried to avoid the update and I woke up one morning with the update done all on its own. Kinda pissed me off really. But that aside again because I do have the update I can't have a custom recovery. That's what's bugging me.
[Nexus 4 Q&A, Help & Troubleshooting] apopberz:
I'm not able to use fastboot at all on my nexus 4

I always get:

< waiting for device >

adb works fine, I can shell and view all the files etc. and "adb devices" lists my phone there and doesn't say offline. I've done all the normal stuff like changing USB ports (2.0 and 3.0) and I've tried different versions of ADB and the driver, clearing the RSA keys on the device. The phone is totally stock, no root and running 4.3 / JWR66Y and this has been happening before the latest OTA (JWR66Y) update (first OTA of 4.3)

Here's my bootloader info

Command line: console=ttyHSL0,115200,n8 androidboot.hardware=mako lpj=67677 uart

_console=enable lcd_maker_id=primary lge.hreset=off lge.reset=mode_reset gpt=ena

ble lge.kcal=0|0|0|x lge.rev=rev_10 androidboot.emmc=true androidboot.serialno=0

0475fbe14129674 androidboot.bootloader=MAKOZ20i androidboot.baseband=mdm bootrea

son=reboot

and I'm currently using the "Android Composite ADB Interface" Rev8 driver from the SDK on Windows 7 x64 along with the 18.0.1 version of the platform tools.
[Nexus 4 Q&A, Help & Troubleshooting] Cream$ickleHJ:
Did you download the fastboot.zip and place it in platform-tools of the android SDK?

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] DaemonDign:
Try the SDK package ..
[Nexus 4 Q&A, Help & Troubleshooting] apopberz:
I'm using the fastboot binary from the SDK as stated in the OP
[Nexus 4 Q&A, Help & Troubleshooting] marsdta:
I know this may seem obvious but covering the basics. You installed the fastboot driver? Is phone seen at all via device manager?
[Nexus 4 Q&A, Help & Troubleshooting] apopberz:
Do you mean the ADB driver or something else, I've tried the naked ADB driver and the SDK ADB driver, both give the same result, ADB.exe connects, I can open a shell and see the files etc., but fastboot.exe just hangs on waiting for device
[Nexus 4 Q&A, Help & Troubleshooting] marsdta:
When you plug in phone and its in fastboot is it recognized by device manager? Do you see an exclamation point next to it. If so you have to click and choose update driver(I used sdks version)
[Nexus 4 Q&A, Help & Troubleshooting] apopberz:
No problem there. I don't think ADB would work if the driver weren't working would it?
[Nexus 4 Q&A, Help & Troubleshooting] marsdta:
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.

Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
[Nexus 4 Q&A, Help & Troubleshooting] Andre_Vitto:
Delete.. Dndnt read OP properly.
[Nexus 4 Q&A, Help & Troubleshooting] apopberz:
Yes I've reinstalled the driver a few times and tried different drivers. I've tried the universal naked 0.72.the rev8 from the SDK and Koushes, all 3 work with adb and none worked with fastboot
[Nexus 4 Q&A, Help & Troubleshooting] apopberz:
Which driver did you use in the end? I've tried just about everything, I even grabbed another nexus 4 and I'm having the same issue with that one (which is on the earlier 4.3 OTA update btw)
[Nexus 4 Q&A, Help & Troubleshooting] Cream$ickleHJ:
Download the fastboot.zip and place it inside platform tools, even though SDK shows fastboot download fastboot again and place it inside

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] apopberz:
Download from where? Which files do you suspect are missing?
[Nexus 4 Q&A, Help & Troubleshooting] marsdta:
I used the one from the SDK. When booted up device manager shows adb composite and when in boot loader device manager shows android boot loader interface.

When you are reinstalling the drivers did you uninstall them first. That's what I usually do. Once helped someone who had the driver installed several times, so they were conflicting . I would uninstall drivers and delete any mention of them. Reboot PC. When plug in phone I ignore it trying to search and install boot loader driver. And install it manually
[Moto X Q&A] Joey766:
Walked out of the AT&T store with a new Moto X today. So far so good but I only use

three "home screens" and for the life of me I can't figure out how to delete the empty

two pages. There doesn't seem to be a pinch action to get to the edit screens page...

This is my first foray into the Moto world, does anyone know whether this is possible?
[Moto X Q&A] martinezma99:
I couldn't figure it out so installed Nova launcher. I feel like some settings seem to be missing but it may be because I'm so used to custom ROMs.
[Sony Xperia P, U, Sola, Go] toxic21:
Hi,

Can i flash This stock .ftf on my sony xperia go with locked bootloader ?

Thanks in advance.
[Sony Xperia P, U, Sola, Go] iamdchosen1:
Yes, you can flash this!

Locked bootloader or unlocked, ftf file can be flashed regardless..