yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] Diazz72:
Well i think all stuff rom this thread are fake, like i sad before guys from Samsung DE. sad that they do not install lollipop on repaired devices.

We all know that all this could be easily faked.
[Galaxy S 4 General] hertzschi:
del
[Galaxy S 4 General] :
Have nothing to d if a German scc they are not getting info from it

---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------

Build prop is fake
[Galaxy S 4 General] SGN4SD:
Well enjoying my lollipop on N910F and for now a put my s4 away until it's time.
[Galaxy S 4 General] mrclaver:
Dear ++chris++,

here's my proof that I am working as a retail salesmen for mobilphones and contracts like Vodafone Telekom Otelo Congstar blau etc.

And yes we send the repairs from our customers to service centers like w-support.

Unfortunately I'm on vacation right now but next week I am able to call that center to ask them if they are already update GT-I9505 lollipop

Google the company i work for and compare our names from here and on that picture. Honestly I was really surprised when you uploaded that Video and i hope that you're not lying about that.

Seems legit for me that video and if you're really right I apologize for bothering you.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
Hi all, i am stuck, i need the help of the experts in either saying my 2 Qtek 9100s are bricked - chuck them or, they are retreivable.

Here goes:

2 X Qtek 9100 made by T-mobile - emei if needed.

Both devices stuck on the boot screen, but will both go in to Tri colour screen for flashing, but fail flashing (with several roms), i think they have button rom, its a beer glass.

GSM: - 01.12.10

OS: - 1.5.4.2

ipl 1.01 and spl 2.24

Can these be revived?

Thanks.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] hanmin:
A Wizard by T-Mobile is a "MDA Vario", you can't have a Qtek9100 by T-Mobile. Anyway..

Have you tried flashing official ROM while they are in bootloader mode (tri colour)? Does the flashing process went smoothly? Does the IPL/SPL change when you flash the latest ROM? Give more info.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
More info

At present both of them are stuck on the info below, i cant reflash them with anything else now.

Official T-mob rom 2.26 will not work...think the error was [239] or something.

Thanks.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] calouro:
sounds like u didn't accomplish step 16 of 'the definitive guide to unlocking & rom upgrading G3 wizards' by Dr Puttingham.

both IPL AND SPL need to be the same
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cuboosh:
what was the exact error.. post the code and error msg.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] bigfatjack:
i got the same problem

ipl/spl 1.01

i tried "CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE"

