yashsingh1/xdaforums huggingface dataset:
[Atrix 4G General] Synertic:
Retail International MB860

Hi and thx for the guide.

There is something that confused me. I read about a ram issue from international users who unlocked their bootloader with pudding method. They all say that the usable amount of ram downgraded around 380 MB after applied pudding. I'm using a retail version of ATRIX MB860 (bought from Europe). So the question is that, will I struggle with the wrong ram amount issue after applying pudding method ? (I want to use stock kernel)

Thanks in advance.
[Atrix 4G General] filipelb:
international users u mean atrix from outside USA?
[Atrix 4G General] pienne:
Yes, for non US Atrix users
[Atrix 4G General] gkarthik16:
Working on Windows 7 64-bit?

Can anybody confirm that this method works without any issues on Windows 7 64-bit OS? Otherwise, I need to go in search of a machine with good ol' XP:D

Thanks in advance.
[Atrix 4G General] damt86:
Forgot to delete instal_recover.sh

Hello everyone, I have a Bell atrix, which until yesterday was running stock Froyo from the box.

I updated to gingerbread, and then ran this one click root:

http://xdaforums.com/showthread.php?t=1255548&highlight=bell

Afterwards, I installed Titanium backup, backed up all my system and app data.

I also downloaded rom manager, but was not able to flash Clockwork Touch Mod, I think because I hadn't unlocked the bootloader.

I proceeded to unlock the bootloader using the procedure listed in this thread.

At the end I forgot to delete the install_recovery.sh file.

I restored my phone using titanium backup, and flashed clockwork touch, it wasn't until I tried to backup my rom in Rom manager that I realized I forgot to delete the .sh file.

I have two questions:

1. will renaming or deleting the .sh file in system/etc and etc/ using RootExplorer solve my problem with backing up my rom and using clockworkmod/rommanager?

2. Since I updated to gingerbread, rooted, and unlocked bootloader, my phone has been super slow and laggy. Apps are closing on their own when I go to my homescreen like my browser or music player. It seems like my RAM is 80% in use even when nothing is open/running, so I think they may be getting closed to free up ram?

Also my lock screen which I can disable using elixir is enabling on its own randomly.

When I restored using titanium backup, my lock screen woudlnt' accept fingerprint input, and I had to go into /data/data/com.motorola.android.providers.settings/databases/settings.db and delete lock_timer lock_fingerprint and lock_type according to a fix posted on xda.

Does anyone know why my phone is so slow and laggy? Will changing the install_recover.sh, backing up with clockwork, and flashing a new rom with rom manager solve my problem?

Any help would be greatly appreciated!
[Galaxy S II General] SirRomie:
Pretty simple, all I want to be able to do is clear the data and cache of the stock widgets that come with my device. The picture frame and youtube widgets especially have a very large impact on homescreen lag and this should hopefully fix it. I am not rooted by the way and running 2.3.5 KI3 if that helps. Thanks in advance.
[Galaxy S II General] JJEgan:
Settings applications manage applications app clear data .

jje
[Droid 2 Global General] D2GxNiNjA:
ok guys heres the problem...

My bootloader is blank. ill try to get in it but the blank screen turns off and on constantly.

i cant normally boot 2.2 because im stuck at the M Splash.

i cant sbf because my bootloader is blank and my power button is jammed.

