yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] gabriel32mty:
I have the same issue, but it seems likes nobody knows the answer or they dont care

i also have a thread open about this

:(
[Moto G Q&A, Help & Troubleshooting] sukhi10:
I'm having the same problem, did anyone get there's resolved, I have done a factory reset but still phone is stuck on the M screen,
[Moto G Q&A, Help & Troubleshooting] tzzeri:
Flash firmware
[Moto G Q&A, Help & Troubleshooting] gabriel32mty:
i have flash some firmwares the last thing i did was unblock the bootloader and now im trying to install a custom recovery but when i click on recovery it shows me the stock recovery not the custom

what else can i do??? [MENTION=1006674]lost101[/MENTION]
[Moto G Q&A, Help & Troubleshooting] lost101:
Provide the maximum amount of information humanly possible please. All commands used, and any errors.
[Moto G Q&A, Help & Troubleshooting] satanas17:
Hi,

And eventually precise model too!! (XT1032, 33, 39...)
[Moto G Q&A, Help & Troubleshooting] gabriel32mty:
MMM [MENTION=1006674]lost101[/MENTION] what information you need??? i have motog XT1032, cid12, 16Gigabytes

i have flash the custom recovery as usual

mfastboot flash recovery eserecovery.img

the error its on the cellphone says mismatched size of partition and thats all i reeboot again and when i click on recovery it show me the stock recovery instead the custom
[Moto G Q&A, Help & Troubleshooting] lost101:
That error means nothing, ignore it. Flash latest TWRP from here: http://xdaforums.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Firedoug:
I have been searching and have not found anything clear about returning ATT MK2 to bone stock.

I have an ATT SG4 Android 4.3 MK2, I have rooted and used Safestrap to install an additional partition with Hyperdrive 13. All is working well, but I just developed 3 dead pixels sending green lines down screen. Phone is still under warranty.

So can someone direct me to the proper way to return the phone to bone stock? All the guides and Tar files I find are for 4.2 MJF and I don't wish to brick the phone.

Any help would be greatly appreciated.

Doug
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
You didn't look to hard http://xdaforums.com/showthread.php?p=49687770
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Firedoug:
Thanks
[8125, K-JAM, P4300, MDA Vario General] sdrimmel:
Anyone....

The following is a description of what has started happening with my phone - has anyone ever had this problem - and can anyone offer me any advice other then "do a hard reset"? Any help would be greatly greatly appreciated!

Ever since I installed PocketZenPhone on my 8125 I have continually received a message saying “The file ‘PZPTools’ cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. You might need to reinstall or restore this file.’

This actually didn’t happen until I replaced the temporary license with the permanent license that was supplied by the developer.

It gets worse –

Every soft reset I do – the window comes up again – if I don’t hit the ‘x’ to close in time my phone locks up and I have to go through another soft reset

The product actually ran for 3 days after I kept closing this window.

I tried an uninstall and still got message on soft reset

I reinstalled software and still got message

3 days after your software did this – every one of my other 3rd party software programs starting doing the same thing

the phone volume suddenly sounded muffled (can’t turn it up)

all icons for other software no longer show up

If anyone can help point me in a direction that might help me recover from this with out a hard reset I am all ears.

Thanks for taking the time to read and hopefully respond.
[8125, K-JAM, P4300, MDA Vario General] harleyxlc:
Don't have an answer, but the dev has a new site...

http://zendrui.free.fr/PZPForum/index.php
[8125, K-JAM, P4300, MDA Vario General] meschle:
You could disable the security feature for software, but that's not your only problem, so i would suggest a hard reset. You are not the only one with this problem with PZP, shame it's a good progam. ;)
[LG Optimus 4X HD] deownagee:
When is it possible people make AOSP rom of CM11?
[LG Optimus 4X HD] abhi08638:
First off AOSP---> stock android with no customizations

Second CM11 is used as a based off other ROMs.

If you are asking for a build of stock cm11 there's already a thread about it
[LG Optimus 4X HD] black@pirate:
I did compiled a pure AOSP 4.4. But camera doesn't work. I'm uploading it right now, I'll post that in Laufer's AOSP thread, hope he don't mind :D

EDIT: I think I shouldn't. It have no sound at all :P
[LG Optimus 4X HD] laufersteppenwolf:
Hehe, somehow sounds familiar ;) :D