many many time but nothing :( :( :(

please help
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mfrazzz:
Since your ipl/spl are 1.xx just follow the sticky by Dr. P at the top of this forum. You will start at the step running lokiwiz as you don't have to downgrade. Then upgrade to an official 2.xx rom. After that you can flash a custom rom.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
errors

Various error messages with various roms.

Invalid vendor

Invalid nkbf file

Upgrade only

I believe that these devices were upgraded by a user who perhaps did not fully unlock them.

Is it possible these devices would exhibit these error if they were flashed with a G4 rom, or would they just not boot if that was the case?

Thanks ALL
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Zzan:
Well, the only difference between a G4 and a G3 rom is that the G4 rom will not contain IPL/SPL. If you flashed a G4 rom in a G3 device you are fine. If you flashed a G3 rom into a G4 device then you have bricked your devices.

In your case you haven't finished the unlock/downgrade process. like mentioned above you seem to have missed step 16.

You need to re-flash the button rom to get both the IPL and SPL to 1.01. Once that is done then flash an OFFICIAL carrier rom (T-Mobile 2.26 suggested). When you have completed that then your IPL/SPL will both be 2.26. From THIS point you will be able to flash a custom rom, you will have no success until then. The unlocking guide that is stickied contains everything you need to recover from your situation.

The 2 steps that most newbies forget is to downgrade a second time to get IPL/SPL to 1.01 and after you are completely unlocked then upgrade to an official carrier rom that includes IPL/SPL (note this unlocking procedure is not for G4 devices -- doing this will brick them) Once your IPL/SPL are 2.xx THEN you can flash custom roms.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
Unlocking them

Thanks ZZan, i think though i have actually blown the rom with button, but it does not bring the ipl/spl down to 1.01, it appears to blow the rom and complete 100% reboots and comes up with button Beer glass and goes no further.....

Err help?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Zzan:
Have you tried booting into bootloader and putting your carrier's latest rom back into it? I would suggest this. If all works and you can get completely back into the phone, you could try to unlock again starting from the beginning.

The only way you could have really hurt your device is if it was a G4 before you started, or interrupted the flash process while the bootloaders were being written. I don't think it would even boot up to that screen, or flash to 100% if this were the case though. It sounds like a bad flash from the first button attempt. I would suggest using a carrier rom from the carrier that the phone is locked to to get it back to working status. Once there then you can try to downgrade and unlock again.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
Are they G3 or G4

How do i tell again, something to do with the ipl/spl revisions?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] trojan9x:
You can also try re-downloading the button rom and performing the downgrade again. I have the button rom in my sig. it's possible the rom may be damaged in some way.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] trojan9x:
G3 or G4.. from the wiki

A G3 Wizard will have the following

IPL: 1.xx or 2.xx or 2.xx.00x (Note that this version only has TWO 0's.).

SPL: 1.xx or 2.xx or 2.xx.00x (Note that this version only has TWO 0's.)

A G4 Wizard will have the following

IPL: 2.xx.000x (Note that this version has THREE 0's.)

SPL: 2.xx.000x (Note that this version has THREE 0's.)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
button rom

Any ideas where i can get this rom from?

thanks.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
Ignore me

:-) just seen it on your footer :-)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
It flashes but....

it goes all the way through 100%, reboots and sits on rom boot screen exibiting:

IPL 1:01

SPL 2.24

GSM 01.12.10

os 1.5.4.2

And a nice picture of a beer glass....

Help, should i reflash again? i Have done it 3 times and it still sits on boot....

Thanks.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Zzan:
You said your phone was a T-Mobile phone. Flash the T-Mobile 2.26 rom and see if you can get it to finish booting. If so THEN you can retry the button rom. You are in a corrupt state right now. Whatever caused it, it doesn't look like the button rom is going to recover you from it. Flash the official carrier rom for your phone and get it back to working status first. Once you can use the device and phone then you can go back and start from the beginning of the unlocking thread.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
T-mob original

I have tried T-mob original (RUU_Prodigy_2210206_22102109_021911_TMO_UK_WWE_Ship.exe)

[294] invalid vendor ID

I have tried t-mob (RUU_Prodigy_1060204_105_11210_TMO_UK_Ship.exe) using NoVendorID and nk.nbf from above rom - Flashed 100% complete - rebooted - stuck on Button boot screen (beer Glass) and not booting.

Button itself will flash, with the same result, looks like its doing it then reboot, halt on beer glass.

I have i trully bricked these two? i cant have they flash and go to boot loader surely they would not do this if i had totally bricked them???

Help....
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
T-mob

Weird, it has upgraded the IPL to 1.06 (from 1.04) though, does this mean anything to anyone?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mfrazzz:
is this a prodigy device? The button rom was made for Wizard, I don't know if it works for Prodigy or not.

You are at 1.06 because that last rom you listed is a 1.06 rom (see the numbers after Prodigy?)

If you can get to the boot loader, you aren't bricked, but since this is a prodigy, I don't know what to tell you for doing this stuff. Not sure if these steps work on Prodigy or not.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
Err

Prodigy device? how would i tell, what is one?

Its a T-mobile MDA vario branded device.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mfrazzz:
Ok, I just learned something... Prodigy is the name of the Wiz200. So I guess it is a wizard (sorry, I just saw prodigy in the name of the rom and thought it was a different device, but its the same wizard family).

Ok, so back on track here ;)... So what I'd recommend is you get back to being a working phone, so find the latest version of your carrier's rom and flash that on. Then try doing the button rom again. Again, remove the SD card.

Also when you do the button rom, put it directly in bootloader mode first. and flash it directly to the bootloader (I'm grasping at straws here).
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
Still no joy

It will flash with original Tmob and button, 100%, reboots and sticks on Boot screen (beer glass).

Are these devices dead?

1 of them i tried to flash with faria 8mb and it flashed to 99% and dies, every time and then reboots to boot loader with ruu in the top right hand corner.

Err, i dont mind paying a reward to get these fixed
[8125, K-JAM, P4300, MDA Vario Software Upgrading] anichillus:
try a hard reset

See if it helps
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mfrazzz:
Ok, lets slow down and work on one at a time here (I guess I didn't realize there are two phones).

Forget the Button rom... Can you flash the T-Mobile 2.26 official rom, and will the phone boot? If so, great. You know you can get back to a working device (thats a good thing! ;)). If not, can you flash the Wizard Love rom on this phone and does it work?

Once you get this phone back to a working device, then we can move forward with trying to unlock and do a custom rom, but you have to get back to a working device state. If its back working, then, go out and get another copy of the button rom (don't use the one you have now, I want you to redownload it. Can be from the same link, I just want you to get a fresh copy in case something happened to the one you had). Then try flashing the button rom. If it works, continue on with the CID Unlock guide. If it doesn't report back here with EVERYTHING (all the details, what your IPL/SPL was, what it is now, what happened when you tried to flash, and what it did or didn't do when it rebooted).

As long as you can get back to the bootloader they should be fine.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
faria

um, flashed them both with Faria, both fail at 99% and both reset back to tri colour boot screen with ruu in the top right hand corner.

Neither get to boot screen anymore....

Possibly killed them?????
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
Back to Sq 1

I have flashed them both with T-mob 1.6 rom, and they now go back to button boot screen again? and get stuck....
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mfrazzz:
Dude! Please listen and do what we say, not what you think should be done. You have to get back to an OFFICIAL ROM first. Quit screwing around with Faria's and other custom roms until you get that accomplished. Whether you realize it or not, you are skipping steps and not doing what has to be done. Believe me when I tell you that you have to do things in the right order and it will work. But if you decide to do it how you want, its most likely going to fail (like you are seeing) and you could brick your phones...

So STOP, and go back to my previous post and do exactly as I said. Then when you post back here, instead of giving some short little post, give us INFORMATION. We can't help if all you say is "it didn't work again". Tell us what you tried, what it did, what the IPL/SPL are now, etc...

To get to bootloader, turn off the phone and then hold down the camera key, and turn it on. Then you can try flashing back to an OFFICIAL ROM. Until I've seen you've done this, there is nothing else we can do for you.

Again, this post will help you, but you have to follow it (every single step, and do everything it says):

http://xdaforums.com/showthread.php?t=298613
[8125, K-JAM, P4300, MDA Vario Software Upgrading] hanmin:
*Salute mfrazzz for his patience.

I would have gave up before the flashing goes 2%. It seems many thinks that either we have psychic powers or it cost them $$ for each single letter they type.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
i hear you

And and have followed your instructions to the letter, i think i mentioned in one of my earlier posts, i have flashed with 2.X and 1.X official rom and both flash 100%, however upon reboot, they never boot in to the OS and get stuck on the boot screen, which is the Beer glass rom.

So from that i deduce that it has not flashed properely as i am pretty sure T-mobile dont use that boot screen :-)

So, if they dont work surely i am entitled to have a go at other roms and see the outcome?

As i say above Official ROMS do not work on this device.......

I appreciate your patience and the fact you have not told me to xxxx off, however if the official ones dont flash on these devices, what do i do?

I cant get these devices to boot on ANY rom official or not.

thanks.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] lokidan:
ipl/spl

Device 1: ipl 1.06

spl 2.24

device 2: 1.01

spl 2.24

both get to tri colour boot screen if selected, both stop on initial boot screen.
[Moto E Q&A, Help & Troubleshooting] nilanko:
I have hard bricked my device XT1022. I have no other phone now.

All I wanna ask is.. can anybody provide me the blankflash files for XT1022 Moto E?

Or is my device gone forever?

Please help :'(

I'm dying :'(

Life is impossible without a phone and I'm a student and I dont earn so I cant buy a new one either :'(
[Moto E Q&A, Help & Troubleshooting] Adarsh1998:
Flash stock ROM using fastboot
[Moto E Q&A, Help & Troubleshooting] kailashrs:
LOL..........Same here...........Ur best bet is to take ur phone to a service centre.......Most probably, they won't check if u have voided ur warranty (Based on the experiences of a few Moto G owners who did the same with their phones and got them bricked)......Tell them that ur phone became like this after an update and they'll fix it for u, I guess.........Try and tell me :).....I'm planning on doing the same :):) Missing my phone :crying::crying::crying:

---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------

The phone won't turn on.
[Moto E Q&A, Help & Troubleshooting] nilanko:
Thankyou for the suggestions dem0nicbl00d. I have talked to the service center owner and he asked me to come on Monday as tomorrow is a holiday.

Another thing is that, I followed http://xdaforums.com/moto-e/development/unbrick-hard-bricked-moto-e-t2974093 this guide and after doing this, the computer doesn't even detect the phone as qhsusb_bulk anymore. It just shows that an "unknown USB device" is connected. I tried re-following the same guide and re-ran blankflash but now all it shows is "waiting for device" which means that even if I get the required blank flash files, it'll be impossible to flash them as the phone is completely dead.

Is the phone really dead now? I mean can't it ever be switched on again? Can the android phones die forever this easily? I mean is it really *impossible* to do anything and get it running ever again? It's unbelievable that there's no other way. And I dont think the service center guy would magically turn it on some or the other way as I am 99.99% sure he's not that awesome of a geek.
[Moto E Q&A, Help & Troubleshooting] kailashrs:
Exactly my situation:eek::eek:......I don't think they'll try fixing it.........They'll most probably just give u a replacement

And FYI, that guide links to tools that are supposed to be used for Moto G and are also so outdated that they don't work on Lollipop->KitKat downgrade bricks anymore............

Also, if anyone can point me in the direction of the FileFactory folder for Moto E, that would be helpful :)

---------- Post added at 04:15 PM ---------- Previous post was at 04:08 PM ----------

And [MENTION=5888184]nilanko[/MENTION], it would b awesome if u cud share ur experiences with the service centre guys:):)..............Situations says I won't b able to get the nearest service centre till Friday............
[Moto E Q&A, Help & Troubleshooting] Deleted member 5225837:
Can you go to boot loader???
[Moto E Q&A, Help & Troubleshooting] nilanko:
If they provide a replacement, I would say I am the luckiest guy alive-- but alas, I hardly have any hopes.. I don't think that if they send it to the company for replacement, they'd replace it just like that. I don't regret rooting as Moto E is pretty much useless without rooting with its mere 2.1 GB free space it offers.

And by the way, if they do send it to the company, where are they gonna send it? To flipkart? And how long will it take.. I mean how long do I have to forget that I used to have a Moto E before the company says anything? Any idea from your mates who have done the same?
[Moto E Q&A, Help & Troubleshooting] kailashrs:
No idea but,

(not my buddy....just a random lucky guy:):))

