Original DockProvider/DockService/PortalApp.apk - Atrix 4G General

Since I accidentally ran the webtopmod installer twice, it overwrote the backups of DockProvider.apk, DockService.apk, and PortalApp.apk, which I need to restore from the originals to remove the WebtopMod.
As the files are modified, it blocks me from updating, saying the check failed. Also, doing a software restore or clearing the data from the bootloader menu does not replace these files with the originals, as I have found out the hard way.
Could someone please upload the original files so that I can update again? I would like to remove the webtop mod so I can update again.

i have the same problem..

me tooooooooooo
i know flashing sbf can solve the problem but it is a bit troublesome

guys go into the dev section..locate the hot to undo webtopmod..someone has posted the original files on page 3 of that thread

You should have backup copies in:
/mnt/sdcard/WebtopModBackup/

No action when connecting an HDMI cable or Dock
Hi guys,
Same problem here.
After following Fenny's instructions I got a direct HDMI webtop, but the device did not worked as a mouse, the screen was just freezed.
So I decided to buy the dock, but the situation mentioned above continued.
I tried doing a software restoring and clearing the data, but nothing happened.
Then I tried the original files (PortalApp, DockService, and DockProvider) from the thread suggested here.
What is sad is that after replacing the files from Fenny's thread for those indicated at (Backup Files ADDED!) [How To] [MOD] Undo Webtop Mod [MOD] [How To], my atrix stopped recognizing when there is an HDMI cable connected.
It just doesn't show any options, nothing!
I have an AT&T Atrix 4G, 4.5.91 Gingerbread.
And now an official dock, that does not work.
Please help!
Thanks!

Hi every one
I got the same problem here with bell atrix.
How do you guys install back the orginal files (PortalApp, DockService, and DockProvider)? I also follow the guide from Fenny's thread for those indicated at (Backup Files ADDED!) [How To] [MOD] Undo Webtop Mod [MOD] [How To], but I was with no luck to install back the original files.
anyone has a solution to help me out?? it would be apprecited.

can't you just flash a fruitcake? it's as stock as possible without SBF flashing...

Alcapone263 said:
can't you just flash a fruitcake? it's as stock as possible without SBF flashing...
Click to expand...
Click to collapse
I am on Bell GB 2.3.4. i tried to flash again, but with no luck. Dockprovider is not there. I am thinking whether i try to flash bell GB leak. If so, can i come back to GB 2.3.4 again??

Preserve Stock Webtop apk's
Same problem for me. For future use, I was thinking about modding Fenny's WebtopMod.sh to retain the stock webtop apks after the first backup. Something like this...
# retain existing WebtopMod folders
if [ -d /data/local/tmp/WebtopMod ]
then
echo "Keep existing WebtopMod backup folder...\n"
else
mkdir /mnt/sdcard/WebtopModBackup
fi
echo "Backing up ..."
...

Related

[Q] Restore to default ROM