Can you grab me a logcat, I think I have an idea ;)
[LG Optimus 4X HD] black@pirate:
The problem is I didn't cherry-pick all of your commit from 4.3 AOSP. I'll try again with your commits, but I don't know whether it'll be compatible. Is it ok if I just pick sound and bluetooth related patch since recent apps and mobile data, RIL, etc: works. :) Anyway, I'll build a new AOSP tomorow and if there is no sound, I'll give a logcat for you :)

---------- Post added at 08:28 AM ---------- Previous post was at 07:36 AM ----------

@laufersteppenwolf, on a second thought, I think providing you with a logcat and asking advice would be a better deal than messing myself with commits :D So, i flashed my old aosp zip quickly and make two logcats.

Here is when I tried to open music, music just force close. I think I should make changes to audioflinger, probably >> http://pastebin.com/2VEgMVEJ

Here is when I made a call and open speaker >> http://pastebin.com/2VEgMVEJ This also might be cause of audioflinger?

Thz :)
[LG Optimus 4X HD] laufersteppenwolf:
Do you have your used sources uploaded somewhere, as without seing the sources, it's pretty much blind guessing ;) :D

But do you have THIS commit cherry-picked? It's one of the most important ones for audio to work on a tegra device ;)
[LG Optimus 4X HD] Adam77Root:
I had audio without this patch on Omni, but DSP Manager always crashed. :D

Regarding camera: Do you have this patch? Our camera HAL needs it, but doesn't give any usable error to know it's missing.
[LG Optimus 4X HD] laufersteppenwolf:
Well, at least on 4.3 this was definitely needed, but also should be on 4.4. At least on pure AOSP ;)

About DSP, THIS commit should fix it, at least on NamelessROM, which got the according changes from Omni ;)
[LG Optimus 4X HD] deownagee:
Looking good im waiting for it
[LG Optimus 4X HD] deownagee:
Oh and i meant aosp 4.4 no additional stuff i should aprriciate when done.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] SilverStone641:
Hey all. I just converted to the Note 3 from the Note 1 and LOVED the ViPER4Android FX effects. Is there any version available for the Note 3? Or perhaps a similar audio enhancement mod?
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Agent:
Here it is.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] SilverStone641:
Any special install procedures? Or is it similar to the previous method?
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] r333xxh4v0k:
it sounds great on my n3 =]

http://xdaforums.com/showthread.php?t=2191223
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] SilverStone641:
Wow!! That's a MUCH easier installation than I was used to on the N1. Thanks!! :D

May have spoken too soon. Everything installed fine, but neither app seems to have any effect on the audio quality. Investigating.

My fault! looks like I had a setting in PowerAmp that was overriding Viper4. We're all good now and it sounds incredible!
[Xoom Q&A, Help & Troubleshooting] webeougher:
Reserved to answer any questions that may arise.
[Xoom Q&A, Help & Troubleshooting] variatbg:
LTE data still not working

All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.

The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
[Xoom Q&A, Help & Troubleshooting] webeougher:
I've repartitioned multiple times now - once from stock, rooted Jelly Bean, and got no data, then back to standard partition and CM 10.1 with only 3G, back to BigPart with no data, then I followed the steps that I wrote up here and now I'm BigParted on CM 11 with data. So it's not the repartitioning process. I'm a testament to that. What were you on when you did the BigPart process for the first time?

Edit: if you're willing to do the whole process again, would you try installing the very first CM 11 that Schischu released? I should've specified that that's the rom I installed first after repartitioning this time. One I had working data, I updated to the latest version.
[Xoom Q&A, Help & Troubleshooting] Thiago Delatorre:
Help with MZ605 (Everest) stock (step 10 of stage 2)

Thank you very much for your work on the data problem.

I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...

Do you have any idea on how I could force the stock to ignore the first SIM verification?

Thank you in advance!
[Xoom Q&A, Help & Troubleshooting] variatbg:
LTE data still not working

I was first using OmniROM of January 12, though I can't quite recall. Then I also tried CM 11 and no dice there. Following your process, when I first reverted to CM 10.1 on original partitions, data was immediately present again.

It was there through all the reversions to stock 3.2.2, and through every OTA update Motorola sent to the device. In fact, some of the updates wouldn't even show up except over Mobile Data.

