yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] blesal:
Nobody?
[Android Q&A, Help & Troubleshooting] blesal:
Please...
[Android Q&A, Help & Troubleshooting] Newthorn:
Stuck?

Next to the power button you will see a very small hole. Use a paper clip (make sure no power supply is connected) push gently until the device shuts down
[Micromax A110] vaiibhav:
Micromax A114 got stuck on logo after root,moreover my phone's (-)volume key is not working.Is there any other way of factory reset.plz plz tell asap,thanks
[Galaxy S III Q&A, Help & Troubleshooting] pahlevy:
Im running Jelly Bean 4.1.2 stock rom and no sim card error already occurs randomly last few weeks ago.. its usually happened when my phone was restarted from charging due to out of battery.. Its usually able to detect my card again after couple of cold restart or taking out and putting my SIM card back to the tray.. But several days ago i forgot to charge my phone and went out of battery, after fully charging i started the phone and it show no SIM card error again..

So I have try regular solution for this problem since it wasnt the first time happened. but it never get fixed. In additional, i have try several solution and test i found on the net such as:

cleaning my SIM card with pencil eraser

checking with other SIM card which is no detection also

put some paper on the back of my SIM card

flashing modem via odin

wipe cache, partition and factory reset

change my SIM and SD card tray

All above really didnt do any good for my phone.. Do you think that i still have chance to use this phone..? I still have one solution left that i didnt try yet.. Someone said that reheating the IC and SIM connector will works.. will this be worth to try since it looks like a job for skillful guy with hot air gun or solder..

should i give up now... or did i missed something..?
[P3300, MDA Compact III  upgrading etc.] Awais:
JUST recieved a orbit stuck in bootloader

The boot loader says

IPL 3.04.0001

SPL 3.04.0000

is there any way to unbrick this set

USPL is not working cuz its stuck in bootloader and cant conect with active sync

i have also tried sd card image but image is also not working