---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------

Nope...........Well, warn whoever u know who owns a Moto E not to downgrade from Lollipop to 4.4.2 and then update to 4.4.4
[Moto E Q&A, Help & Troubleshooting] Deleted member 5225837:
Haha

Well I just did

Was on lollipop

Installed twrp (may be did some mistake) and then my phone stuck at boot animation. No further progress.

Went to boot loader and flashed the stock 4.4.4 firmware and again updated to lollipop.
[Moto E Q&A, Help & Troubleshooting] kailashrs:
I mean downgrade to stock 4.4.2 factory image and update via 4.4.4 OTA

And can u link me Moto E's FileFactory folder ??
[Moto E Q&A, Help & Troubleshooting] nilanko:
dem0nicbl00d, yeah I would tell ya but I am gonna be dead if they return my dead phone back to me. I don't have money neither are my parents going to gimme 1 buck for another phone. Now using Nokia 6030.. I am telling in advance that I'm gonna be actually dead.

dhruvmu, no nothing. Phone does not turn on any more in anyway. I tried all possible combinations of key-pressing-- nothing works. It's totally dead. Not even the computer detects it as qhsusb_bulk anymore. It's just a dead unknown device which even the computer cant communicate with anymore.
[Moto E Q&A, Help & Troubleshooting] Deleted member 5225837:
I used this.