One thing that might make a difference is that this Xoom is on a business account through Verizon. It's not part of a shared data plan, but there might be a different categorization perhaps?

Anyways, I'm not going through all that partitioning and flashing again just now. I will though, eventually do a Nandroid backup and try again, once I see here or elsewhere that something might have changed for me. I have spent just too much time on this, and data is more important in this case than KitKat. :(
[Xoom Q&A, Help & Troubleshooting] webeougher:
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
[Xoom Q&A, Help & Troubleshooting] Thiago Delatorre:
Not stupid at all, it could make all the difference!

I flashed the MZ605 Brazilian, MZ601 International and the one you linked. The formers booted and asked for the SIM card and the last just didn't boot. I put two different SIM cards and it didn't work, I was wondering it there were a way to circumvent the first check. I also read somewhere that the MZ601/MZ605 US Retail version didn't check for a SIM card on the first boot, but I didn't find an official stock rom for such a device (I don't even know if these devices exist).

The next trial would be with the MZ600 Verizon 3G, but I'm not that confident that it is gonna work...

Another problem is that I stopped using the 3G data on Xoom for more than one year, so I can't even tell if the SIM card would be recognized nowadays...

Beside that, what choices do we have? Is it possible to avoid the first boot SIM card verification? Is it possible to extract the baseband files from another MZ605 and put them in mine?

Do you know what kind of file/library is the baseband?

Another thing, how the modem stays working if we completely clean the internal storage of Xoom going from the official to the CM11 (on your procedure)? What I'm missing...?

Thank you very much for your guide, I didn't know how to revert the bigPart ;)

Regards,

Thiago
[Xoom Q&A, Help & Troubleshooting] rapson2000:
So [MENTION=1515895]webeougher[/MENTION] ...I FINALLY had some time to sit down with my Xoom and try this. In the interest of verifying that this process works, I went through your guide step by step without deviation and... SUCCESS! I'm back to BigPart CM11 w/ full 4G LTE!!! Thanks for taking the time to write out such a detailed guide! It was just about perfect.

I have just two things to mention... First, the link to the stock image HRI66 didn't work. I had to look elsewhere (http://rootzwiki.com/topic/1586-stock-images/). Also, in step one of stage 4, the adb command should be "adb reboot recovery", not "adb reboot bootloader"... correct?

One last thing, at this point should we start recommending people not attempt BigPart / CM11 if they start from stock Jelly Bean?

Again, I can't tell you how stoked I am to be back up and running. This... all of it... BigPart, CM11 for Xoom, and the fix for the no data situation... it's all awesome.
[Xoom Q&A, Help & Troubleshooting] rmkenney12:
Awesome! It's amazing that somebody was able to figure out the process with all of

it's steps, and have it actually work.

I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!

Thank you!

About the only thing I did differently was to do the "fastboot oem lock" after reflashing the

baseline honeycomb partition images. I always thought you had to have the thing locked before

it would allow you to do OTA updates. Whatever.

I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"

before applying the universal root. Other than the locking & unlocking, I followed your instructions

exactly. Perfecto!
[Xoom Q&A, Help & Troubleshooting] webeougher:
It's not necessary to relock to get OTAs, so long as you're running a pure stock rom.
[Xoom Q&A, Help & Troubleshooting] peterkling:
There was aleady a problem with Step 4... unable to mont /cache - therefore Failed to wipe /data and /cache.

Step 8 also showed NO /data-partition.

I downloaded the original Xoom stock boot,system,recovery (MZ601) MZ601_H.6.1-38-5_TMO_Germany...

boot status - done!

system status - done!

recovery status - done!

userdata status | | | | | | | | | | | | | | | | | | | | | | - done! (there have been such weird lines)

formatting cache: CAC status: -done!

Rebooting - after 60 min of M-logo I quit.

Is there a way to TOTALLY MANUALLY repartition the xoom and recover everything from scratch?

EDIT: New development: not even in fastboot mode I'm able to flash anything anymore... CWM recovery (recovery-clockwork-touch-6.0.3.2-everest.img and recovery-Tiamat-R4c-100611-1150-cwm.img) for example: status done! Still TWRP
[Xoom Q&A, Help & Troubleshooting] semp3rfi:
Thank you and Question

First off thank you this worked perfectly for me, everything worked like it was supposed to! :) Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
[Xoom Q&A, Help & Troubleshooting] webeougher:
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
[Xoom Q&A, Help & Troubleshooting] semp3rfi:
Thank you