HELP
[Droid 2 Global General] leobg:
How do you access boot loader mode? If you get M screen, bootloader should be fine. The right way to access the bootloader is to hold volume up and down at the same time while phone off then press power button like you're powering on the phone.
[Droid 2 Global General] D2GxNiNjA:
My power button is jammed though.:(
[Droid 2 Global General] sd_shadow:
Can work around stuck power button

To power up you will need to connect usb to computer or hold x will connecting to charger.
[T-Mobile LG G2x] Mister Hat:
So Hey I'm using voodoo listening to music right? Either with the volume key map hack or not, and after I get a text (notification tone) it pauses the music for a second to let it play, and then it cranks up voodoo to 5db and blasts my ears. Using Faux's 4.3 on MIUI. Any ideas>?
[T-Mobile LG G2x] cyhamada:
Had a similar problem using faux's stock GB kernel. The only thing that worked was using the voodoo control app with volume key hack OFF and also using DSP manager. In DSP I only tweak the bass and EQ and don't mess with the loudness/compression stuff (leave that to voodoo).

Those two sound processors together have given me "normal" results...great sounds and the volume stays where I set it.
[HD7 General] datastor2004:
I am currently receiving the Mango (7720) update in Zune. Could this be the start of the official rollout?
[HD7 General] sh4d0w86:
yes, rollout started today.

source. Microsoft.

sh4d0w86.
[HD7 General] wizziletizzle:
I keep getting error codes that my drivers are not installed, and even if I reinstall them, I get the same error. Any help?
[HD7 General] xxtsfxx:
Ok, SO i FINALY saw the update today. Then i wanted to reset my phone before the update and after i did it is now saying there is no update available. MS is starting to really tick me off.....

Just did the "Force Udate" Trick. Idk what i would do without XDA in my life..

FML:... IT installed 7392... Guess ill keep trying...
[HD7 General] bver100:
Don't unplug it - just let it keep on going, it installed 7392 and then the intermediate 74xx (i think?) and then mango. it took me about 30 minutes to go through
[HD7 General] P1 Wookie:
It has to install previous updates before mango. I went through the same with my brother's hd7s the day the update rolled out. Didn't have to force his though.
[Captivate Q&A, Help & Troubleshooting] kipmisky:
Hi, everybody.

I am really happy i would be a new memeber of this subforum for captivate in a few days.

so my question is is captivate still being sold and manufactured at ATNT? I just want to make sure if mine is a fake or personally refurnished, low quality one.

With the IME retailers gave me, I did some research on SAMSANG, then I was told this phone was manufacutred in 27,6,2011. Is it possible? Because ATNT is not one of the carriers in the country i lived, I can't buy it directly from there.

Is this phone only avalable on contrat at ATNT? or we can just buy it and take away.

Anyone who would share your ponits would be appreciated.:confused:
[Captivate Q&A, Help & Troubleshooting] fractaline:
hi, i bought my captivate on ebay and it was still locked to att. and of course no warranty with att as i'm in AU. i unlocked and rooted with "super one click" (found here on xda)

i have not heard of any captivate that was a fake in any country.

check under the battery near the imei, there is a 4 digit build number which will indicate the approximate time of manufacture. the oldest is 1006 i think, and the newer ones begin with 11....... should be 1106 in your case

have you already bought it? i wouldn't worry too much about a fake but i guess i don't know where you are... good luck

post again your build# i'm curious now....

:)
[Captivate Q&A, Help & Troubleshooting] DaNaRkI:
Well first off AT&T does not make anything not one device. This phone was made by Samsung, and there are 3 versions. AT&T (USA), Rodgers (Canada), and Armani (special/Europe). The only differences between them is a little bit of software for the network they run on and that only the AT&T version has a audience chip for background noise cancellation.

No one here has access to any part of Samsung to know if they are still in production, nor when it end(s/ed). I would have to question just who say it was made on that date, and where is their proof.

There are no known fakes, and at this point in it's life really no reason for fakes to be made.

Depending on which ROM you use, and if it's globally unlocked, you can use the phone on any GSM type network so long as it uses the a supported frequently (this is hardware limited).

leaked from my FUSED SGS I897 contaminating you via XDA app.
[Captivate Q&A, Help & Troubleshooting] b-eock:
both canada's and usa's has the audience chip, there are no hardware differences. Now the armani i cannot speak about because i don't know.
[Captivate Q&A, Help & Troubleshooting] fractaline:
No audience chip in the i896

<«Swyped from phone»>
[Captivate Q&A, Help & Troubleshooting] b-eock:
YEs there is, look it up
[Captivate Q&A, Help & Troubleshooting] LNJ:
FCC ID on the i896 says i897. If there is any hardware difference there would be a different FCC ID.
[Captivate Q&A, Help & Troubleshooting] b-eock:
Thank you
[Captivate Q&A, Help & Troubleshooting] fractaline:
Ok, forgive my over simplification....