http://xdaforums.com/showthread.php?p=56871696

Its stock 4.4.4 Asia retail xt 1022

I think if u can go to boot loader then reverting to KitKat is possible. I just did.
[Moto E Q&A, Help & Troubleshooting] kailashrs:
Wish I'd found this image earlier...............Thanks anyway :)
[Moto E Q&A, Help & Troubleshooting] Deleted member 5225837:
I think the battery might be down.

Charging it might let u go to boot loader.

I have hard bricked my xperia ion a no of times and recovering it a tough job. Requires full charged battery to go to fastboot which takes 36 to 48 hrs. Notification led helps.

But dont know whether with charging the moto e you will be able to go to boot loader. Never faced anything like this.
[Moto E Q&A, Help & Troubleshooting] nilanko:
Thanks for all this. You gave me some hope. But I know I am unlucky. I hope they replace the mobo or something.

I never knew 5.0.2 -> 4.4.2 -> 4.4.4 would lead to the phone's death and would require the hardware to be replaced. This is really weird.
[Moto E Q&A, Help & Troubleshooting] kailashrs:
Nothing is wrong with the hardware actually.......If we just had the necessary tools, the fix is just a few clicks away...........Like flash the bootloader, the flash the stock ROM n then voila.........But unfortunately for us, the tools are unavailable :(

And I'm pretty sure u'd b able to get it replaced for free..............Like that guy.......
[Moto E Q&A, Help & Troubleshooting] panart:
Basically it was not 5.0.2 -> 4.4.2 -> 4.4.4 that bricked your device. I remember reading on XDA forums (i don't remember the exact posts) that once you upgrade from 4.4.2 to 4.4.4 you should never try to go back to 4.4.2.
[Moto E Q&A, Help & Troubleshooting] Brawn_Sg:
wait

One thing can only help u

Waiting till mbm ci 5.0 for moto e is not released

When u downgraded to 4.4.2 I hope u did it without flashimg gptand motoboot

Were there screwn flickering issues

Many moto g owners also bricked their precious while applying ota from 4.4.2 to 4.4.4

So we are waiting for singleimage.mbn

Press thank if I helped
[Moto E Q&A, Help & Troubleshooting] kailashrs:
I did'nt have issues with 4.4.4->4.4.2 except that gpt n motoboot failed to flash..........AFAIK the updated bootloader in Lollipop does not allow the KitKat kernel to boot and like during 4.4.4->4.4.2, does not allow being replaced by an older bootloader version and typically, the phone's bricked...................

---------- Post added at 05:04 PM ---------- Previous post was at 05:01 PM ----------

During factory image flashing, I was able to cancel flashing those two........But the 4.4.4 OTA went ahead and did that, typically screwing my phone................I'm just gonna get to the service centre , say my phone just went poof n get a mobo replacement or something;);)

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

I recall someone telling singleimage can be dumped easily from another phone..........It's the programmer.bin that's missing
[Moto E Q&A, Help & Troubleshooting] panart:
When i downgraded 5.0.2 (XT1022) to 4.4.4 (XT1021) i got the gpt and motoboot fail but all the rest of commands succeeded and i was back to 4.4.4 without any issues.
[Android Software Development] slavenvrhovac:
Hi i opened this post because i have that problem and i cant solve it.

My device:

Huawei G630-U20, stock Android 4.3 Jelly Bean B127.

When i connect my device to TV with via usb and i enable USB Mass Storage on my phone, my phonr unmounts sd card and i can only access internal storage. So i cant view images and video from sd card on TV.

I also have Allview viper v1 and it has kitkat. On it i can view staf from sd card on TV via usb when USB MASS STORAGE IS ENABLED.

So my quastion here is, how to enable sd card when i connect my Huawei G630 with android 4.3 Jelly Bean to TV via usb???

Thx in advance
[Nexus 6 Q&A, Help & Troubleshooting] Jon.StatiK:
Adb and fastboot don't recognize phone. I've made sure I installed the correct jre and the SDK is installed at the latest version with the addons needed for it.

Am I missing something?
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
how about the nexus 6 or adb driver? is it installed? computer wont see your phone without it.
[Nexus 6 Q&A, Help & Troubleshooting] Jon.StatiK:
I figured it out. I had to uninstall the adb driver then install it manually pointing it towards the adb folder. Thanks though!