(flashing through sd card does'nt starts )

what it could be???
[P3300, MDA Compact III  upgrading etc.] Technoboots:
If I remember correctly, if you get a copy of the original ROM for your phone you can flash that from the bootloader. I'm not sure how to exactly though. I think you load the phone to the bootloader, then connect to the computer. Next I think you run the ROM update utility for the original ROM, this does'nt require activesync. I'm not 100% sure of this since I have'nt had to do it myself, but I found information in other posts on this forum. Run a search for Bootloader in the artemis section and you should find more information.
[P3300, MDA Compact III  upgrading etc.] Awais:
i have tried that too

but not working
[P3300, MDA Compact III  upgrading etc.] Firebirdapache:
I did this last week. I downloaded the WM6 update from the o2 xda website. I left the phone on the bootloader screen and rean the download from the PC. It re-installed the WM6 rom without activesync. You need your Serial number from off the phone.
[P3300, MDA Compact III  upgrading etc.] fdp24:
not flashing or not booting after flashing with original rom?

try another rom with same model id.

regards,
[P3300, MDA Compact III  upgrading etc.] Awais:
yes not flashig even i have tried from card

but its able to sync with the pc in bootloader mode (but not with active sync of course)

i have tried these roms

Arteimg.nbh (through card)

and these through windows

HTC_P3300_GER_3.13.407.1_4.1.13.44_02.94.90_Ship_R.exe

ARTEMIS_Black_Blue_v2.zip
[P3300, MDA Compact III  upgrading etc.] fdp24:
please send error message and your device model id.

regards,
[P3300, MDA Compact III  upgrading etc.] Awais:
hi and sorry for answering late

i am actually away from office now and that set from the customer is in my office

i thought that invalid vender id error in the end of ruu update

i will check again and post screen shots
[P3300, MDA Compact III  upgrading etc.] Awais:
OK

here is the error i am facing

and when press the send button to hard reset

it says "format failed"
[P3300, MDA Compact III  upgrading etc.] fdp24:
- try to flash device while in bootloader (there will be no activesync connection, but it is not a problem);

if this will not work either, try to flash from another PC;

also perform set 32 command from mtty console to see what is your model id.

regards,
[P3300, MDA Compact III  upgrading etc.] Awais:
i have tried on 3 different pc's

here is what i got after set 32

set 32

+ SD Controller init

- SD Controller init

+StorageInit

SDInit+++

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

CMD55 failed

+ SD Controller init

- SD Controller init

+StorageInit

SDInit+++

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

CMD55 failed

g_cKeyCardSecurityLevel = FF

HTCE

Cmd>
[P3300, MDA Compact III  upgrading etc.] Awais:
and now i put wm5 o2 orbit image in the sd card and in mtty set 32

gives this

set 32

+ SD Controller init

- SD Controller init

+StorageInit

SDInit+++

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SD clock to 24MHz

***** user area size = 0x3C8C0000 Bytes

SDInit---

SDInit OK

g_cKeyCardSecurityLevel = FF

HTCE

Cmd>
[P3300, MDA Compact III  upgrading etc.] fdp24:
in mtty:

Cmd>password BsaD5SeoA

Pass.

+ SD Controller init

- SD Controller init

+StorageInit

SDInit+++

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SD clock to 24MHz

***** user area size = 0x79E80000 Bytes

SDInit---

SDInit OK

g_cKeyCardSecurityLevel = 0

HTCEType (0x1)(Operation mode flag): cOpModeFlag=(0x0).

Type (0x2)(Back color flag): cBackColorShowFlag=(0x1).

Type (0x5)(Background color value): g_wBColor=(0xC618) (0xC0C0C0).

HTCST

Cmd>getdevinfo

HTCSARTE10000àyqHTCE

Cmd>

look at your model id.

open nbh file with hexeditor, look for offset 00000040 for model id.

make sure model of device match with model in nbh. otherwise it will not flash.

have you tried to flash another device (same model id) with nbh file you have.

maybe you have corrupted file!!

regards,
[P3300, MDA Compact III  upgrading etc.] Awais:
OK I DID THAT

i find my id

Cmd>password BsaD5SeoA

Pass.

+ SD Controller init

- SD Controller init

+StorageInit

SDInit+++

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

CMD55 failed

+ SD Controller init

- SD Controller init

+StorageInit

SDInit+++

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd1 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

SDCmd55 Command response time-out. MMC_STAT = 80

CMD55 failed

g_cKeyCardSecurityLevel = FF

HTCEType (0x1)(Operation mode flag): cOpModeFlag=(0x0).

Type (0x2)(Back color flag): cBackColorShowFlag=(0x1).

Type (0x5)(Background color value): g_wBColor=(0xC618) (0xC0C0C0).

RUURUN fail

HTCSF

Cmd>getdevinfo

HTCSARTE20000€zÁjHTCE

Cmd>

and now i am doing this rom

ftp://ftp.xda-developers.com/Uploads/Upload/Official XDA Orbit ROM UK TEST/

RUU_Artemis_O2_UK_1.25.206.1_02.67.90_Ship_R2.nbh

given by WolfDac

here

http://xdaforums.com/showthread.php?p=1681205#post1681205

and he said its official orbit uk rom

but the rom upgrade utility in german

and this rom is also not working for me

my device info is this

Cmd>getdevinfo

HTCSARTE20000€zÁjHTCE

Cmd>

and in the offset 00000040 my rom (in hex) ARTE200

where is the model id in my mtty pasted data????
[P3300, MDA Compact III  upgrading etc.] Awais:
no i dont have any other orbit (yet) to check

i had purchased from customer

and he said its from uk

no, my file is 100% ok,,, i am sure cuz i download that nbh image from three different hostings three times, same size and same file

o2 provides xda orbit in how many countries ???

may b i should try some other files, instead of germany and uk

from where i can get other files ???

i am very thankful for your co-opertation
[P3300, MDA Compact III  upgrading etc.] Awais:
waiting for the answer
[P3300, MDA Compact III  upgrading etc.] Awais:
i was messed up

so i opened my orbit, and the board was perfectly fine (new), i opened in the confusion that it may be water damaged or some thing like that.

but my doubt is clear now, there is no hardware problem in this set, it is sure that i need a factory rom for this but still not able to find out that from which country O2 provided that set???......
[P3300, MDA Compact III  upgrading etc.] fdp24:
i was saying about change of model id nbh file assuming that device is cid unlocked. if not it will not work, because if you made a change, you need to sing nbh file with htc certificate, otherwise it will not install.

you know your model id, search internet and install corresponding rom for arte200.

regards,
[P3300, MDA Compact III  upgrading etc.] Awais:
what exactly is my model id i have pasted details of mtty obove

would you please tell me that which rom i should try now???
[ZTE Axon 7 Questions & Answers] malditos:
So this is probably one of the stupider questions on this forum but my Axon 7 won't let me choose "None" for the lock screen unlock. When I go into the security settings I only have the option of "Pattern, Pin or Complex Password" but the Swipe and the None options are greyed out. They read they are disabled by the administration, encryption policy or credential storage.

My device admins are only two programs, none of which are the lockscreen. I never installed any credentials and the phone is not encrypted...

I know that whatever it is, it's starring at me right in my face but I can't figure out what it is. :confused:

Help.
[ZTE Axon 7 Questions & Answers] DrakenFX:
The Axon 7 as far as I know is Encrypted out of the box and when you setup any of the security lock screen, the only way to get it back to none is doing a factory reset and not enabling any of the security lock screen.
[ZTE Axon 7 Questions & Answers] malditos:
Didn't realize the phone encrypted itself when a security measure was done. Good to know. Thanks.
[ZTE Axon 7 Questions & Answers] peramikic:
The phone encrypts on start up, it just uses default password and in such case can decrypt itself always. Once you set a security meassure, this password gets encrupted again with your key. This way the original key is always used for decrypting so that FS is not in need of decrypting/renecrypting on pass/pin change.

As far as the admin lockout. If you have setup exchange email account for instance, it has enforced the security method on you and will not let you remove it while you have account setup. Also, those admin apps can enforce security model of their own as well, so i would look at those as well.
[Xperia Z3 Q&A, Help & Troubleshooting] xkeita:
On previous releases like Lollipop in /system/vendor/ there was a folder called overlays which was useful to create overlays for various apps without having the need to edit them, but on Marshmallow looking through the files I saw that the folder was no longer there. Does the overlay theming system still work on marshmallow or it's gone?
[Nexus 5X Q&A, Help & Troubleshooting] justingriff:
Been running dev preview and now I got the full meal deal, but I swear battery life is worse an phone lags more. Anyone else have this experience?
[Nexus 5X Q&A, Help & Troubleshooting] ljfnky:
I haven't noticed it on my 5X.
[Nexus 5X Q&A, Help & Troubleshooting] iamterence:
Not at all. Phone runs better for me. Maybe you should try doing a factory reset.
[Nexus 5X Q&A, Help & Troubleshooting] justingriff:
That's the plan once I have time. Might just be in my head if no one else has noticed!
[Nexus 5X Q&A, Help & Troubleshooting] tpb482061:
Factory reset and give it a few battery cycles.
[Nexus 5X Q&A, Help & Troubleshooting] Evo_Shift:
Maybe that's why the factory images still aren't available. Maybe Google discovered some issues. Technically anyone running N should still be in the beta program.
[Nexus 5X Q&A, Help & Troubleshooting] justingriff:
Is that a general suggestion or what you did?
[Nexus 5X Q&A, Help & Troubleshooting] revamper:
Always try a factory reset before assuming the worst.
[Huawei MediaPad M2] wmoore:
I'm running this ROM (after bricking my device and trying just about every recovery method possible). I had 2 oddities with it. The first one may have just been coincidence but it wouldn't keep the Play store open for more than a few seconds. I cleared cache, data and everything else but in the end had to sideload the Play store APK to get it to work. I think Play Services must have updated before the Store so then the store was incompatible and crashed.

Secondly, my smart cover no longer works. If I open the cover the screen lights for a few seconds but doesn't respond to touch. Then if Ihit the power button, it takes about 8 seconds but then still isn't responsive. Repeat and then it comes to life. Take it out of the case, no problem. Disable smart cover in settings and we're good. As far as I can tell, there is a specific smart cover available in Asia for this device but it is no good with a generic one. The original ROM worked fine with my cover.

I have contacted Huawei support asking for a link to the Aussie ROM but a week and several back and forth emails later, they haven't told me anything. Apparently they have escalated my call and a senior will call me back.
[Huawei MediaPad M2] beast.in.black:
Hm. I've been using this ROM for a while now and haven't noticed any such issues (I'm using a generic smart cover I bought off the US Amazon site). How exactly did you flash this ROM? What were the exact steps you used? I ask because I think what may be happening is that you may possibly have bits and pieces left over from your original aussie ROM that is experiencing some culture shock with the Taiwanese bits of this ROM :)

At any rate, what I would recommend to try to fix your issues is to reflash the full ROM again, with the original Huawei BOOT and RECOVERY partitions of course (it'll still keep all your data and apps, don't worry, I've done this a few times now in my R&D):

If you're rooted, remember to unroot first

If you have a custom recovery like TWRP then remember to flash the stock recovery and boot partitions back first. Let me know if you need to know how to get these partitions or how to flash them.

Stick the "dload" directory of this ROM directory back on to your SD card, access the Updater, choose the "Local Update" option and update from there. It should reboot into the Huawei recovery and flash the full ROM, which (I think) is all partition images contained in the UPDATE.APP for the ROM).

Let the ROM reboot. It should now say that its "upgrading" your apps. After a bit, if you access the updater, you should see a "B003 to B005" OTA update available which is about 256 MB. Select to download and install this update.

See how it behaves after this update is installed.

As a final cleaning step, reboot into the recovery by first shutting it off and then pressing the power button with VOLDN pressed simultaneously. In the recovery menu, select the "Clear cache/Dalvik cache" (don't remember exact wording because I pretty much immediately flash the latest TWRP for this device), let it clean the cache, then reboot and see if your problems go away.

I've been running this ROM in the US on the AT&T network quite troublefree (except for AT&T outages) ever since I first flashed this ROM - all my subsequent troubles are usually caused by my messing around with it trying to learn stuff by poking around where I don't belong :cyclops:
[Huawei MediaPad M2] wmoore:
I suspect you're right. As for how did I flash this ..... Truth is there is no way I could recreate the steps. I wrote about it in the "help I've soft-bricked ..." thread. It was more a matter of luck that judgement that I got the tablet recovered.

I'll give this a go though and see what happens. I wasn't aware there was a newer ROM than B003. Mind you, I've been trying to get some information from Huawei for over a week and have finally given up. Huawei says speak to Vodafone, Vodafone says speak to Huawei.

---------- Post added at 03:19 PM ---------- Previous post was at 02:55 PM ----------

When I tried to run the update from SD card, it gets to about 75% and then tells me the update failed. I reboot and come straight back to where I was before.

In my bootloader I have "FRP Lock" which I believe is to do with password / PIN lock. However I cannot remove those as "something" is holding on to them. I removed my company Exchange account and deactivated the Google "find my phone" administrator. But I;m not sure what else is hogging it, or even if this is the actual problem.
[Huawei MediaPad M2] beast.in.black:
Fair enough. I did see your post there, but there wasn't enough detail for me to go on.

If you're feeling brave, you can try a fastboot erase and manual flash of the SYSTEM partition from the OEM Taiwanese ROM (as I had outlined in the other thread), before you try the full update again (but see below).

I also wonder: to solve what I strongly suspect are "chimera ROM" issues due to an incomplete original flash which initially resurrected your phone, whether perhaps you might need to manually flash one or more of the other partition images present in the Taiwanese ROM's UPDATE.APP (I'm just taking a SWAG here) to allow a subsequent proper update process to work:

MCUIMAGE.img
CUST.img
USERDATA.img
SENSORHUB.img
TRUSTFIRMWARE.img

Unfortunately, there is practically no information available on what any of these Huawei partition images are for, so it's pretty much "take a guess based on the image name", which may or may not be what one thinks it is, especially given that Huawei is a Chinese company, with all the attendant language issues that can exist in such a scenario.

The B003->B005 update is not a full ROM, it's just a 250MB partial update which is only available OTA, as far as I know. The only full ROM (2.5GB) currently out in the wild for the M2-802L seems to be the B003 ROM (or at least, it's the only one I've found in about 3 weeks of frantic searching).

Bloody typical. I had sent Huawei more than a few emails asking for the bootloader unlock code, as well as several frantic emails begging for the 802L ROM when I had accidentally messed up my own factory ROM due to the TWRP+SuperSU interop glitch. All I got from them was the written equivalent of "P*$$ off" from Huawei's US support as well as China support, so I said "Eff these guys" and just paid the DC-Unlocker guys 4 euros for the privilege of getting the unlock code, which was fast, painless and efficient. I then figured that there had to be an 802L ROM available somewhere, and I spent about 2 weeks going through all of Huawei's international channel support sites until I found it in a single place: the Taiwan site.

Actually, the FRP lock is controlled by the Developer option "Allow OEM Unlock". If you have developer options enabled, it should show up in your settings, under the "System" settings menu (see attached images).

However, even if your FRP is locked it should not prevent you from flashing the official Huawei image. Could you post the recovery log of the failed update? The recovery log of the OEM Huawei recovery is located at

/splash2/recovery_log

on your internal SD's filesystem, so you can maybe use adb or a file manager on your phone to get it out of the phone to post it here. I don't know if I have a matchstick's chance in Nordic hell to find what the issue is, but I'm willing to take a look...
[Huawei MediaPad M2] wmoore:
First problem is I don't have Enable OEM Unlock in dev options.

When I try to flash TWRP, I get

Bootloader says PHONE Unlocked and FRP Lock but it seems to me that my bootloader is locked, as I cannot do anything at all with it. If I try fastboot oem unlock, I get:

I'm running Linux so the DC Unlocker tool won't work. I might have to find a Windows machine to try that.
[Huawei MediaPad M2] beast.in.black:
Hmmm... what is the exact output of

fastboot oem get-bootinfo

for you? It is possible that your "Phone unlocked" message may be bogus like it was for the original poster of the "softbricked" thread, although I have no explanation for how that situation came to be. And not having the "Enable OEM Unlock" option in your dev options is deeply disturbing and more than a little suspicious...

SAY!!!! Hang on a bit!! I just realized something: Your reply in the softbrick thread (which the original poster created for the 803L) said that you downloaded the ROM which I had linked in this thread....but my ROM is for the 802L, which is the model I have.

Now, here are the specs from the Huawei site for the 802L and 803L:

M2-802L
GSM:850/900/1800/1900MHz
UMTS:850(B5/B19)/900/1700/1800/1900/2100MHz
LTE -FDD:Band 1/2/3/4/5/7/8/19/26/28;
LTE -TDD:Band 41/40
WLAN:2.4/5GHz

M2-803L
GSM:850/900/1800/1900MHz
UMTS:850/900/1900/2100MHz;TD-SCDMA:Band 34/39;
LTE -FDD:Band 1/3/7;LTE -TDD:Band 38/39/40/41
WLAN:2.4/5GHz

I have a very important question for you: Is your phone an 803L or an 802L?

This is of prime importance because they have different radio hardware (for starters - see the specs above; there might be other hardware differences)!

Due to this different hardware, the contents of the important partitions that contain the low-level kernel drivers and other ancillary information related to configuring and operating them will be totally different for the two different models! That is why I left the OP in that thread to his own devices using his own ROM - because the 802L ROM would be totally unsuitable at a low-level device-driver level for his phone!

Now, if your phone is indeed the 803L, then much becomes clear!

Consider: If you've got a partial flash of the 802L ROM on your 803L, that would likely explain your strange issues with the smart case etc. In fact, I'm surprised that you aren't having more and deeper issues, but likely the "Failed" update in the Huawei recovery is what is actually saving you from catastrophe here: it's actually refusing to flash the low-level partitions that deal with the hardware at the device layer and which would seriously damage your phone and hard-brick it if the flash actually succeeded.

In addition, if your phone is an 803, that would also sort of explain your weird "Phone unlocked but FRP locked" state that no one but you and the OP in the softbrick thread are reporting - one might draw the conclusion that there is some ROM bug (which especially shows up when one is trying to unlock the phone) in the 803L which is causing this behavior.

As an aside, I'm now also wondering if the poor OP in that thread is also an aussie with a Vodaphone-flogged device...
[Huawei MediaPad M2] wmoore:
Yeah mine is definitely the m2-802l. And I think your right about the bogus unlocked notification in the bootloader. My plan at the moment is this:

1 Get rid of the FRP lock. I found an article describing how to do it. Basically remove all Google accounts, then wipe / factory reset.

2 Get an unlock code and try unlock bootloader with fastboot and / or dc unlocker on a windows PC.

I'm not at a computer at the moment but I suspect the result of the command you mentioned will be "remote: command not allowed". Most fastboot command give me that. I'll test the theory shortly.