Awesome thanks for the reply!
[Xoom Q&A, Help & Troubleshooting] dersh:
What does this whole sequence actually accomplish? Is the problem that we have the wrong radios installed, and this is a way to get the right ones installed? If so is there a way to extract the new radios so that they can be installed directly?

I am just trying to understand the process, and see if it can be simplified.

Thanks much for coming up with a solution. I will try it soon.
[Xoom Q&A, Help & Troubleshooting] webeougher:
I'm no developer, but my best theory is that these BigPart roms and kernels use proprietary files from ICS. By taking the OTA to JB, something changed. I tried flashing other radio files and nothing worked, so when it was suggested that only people who had taken the OTA were losing data, I went through this process just on a whim to see if it worked. When it did, I didn't really think much else about it.
[Xoom Q&A, Help & Troubleshooting] Gwalcmai:
Wow

Talk about a long process but it worked for me! :) Thank you so very much!

I did have an issue with the google keyboard fc on me after going through the whole process but I ended up downloading the go keyboard (not selecting it) and for some reason that took care of the Google keyboard fcing.

I also used the omnirom instead of cm.

Again, thanks for your hard work!
[Xoom Q&A, Help & Troubleshooting] JediMindTrixx:
Wanted to thank you. I pulled out the ole Xoom and flashed Omni and the data wasn't working... But you're instructions got me back on track. Thanks again bro! :good:
[Xoom Q&A, Help & Troubleshooting] vladdracul1431:
A million Thank Yous for investigating this. I followed your process almost to the letter (had to find a different link for the stock ROM and I used CM11 non-BigPart rom) and it worked like a charm. Just to confirm, this worked going to OMNI as you described it (with SU flashed at the same time and gaaps after).
[Xoom Q&A, Help & Troubleshooting] carmelcwxoom:
May I know it will fix the 4GB storage issue? I went through other post but still cannot resume to 32GB storage?
[Xoom Q&A, Help & Troubleshooting] carmelcwxoom:
Hi,

I need some advice.

On stage 1, step 8, under the Mount menu, it only showing my internal storage as 4199MB, is it correct, is it suppose to be 28GB?

One stage 2, step 8, after the flash data commend, I got the error "Partition image is bigger the partition size, Failed to process command error (0x2).

I understand it may related to the stage 1, step 8. I'm flash from the bigpart rom before, which I would like to follow this post to fix the internal storage issue. Any one can help?

I'm using MZ601 HK version.

Many thanks in advance.
[Xoom Q&A, Help & Troubleshooting] carmelcwxoom:
After went though all the steps, I still have the 4GB internal storage only. Any one can give us some hint?
[Xoom Q&A, Help & Troubleshooting] webeougher:
Something isn't working right when you're going through the process to revert to the normal partition. Did BigRushDog and RealJumy ever get BigPart working for the HK Xoom?
[Xoom Q&A, Help & Troubleshooting] r1nstang:
been working on this for awhile now. Took awhile to find a copy of a honeycomb rom for the img files. boot, recovery, and user flash fine but anytime i flash the system.img it fails failed to process command error (0x120000)

and when i try to go on with everything i get hung at the boot logo

got it working using this method

http://xdaforums.com/showthread.php?t=1341834
[Xoom Q&A, Help & Troubleshooting] r1nstang:
sadly worked on this all night. Install all the OTA updates get to the ICS update IMM76L and it restarts and starts installing, then halfway thru the install it goes yellow triangle with ! mark. tried multiple times with no luck at all
[Xoom Q&A, Help & Troubleshooting] gooniegoogoo5:
HELP.....XOOM won't boot into recovery after Step 5

Hey there......

After doing TWRP BigPart and trying OminRom and CM11....i had no data so started this tutorial.

Loaded up all the listed programs on my Memory card and started the process.

Problem is after performing step 5......and then rebooting into Recovery my device is stuck on the teamwin logo.

I have left it alone for ages (like an hour) and nothing.

I did a system reset...chose Recovery manually....and still stuck on 'Teamwin'.

Any help would be greatly appreciated.
[Xoom Q&A, Help & Troubleshooting] gooniegoogoo5:
IMM76L OTA Update step - Android Yellow Triangle