I have an i897 and for several months used an i896 based ROM, the Rogers firmware will not support the audience chip, at all.. Which would indicate that it was not there (if it's there why would Rogers not use it right?)... I looked it up (very briefly from the phone) at your suggestion and found that even those who took them apart to see the board could not find it.....

Yet others were confident that it's there.

The logic is sound that if there are no marked differences on the board, it must be there. But it seems unconfirmed.

So, with that I'll say.......

I don't know........... :)

<«Swyped from phone»>
[Captivate Q&A, Help & Troubleshooting] LNJ:
You can clearly hear the difference in stock AT&T roms on the i896. And as far as it not being on the board, there is no proof of it or a side by side comparison of the i897 beside a i896.

Plus you need a new FCC ID even if there is a minute difference in circuitry.
[Captivate Q&A, Help & Troubleshooting] kipmisky:
i bought it the day i posted. Now im back with my cappy. The build digits that i saw behind battery is 1106，so its a new device？

I flashed miui to my cappy which looks sooooo great and feels much faster and smooth，the only thing annoys me about this rom is the battery life that can only last for less than a day if i use it a lot，such as texting（usually lesson than 20 pieces），making phone calls（no more than 20 minutes）

and using dictionay app for 2 hours or so. does it work normally？
[Captivate Q&A, Help & Troubleshooting] apbthe3:
That sounds about right. Turning off automatic screen brightness and set the brightness as low as you can stand it is the biggest thing you can do to improve your battery life. If you search around you can find guides for other ways to improve it.
[Captivate Q&A, Help & Troubleshooting] kipmisky:
ok，i'll try this. hopefully it will work for me, and i will post again after my test.
[AT&T Samsung Galaxy S II SGH-I777] akira02rex:
Stock rom rooted w/ Entropy's Daily driver kernel at 1.6ghz

Not too shabby!
[AT&T Samsung Galaxy S II SGH-I777] kdwolf85:
Quadrants are useless. There are ways to cheat it and get you're scores above 8k.

Swyped on my Galaxy SII
[AT&T Samsung Galaxy S II SGH-I777] cliffgardner:
They are useless. That being said... View attachment 749306

Overclocked to 1.6
[AT&T Samsung Galaxy S II SGH-I777] aintwaven:
Worthless or not, I am still impressed.
[AT&T Samsung Galaxy S II SGH-I777] kletiz:
I really wish quadrant didn't exist to prevent threads like these.
[AT&T Samsung Galaxy S II SGH-I777] smjfosho:
no, THIS is impressive

but i agree, quadrant is pointless
[AT&T Samsung Galaxy S II SGH-I777] akira02rex:
Quadrant isnt totally useless as it can show benefits of overclocking. But for the most part it seems linpack is the way to go.
[Defy General] Eramix3:
Hey guys, look this: http://bbs.mfunz.com/thread-178313-1-1.html

said that SBF acts as the key to downgrade the SBF Defy +

Sorry my bad english.
[Defy General] Eramix3:
posted in the wrong place. _
[Samsung Galaxy S (4G Model)] jcjackjay:
If you flash from firmware to firmware too many times, does it mess up your phone in any way?
[Samsung Galaxy S (4G Model)] Exodian:
I flash in and out of roms a lot. A lot. And nothing in the sense your asking ever happens.
[Samsung Galaxy S (4G Model)] bkoon1218:
Just be careful when you flash your ROMs. Flashing something wrong will damage your phone. The same applies to OC or UC.
[Samsung Galaxy S (4G Model)] bhundven:
It is possible to wear out the samsung flex onenand chip(s).

http://en.wikipedia.org/wiki/Flash_memory#Write_endurance
[Samsung Galaxy S (4G Model)] avrillapete:
The /data path containing apps and cache is written and rewritten many more times than you'd ever be able to do flashing different ROMs (unless you flash many, many times a day,) so in reality, that part of the chip would most likely begin to wear out first. Not saying it doesn't effect the wear and tear on the chip, but probably not enough to worry about. You'd be more likely to corrupt something by doing a flash incorrectly.
[Samsung Epic 4G Touch] _MetalHead_:
If you guys haven't played it you MUST. It is a great sci-fi FPS and is awesome on our massive screens. You gotta grab it from gameloft.com and it's $4.99. If you're cheap Gameloft is known for doing sales from time to time, but I assure you this game is well worth the cost. Easily one of the best gaming experiences on Android right now. ONLINE MULTIPLAYER!!!

http://www.gameloft.com/android-games/nova-2-android/?adid=101966
[Samsung Epic 4G Touch] kessomatt:
OK now I'm confused. Didn't this game come with the phone? Or was it a demo? I've been trying to find out how to reinstall it.
[Samsung Epic 4G Touch] _MetalHead_:
A short demo of one of the NOVAs came with it... not sure which though, I deleted it right away. I'm sure if you did a factory reset it would come back but it's only a demo so it's not worth the hassle of the reset. Just pick up the full game from gameloft :)
[Samsung Epic 4G Touch] ipetloudog:
Hi gameloft employee! Why the eff does the game you are shamelessly plugging **** out after 10 mins of play?

And why the EFF did you make an apk for MC2 specifically for our phones that does not work? Check the markets comments on the game.

Sent from my SPH-D710 Galaxy S II [suck it]
[Samsung Epic 4G Touch] _MetalHead_:
This is the only response I have for you.
[Samsung Epic 4G Touch] kessomatt:
When I try and re-download the damn game it says "content not supported on your phone". How can it be not supported if I bought and played it already?
[Samsung Epic 4G Touch] ipetloudog:
Hey you are lucky I am not using straight profanity at your customer service, beat-around-the-bush practices. I payed for this game that you are shamelessly and anonymously promoting on this forum and I am calling you out because it doesnt work. You are being shady and my words are the consequence.

Sent from my SPH-D710 Galaxy S II [suck it]
[TouchPad General] nemosomen:
So, when you install the Alpha CyanogenMod 7 build, chances are ClockworkMod Recovery will fail. This tends to be because the custom overclocked kernels in WebOS take up a lot of room in the /boot partition, and ACMEInstaller does NOT (And maybe cannot) resize this partition. If you want to use ClockworkMod, you need to boot it via novacom.

1. Unzip the update-cwm_tenderloin-1012.zip file into the same directory as Novacom.

2. Make sure your TouchPad is plugged into your computer, and reboot it while holding volume up. You should see a USB icon.

3. In the command line, browse to the directory Novacom is installed in.

4. Type this into the command line prompt:

novacom boot mem:// < uImage.ClockworkMod

You should now be able to flash gapps or whatever else you need to install (Except moboot, which you need to use ACMEInstaller to install)

Novacom is probably installed in: "C:\Program Files\Palm, Inc" for most users.

To get there in the command line, type:

C:
cd "C:\Program Files\Palm, Inc\"

Then you can continue on to step 4.
[TouchPad General] 27scoob:
Thanks for this info , it worked great. So am I to assume if I remove overclock Kernel thenI wont have this problem and will be able to install CWM through ACme with no problems ?

Edit. Tried to uninstall F15C to no avail.
[TouchPad General] Komodo Rogue:
I don't know, but I kinda suspect not, because I brought my touchpad back to stock and *completely* wiped my touchpad before installing CM7, and I had problems with installing CWM through ACME. I don't understand the inner workings, but that seems like it may answer your question?

OP: Thanks!!!
[TouchPad General] 27scoob:
Reckon I will be tied to a cord when it comes to CWM ....
[TouchPad General] scifan:
The oc kernels get written to the main boot partition... I'm unsure which, but one of the oc kernel's can consume too much space, not leaving enough room to flash cwm... try booting into webos and removing your oc kernels... and try again... you don't have to flash the entire thing... you can just flash the cwm with the acme installer...
[TouchPad General] melvinquinones:
thanks!

I am in the CWM-based Recovery v5.0.2.6 but nothing works, not even the reboot option... any option i select does nothing.

any ideas?
[TouchPad General] Propergood:
Hold home and power, go back to USB download, start ACME install process from step one. If you follow instructions exactly, it should all work. There are occasions where you need to do the same thing twice... but your patience will pay off.
[TouchPad General] 27scoob:
Yeah I tried to remove the F15C overclock kernel and do just that with the installer . No dice , can't remove the OC kernel go to remove it and reboot to replace and it just reboots into F15C then in Preware go to put the stock kernel on goes through shows install asks for restart and just boots F15C back again .. I have also tried to just flash the CWM zip afew times throught the installer and get the error half way through about there not being enough available space..ugh..
[TouchPad General] Propergood:
Try installing one of the smaller oc kernels through preware? If not, crack out the webOS doctor..
[TouchPad General] melvinquinones:
WebOS Doctor

Tried several times, but the recovery boot did not respond, i see the menu options, backup/restore, reboot, install from ZIP, etc... but when I select the options they didnt do anything...

After several tries I decided, let me start all over so I installed webos doctor. Unfortunately I cannot share the link here..

Unfortunately after I ran it and finally clicked DONE, my touchpad wont boot, has a battery icon with a question mark inside. (The battery level should be at least 25% before you run WebOS Doctor). I left it charging for at least an hour but still on the same status, so I assume it got bricked when running the webos doctor. If the battery just went bad at the same time it would be a big coincidence.

There is a chat support which seems to be pretty good. DO NOT TELL THEM that you were trying to install Android, I assume you all know that lol..

portal dot webos dot com (Sorry, couldnt share the link here)

If battery doesnt work in an hour or 2, then I may have to send it back to repair...
[TouchPad General] Daps:
My CVM recovery works.

When I did the install yesterday I put the cm install,cvm,mboot and market all in the cminstall folder everything installed except the cvm, went back into webos and put it back in the cminstall folder and ran the ACMEInstaller again and it was there this time.

Used the CVM to install the google market update this morning.

I had Webos O/C also
[TouchPad General] Stroid01:
I installed mboot, cm7, and cwm with acmeinstaller and my CWM works just fine. Flashed gapps with it no problem....seems like a strange problem for you and misleading if you ask me
[TouchPad General] crump84:
I had a similar issue getting clockwork to flash. The problem is that some custom kernels take up too much space in the boot partition and doesnt leave enough room for cwm. Changing your webos kernel should fix the problem.

Sent from my Android powered Tenderloin
[TouchPad General] Stroid01:
That actually makes perfect sense to me...i probably never had an issue due to the fact i didnt mess with my webos kernel.

+1 for you sir
[TouchPad General] 27scoob:
Nothing strage or misleading the OC kernel is the culprit.. Just cause it orks fine on one device does not mean different things will happen on others ...Thats how things work and how this thread got started...

---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------

Yeah I thought the smae thing but I can not remove the F15C kernel.. I go through preware and uninstall , reboot , F15C boots up and then go back into preware and install stock kernel and then reboot and F15C still boots up. I have not tried to start from scratch with the Web DR. ... just trying to see if there are any other avenues try first..It's been fun trying to figure some out though lol...
[TouchPad General] crump84:
If you can't switch kernels you may have to use the doctor. Thats actually what I did before I found out about the kernel size. I didnt really care as I dont plan on using WebOS.
[TouchPad General] zuifon:
I have restored the palm kernel.

But ACMEInstaller doesn't resize partition a second time !

Is there a way to force the installation ?
[TouchPad General] nemosomen:
The boot partition cannot be resized, at least not by ACME. That is the problem. In my opinion, pushing Clockwork Recovery via USB is preferable to uninstalling an OC'd kernel. You should rarely need to use Clockwork Recovery, and in fact, most things you would normally install using it would, in the case of the Touchpad, not work.
[TouchPad General] zeke395:
: (

I know this is kinda old but im new to this, But im having this problem, I just installed CM9 and it boots nd everything, But no gapps, I went to go flash them and clockwork mod disappeared. So i stumbled on to this, When it goes to flash threw novacom It blinks the linus penguins and white words then gos backinto the boot loader with no Clockwork Recovery. I tried twice, What do i do? :confused:
[TouchPad General] dreamliner77:
Just trying to install Android on the TP for the first time... I seem to also be having this problem. Is there an update to this problem? Any new fixes? Or is everyone just dealing with either getting rid of an overclocked kernel or being tethered to a PC to get into CWM?
[TouchPad General] ph03n!x:
In case anyone is still facing this problem - I did today, and fixed it. Here goes:

Extract uImage.ClockworkMod from the clockwork zip file and place it in the SD Card of the Touchpad - you can do this in WebOS or in Android

Boot to Android if you are in WebOS

Open Terminal Emulator, type su and hit enter (accept the Super User prompt). Make sure you have enabled Root Access for Apps if you face any issues here (Settings > Developer Options > Root Access)

The following commands have to typed in the Terminal

mount -o rw,remount /boot
cd /boot
cp /sdcard/uImage.ClockworkMod
chmod 644 uImage.ClockworkMod
reboot

The Touchpad would now reboot and show the moboot options - you should see ClockworkMod as the 3rd option if all went well.
[TouchPad General] sstar:
Just a heads up if you are installing cyanogenMod 9

You will need update-cwm_tenterlion-1012

See this thread

http://xdaforums.com/showthread.php?t=1539194
[TouchPad General] unglued94ta:
I have tried this. After I type in chmod 644 uImage.ClockworkMod, it gives me the error "Unable to chmod uImage.ClockworkMod: No such file in directory"

any idea's
[TouchPad General] amarkow2:
I'm having the same issue
[TouchPad General] nelodroid:
hi! is this also can apply to CM9 bcz i cannot also go to boot recovery mode.. tnx!
[TouchPad General] Stuba:
Worked! But...

This worked out for me. I just wanted to add that in my case I was stuck on the CM9 boot screen ( all other boots were gone), and the device wouldn't take much of a charge. When I would re-boot and hold the volume botton down, I'd get a promt to rechage (Power plug image). Eventually I tried leaving on the Touchstone with usb connected to pc. I got a little red digital power readout. When it hit 25% I ran webos doctor (which left everything intact) then followed the instructions above (Thanks!) and booted right into CWMod. I expanded the partition and flashed everything from there, wiping caches fixing permissions and roobooting at each flash. I'm a total noob but my CM9 is working perfectly!