I'm trying to restore my Acer Iconia A500 back to the stock/ original ROM so that I can grab the official update in July. Is there any way to do that? I really like the custom ROMS, I just want to revert to see what it was like.
Mestiza5683 said:
I'm trying to restore my Acer Iconia A500 back to the stock/ original ROM so that I can grab the official update in July. Is there any way to do that? I really like the custom ROMS, I just want to revert to see what it was like.
Click to expand...
Click to collapse
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Yes I'd also be interested in this. I have the droid x so when ever I want to revert to factory settings theirs a program on the computer (rsd lite) I use to revert it. So I almost never backup my roms. Now on my iconia they don't have such program. At least that I know of. So I flashed a rom on my iconia and didn't make a backup of my current one. I tried fixing it by flashing stock_acer a500.zip I thing by dexter don't quote me on that one. But it was the emea version so now its stock european and I live in america. Help is apreciated.
I'm a flashing person that has flashed many times on my phones. I forgot to make a nandroid backup of my original rom myself...so I'm not judging. I would say, flash honeyvillian, as its the closest thing to stock I've seen.
But, if your already flashing, I wouldn't want to grab the official anything...someone will post it once it comes out.
Sent from my A500 using XDA Premium App
I want to flash it to the latest stock. So when ota 3.1 is released, I could rest assure knowing that my device would get updates ota.
Euclid's Brother said:
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Click to expand...
Click to collapse
because we are impatient and stupid
I am running to get someone with a tablet of my country to get back the STOCK ROM in case of... I am going to see if I can deal with the shop to root and recovery on SD Card the stock rom so I will be able to have the stock rom...
For USA version 1.104.02, Check out this post.. You'll probably want to skip flashing the stock recovery until you know the system will boot normally.. So from this post, run itsmagic, flash boot, flexrom and system, in that order. Preferable from an adb connection. The tablet will freeze while flashing system. Give at least 5 mintues to make sure it's complete.
You may need to do a data wipe if it bootloops (that's why you should skip flashing recovery). Once it's booting normally, you can flash the stock recovery if you want.
Alternatively, you should be able to replace the files in dexter's stock update zip with these files. But I haven't looked at that zip, so I don't know if system is an image file or a archive file.
Thanks for the replies quick question though. How do in run its magic is their a command for ADB or do I acess it via clockwork recovery?
Respawntime said:
Thanks for the replies quick question though. How do in run its magic is their a command for ADB or do I acess it via clockwork recovery?
Click to expand...
Click to collapse
You download it from the itsmagic thread in the development form and follow the directions in that thread.
Euclid's Brother said:
And, of course you made a backup via clockworkmod???? eh?
Why are so many not making backups of their tabs before installing unknown software?
There's lots of threads about this in the forums with instructions already. And this belongs in the General forum, not development.
Click to expand...
Click to collapse
I too would like to restore to the 3.0.1 stock rom, however my backup of the stock rom got corrupted somehow. I know it had to be something I done, but know not what it was I did. Any help would be much appreciated. Or would it be a better idea to flash the 3.1 leak?

[Updated 2-11-2012] THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs

So you’re a N00B with a brand new Android device, and you have no idea what all this sbf, adb, bootloader talk is all about; you just want to know how to do cool stuff with your new phone and be as cool as all of us Senior Members
Well here’s a Atrix N00B Guide just for you that will hopefully be a good jumping off point for you to start exploring and getting into the world of themeing, ROMing, flashing, etc. Most of this stuff was pulled from various XDA forums, and is easy enough to find, if you just take the time to search for it, but being the nice N00B friend that I am, I thought I’d try and compile most of it one place. So here goes…
*If you can’t figure something out or need help with whatever your particular problem may be, before you go cluttering up the forums with your problem and you get blasted by Senior Members like me use the SEARCH bar at the top of each section and/or thread. I promise you, you are not the first person to have your problem, and more times than not, your problem has been answered more than once. People HATE seeing questions that were just answered one or two pages previously. SO USE THE FREAKING SEARCH BUTTON!!!
*NOTE: Most of the following links are going to be for U.S. AT&T based phones only. Sorry, but that’s what I have and that’s what I know. Most of you BELL & other international guys should find some of this useful though, and most of the links below also have a international build version now.
CLICK HERE FOR UPDATES​
Lets start with some basic terminology & general understanding:
What is Root / Rooting?
Put simply, Rooting your device allows you, and/or rooted apps, to access parts of the Linux based Android software that is your OS, and that you would otherwise not be able to access. These tasks can be as simple and beneficial as backing up your system setting, or as complicated as installing custom ROMs, Kernels, etc. (more on this later).
What is a Motorola .SBF file?
SBF stands for Single Binary File, and contains a firmware image that can be installed on your device. i.e. they are more of less what you are installing on your device when you do a OTA (over the air) update; except an actual .sbf file that you download and flash on your own will most of the time not only contain the updated info. in the OTA, but also all the other “stock” info. that came with the device. That’s why when you flash a .sbf file it will return you to a stock/retail device.
What is ADB?
ADB = Android Debug Bridge. So what this basically is, is a command/terminal based interface you can run from your PC, to interact with your device and its file structure. You can PUSH (install) programs, apps, .apk files, etc. to your device, move things around, set permissions, etc. One of the primary things to remember when trying to use adb, is that you need to enable debugging on your device. In fact it’s a good idea to enable this, and leave it that way… forever! This setting can be found on your device under Settings -> Applications -> Development -> USB debugging
Here is a list of helpful adb commands:
http://android-dls.com/wiki/index.php?title=ADB
What is a ROM?
A rom is like a custom firmware image that is made by a Developer either entirely from scratch, or based off of the official firmware package. Some ROMs contain simple changes like changing icons and adding extra options to things, other more complicated ROMs can change the entire Android experience. Which one you will want to flash, will be entirely up to you. Read carefully, and make sure you understand what you are getting into before you flash.
What is a Kernel?
As a rule of thumb, if you have to ask, you probably shouldn’t be messing with this anyway. But hey, best for you to at least know what it is. A kernel is the heart of the device's OS. In simplest terms it’s a connection between your apps and your device’s hardware; i.e. the processor, RAM, etc. A custom kernel can dramatically change the way your device’s hardware performs… for the better and/or the worse.
What is a Bootloader?
The bootloader is a program code that is executed before the device OS starts up, and that instructs that device to boot “normally”. The bootloader can come locked or unlocked from the manufacture. A unlocked bootloader will allow you to install custom ROMs & Kernels (as well as some other neat things) on your device.
What is a odexed and de-odexed framework, and what is the difference between the two?
Just read this:
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
What is CWM Recovery (ClockWorkMod Recovery)?
CWM is a custom recovery program that allows you to backup / restore a full or partial system backup of your device. It also allows you to install flashable .zip files; which is one of the primary installation methods for custom ROMs. It also provides other neat features such as cache wiping, battery reset, and other processes. Long story short, if you are thinking about flashing custom ROMs or just want a really good backup program, incase you FUBAR your device, you need to install this.
What is Fastboot?
Again, just read these for description & helpful Commands:
http://forum.xda-developers.com/showthread.php?t=619153 [Thanks briggie108]
or
http://android-dls.com/wiki/index.php?title=Fastboot
What is all this CM7 stuff about?
CM7 stands for CyanogenMod v7. It's a very popular ROM, b/c of its built-in options, great enchantments and total removal of manufacture software; i.e. all that MotoBlur stuff on your device is gone. It is a stripped down fast and well designed ROM with a custom kernel, that allows for easy flashing of great custom themes (just check out the General Theme Section for Android on XDA). Only a small selection of Android devices have a "official" release of CM7, however almost all Android devices have a "un-official" port for it. The Atrix 4G port is currently in its pre-beta stage and is being worked on by the Atrix Dev-Team.
More info. on CM7 can be found here:
http://www.cyanogenmod.com/
And here:
http://en.wikipedia.org/wiki/CyanogenMod
The #1 rule of CyanogenMod is that you do not ask for timetables!!! You have been warned. If you choose to ignore my warning, ask away and prepare to be blasted until you cry.
Information on the current status of the Atrix 4G port of CM7, as well as a list of current bugs, can be found here:
https://code.google.com/p/atrix-dev-team/
CM7.1 Beta for the Atrix is Available Now!!!
Information, install instructions, etc. can be found here:
http://forum.xda-developers.com/showthread.php?t=1257574
CM7 Nightlies Now Available for the Atrix (a.k.a. Olympus)
*Note: Nightly builds may be unstable, and are unsuppoted by the Dev Team.
http://download.cyanogenmod.com/?device=olympus
Nightly change log can be found here:
http://cm-nightlies.appspot.com/?device=olympus
The current version of CM7 for the Atrix does not yet support the following:
- Webtop
- Fingerprint Scanner
- Pocket Detector
- Horizontal HDMI Mirroring
MY CYANOGENMOD INSTALLATION GUIDE:
http://forum.xda-developers.com/showpost.php?p=19986512&post=234
Theme Chooser Themes for CM7 (200+):
http://forum.xda-developers.com/showthread.php?t=1167075
*Please make sure to search the thread before you post an already answered question. Also, if you have the $ available, please consider a $donation$ to the Atrix Dev Team for their continued hard work (remember, this is still beta, they're still working hard at it).
ATRIX (4.5.91 FIRMWARE) HOW TOs:
Here are some How To Guides that may be helpful to new Atrix 4G owners that have just got thier phone & have the most recent firmware = 4.5.91 (Android 2.3.4). Read each How TO carefully and completely before attempting. If you are unsure of what to do, or how to do it, ask a question first. I will try a put this is a order that somewhat makes sense.
HOW TO FLASH A SBF:
WARNING: If you are on Android 2.3.4 (4.5.91) w/ a unlocked bootloader, do NOT flash back to a earlier sbf version. DOING SO WITH BRICK YOUR DEVICE!!! Use CWM Fruitcake described below instead.
SBF Hints, Tricks & Guidelines:
- Always make sure to flash with a full battery! The last thing you want to do is run out of juice in the middle of a sbf flash; that's a great way to brick your device.
- As a general rule of thumb before flashing a sbf file to your device, you should always download the sbf file to a file path on your computer with the least possible spaces (i.e. the shorter the file path to the sbf file the better). So just download it to the root drive of your computer, such as C:\.
- Also, because these sbf files are so long, this sometimes causes problems with RSD Lite (the program you use to flash the sbf to your device). So, I would suggest you change the file name to something short, like OLYFR.sbf. It doesn’t so much matter what you name the sbf file, just so long as it’s short, does not contain any spaces in the name and you do not change the .sbf file extension. This will help prevent errors when trying to flash (no, I don’t know why, it just does).
- If you are running Windows on your PC, open RSD Lite as a Administrator. Also, when you open RSD Lite, Instead of browsing for the sbf file via the normal “…” button in the program, just drag the sbf file onto the file path bar in RSD Lite. Sometimes, the sbf file will not load when you select it via the browser button in RSD Lite (again I have no idea why).
- Once your sbf file begins to flash to your device, be patient… the device will re-boot at least a couple times in the flash process. Do not get jumpy and disconnect your device until RSD Lite says you are 100% done! Doing so can cause your device to BRICK! If for some reason you have waited for an inordinate amount of time, and it does not say finished, then ask for help on the thread, before unplugging. The same goes for pulling the battery. DO NOT DO THAT!!! Pulling your battery during a sbf flash, is one sure fire way to brick your device. Only pull the battery as a last resort and only after you have asked for help.
- RSD Lite has been updated to v5.3.1, here is the download link:
http://www.mediafire.com/?zz81vf1o2y73d4n
or
http://www.datafilehost.com/download-33dce367.html
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
*Note: After unlocking your bootloader and installing a CWM (*see below), you have the option to flash stock sbf files named "Fruitcakes" that do not require RSD Lite to flash (see information below).
HOW TO UNLOCK YOUR BOOTLOADER FOR ANDROID 2.3.4 (FIRMWARE 4.5.91):
WARNING: If you are on Android 2.3.4 (4.5.91) w/ a unlocked bootloader, do NOT flash back to a earlier sbf version. DOING SO WITH BRICK YOUR DEVICE!!!
Try the automated scrpit in this thread: http://forum.xda-developers.com/showthread.php?t=1182871
or
Try the original unlock method in the Main Pudding Thread: http://forum.xda-developers.com/showthread.php?t=1136261
*Use the instructions on this page for this method: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader]
Directions are in the respective OP
HOW TO ROOT YOUR DEVICE ON ANDROID 2.3.4:
One Click Root For Motorola Phones Running Android 2.3.4:
http://forum.xda-developers.com/showthread.php?t=1255548
Alternative Root Methods:
Follow the instructions in this post:
forum.xda-developers.com/showpost.php?p=15872818
or
These Instructions:
http://briefmobile.com/motorola-atrix-4g-root
*Note: Many of the ROMs you may wish to install, after your boot loader is unlocked, will also include a ROOT package. Check the indiviual ROM OP to make sure though.
HOW TO INSTALL CWM RECOVERY ON 2.3.4:
CWM Options:
With 2.3.4, you now have 2 different options available for CWM Recovery. You should have a unlocked bootloader, be rooted and be on Android 2.3.4 (firmware version 4.5.91), before attempting to flash any of these. Each is described below.
Option 1: RomRacer's CWM
http://forum.xda-developers.com/showthread.php?t=1204500
- This CWM is extremely stable & has multiple features, such as the ability to choose whether to backup the webtop portion of your device, or not. It supports both ext-sd (micro sd card) and internal sd (internal storage). You can also choose from a variety of colors & supports both U.S AT&T and International users. This CWM will also be the official CWM of CM7 ported by the Atrix Dev Team.
- I personally prefer this CWM as it also works with ROM Manager (app from the market - *see details below).
*Note: If you do not have any CWM Recovery installed yet, you can use the fastboot commands in the OP (use the non .zip version to install via fastboot), or you can install via ROM Manager with the below instructions.
*Note: If you already have a different version of CWM Recovery installed, and want to switch to RomRacer's, then first check to see if a file labeled "install-recovery.sh" @ /system/etc/. If the file is there, delete it, before proceeding with the install of RomRacer's version.
Install Instructions to Use RomRacer's CWM w/ ROM Manager APP:
1) Download the ".zip" file of your color choice (make sure you choose the right version AT&T or international), and place the .zip file on the sd-card (internal storage).
2) Download ROM Manager from the Market (paid or free, it doesn't matter) and install app.
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
3) Open ROM Manager and select "Flash ClockworkMod Recovery," making sure to select the right device (i.e. Atrix 4G). This will flash the current version of CWM to your device, which will also work (see details/limitations discussed below).
4) Now, choose "Install ROM from SD Card", and choose the .zip file that you saved on your internal storage. You should not need to delete any of the cache options. ROM Manager will reboot the device into CWM and flash the .zip automatically, and then reboot again.
5) You should now have RomRacer's custom CWM installed over the ROM Manager version. You can now select Reboot into Recovery from ROM Manager, and it should boot into CWM Recovery.
Option 2: ROM Manager's Stock CWM
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
- For install instructions, see steps 1-3 under the RomRacer's CWM.
- Allows for easy CWM updating, as well as ROM updates that are posted by the developer on ROM Manager's servers.
- Current build much better, and allows for both internal & external sd installs/backups.
HOW TO INSTALL FRUITCAKES ON 2.3.4 (GREAT SBF/RSD ALTERNATIVE!!!):
If you have a unlocked boot loader and CWM Recovery installed, and you wish to go back to "stock" you now have a wonderful alternative called Fruitcake. The fruitcake files are essentially stock sbf files that bypass the need to use RSD Lite; they flash via CWM just like any other .zip file that you flash. This is very welcome as it eliminates the need for RSD Lite and the problems associated with it.
You can find your Fruitcake here: http://forum.xda-developers.com/showthread.php?t=1163009
WHAT DO I DO IF MY DEVICE WILL NOT FULLY BOOT??? (i.e. Boot Loop or Soft Brick):
- If you have a bootloop/softbirck after atempting to unlock your bootloader:
a) If you flashed the unlock .sbf, are you sure you booted into fastboot and issued the "fastboot oem unlock" command.
b) If you happen to have a 2.3.4 ROM saved on you device, or a Fruitcake.zip, try booting into Android Recovery and reflashing. Make sure to wipe dalvik cache, cache partition, and format data first though.
c) If you can boot into fastboot, you can fastboot flash the "stock" 2.3.4 Gingerbread .img/system files by following the instructions on this page:
http://forum.xda-developers.com/showthread.php?t=1163342
*Note: The .img files to install via fastboot are located under "Download Gingerbread Stock Images" on the download page.
- If you have bootloop/softbrick after attempting to flash a ROM or Kernel:
a) Did you download the correct version of the ROM or Kernel for your device (i.e. US AT&T vs International).
b) If you're installing a new kernel, did you flash back to the stock kernel first, before trying to flash the different kernel.
c) Are you sure you wiped the dalvik cache, cache partition & formated the data (i.e. The Big Three) before installing the ROM. For a kernel install, just wipe dalvik cache & chace partition.
*Note: If you are using the stock ROM Manager CWM version, then you need to fastboot wipe for fomating data, as this feature does not yet work on ROM Manager. Fastboot command: "fastboot -w".
d) Try re-flashing ROM, after making sure you did the above 3 correctly... still not working, you can hopefully still:
1) Flash a Fruitcake in CWM to give you a clean install. Make sure to wipe "the big 3" first.
2) Can't get into Android Recovery/CWM, try flashing the stock Gingerbread .img files via fastboot. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1163342
The 2.3.4 (4.5.91 Firmware) Section:
Updated ROMs, Kernels, etc. for 2.3.4 (firmware 4.5.91) --- UPDATED 8/14/2011
So with the official release of Gingerbread 2.3.4, a host of new ROMs & Kernels have been released for the Atrix, along with various fixes and mods for those ROMs & Kernels. I'll try and cover the most common ones below, as always if you feel something needs to be added, just let me know.
*Note: Before flashing any of these make sure that you:
1) Have a unlocked boot loader:
http://forum.xda-developers.com/showthread.php?t=1136261
2) Have CWM installed
3) Understand Fastboot/moto-fastboot commands
ROMs & Kernels:
FYI:
Before installing any ROM or Kernel I suggest you do the following to help prevent error, boot-loops, etc. Also, it's a good idea to flash a new ROM or Kernel on a fully charged device:
1) Download which ever ROM or Kernel you plan on flashing and have the .zip on your device ready to flash.
2) Backup your apps (not system data), contacts, etc. Also consider making a CWM backup of your device, just in case.
3) Boot into CWM Recovery
4) Wipe Dalvik Cache (under advanced in CWM)
5) Wipe Cache Partition
6) Wipe data/factory reset
6a) If you're using ROM Manager/CWM you will need to reboot the device after step 5, and upon reboot enter fastboot mode and enter the command: "fastboot -w" or "moto-fastboot -w" if you prefer using moto-fastboot. Then type "fastboot reboot" and upon reboot make sure to enter Android Recovery again, so that you can flash the ROM/Kernel.
7) Install .zip from SD Card (choose the .zip you wish to install)
8) If you installing a radio, theme, kernel, etc. on top of a ROM, I would suggest redoing the whole wipe process again between flashes.
9) Reboot the Device
- If you get a boot loop, try entering Android recovery and re-wiping the chace and data, and perhaps try reflashing the ROM/Kernel. Or if you made a CWM backup, you can always restore that.
ROMS
Stock Gingerbread 2.3.4 (Thanks KennethPenn):
*Note: This is useful if you need to return to stock Gingerbread. Both CWM & Fastboot install available.
http://forum.xda-developers.com/showthread.php?t=1163342
Home Base ROM (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1242721
This is a "stock" Android base ROM, with multiple versions ranging from almost stock with only a few tweaks, to a stock feel with multiple mods, extras, etc.
ASOP Atrix ROM (by Stinebd):
http://forum.xda-developers.com/showthread.php?t=1306550
ASOP = Android Open Source Project - - in other words, it's supposed to make your device as close to a stock Google Android device as possible (i.e. like a Nexus device).
*Note: since this rom is essentially a stock Android experience, many of the Atrix's stock features will not work; like the fingerprint scanner, webtop, etc.
Alien ROM & Theme (by KennethPenn):
*Note: The ROM is separate from the theme, which can be applied afterwards if you wish.
http://forum.xda-developers.com/showthread.php?t=1186537
This is a very stable ROM, however there are a few issues with the Theme portion. The Kernel is stock 2.3.4.
Ninja ROM (by SamCripp):
http://forum.xda-developers.com/showthread.php?t=1173843
Super fast ROM, with Faux123's Kernel included.
Cherry Pie & Pie Crust (by Navalynt):
http://forum.xda-developers.com/showthread.php?t=1189497
Includes optional themes and has a separate international build version.
Aura ROM (by Diviance):
http://forum.xda-developers.com/showthread.php?t=1186990
Includes Faux's Kernel
3 versions to choose from (de-bloat, de-bloat w/ accounts, & w/ all bloat)
DarkSide ROM (by Nottach):
http://forum.xda-developers.com/showthread.php?t=1222108
Includes Faux's Kernel
Multiple Mods available to add to ROM
Theme incorporates many apps
HoneyComb ROM/Theme (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1206767
Based off of Alien ROM w/ a Honey Comb Theme. Different versions are available for different kernel choices.
iBlur ROM (by Marko!):
http://forum.xda-developers.com/showthread.php?t=1305015
Like the look of the iPhone... but hate the iPhone. Give this ROM a try then.
StarWars Rom/Theme (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1200214
Ying / Yang ROM (by Shady_lanem):
http://forum.xda-developers.com/showthread.php?t=1244852
Nice black/white ROM, with all the latest tweaks, mods, etc.
KERNELS
Faux's Kernel (over-clocked @ 1.45 GHz):
http://forum.xda-developers.com/showthread.php?t=1156040
*Note:
- Froyo version, Gingerbread version & CM7 version, each w/ multiple versions avaliable; a enchanced stock kernel @ 1 GHz that allows undervolting, profiles, etc. Also a OC kernel @ 1.3 GHz & 1.45 GHz.
- Make sure you pick the right kernel; i.e. if you are on CM7, use a CM7 kernel, if you are using a Gingerbread based ROM, use the Gingerbread kerenl.
- The overclocked 1.45 GHz kernel may cause heat issues with your battery, thus causing random reboots... suggest undervolting.
Kholk's EternityProject Kernel (over-clocked @ 1.5 GHz):
http://forum.xda-developers.com/showthread.php?t=1153003
*Note:
- Current build based off of Faux's kernel.
- Kernel may cause heat issues with your battery, thus causing random reboots... suggest undervolting.
Clemsyn's Kernel (over-clocked @ 1.4 GHz):
http://forum.xda-developers.com/showthread.php?t=1354502
*Note:
- Based off of Faux's Kernel, but includes additonal optimizations.
- AT&T and CM7 versions available @ either 1.0 GHz or 1.4 GHz.
- B/C of memory timings, this kernel may not work on your device (like mine), and you will not be able to fully boot. Make sure you have a backup kernel to flash incase this happens to you.
OTHER MODS & FIXES:
V6 SuperCharger Script
My Instructions Here: http://forum.xda-developers.com/showpost.php?p=18906120&post=201
Battery Jumping Fix:
*Note: Charge battery to 100% (overnight) & wipe battery stats in CWM (under advanced) before flashing this.
http://forum.xda-developers.com/showthread.php?t=1174349
WEBTOP on 2.3.4:
http://forum.xda-developers.com/showthread.php?t=1169457
Native Tethering MOD for 2.3.4 (included in the above ROMs):
http://forum.xda-developers.com/showthread.php?t=1160452
All Atrix 4G AT&T Radios:
http://www.multiupload.com/G8T8IGZF05
2.3.4 Ported Boot Animations:
http://forum.xda-developers.com/showthread.php?t=1162936
OTHER HELPFUL THREADS:
How To Recover From A Soft Brick:
http://forum.xda-developers.com/showthread.php?t=966405
The Same Thing As This Thread (Posted in the Dev Section), Without All The Fluff:
http://forum.xda-developers.com/showthread.php?t=972423
Theming the Atrix 4G: tools, processes, locations, etc.:
http://forum.xda-developers.com/showthread.php?t=1060199
How To Port A Theme:
http://forum.xda-developers.com/showthread.php?t=1186819
How To Theme Gingerblur / Compiling & De-compiling a Framework (This is what got me started):
XDA Thread Here: http://forum.xda-developers.com/showthread.php?t=1101138&highlight=gingerblur
How To Here: http://briefmobile.com/how-to-theme-gingerblur
List of ROOT APPS available & working on the Atrix:
http://forum.xda-developers.com/showthread.php?t=1099846
A Whole Bunch of Icon Sets (for when you're ready to start customizing):
http://forum.xda-developers.com/showthread.php?t=824656
Widget Locker Themes:
http://forum.xda-developers.com/showthread.php?t=968613&highlight=D3S-L002
How to Manually Deodex Any Atrix ROM:
http://forum.xda-developers.com/showthread.php?t=1162764
Invaluable Resource:
http://gitbrew.org/android/
Terrific Info!
Great job as usual Swiftks!! It's always nice having everything in one place. Sometimes searching XDA can be frustrating with the amount of search results. This should help everyone, not just the noobs.
Good work.. Only way to be useful is its stickied so it isn't lost
Sent from my MB860 using XDA Premium App
Great post/thread, someone should sticky this... Maybe it will help reducing all the generic questions...
Might want to add asking for cm7/miui
Sent from my MB860 using XDA Premium App
Nice thread, just what i needed, i am new to the Atrix and i need all the help i can get. Cheers Dude
What a great thread. I am well versed in rooting and flashing my nexus one, even did some minor development for it. But this is a very useful summary for the atrix, and not everything is the same between devices. For example I had no idea what an sbf file was.
I'm glad this is helping some of you. I thought of a few more details I can add to the OP when I get home today... also, I'll see about trying to get stickyfied.
Sent from my MB860 using XDA Premium App
Swiftks said:
What is Root / Rooting?
Put simply, Rooting your device allows you, and/or rooted apps, to access parts of the Linux based Android software that is your OS, and that you would otherwise not be able to access. These tasks can be as simple and beneficial as backing up your system setting, or as complicated as installing custom ROMs, Kernels, etc. (more on this later).
Click to expand...
Click to collapse
You have made a great post that will help a lot of new people out. For rooting it would be helpful to add that all rooting does is give you the equivalent of the Administrator account, like in Windows.
For your fastboot/bootloader section. I always point new people to this:
http://forum.xda-developers.com/showthread.php?t=619153
Your link is pretty good. I like the one I posted as well. It is a little advanced, but it also has some added fluff for newbies.
Also some advice while flashing in general. Never ever do a battery pull unless you are absolutely 100% sure something went wrong and the phone is frozen. Some mods take a while to install, or the progress bar might not be coded in correctly. I have made some personal mods where the progress bar screwed up. After a couple minutes of freaking out, all of a sudden cwm goes "Ding, done!" so yeah patience is key.
I second that it should be stickied....
Very well written guide. Wish this guidewould have been here when I started flashing. Will be very helpful to the newbies coming to the atrix/xda. Good job.
Sent from my MB860 using XDA Premium App
Woow i feel like dev after reading this lol ^__^
thanks!!
GreAt thread! Question, was my post the one you are talk in about for the non-market apps enabled? I posted that just recently and worked like a charm. I was surprised that it did. It is ironic how an app from app store enables non market apps..lmfao. Great work on thread.
demandarin said:
GreAt thread! Question, was my post the one you are talk in about for the non-market apps enabled? I posted that just recently and worked like a charm. I was surprised that it did. It is ironic how an app from app store enables non market apps..lmfao. Great work on thread.
Click to expand...
Click to collapse
Yeah, I think it might have been.
Am Updating the OP now with some more info.
Sent a request to Mr. Clown for a Stick, and he said they he would do it... so hopefully this thread won't get lost for future noobs.
One thing though is instead of calling it the "noobs" guide? Why not just call it beginners guide cause the new people coming here are probably not gonna have any idea wth a noob is anyway! Great guide besides that though!
Gutterball said:
One thing though is instead of calling it the "noobs" guide? Why not just call it beginners guide cause the new people coming here are probably not gonna have any idea wth a noob is anyway! Great guide besides that though!
Click to expand...
Click to collapse
Makes Sense...
I was a total noob when I picked up my Atrix back in Feb. Proceeded to mess around with things and soft-bricked it. Took me a few days to seach for all of this information and finally get it back to stock. Thanks for putting it all in one spot!!
this just just great work dude.
Can you include a brief explanation about what CWM is?
Edit: Oops... I saw that you've already done this.
yay its stickied...good job man

Bricked Atrix can't restore

Ok hello all, I have a bricked atrix here (new user) and cannot restore the previous firmware I backed up.
What I did step by step is:
I followed this guide to unlock phone and install CWM recovery mod. ( I backed up my factory "firmware" )
After that I installed Neutrino ROM 2.2 from here but it was a bit buggy and I wanna revert to my factory settings.
When I try to restore the old firmware checking md5 and bootloader restore ok, system gives me a message: "Error while restoring /system"
At some point I also installed "recovery-en-goapk-0630-1029" which seems just another recovery tool (dont know if this caused the issue)
I also have RSD Lite and the original ATT's 4.5.91 .sbf file but that cant work as well. Once I hit RSD mode on my phone and hit start on pc, phone says after a couple of mins: sec_exception: febe, 35, 35 and then doesnt progress anymore.
By the way my phone is European and it came with 2.3.4 preinstalled out of the box, I just wanna revert it back! please help!
what's that "sec_exception" about? I always get this when I try to RSD-mount the .sbf from ATT 2.3.4 Pudding
RSD tells me a short after: Failed Flashing Process. Phone [0000] . Phone did not re-enumerate after RAM-downloader was sent (0x703E); phone connected (Result FAIL)
First of all, I don't think you should be using an ATT sbf file with your European Atrix. Not a good idea; they are not the same.
Secondly, using a sbf and RSD is tricky business and should be avoided if possible.
If you want to return to stock I suggest using the tool in this thread:
http://forum.xda-developers.com/showthread.php?t=1421522
It is dead simple to use.
since I'm new to this (got some good pc experience tho) I wanna keep things clean and organized, so what can I do to clean previous installations , zips , rsd sbf mounting etc. As I see this, the phone's memory has 2 partitions, 1 for system and 1 for apps? Correct me if I'm wrong I'm just starting to get familiar with all this thing
If you follow the link above it will wipe everything on the phone and return it to stock. You will need to wipe your SD card yourself however.
Sent from my MB860 using XDA App
I had this with all recovery iv try I found out its because the system.ext3.tar backup is over 300mb the only the only. Way back from this was to ever flash a European gingerbread sdf or use fruitcake
the way I got past this was to deodx my rom so it is under 300mb
following the above link is the best method. please do so.
the method is perfect indeed, my phone is back to normal except that AT&T submenus and logo. Is there any program to view root folders and clean previous installations / garbage files? Any guides on what should be left off - uninstalled? (Neutrino 2.2 custom ROM had a file explorer that could navigate between root folders and sd storage
thanks again
i got the same issue but my phone doesnt turn on at all, just the led light in green then it goes off
have you tried to pull the battery off? Do you see the Motorola logo or just black screen?

Is it bricked?

I originally followed this:
http://www.modaco.com/topic/341011-ultimate-guide-to-the-huawei-u8800/
and rooted the phone
Then I followed this:
http://forum.xda-developers.com/showthread.php?t=1420728
and I read this:
http://forum.xda-developers.com/showthread.php?t=1492957
I thought that the phone had 2.3.5 on, and then after a while (After I flashed the new zip file), I realised that it only had 2.3.3 on and it won't get past the Huawei screen ie: it's stuck
I backed up the current ROM, but I've no idea on what to do now that it's bricked. I've tried fixing permissions, connected via USB and using the "adb logcat" command when I got the reply
/sbin/sh: exec: line 1: logcat: not found
And it's just stuck at the boot screen. Just wondering if any one can help?
Re-flash firmware.
Sent from my U8800 using Tapatalk 2
Qqqxxxzzz said:
Re-flash firmware.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
I haven't the foggiest as to why my last post didn't go through. Any way, I did do that and I tried to restore my current ROM as well - remember it hasn't had the 2.3.5 update
On another note, my post also serves as a "hello" post considering that I didn't realise that I had an account here with zero posts until recently. I must have made it a while ago so hello
Hi, I didn't notice it because I use tapatalk.
Sent from my U8800 using Tapatalk 2
That's not a bricked people. A bricked phone is one that does not turn on no matter what, does't react in any shape or form, no screen, no vibration, no sound, no led when plugging usb or charger, no pink mode, no pc access to the phone, no nothing.
Your phone goes to huawei loading screen! How is that a bricked phone? Just reflash The ROM and do triple wipes. Search the forum for that.
flash stock rom. 2.3 or 2.2
not bricked
i can trustly say that it's not bricked, a brick phone means "unusable hardware tools"
the implementation that you explained can not cause a brick operation, you only have to teach your phone to work - that its possible to install the original stock rom.
original stock rom images also contains hubbable hardware working scripts and images.
so you can get your system back and also imei.
fjsferreira said:
That's not a bricked people. A bricked phone is one that does not turn on no matter what, does't react in any shape or form, no screen, no vibration, no sound, no led when plugging usb or charger, no pink mode, no pc access to the phone, no nothing.
Your phone goes to huawei loading screen! How is that a bricked phone? Just reflash The ROM and do triple wipes. Search the forum for that.
Click to expand...
Click to collapse
Thanks for that. I'll go off to search for a stock ROM
EDIT: Which stock ROM do I use?
http://coraldrive.net/users/androidz/583/u8800 stock roms
Once I've got the correct ROM, then I'll probably follow this:
http://forum.xda-developers.com/showthread.php?t=1011527
I'm putting that link in, to help others and in case I can't find it. I'm from the UK if that helps
So today, I loaded the general overseas version stock ROM and formatted the Micro SD card to FAT32 and it loaded with android 2.2 on it (yay)
However, I can't download the official 2.3 ROM because the Huawei site is having problems with it's server, and every file sharing site I've seen has deleted it for "copyright infringement" Why the hell Huawei even requested for it's removal, when it doesn't even work from their own site, I have no idea
So, just wondering if there's any kind people out there that can send us the official 2.3 ROM either by email or a public dropbox link, which can then be deleted?
Thanks
EDIT: I may have found something:
huaweidevice.com/worldwide/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDQzNTg=
Just an update to show what I've now done, in case any one else has the same problem. Go here:
huaweidevice.com/worldwide/downloadCenter.do?method=toDownloadFile&flay=softw are&softid=NDQzNTg=
(XDA forums won't allow me to insert external live links just yet)
Download the file from there. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1011527
Follow step 12 and onwards from here:
http://forum.xda-developers.com/showthread.php?p=22682229#post22682229
I also deleted the dload folder, in case I accidentally revert it to stock ROM. I also had to run SuperOneBoot again because it was unrooted after I flashed the official ROM
To get clockword mod, go here:
http://forum.xda-developers.com/showthread.php?t=1420728
Once you've got clockword mod, a rooted phone etc... and if you follow the guide posted above, then you can also install custom ROM's on to your Huawei device
Thanks to the XDA people for providing these guides

Important/Urgent: Who has a STOCK Verizon tab 7.7 (SCH-i815)

I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
electron73 said:
I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
Click to expand...
Click to collapse
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
I'll check my laptop at home tonight. I believe I kept my heimdall backup before flashing cwm
Sent from my DROID BIONIC using Tapatalk 2
Just checked, mightve deleted it. Sorry man
aximtreo said:
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
Click to expand...
Click to collapse
Oh that would be awesome! Are you rooted? Let me find the commands in the meantime, I read somewhere it's a simple one command in terminal to extract the recovery partition into a file on sd card...
WHAT AN ORDEAL !!!!
But in the end: SUCCESS!
I managed to get my tab updated with the Verizon OTA update.
The problem is definitely CWM !!! A rude awakening is in store for everyone with the P6800 CWM installed, because it a) fails to verify the checksum of OTA files correctly on the i815, b) it thinks the tablet is a P6800, so the OTA file fails to run if it assert checks for "SCH-i815" hardware AND lastly c) modem updates don't work because the device /dev/cdma_update doesn't exist, so the modem.bin firmware_update call fails !!!
In short, I had to fumble the OTA file apart and do the update manually in two runs:
First file, kick the checksum, hardware check and modem update out, then manually run the ZIP through CWM. The zip subsequently (LUCKILY) updated the stock recovery and overwrote CWM with a new fresh stock recovery.
Second file had everything kicked out BUT the modem udpate and LTE patch, so with the STOCK recovery this file ran through just fine, updated the modem and then applied the LTE delta patch.
Phew!!!
Of course I had to manually restore root after the update, had backed up with voodoo, auto restore failed, so terminal and hacking it was...
Now I have the tab running on clean stock FD01, baseband and LTE FD01, rooted and stock recovery.
No more CWM, no more "hacking" with the ROM until some dev finally releases a "correct" CWM and at least ANY factory ODIN image is available to bring the tab back to stock if needed!!!
Kinda sick of the non-support for this tab. So much going on for the Galaxy Note and pretty much every other device. I'm starting to regret having bought this "special" Verizon version
Awesome find and great to know for whenever ics does come out. Could you please post the recovery img you got?
Sent from my DROID BIONIC using Tapatalk 2
OK after getting so many responses I decided to just post everything here in hopes that it will help others, too:
All files are here:
http://www.mywo.org:88/XDA/sch-i815/index.php
Step by step procedure to update the Verizon Tab from ..FA02 to ..FD01 build IF YOU ARE stuck with CWM installed on your tab and the original OTA fails with errors:
Upload the SCH-I815_FA02c_To_FD01.1.zip to the INTERNAL(!) SD card. This is important because CWM contains a bug that will only allow you to install from ZIPs stored on the INTERNAL SD storage.
Upload the SCH-I815_FA02c_To_FD01.2.zip to the EXTERNAL(!) (micro SD) card. This is important, because after the factory recovery is restored, it will correctly (and only) look for ZIPs on the EXTERNAL card.
Best way just copy both files to both locations
Fire up CWM and do "install from ZIP" and select SCH-I815_FA02c_To_FD01.1.zip
It should run (takes a while) and eventually tell you all is done. BOOT the tab. It should boot fine but in system it will show the new Android build FD01 but the baseband (radio) will still be the "old" one.
Now press and hold power and vol up again until you see the default Samsung recovery menu. Choose install from ZIP and select SCH-I815_FA02c_To_FD01.2.zip. This will now upgrade the baseband only. When done, reboot and enjoy being back on the "factory upgrade path" with the tab.
I hope someone more savvy than me can "fix" CWM to work properly with VZW tabs (accept the checksum, not fail the check for "SCH-i815" and provide the correct /dev file links for radio upgrades). Until then, I recommend just leaving the tab as-is and not tinkering with the ROM. Not that there is any custom ROM available anyway :-(
I also pulled the NEW factory recovery image FD01_recovery.img with the following command:
dd if=/dev/block/mmcblk0p6 of=/sdcard/FD01_recovery.img bs=4096
So in case anyone with a botched recovery wants to restore factory (Samsung 3e) recovery. This was actually the reason I had to go through all this... There is NO factory recovery image ANYWHERE to be found. I can't believe that I should be the first one ever to post one?? Anyway, hope it will help
I'm still quite new here, so I do really appreciate every click on that "thanks" button
P.S. for tinkerers and devs I also uploaded the original, untouched OTA file (0559c0e4e08e.update_SCH-I815_FA02c_To_FD01.bin) as it came from Samsung or Verizon or whatever and ended up in the /cache partition.
THANK YOU!
Electron,
You sir, are a BOSS! Thank you so very much for doing the work, and sharing it. You just made things one hell of a lot easier on me, and anyone else that follows.
Regards,
-Rob
Also want to say thanks. You rock, dude. I wouldn't have known how to revert **** on my own.
Also, I feel like we need a sticky or something for sch-i815 owners to go to for device specific stuffs, especially since there is little knowledge/info out for this device.
Sent from my Galaxy Nexus using xda premium
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
phigmeta said:
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
Click to expand...
Click to collapse
You're in luck! You don't need to go through the whole ordeal because you do NOT have CWM! You can just update the regular intended way. Go into settings, about phone and then click check for system updates. If it presents you the OTA update, just do it the regular way.
My complicated "hack" is only necessary if you DO HAVE CWM installed.
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
phigmeta said:
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
Click to expand...
Click to collapse
Hey
OK unless someone can tell us how to "make" an ODIN flashable ROM for you, here is what I would do (and please don't get scared because it sounds a bit convoluted).
First, you need to be rooted. This is obviously the case.
IMPORTANT since you don't have CWM installed yet, SAVE your factory restore.img before proceeding, this saves you a lot of hassle later!
Open the android terminal, type su (accept the prompt) and then type (or copy/paste)
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/factory_recovery.img bs=4096
Check that you have a "factory_recovery.img" file on your sd card now it should be about 8M big.
Now you're safe to install CWM from the forum, look for the other thread(s) where this is being discussed and follow the instructions for the P6800 "international" version with 3G. CWM Thread here:
http://forum.xda-developers.com/showthread.php?t=1613638&highlight=cwm&page=3
Then (thanks to nicduim!) there is a full factory (rooted) CWM image floating around on the forums here:
http://forum.xda-developers.com/showthread.php?t=1613638&page=6
Which I used to restore my tab to "almost factory" with the missing bloat apps back in place.
I have a copy on my server here: http://ww.mywo.org:88/XDA/sch-i815/ it's the "2012-05-06.22.48.58.ZIP"
unzip that and put the contents on your INTERNAL SD card in the folder clockwordmod. So on your internal SD you should have /clockworkmod/2012-05-06.22.48.58 and inside there the files boot.img, recovery.img etc.
Use CWM recovery to restore this backup. If you never used CWM before. Press power button and volume up and hold both until you see the menu screen with text. You can go up/down with the volume buttons (go slow, it's very laggy) and with the power button you "select" an option. Select the "restore from backup" option and point it to the only folder being offered, the 2012-05-06.22.48.58.
The restore takes a while, then reboot the tab. Now you're back to stock! Last thing you need to do is get rid of CWM again because in the end it's still a bit buggy and will prevent the OTA update from running properly.
Since you luckily have a backup of the factory recovery in form of that factory_recovery.img file, just install and open terminal again, type su and then type (or copy)
dd if=/mnt/sdcard/factory_recovery.img of=/dev/block/mmcblk0p6 bs=4096
This overwrites CWM with your original Samsung Android recovery.
Now you just reboot as usual, connect to the internet and wait until the popup message shows up that a system update is ready, accept it and enjoy
If you don't want to wait for the automatic OTA, you can also stop before killing CWM and use my convoluted 2-step manual update which will get you to the exact same condition as the official OTA.
Hope all this makes sense
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
AlpineMan said:
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
Click to expand...
Click to collapse
Oh wait, so you are saying that in "About device" your Android is 3.2
Baseband i815.04 V.FD01 I815FD01
and your Build number is already at HTJ85B.I815FD01.SCH-I815.I815FD01 ?
That would mean you are already updated. In this case, it should be pretty easy to fix your problem. Which apps did you delete with Titanium? I can back them up from my system and make them available for you. All you'd need to do is drop the backup files into your Titanium backups folder and then fire up titanium and restore them!
The /dev/cdma_update node is only required WITHIN CWM recovery, so that is nothing for you to worry about. The zip files above won't help you because they are incremental updates requiring your system to be at FA02, not FD01 !
Yes... I'm already in the latest update. I already backed up the bloatware using Titanium Backup before uninstalling. So I just need to restore them back in order to receive and apply OTA updates in the future?
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
Please Help
Hi. I'm rooted and removed all sorts of bloatware with Titanium. I did this a long time ago and did not back anything up because I'm used to running hardware with custom ROMs available, and not relying on OTA updates.
Since there aren't any custom ROMs for the i815, I'd like to get ready for the upcoming ICS update. To do so, I want to get FD01 loaded onto my device, but I can't update because I've apparently removed too much of the required bloatware.
Does anyone know WHAT pieces of bloatware I'd need to reinstall in order for the OTA update to apply? I'd assume I can restore them and then apply the update and re-root.
If anyone can help pinpoint what missing APKs might help, I'll give them a shot. And, to the extent I figure anything out, I'll repost here in the hopes that it helps someone else.
electron,
Your instructions worked ... thank you so much
@jkrell... the failed attempt at installing the update should return an error message(s). You just have to read through them until you find the culprit(s). Apparently I uninstalled a few odexed files that were needed. I couldn't update until i hunted them down and restored them.
I guess we all jumped at the opportunity to install the cwm recovery image, that we didn't even think about cmda updates....ooops. So far i had to do a complete factory restore after the update. I was getting soft bricked to the point where I had no choice. Good thing I sent all titanium backups to actual sd card, i was able to salvage 97% f my data..... with the exception of a few downloads i forgot to move.
Gamecih doesn't work anymore (either version). No more automative data hacks I'm not sure what's going on. I uninstalled adfree..used titanium backup to uninstall both versions and reinstalled both several times. Oh well.
It really sucks not having nandroid backups but it's not worth the trouble of having to do this everytime an OTA modem update gets pushed to my tab. Needless to say, I won't be odining the cwm based recovery image again.
I'm with the O.P. I wish i hadn't wasted my money on this tab. No true cwm for this tab, so no dev will ever waste thier time with this tab. The sch i815 will soon be forgotten about and some other tablet will be all the hype before summer ends....that's just how it is. 21 months left on my contract.... [email protected]#k my life. Lol
Thanks Smitty.
When I try to update, I just see the "!" logo and then the device reboots. Is there a log file somewhere I can look at to see what the errors are?
I hear ya on the gloom and doom, but this device has only been out for just over 3 months now. I'd expect a recovery and some custom ROMs to come eventually. I doubt I'll go the custom ROM route unless CyanogenMod is supported, because I have no complaints about the tablet's performance thus far. It's speedy, smooth and the battery lasts forever.
In my book, this is a great tablet and I'm satisfied with the purchase.

Categories

Resources