Recovery started working again and ran into another issue........:

In the final update to IMM76L......my XOOM reboots into recovery to apply the ICS update....

It gets halway and then the Android with the Yellow Triangle with the Exclamation Point occurs.

What do I do ???

UPDATE: Ok......tried to do a manual install of the update via USB....same issue.
[Xoom Q&A, Help & Troubleshooting] gooniegoogoo5:
Seems since I reset to Honeycomb........despite 'Activating' device....it is registering only 3G....but not really activating......so once it reaches the point it is attempting to apply Build HTK75D (which is the XOOM 3G CDMA Build)

This is the incorrect Build for the Verizon XOOM 4G LTE (It requires build HLK75D or HLK75H to have IMM76L applied properly??

Does anyone have images of these stock OTA images available?? I cannot locate them for the life of me.....

If I actually go into a full service Verizon store will they be able to apply the proper firmware up to IMM76L??

As the device will be running stock (though unlocked) so I don't see them having an issue with the device

Opinions or advice??

Can I apply the IMM76L update manually (there are specifica patches for each build) and still have 4G functionality or will I be stuck in 3G if I do so?

Do I need to make sure the 3G/4G Sim is active before even attempting another update?
[Xoom Q&A, Help & Troubleshooting] gooniegoogoo2:
Figured out how to get past Verizon's pushing the improper update for 4G LTE Updated XOOMS.....

1. You need to download HLK75D directly from Motorola - This is the correct firmware for the 4G LTE XOOMS to get you to HLK75H

motorola-global-portal.custhelp.com/app/standalone/rom-images

Note: You need an active Google Mail/Drive account to download

2. You can save yourself a couple patches by substituting the HLK75D Firmware files instead of the HRI66 stock firmware used in STAGE 2 (it will take 3 patches to get you to IMM76L - HLK75D --> HLK75F --> HLK75H --> IMM76L

Now the issue is ....where do I get the LTE-Baseband.zip or imm76l-radios-update.zip for the correct Baseband.....all the links I've located are dead. They radio files are not included in any of the firmware packages.

My Baseband is currently only showing CDMA_N_03.1A.65P ( No LTEDC_U_05.19.07 which is required for the 4G to work)

HELP!!!!
[Xoom Q&A, Help & Troubleshooting] gooniegoogoo2:
FINAL UPDATE:

KitKat fully functional with CM11 on my XOOM 4G LTE with full baseband files restored.......

After technical support chats with both Verizon and Motorola, we figured out that in order to restore the LTE baseband files, you MUST start with firmware image HRI66 or older then do the OTA updates on Verizon Wireless.....and activate your SIM after every patch to be sure.

Verizon pushes the HTK75D ...Baseband :	N_02.0F.00R which is the last before the 4G Upgrade was available.....

The LTE Baseband files will be installed with the IMM76L update (and also with the -F and -H patches) regardless of whether you are coming from HTK75D or HLK75H

HTK75D will patch to HLK75F then HLK75H....then to finally IMM76L (ICS).

If you experience any issues with the IMM76L patch (i.e Yellow Triangle with Exclamation Point) or an error.....You have to wipe and start over with HRI66 again. You will know if your card is registering the 4G LTE correctly if there is a '4G' next to the signal bar.

No 4G signal....check the Baseband in Settings : About Tablet.....it should read:

CDMA_N_03.1A.65P LTEDC_U_07.1F.00

If not....redo the process.

Also.....if you are thinking of switching the runtime from DALVIK to ART.......all I ran into was issues.

Android UI files were constantly crashing with error pop-ups.You may have better luck just make sure to make a full backup of your fresh KitKat install before you do it.

---------- Post added at 05:44 PM ---------- Previous post was at 05:26 PM ----------

To assist others in future....and if anyone wishes to integrate the LTE Drivers into future ROMs:

XOOM Firmwares:

http://www.randomphantasmagoria.com/firmware/xoom/trygon4g/

https://motorola-global-portal.custhelp.com/app/standalone/rom-images

XOOM INFO Firmware and Build Info / Basebands:

http://xdaforums.com/wiki/Motorola_Xoom#Official

LTE MODEM FILES/Kernel:

http://sourceforge.net/projects/ltemodem.motorola/files/LTEModem/